JUNOSe 9.1.x Link Layer Configuration Guide > Configuring Multilink Frame Relay > Monitoring MLFR

Monitoring MLFR

Use the commands in this section to display information about MLFR interfaces.

You can set a statistics baseline for an MLFR bundle or subinterface using the baseline frame-relay interface mlframe-relay command. Similarly, you can set a statistics baseline for an MLFR link with the baseline frame-relay multilink interface command. Use the delta keyword with the show commands described below to display statistics with the baseline values subtracted.

After you configure multilink Frame Relay, you can use the show frame-relay commands to view information about the multilink. For information about these commands, see Chapter 2, Configuring Frame Relay.

You can use the output filtering feature of the show command to include or exclude lines of output based on a text string you specify. Refer to show Commands in JUNOSe System Basics Configuration Guide, Chapter 2, Command-Line Interface, for details.

baseline frame-relay interface

• Use to set a statistics baseline for the Frame Relay layer on MLFR bundles, Frame Relay interfaces, subinterfaces, and circuits.
• Specify the keyword mlframe-relay and the name of the MLFR bundle to set a baseline for the Frame Relay statistics on an MLFR bundle.
• The router implements the baseline by reading and storing the statistics at the time the baseline is set and then subtracting this baseline whenever baseline-relative statistics are retrieved.
• You cannot set a baseline for groups of interfaces, subinterfaces, or circuits. You must set baselines one at a time.
• When baselining is requested, the time since the last baseline was set is displayed in hours:minutes:seconds or days/hours format. If a baseline has not been set, the message "No baseline has been set" is displayed instead.
• The regular interface statistics and LMI statistics for interfaces are subject to the same baseline timestamp. You cannot set separate baselines for these statistics.
• Use the optional delta keyword with Frame Relay show commands to specify that baselined statistics are to be shown.
• Example

host1#baseline frame-relay interface mlframe-relay boston

• There is no no version.

baseline frame-relay multilinkinterface

• Use to set a statistics baseline for MLFR links.
• The router implements the baseline by reading and storing the statistics at the time the baseline is set and then subtracting this baseline whenever baseline-relative statistics are retrieved.
• When baselining is requested, the time since the last baseline was set is displayed in hours:minutes:seconds or days/hours format. If a baseline has not been set, the message "No baseline has been set" is displayed instead.
• The regular interface statistics and LIP statistics for interfaces are subject to the same baseline timestamp. You cannot set separate baselines for these statistics.
• Use the optional delta keyword with Frame Relay show commands to specify that baselined statistics are to be shown.
• Example

host1#baseline frame-relay multilinkinterface serial 3/2

• There is no no version.

show frame-relay interface

• Use to display the information about the Frame Relay layer of the interface.
• Use the brief keyword to display the operational status of all configured interfaces.
• Use the optional delta keyword to specify that baselined statistics are to be shown.
• Field descriptions

• Frame relay interface mlframe-relay—Name of the MLFR bundle
• Status of the major Frame Relay interface—One of the following states:

• Up—Traffic can flow on the interface
• Offline—Traffic cannot flow because hardware is unavailable
• Down—Traffic cannot flow because of a problem in the interface at the current protocol layer
• LowerLayerDown—Traffic cannot flow because of a problem in an interface at a lower protocol layer
• AdministrativelyDown—Traffic cannot flow because of manual administrative intervention

• Number of interface down transitions—Number of interfaces that have changed to a down state
• Time since last status change—Time since the interface last changed its state
• In bytes—Number of inbound bytes received on the interface
• In frames—Number of inbound frames received on the interface
• In errors—Number of inbound errors received on the interface
• In discards—Number of inbound packets discarded
• In unknown protos—Number of packets received on the interface with unknown protocols
• Out bytes—Number of outbound bytes transmitted on the interface
• Out frames—Number of outbound frames transmitted on the interface
• Out errors—Number of outbound errors transmitted on the interface
• Out discards—Number of outbound packets discarded

• Example 1

host1#show frame-relay interface brief

Frame relay interface mlframe-relayTEST, status is up

• Example 2

host1#show frame-relay interface mlframe-relay TEST

Frame relay interface mlframe-relayTEST, status is up

Number of interface down transitions is 0

Time since last status change 00:01:47

Number of configured circuits: 2

  In bytes: 452              Out bytes: 198

  In frames: 19              Out frames: 11

  In errors: 0               Out errors: 0

  In discards: 8             Out discards: 0

  In unknown protos: 0

• Example 3

host1#show frame-relay interface mlframe-relay members

Frame relay interface mlframe-relay TEST is up

   Frame relay multilink member-interface 4/0:1 is up

   Frame relay multilink member-interface 4/1:1 is up

show frame-relay lip

• Use to display the state of MLFR Link Integrity Protocol (LIP) on an MLFR link.
• Use the brief keyword to display the operational status of all configured interfaces.
• Use the delta keyword to specify that baselined statistics are to be shown.
• Field descriptions

• Frame relay interface—Specifier for the Frame Relay interface
• Status of the major Frame Relay interface—One of the following states:

• Up—Traffic can flow on the interface
• Offline—Traffic cannot flow because hardware is unavailable
• Down—Traffic cannot flow because of a problem in the interface at the current protocol layer
• LowerLayerDown—Traffic cannot flow because of a problem in an interface at a lower protocol layer
• AdministrativelyDown—Traffic cannot flow because of manual administrative intervention

• Number of interface down transitions—Number of interfaces that have changed to a down state
• Time since last status change—Time since the interface last changed its state
• Add Links sent—Number of Add Link messages sent from this interface
• Add Links received—Number of Add Link messages received on this interface
• Add Link Acknowledgments sent—Number of Add Link acknowledgments sent from this interface
• Add Link Acknowledgments received—Number of Add Link acknowledgments received on this interface
• Add Link Rejects sent—Number of Add Link Reject messages sent from this interface
• Add Link Rejects received—Number of Add Link Reject messages received on this interface
• Hellos sent—Number of Hello messages sent from this interface
• Hellos received—Number of Hello messages received on this interface
• Hello Acknowledgments sent—Number of Hello messages sent from this interface
• Hello Acknowledgments received—Number of Hello messages received on this interface
• Remove Links sent—Number of Remove Link messages sent from this interface
• Remove Links received—Number of Remove Link messages received on this interface
• Remove Link Acknowledgments sent—Number of Remove Link acknowledgments sent from this interface
• Remove Link Acknowledgments received—Number of Remove Link acknowledgments received on this interface

• Example 1

host1#show frame-relay lip brief

LIP information for frame relay interface 4/0:1, status is up

Number of interface down transitions is 0

Time since last status change 00:03:16

LIP information for frame relay interface 4/1:1, status is up

Number of interface down transitions is 0

Time since last status change 00:03:20

• Example 2

host1#show frame-relay lip interface serial 4/0:1

LIP information for frame relay interface 4/0:1, status is up

Number of interface down transitions is 0

Time since last status change 00:05:19

  Add Links sent: 1

  Add Links received: 1

  Add Link Acknowledgements sent: 1

  Add Link Acknowledgements received: 1

  Add Link Rejects sent: 0

  Add Link Rejects received: 0

  Hellos sent: 32

  Hellos received: 31

  Hello Acknowledgements sent: 31

  Hello Acknowledgements received: 32

  Remove Links sent: 0

  Remove Links received: 0

  Remove Link Acknowledgements sent: 0

  Remove Link Acknowledgements received: 0

show frame-relay lmi

• Use to display configuration and state information and statistics about the LMI.
• You can specify an interface type and location.
• Use the brief keyword to display abbreviated PVC information.
• Use the delta keyword to specify that baselined statistics are to be shown.
• DTE field descriptions

• Frame relay DTE interface mlframe-relay—Name of the MLFR bundle
• N391—Value of the N391 full-status polling counter
• N392—Value of the N392 error threshold counter
• N393—Value of the N393 monitored events counter
• T391—Value of the T391 link integrity polling timer interval
• Configured LMI type—One of the following options:

• ANSI—ANSI T1.617 Annex D
• Q933A—ITU-T Q.933 Annex A
• Cisco—Original Group of Four specification developed by DEC, Northern Telecom, Stratacom, and Cisco
• None—Suppresses LMI

• status is up—Availability of the MLFR bundle: up or down
• Number of interface down transitions—Number of times the interface has become unavailable
• Time since last status change—elapsed time since LMI information changed

• Enquiries sent—Total number of LMI status inquiries sent by the DTE on this interface
• Full enquiries sent—Total number of LMI full status inquiries sent by the DTE on this interface
• Enquiry responses received—Total number of LMI full and regular status responses received by the DTE on this interface
• Full enquiry responses received—Total number of LMI full status responses received by the DTE on this interface
• Async updates received—Total number of asynchronous LMI updates received by the DTE on this interface
• Unknown messages received—Total number of unknown LMI messages received on this interface
• Loss of sequencing detected—Total number of times a loss of sequencing in received LMI messages was detected by the DTE on this interface
• No response timeouts—Total number of times a timeout occurred without receiving a response to an LMI request by the DTE on this interface
• Last sequence number sent—Last sequence number sent on this interface
• Last sequence number received—Last sequence number received on this interface

• DCE field descriptions:

• Frame relay DCE interface mlframe-relay—Name of the MLFR bundle
• N391—Value of the N391 full-status polling counter
• N392—Value of the N392 error threshold counter
• T392—Value of the T392 polling verification timer
• Configured LMI type: one of the following options:

• ANSI—ANSI T1.617 Annex D
• Q933A—ITU-T Q.933 Annex A
• Cisco—Original Group of Four specification developed by DEC, Northern Telecom, Stratacom, and Cisco
• None—Suppresses LMI

• status is up—Availability of the MLFR bundle: up or down
• Number of interface down transitions—Number of times the interface has become unavailable
• Time since last status change—Elapsed time since LMI information changed

• Enquiries received—Total number of LMI status inquiries received by the DCE on this interface
• Enquiry responses sent—Total number of LMI status responses sent by the DCE on this interface
• Full enquiry responses sent—Total number of LMI full status responses sent by the DCE on this interface
• Async updates sent—Total number of LMI ASYNC updates sent by the DCE on this interface
• Unknown messages received—Total number of unknown LMI messages received on this interface
• Loss of sequencing detected—Total number of times a loss of sequencing in received LMI messages was detected by the DCE on this interface
• No response timeouts—Total number of times a timeout occurred without receiving a status inquiry from the DTE on this interface
• Last sequence number sent—Last sequence number sent on this interface
• Last sequence number received—last sequence number received on this interface

• Example 1

host1#show frame-relay lmi brief

LMI information for frame relay DTE interface mlframe-relayTEST

DTE parameter N391 is 6, N392 is 3, N393 is 4, T391 is 10

Configured LMI type is ANSI, status is up

Number of interface down transitions is 0

Time since last status change 00:05:39

• Example 2

host1#show frame-relay lmi interface mlframe-relay TEST

LMI information for frame relay DTE interface mlframe-relayTEST

DTE parameter N391 is 6, N392 is 3, N393 is 4, T391 is 10

Configured LMI type is ANSI, status is up

Number of interface down transitions is 0

Time since last status change 00:06:20

  Enquiries sent: 39

  Full enquiries sent: 7

  Enquiry responses received: 39

  Full enquiry responses received: 7

  Async updates received: 0

  Unknown messages received: 0

  Loss of sequencing detected: 0

  No response timeouts: 0

  Last sequence number sent: 39

  Last sequence number received: 39

show frame-relay map

• Use to display the current Frame Relay and MLFR map entries.
• Field descriptions

• subinterface—Name and subinterface number of the MLFR bundle in the format bundle-name.subinterface-number
• State of the subinterface—One of the following states:

• Up—Traffic can flow on the interface
• Offline—Traffic cannot flow because hardware is unavailable
• Down—Traffic cannot flow because of a problem in the interface at the current protocol layer
• LowerLayerDown—Traffic cannot flow because of a problem in an interface at a lower protocol layer
• AdministrativelyDown—Traffic cannot flow because of manual administrative intervention

• DLCI number—Decimal value, hexadecimal value, and value as it appears on the wire of the DLCI

• Example

host1#show frame-relay map

Frame relay sub-interface mlframe-relayTEST.1 (up): DLCI 16(0x10,0x4)

Frame relay sub-interface mlframe-relayTEST.2 (up): DLCI 17(0x11,0x14)

show frame-relay multilinkInterface

• Use to display the statistics about all MLFR interfaces or the specified MLFR interfaces.
• Field descriptions

• Multilink Frame relay interface—Specifier for the Frame Relay interface
• State of the MLFR interface—One of the following states:

• Up—Traffic can flow on the interface
• Offline—Traffic cannot flow because hardware is unavailable
• Down—Traffic cannot flow because of a problem in the interface at the current protocol layer
• LowerLayerDown—Traffic cannot flow because of a problem in an interface at a lower protocol layer
• AdministrativelyDown—Traffic cannot flow because of manual administrative intervention

• Number of multilink interface down transitions—Number of interfaces that have changed to a down state
• Time since last status change—Time since the interface last changed its state
• In bytes—Number of inbound bytes received on the interface
• In frames—Number of inbound frames received on the interface
• In errors—Number of inbound errors received on the interface
• In discards—Number of inbound packets discarded
• In unknown protos—Number of packets received on the interface with unknown protocols
• Out bytes—Number of outbound bytes transmitted on the interface
• Out frames—Number of outbound frames transmitted on the interface
• Out errors—Number of outbound errors transmitted on the interface
• Out discards—Number of outbound packets discarded

• Example

host1#show frame-relay multilinkInterface

Multilink Frame relay interface 6/2:2, status is down

Number of multilink interface down transitions is 0

Time since last status change 2 days, 23 hours

  In bytes: 0                Out bytes: 0

  In frames: 0               Out frames: 0

  In errors: 0               Out errors: 0

  In discards: 0             Out discards: 0

  In unknown protos: 0

show frame-relay pvc

• Use to display statistics about PVCs for Frame Relay interfaces.
• Specify a DLCI number or an interface type and location.
• Use the optional delta keyword to specify that baselined statistics are to be shown.
• The brief keyword displays abbreviated PVC information.
• Field descriptions

• DLCI—DLCI number
• subinterface—Name and subinterface number of the MLFR bundle in the format bundle-name.subinterface-number
• status—Status of the PVC
• Number of circuit status inactive transitions—Number of times a circuit came down because of error conditions
• Time since creation—Time since the PVC was created
• last status change—Time since the PVC status last changed
• In pkts—Number of incoming packets received on the circuit
• Out pkts—Number of outgoing packets transmitted on the circuit
• In bytes—Number of input bytes received on the circuit
• Out bytes—Number of output bytes received on the circuit
• In FECN pkts—Number of packets received with the forward explicit congestion notification (FECN) bit set. The FECN bit is set by a network to notify the user that data traffic may experience congestion in the direction of the frame carrying the FECN bit. The FECN bit is set by the network (not by the transmitting user), and there is no obligation for end systems to take any action regarding the FECN bit.
• Out FECN pkts—Number of packets transmitted with the FECN bit set
• In BECN pkts—Number of packets received with the backward explicit congestion notification (BECN) bit set. The BECN bit is set by a network to notify the user that data traffic may experience congestion in the opposite direction of the frame carrying the BECN bit. The BECN bit is set by the network, and there is no obligation for end systems to take any action regarding the BECN bit.
• Out BECN pkts—Number of packets transmitted with the BECN bit set
• In DE pkts—Number of packets received with the discard eligibility (DE) bit set. When the DE bit is set, it indicates that the frame is discarded in preference to other frames without the DE bit set. The DE bit may be set by the network or the user. Once it is set, it cannot be reset by the user.
• Out DE pkts—Number of packets transmitted with the DE bit set
• Dropped packets—Number of dropped packets

• Example 1

host1#show frame-relay pvc brief

PVC information for frame relay DTE interface mlframe-relayTEST

DLCI 16 in sub-interface mlframe-relayTEST.1, status is active

DLCI 17 in sub-interface mlframe-relayTEST.2, status is active

• Example 2

host1#show frame-relay pvc interface mlframe-relay TEST

PVC information for frame relay DTE interface mlframe-relayTEST

DLCI 16 in sub-interface mlframe-relayTEST.1, status is active

Number of circuit status inactive transitions is 0

Time since creation 00:07:20, last status change 00:07:11

  In pkts: 14               Out pkts: 0

  In bytes: 420             Out bytes: 0

  In FECN pkts: 0           Out FECN pkts: 0

  In BECN pkts: 0           Out BECN pkts: 0

  In DE pkts: 0             Out DE pkts: 0

  Dropped pkts: 14

DLCI 17 in sub-interface mlframe-relayTEST.2, status is active

Number of circuit status inactive transitions is 0

Time since creation 00:07:20, last status change 00:07:11

  In pkts: 14               Out pkts: 0

  In bytes: 420             Out bytes: 0

  In FECN pkts: 0           Out FECN pkts: 0

  In BECN pkts: 0           Out BECN pkts: 0

  In DE pkts: 0             Out DE pkts: 0

  Dropped pkts: 14

show frame-relay subinterface

• Use to display the state of the subinterface.
• The subinterface can be in one of the following states:

• Up—Traffic can flow on the interface
• Offline—Traffic cannot flow because hardware is unavailable
• Down—Traffic cannot flow because of a problem in the interface at the current protocol layer
• LowerLayerDown—Traffic cannot flow because of a problem in an interface at a lower protocol layer
• AdministrativelyDown—Traffic cannot flow because of manual administrative intervention

• Use the brief keyword to display only the operational status of all configured subinterfaces.
• Use the optional delta keyword to specify that baselined statistics are to be shown.
• Field descriptions

• Frame relay sub-interface mlframe-relay—Name and subinterface number of the MLFR bundle in the format bundle-name.subinterface-number
• status—State of the subinterface, as follows:

• Up—Traffic can flow on the interface
• Offline—Traffic cannot flow because hardware is unavailable
• Down—Traffic cannot flow because of a problem in the interface at the current protocol layer
• LowerLayerDown—Traffic cannot flow because of a problem in an interface at a lower protocol layer
• AdministrativelyDown—Traffic cannot flow because of manual administrative intervention

• Number of sub-interface down transitions—Number of times a subinterface came down because of error conditions
• Time since last status change—Time since the last status change on the subinterface
• In bytes—Number of inbound bytes received on the subinterface
• Out bytes—Number of outbound bytes transmitted on the subinterface
• In frames—Number of inbound frames received on the interface
• Out frames—Number of outbound frames transmitted on the interface
• In errors—Number of inbound errors received on the subinterface
• Out errors—Number of outbound errors transmitted on the subinterface
• In discards—Number of inbound packets discarded
• Out discards—Number of outbound packets discarded
• In unknown protos—Number of packets received on the subinterface with unknown protocols

• Example 1

host1#show frame-relay subinterface brief

Frame relay sub-interface mlframe-relayTEST.1, status is up

Frame relay sub-interface mlframe-relayTEST.2, status is up

• Example 2

host1#show frame-relay subinterface mlframe-relay TEST

Frame relay sub-interface mlframe-relayTEST.1, status is up

Number of sub-interface down transitions is 0

Time since last status change 00:07:49

  In bytes: 512              Out bytes: 0

  In frames: 16              Out frames: 0

  In errors: 0               Out errors: 0

  In discards: 16            Out discards: 0

  In unknown protos: 0

Frame relay sub-interface mlframe-relayTEST.2, status is up

Number of sub-interface down transitions is 0

Time since last status change 00:07:50

  In bytes: 512              Out bytes: 0

  In frames: 16              Out frames: 0

  In errors: 0               Out errors: 0

  In discards: 16            Out discards: 0

  In unknown protos: 0

show frame-relay summary

• Use to scan all defined Frame Relay interfaces and circuits and to report the status for each discovered interface and circuit as follows:

• Up—Traffic can flow on the interface
• Down—Traffic cannot flow because of a problem in the network
• Unavailable—Traffic cannot flow because hardware is unavailable

• Example

host1#show frame-relay summary

2 multilink interface(s) defined, 2 up, 0 down

1 interface(s) defined, 1 up, 0 down

2 sub-interface(s) defined, 2 up, 0 down

2 circuit(s) defined, 2 up, 0 down