[Contents] [Prev] [Next] [Index] [Report an Error]

Monitoring Frame Relay

Use the show frame-relay commands described in this section to monitor Frame Relay interfaces.

You can set a statistics baseline for Frame Relay interfaces, subinterfaces, or circuits using the baseline frame-relay command.

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. See show Commands in JUNOSe System Basics Configuration Guide for details.

If you do not specify an interface type for the appropriate show command, the output indicates whether a serial or POS interface is being displayed.

baseline frame-relay interface

Use to set a statistics baseline at the Frame Relay layer for multilink Frame Relay, POS, serial or GRE tunnel interfaces, subinterfaces, or circuits.
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.
Specify an interface or subinterface using the interface type and specifier. For more information, see Interface Types and Specifiers in JUNOSe Command Reference Guide.
Specify a circuit using the interface type and specifier and the dlci keyword and the dlci number.
You cannot set a baseline for groups of interfaces, subinterfaces, or circuits. You must set baselines individually.
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.
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 serial 2/0:1/1

host1#show frame-relay interface delta
Frame relay interface 2/0:1/1, status is lowerLayerDown
Number of interface down transitions is 0
Time since last status change 21:06:34
Number of configured circuits: 0
Time since last baseline 00:00:05
  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

There is no no version.
See baseline frame-relay interface.

show frame-relay interface

Use to display statistics for the Frame Relay layer in a multilink Frame Relay, POS, serial, or GRE tunnel interface.
Optionally, you can specify an interface using the interface type and specifier. For more information, see Interface Types and Specifiers in JUNOSe Command Reference Guide.
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
- status—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
- Description—Text description or alias if configured for the interface
- In bytes—Number of inbound bytes received on the interface
- Out bytes—Number of outbound bytes transmitted on the interface
- 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 interface
- Out errors—Number of outbound errors transmitted on the interface
- In discards—Number of inbound packets discarded
- Out discards—Number of outbound packets discarded
- In unknown protos—Number of packets received on the interface with unknown protocols
- Time since last status change—Time since the last status change on the interface

Example

host1#show frame-relay interface
Frame relay interface 3/2:1/1, status is up
Description: boston01
Time since last status change 01:21:10
  In bytes: 19712            Out bytes: 60918
  In frames: 1232            Out frames: 1232
  In errors: 0               Out errors: 0
  In discards: 0             Out discards: 0
  In unknown protos: 0
Frame relay interface 3/2:2/1, status is up
Description: newyork02
Time since last status change 03:06:18
  In bytes: 19728            Out bytes: 60702
  In frames: 1233            Out frames: 1233
  In errors: 0               Out errors: 0
  In discards: 0             Out discards: 0
  In unknown protos: 0
Frame relay interface 3/2:3/1, status is up
Description: chicago03
Time since last status change 01:20:38
  In bytes: 19696            Out bytes: 60744
  In frames: 1231            Out frames: 1231
  In errors: 0               Out errors: 0

See show frame-relay interface.

show frame-relay lmi

Use to display configuration and state information and statistics about the LMI for a multilink Frame Relay, POS, serial, or GRE tunnel interface.
Optionally, you can specify an interface using the interface type and specifier. For more information, see Interface Types and Specifiers in JUNOSe Command Reference Guide.
Use the optional delta keyword to specify that baselined statistics are to be shown.
Field descriptions
- This command displays both DTE and DCE fields for NNI.
- For the DTE:
  - Enquiries sent—Total number of LMI status enquiries sent by the DTE on this interface
  - Full enquiries sent—Total number of LMI full-status enquiries 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 LMI asynchronous 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
- For the DCE:
  - Enquiries received—Total number of LMI status enquiries 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 asynchronous 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

host1#show frame-relay lmi
LMI information for frame relay NNI interface 3/2:1/1
DTE Parameter N391 is 6, N392 is 3, N393 is 4, T391 is 10
DCE Parameter N392 is 2, N393 is 2, T392 is 15
Configured LMI type is ANSI, status is up
Time since last status change 01:21:14
  Enquiries received: 1232
  Full enquiries received: 207
  Enquiry responses sent: 1232
  Full enquiry responses sent: 207
  Async updates sent: 0
  Unknown messages received: 0
  Loss of sequencing detected: 2
  No response timeouts: 0
  Last sequence number sent: 0
  Last sequence number received: 0
  Unknown messages received: 0
  Loss of sequencing detected: 2
LMI information for frame relay DCE interface 3/2:2/1
Parameter N392 is 2, N393 is 2, T392 is 15
Configured LMI type is ANSI, status is up
Time since last status change 03:06:22
  Enquiries received: 1233
  Full enquiries received: 207
  Enquiry responses sent: 1233
  Full enquiry responses sent: 207
  Async updates sent: 0
  Last sequence number sent: 0
  Last sequence number received: 0

See show frame-relay lmi.

show frame-relay map

Use to display the current Frame Relay map entries and information about Frame Relay connections.
Field descriptions
- Frame relay sub-interface—Interface number and 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—Provides decimal value, hexadecimal value, and its value as it appears on the wire

Example

host1#show frame-relay map
Frame relay sub-interface 3/2:1/1.1 (up): DLCI 101(0x65,0x58)
Frame relay sub-interface 3/2:1/1.2 (up): DLCI 102(0x66,0x78)
Frame relay sub-interface 3/2:1/1.3 (up): DLCI 103(0x67,0x78)
Frame relay sub-interface 3/2:1/1.4 (up): DLCI 104(0x68,0x98)
Frame relay sub-interface 3/2:1/1.5 (up): DLCI 105(0x69,0x98)
Frame relay sub-interface 3/2:1/1.6 (up): DLCI 106(0x6a,0xb8)
Frame relay sub-interface 3/2:1/1.7 (up): DLCI 107(0x6b,0xb8)
Frame relay sub-interface 3/2:1/1.8 (up): DLCI 108(0x6c,0xd8)
Frame relay sub-interface 3/2:1/1.9 (up): DLCI 109(0x6d,0xd8)
Frame relay sub-interface 3/2:1/1.10 (up): DLCI 110(0x6e,0xf8)
Frame relay sub-interface 3/2:1/1.11 (up): DLCI 111(0x6f,0xf8)
Frame relay sub-interface 3/2:1/1.12 (up): DLCI 112(0x70,0x1c)
Frame relay sub-interface 3/2:1/1.17 (up): DLCI 117(0x75,0x5c)
Frame relay sub-interface 3/2:1/1.18 (up): DLCI 118(0x76,0x7c)
Frame relay sub-interface 3/2:1/1.19 (up): DLCI 119(0x77,0x7c)
Frame relay sub-interface 3/2:1/1.20 (up): DLCI 120(0x78,0x9c)
Frame relay sub-interface 3/2:1/1.21 (up): DLCI 121(0x79,0x9c)
Frame relay sub-interface 3/2:1/1.22 (up): DLCI 122(0x7a,0xbc)
Frame relay sub-interface 3/2:1/1.23 (up): DLCI 123(0x7b,0xbc)
Frame relay sub-interface 3/2:1/1.24 (up): DLCI 124(0x7c,0xdc)

See show frame-relay map.

show frame-relay pvc

Use to display statistics about PVCs for Frame Relay layer on a multilink Frame Relay, POS, serial, or GRE tunnel interface or a specific PVC.
Optionally, you can specify an interface using the interface type and specifier. For more information, see Interface Types and Specifiers in JUNOSe Command Reference Guide.
Specify a virtual circuit using the DLCI number.
Use the brief keyword to display abbreviated PVC information.
Use the optional delta keyword to specify that baselined statistics are to be shown.
Field descriptions
- DLCI—DLCI number
- interface—Identifies an interface in slot/port:channel/subchannel format or a subinterface in slot/port:channel/subchannel.subinterface format
- PVC status—Status of the circuit; valid states are active and inactive.
- 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 congestions may be experienced by data traffic 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 congestions may be experienced by data traffic 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

host1#show frame-relay pvc
PVC information for frame relay NNI interface 3/2:1/1
 
DLCI 101 in sub-interface 3/2:1/1.1, status is active
Number of circuit status inactive transitions is 0
Time since creation 03:27:29, last status change 01:21:29
  In pkts: 0                Out pkts: 0
  In bytes: 0               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: 0
DLCI 102 in sub-interface 3/2:1/1.2, status is active
Number of circuit status inactive transitions is 0
Time since creation 03:27:28, last status change 01:21:29
  In pkts: 0                Out pkts: 0
  In bytes: 0               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: 0
DLCI 103 in sub-interface 3/2:1/1.3, status is active
Number of circuit status inactive transitions is 0
Time since creation 03:27:28, last status change 01:21:29
  In pkts: 0                Out pkts: 0
  In bytes: 0               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: 0

See show frame-relay pvc.

show frame-relay subinterface

Use to display the state of the Frame Relay 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 optional delta keyword to specify that baselined statistics are to be shown.
The brief keyword displays only the operational status of all configured subinterfaces.
Field descriptions
- sub-interface—Identifies the subinterface in slot/port:channel/subchannel.subinterface format
- status—Status of the subinterface
- Description—Text description or alias if configured for the subinterface
- 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

host1#show frame-relay subinterface
Frame relay sub-interface 3/2:1/1.1, status is up
Description: toronto011
Time since last status change 01:21:26
  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

Frame relay sub-interface 3/2:1/1.2, status is up
Description: ottawa012
Time since last status change 01:21:26
  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
Frame relay sub-interface 3/2:1/1.3, status is up
Description: montreal013
Time since last status change 01:21:26
  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

See show frame-relay subinterface.

show frame-relay summary

Use to scan all defined Frame Relay interfaces and circuits; reports aggregate status as one of the following:
- 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
28 interface(s) defined, 28 up, 0 down
840 sub-interface(s) defined, 840 up, 0 down
840 circuit(s) defined, 840 up, 0 down

See show frame-relay summary.

[Contents] [Prev] [Next] [Index] [Report an Error]