|
COMMAND DESCRIPTION 19/190 82-CRA 119 1170/1-V1 Uen C | |
Copyright
© Ericsson AB 2009–2010. All rights reserved. No part of this document may be reproduced in any form without the written permission of the copyright owner.
Disclaimer
The contents of this document are subject to revision without notice due to continued progress in methodology, design and manufacturing. Ericsson shall have no liability for any error or damage of any kind resulting from the use of this document.
Trademark List
| SmartEdge | is a registered trademark of Telefonaktiebolaget LM Ericsson. | |
| NetOp | is a trademark of Telefonaktiebolaget LM Ericsson. |
Commands starting with “show d” through commands starting with “show f” are included.
show debug circuit
Displays a list of circuits for which the generation of debug messages has been enabled.
All modes
This command has no keywords or arguments.
None
Use the show debug circuit command to display a list of circuits for which the generation of debug messages has been enabled. The circuits are listed in the order in which the debug circuit commands (in exec mode) were entered.
The following example shows how to enable the generation of debug messages for the following circuits.
It then displays the list of circuits that have the generation of debug messages enabled:
[local]Redback#debug circuit 14/3 vlan-id 1:100 [local]Redback#debug circuit 2/1:1 [local]Redback#show debug circuit Circuit debugging: 14/3:1023:63/1/2/160 2/1:1:63/15/3/16777215
show debugging
Displays the debugging options that are currently enabled.
All modes
This command has no keywords or arguments.
None
Use the show debugging command to display the debugging options that are currently enabled.
The following example displays output from the show debugging command for the debugging options that have been enabled:
[local]Redback>show debugging
ARP:Redback All debugging bits are turned on RPL : ipv6 access-list debugging is turned on
show destination card ip-addr
Displays the chassis slot number of the active line card to which outbound packets with the specified IP address are dispatched for Forwarding Information Base (FIB) lookup.
All modes
|
ip-addr |
IP address of the traffic destination. |
This command has no default.
Use the show destination card command to display the chassis slot number of the active line card to which outbound packets with the specified IP address are dispatched for FIB lookup.
To reduce the size of the FIB table in the active controller card, all outbound traffic packets that are not to be transmitted on the Ethernet management port (on the active controller card) are off-loaded to the active line cards in the SmartEdge® router for FIB lookup. A destination card is not configurable; instead, the controller card load balances the work by selecting a destination card based on the destination IP address in a packet.
The line card selected by the active controller performs the FIB lookup to locate the line card that actually transmits the packet and then dispatches the packet to that line card for output processing. If insufficient information exists to select a destination card for an IP packet (for example, Intermediate System-to-Intermediate System [IS-IS] or Open Shortest Path First [OSPF] control packets sent directly on to a Generic Routing Encapsulation [GRE] tunnel), the packet is sent to the default line card. To determine the default line card, enter the show chassis command (in any mode). The default line card displays a “D” in the “Flags” field.
The following example shows how to display the destination line card for the IP address, 10.13.49.165:
[local]Redback>show destination card 10.13.49.165
Destination address 10.13.49.165 will be dispatched to slot 10. (2nd active card from left, out of a total 2 active cards.
If the destination address, 10.13.49.165, is not resolved to the Ethernet management port, all packets with that IP address are dispatched to the active line card in slot 10 for FIB lookup.
show dhcp relay hosts [{duplicate-mac | ip-addr | mac-addr}] [detail]
Displays Dynamic Configuration Host Protocol (DHCP) relay hosts.
All modes
|
duplicate-mac |
Optional. Displays information for all DHCP relay hosts with duplicate medium access control (MAC) addresses for the current context. |
|
ip-addr |
Optional. Displays the IP address (in the form A.B.C.D) of the DHCP relay host. |
|
mac-addr |
Optional. Displays the medium access control (MAC) address (in the form hh:hh:hh:hh:hh:hh) of the DHCP relay host. |
|
detail |
Optional. Displays more detailed information about the DHCP relay hosts. |
None
Use the show dhcp relay hosts command to display DHCP relay hosts.
Use the ip-addr or mac-addr argument to display information only for a specific DHCP relay host. Use the duplicate-mac keyword to display information for all DHCP relay hosts with duplicate MAC addresses for the current context.
DHCP, in both proxy and relay modes, maintains host entries only for multibind interfaces, and this command displays information only for those entries.
The following example shows how to display DHCP relay host information:
[local]Redback>show dhcp relay hosts Circuit Host Address Hardware Address Lease Timestamp DHCP_Context 4/10 vlan-id 2 120.2.0.241 00:01:02:03:01:02 86400 Wed Nov 7 22:21:11 2005 Proxy local 4/10 vlan-id 7 120.2.199.114 00:01:02:03:01:07 86400 Wed Nov 7 22:19:55 2005 Proxy local 4/10 vlan-id 9 120.2.199.121 00:01:02:03:01:09 86400 Wed Nov 7 22:21:03 2005 Proxy local
The following example shows how to display all the DHCP relay hosts that have duplicate MAC addresses:
[local]Redback#show dhcp relay hosts duplicate-mac Circuit Host Hardware address Lease Ttl Timestamp Type Context 10/4 vlan-id 2 clips 131135 15.1.1.200 00:aa:aa:aa:00:01 72000 71695 Wed Aug 29 10:13:39 2007 Relay local 10/4 vlan-id 4 clips 131125 17.1.1.200 00:aa:aa:aa:00:01 72000 71695 Wed Aug 29 10:13:44 2007 Relay local 10/4 vlan-id 2 clips 131128 15.1.1.100 00:aa:aa:aa:00:02 72000 71695 Wed Aug 29 10:14:29 2007 Relay local 10/4 vlan-id 4 clips 131116 17.1.1.199 00:aa:aa:aa:00:02 72000 71695 Wed Aug 29 10:14:21 2007 Relay local 10/4 vlan-id 2 clips 131126 15.1.1.198 00:aa:aa:aa:00:03 72000 71695 Wed Aug 29 10:14:16 2007 Relay local 10/4 vlan-id 4 clips 131117 17.1.1.196 00:aa:aa:aa:00:03 72000 71695 Wed Aug 29 10:13:45 2007 Relay local 10/4 vlan-id 2 clips 131127 15.1.1.197 00:aa:aa:aa:00:04 72000 71695 Wed Aug 29 10:14:02 2007 Relay local
The following example shows how to display information for the DHCP relay host that has the IP address of 200.100.1.3:
[local]Redback>show dhcp relay hosts 200.100.1.3
--------------------------------------------------------------------- Displaying information for host: 200.100.1.3 MAC Address : 02:dd:00:00:00:26 Circuit : 12/5 vlan-id 101 Context : sj8 Circuit Handle : 12/5:1023:63/1/2/8194 Create time : Tue Dec 2 14:50:30 2008 Type : Server Server : 200.100.1.1 Lease : 900 Ttl : 892 giaddr : 0.0.0.0 flags : 0x411805 helper flags : 0xa Standby helper flags: 0x2 Act. File Page # : 0 Act. File Page Elem : 0 Sby. File Page # : 1148 Sby. File Page Elem : 0 Agent-Circuit-id : 0x0a0b0c0d0e Agent-Remote-id : defghijklm
show dhcp relay server [detail]
Displays information about the Dynamic Host Configuration Protocol (DHCP) relay server.
All modes
|
detail |
Optional. Displays more detailed information about the DHCP relay servers. |
None
Use the show dhcp relay server command to display information about the DHCP relay server.
The following example shows how to display DHCP relay server information:
[local]Redback>show dhcp relay server Server Name/IP Address MinWait MaxHops Group 10.2.1.1 0 4 default
The following example shows how to display detailed DHCP relay server information:
[local]Redback>show dhcp relay server detail DHCP Relay server : 10.2.1.1 Minimum wait : 0 Maximum hops : 4 Server Group grid : 0x1 Server group : default Server is available : Yes Route to the server available : Yes Source ipaddress for server bound pkts : 10.2.1.2 Dhcp relay option (82) enabled : FALSE Stats----------------------------------------------------------------- Discover Tx : 5367 Request Tx : 5063 Release Tx : 5000 Decline Tx : 0 Offer Rx : 5277 Ack Rx : 5000 Nack Rx : 0 No. of leases : 5000
show dhcp relay stats
Displays Dynamic Host Configuration Protocol (DHCP) relay statistics.
All modes
This command has no keywords or arguments.
None
Use the show dhcp relay stats command to display DHCP relay statistics.
The following example displays output from the show dhcp relay stats command:
[local]Redback>show dhcp relay stats Packets Received : 96 Packets Relayed : 86 DHCP Discover : 20 DHCP Offer : 20 DHCP Request : 26 DHCP Decline : 0 DHCP Ack : 20 DHCP Nack : 0 BOOTP Request : 0 BOOTP Reply : 0 Bad Length : 0 Bad Circuit : 4 Bad Context : 0 Bad Server IP : 0 No Server : 0 No Interface : 0 Unbound Circuit : 0 Disabled Interface : 0 Min Wait Error : 0 Max Hops Error : 0 Bad IP : 0 Unknown Packet Type : 0 TX Error : 0 Unmatched MAC : 0 Send Client Error : 0 Send Client Retries : 0 Offer pkt: count : 40 Offer pkt: refresh : 0 ARP Table Error : 0 Input pack Q full (packet drops):: 0 Input pack Q mem error:: 0 Input pack Q (enqueued) count:: 92 Input pack Q (dequeued) count:: 92
show dhcp relay summary
Displays a summary of Dynamic Configuration Host Protocol (DHCP) relay host information.
All modes
This command has no keywords or arguments.
None
Use the show dhcp relay summary command to display a summary of DHCP relay host information.
The following example shows how to display a summary of DHCP relay host information. The Host count column lists the number of hosts in the current context, while the Total Host count column lists the number of hosts in the system:
[local]Redback>show dhcp relay summary Host count : 26 Total Host count : 2626
show dhcp server {lease | host} [{count | duplicate-mac | ip-address ip-addr | mac-address mac-addr | {subnet subnet-ip-addr/prefix-length | netmask} [count] | time-remaining {at-least | at-most} time-remaining [count]}]
Displays information about the hosts or leases for the internal Dynamic Host Configuration Protocol (DHCP) server.
All modes
|
leases |
Displays all information about one or more DHCP leases. |
|
hosts |
Displays all information about one or more DHCP hosts. |
|
count |
Optional. Displays the number of leases or hosts, the number of submits, or the number of leases or hosts for the time remaining. |
|
duplicate-mac |
Optional. Displays leases or hosts with duplicate medium access control (MAC) addresses in the current context. |
|
ip-address ip-addr |
Optional. IP address for a DHCP host or lease. |
|
mac-address mac-addr |
Optional. MAC address for the DHCP host or lease. |
|
subnet subnet-ip-addr |
Optional. IP address for the subnet for a DHCP lease or host. |
|
prefix-length |
Prefix length for the associated subnet; the range of values is 0 to 32. |
|
netmask |
Network mask for the associated subnet; the range of values is 255.255.0.0 to 255.255.255.255. |
|
time-remaining |
Optional. Displays the time remaining for one or more DHCP leases or hosts. |
|
at-least |
Displays DHCP leases or hosts with a time remaining equal to or greater than the value of the time-remaining argument. |
|
at-most |
Displays DHCP leases or hosts with a time remaining equal to or less than the value of the time-remaining argument. |
|
time-remaining |
Number of seconds remaining for a DHCP lease or host; the range of values is 0 to 4,294,967,295. |
When entered without any optional syntax, the show dhcp server command displays all information about all hosts or leases for the internal DHCP server.
Use the show dhcp server command to display information about the hosts or leases for the internal DHCP server.
The following example shows how to display the DHCP lease information:
[local]Redback>show dhcp server leases Circuit Host Hardware address Lease Ttl Timestamp Type Context 2/1 100.100.10.202 00:dd:00:00:00:01 1600 1491 Fri Feb 3 22:09:48 2006 Server dhcpserver 2/1 100.100.10.205 00:dd:00:00:00:04 1600 1492 Fri Feb 3 22:09:49 2006 Server dhcpserver 2/1 100.100.10.204 00:dd:00:00:00:03 1600 1492 Fri Feb 3 22:09:49 2006 Server dhcpserver
The following example shows how to display the number of DHCP hosts:
[local]Redback>show dhcp server hosts count Number of leases is 100
The following example shows how to display the number of hosts with at least 360 seconds remaining on their leases:
[local]Redback>show dhcp server hosts time-remaining at-least 360 count Number of leases is 100
show dhcp server file {context [{name ctx-name | start name ctx-name}] | header | session [{mac-addr | start mac-addr}]}
Displays file information for a Dynamic Host Configuration Protocol (DHCP) server.
All modes
|
context |
Display context information. |
|
name ctx-name |
Name of a context that is configured for a DHCP server. |
|
start |
Display context or session information starting with the specified context or medium access control (MAC) address. |
|
header |
Display header information. |
|
mac-addr |
MAC address for which session information is to be displayed. |
|
session |
Display session information. |
None
Use the show dhcp server file command to display file information for a DHCP server.
The following example shows how to display DHCP file header information:
[local]Redback>show dhcp server file header Magic: SaVe Version: 10 Type: 1 Valid: Yes
show dhcp server option-82 circuit-id [string]
Displays the maximum number of IP addresses allowed and the number of IP addresses currently assigned to one or more agent circuit IDs.
All modes
|
circuit-id |
Displays agent circuit ID information. |
|
string |
Optional. Agent circuit ID for which IP address information is to be displayed. |
None
Use the show dhcp server option-82 command to display the maximum number of IP addresses allowed and the number of IP addresses currently assigned to one or more agent circuit IDs.
The following example shows how to display all agent circuit IDs:
[local]Redback>show dhcp server option-82 circuit-id Agent-circuit-id Max IP IP assigned ---------------------------------------------------- slot8-port0-channel0 10 5
show dhcp server range [if-name]
Displays range usage information for one or more interfaces configured for a Dynamic Host Configuration Protocol (DHCP) server.
All modes
|
if-name |
Optional. Name of an interface that is configured for a DHCP server. |
When entered without any optional syntax, the show dhcp server range command displays range usage information for all interfaces configured for a DHCP server.
Use the show dhcp server range command to display range usage information for one or more interfaces configured for a DHCP server.
The following example displays range information for the to-client interface:
[local]Redback>show dhcp server range to-client Interface "to-client": 10.1.0.1 10.1.255.254 0 in use, 65533 free,1 reserved
show dhcp server stats [{circuit slot/port circuit-id [pending mac-addr] | context ctx-name interface if-name [pending mac-addr]}]
Displays Dynamic Host Configuration Protocol (DHCP) process statistics.
All modes
|
circuit slot/port |
Slot and port numbers for the line card that holds the circuit to be displayed. |
|
circuit-id |
Circuit identifier, according to one of the constructs listed in Table 1. |
|
pending mac-addr |
Optional. DHCP host entry for the specified medium access control (MAC) address. |
|
context ctx-name |
Context for which DHCP statistics are displayed. |
|
interface if-name |
Interface in the specified context for which DHCP statistics are displayed. |
When entered without any optional syntax, the show dhcp server stats command displays DHCP process statistics.
Use the show dhcp server stats command to display DHCP process statistics. Table 1 lists the values for the circuit-id argument.
|
Construct |
Description |
|---|---|
|
clips |
Clientless IP service selection (CLIPS) circuit. |
|
dlci dlci |
Data-link connection identifier (DLCI) for a Frame Relay permanent virtual circuit (PVC). The range of values is 16 to 991. |
|
vlan-id vlan-id |
Virtual LAN (VLAN) tag value for an 802.1Q tunnel or PVC. The vlan-id argument is one of the following constructs:
The range of values for either VLAN tag value is 1 to 4,095. |
|
vpi-vci vpi vci |
Virtual path identifier (VPI) and virtual circuit identifier (VCI) for an Asynchronous Transfer Mode (ATM) PVC. The range of values is 0 to 255 and 1 to 65,535, respectively. |
The following example shows how to display DHCP statistics for the specified circuit:
[local]Redback>show dhcp server stats circuit 11/4 vlan-id 10 Current time: Fri Aug 4 17:49:44 2006 Last cleared: Never Internal Circuit Handle: 11/5:1023:63/1/2/10 Discovers Received : 0 Requests Received : 0 Releases Received : 0 Declines Received : 0 Renewal REQs Received : 0 Offers Sent : 0 ACKs Sent : 0 Renewal ACKs Sent : 0
The following example shows how to display DHCP statistics for the specified interface:
[local]Redback#show dhcp server stats context c1 interface i1 Current time: Fri Aug 4 17:49:46 2006 Last cleared: Never Discovers Received : 0 Requests Received : 0 Release Received : 0 Decline Received : 0 Renewal REQs Received : 0 Offers Sent : 0 ACKs Sent : 0 Renewal ACKs Sent : 0
show dhcp server threshold {context | range}
Displays Dynamic Host Configuration Protocol (DHCP) threshold configuration and status information.
All modes
|
context |
Displays threshold configuration and status for the current context at the context level. |
|
range |
Displays threshold configuration for all ranges in the current context. |
None
Use the show dhcp server threshold command to display DHCP threshold configuration and status information.
The following example shows how to display the threshold configuration for all ranges in the current context:
[local]Redback>show dhcp server threshold range Interface "subs": 100.100.10.2 100.100.10.254 threshold falling 10 log
show dhcpv6 log [circuit slot/port:ch:sub | duid hex-string | prefix ipv6-prefix/length]
Displays the DHCPv6-PD log history.
All modes
|
circuit slot/port:ch:sub |
Optional. Filters log messages by circuit. The slot/port:ch:sub argument is the slot and port, channel, and subchannel numbers for a circuit. |
|
duid hex-string |
Optional. Filters log messages by DHCPv6 server DUID; hex-string is a colon-delimited hexadecimal number. |
|
prefix ipv6-prefix/length |
Optional. Filters log messages by IPv6 prefixes; the ipv6-prefix/length argument specifies an IPv6 prefix and length in the format A:B:C:D::E/length; the length can be from 0 to 128. |
None
To display the DHCPv6 logs, enter the show dhcpv6 log command.
You can filter the output by circuit, DUID, or IPv6 prefix.
To determine the DUID for a DHCPv6 server, see show dhcpv6 server.
The following example shows sample output with no filtering:
[local]Redback#show dhcpv6 log
Time Evnt SubEvent Key (ccth|ipv6addr|etc) Details
------ ---- ---------------- ------------------------- -------
506.17 Proc Create-thread helper
582.32 Hlpr Do-Upload
582.34 Hlpr Upload
582.36 Proc Create-thread cmd
582.38 Proc Create-thread be
582.40 Proc Endpoint-alive rcm
582.41 Hlpr Ctx-Add
582.43 Hlpr Ctx-Add
582.44 Hlpr Ctx-Add
582.44 RCM R:EOF
582.50 Proc Create-thread ism
582.58 Proc Endpoint-alive ism_mbe
582.58 ISM FSM-Event MBE-EP-Up
582.58 ISM FSM-New-State MBE-EP-up (All-EP-down)
582.58 Proc Endpoint-alive ism
582.58 ISM FSM-Event Client-EP-Up
582.58 ISM S:reg-clnt
582.58 ISM S:reg-mbe
582.59 ISM FSM-New-State Await-EOF (MBE-EP-up)
582.82 ISM R:Cct-State 1/1:1023:63/1/1/11 CCT create
582.82 ISM R:Cct-Cfg 1/1:1023:63/1/1/11 CCT ethcfg
582.82 ISM R:Cct-State 1/1:1023:63/1/1/11 CCT up
582.82 ISM R:Cct-State 7/1:1023:63/1/1/13 CCT create
582.82 ISM R:Cct-Cfg 7/1:1023:63/1/1/13 CCT ethcfg
582.82 ISM R:Cct-State 7/1:1023:63/1/1/13 CCT up
582.82 ISM R:Cct-State 255/6:5:18/1/1/4 CCT create
582.82 ISM R:Cct-Cfg 255/6:5:18/1/1/4 CCT ethcfg
582.82 ISM R:Cct-State 255/6:5:18/1/1/4 CCT down
582.82 ISM R:Cct-State 255/6:5:19/1/1/6 CCT create
582.82 ISM R:Cct-Cfg 255/6:5:19/1/1/6 CCT ethcfg
582.82 ISM R:Cct-State 255/6:5:19/1/1/6 CCT down
582.82 ISM R:Cct-State 255/6:5:20/1/1/7 CCT create
582.82 ISM R:Cct-Cfg 255/6:5:20/1/1/7 CCT ethcfg
582.82 ISM R:Cct-State 255/6:5:20/1/1/7 CCT down
582.82 ISM R:Cct-State 255/11:5:18/1/2/5 CCT create
582.82 ISM R:Cct-Cfg 255/11:5:18/1/2/5 CCT 1qcfg
582.82 ISM R:Cct-State 255/11:5:18/1/2/5 CCT down
582.82 ISM R:Cct-State 255/11:5:20/1/2/8 CCT create
582.82 ISM R:Cct-Cfg 255/11:5:20/1/2/8 CCT 1qcfg
582.82 ISM R:Cct-State 255/11:5:20/1/2/8 CCT down
582.82 ISM R:Cct-State 255/22:1:26/1/1/2 CCT create
582.82 ISM R:Cct-Cfg 255/22:1:26/1/1/2 CCT ethcfg
582.82 ISM R:Cct-State 255/22:1:26/1/1/2 CCT down
582.82 ISM R:Cct-State 255/22:1:27/1/1/3 CCT create
582.82 ISM R:Cct-Cfg 255/22:1:27/1/1/3 CCT ethcfg
582.82 ISM R:Cct-State 255/22:1:27/1/1/3 CCT down
582.82 ISM R:If-State I/F create
582.82 ISM R:If-Cfg I/F cfg
582.82 ISM R:If-Ipv6Cfg I/F ipcfg
582.82 ISM R:If-State I/F down
582.82 ISM R:If-State I/F create
582.82 ISM R:If-Cfg I/F cfg
582.82 ISM R:If-Ipv6Cfg I/F ipcfg
582.82 ISM R:If-State I/F down
582.82 ISM R:If-State I/F create
582.82 ISM R:If-Cfg I/F cfg
582.82 ISM R:If-Ipv6Cfg I/F ipcfg
582.82 ISM R:If-State I/F down
582.82 ISM R:EOF
582.82 ISM R:Mbe-All-EOF
582.82 ISM FSM-Event EOF
582.82 ISM FSM-New-State All-EP-up (Await-EOF)
582.82 ISM FSM-Event MBE-All-EOF
582.91 Proc Create-thread pkt-rx
582.93 Proc Create-thread pkt-process
582.95 Proc Create-thread timer
582.97 ISM S:EOF
582.97 Proc Ready
054.02 ISM R:Cct-State 1/1:1023:63/6/2/1 CCT create
054.02 ISM R:Cct-Cfg 1/1:1023:63/6/2/1 CCT ethcfg
054.02 ISM R:Cct-State 1/1:1023:63/6/2/1 CCT up
054.13 ISM R:Cct-State 1/1:1023:63/6/2/2 CCT create
054.13 ISM R:Cct-Cfg 1/1:1023:63/6/2/2 CCT ethcfg
054.13 ISM R:Cct-State 1/1:1023:63/6/2/2 CCT up
054.19 ISM R:Cct-Cfg 1/1:1023:63/6/2/1 CCT ethcfg
054.22 ISM R:Cct-Cfg 1/1:1023:63/6/2/2 CCT ethcfg
054.58 ISM R:Cct-Cfg 1/1:1023:63/6/2/1 CCT ethcfg
054.59 ISM R:Cct-Cfg 1/1:1023:63/6/2/2 CCT ethcfg
054.77 ISM R:Cct-Cfg 1/1:1023:63/1/1/11 CCT ethcfg
054.77 ISM R:Cct-Cfg 1/1:1023:63/6/2/1 CCT ethcfg
054.85 ISM R:Cct-Cfg 1/1:1023:63/6/2/2 CCT ethcfg
054.85 ISM R:If-Cfg I/F cfg
054.85 ISM R:If-State I/F bind
054.85 ISM R:If-State I/F bind
054.85 ISM R:If-Ipv6Cfg I/F ipcfg
054.85 ISM R:If-State I/F up
054.90 Pkt Pkt from Client 1/1:1023:63/6/2/1 Solicit
(cont'd) fe80::54c2:26b0:3dba:4fda
(cont'd) 00:03:00:01:00:00:64:01:01:02
054.92 Pkt Pkt to Client 1/1:1023:63/6/2/1 Advertise
(cont'd) fe80::230:88ff:fe00:1cf7
(cont'd) 00:03:00:01:00:00:64:01:01:02
054.92 Pkt Pkt from Client 1/1:1023:63/6/2/2 Solicit
(cont'd) fe80::25bb:5e6a:1332:a330
(cont'd) 00:03:00:01:00:00:64:01:01:03
054.92 Pkt Pkt to Client 1/1:1023:63/6/2/2 Advertise
(cont'd) fe80::230:88ff:fe00:1cf7
(cont'd) 00:03:00:01:00:00:64:01:01:03
054.92 Pkt Pkt from Client 1/1:1023:63/6/2/1 Request
(cont'd) fe80::54c2:26b0:3dba:4fda
(cont'd) 00:03:00:01:00:00:64:01:01:02
054.92 Int IPv6 Add 1/1:1023:63/6/2/1
(cont'd) 2001:a:1:1::/64
(cont'd) 00:03:00:01:00:00:64:01:01:02
054.92 Int Route Add 1/1:1023:63/6/2/1
(cont'd) 2001:a:1:1::/64
(cont'd) 00:03:00:01:00:00:64:01:01:02
054.93 Tmr Timer Start 1/1:1023:63/6/2/1
(cont'd) 00:03:00:01:00:00:64:01:01:02
054.93 Hlpr Add 1/1:1023:63/6/2/1
(cont'd) 00:03:00:01:00:00:64:01:01:02
054.93 Int Bind Add 1/1:1023:63/6/2/1
(cont'd) 00:03:00:01:00:00:64:01:01:02
054.93 Pkt Pkt to Client 1/1:1023:63/6/2/1 Reply
(cont'd) fe80::230:88ff:fe00:1cf7
(cont'd) 00:03:00:01:00:00:64:01:01:02
054.93 Pkt Pkt from Client 1/1:1023:63/6/2/2 Request
(cont'd) fe80::25bb:5e6a:1332:a330
(cont'd) 00:03:00:01:00:00:64:01:01:03
054.93 Int IPv6 Add 1/1:1023:63/6/2/2
(cont'd) 2001:b:1:2::/64
(cont'd) 00:03:00:01:00:00:64:01:01:03
054.93 Int Route Add 1/1:1023:63/6/2/2
(cont'd) 2001:b:1:2::/64
(cont'd) 00:03:00:01:00:00:64:01:01:03
054.93 Tmr Timer Start 1/1:1023:63/6/2/2
(cont'd) 00:03:00:01:00:00:64:01:01:03
054.93 Hlpr Add 1/1:1023:63/6/2/2
(cont'd) 00:03:00:01:00:00:64:01:01:03
054.93 Int Bind Add 1/1:1023:63/6/2/2
(cont'd) 00:03:00:01:00:00:64:01:01:03
054.93 Pkt Pkt to Client 1/1:1023:63/6/2/2 Reply
(cont'd) fe80::230:88ff:fe00:1cf7
(cont'd) 00:03:00:01:00:00:64:01:01:03The following example shows output filtered by the IPv6 prefix 2001:a:1:1::/64
[local]Redback#show dhcpv6 log prefix 2001:a:1:1::/64
Time Evnt SubEvent Key (ccth|ipv6addr|etc) Details
-------------------------- --------------------------------
054.92 Int IPv6 Add 1/1:1023:63/6/2/1
(cont'd) 2001:a:1:1::/64
(cont'd) 00:03:00:01:00:00:64:01:01:02
054.92 Int Route Add 1/1:1023:63/6/2/1
(cont'd) 2001:a:1:1::/64
(cont'd) 00:03:00:01:00:00:64:01:01:02
055.24 Hlpr Add-Resp 2001:a:1:1::/64
(cont'd) 00:03:00:01:00:00:64:01:01:02
055.16 Hlpr Update-Resp 2001:a:1:1::/64
(cont'd) 00:03:00:01:00:00:64:01:01:02
055.11 Hlpr Update-Resp 2001:a:1:1::/64
(cont'd) 00:03:00:01:00:00:64:01:01:02
055.06 Hlpr Update-Resp 2001:a:1:1::/64
(cont'd) 00:03:00:01:00:00:64:01:01:02
055.03 Hlpr Update-Resp 2001:a:1:1::/64
(cont'd) 00:03:00:01:00:00:64:01:01:02
054.99 Hlpr Update-Resp 2001:a:1:1::/64
(cont'd) 00:03:00:01:00:00:64:01:01:02
054.95 Hlpr Update-Resp 2001:a:1:1::/64
(cont'd) 00:03:00:01:00:00:64:01:01:02
054.90 Hlpr Update-Resp 2001:a:1:1::/64
(cont'd) 00:03:00:01:00:00:64:01:01:02show dhcpv6 server duid
Displays the DUID that the SmartEdge OS DHCPv6-PD Server is using as its identifier when communicating with clients.
All modes
This command has no keywords or arguments.
None
Use the show dhcpv6 server duid command to look up the DUID for a DHCPv6-PD server.
[local]Redback#show dhcpv6 server duid Dhcpv6 Server DUID: 00:01:00:01:12:fc:7f:6e:00:30:88:00:1c:f7
show dhcpv6 server host [circuit slot/port:ch:sub | duid hex-string | prefix host-prefix | subnet prefix/length] [detail | summary]
Display information about DHCPv6-PD server hosts.
All modes
|
circuitslot/port:ch:sub |
Optional. Show information for the host with the specified circuit. The slot/port:ch:sub argument is the slot and port, channel, and subchannel numbers for a circuit. |
|
duid hex-string |
Optional. Show information for the host or client with the specified DUID. |
|
prefix host-prefix/length |
Optional. Display information about a host with the specified prefix (per context) (an exact match). The IPv6 prefix and length are in the format A:B:C:D::E/length; the length can be from 0 to 128. |
|
subnet prefix/length |
Optional. Display information about the hosts on the specified subnet (per context); matches any prefix whose address part matches the address part of the subnet. The IPv6 prefix and length are in the format A:B:C:D::E/length; the length can be from 0 to 128. |
|
detail |
Optional. Display detailed information. |
|
summary |
Optional. Summary information is displayed. |
None
Use the show dhcpv6 server host command to view information about DHCPv6-PD server hosts. You can filter the output with one of the optional circuit, host or client DUID, IPv6 prefix or subnet constructs. You can add the mutually exclusive detail or summary keywords after the filtering constructs.
To determine the DUID to use for a DHCPv6-PD server in the current context, use the show dhcpv6 server duid command. You can also determine the DUIDs for hosts with specified prefixes or subnets using the show dhcpv6 server host command with the prefix or subnet keyword, which are context specific.
To show information for a context other than the current one, enter the context ctx-name construct before the command.
The following example shows how to display detailed information for the active DHCPv6-PD server hosts:
[local]Redback#show dhcpv6 server host detail
DHCPv6 Server Host Record:
------------------------------------
DUID: 00:03:00:01:00:00:64:01:01:02
IA Type: PD, IA ID: 0, T1: 3600, T2: 5760
Prefix: 2001:a:1:1::/64
preferred lifetime: 7200
valid lifetime: 14400
TTL: 11929
expires at Fri Feb 5 14:10:53 2010
Ifgrid: 0x10000001
Context id: 0x40080001
Cct: 1/1:1023:63/6/2/1
Cct flags: 0x0007
DUID: 00:03:00:01:00:00:64:01:01:03
IA Type: PD, IA ID: 0, T1: 3600, T2: 5760
Prefix: 2001:b:1:2::/64
preferred lifetime: 7200
valid lifetime: 14400
TTL: 11929
expires at Fri Feb 5 14:10:53 2010
Ifgrid: 0x10000001
Context id: 0x40080001
Cct: 1/1:1023:63/6/2/2
Cct flags: 0x0007The following example displays the DHCPv6 client on the 1/1 pppoe 1 circuit:
[local]Redback#show dhcpv6 server host circuit 1/1 pppoe 1
DHCPv6 Server Host Record:
--------------------------
DUID: 00:03:00:01:00:00:64:01:01:02
IA Type: PD, IA ID: 0, T1: 3600, T2: 5760
Prefix: 2001:a:1:1::/64
preferred lifetime: 7200
valid lifetime: 14400
TTL: 11646
expires at Fri Feb 5 14:10:53 2010The following example displays output for the DHCPv6 client that has the DUID, 00:03:00:01:00:00:64:01:01:03:
[local]Redback#show dhcpv6 server host duid 00:03:00:01:00:00:64:01:01:03
DHCPv6 Server Host Record:
--------------------------
DUID: 00:03:00:01:00:00:64:01:01:03
IA Type: PD, IA ID: 0, T1: 3600, T2: 5760
Prefix: 2001:b:1:2::/64
preferred lifetime: 7200
valid lifetime: 14400
TTL: 11594
expires at Fri Feb 5 14:10:53 2010The following example displays output for the DHCPv6-PD server hosts on the 2001::/16 subnet in the isp203 context:
[local]Redback#context isp203 show dhcpv6 server subnet 2001::/16
DHCPv6 Server Host Record:
--------------------------
DUID: 00:03:00:01:00:00:64:01:01:02
IA Type: PD, IA ID: 0, T1: 3600, T2: 5760
Prefix: 2001:a:1:1::/64
preferred lifetime: 7200
valid lifetime: 14400
TTL: 11735
expires at Fri Feb 5 14:10:53 2010
DUID: 00:03:00:01:00:00:64:01:01:03
IA Type: PD, IA ID: 0, T1: 3600, T2: 5760
Prefix: 2001:b:1:2::/64
preferred lifetime: 7200
valid lifetime: 14400
TTL: 11735
expires at Fri Feb 5 14:10:53 2010show dhcpv6 statistics [clear] [detail]
Displays and optionally clears DHCPv6-PD statistics.
All modes
|
clear |
Optional. Clears DHCPv6 statistics after producing the output. |
|
detail |
Optional. Displays detailed DHCPv6 statistics. |
None
To view statistics about the DHCPv6-PD server, enter the show dhcpv6 statistics command. Adding the clear keyword has the same effect as running the clear dhcpv6 statistics command after the show command.
The following example shows how to display DHCPv6-PD statistics:
[local]Redback#show dhcpv6 statistics Current time: Tue Mar 23 21:52:31 2010 Last cleared: Never PKT----------------------------------------------------------- Packets Rx : 0 Packets Tx : 0 Solicit : 0 Advertise : 0 Request : 0 Confirm : 0 Renew : 0 Rebind : 0 Reply : 0 Release : 0 Decline : 0 Reconfigure : 0 Relay Fwd : 0 Relay Reply : 0 Info Req : 0 Unknown Pkt : 0 Dropped pkt--------------------------------------------------- Solicit : 0 Advertise : 0 Request : 0 Confirm : 0 Renew : 0 Rebind : 0 Reply : 0 Release : 0 Decline : 0 Reconfigure : 0 Inform Req : 0 Unknown Pkt : 0
The following example shows how to display detailed DHCPv6-PD statistics:
[local]Redback#show dhcpv6 statistics detail Current time: Tue Mar 23 21:55:00 2010 Last cleared: Never PKT----------------------------------------------------------- Packets Rx : 0 Packets Tx : 0 Solicit : 0 Advertise : 0 Request : 0 Confirm : 0 Renew : 0 Rebind : 0 Reply : 0 Release : 0 Decline : 0 Reconfigure : 0 Relay Fwd : 0 Relay Reply : 0 Info Req : 0 Unknown Pkt : 0 Dropped pkt--------------------------------------------------- Solicit : 0 Advertise : 0 Request : 0 Confirm : 0 Renew : 0 Rebind : 0 Reply : 0 Release : 0 Decline : 0 Reconfigure : 0 Inform Req : 0 Unknown Pkt : 0 No I/F Bind : 0 No Prefix : 0 No Cct : 0 No Context : 0 Rx Opt Err : 0 Tx Opt Err : 0 Bad Cct : 0 Bad Slot : 0 Inv Unicast : 0 Slot Throttle : 0 RxMsg Error : 0 Bad Length : 0 Dhelperv6----------------------------------------------------- Birth : 1 Death : 0 IPC In : 3 Msgs In : 3 Add Request : 0 Update Request : 0 Delete Request : 0 Add Response : 0 Update Response : 0 Delete Response : 0 Add Request Fail : 0 Upd Request Fail : 0 Del Request Fail : 0 Upload From Helper : 1 Standby Dhelperv6--------------------------------------------- Standby Birth : 1 Standby Death : 0 Add Request : 0 Update Request : 0 Delete Request : 0 Add Response : 0 Update Response : 0 Delete Response : 0 Add Request Fail : 0 Upd Request fail : 0 Del Request fail : 0 ISM----------------------------------------------------------- Birth : 1 Death : 0 IPC In : 2 Msgs In : 9 ISM Cct Create : 1 ISM Cct Delete : 0 ISM Cct Up : 1 ISM Cct Down : 0 ISM Bind Msg : 0 ISM UnBind Msg : 0 ISM IF Create : 1 ISM IF Delete : 0 ISM IF Up : 0 ISM IF Down : 1 ISM Port Down : 0 ISM Port Delete : 0 Rx EOF : 1 Rx MBE All EOF : 1 Tx EOF : 1 ISM Throttle : 0 Ipv6 Host Add : 0 Ipv6 Host Del : 0 Input pack Q full (packet drops): 0 Input pack Q (enqueued) count: 0 Input pack Q (dequeued) count: 0
For any SmartEdge chassis except the SmartEdge 100 chassis, to display the results of the power-on diagnostic (POD) tests:
show diag pod [backplane [detail] | card slot [detail] | fantray [detail] | detail]
For a SmartEdge 100 chassis, to display the results of the POD tests:
show diag pod [card [detail] | detail]
For any SmartEdge chassis except the SmartEdge 100 chassis, to display the results of the on-demand diagnostic (ODD) tests:
show diag on-demand [card slot [disk disk_num] [detail] | mesh [detail] | standby [detail] | history num-ses [detail] | detail]
For a SmartEdge 100 chassis, to display the results of the ODD tests:
show diag on-demand [card [detail] | history num-ses [detail] | detail]
Displays the results of POD or ODD tests for one or more units.
All modes
|
pod |
Displays results from the POD tests. |
|
on-demand |
Displays results from the ODD tests. |
|
backplane |
Optional. Displays POD results for the backplane in any chassis. |
|
card slot |
Optional. Latest results for the card specified by the slot argument. The range of values for slot is:
|
|
disk disk_num |
Optional. Disk number on the SSE card. Values: 1 or 2. |
|
standby |
Optional. Displays the latest results for the standby controller card. |
|
fantray |
Optional. Displays POD results for the fan tray or the fan and alarm unit in the SmartEdge 800 chassis. |
|
mesh |
Optional. Displays results for packet mesh tests. |
|
detail |
Optional. Displays detailed results. |
|
history num-ses |
Optional. Previous results from the history file for the number of ODD sessions specified by the num-ses argument. The first set of results is for the last initiated session. The range of values is 1 to 100. |
|
pod |
Displays results from the POD tests. |
|
on-demand |
Displays results from the ODD tests. |
|
backplane |
Optional. Displays POD results for the backplane in any chassis. |
|
card slot |
Optional. Latest results for the card specified by the slot argument. The range of values for slot is:
|
|
standby |
Optional. Displays the latest results for the standby controller card. |
|
fantray |
Optional. Displays POD results for the fan tray or the fan and alarm unit in the SmartEdge 800 chassis. |
|
mesh |
Optional. Displays results for packet mesh tests. |
|
detail |
Optional. Displays detailed results. |
|
history num-ses |
Optional. Previous results from the history file for the number of ODD sessions specified by the num-ses argument. The first set of results is for the last initiated session. The range of values is 1 to 100. |
For POD, displays a summary of the results for all units. For ODD, displays summary results for all cards from the last initiated session.
Use the show diag command to display the results of the POD or ODD tests for one or more units.
Results for POD are updated whenever a card is installed in the chassis of a running system, or the system is reloaded using the reload command (in exec mode). Only the latest results are displayed.
The latest results for POD are stored in a log with a buffer for each card. The system also stores the log and maintains a history file on the compact-flash card for low-level software to store results for up to 100 sessions.
For POD, use the detail keyword to determine which tests the unit has failed.
No POD results are reported for unprovisioned cards. You must first provision a card before POD results for it can be reported.
For ODD, use the detail keyword to display all data in the summary, and, for each test that failed, the details about the test failure. This keyword can be combined with any other keyword or argument; if it is the only keyword specified, it displays detailed results from the last session.
For the SmartEdge 100 chassis, use the history keyword to display results of previous ODD sessions; for any other SmartEdge chassis, use the history num-ses construct. The first set of results is for the last initiated session.
For the SmartEdge 100 chassis, use the card keyword to display the log for the carrier card; for any other SmartEdge chassis, use the card slot construct to display the log for any line card.
Table 2 lists the possible summary results for an ODD session.
|
Session Status |
Description |
|---|---|
|
Aborted |
Session was terminated by the user. |
|
Incomplete |
At least one of the requested tests could not be run. |
|
In-Progress |
Session is currently in progress. |
|
n Failures |
Number of test failures that occurred during the session. |
|
Passed |
All tests passed. |
Table 3 lists the descriptions for the test status that can be displayed.
|
Test Status |
Description |
|---|---|
|
Aborted |
Test was started but was terminated before it could be completed. |
|
Failed |
Test ran and failed. |
|
Not Run |
Initial state, test not yet run. |
|
Passed |
Test ran successfully. |
|
Running |
Test is currently in progress. |
|
Skipped |
Test could not be run; for example, part revision is earlier than the required minimum version or no file found. |
In general, if a unit fails to pass a test, you should replace it or make arrangements for its replacement. Contact your local technical support representative for more information about the results of a failed test. For troubleshooting information on uncorrected file system error recovery on an SSE card, see SSE Configuration and Operation.
Example 1
The following command line is used to show the summary results of the POD tests:
[local]Redback#show diag pod
Example 2
The following command line is used to show the detailed results of the POD tests for the card in slot 2:
[local]Redback#show diag pod card 2 detail
Example 3
The following command line is used to show the detailed of the POD results for the card in slot 7:
[local]Redback#show diag pod card 7 detail
Example 4
The following example displays the summary results for the ODD level 2 test on the line card in slot 2:
[local]Redback#show diag on-demand card 2
Example 5
The following example shows the detailed results of the mesh ODD test of a SmartEdge 400 chassis. P indicates a passed condition, F indicates a failed condition, and “-” indicates not applicable. The system keeps track of mesh test failures from previous mesh test runs and displays summary results for all line card slots. The diag on-demand mesh reset command clears this summary information (resets the values to -):
[local]Redback#show diag on-demand mesh detail
Slot Number : 1
Card Type : oc3-8-port
Detected Card Type : oc3-8-port
Serial Number : 8J0O8070200146
Detected Serial Number : 8J0O8070200146
Test Summary : 1 Failure detected
Slot Number : 2
Card Type : ether-12-port
Detected Card Type : ether-12-port
Serial Number : 7U123456789012
Detected Serial Number : 7U123456789012
Test Summary : 1 Failure detected
Slot Number : 3
Card Type : oc48-1-port
Detected Card Type : oc48-1-port
Serial Number : 8L0E6090100666
Detected Serial Number : 8L0E6090100666
Test Summary : Incomplete - 3 tests skipped
Controller Serial Number: 6Y038050200239
Test Level : Mesh
Loop Count : 1
Start Time : 23:25:23 11/09/2002
Completion Time : 23:27:58 11/09/2002
Mesh Test Summary : Passed
Test Results Loop 1:
Tx Pkts Rx Pkts
Slot Sent Slot Recv Status
-----------------------------------
1 37500 2 36498 Failed
Summary Results of Mesh Bus Testing
Tx/Rx 1 2 3 4 XC XC
-----------------------------------
1 - *F* P - - -
2 P - P - - -
3 P P - - - -
4 - - - - - -
XC - - - - - -
XC - - - - - - Example 6
The following example shows how to display the controller card and carrier card results of the on-demand testing of a SmartEdge 100 chassis:
[local]Redback#show diag on-demand Slot Number : 1 Card Type : XCRP Detected Card Type : none Serial Number : A90J5080500069 Detected Serial Number : Controller Serial Number: 8N026090100864 Test Level : 3 Loop Count : 1 Start Time : 21:53:50 05/9/2006 Completion Time : 21:54:37 05/9/2006 Test Summary : Passed Slot Number : 2 Card Type : carrier Detected Card Type : none Serial Number : A80C5040500029 Detected Serial Number : Controller Serial Number: 8N026090100864 Test Level : 3 Loop Count : 1 Start Time : 21:55:31 05/09/2006 Completion Time : 21:57:11 05/09/2006 Test Summary : 1 Failure MIC 1 MIC Type : ge-2-port Detected MIC Type : none Serial Number : A80C5040500029 Detected Serial Number : Controller Serial Number: 8N026090100864 Test Level : 3 Loop Count : 1 Start Time : 21:55:31 05/09/2006 Completion Time : 21:57:11 05/09/2006 Test Summary : 1 Failure MIC 2 MIC Type : ge-2-port Detected MIC Type : none Serial Number : A80C5040500029 Detected Serial Number : Controller Serial Number: 8N026090100864 Test Level : 3 Loop Count : 1 Start Time : 21:55:31 05/09/2006 Completion Time : 21:57:11 05/09/2006 Test Summary : Passed.
show disk [internal | external] [detail]
Displays status for the internal (NetBSD compact-flash card) card, and the external (mass-storage device) card, if installed, and the soft and hard error count, in the external slot of the controller card to which you are connected.
All modes(10)
|
internal |
Optional. Displays status for the root file system on the NetBSD compact-flash card. |
|
external |
Optional. Displays status for the /md file system on the mass-storage device. |
|
detail |
Optional. Displays detailed results. |
Displays status for both the root and /md file systems.
Use the show disk command to display status for the internal (NetBSD compact-flash card) card, and the external (mass-storage device) card, if installed, and the soft and hard error count, in the external slot of the controller card to which you are connected.
Table 4 lists the fields displayed by this command.
|
Field |
Description |
|---|---|
|
Location |
Location of the storage device:
|
|
512-blocks |
Size of the file system in 512-byte blocks:
|
|
Used |
Number of blocks in use |
|
Avail |
Number of blocks available |
|
Capacity |
Percent of blocks used in the file system, calculated using the number of usable blocks (Used + Avail) |
|
Mounted on |
Device on which the file system is mounted:
|
The following notes apply to the data in Table 4:
Table 5 lists the additional fields that are displayed by the show disk command when you include the detail keyword.
|
Field |
Description |
|---|---|
|
Controller Status |
Controller status flags:
|
|
Num attach/detach |
Number of times an external device was inserted or removed |
|
Disk Status |
A—Attached C—Changing the current directory failed (cd command failure) D—Change to file permissions failed E—Installed in external slot F—File system check failed I—Installed in internal slot M—Mounted N—Creation of a new file system failed O—Automatic mount failed R—Reformatting disk S—Failed to attach an external disk as a core dump device T—Unmount command failed U—Automatically mounted |
|
Disk # of event |
Number of times the operating system notified applications that the external device was inserted |
A hard error occurs when the system cannot read the drive information or when an error is not recoverable. Typically, if a hard error occurs, the drive needs to be replaced.
The hard error counter is incremented when one of the following conditions occurs:
The following example displays detailed status for the mass-storage device in the external slot of the active controller card:
[local]Redback>show disk external
Controller Status Flags
Flags: P - device presenct, I - Failed to clear an interrupt,
N - New event not processed
--------------------------------------------------------------
Controller status: P
Num attach/detach: 1/1
Card Status Flags
Flags: A - Attached, M - Mounted
U - Automatically mounted, F - Filesystem check failed
N - Creation of new filesystem failed, O - automatic mount failed,
C - changing the current directory failed, S - Swap failed, T - unmount failed
D - change to file permissions failed
--------------------------------------------------------------
Disk status: AMU
Disk # evnt: 3
Mount Time : Mon Apr 18 10:56:15 2005 PST
Mounted in slot: 6 Status : Operational
Soft Errors : 0 Hard Errors: 0
Location 512-blocks Used Avail Capacity Mounted on
External 1021244 54118 916062 5% /md
The following example displays status for the NetBSD compact-flash card and the mass-storage device on the active controller card:
[local]Redback>show disk
Location 512-blocks Used Avail Capacity Mounted on Internal 985262 309074 626924 33% / External 1021244 45146 925034 4% /md
The following example displays status for the NetBSD compact-flash card and the mass-storage device on the standby controller card:
[local]standby#show disk
Location 512-blocks Used Avail Capacity Mounted on Internal 362526 254592 89806 73% / External 1021244 59426 910754 6% /md
show disk sse slot [disk_num]
All modes
|
slot |
Chassis slot number of the SSE card. |
|
disk_num |
Disk number on the SSE card. Values: 1 or 2. |
Displays SSE disk information for the SSE card.
[local]Redback#show disk sse 2 Slot : 2 State : Up FS Group Name : grp1 Active Alarms : NONE Disk Info : ------------------------------------------------- Disk : 1 State : Up Total Size (GB) : 134.12 Available (GB) : 130.11 Active Alarms : NONE Disk : 2 State : Up Total Size (GB) : 134.00 Available (GB) : 134.00 Active Alarms : NONE # of Partitions : 2 ------------------------------------------------- Name : ptn1 In FS Group : Yes Disk Allocated : 1 Size (GB) : 2.00 Name : ptn2 In FS Group : Yes Disk Allocated : 1 Size (GB) : 2.00
[local]Redback#show disk sse 5 Slot : 5 State : Up FS Group Name : grp1 Active Alarms : NONE Disk Info : ------------------------------------------------- Disk : 1 State : Up Total Size (GB) : 134.12 Available (GB) : 130.11 Active Alarms : NONE # of Partitions : 0 -------------------------------------------------
show disk sse counters slot [disk_num]
All modes
|
slot |
Chassis slot number of the SSE card. |
|
disk_num |
Disk number on the SSE card. Values: 1 or 2. |
Displays SSE disk counters for the SSE card.
[local]Redback#show disk sse counters 2 timestamp: 11465058820 timestamp secs: 11465 timestamp usecs: 58820 Disk Counters : ------------------------------------------------- Disk : 1 Transfers (ps) : 93.08 Writes (kbps) : 15.45 Reads (kbps) : 6981.33 Total Write (kb) : 4659 Total Read (kb) : 2105917 Write Reqs (ps) : 0.22 Read Reqs (ps) : 142.36 Sector Writes (ps) : 15.45 Sector Reads (ps) : 6981.09 Avg Req Sz (sectors): 150.34 Avg Wait (ms) : 11.54 Avg Servicing (ms) : 0.93 Disk : 2 Transfers (ps) : 1.02 Writes (kbps) : 0.11 Reads (kbps) : 7.36 Total Write (kb) : 32 Total Read (kb) : 2220 Write Reqs (ps) : 0.03 Read Reqs (ps) : 10.66 Sector Writes (ps) : 0.11 Sector Reads (ps) : 7.36 Avg Req Sz (sectors): 14.67 Avg Wait (ms) : 0.95 Avg Servicing (ms) : 0.85
show dot1q counters [persistent] [slot/port [vlan-id vlan-id]] [detail]
Displays counter information for 802.1Q permanent virtual circuits (PVCs).
All modes
|
persistent |
Optional. If omitted, displays values since the counters were last cleared or the card was last reloaded. If specified, displays values since the system was last reloaded. |
|
slot |
Optional. Chassis slot number of the line card for which counters are displayed. |
|
port |
Required if you enter the slot argument. Port number of the port for which counters are displayed. |
|
vlan-id vlan-id |
Virtual LAN (VLAN) tag value for an 802.1Q tunnel or PVC. The vlan-id argument is one of the following constructs:
The range of values for any VLAN tag value is 1 to 4095. |
|
detail |
Optional. Specifies that more details are displayed for each 802.1Q PVC. |
Displays counter information on all 802.1Q tunnels and PVCs on the system.
Use the show dot1q counters command to display counter information for 802.1Q PVCs.
If you enter the optional slot and port arguments, the output displays circuit counters for the specified card or port; otherwise, the output displays only summary counter information for all 802.1Q PVCs.
The value for the port argument on the SmartEdge 100 router is either of the following:
If you enter the optional vlan-id vlan-id construct, the output displays counters for the specified 802.1Q PVC.
If you specify the VLAN tag value for an 802.1Q tunnel, the output includes circuit counters for all the PVCs within the tunnel.
The following example shows how to display counters for all 802.1Q PVCs on port 4/1:
[local]Redback>show dot1q counters 4/1
Circuit Packets/Bytes Sent Packets/Bytes Received 4/1 vlan-id 2 0 0 4/1 vlan-id 3 0 0 4/1 vlan-id 4 0 0 4/1 vlan-id 5 0 0 4/1 vlan-id 6 0 0 4/1 vlan-id 7 0 0 4/1 vlan-id 8 0 0
show dot1q profile [prof-name | detail]
Displays information for one or more 802.1Q permanent virtual circuit (PVC) profiles.
All modes
|
prof-name |
Optional. Name of the profile to be displayed. |
|
detail |
Optional. Displays detailed information for all profiles. |
Displays information for all 802.1Q PVC profiles.
Use the show dot1q profile command to display information for one or more 802.1Q PVC profiles.
If you do not specify the prof-name argument or detail keyword, this command displays a list of all 802.1Q profiles with their descriptions and PVC counts.
Use the prof-name argument to display the same detailed information is displayed with the detail keyword; use the detail keyword to display the information for all 802.1Q profiles. Table 6 lists the fields displayed with the detail keyword.
|
Field |
Description |
|---|---|
|
Profile Name |
Name specified with the dot1q profile command in global configuration mode. |
|
Description |
Text string specified with the description command in dot1q profile configuration mode. |
|
PVC Count |
Number of 802.1Q PVCs that reference this profile. |
|
Nas-port-type |
|
|
Propagate Qos from ether |
State of QoS propagation as specified by the propagate qos from ethernet command in dot1q profile configuration mode:
|
|
Propagate Qos to ether |
State of QoS propagation as specified by the propagate qos to ethernet command in dot1q profile configuration mode:
|
The following example shows how to display profile information for the profile dot:
[local]Redback>show dot1q profile dot Profile Name : dot Description : PVC Count : 0 Nas-port-type : 253 Propagate Qos from ether : Disabled Propagate Qos to ether : Enabled
show dot1q pvc [link-group-filter] [on-demand-filter | general-filter] [detail]
Displays information about 802.1Q permanent virtual circuit (PVCs).
All modes
|
link-group-filter |
link-group lg-name Optional. A filter that causes the command to display information only for PVCs in the link group specified by lg-name argument. |
|
on-demand-filter |
on-demand [[range] slot/port:ch:sub [vlan-id vlan-id]] [up | down] [all]] Optional. A filter that causes the command to display information only for on-demand PVCs. |
|
general-filter |
[summary] [up | down] [all] Optional. A general filter that causes the command to display summary information, only for active or inactive PVCs, or PVCs in all contexts. |
|
range |
Optional. The range keyword provides a summary description of all on-demand PVCs in the range specified by slot/port:ch:sub and optionally by vlan-id vlan-id. The up, down, and all keywords do not apply if the range keyword is used. |
|
slot/port:ch:sub |
Optional. Chassis slot and port numbers of the line card for which 802.1Q PVCs are displayed. For channelized media, the channel number (ch) and subchannel number (sub) can also be specified. |
|
vlan-id vlan-id |
Optional. Virtual LAN (VLAN) tag value for an 802.1Q tunnel or PVC. The vlan-id argument is one of the following constructs:
The range of values for any VLAN tag value is 1 to 4095. |
|
up |
Optional. Provides information for the specified active 802.1Q PVCs. |
|
down |
Optional. Provides information for the specified inactive 802.1Q PVCs. |
|
summary |
Optional. Provides summary information. |
|
all |
Optional. Provides information for 802.1Q PVCs in all contexts. |
|
detail |
Optional. Provides detailed information. |
None
Use the show dot1q pvc command to display information about 802.1Q PVCs.
The value for the port argument on the SmartEdge 100 router is one of the following:
If you specify the VLAN tag value for an 802.1Q tunnel, the output includes PVC information for all the PVCs within the tunnel.
The following example shows how to display 802.1Q PVCs on port 1 in slot 13:
[local]Redback>show dot1q pvc 13/1
Circuit State Profile Bound to 13/1 vlan-id 1 Up vlan1@local
The following example shows how to display a summary of all 802.1Q PVCs in all contexts:
[local]Redback#show dot1q pvc summary all
PVCs total: 1, Up: 1, Down: 0, Bound: 0
The following example shows how to display detailed information all 802.1Q PVCs:
[local]Redback#show dot1q pvc detail Circuit : 5/1 vlan-id 700:201 Bindings : gig700.201@local State : Up Description : Encapsulation : dot1q Profile : Agent Circuit ID: QOS Hierarchical Mode: wrr QOS Max Rate : 91000 QOS Min Rate : 50000 QOS Policing : peanut acl-counters QOS Queuing : sony Circuit : 5/1 vlan-id 700:202 Bindings : gig700.202@local State : Up Description : Encapsulation : dot1q Profile : Agent Circuit ID: QOS Hierarchical Mode: strict QOS Weight : 40 QOS Policing : butter inherit acl-counters QOS Metering : science inherit acl-counters QOS Queuing : sony
The following example shows how to get information on PVCs in the lg-vlans link-group:
[local]Redback(config)#show dot1q pvc link-group lg-vlans
The following example shows how to display the information for the on-demand 802.1Q PVC connected to port/slot 5/1:
[local]Redback>show dot1q pvc on-demand range 5/1 Port Vlan through Vlan 5/1 1 through 2 5/1 3 through 3 C-VLANs: 0; S-VLANs: 0; VLANs: 3; Total: 3
show dot1q pvc transport
Displays information for all transport-enabled 802.1Q permanent virtual circuits (PVCs).
All modes
None
Use the show dot1q pvc transport command to display information about all transport-enabled 802.1Q PVCs.
The following example shows how to display information about all transport-enabled 802.1Q PVCs connected to the SmartEdge router:
[local]Redback>show dot1q pvc transport TSP-ID : 5/1 any Range End : Profile : --- Description : Binding : --- State : Down
show dvsr [ip-addr/prefix-length | detail | profile | summary] [all]
Displays information about all dynamically verified static routing (DVSR) routes.
All modes
|
ip-addr/prefix-length |
Optional. Displays the DVSR routes that match the IP address, in the form A.B.C.D, and the prefix length, separated by the slash (/) character. The range of values for the prefix-length argument is 0 to 32. |
|
detail |
Optional. Displays detailed DVSR route information. |
|
profile |
Optional. Displays DVSR profile information. |
|
summary |
Optional. Displays a summary report on DVSR routes in all contexts. |
|
all |
Optional. Displays DVSR information for all contexts. |
All DVSR routes in the current context are displayed.
Use the show dvsr command to display information about all DVSR routes.
Use the optional keywords to display specific DVSR routes, DVSR profiles, detailed DVSR route information, and summary reports.
Table 7 describes the show dvsr command output fields.
|
Field |
Description |
|---|---|
|
DVSR route |
IP address and prefix length of the static route. |
|
S |
State of the DVSR, either Up or Down. |
|
Verify Addr |
IP address that the DVSR route should verify. |
|
Count |
Number of verification successes (or failures) since the DVSR state change. |
|
Delay |
Average round trip and processing delay of the verification. |
|
Tran |
Number of state transitions for the DVSR route. |
|
Seq |
Internal sequence number for the DVSR route. |
|
profile |
Name of the DVSR profile for the DVSR route. |
Table 8 describes the show dvsr profile command output fields.
|
Field |
Description |
|---|---|
|
DVSR profile |
Name of the DVSR profile. |
|
Num |
Number of DVSR routes associated with this profile. |
|
Intv |
Verification interval in seconds of the profile. |
|
F |
Timeout multiplier value of the profile. |
|
S |
Minimum success value of the profile. |
|
Next |
Number of seconds for the next verification process for this profile to start. |
|
TTL |
Time-to-live value of the profile. |
|
DIST |
Distance value of the profile. |
|
TAG |
Tag value of the profile. |
|
Src Addr |
Source address of the profile. |
The following example displays all DVSR routes:
[local]Redback>show dvsr
DVSR route S Verify Addr Count Delay Tran Seq profile 11.12.0.0/16 Up 10.14.100.2 172 305 1 513 find-dopey 12.12.12.12/32 Up 10.14.101.2 172 309 1 714 find-dopey 12.1.1.0/24 Dn 10.14.100.4 12 0 2 514 black 12.1.2.0/24 Up 10.14.100.7 171 7 1 515 black Total DVSR prefixes in context local: 4
The following example displays all DVSR profiles:
[local]Redback>show dvsr profile
DVSR profile Num Intv F S Next TTL DIST TAG Src Addr nice 12 20 3 2 12 5 1 0 good 3 20 3 2 7 5 1 0 Total DVSR profiles in context local: 2
The following example shows how to display the DVSR summary report:
[local]Redback>show dvsr summary
DVSR summary: dvsr profiles: 4 dvsr routes: 5 routes alive: 5 routes fail: 0 total ping sent: 122 total recv icmp replies: 122 total icmp timeout: 0 total icmp no reply: 0 total reply no route: 0 total nexthop invalid: 2 avg round trip delay(msec): 0 max round trip delay(msec): 80 avg ping time(msec): 0 max ping time(msec): 80 total ping operation: 73 total ping error: 0 total route state changes: 5 max pings in a batch: 2
show ethernet-cfm circuit cct [level level]
Displays the CFM information about a specified circuit or circuits or a bundle of link-group aggregated circuits.
Exec (10)
|
circuit cct |
Link-group or VLAN-ID of the circuit for which CFM instance information is displayed. The syntax for the circuit argument is: {lg lg-name | id lg-ID} | {slot/port [vlan-id vlan-id]}[level level] |
|
level level |
The level of the MD containing the specified circuit. |
|
detail |
Display detailed CFM information. |
|
lg lg-name | id lg-ID |
Specifies the link-group name or link-group ID for which circuit CFM information is displayed. |
|
slot/port |
Specifies the slot and port on the system for which circuit CFM information is displayed. |
|
vlan-id vlan-id |
Specifies the VLAN-ID of the circuit for which CFM information is displayed. |
No default
Use this command to display the CFM information about a specified circuit or circuits or a bundle of link-group aggregated circuits.
The following example illustrates the usage of this command:
[local]jazz#show ethernet-cfm circuit 6/1 vlan-id 2 level 1 Instance Name: DOWN-INSTANCE Domain Name : ericsson Domain Id : 1 Level : 1 MP Id : 106 MP Type : MEP MA Name : devtest MA Id : 1 Ccms : Enabled Cct handle : 6/1:1023:63/1/2/19
show ethernet-cfm database instance-name domain domain-name [detail]
Displays the CFM information about a specified maintenance domain (MD) in a specified CFM instance.
Exec (10)
|
instance-name |
Name of a CFM instance in the SmartEdge router. |
|
domain-name |
The name of the MD which is configured in the CFM instance. If no domain-name is specified, the instance-name is used. |
|
detail |
Display detailed information. |
No default
Use this command to display the CFM information about a specified MD in a specified CFM instance.
The following two examples illustrates the output fields of this command:
[local]Redback#show ethernet-cfm database UP-INSTANCE domain redback DOMAIN NAME : redback ----------------- Level : 2 Domain Id : 1 Number of MAs : 1 Number of MIPs : 1 [local]Redback#show ethernet-cfm database UP-INSTANCE domain redback detail DOMAIN NAME : redback ----------------- Level : 2 Domain Id : 1 Number of MAs : 1 Number of MIPs : 1 Group mac : 01:80:c2:00:00:32
instance-name
show ethernet-cfm database instance-name
Displays information stored in the system’s CCM database for the specified CFM instance. Displays all the maintenance domains (MDs), their maintenance associations (MAs), their maintenance intermediate points (MIPs), and the maintenance end points (MEPs) for the maintenance associations (MAs).
Exec (10)
|
instance-name |
Name of a CFM instance in the SmartEdge router. |
No default
Use this command to display information stored in the system’s CCM database for the specified CFM instance. This command displays all the maintenance domains, their MAs, their MIPs, the MEPs for the MAs.
|
Field |
Description |
|---|---|
|
DOMAIN NAME |
Domain name associated with the specified CFM instance |
|
Level |
MD level |
|
Domain Id |
Index for the MD configured under the CFM instance |
|
Number of MAs |
Number of MAs in the MD |
|
Number of MIPs |
Number of MIPs in the MD |
|
MA Name |
Maintenance association name |
|
Ccms |
Continuity check enabled/disabled |
|
Ccm Interval |
Interval between CCM PDUs |
|
Number of local MEPS |
For each MA: the number of local maintenance association endpoints (MEPs). |
|
MA Id/MA Name/MD Id/Vlan Id/Status |
For each MA:
|
|
MpId/Level/MAC Addr/MA Id/Vlan Id |
For each MEP in the MA:
|
|
State\Direction\Circuit Type |
For each MEP in the MA:
|
|
Number of Remote MEPs |
Number of MEPs in the maintenance domain (MD) for which MEPIDs have been assigned, and which are bound to ports or circuits not in the SmartEdge router. |
|
MpId/Level/MAC Addr/MA Id/Vlan Id |
For each remote MEP in the MD:
|
|
State\Direction\Circuit Type |
For each remote MEP in the MD:
|
|
Number of MIPs |
Number of maintenance association intermediate points (MIPs) in the current MD |
|
MpId/Level/MAC Addr/MA Id/Vlan Id |
For each MIP in the MD:
|
|
State\Direction\Circuit Type |
For each remote MIP in the MD:
|
The following example shows the output fields of this command. The Domain Id field represents the index for the maintenance domain configured under the CFM instance. The Index field reports the index of the MA configured under the MD:
[local]Redback#show ethernet-cfm database instance-2 DOMAIN NAME : redback ----------------- Level : 5 Domain Id : 3 Number of MAs : 1 Number of MIPs : 0 MA Name : platform (Index : 3) --------- Ccms : Enabled Ccm Interval : 100 ms Number of local meps : 1 Number of remote meps : 1 Local MEP Information: MepId Level MacAddr State Dir Defects Circuit -------------------------------------------------------------- 101 5 00:30:88:02:7f:5e Reset Up 2 1/1 vlan-id 100 Remote MEP Information: MepId MacAddr State -------------------------------- 100 00:00:00:00:00:00 None
The following example shows a CFM database instance in which an MIP has been configured:
[local]Redback#show ethernet-cfm database UP-INSTANCE DOMAIN NAME : redback ----------------- Level : 2 Domain Id : 1 Number of MAs : 1 Number of MIPs : 1 MIP Information: MipId Level MacAddr State Dir Circuit ----------------------------------------------------- 1 2 00:30:88:02:f3:22 Reset Up 2/1 vlan-id 1 MA Name : platform (Index : 1) --------- Ccms : Enabled Ccm Interval : 1s Number of local meps : 1 Number of remote meps : 1 Local MEP Information: MepId Level MacAddr State Dir Defects Circuit -------------------------------------------------------------- 100 2 00:30:88:02:f3:24 Reset Up - 2/3 vlan-id 1 Remote MEP Information: MepId MacAddr State -------------------------------- 101 00:30:88:12:3d:8f OK
show ethernet-cfm database instance-name domain domain-name ma ma-short-name [detail]
Displays CFM information about a maintenance association (MA) in a specified CFM instance.
Exec (10)
|
instance-name |
Name of a CFM instance in the SmartEdge router. |
|
domain-name |
The name of the MD that is configured in the CFM instance. If no domain-name is specified, the instance-name is used. |
|
ma ma-short-name |
The name of the MA. |
|
detail |
Display detailed information. |
No default
Use this command to display CFM information about a maintenance association (MA) in a specified CFM instance.
The following example shows the output fields of this command. The Frame Loss field reports the setting entered for the MA by the frame-loss command:
[local]Redback#show ether data instance-1 domain redback ma platform detail MA Name : platform Instance name: instance-1 Level : 5 Domain name : redback Domain Id : 2 MA-Index : 2 Flags : 0 Ccms : Enabled Ccm Interval : 100ms Slot mask : Ox1 Frame loss : 0 Number of local meps : 1 Number of remote meps : 1
show ethernet-cfm database instance-name domain domain-name ma ma-short-name mep mep-id [detail]
Displays CFM information about local Maintenance Endpoints (MEPs) in a specified Maintenance Association (MA) in a specified CFM instance.
Exec (10)
|
instance-name |
Name of a CFM instance in the SmartEdge router. |
|
domain-name |
The name of the MD which is configured in the CFM instance. If no domain-name is specified, the instance-name is used. |
|
ma ma-short-name |
The name of the MA. Displays summary of all MAs in the CFM instance if no MA name is specified. |
|
mep mep-id |
The ID of a local MEP. Reports specified MEP in the specified MA that is bound to a local circuit interface on the SmartEdge router. |
|
detail |
Display detailed information. |
No default
Use this command to display CFM information about local Maintenance Endpoints (MEPs) in a specified Maintenance Association (MA) in a specified CFM instance.
|
Field |
Description |
|---|---|
|
Domain id |
Index of MD configured under the CFM instance. |
|
MA index |
Index of the MA configured under the CFM instance. |
|
Slotmask |
The mask to reflect the physical slot on which the MEP is configured. |
|
Ref counter |
Number of circuits in the MEP (including the MEP circuit). |
|
Xc/L2vpn |
Reports if the MEP has a cross connection or L2VPN configured. |
|
Linkgroup Id |
The ID of the Link group configured under the MEP |
|
Cct handle |
The circuit handle (unique identifier in the system) for the circuit on which the local MEP is configured |
|
Lg active cct |
The circuit in the link group used to transmit CCMs. |
|
State |
FNG state of the MEP. |
|
Mep Defects |
Defect detected for the MEP, which could be a remote MEP defect, configuration error, and so on. |
|
Highest Defect |
The highest defect detected for the MEP. |
|
Lbms |
Displays if loopback message (LBM) is enabled in the MEP. |
|
Ltms |
Displays if link-trace message (LTM) is enabled in the MEP. |
|
Lbms/Ltms in |
Counters for the number of LTMs and LBMs received. |
|
Ltms priority |
Priority value of the LTMs sent out. |
|
Lbms/Ltms dropped |
Counter for the number of LTMs and LBMs dropped. |
|
Lbms bad msdu |
Counter for the number of LBMs received with incorrect field values. |
|
Lbrs in/out |
Counter for the number of LBRs received and sent out. |
|
Lbrs OutOfOrder |
Counter for the number of LBRs received out of order. |
|
Lbrs bad msdu |
Counter for the number of LBRs received with incorrect field values. |
The following example shows the output fields of this command.
Example 1 Detailed Output of show ethernet-cfm... Linktrace Output
[local]Redback#show ethernet-cfm database up domain dd ma platform mep 101 linktrace detail ------------------------------------------------------------------- SequenceNumber: 32 ReceiveOrder : 1 ------------------------------------------------------------------- Ttl : 63 Forwarded : No TerminalMep : No Relay Action : RlyMpDB LastEgressId : 00:00:00:30:88:13:07:8f NextEgressId : 00:00:00:00:00:00:00:00 ChassisId Subtype : NetworkAddress ChassisId : 01 0a 0d 0b 1e ManAddressDomain : snmpOther ManAddress : 0 0 0 0 0 IngressMac : 00:30:88:01:a0:74 Ingress Action : IngOk IngressPortIdSubtype : Local IngressPortId : 9/5:1023:63/1/2/18 EgressMac : 00:00:00:00:00:00 Egress Action : IngNoTlv
show ethernet-cfm database instance-name domain domain-name mip [mip-id] [detail]
Displays CFM information about maintenance intermediate points (MIPs) in a specified CFM instance.
Exec (10)
|
instance-name |
Name of a CFM instance in the SmartEdge router. |
|
domain-name |
The name of the MD which is configured in the CFM instance. If no domain-name is specified, the instance-name is used. |
|
mip mip-id |
The MIP ID. If no mip-id argument is specified, all MIPs in the CFM instance are displayed. |
|
detail |
Display detailed information. |
No default
Use this command to display the CFM information about MIPs in a specified CFM instance.
|
Abbreviation |
Description |
|---|---|
|
Slotmask |
The mask to reflect the physical slot on which the MIP is configured. |
|
Ref counter |
Number of circuits in the MIP (including the MIP circuit). |
|
Xc/L2vpn |
Reports if the MIP has a cross connection or L2VPN configured. |
|
Linkgroup Id |
The ID of the Link group configured under the MIP. |
|
Cct handle |
The circuit handle (unique identifier in the system) for the circuit on which the local MIP is configured. |
|
Lg active cct |
The circuit in the link group used to transmit CCMs. |
|
Active cct handle |
The circuit handle (unique identifier in the system) for the circuit in the link group used to transmit CCMs. |
|
Lbms in |
Loopback message (LBM) received. |
|
Ltms in |
Link-trace message (LTM) received. |
The following example shows the output fields of this command:
[local]Redback#show ether data UP-INSTANCE domain redback mip 1 detail MipId : 1 Instance name : UP-INSTANCE Level : 2 Domain name : redback Domain id : 1 Slotmask : Ox0 Ref counter : 2 Xc/L2vpn : Yes Linkgroup Id : 0 Circuit : 2/1 vlan-id 1 Cct handle : 2/1:1023:63/1/2/6 Lg active cct : - Active cct handle: - MacAddr : 00:30:88:02:f3:22 Lbms in : 0 Lbms out : 0 Lbrs in : 0 Lbrs out : 0 Ltms in : 0 Ltms out : 0 Ltrs in : 0 Ltrs out : 0 Lbms dropped : 0 Lbms bad msdu : 0 Lbrs OutOfOrder: 0 Lbrs bad msdu : 0 Ltms dropped : 0 Ltrs dropped : 0 Ltrs UnexpIn : 0
show ethernet-cfm database instance-name domain domain-name ma ma-short-name rmep rmep-id [detail]
Displays CFM information about local Remote Maintenance Endpoints (RMEPs) in a specified Maintenance Association (MA) in a specified CFM instance. The following fields are displayed
|
Field |
Description |
|---|---|
|
Remote MepID. MacAdd, State |
Remote MEP identifier, the MAC address of the port, the status of the port. |
|
Instance name |
Name of the instance in which the RMEP is defined. |
|
Level |
Level of the instance |
|
Domain name |
Name of the MD that contains the RMEP.. |
|
Domain id |
ID of the domain assigned by the CFM database. |
|
MA name |
Name of the MA that contains the RMEP. |
|
MA id |
ID of the domain assigned by the CFM database. |
|
MA index |
Index of the MA assigned by the CFM database. |
|
State |
Status of the RMEP. |
|
Mac addr |
MAC address of the RMEP. |
|
Local MepId |
The ID of the local MEP that is peer to the specified RMEP. |
|
Vlan |
VLAN ID of the PVC on which the RMEP CCMs are received. |
Exec (10)
|
instance-name |
Name of a CFM instance in the SmartEdge router. |
|
domain-name |
The name of the MD which is configured in the CFM instance. If no domain-name is specified, the instance-name is used. |
|
ma ma-short-name |
The name of the MA. Displays summary of all MAs in the CFM instance if no MA name is specified. |
|
rmep rmep-id |
The ID of a remote MEP. Reports specified MEP in the specified MA that is bound to another network node. |
|
detail |
Display detailed information. |
No default
Use this command to display CFM information about Remote Maintenance Endpoints (RMEPs) in a specified MA in a specified CFM instance.
The following example shows the output fields of this command:
[local]jazz#show ethernet-cfm database DOWN-INSTANCE domain ericsson ma devtest rmep 601 detail Remote MepId : 601 Instance name: DOWN-INSTANCE Level : 1 Domain name : ericsson Domain id : 1 MA name : devtest MA index : 1 State : OK Mac addr : 00:30:88:11:d1:8d Local MepId : 106 Vlan : 2:0
show ethernet-cfm errors instance-name domain-name ma-short-name
Displays the CFM error conditions detected in the specified Maintenance Association (MA).
This command displays the following error reasons when they occur:
Can indicate level mismatch, CCM disabled, CCM interval mismatch, CCM sequence errors, or remote mep MAC changes.
Can indicate CCM interval expiry or remote MEP port type, length, or value (TLV) change in the CCM detected.
Indicates receipt of CCMs with same MAC address and MEP ID as the local MEP.
Indicates receipt of CCMs from remote MEP ID that is not present in the CFM instance database.
Indicates one of the following: Receipt of CCMs from a lower MD level than the one configured on the CFM instance, MAID mismatch, or local MEP ID mismatch.
Exec (10)
|
instance-name |
Name of a CFM instance that contains the MA.. |
|
domain-name |
The name of the MD that contains the MA. |
|
ma-short-name |
The name of the MA for which you wish to see the CFM error report. |
No default
The following example shows that a port down was detected at the remote MEP 601:
[local]jazz#show ethernet-cfm errors DOWN-INSTANCE ericsson devtest --------------------------------------------------------------- Instance Name : DOWN-INSTANCE Domain Name : ericsson Domain Id : 1 Level : 1 MA Name : devtest MA Id : 1 RMEP Id : 601 Mac addr : 00:30:88:11:d1:8d Error : MEP down (Port down)
show ext-community-list [ecl-name | first-match ecl-name ext-community-num | summary]
Displays information about configured Border Gateway Protocol (BGP) extended community lists.
All modes
|
ecl-name |
Optional. Extended community list name. |
|
first-match |
Optional. Searches for the first match in the extended community list specified by the ecl-name argument. |
|
ext-community-num |
Extended community list number for the list in which the ecl-name first match is attempted. The extended community number can be specified only when configuring an extended community list. It can be expressed in either of the following formats:
|
|
summary |
Optional. Displays extended community list summary information. |
Displays all configured extended community lists.
Use the show ext-community-list command to display information about configured BGP extended community lists.
The following example displays two extended community lists (1 and 2):
[local]Redback>show ext-community-list
ext-community-list ext-comm-list01: count: 1, sequences: 10 - 10, client count: 1 modified: 4 day(s), 17 hour(s) ago seq 10 permit RT:100:100 (hits: 0, cache hits: 0) seq 20 permit RT:100:200 (hits: 2, cache hits: 1) ext-community-list ext-comm-list02: count: 4, sequences: 30 - 60, client count: 1 modified: 4 day(s), 17 hour(s) ago seq 30 permit RO:10.10.10.1:3600 (hits: 0, cache hits: 0) seq 40 permit RO:20.20.20.1:22 (hits: 0, cache hits: 0) seq 50 permit RT:11:121 (hits: 4, cache hits: 2) seq 60 permit RT:11:102 (hits: 2223, cache hits: 2217)
show flow admission-control profile {all | id profile-id | name profile-name}
Displays details of one or all flow admission control (FAC) profiles on the current SmartEdge router.
All modes
|
all |
Displays abbreviated output for all FAC profiles on the current SmartEdge router. |
|
id profile-id |
ID of the FAC profile to be displayed. |
|
name profile-name |
Name of the FAC profile to be displayed. |
None
Use the show flow admission-control profile command to display details of one or all FAC profiles on the current SmartEdge router.
The following example shows how to display all FAC profiles:
[local]Redback(config)#show flow admission-control profile all Name Id ---------------------------------------------------- ---------- f1 0x40500001 f2 0x40500002 f3 0x40500003
The following example shows how to display information for a FAC profile with the ID 0x40500001:
[local]Redback(config)#show flow admission-control profile id 0x40500001 Name Id --------------------------------------------------------------- f1 0x40500001
The following example shows how to display information for a FAC profile with the name f1:
[local]Redback(config)#show flow admission-control profile name f1 Name Id --------------------------------------------------------------- f1 0x40500001
show flow circuit {all | circuit-id}
Displays FAC profile IDs for all circuits on the current SmartEdge router
All modes
|
all |
Optional. Displays the FAC profile IDs for all circuits. |
|
circuit circuit-id |
Optional. ID of an 802.1Q permanent virtual circuit (PVC). |
None
Use the show flow circuit command to display FAC profile IDs for all circuits on the current SmartEdge router
The following example shows how to display FAC details for all circuits that have a FAC profile applied:
[local]Redback(config)#show flow circuit all Circuit FAC Id Dir FAC Id Dir ---------------------------------------------------------- 1/1:1023:63/1/2/6 0x40500002 OUT 1/1:1023:63/1/2/8 0x40500003 IN 1/1:1023:63/1/2/245750x40500003 BIDIR
show flow collector [collector-name [statistics]]
Displays information related to an external collector.
All modes
|
collector-name |
Identifies an external collector. |
|
statistics |
Displays statistical information for the specified external collector. |
Enter the show flow collector command without the optional argument or keyword to display a list of all external collectors configured in the current context.
Use the show flow collector command to display information related to an external collector.
Table 13 describes the show flow collector command output for all external collectors configured in the current context.
|
Field |
Description |
|---|---|
|
Collector |
Identifies the external collector for which information is displayed. |
|
Identifier |
External collector identifier in hexadecimal format. A hexadecimal identifier is internally created when you create a new collector and is mapped to the collector. The hexadecimal identifier is used primarily for debugging purposes. |
|
IP Address |
Destination address for the external collector where exported packets are received. Use the ip address command in flow collector configuration mode to specify an IP address for an external collector. |
|
Port |
Port on the external collector that receives exported packets. This is the port that listens for flow records from the SmartEdge router. Use the port command in flow collector configuration mode to configure or modify the destination port for an external collector. |
Table 14 describes the show flow collector command output for a specific external collector.
|
Field |
Description |
|---|---|
|
Collector |
Identifies the external collector for which information is displayed. |
|
Identifier |
External collector identifier in hexadecimal format. A hexadecimal identifier is internally created when you create a new external collector and is mapped to the external collector. The hexadecimal identifier is used primarily for debugging purposes. |
|
Context |
Context that hosts the specified external collector. |
|
Source IP |
Source IP address from which packets are sent to the external collector. If the source IP address was set to zero, then the ip-address of the outgoing interface will be used. |
|
Destination IP |
Destination address for the external collector where exported packets are received. Use the ip address command in flow collector configuration mode to specify an IP address for an external collector. |
|
Destination port |
Port on the external collector that receives exported packets. This is the port that listens for flow records from the SmartEdge router. Use the port command in flow collector configuration mode to configure or modify the destination port for an external collector. |
|
Transport protocol |
Protocol used for transporting flow records. User Datagram Protocol (UDP) is the only supported protocol in this release. |
|
Export version |
Export version that determines the fields included in the flow record. In this release, only Export version 5 is supported. |
|
Profile |
Identifies an RFlow profile that is attached to the specified external collector. A single external collector can have multiple RFlow profiles attached to it. You can configure up to 10 profiles on a single external collector. |
The following example displays summarized information about all external collectors configured in the current context:
[local]Redback#show flow collector Collector Identifier IP Address Port --------- ---------- ---------- ---- c1 0x2 10.13.168.77 5000
The following example displays information about all external collectors configured on the router:
[local]Redback#show flow collector c1 Collector : c1 Identifier : 0x2 Context : local Source IP : 10.13.168.70 Destination IP : 10.13.168.77 Destination port : 5000 Transport protocol : udp Export version : v5 Profile : p1
show flow counters [{detail | debug | clear}]
Displays settings for common flow admission control (FAC) counters.
All modes
|
detail |
Optional. Displays FAC counters. |
|
debug |
Optional. Displays debug information for FAC counters. |
|
clear |
Optional. Clears FAC counters after displaying them. |
None
Use the show flow counters command to display FAC counters
The following example shows how to display summary information for FAC counters:
[local]Redback(config)#show flow counters Current time: Mon Apr 30 17:51:37 2007 Last cleared: Never FAC Profile------------------------------------ Create4Apply3 Delete0UnApply0 FAC Profile Current---------------------------- FAC Profs4Applied Ccts3
The following example shows how to display detailed information for FAC counters:
[local]Redback(config)#show flow counters detail Tree Failures---------------------------------------------------- No Memory 0 No Room in Table 0 ISM Msgs Ignored------------------------------------------------- Unknown Event 0 Port State Ign 3 Cct State No Cct 0 Cct State Ign 6 Cct Cfg No Cct 0 Total Ignored 9 Flow Application------------------------------ ------------------- RCM Apply 3 AAA Apply 0 RCM UnApply 0 AAA UnApply 0 RCM Appl Ignored 0 AAA Appl Ignored 0 RCM UnAppl Ignor 0 AAA UnAppl Ignor 0 Apply Conflict 0 UnApply Conflict 0 UnApply No Cct 0 FAC Cct Adds 3 FAC Cct Dels 0 FAC Application Current------------------------------------------ RCM Applied Ccts 3 AAA Applied Ccts 0
The following example shows how to display debug information for FAC counters:
[local]Redback(config)#show flow counters debug
Current time: Sat Jun 18 08:37:22 2007
Last cleared: Never
IPC----------------------------------------------
IPCs from ISM 4 Msgs from ISM 6
IPCs from RCM 8
IPCs from PPAs 0
PPA----------------------------------------------
Births 2 Deaths 0
RCM----------------------------------------------
Births 3 Deaths 2
IPC in Rejected 0
ISM----------------------------------------------
Births 1 Deaths 0
EOF 1 MBE All EOF 1
ISM In-------------------------------------------
ISM Statistics
Total events: ipc rcvd: 0, ipc err 0, unknown event 0
ID: I/F :state 0, cfg 0, IP cfg 0,
Cct :state 2, Cct cfg 1, Cct grp 0
Port :state 1, Port cfg 0
Lg :cfg 0
L2tp :sesscfg 0
Hdr :only 2
GrpMac :cfg 0
Card :state 0The following example shows how to display FAC counters and then clears them:
[local]Redback(config)#show flow counters clear Current time: Mon Jun 27 09:45:27 2007 Last cleared: Never FAC Profile------------------------------------------------- Create 3 Apply 1 Delete 0 Unapply 0 FAC Profile Current----------------------------------------- FAC Profs 3 Applied Ccts 1
show flow ip [show-flow-ip-arguments]
Shows IP flow accounting information.
All modes
You can replace show-flow-ip-arguments with the following keywords:
|
application-list |
Displays information on application lists. |
|
cache |
Displays cache information. |
|
circuit |
Displays information on circuits. |
|
log |
Displays IPFIX logging information. |
|
profile |
Displays profile information. |
If you have configured one profile, the show flow ip command displays the following output:
[local]Redback# show flow ip Number of Profiles : 1 Number of Circuits : 0 Number of Collectors : 0 Number of Caches : 0 Sampling Interval : 1 [local]Redback#
In the output, the Sampling Interval is 1 (the default value). The rest of the fields are reported based on configuration.
Use the show flow ip command to display information on RFlow profiles, circuits, collectors, caches, and the sampling interval. Table 15 describes the show flow ip command output:
|
Field |
Description |
|---|---|
|
Number of Profiles |
Displays number of configured RFlow profiles. |
|
Number of Circuits |
Displays number of RFlow circuits. |
|
Number of Collectors |
Displays number of configured RFlow collectors in the system |
|
Number of Caches |
Displays number of RFlow caches created in the system. |
|
Sampling Interval |
Displays configured sampling packet interval. |
The following example displays information on the number of profiles, circuits, collectors, caches, and the packet sampling interval:
[local]Redback# show flow ip Number of Profiles : 4 Number of Circuits : 2 Number of Collectors : 1 Number of Caches : 2 Sampling Interval : 1
show flow ip application-list [appl-list-name]
Displays the configured application lists.
All modes
|
appl-list-name |
Name of an application list. |
Displays the names of all the application lists configured on the system, including the system default application list,_sys_dflt_app_list_.
Use the show flow ip application-list command to view the list of configured application lists and their contents.
The following example displays the contents of the system default application list, _sys_dflt_app_list_:
[local]Redback# show flow ip application-list _sys_dflt_app_list_ application-list _sys_dflt_app_list_ application TCP-Telnet protocol tcp port 23 application TCP-FTP protocol tcp port 21 application TCP-FTPD protocol tcp port 20 application TCP-HTTP protocol tcp port 80 application TCP-SMTP protocol tcp port 25 application TCP-BGP protocol tcp port 179 application TCP-NNTP protocol tcp port 119 application TCP-Other protocol tcp application UDP-DNS protocol udp port 53 application UDP-NTP protocol udp port 123 application UDP-TFTP protocol udp port 69 application UDP-Other protocol udp application ICMP protocol icmp application IGMP protocol igmp
The show flow ip application-list command displays the configured values. For more information, see the flow ip application-list command.
show flow ip cache [ profile-name {dump | statistics [application ] | top-talkers [number [sort-by {packets | bytes } | all-context]
Displays a list of all RFlow caches currently configured on the router or detailed information about a specific RFlow cache.
All modes
|
profile-name |
Profile hosting the cache or caches of information that you want to display. |
|
dump |
Displays the entire contents of the specified cache. |
|
statistics |
Displays statistical information for all the flow records in the specified cache. |
|
application |
Displays statistics related to your application protocols in a specified cache. |
|
top-talkers |
Displays information about the largest packet and byte consumers in the network. |
|
number |
Displays the specified range, between 1 and 20, of items to display in the top-talkers output list. |
|
sort-by packets or byte |
Displays information based on your sort criteria for top-talkers, whether top-talkers are determined by number of packets or number of bytes. |
|
all-context |
Displays the names of all profile caches in all contexts. The all-context keyword is available in the local context only. |
Enter the show flow ip cache without any of the optional arguments or keywords to display summarized information for all RFlow caches in the current context.
Use the show flow ip cache command to display a list of all RFlow caches currently configured on the router, or to display detailed information about a specific RFlow cache.
Table 16 describes the show flow ip cache command output.
|
Field |
Description |
|---|---|
|
Profile |
Identifies an RFlow profile associated with this cache. |
|
Max Size |
Number of entries allowed in the cache before they are aged (sent to an external collector). |
|
Usage |
Amount of the cache used at the time the show flow ip cache command is executed. The display shows the number of resource entries currently in the cache. |
Table 17 describes the show flow ip cache all-context command output.
|
Field |
Description |
|---|---|
|
Profile |
Identifies an RFlow profile associated with this cache. |
|
Max Size |
Number of entries allowed in the cache before they are aged (sent to an external collector). |
|
Usage |
Amount of the cache used at the time the show flow ip cache command is executed. The display shows the number of resource entries currently in the cache. |
|
Context |
Identifies the context of the cache. |
Table 18 describes the show flow ip cache statistics command output.
|
Field |
Description |
|---|---|
|
Profile |
Identifies the RFlow profile for which information is displayed. |
|
Context |
Identifies the context that hosts the specified profile. |
|
Statistics |
Displays statistics for the following cache counters:
The cache statistics counters are not resilient and are initialized to 0 after a process restart. |
|
Collector Stream Information |
Displays the following stream statistic counters for the specified external collectors:
All stream statistic counters are resilient except ExportID. The ExportID counter is reset to 0 after a restart or switchover, indicating that an error has occurred in RFlow. |
Table 19 describes the show flow ip cache statistics application command output.
|
Field |
Description |
|---|---|
|
Total Flows |
Number of flows in the cache for this application since the last time the statistics were cleared. |
|
Flows/Sec |
Average number of flows per second for this application. |
|
Packets/Flow |
Average number of packets per flow for this application. |
|
Bytes/Pkt |
Average number of bytes per packet for this application. |
|
Packets/Sec |
Average number of packets per second for this application. |
|
Active(Sec)/Flow |
Average number of seconds that a flow was active for this application before it expired. |
|
Idle(Sec)/Flow |
Average number of seconds that a flow was idle for this application before it expired. |
The following example shows how to display summary information for all RFlow caches in the current context:
[local]Redback#show flow ip cache Profile Max Size Usage ------- -------- ----- p1 4096 0
The following example shows how to display information about all caches configured on the router:
[local]Redback#show flow ip cache all-context Profile Max Size Usage Context ------- -------- ----- ------- p1 4096 0 local p1 4096 0 rflow
The following example shows how to display statistical information for the cache called p1:
[local]Redback#show flow ip cache p1 statistics
Profile : p1
Context : local
Statistics:
PPA flows received : 0
PPA flows processed : 0
PPA flows discarded : 0
Processing errors : 0
Cache entries created : 0
Cache entries updated : 0
Cache entries aged : 0
Cache entries fast-aged: 0
Entries in cache : 0
Ager walks : 0
Collector Stream Information:
Collector ExportID Seq Number Generated Send Errors
Packets Records Packets Records
--------- -------- ---------- -------- ---------- --------- -------
c1 1 0x4 2 4 0 0
The following example displays statistical information on flow records for application protocols gathered per cache since the last time it was cleared. To look for information on a specific application, use output modifier and grep for information on that specific application.
[local]Redback#show flow ip cache p1 statistics application Last cleared: Thu Aug 13 18:57:22 2009 Current time: Thu Aug 13 19:12:57 2009 Application Total Flows Packets Bytes Packets Active(Sec) Idle(Sec) ----------- Flows /Sec /Flow /Pkt /Sec /Flow /Flow TCP-Telnet 0 0.0 0 0 0.0 0.0 0.0 TCP-FTP 0 0.0 0 0 0.0 0.0 0.0 TCP-FTPD 0 0.0 0 0 0.0 0.0 0.0 TCP-HTTP 0 0.0 0 0 0.0 0.0 0.0 TCP-SMTP 0 0.0 0 0 0.0 0.0 0.0 TCP-BGP 0 0.0 0 0 0.0 0.0 0.0 TCP-NNTP 0 0.0 0 0 0.0 0.0 0.0 TCP-Other 6 0.0 46666 1200 299.5 9.9 20.1 UDP-DNS 0 0.0 0 0 0.0 0.0 0.0 UDP-NTP 0 0.0 0 0 0.0 0.0 0.0 UDP-TFTP 0 0.0 0 0 0.0 0.0 0.0 UDP-Other 0 0.0 0 0 0.0 0.0 0.0 ICMP 0 0.0 0 0 0.0 0.0 0.0 IGMP 0 0.0 0 0 0.0 0.0 0.0 Other 0 0.0 0 0 0.0 0.0 0.0
show flow ip circuit [circuit-id | all-context]
Displays information about a specified IP circuit that has RFlow enabled.
All modes
|
circuit-id |
Optional. Circuit identifier. Use the show flow circuit all command to display a list of all FAC profile IDs for all circuits on the current SmartEdge router. |
|
all-context |
Displays information about all circuits configured in all contexts. The all-context keyword is available in the local context only. |
Enter the command without the optional circuit-id argument to display brief information about all circuits in the current context that have RFlow enabled.
Use the show flow ip circuit command to display information about a specified IP circuit that has RFlow enabled.
Table 20 describes the show flow ip circuit command output for all circuits.
|
Field |
Description |
|---|---|
|
Circuit |
Identifies the circuit for which RFlow information is displayed. |
|
Interface |
Identifies the interface that is bound to the specified circuit. |
|
Direction |
Direction of the interface. Can be outgoing (egress), incoming (ingress), or both. |
|
Profile |
Identifies the profile that is currently applied to this circuit. |
Table 21 describes the show flow ip circuit command output for a specific circuit.
|
Field |
Description |
|---|---|
|
Circuit |
Identifies the circuit for which RFlow information is displayed. |
|
Profile applied |
Identifies the profile currently applied to this circuit. |
|
Direction |
Direction of the interface. Can be outgoing (egress), incoming (ingress), or both. |
|
IPPA Statistics |
Displays the current statistics from the iPPA (ingress Packet Processing ASIC) counters. See Table 22 for a description of the IPPA counters. With the exception of the “Flows received by XCRP” and “Flows dropped by XCRP” counters, all counters are maintained on the PPA, which updates the counters once every 5 minutes. The “Flows received by XCRP” and “Flows dropped by XCRP” counters are maintained on the XCRP. As a result, there may be some inconsistencies between the “Flows received by the XCRP” counter and the “Flows aged out of L1 cache” counter if the PPA has not updated the “Flows aged out of L1 cache” counter yet. |
|
EPPA Statistics |
Displays the current statistics from the ePPA (egress Packet Processing ASIC) counters. See Table 23 for a description of the IPPA counters. With the exception of the “Flows received by XCRP” and “Flows dropped by XCRP” counters, all counters are maintained on the PPA, which updates the counters once every 5 minutes. The “Flows received by XCRP” and “Flows dropped by XCRP” counters are maintained on the XCRP. As a result, there may be some inconsistencies between the “Flows received by the XCRP” counter and the “Flows aged out of L1 cache” counter if the PPA has not updated the “Flows aged out of L1 cache” counter yet. |
Table 22 describes the IPPA counters displayed in the show flow ip circuit command.
|
Flows received by XCRP |
Total number of flows received by the XCRP for a given circuit. |
|
Flows dropped by XCRP |
Total number of flows that were dropped by the XCRP due to errors. |
|
Bytes bypassed flow infrastructure |
Bytes bypassed because no resources were available to process flows. |
|
Packets bypassed flow infrastructure |
Total number of packets for which the PPA was unable to create a flow. Use this counter to track packets on a circuit that RFlow is unable to monitor. |
|
Microflows aged out |
Number of microflows that were exported because the inactive or active timeout expired. When a new flow arrives on the PPA, the PPA creates a Flow Control Block (FCB). After the FCB is created, the flow is called a microflow. When a flow is expired (or aged) its corresponding FCB is deleted. The next packet with the same key fields starts a new a new microflow, so a new FCB is created. |
|
Microflows not L1 aggregated— |
Total number of bytes that were not aggregated because the PPA could not add them to the L1 cache. |
|
Bytes not L1 aggregated |
Total number of microflows that were not aggregated because the PPA could not add them to the L1 cache. |
|
Packets not L1 aggregated |
Total number of packets that were not aggregated because the PPA could not add them to the L1 cache. |
|
Flows aged out of L1 cache |
Total number of flows exported (aged) out of the L1 cache because the inactive or active timeout expired. |
|
Flows not reported due to no buffer |
Total number of received flows that the PPA did not report to the XCRP because the XCRP buffer was out of memory. |
|
Bytes aggregated but not reported |
Total number of aggregated bytes that the PPA did not report to the XCRP. |
|
Packets aggregated but not reported |
Total number of aggregated packets that the PPA did not report to the XCRP. |
Table 23 describes the EPPA counters displayed in the show flow ip circuit command.
|
Flows received by XCRP |
Total number of flows received by the XCRP for a given circuit. |
|
Flows dropped by XCRP |
Total number of flows that were dropped by the XCRP due to errors. |
|
Bytes bypassed flow infrastructure |
Total number of bytes for which the PPA was unable to create a flow. Use this counter to track packets on a circuit that RFlow is unable to monitor. |
|
Packets bypassed flow infrastructure |
Total number of packets for which the PPA was unable to create a flow. Use this counter to track packets on a circuit that RFlow is unable to monitor. |
|
Microflows aged out |
Number of Flow Control Blocks (FCBs) that the PPA added to the L1 aggregation cache because the inactive or active timeout expired. When a new flow arrives on the PPA, the PPA creates an FCB. After the FCB is created, the flow is called a microflow. When a flow is expired, its corresponding FCB is deleted. The next packet with the same key fields starts a new microflow and a new FCB. |
|
Microflows not L1 aggregated |
Total number of bytes that were not aggregated because the PPA could not add them to the L1 cache. |
|
Bytes not L1 aggregated |
Total number of microflows that were not aggregated because the PPA could not add them to the L1 cache. |
|
Packets not L1 aggregated |
Total number of packets that were not aggregated because the PPA could not add them to the L1 cache. |
|
Flows aged out of L1 cache |
Total number of flows exported (aged) out of the L1 cache because the inactive or active timeout expired. |
|
Flows not reported due to no buffer |
Total number of received flows that the PPA did not report to the XCRP because the XCRP buffer was out of memory. |
|
Bytes aggregated but not reported |
Total number of aggregated bytes that the PPA did not report to the XCRP. |
|
Packets aggregated but not reported |
Total number of aggregated packets that the PPA did not report to the XCRP. |
The following example shows how to display RFlow information for all circuits in the current context that have RFlow enabled:
[local]Router#show flow ip circuit Circuit Interface Direction Profile ------- --------- --------- ------- 5/5:1023:63/1/2/10 egress both p1
The following example shows how to display RFlow information for the circuit with the handle 5/6:1023:63/1/2/8296
[local]Router#show flow ip circuit 5/6:1023:63/1/2/8296 Circuit : 5/6 vlan-id 50 Profile applied : p1 Direction : both IPPA Statistics: Flows received by XCRP : 10 Flows dropped by XCRP : 0 Bytes bypassed flow infrastructure : 0 Packets bypassed flow infrastructure : 0 Microflows aged out : 10 Microflows not L1 aggregated : 0 Bytes not L1 aggregated : 0 Packets not L1 aggregated : 0 Flows aged out of L1 cache : 10 Flows not reported due to no buffer : 0 Bytes aggregated but not reported : 0 Packets aggregated but not reported : 0 EPPA Statistics: Flows received by XCRP : 10 Flows dropped by XCRP : 0 Bytes bypassed flow infrastructure : 0 Packets bypassed flow infrastructure : 0 Microflows aged out : 10 Microflows not L1 aggregated : 0 Bytes not L1 aggregated : 0 Packets not L1 aggregated : 0 Flows aged out of L1 cache : 10 Flows not reported due to no buffer : 0 Bytes aggregated but not reported : 0 Packets aggregated but not reported : 0
show flow ip log ism [error | rx]
Displays a log of all RFlow events on the SmartEdge router.
All modes
|
ism |
Displays Circuit State Manager (ISM) events only. |
|
error |
Displays error events only. |
|
rx |
Displays only those events received from ISM. |
Enter the show flow ip log command with no optional keywords to display a log of all RFlow events that occurred on the SmartEdge router.
Use the show flow ip log command to display a log of all RFlow events that occurred on the SmartEdge router.
Table 24 describes the show flow ip log command output.
|
Field |
Description |
|---|---|
|
Entry number |
Number that identifies the individual event message. |
|
month day hours:minutes:seconds |
Date and time when the event occurred. |
|
ISM RX rc |
ISM return code. |
|
IPFIX ISM Event: |
Location where the event occurred, and type of event that occurred. |
|
event |
Description of the event that occurred. |
|
cct_handle |
The circuit where the event occurred. |
|
port type |
Type of port on which the event occurred, in hexadecimal format. |
|
state |
Current state of the port where the event occurred. |
|
encaps |
Port encapsulation type, expressed in hexadecimal format. The encaps field is displayed for port configuration events only. |
|
if index |
Interface identifier, expressed in hexadecimal format. The if index field is displayed for port configuration events only. |
The following example shows how to display a log of all RFlow ISM events that have occurred on the router:
[local]Redback #show flow ip log ism
IPFIX<->ISM log messages (20 total entries):
0: Jul 7 22:48:31 ISM RX rc: 0
IPFIX ISM Event: Port Config, event: PRT ethcfg
cct_handle: 5/5:1023:63/1/0/2 port type: 0xa
encaps: 0x1000000 if index: 0x1
1: Jul 7 22:48:31 ISM RX rc: 0
IPFIX ISM Event: Port State, event: PRT up
cct_handle: 5/5:1023:63/1/0/2, state: Unknown
2: Jul 7 22:48:31 ISM RX rc: 0
IPFIX ISM Event: Port Config, event: PRT ethcfg
cct_handle: 5/6:1023:63/1/0/4 port type: 0xa
encaps: 0x1000000 if index: 0x2
3: Jul 7 22:48:31 ISM RX rc: 0
IPFIX ISM Event: Port State, event: PRT up
cct_handle: 5/6:1023:63/1/0/4, state: Unknown
4: Jul 7 22:48:31 ISM RX rc: 0
IPFIX ISM Event: Port Config, event: PRT ethcfg
cct_handle: 5/8:1023:63/1/0/6 port type: 0xa
encaps: 0x1000000 if index: 0x3
5: Jul 7 22:48:31 ISM RX rc: 0
IPFIX ISM Event: Port State, event: PRT up
cct_handle: 5/8:1023:63/1/0/6, state: Unknown
6: Jul 7 22:48:31 ISM RX rc: 0
IPFIX ISM Event: Port Config, event: PRT ethcfg
cct_handle: 7/1:1023:63/1/0/8 port type: 0x10
encaps: 0x1000000 if index: 0x4
7: Jul 7 22:48:31 ISM RX rc: 0
IPFIX ISM Event: Port State, event: PRT up
cct_handle: 7/1:1023:63/1/0/8, state: Unknown
8: Jul 9 00:08:36 ISM RX rc: 0
IPFIX ISM Event: Port State, event: PRT down
cct_handle: 5/5:1023:63/1/0/2, state: DOWN
9: Jul 9 00:08:36 ISM RX rc: 0
IPFIX ISM Event: Port State, event: PRT down
cct_handle: 5/6:1023:63/1/0/4, state: DOWN
10: Jul 9 21:06:20 ISM RX rc: 0
IPFIX ISM Event: Port State, event: PRT down
cct_handle: 5/8:1023:63/1/0/6, state: DOWN
11: Jul 9 21:06:23 ISM RX rc: 0
IPFIX ISM Event: Port State, event: PRT up
cct_handle: 5/8:1023:63/1/0/6, state: Unknown
12: Jul 9 21:44:11 ISM RX rc: 0
IPFIX ISM Event: Port State, event: PRT down
cct_handle: 5/8:1023:63/1/0/6, state: DOWN
13: Jul 9 21:44:14 ISM RX rc: 0
IPFIX ISM Event: Port State, event: PRT up
cct_handle: 5/8:1023:63/1/0/6, state: Unknown
14: Jul 9 21:44:16 ISM RX rc: 0
IPFIX ISM Event: Port State, event: PRT down
cct_handle: 5/8:1023:63/1/0/6, state: DOWN
15: Jul 9 21:44:21 ISM RX rc: 0
IPFIX ISM Event: Port State, event: PRT up
cct_handle: 5/8:1023:63/1/0/6, state: Unknown
16: Jul 9 21:47:36 ISM RX rc: 0
IPFIX ISM Event: Port State, event: PRT down
cct_handle: 5/8:1023:63/1/0/6, state: DOWN
17: Jul 9 21:47:59 ISM RX rc: 0
IPFIX ISM Event: Port State, event: PRT up
cct_handle: 5/8:1023:63/1/0/6, state: Unknown
18: Jul 9 21:48:38 ISM RX rc: 0
IPFIX ISM Event: Port State, event: PRT down
cct_handle: 5/8:1023:63/1/0/6, state: DOWN
19: Jul 9 21:49:19 ISM RX rc: 0
IPFIX ISM Event: Port State, event: PRT up
cct_handle: 5/8:1023:63/1/0/6, state: Unknown
show flow ip profile [profile-name [circuits [all-context] | collectors [all-context]]
Displays information about an RFlow profile.
All modes
|
profile-name |
Identifies the profile for which you want to display information. |
|
circuits |
Displays a list of circuits to which the specified profile is applied. |
|
collectors |
Displays a list of external collectors attached to the specified profile. |
|
all-context |
Displays profile information for all contexts currently configured on the router. If you do not include the all-context keyword, the command output displays profile information for the current context only. |
Enter the command without any of the optional keywords or arguments to display a list of all profiles configured in the current context.
Use the show flow ip profile command to display information related to an RFlow profile.
Table 25 describes the show flow ip profile command output for all profiles.
|
Field |
Description |
|---|---|
|
Profile |
Identifies the RFlow profile for which information is displayed. |
|
Identifier |
RFlow profile identifier in hexadecimal format. The hexadecimal RFlow profile identifier is used for debugging. |
Table 26 describes the show flow ip profile command output for a specific profile.
|
Field |
Description |
|---|---|
|
Profile |
Identifies the RFlow profile for which information is displayed. |
|
Identifier |
RFlow profile identifier in hexadecimal format. The hexadecimal RFlow profile identifier is used for debugging purposes. |
|
Active timeout |
Timeout period, in seconds, after which a flow is considered complete (expired) and a flow record is created and exported to the external collector. Use the active timeout command in flow IP profile configuration mode to configure or modify the active timeout period. |
|
Aggregation cache size |
Number of entries that can be stored in the aggregation cache at one time. The aggregation cache size determines how much information is reported when you access the RFlow data. Use the aggregation-cache-size command in flow IP profile configuration mode to configure or modify the size of the aggregation cache. |
The following example shows how to display a lists of all profiles configured in the current context:
[local]Redback #show flow ip profile Identifier Profile ----------- ------- 0x40800001 p1
The following example shows how to display information about a specific profile called p1:
[local]Redback #show flow ip profile p1 Profile : p1 Identifier : 0x40800001 Active timeout : 1800 Aggregation cache size : 4096
show flow log
Displays the log of all flow events on the current SmartEdge router.
All modes
None
Use the show flow log command to display the log of all flow events on the current SmartEdge router.
The following example shows how to display the log of flow events on the current SmartEdge router:
[local]Redback(config)#show flow log Time Evnt SubEvent Circuit Details ---- ---------------------------------------------- 264.99 Proc Create-thread cmd 264.31 Proc Create-thread ppa-rx 264.33 Proc Create-thread ism-rx 264.33 Proc Endpoint-alive ism-mbe 264.34 ISM FSM-Event MBE-EP-Up 264.34 ISM FSM-New-State MBE-EP-up (All-EP-down)
show flow ppa log circuit circuit_name {continuous | duration duration}
Displays statistics associated with the pull value of the current PPA log for a specified circuit.
Global configuration
|
circuit_name |
Name of the circuit for which you are displaying PPA log information. |
|
continuous |
Specifies the amount of time for which PPA log information is being displayed is ongoing. |
|
duration duration |
Time interval in seconds for which PPA log information is being displayed |
None
Use the show flow ppa log circuit to display statistics associated with the pull value of the current PPA log for a specified circuit.
The following example shows how to display statistics associated with the pull value of the current PPA log for the circuit1 circuit:
[local]Redback(config-ctx)#show flow ppa log 1/1:1023:63/1/2/6 circuit1
show flow ppa state
Displays Packet Processing ASIC (PPA) communications state information for all flows on the current SmartEdge router.
All modes
This command has no keywords or arguments.
None
Use the show flow ppa state command to display PPA communications state information for all flows on the current SmartEdge router.
The following example shows how to display PPA communication state information for the current circuit:
[local]Redback(config)#show flow ppa state S:P EP Name Index PR ES EU SE -------------------------------------------------------- 1:I FLOW SLOT 01/0 0000005 Y Y Y Y 1:E FLOW SLOT 01/1 0000004 Y Y Y Y
show flow ppa circuit circuit summary
Displays a summary of flow counters for a specified circuit.
Global configuration
|
circuit circuit |
Circuit to which the FAC profile is applied. |
None
Use the show flow ppa circuit summary to display a summary of flow counters for a specified circuit.
The following example shows how to display a summary of flow counters for the circuit1 circuit:
[local]Redback(config-ctx)#show flow ppa circuit 1/1:1023:63/1/2/6 summary
show forward policy pol-name
Displays information about configured forward policies.
All modes
|
pol-name |
Forward policy name. |
None
Use the show forward policy command to display information about configured forward policies.
The following example displays brief information about the redirect_policy forward policy:
[local]Redback>show forward policy redirect_policy
Policy-Name Type Grid Qs Slots Ports Bound DnLd Status redirect_policy forward 3 0 2 42 in/out Total policy map: 1
The following example displays detailed information for the multi_policy forward policy:
[local]Redback>show forward policy multi_policy
Policy-Name Type Grid Qs Slots Ports Bound DnLd Status multi_policy forward 1 0 1 1 in Slot#: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 iPPA dnld: ePPA dnld: iPPA ports: 1 ePPA ports: Class-Name Action Mode IP-Address Bound Int,msec Output-Name redir1 redir hop 10.3.50.2 default redir2 redir local Total policy map: 1
The following example displays detailed information about the l2_policy forward policy configured with the mirror destination dest-name l2-frames command for mirroring Layer 2 attachment circuits:
[local]Redback>show forward policy l2_policy
Policy-Name Type Grid Qs Slots Ports Bound DnLd Status
l2_policy forward 1 0 0 0 updt
Slot#: 1 2 3 4 5 6 7 8 9 10 11 12 13 14
iPPA dnld:
ePPA dnld:
iPPA ports:
ePPA ports:
Class-Name Action Mode IP-Addr/Option Bound Int,msec Output-Name
default mirror forw l2-frames no 20000 you_bar
Total policy map: 1 [local]Redback#
For ports on channelized OC-12 or STM-1 line cards, the syntax is:
show frame-relay [slot/port[:chan-num[:sub-chan-num]] [dlci dlci]] [detail]
For channelized ports on DS-3 or E1 line cards, the syntax is:
show frame-relay [slot/port[:chan-num] [dlci dlci]] [detail]
For clear-channel ports on DS-3, E3, or E1 line cards, or ports on Packet over SONET/SDH (POS) line cards, the syntax is:
show frame-relay [slot/port [dlci dlci]] [detail]
Displays configuration information for configured Frame Relay permanent virtual circuits (PVCs).
All modes
|
slot |
Optional. Chassis slot number of a line card for which circuit information is displayed. If omitted, displays circuit information for all circuits in the system. |
|
port |
Required if you enter the slot argument. Port number for which circuit information is displayed. |
|
chan-num |
Optional. Channel number for which circuit information is displayed. If omitted, displays circuit information for all channels on the specified port. The range of values depends on the type of port; see Table 27 for the range of values. |
|
sub-chan-num |
Optional. Subchannel number for which circuit information is displayed. If omitted, displays circuit information for all subchannels in the specified channel. The range of values depends on the type of port; see Table 27 for the range of values. |
|
dlci dlci |
Optional. Data-link connection identifier (DLCI) of the configured PVC. The range of values is 16 to 991. |
|
detail |
Optional. Displays detailed circuit information. |
Displays configuration information for all configured Frame Relay PVCs.
Use the show frame-relay command to display configuration information for configured Frame Relay PVCs.
Table 27 lists the range of values for the chan-num and sub-chan-num arguments for various types of channelized ports.
|
Port |
Channel Types |
chan-num Range |
sub-chan-num Range |
|---|---|---|---|
|
Channelized OC-12 |
DS-3, DS-1 |
1 to 12 |
1 to 28 |
|
Channelized STM-1 |
E1, DS-0 channel group |
1 to 63 |
1 to 31 |
|
Channelized DS-3 |
DS-1 |
1 to 28 |
– |
|
Channelized E1 |
DS-0 channel group |
1 to 31 |
– |
If you enter the optional slot, port, and chan-num arguments, the command displays configuration information for the specified card, port, or channel; if you enter the optional sub-chan-num argument, the command displays configuration information for the DS-1 channel or DS-0 channel group.
If you enter the optional dlci dlci construct, the output displays configuration information for the specified circuit.
The following example shows how to display detailed configuration information for all Frame Relay PVCs:
[local]Redback>show frame-relay detail
Circuit: 1/1:1:1, internal id: 3/1/6, state: Up ---------------------------------------------------------- bound to : admin state : Down hardware address : 00:00:00:00:00:00 media type : sonet encap type : frame-relay mode type : 0x2 port type : ds1 mtu size : 1500 cct speed : 0 if_flags : 0x0 version : 14366 internal handle : 1/1:1:1/3/1/6 Circuit: 1/1:1:1, internal id: 6/2/7, state: Up ---------------------------------------------------------- bound to : admin state : Down hardware address : 00:00:00:00:00:00 media type : sonet encap type : frame-relay mode type : 0x2 port type : ds1 mtu size : 1500 cct speed : 1536 if_flags : 0x0 version : 15139 internal handle : 1/1:1:1/6/2/7 Circuit: 1/1:1:1 dlci 1023, internal id: 6/2/8, state: Up ---------------------------------------------------------- bound to : admin state : Down hardware address : 00:00:00:00:00:00 media type : sonet encap type : frame-relay mode type : 0x2 port type : ds1 mtu size : 1500 cct speed : 1536 if_flags : 0x0 version : 15140 internal handle : 1/1:1:1/6/2/8 Circuit: 1/1:1:1 dlci 20, internal id: 6/2/9, state: Up ---------------------------------------------------------- bound to : 1.1.dlci20@local admin state : Down hardware address : 00:00:00:00:00:00 media type : sonet encap type : frame-relay mode type : 0x2 port type : ds1 mtu size : 1500 cct speed : 1536 version : 15141 internal handle : 1/1:1:1/6/2/9 . .
For ports on channelized OC-12 or STM-1 line cards, the syntax is:
show frame-relay counters [persistent] [slot/port[:chan-num[:sub-chan-num]] [dlci dlci ]] [detail]
For channelized ports on DS-3 or E1 line cards, the syntax is:
show frame-relay counters [persistent] [slot/port[:chan-num] [dlci dlci ]] [detail]
For clear-channel ports on DS-3, E3, or E1 line cards or ports on Packet over SONET/SDH (POS) line cards, the syntax is:
show frame-relay counters [persistent] [slot/port [dlci dlci ]] [detail]
Displays traffic counters for configured Frame Relay permanent virtual circuits (PVCs).
All modes
|
persistent |
Optional. If omitted, displays values since the counters were last cleared or the card was last reloaded. If specified, displays values since the system was last reloaded. |
|
slot |
Optional. Chassis slot number of a line card with the port for which traffic counters are displayed. |
|
port |
Required if you enter the slot argument. Port number for the port for which traffic counters are displayed. |
|
chan-num |
Optional. Channel for which traffic counters are displayed. The range of values depends on the type of port; see Table 28 for the range of values. |
|
sub-chan-num |
Optional. Subchannel number for which the traffic counters are displayed. If not specified, displays traffic counters for all subchannels in the specified channel. The range of values depends on the type of port; see Table 28 for the range of values. |
|
dlci dlci |
Optional. Data-link connection identifier (DLCI) of a configured Frame Relay PVC for which to display traffic counters. The range of values is 16 to 991. |
|
detail |
Optional. Specifies that more details are displayed for each Frame Relay PVC. |
Displays the traffic counters for all Frame Relay PVCs that are bound in the current context.
Table 28 lists the range of values for the chan-num and sub-chan-num arguments for various types of channelized ports.
|
Port |
Channel Types |
chan-num Range |
sub-chan-num Range |
|---|---|---|---|
|
Channelized OC-12 |
DS-3, DS-1 |
1 to 12 |
1 to 28 |
|
Channelized STM-1 |
E1, DS-0 channel group |
1 to 63 |
1 to 31 |
|
Channelized DS-3 |
DS-1 |
1 to 28 |
– |
|
Channelized E1 |
DS-0 channel group |
1 to 31 |
– |
To display the counters with values accumulated since the system was last reloaded, issue the show frame-relay counters command with the persistent keyword.
The show frame-relay counters command is an alias for the show circuit counters fr command in exec mode.
Use the slot and port arguments to display only Frame Relay PVCs configured on the card in that slot or on that port; if not specified, Frame Relay traffic counters are displayed for all ports in all slots in the system.
If the port is on a channelized OC-12 line card, use the chan-num argument to display the traffic counters for only that DS-3 channel; use the sub-chan-num argument to display the traffic counters for only that DS-1 channel or DS-0 channel group. Otherwise, the traffic counters for all Frame Relay PVCs on that slot and port are displayed.
Use the dlci dlci construct to display traffic counters for only a single Frame Relay PVC.
Use the detail keyword to display detailed output for each specified slot, port, channel, or Frame Relay PVC; otherwise, the output displays one line of output for each specified slot, port, channel, or Frame Relay PVC.
The following example shows how to display the traffic counters for the Frame Relay-encapsulated PVCs on POS port 2 in slot 6:
[local]Redback>show frame-relay counters 6/2
Circuit Packets/Bytes Sent Packets/Bytes Received
6/2 0 0
0 0
6/2 0 0
0 0
6/2 dlci 1023 0 0
0 0
6/2 dlci 16 0 0
0 0
For ports on channelized OC-12 or STM-1 line cards, the syntax is:
show frame-relay lmi-config [slot[/port[:chan-num[:sub-chan-num]]]]
For channelized ports on DS-3 or E1 line cards, the syntax is:
show frame-relay lmi-config [slot[/port[:chan-num]]]
For clear-channel ports on DS-3, E3, or E1 line cards, or ports on Packet over SONET/SDH (POS) line cards, the syntax is:
show frame-relay lmi-config [slot[/port]]
Displays Frame Relay Local Management Interface (LMI) configuration information.
All modes
|
slot |
Optional. Chassis slot number of a line card with the port for which the LMI configuration displays. If not specified, LMI configuration data displays for all Frame Relay-encapsulated ports in all slots. |
|
port |
Optional. Port number of the port for which the LMI configuration displays. If not specified, LMI configuration data displays for all Frame Relay-encapsulated ports on the card in the specified slot. |
|
chan-num |
Optional. Channel for which the LMI configuration displays. If not specified, displays LMI configuration data for all channels on the specified port. The range of values depends on the type of port; see Table 29 for the range of values. |
|
sub-chan-num |
Optional. Subchannel number for which LMI configuration data displays. If not specified, displays LMI configuration data for all subchannels in the specified channel. The range of values depends on the type of port; see Table 29 for the range of values. |
Displays the LMI configuration information for all configured Frame Relay-encapsulated ports or channels in all slots.
Use the show frame-relay lmi-config command to display LMI configuration information.
Table 29 lists the range of values for the chan-num and sub-chan-num arguments for various types of channelized ports.
|
Port |
Channel Types |
chan-num Range |
sub-chan-num Range |
|---|---|---|---|
|
Channelized OC-12 |
DS-3, DS-1 |
1 to 12 |
1 to 28 |
|
Channelized STM-1 |
E1, DS-0 channel group |
1 to 63 |
1 to 31 |
|
Channelized DS-3 |
DS-1 |
1 to 28 |
– |
|
Channelized E1 |
DS-0 channel group |
1 to 31 |
– |
If you specify the slot and port arguments, the display shows the configuration for just that port; if you specify the chan-num argument, the display shows the configuration for just that channel; if you specify the sub-chan-num argument, the display shows the configuration for just that subchannel.
The following example shows how to display the configuration for DS-3 channel 1 on channelized OC-12 port 1 in slot 3:
[local]Redback>show frame-relay lmi-config 3/1:1
Keep --------DCE-------- -- DTE --
Slot/Port Dlci Link Type State Alive T392 N391 N392 N393 N392 N393
------------ ---- ---- ---- ----- ----- ---- ---- ---- ---- ---- ----
3/1:1 1023 dte g4 up 10 15 6 3 4 3 4
For ports on channelized OC-12 or STM-1 line cards, the syntax is:
show frame-relay lmi-errors [bootup] [full] [slot[/port[:chan-num[:sub-chan-num]]]]
For channelized ports on DS-3 or E1 line cards, the syntax is:
show frame-relay lmi-errors [bootup] [full] [slot[/port[:chan-num]]]
For clear-channel ports on DS-3, E3, and E1 line cards, or ports on Packet over SONET/SDH (POS) line cards, the syntax is:
show frame-relay lmi-errors [bootup] [full] [slot[/port]]
Displays Frame Relay Local Management Interface (LMI) error counters.
All modes
|
bootup |
Optional. Displays LMI error counters accumulated since the time the system was last reloaded. If not specified, the LMI error counters are accumulated since the last time the show frame-relay lmi-errors command was issued. |
|
full |
Optional. Displays LMI error counters for all LMIs. |
|
slot |
Optional. Chassis slot number of a line card for which LMI error counters are displayed. If not specified, displays LMI error counters for all Frame Relay ports in all slots. |
|
port |
Optional. Port number for which LMI error counters are displayed. If not specified, displays LMI error counters for all Frame Relay ports in the specified slot. |
|
chan-num |
Optional. Channel number for which LMI error counters are displayed. If not specified, displays LMI error counters for all channels on the specified port. The range of values depends on the type of port; see Table 30 for the range of values. |
|
sub-chan-num |
Optional. Subchannel number for which LMI error counters are displayed. If not specified, displays LMI error counters for all subchannels in the specified channel. The range of values depends on the type of port; see Table 30 for the range of values. |
Displays LMI error counters for all configured Frame Relay encapsulated channels or ports in all slots since the last time the system was reloaded (booted).
Use the show frame-relay lmi-errors to display LMI error counters.
Table 30 lists the range of values for the chan-num and sub-chan-num arguments for various types of channelized ports.
|
Port |
Channel Types |
chan-num Range |
sub-chan-num Range |
|---|---|---|---|
|
Channelized OC-12 |
DS-3, DS-1 |
1 to 12 |
1 to 28 |
|
Channelized STM-1 |
E1, DS-0 channel group |
1 to 63 |
1 to 31 |
|
Channelized DS-3 |
DS-1 |
1 to 28 |
– |
|
Channelized E1 |
DS-0 channel group |
1 to 31 |
– |
If you specify the slot and port arguments, only the LMI error counters for that slot or port are displayed; if you specify the chan-num argument, the display shows the LMI error counters for just that channel; if you specify the sub-chan-num argument, the display shows the LMI error counters for just that subchannel.
The system maintains the following sets of error counters for each LMI interface: general errors that apply regardless of the LMI interface type, error counters that only apply to the DCE interface, and error counters that only apply to the data terminal equipment (DTE) interface.
When the error counters are displayed, the general errors are always shown. Then normally the error counters for only the configured LMI interface type are displayed. For example, if port is configured with a Frame Relay interface type of DTE, only the DTE error counters are displayed. Both the DTE and DCE error counters are displayed if you specify the full keyword.
The following example shows how to display the LMI error counters for DS-3 channel 11 on channelized OC-12 port 1 that is configured as a DTE interface:
[local]Redback>show frame-relay lmi-errors 3/1:11
3/1:11 General errors since Wed Aug 29 21:47:03 2002 Last cleared: never Header errors: 0 Unknown Messages: 0 Invalid Unnumbered frame: 0 Frame too big: 0 Status rcvd for unkn pvc: 0 Too Many Status Enq: 0 Unexpected PVC Stat IE: 0 Too Few Stat Enq: 0 No response to Stat Enq: 3 3/1:11 DTE LMI errors Q.922 Header errors: 0 Protocol errors: 0 Unknown Messages: 0 Info Element missing: 0 KeepAlive IE Missing: 0 KeepAlive Seq errors: 0 Unknown IE errors: 0 Positive Threshold Events: 0 Total Negative Events: 0 Current Threshold state: Normal
For ports on channelized OC-12 or STM-1 line cards, the syntax is:
show frame-relay lmi-stats [bootup] [slot[/port[:chan-num[:sub-chan-num]]]]
For channelized ports on DS-3 or E1 line cards, the syntax is:
show frame-relay lmi-stats [bootup] [slot[/port[:chan-num]]]
For clear-channel ports on DS-3, E3, or E1 line cards, or ports on Packet over SONET/SDH (POS) line cards, the syntax is:
show frame-relay lmi-stats [bootup] [slot[/port]]
Displays Frame Relay Local Management Interface (LMI) statistics counters.
All modes
|
bootup |
Optional. Displays LMI statistics counters accumulated since the time the system was last reloaded. If not specified, the LMI statistics counters are accumulated since the last time the show frame-relay lmi-stats command was issued. |
|
slot |
Optional. Chassis slot number of a line card for which LMI statistics counters are displayed. If not specified, displays LMI statistics counters for all configured Frame Relay encapsulated ports in all slots. |
|
port |
Optional. Port number of the port for which LMI statistics counters are displayed. If not specified, displays LMI statistics counters for all Frame Relay encapsulated ports in the specified slot. |
|
chan-num |
Optional. Channel number for which LMI statistics counters are displayed. If not specified, displays LMI statistics counters for all channels on the specified port. The range of values depends on the type of port; see Table 31 for the range of values. |
|
sub-chan-num |
Optional. Subchannel number for which LMI statistics counters are displayed. If not specified, displays LMI statistics counters for all subchannels in the specified channel. The range of values depends on the type of port; see Table 31 for the range of values. |
Displays LMI statistics counters for all configured Frame Relay channels on all ports in all slots since the last time the system was reloaded (booted).
Use the show frame-relay lmi-stats command to display LMI statistics counters.
Table 31 lists the range of values for the chan-num and sub-chan-num arguments for various types of channelized ports.
|
Port |
Channel Types |
chan-num Range |
sub-chan-num Range |
|---|---|---|---|
|
Channelized OC-12 |
DS-3, DS-1 |
1 to 12 |
1 to 28 |
|
Channelized STM-1 |
E1, DS-0 channel group |
1 to 63 |
1 to 31 |
|
Channelized DS-3 |
DS-1 |
1 to 28 |
– |
|
Channelized E1 |
DS-0 channel group |
1 to 31 |
– |
If you specify the slot and port arguments, the LMI statistics for that slot or port are displayed; if you specify the chan-num argument, the display shows the statistics for just that channel; if you specify the sub-chan-num argument, the display shows the statistics for just that subchannel.
The following example shows how to display LMI statistics counters for DS-3 channel 11 on channelized OC-12 port 1:
[local]Redback>show frame-relay lmi-stats 3/1:11
3/1:11 LMI stats since Wed Aug 29 21:45:18 2002
Last cleared: never
status enquires sent: 563 status enquires rcvd: 0
full status enqs sent: 94 full status enqs rcvd: 0
status messages sent: 0 status messages rcvd: 560
full status msgs sent: 0 full status msgs rcvd: 94
async updates rcvd: 0
show frame-relay profile [prof-name]
Displays information about Frame Relay profiles configured in the current context.
All modes
|
prof-name |
Optional. Name of the configured Frame Relay profile. |
When used without the optional argument, displays a brief description of all configured Frame Relay profiles.
Use the show frame-relay profile command to display information about Frame Relay profiles configured in the current context.
The following example shows how to display information about all Frame Relay profiles configured in the local context:
[local]Redback>show frame-relay profile
Name Counters PVCs ------------------ --------------- ---- fr-pro none 1 Total: 1
For ports on channelized OC-12 or STM-1 line cards, the syntax is:
show frame-relay pvc [all | active | inactive | l2vpn | summary] [slot[/port[:chan-num[:sub-chan-num]] [dlci dlci]]]
For channelized ports on DS-3 or E1 line cards, the syntax is:
show frame-relay pvc [all | active | inactive | l2vpn | summary] [slot[/port[:chan-num] [dlci dlci]]]
For clear-channel ports on DS-3, E3, or E1 line cards, or ports on Packet over SONET/SDH (POS) line cards, the syntax is:
show frame-relay pvc [all | active | inactive | l2vpn | summary] [slot[/port [dlci dlci]]
Displays a list of configured Frame Relay permanent virtual circuits (PVCs).
All modes
|
all |
Optional. Displays information for all configured Frame Relay PVCs in all contexts. This option is valid only in the local context. |
|
active |
Optional. Displays only active Frame Relay PVCs. |
|
inactive |
Optional. Displays only Frame Relay PVCs in the Down state. |
|
l2vpn |
Optional. Displays only Frame Relay PVCs that are enabled for Layer 2 Virtual Private Networks (L2VPNs). |
|
summary |
Optional. Displays only a summary of bound and unbound Frame Relay PVCs. |
|
slot |
Optional. Chassis slot number of a line card with the port for which Frame Relay PVCs are displayed. If not specified, displays PVCs that are bound in the current context for all configured Frame Relay PVCs in all slots. |
|
port |
Optional. Port number of the port for which PVCs are displayed. If not specified, displays Frame Relay PVCs for all ports in the specified slot. |
|
chan-num |
Optional. Channel number for which Frame Relay PVCs are displayed. If not specified, displays Frame Relay PVCs for all channels on the specified port. The range of values depends on the type of port; see Table 32 for the range of values. |
|
sub-chan-num |
Optional. Subchannel number for which the Frame Relay PVCs are displayed. If not specified, displays Frame Relay PVCs for all subchannels in the specified channel. The range of values depends on the type of port; see Table 32 for the range of values. |
|
dlci dlci |
Optional. Data-link connection identifier (DLCI) of the configured Frame Relay PVC. The range of values is 16 to 991. If not specified, displays Frame Relay PVCs for all DLCIs as specified by the slot, port, chan-num, and sub-chan-num arguments. |
Displays all configured Frame Relay PVCs that are bound in the current context.
Use the show frame-relay pvc command to display a list of configured Frame Relay PVCs.
Table 32 lists the range of values for the chan-num and sub-chan-num arguments for various types of channelized ports.
|
Port |
Channel Types |
chan-num Range |
sub-chan-num Range |
|---|---|---|---|
|
Channelized OC-12 |
DS-3, DS-1 |
1 to 12 |
1 to 28 |
|
Channelized STM-1 |
E1, DS-0 channel group |
1 to 63 |
1 to 31 |
|
Channelized DS-3 |
DS-1 |
1 to 28 |
– |
|
Channelized E1 |
DS-0 channel group |
1 to 31 |
– |
In the local context, use the all keyword to display information about all configured Frame Relay PVCs, both bound (in any context) and unbound. This keyword is valid only in the local context. For any other context, only the Frame Relay PVCs that are bound within the current context are displayed.
Use the active keyword to display only the active Frame Relay PVCs; use the inactive keyword to display only the inactive PVCs.
Use the l2vpn keyword to display all Frame Relay PVCs that are enabled for L2VPN. Output for the option displays three states for each PVC:
Use the summary keyword to display only summary information.
Use the slot and port arguments to display only PVCs for that slot or that port. If the port is on a channelized OC-12 line card or STM-1 line card, use the chan-num argument to display only the PVCs on that channel; use the sub-chan-num argument to display only the PVCs on that DS-1 channel or DS-0 channel group; otherwise, the PVCs on all channels on the port are displayed.
Use the dlci dlci construct to display only the Frame Relay PVC with that DLCI.
The following example shows how to display output for all active Frame Relay PVCs:
[local]Redback>show frame-relay pvc active
Slot/Port Traffic Profile State Encaps Binding 3/1:1 dlci 16 fr-pro up auto1490 1.dlci16@local 3/1:1 dlci 17 fr-pro up auto1490 1.dlci17@local 3/1:1 dlci 18 fr-pro up auto1490 1.dlci18@local 3/1:1 dlci 19 fr-pro up auto1490 1.dlci19@local 3/1:1 dlci 20 fr-pro up auto1490 1.dlci20@local 3/1:1 dlci 21 fr-pro up auto1490 1.dlci21@local 3/1:1 dlci 22 fr-pro up auto1490 1.dlci22@local 3/1:1 dlci 23 fr-pro up auto1490 1.dlci23@local .... Total: 1212 Up: 1212 Down: 0 Shut: 0 Bound: 1212 last status change: Thu Sep 26 01:51:26 2002
The following example shows how to display output for L2VPN-enabled PVCs:
[local]Redback>show frame-relay pvc l2vpn
Circuit Local State L2VPN state State 12/1 dlci 100 up down down 12/1 dlci 101 up down down 12/1 dlci 102 up down down 12/1 dlci 103 up down down 12/1 dlci 104 up down down 12/1 dlci 105 up down down 12/1 dlci 106 up down down 12/1 dlci 107 up down down 12/1 dlci 108 up down down 12/1 dlci 109 up down down 12/1 dlci 110 up down down 12/1 dlci 111 up down down 12/1 dlci 112 up down down 12/1 dlci 113 up down down 12/1 dlci 114 up down down 12/1 dlci 115 up down down
The following example shows how to display summary information:
[local]Redback>show frame-relay pvc summary
PVCs total: 1212 Up: 1212 Down: 0 Shut: 0 Bound : 1212 last status change: Thu Sep 26 01:51:26 2002
The following example shows how to display information for the Frame Relay PVC associated with slot 1 port 1, channel 1, DLCI 16 on a channelized OC-12 line card:
[local]Redback>show frame-relay pvc 1/1:1 DLCI 16
Slot/Port/Channel: 1/1:1 DLCI: 16 status: up bound to 1.dlci16@local