Interface Commands
This chapter is a reference for each of the interface commands.
admin-group
Use this command to create an administrative group to be used for links. Each link can be a member of one or more, or no administrative groups.
When used in the interface mode, this command adds a link between an interface and a group. The name is the name of the group previously configured. There can be multiple groups per interface. The group is created in configure mode, then interfaces are added to the group in interface mode.
Use the no parameter with this command to disable this command.
Command Syntax
admin-group NAME
no admin-group NAME
Parameters
NAME
Name of the admin group to add.
Default
No default value is specified
Command Mode
Interface mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
In the following example, the eth3 interface is added to the group myGroup:
#configure terminal
(config)#interface eth3
(config-if)#admin-group myGroup
bandwidth
Use this command to specify a discrete, maximum bandwidth value for the interface.
Use the no parameter resets the interface’s bandwidth to the default value.
Command Syntax
bandwidth BANDWIDTH
no bandwidth
Parameter
BANDWIDTH
<1-999>k for 1 to 999 kilobits/s
<1-999>m for 1 to 999 megabits/s
<1-100>g for 1 to 100 gigabits/s
Default
Default bandwidth will be default speed of the interface. For LAG, default bandwidth will be collective bandwidth of its member ports. For VLAN interface, default bandwidth is 1 gigabits/sec.
Command Mode
Interface mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
#configure terminal
(config)#interface xe4
(config-if)#bandwidth 100m
bandwidth-measurement static uni-available-bandwidth
Use this command to advertise the available bandwidth between two directly connected OSPF/ISIS neighbors.
Use the no parameter with this command to unset available bandwidth on the current interface.
Command Syntax
bandwidth-measurement static uni-available-bandwidth BANDWIDTH
no bandwidth-measurement static uni-available-bandwidth
Parameter
BANDWIDTH
<0-999>k for 0 to 999 kilo bits/s
<0-999>m for 0 to 999 mega bits/s
<0-100>g for 0 to 100 giga bits/s
Command Mode
Interface mode
Applicability
This command was introduced in OcNOS-SP version 5.0.
Examples
(config)#int eth2
(config-if)#bandwidth-measurement static uni-available-bandwidth 10k
(config-if)#commit
(config)#int eth2
(config-if)#no bandwidth-measurement static uni-available-bandwidth
(config-if)#commit
bandwidth-measurement static uni-residual-bandwidth
Use this command to advertise the residual bandwidth between two directly connected OSPF/ISIS neighbors.
Use the no parameter with this command to unset residual bandwidth on the current interface.
Command Syntax
bandwidth-measurement static uni-residual-bandwidth BANDWIDTH
no bandwidth-measurement static uni-residual-bandwidth
Parameter
BANDWIDTH
<0-999>k for 0 to 999 kilo bits/s
<0-999>m for 0 to 999 mega bits/s
<0-100>g for 0 to 100 giga bits/s
Command Mode
Interface mode
Applicability
This command was introduced in OcNOS-SP version 5.0.
Examples
(config)#interface ethernet 2
(config-if)#bandwidth-measurement static uni-residual-bandwidth 10g
(config-if)#commit
(config)#interface ethernet 2
(config-if)#no bandwidth-measurement static uni-residual-bandwidth
(config-if)#commit
bandwidth-measurement static uni-utilized-bandwidth
Use this command to advertise the utilized bandwidth between two directly connected OSPF/ISIS neighbors.
Use the no parameter with this command to unset utilized bandwidth on the current interface.
Command Syntax
bandwidth-measurement static uni-utilized-bandwidth BANDWIDTH
no bandwidth-measurement static uni-utilized-bandwidth
Parameter
BANDWIDTH
<0-999>k for 0 to 999 kilo bits/s
<0-999>m for 0 to 999 mega bits/s
<0-100>g for 0 to 100 giga bits/s
Command Mode
Interface mode
Applicability
This command was introduced in OcNOS-SP version 5.0.
Examples
(config)#int eth2
(config-if)#bandwidth-measurement static uni-utilized-bandwidth 10m
(config-if)#commit
(config)#int eth2
(config-if)#no bandwidth-measurement static uni-utilized-bandwidth
(config-if)#commit
clear hardware-discard-counters
Use this command to clear device level discard counters.
Command Syntax
clear hardware-discard-counters
Parameters
None
Command Mode
Exec mode
Applicability
The command is introduced before OcNOS version 1.3.
Examples
#clear hardware-discard-counters
clear interface counters
Use this command to clear the statistics on a specified interface or on all interfaces.
Note: This command is not supported on loopback interfaces or the out-of-band management (OOB) management interface.
Command Syntax
clear interface (IFNAME|) counters
Parameter
IFNAME
Interface name.
Command Mode
Exec mode and Privileged Exec mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
#clear interface xe0 counters
clear interface cpu counters
Use this command to clear the CPU queue counters.
Command Syntax
clear interface cpu counters
Parameter
None
Command Mode
Exec mode and Privileged Exec mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
#clear interface cpu counters
clear interface fec
Use this command to clear FEC (forward error correction) statistics on a specified interface or on all interfaces.
Note: This command is not supported on loop-back interfaces or the out-of-band (OOB) management interface.
Command Syntax
clear interface (IFNAME|) fec
Parameters
IFNAME
Physical Interface name.
Default
None
Command Mode
Exec mode and Privileged exec mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
#clear interface ce1/1 fec
clear ip prefix-list
Use this command to reset the hit count to zero in the prefix-list entries for an IPv4 interface.
Command Syntax
clear ip prefix-list
clear ip prefix-list WORD
clear ip prefix-list WORD A.B.C.D/M
Parameters
WORD
Name of the prefix-list.
A.B.C.D/M
IP prefix and length.
Command Mode
Exec mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
#clear ip prefix-list List1
clear ipv6 neighbors
Use this command to clear all dynamic IPv6 neighbor entries.
Command Syntax
clear ipv6 neighbors
Parameters
None
Command Mode
Privileged Exec mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
#clear ipv6 neighbors
clear ipv6 prefix-list
Use this command to reset the hit count to zero in the prefix-list entries for an IPv6 interface.
Command Syntax
clear ipv6 prefix-list
clear ipv6 prefix-list WORD
clear ipv6 prefix-list WORD X:X::X:X/M
Parameters
WORD
Name of the prefix-list.
X:X::X:X/M
IP prefix and length.
Command Mode
Privileged Exec mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
#clear ipv6 prefix-list List1
debounce-time
Use this command to set the debounce time for a interface.
The debounce timer avoids frequent updates (churn) to higher layer protocol during interface flapping. If the status of a link changes quickly from up to down and then back to up, the port debounce timer suppresses the link status notification. If the link transitions from up to down, but does not come back up, the port debounce timer delays the link status notification.
Note: Keep the following in mind when using the debounce timer:
• Debounce is not applicable for admin down operations.
• Debounce timer is supported only for physical L2 and L3 interfaces.
• The debounce flap-count refers to the number of flaps OcNOS receives while the debounce timer is running:
• The flap-count is only updated if the timer is still running and OcNOS receives a link status event for the interface.
• The flap-count is reset at the subsequent start of the debounce timer.
• Protocol-specific timers such as BFD which depend on the link status should be configured to a minimum of 1.5 times the value of the debounce timer. Otherwise it could affect the protocol states if the debounce timer is still running.
Use the no form of this command to turn-off the debounce timer on a interface.
Command Syntax
debounce-time <250-5000>
no debounce-time
Parameters
<250-5000>
Timer value in milliseconds.
Default
By default, disabled.
Command Mode
Interface mode
Applicability
This command was introduced in OcNOS version 1.3.8.
Example
#configure terminal
(config)#interface eth1
(config-if)#debounce-time 4000
delay-measurement dynamic twamp
This command will start the measurement on the interface by using the "interfaces" profile.
The user should be aware that the IP used as a reflector IP must be a directly connected IP.
In case hostname needs to be used, the user must be sure about the hostnames configured in the network.
In case the user configures the delay-measurement with a certain hostname and then the hostname entry in the DNS changes, the delay-measurement must be unconfigured and configured again for the new configuration to take effect (a clear command would not be sufficient in this situation)
Use the no form of this command to stop the delay measurement.
Command Syntax
delay-measurement dynamic twamp reflector-ip (HOSTNAME | X:X::X:X | A.B.C.D) (reflector-port <1025-65535>|) (sender-ip (HOSTNAME | X:X::X:X | A.B.C.D)|) (dscp WORD|)
no delay-measurement dynamic twamp reflector-ip (HOSTNAME | X:X::X:X | A.B.C.D)
Parameters
twamp
This parameter specifies the protocol to be used to do the measurement. It is the only protocol available in this implementation. The subsequent parameters in this command are specific to the protocol chosen (TWAMP).
reflector-ip
Specify the reflector ip/hostname used to send the TWAMP packets to
HOSTNAME
The hostname of the reflector
X:X::X:X
The ip address of the reflector
A.B.C.D
The ip address of the reflector
reflector-port
specify the UDP port of the TWAMP reflector
<1025-65535>
The reflector port value
sender-ip
Specify the IP used to send the TWAMP packets from (must be an IP configured on the current interface)
HOSTNAME
The hostname of the reflector
X:X::X:X
The ip address of the reflector
A.B.C.D
The ip address of the reflector
dscp
Specify the dscp value used during this measurement
WORD
The dscp value
Command Mode
Interface mode
Applicability
This command was introduced in OcNOS version 5.1.
Example
OcNOS(config)#
OcNOS(config)#interface xe7
OcNOS(config-if)#delay-measurement dynamic twamp reflector-ip 23.1.1.2 sender-ip 23.1.1.1 dscp 24
OcNOS(config-if)#commit
OcNOS(config-if)#no delay-measurement dynamic twamp reflector-ip 23.1.1.2
OcNOS(config-if)#commit
delay-measurement a-bit-min-max-delay-threshold
Use this command to advertise the minimum and maximum delay values between two directly connected IS-IS/OSPF neighbors.
The A bit is set when one or more measured values exceed a configured maximum threshold. The A bit is cleared when the measured value falls below its configured reuse threshold.
Use the no parameter with this command to unset a-bit-min-max-delay-threshold on the current interface.
Command Syntax
delay-measurement a-bit-min-max-delay-threshold min <1-16777215> <1-16777215> max <1-16777215> <1-16777215>)
no delay-measurement a-bit-min-max-delay-threshold
Parameter
min
Reuse threshold
<1-16777215>
Reuse threshold value of Min-Delay in microseconds
<1-16777215>
Reuse threshold value of Max-Delay in microseconds
a-bit-threshold
Threshold values to set/clear A-bit
max
Maximum threshold
<1-16777215>
Maximum threshold value of Min-Delay in microseconds
<1-16777215>
Maximum threshold value of Max-Delay in microseconds
Command Mode
Interface mode
Applicability
This command was introduced in OcNOS-SP version 5.0.
Examples
#configure terminal
(config)#interface eth1
(config-if)#delay-measurement a-bit-min-max-delay-threshold min 11 22 max 33 44
(config-if)#no delay-measurement a-bit-min-max-delay-threshold
delay-measurement static
Use this command to advertise static the minimum and maximum delay values or average link delay variation or average link delay values between two directly connected IS-IS/OSPF neighbors.
Use the no parameter with this command to unset min-max-uni-link-delay, uni-delay-variation and uni-link-delay static values on the current interface.
Command Syntax
delay-measurement static (min-max-uni-link-delay <1-16777215> <1-16777215> | uni-delay-variation <0-16777215> | uni-link-delay <1-16777215>)
no delay-measurement static (min-max-uni-link-delay | uni-delay-variation | uni-link-delay)
Parameter
min-max-uni-link-delay
Min/Max Unidirectional Link Delay
<1-16777215>
Minimum Unidirectional Link Delay in microseconds
<1-16777215>
Maximum Unidirectional Link Delay in microseconds
uni-delay-variation
Unidirectional Delay Variation
<0-16777215>
Value in microseconds
uni-link-delay
Unidirectional Link Delay
<1-16777215>
Value in microseconds
Command Mode
Interface mode
Applicability
This command was introduced in OcNOS-SP version 5.0.
Examples
#configure terminal
(config)#interface eth1
(config-if)#delay-measurement uni-delay-variation static 12
(config-if)#no delay-measurement uni-delay-variation static
#configure terminal
(config)#interface eth1
(config-if)#delay-measurement static uni-link-delay 12
(config-if)#no delay-measurement static uni-link-delay
(config-if)#delay-measurement static min-max-uni-link-delay 1 3
config-if)#no delay-measurement static min-max-uni-link-delay
delay-measurement a-bit-delay-threshold
Use this command to advertise average link delay between two directly connected IS-IS/OSPF neighbors.
a-bit-threshold represents the Anomalous (A) bit. The A bit is set when the static value exceeds its configured maximum threshold. The A bit is cleared when the static value falls below its configured reuse threshold.
Use the no parameter with this command to unset uni-link-delay on the current interface.
Command Syntax
delay-measurement a-bit-delay-threshold min <1-16777215> max <1-16777215>))
no delay-measurement a-bit-delay-threshold
Parameter
min
Reuse threshold
<1-16777215>
Reuse threshold value in microseconds
max
Maximum threshold
<1-16777215>
Maximum threshold value in microseconds
Command Mode
Interface mode
Applicability
This command was introduced in OcNOS-SP version 5.0.
Examples
#configure terminal
(config)#interface eth1
(config-if)#delay-measurement a-bit-delay-threshold min 11 max 22
(config-if)#no delay-measurement a-bit-delay-threshold
description
Use this command to assign an description to an interface.
Use the no parameter to remove an interface description.
Command Syntax
description LINE
no description
Parameter
LINE
Interface description. Avoid the special characters “?”, “,”, “>”, “|”, and “=” in the description. The “|” is allowed only for interface description CLI.
Default
No default value is specified
Command Mode
Interface mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
The following example provides information about the connecting router for interface eth1.
Router#configure terminal
Router(config)#interface eth1
Router(config-if)#description Connected to Zenith's fas2/0
duplex
Use this command to set the duplex mode for each interface.
Use the no parameter to remove the duplex mode.
Note: Interface duplex setting is not supported on Management interface eth0.
Command Syntax
duplex (half|full)
no duplex
Parameter
half
Half-duplex mode.
full
Full-duplex mode.
Default
By default, duplex mode is full duplex.
Command Mode
Interface mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#interface eth3
(config-if)#duplex full
(config-if)#no duplex
fec
fec
Use this command to force/auto configure forward error correction (FEC) on a physical port.
Use the no parameter to enable automatic FEC configuration provisioning based on medium.
Command Syntax
fec (on (cl74|cl91)|off|auto)
no fec
Parameter
on
Enable FEC.
on cl74
Enable Base-R FEC if H/W supports it
on cl91
Enable RS-528 FEC is H/W supports it
off
Disable FEC.
auto
Automatically apply FEC for the below transceiver Ethernet compliance codes.
Transceiver compliance codes can be fetched via the "show interface controller"
command. Also, "fec auto" behavior is the same as no fec.
100G AOC (Active Optical Cable) or 25GAUI C2M AOC
100G ACC (Active Copper Cable) or 25GAUI C2M ACC
100G ACC or 25GAUI C2M ACC
100G AOC or 25GAUI C2M AOC
100GBASE-SR4 or 25GBASE-SR
100G AOC (Active Optical Cable) or 25GAUI C2M AOC
Default
By default, FEC mode is set to auto.
Command Mode
Interface mode
Applicability
This command was introduced before OcNOS version 4.1. The CLI is updated for options cl74|cl91 in OcNOS version 6.3.1
Examples
(config)#interface eth3
(config-if)#fec on
(config-if)#fec off
(config-if)#fec auto
(config-if)#fec on cl74
(config-if)#fec on cl91
flowcontrol
Use this command to enable or disable flow control.
Flow control enables connected Ethernet ports to control traffic rates during periods of congestion by allowing congested nodes to pause link operations at the other end. If one port experiences congestion and cannot receive any more traffic, it notifies the other port to stop sending until the condition clears. When a local device detects congestion at its end, it notifies the remote device by sending a pause frame. On receiving a pause frame, the remote device stops sending data packets, which prevents loss of data packets during the period of congestion.
Use the no parameter with this command to disable flow control.
Command Syntax
flowcontrol both
flowcontrol send on
flowcontrol send off
flowcontrol receive on
flowcontrol receive off
no flowcontrol
Parameters
both
Specify flow control mode for sending or receiving.
send
Specify flow control mode for sending.
receive
Specify the flow control mode for receiving.
off
Turn off flow control.
on
Turn on flow control.
Default
The flow control is enabled globally and auto-negotiation is on, flow control is enabled and advertised on 10/100/1000M ports. If auto-negotiation is off or if the port speed was configured manually, flow control is neither negotiated with nor advertised to the peer.
Command Mode
Interface mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#interface eth1
(config-if)#flowcontrol receive off
#configure terminal
(config)#interface eth1
(config-if)#flowcontrol receive on
(config)#interface eth1
(config-if)#no flowcontrol
hardware-profile portmode
Use this command to set the global port mode.
Command Syntax
hardware-profile portmode (4X10g|40g)
Parameter
4X10g
Split all the 40G flex ports on the system
40g
Disable splitting on all flex ports and make all ports 40G
Default
No default value is specified
Command Mode
Configure mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#hardware-profile portmode 40g
if-arbiter
Use this command to discover new interfaces recently added to the kernel and add them to the OcNOS database.
This command starts the arbiter to check interface information periodically. OcNOS dynamically finds any new interfaces added to the kernel. If an interface is loaded dynamically into the kernel when OcNOS is already running, this command polls and updates the kernel information periodically.
Use the no parameter with this command to revert to default.
Command syntax
if-arbiter (interval <1-65535>|)
no if-arbiter
Parameter
interval
Interval (in seconds) after which NSM sends a query to the kernel.
Default
By default, if-arbiter is disabled. When interface-related operations are performed outside of OcNOS (such as when using the ifconfig command), enable if-arbiter for a transient time to complete synchronization. When synchronization is complete, disable it by giving the noif-arbiter command.
Command Mode
Configure mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
#configure terminal
(config)#if-arbiter interval 5
interface
Use this command to select an interface to configure, and to enter the Interface command mode.
Use the no parameter with this command to remove this configuration.
Command Syntax
interface IFNAME
no interface IFNAME
Parameter
IFNAME
Name of the interface.
Default
No default value is specified
Command Mode
Configure mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
This example shows the use of this command to enter the Interface mode (note the change in the prompt).
#configure terminal
(config)#interface eth3
(config-if)#
ip address A.B.C.D/M
Use this command to specify that an IP address and prefix length will be used by this interface. If the secondary parameter is not specified, this command overwrites the primary IP address. If the secondary parameter is specified, this command adds a new IP address to the interface. The secondary address cannot be configured in the absence of a primary IP address. The primary address cannot be removed when a secondary address is present.
Use the no parameter with this command to remove the IP address from an interface.
Command Syntax
ip address A.B.C.D/M label LINE
ip address A.B.C.D/M (secondary|)
ip address A.B.C.D/M secondary label LINE
no ip address A.B.C.D/M label LINE
no ip address A.B.C.D/M secondary label LINE
no ip address (A.B.C.D/M (secondary|)|)
Parameters
LINE
Label of this address.
secondary
Make the IP address secondary.
Default
No default value is specified
Command Mode
Interface mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
(config)#interface eth3
(config-if)#ip address 10.10.10.50/24
(config-if)#ip address 10.10.11.50/24 secondary
ip address dhcp
Use this command to specify that a DHCP client will be used to obtain an IP address for an interface.
Use the no parameter with this command to remove the IP address from an interface.
Command Syntax
ip address dhcp
no ip address dhcp
Parameters
None
Default
No default value is specified
Command Mode
Interface mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
(config)#interface eth3
(config-if)#ip address 10.10.10.50/24
(config-if)#ip address 10.10.11.50/24 secondary
(config-if)#ip address dhcp
ip forwarding
Use this command to turn on IP forwarding.
Use the no parameter with this command to turn off IP forwarding.
Command Syntax
ip forwarding
ip forwarding vrf NAME
no ip forwarding
no ip forwarding vrf NAME
Parameters
NAME
Virtual Routing and Forwarding name
Default
No default value is specified
Command Mode
Configure mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#ip forwarding
ip prefix-list
Use this command to create an entry for a prefix list.
A router starts to match prefixes from the top of the prefix list and stops whenever a match or deny occurs. To promote efficiency, use the seq parameter and place common matches or denials towards the top of the list. The sequence values are generated in the sequence of 5.
Use the parameters ge and le specify the range of the prefix length to be matched. When setting these parameters, set le to be less than 32 and ge to be less than le value.
Use the no parameter with this command to delete the prefix-list entry.
Command Syntax
ip prefix-list WORD
(deny|permit) (A.B.C.D/M|any)
(deny|permit) A.B.C.D/M eq <0-32>
(deny|permit) A.B.C.D/M ge <0-32>
(deny|permit) A.B.C.D/M ge <0-32> le <0-32>
(deny|permit) A.B.C.D/M le <0-32>
(deny|permit) A.B.C.D/M le <0-32> ge <0-32>
seq <1-4294967295> (deny|permit) (A.B.C.D/M|any)
seq <1-4294967295> (deny|permit) A.B.C.D/M eq <0-32>
seq <1-4294967295> (deny|permit) A.B.C.D/M ge <0-32>
seq <1-4294967295> (deny|permit) A.B.C.D/M ge <0-32> le <0-32>
seq <1-4294967295> (deny|permit) A.B.C.D/M le <0-32>
seq <1-4294967295> (deny|permit) A.B.C.D/M le <0-32> ge <0-32>
description LINE
no seq <1-4294967295> (deny|permit) (A.B.C.D/M|any)
no description LINE
no description
no ip prefix-list WORD
ip prefix-list sequence-number
no ip prefix-list sequence-number
Parameters
WORD
Name of the prefix list.
deny
Reject packets.
permit
Accept packets.
A.B.C.D/M
IP address mask and length of the prefix list mask.
eg
Exact prefix length match
le
Maximum prefix length match
ge
Minimum prefix length match
<0-32>
Prefix length to match
<1-4294967295>
Sequence number of the prefix list.
any
Take all packets of any length. This parameter is the same as using 0.0.0.0/0 le 32 for A.B.C.D/M.
sequence-number
To suppress sequence number generation, give the no ip prefix-list sequence-number command. If you disable the generating sequence numbers, you must specify the sequence number for each entry using the sequence number parameter in the ip prefix-list command.
To enable sequence number generation, give the ip prefix-list sequence-number command.
LINE
Up to 80 characters describing this prefix-list.
Default
No default value is specified
Command Mode
Configure mode
IP prefix-list mode
Applicability
This command was introduced before OcNOS Version SP 4.0.
Examples
In this configuration, the ip prefix-list command matches all, but denies the IP address range, 76.2.2.0.
#conf t
(config)#router bgp 100
(config-router)#network 172.1.1.0
(config-router)#network 172.1.2.0
(config-router)#
(config-router)#neighbor 10.6.5.3 remote-as 300
(config-router)#neighbor 10.6.5.3 prefix-list mylist out
(config-router)#exit
(config)#ip prefix-list mylist
(config-ip-prefix-list)#seq 5 deny 76.2.2.0/24
(config-ip-prefix-list)#seq 10 permit 0.0.0.0/0
ip proxy-arp
Use this command to enable the proxy ARP feature on an interface.
Use the no parameter to disable the proxy ARP feature on an interface.
Command Syntax
ip proxy-arp
no ip proxy-arp
Parameters
None
Default
By default, the ip proxy-arp is disabled
Command Mode
Interface mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
#configure terminal
(config)#interface eth3
(config-if)#ip proxy-arp
ip remote-address
Use this command to set the remote address (far end) on a point-to-point non multi-access link. This command can be used only on unnumbered interfaces. When a new remote-address is configured, the old address gets overwritten.
Use the no parameter to disable this function.
Command Syntax
ip remote-address A.B.C.D/M
no ip remote-address
Parameter
A.B.C.D/M
IP address and prefix length of the link remote address.
Default
No default value is specified
Command Mode
Interface mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
(config)#interface ppp0
(config-if)#ip unnumbered eth1
(config-if)#ip remote-address 1.1.1.1/32
ip unnumbered
Use this command to enable IP processing without an explicit address on a point-to-point non multi-access link. Moreover, this command lets an interface borrow the IP address of a specified interface to enable IP processing on a point-to-point interface without assigning it an explicit IP address. In this way, the IP unnumbered interface can borrow the IP address of another interface already configured on the router to conserve network and address space.
Use the no parameter with this command to remove this feature on an interface.
Command Syntax
ip unnumbered IFNAME
no ip unnumbered
Parameter
IFNAME
Interface name.
Default
No default value is specified
Command Mode
Interface mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
The following example creates a tunnel on eth1.
(config)#interface lo
(config-if)#ip address 127.0.0.1/8
(config-if)#ip address 33.33.33.33/32 secondary
(config-if)#exit
(config)#interface eth1
(config-if)#ip address 10.10.10.145/24
(config-if)#exit
(config)#interface Tunnel0
(config-if)#tunnel source 10.70.0.145
(config-if)#tunnel destination 10.70.0.77
(config-if)#tunnel ttl 255
(config-if)#tunnel path-mtu-discovery
(config-if)#tunnel mode vxlan
(config-if)#ip unnumbered eth1
(config-if)#exit
(config)#router ospf
(config-router)#network 10.10.10.0/24 area 0
ip vrf forwarding
This command associates an interface with a VRF.
Use the no parameter with this command to unbind an interface.
Note: When you give this command in interface configuration or subinterface configuration mode of the parent VR, the IP address and other attributes of the interface are deleted from the interface. After giving this command, the IP attributes must then be configured in the context of the VRF.
Note: The Out Of Band (OOB) management port is part of the “management” VRF. Also, this port cannot be moved out of “management” VRF.
Command Syntax
ip vrf forwarding WORD
no ip vrf forwarding WORD
Parameter
WORD
Name of the VRF.
Default
No default value is specified
Command Mode
Interface mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
#configure terminal
(config)#ip vrf myVRF
(config-vrf)#exit
(config)#interface eth1
(config-if)#ip vrf forwarding myVRF
ipv6 address
Use this command to set the IPv6 address of an interface.
Use the no form of this command to disable this function.
Note: This command is also used to configure an IPv6 link-local address for an interface.
Command Syntax
ipv6 address X:X::X:X/M
ipv6 address X:X::X:X/M anycast
no ipv6 address X:X::X:X/M
Parameters
X:X::X:X/M
IP destination prefix and a mask length.
anycast
Make an anycast address which is assigned to a set of interfaces that belong to different devices. A packet sent to an anycast address is delivered to the closest interface (as defined by the routing protocols in use) identified by the anycast address
Default
No default value is specified
Command Mode
Interface mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
#configure terminal
(config)#interface eth3
(config-if)#ipv6 address 3ffe:506::1/64
#configure terminal
(config)#interface eth4
(config-if)#ipv6 address fe80::ab8/64
ipv6 forwarding
Use this command to turn on IPv6 forwarding.
Use the no parameter with this command to turn off IPv6 forwarding.
Command Syntax
ipv6 forwarding
ipv6 forwarding vrf NAME
no ipv6 forwarding
no ipv6 forwarding vrf NAME
Parameters
NAME
Virtual Routing or Forwarding name
Default
No default value is specified
Command Mode
Command mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
#configure terminal
(config)#ipv6 forwarding
ipv6 prefix-list
Use this command to create an entry for an ipv6 prefix-list.
Router starts to match prefixes from the top of the prefix list, and stops whenever a match or deny occurs. To promote efficiency, use the seq parameter and place common matches or denials towards the top of the list. The sequence values are generated in the sequence of 5.
The parameters ge and le specify the range of the prefix length to be matched.
Use the no parameter with this command to delete the prefix-list entry.
Command Syntax
ipv6 prefix-list WORD
(deny|permit) (X:X::X:X/M|any)
(deny|permit) X:X::X:X/M ge <0-128>
(deny|permit) X:X::X:X/M ge <0-128> le <0-128>
(deny|permit) X:X::X:X/M le <0-128>
(deny|permit) X:X::X:X/M le <0-128> ge <0-128>
seq <1-4294967295> (deny|permit) (X:X::X:X/M|any)
seq <1-4294967295> (deny|permit) X:X::X:X/M ge <0-128>
seq <1-4294967295> (deny|permit) X:X::X:X/M ge <0-128> le <0-128>
seq <1-4294967295> (deny|permit) X:X::X:X/M le <0-128>
seq <1-4294967295> (deny|permit) X:X::X:X/M le <0-128> ge <0-128>
description LINE
no seq <1-4294967295> (deny|permit) (X:X::X:X/M|any)
no description
no ipv6 prefix-list WORD
ipv6 prefix-list sequence-number
no ipv6 prefix-list sequence-number
Parameters
WORD
Name of the prefix list.
deny
Reject packets.
permit
Accept packets.
X:X::X:X/M
IP address mask and length of the prefix list mask.
any
Take all packets of any length. This is the same as specifying ::/0 for X:X::X:X/M.
eg
Exact prefix length match
le
Maximum prefix length match
ge
Minimum prefix length match
<0-128>
Prefix length to match
<1-4294967295>
Sequence number of the prefix list.
sequence-number
To suppress sequence number generation, give the no ipv6 prefix-list sequence-number command. If you disable the generating sequence numbers, you must specify the sequence number for each entry using the sequence number parameter in the ipv6 prefix-list command.
To enable sequence number generation, give the ipv6 prefix-list sequence-number command.
LINE
Up to 80 characters describing this prefix-list.
Default
No default value is specified
Command Mode
Configure mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#ipv6 prefix-list mylist
(config-ipv6-prefix-list)#seq 12345 deny 3ffe:345::/16 le 22 ge 14
ipv6 unnumbered
Use this command to enable IPv6 processing without an explicit address, on a point-to-point non multi-access link.
This command lets an interface borrow the IPv6 address of a specified interface to enable IPv6 processing on a point-to-point interface without assigning it an explicit IPv6 address. In this way, the IPv6 unnumbered interface can borrow the IPv6 address of another interface already configured on the router to conserve network and address space.
Use the no parameter with this command to remove this feature on an interface.
Command Syntax
ipv6 unnumbered IFNAME
no ipv6 unnumbered
Parameter
IFNAME
Interface name.
Default
No default value is specified
Command Mode
Interface mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
The following example creates a tunnel on eth1:
#configure terminal
(config)#interface lo
(config-if)#ipv6 address::1/128
(config-if)#exit
(config)#interface eth1
(config-if)#ipv6 address fe80::20e:cff:fe6e:56dd/64
(config-if)#exit
(config)#interface Tunnel0
(config-if)#tunnel source 10.70.0.145
(config-if)#tunnel destination 10.70.0.77
(config-if)#tunnel ttl 255
(config-if)#tunnel path-mtu-discovery
(config-if)#tunnel mode vxlan
(config-if)#ipv6 unnumbered eth1
(config-if)#ipv6 router ospf area 0 tag 1
(config-if)#exit
(config)#router ipv6 ospf 1
(config-router)#router-id 10.70.0.145
link-debounce-time
Use this command to set the debounce time for linkup and linkdown transitions for the interface.
User can set only one of the timers (either linkup or linkdown) by setting the other one to 0.
Use the no form of this command to turn off the link debounce timer on the interface.
Command Syntax
link-debounce-time <0-5000> <0-5000>
no link-debounce-time
Parameter
<0-5000>
timer value in milliseconds for the linkup transition
<0-5000>
timer value in milliseconds for the linkdown transition
Default
By default, it is disabled.
Command Mode
Interface mode
Applicability
This command was introduced before OcNOS-SP version 5.0.
Example
#configure terminal
(config)#interface eth1
(config-if)#link-debounce-time 4000 5000
(config-if)#link-debounce-time 0 5000
(config-if)#link-debounce-time 3000 0
load interval
Use this command to configure the interval for which average traffic rate need to be shown. Intervals can be configured in steps of 30 seconds.
Use the no parameter with this command to set the load interval to its default.
Command Syntax
load-interval <30-300>
no load-interval
Parameter
<30-300>
Load period in multiples of 30 seconds.
Default
By default, load interval is 300 seconds
Command Mode
Interface mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
#configure terminal
(config)#interface xe1/1
(config-if)#load-interval 30
(config-if)#no load-interval
loopback
Use this command to set the ethernet loopback mode on the interface.
Use the no form of this command to remove loopback on the interface.
Note: Remote PHY loopback supported only on a single serdes lane of serdes-quad at a time. So below cases are not supported:
1. 100G and 40G interface mode.
2. 2x50G port breakout mode.
3. In 4x10 or 4x25G breakout mode, at a time only one interface is supported.
4. If interface is part of port-group, at a time only one interface is supported.
Command Syntax
loopback ((tx (mac|phy))|(rx phy))
Parameter
The parameters for Tx are MAC or PHY and for Rx is PHY.
Default
No default value is specified.
Command Mode
Interface mode
Applicability
This command is introduced before OcNOS-DC version 5.0.
Example
#configure terminal
(config)#interface xe0
(config-if)#loopback tx mac
(config-if)#exit
(config)#interface xe0
(config-if)#loopback tx phy
(config-if)#exit
(config)#interface xe0
(config-if)#loopback rx phy
(config-if)#exit
loss-measurement uni-link-loss
Use this command to advertise the loss (as a packet percentage) between two directly connected IS-IS/OSPF neighbors.
The A bit is set when the measured value of this parameter exceeds its configured maximum threshold. The A bit is cleared when the measured value falls below its configured reuse threshold.
Use the no parameter with this command to unset uni-link-loss on the current interface.
Command Syntax
loss-measurement uni-link-loss ((static VALUE) | (a-bit-threshold min VALUE max VALUE))
no loss-measurement uni-link-loss (static | a-bit-threshold)
Parameter
static
Static value
VALUE
Loss percentage in six precision float format. eg: 3.123456
a-bit-threshold
Threshold values to set/clear A-bit
min
Reuse threshold
VALUE
Reuse threshold percentage in six precision float format. eg:3.123456
max
Maximum threshold
VALUE
Maximum threshold percentage in six precision float format. eg:3.123456
Command Mode
Interface mode
Applicability
This command was introduced in OcNOS-SP version 5.0.
Examples
#configure terminal
(config)#interface eth1
(config-if)#loss-measurement uni-link-loss static 12.3
(config-if)#no loss-measurement uni-link-loss static
(config-if)#loss-measurement uni-link-loss a-bit-threshold min 1.12 max 2.2
(config-if)#no loss-measurement uni-link-loss a-bit-threshold
mac-address
Use this command to configure a MAC address for Layer 3 interfaces. Interface can be Layer 3 physical interface or routed VLAN interface or port-channel.
Use the no form of this command to remove the MAC address from an interface.
Command Syntax
mac-address HHHH.HHHH.HHHH
no mac-address
Parameters
mac-address
mac-address in HHHH.HHHH.HHHH format (only supported on L3 Interfaces)
Default
None
Configuration mode
Interface mode
Applicability
This command was introduced before OcNOS version 6.4.2.
Examples
OcNOS(config)#int xe46
OcNOS(config-if)#mac-address 00e0.aaaa.bbbb
mac-address secondary peer-mlag
Use this command to enable L3 termination of data-packets on both the MLAG peers applicable on SVI interfaces.
Use the no form of this command to disable.
Command Syntax
mac-address secondary peer-mlag
no mac-address secondary peer-mlag
Parameters
NA
Default
Disabled
Configuration mode
Interface mode
Applicability
This command was introduced before OcNOS version 6.1.0.
Examples
OcNOS(config)#interface vlan1.10
OcNOS(config-if)#mac-address secondary peer-mlag
OcNOS(config-if)#exit
monitor speed
Use this command to enable speed monitoring on interface.
Use the no parameter with this command to disable monitoring.
Command Syntax
monitor speed
no monitor speed
Default
By default, speed monitoring will be disabled
Command Mode
Interface mode
Applicability
This command was introduced in OcNOS-SP version 1.0.
Example
#configure terminal
(config)#interface xe1/1
(config-if)#monitor speed
(config-if)#no monitor speed
monitor queue-drops
Use this command to enable queue-drops monitoring on interface.
Use the no parameter with this command to disable monitoring.
Command Syntax
monitor queue-drops
no monitor queue-drops
Default
By default, queue-drops monitoring will be disabled
Command Mode
Interface mode
Applicability
This command was introduced in OcNOS-SP version 1.0.
Example
#configure terminal
(config)#interface xe1/1
(config-if)#monitor queue-drops
(config-if)#no monitor queue-drops
monitor speed threshold
Use this command to modify default speed monitor threshold on interface.
Use the no parameter with this command to set the monitor speed threshold to its default.
Note: Warning threshold must be greater than recovery threshold and it is recommended to keep a difference of 10 percent to avoid frequent notifications caused by variations in average speed.
Command Syntax
monitor speed threshold warning <1-100> recovery <1-100>
no monitor speed threshold
Parameter
<1-100>
Warning level threshold value in percentage
<1-100>
Recovery level threshold value in percentage
Default
By default, warning threshold is 90 percentage and recovery is 80 percentage.
Command Mode
Interface mode
Applicability
This command was introduced in OcNOS-SP version 1.0.
Example
#configure terminal
(config)#interface xe1/1
(config-if)# monitor speed threshold warning 80 recovery 70
(config-if)#no monitor speed threshold
mtu
Use this command to set the Maximum Transmission Unit (MTU) and Maximum Receive Unit (MRU) for an interface
Use the no parameter with this command to set the MTU to its default.
Note: To allow jumbo frames over SVI interfaces, it is mandatory to configure the applicable MTU for the specific SVI interfaces.
Limitation for MTU configuration on Label-Switching:
Creating a sub-interface automatically increases the physical interface MTU size by 8 bytes to accommodate double VLAN tag encapsulation.
Configuring label switching for physical layer-3 interfaces adds 20 bytes internally to the MTU to accommodate up-to five labels. However, configuring label-switching on sub-interface does not change the MTU of physical interface. Hence, the physical interface requires a manual increase in MTU size.
During the BGP update, in case the control packet contains 1500 bytes when it reaches the hardware, the hardware adds the Encapsulation for the sub-interface and MPLS header (Additional bytes). Now, the hardware drops it as physical port MTU is limited to 1500 bytes.
While configuring MTU on label-switching enabled with Subinterface/SVI/LAG and the Parent Physical port follow guide lines mentioned below:
It is recommended to configure higher MTU on network ports in comparison with access ports. Hence, increase the MTU on both physical and sub-interfaces to accommodate the PDU.
When using sub-interface for MPLS network interfaces, considering the default MTU of 1500, minimum MTU configuration recommendation is as follows
• Sub-interface: MTU 1520 (to accommodate 5 MPLS labels)
• Physical interface: MTU 1528: (Default MTU 1500 + double encap 8 + MPLS up-to 5 labels 20) = 1528).
Note: MTU configuration is considered from IP header onwards. Hence, OcNOS adds 14 bytes to MTU internally to accommodate L2 header. The effective MTU in hardware will be 1528+14 = 1542.
• LAG interface: MTU is applied on all members internally
• SVI: When label-switching enabled on VLAN interface, MTU value must be manually increased by at least 20 bytes on Parent interfaces of VLAN.
Example, default MTU must be set as 1520 instead of 1500 on label-switching parent interface label switched VLAN interface. (Parent Interface MTU >= label switched VLAN interface MTU + 20).
Command Syntax
mtu <64-65536>
no mtu
Parameter
<64-65536>
Specify the size of MTU in bytes:
<64-16338> for L2 packet
<576-9216> for L3 IPv4 packet
<1280-9216> for L3 IPv6 packet
<576-65536> for IPv4 packet
<1280-65536> for IPv6 packet on loopback interface
Default
By default, MTU is 1500 bytes
Command Mode
Interface mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
#configure terminal
(config)#interface eth3
(config-if)#mtu 120
multicast
Use this command to set the multicast flag for the interface.
Use the no form of this command to disable this function.
Command Syntax
multicast
no multicast
Parameters
None
Default
No default value is specified
Command Mode
Interface mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
#configure terminal
(config)#interface eth3
(config-if)#multicast
show flowcontrol
Use this command to display flow control information.
Command Syntax
show flowcontrol
show flowcontrol interface IFNAME
Parameters
interface IFNAME
Specify the name of the interface to be displayed.
Command Mode
Exec mode and Privileged Exec mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
The following is a sample output of the show flowcontrol interface command displaying flow control information:
#show flowcontrol interface ge1
Port Send FlowControl Receive FlowControl RxPause TxPause
admin oper admin oper
----- ------- -------- ------- -------- ------- -------
ge1 on on on on 0 0
#
Table 20-38 explains the show command output fields.
Table 20-38: show flow control output
Entry | Description |
|---|
Port | Interface being checked for flowcontrol. |
Send admin | Displays whether the flowcontrol send process is administratively on or off. |
FlowControl oper | Displays whether send flowcontrol is on or off on this interface. |
Received admin | Displays whether the flowcontrol receive process is administratively on or off. |
FlowControl oper | Displays whether receive flowcontrol is on or off on this interface. |
RxPause | Number of received pause frames. |
TxPause | Number of transmitted pause frames. |
show hardware-discard-counters
Use this command to check device level discard counters.
Command Syntax
show hardware-discard-counters
Parameters
None
Command Mode
Exec mode
Applicability
The command is introduced before OcNOS version 1.3.
Qumran devices do not support discard counters per interface. Only global level counters are available for advanced debugging using the
show hardware-discard-counters command.
Examples
#show hardware-discard-counters
+--------------------------------------------------+--------------------+
| Registers | Core 0 |
+--------------------------------------------------+--------------------+
CGM_VOQ_SRAM_ENQ_RJCT_PKT_CTR 437
Reason : QNUM_NOT_VALID Y
EGQ_PQP_DISCARD_UNICAST_PACKET_COUNTER 8894
Reason : SRC_EQUAL_DEST_INT Y
See
Table 20-39 and
Table 20-40 for details:
Table 20-39: Table detailing about counters supported
Register | Description |
|---|
CGM_VOQ_SRAM_ENQ_RJCT_PKT_CTR for QAX IQM_QUEUE_ENQ_DISCARDED_PACKET_COUNTER for QMX | Drop is due to PPdecision to drop, or invalid destination received from PPblocks. The packet DP (Drop Precedence) is higher than the configured Drop DP. |
EGQ_PQP_DISCARD_UNICAST_PACKET_COUNTER | Seen with unknown unicast frames, source and destination learnt from same interface. |
Table 20-40: Table detailing about reasons supported
Register | Description |
|---|
QNUM_NOT_VALID for QAX QUEUE_NOT_VALID_STATUS for QMX DP_LEVEL_RJCT for QAX DP_LEVEL_STATUS for QMX | Seen with Vlan Discards, ACL Drops, Storm Control, STP Blocked Port. Seen with Policer Discards. |
SRC_EQUAL_DEST_INTF | Seen when traffic is not learned, but is still forwarded/flooded. |
show interface
Use this command to display interface configuration and status information.
Command Syntax
show interface (IFNAME|)
Parameter
IFNAME
Interface name.
Command Mode
Exec mode and Privileged Exec mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
#show interface xe1/1
Interface xe1/1
Scope: both
Flexport: Breakout Control Port (Active): Break Out Enabled
Hardware is ETH Current HW addr: ecf4.bb6e.934b
Physical:ecf4.bb6e.934b Logical:(not set)
Port Mode is access
Interface index: 5001
Metric 1 mtu 1500 duplex-full(auto) link-speed 1g(auto)
<UP,BROADCAST,RUNNING,MULTICAST>
VRF Binding: Not bound
Label switching is disabled
No Virtual Circuit configured
DHCP client is disabled.
Last Flapped: 2016 Nov 05 22:40:23 (00:19:25 ago)
Statistics last cleared: 2016 Nov 05 04:49:55 (18:09:53 ago)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 256 bits/sec, 0 packets/sec
RX
unicast packets 39215813 multicast packets 0 broadcast packets 0
input packets 39215813 bytes 2666662432
jumbo packets 0
runts 0 giants 0 CRC 0 fragments 0 jabbers 0
input error 0
input with dribble 0 input discard 0
Rx pause 0
TX
unicast packets 38902 multicast packets 437 broadcast packets 0
output packets 437 bytes 28018
jumbo packets 0
output errors 0 collision 0 deferred 0 late collision 0
output discard 0
Tx pause 0
Table 20-41 explains the output fields.
Table 20-41: show interface output details
Field | Description |
|---|
Scope | Interface can be used for communication within the device and outside the device (Both). |
Flexport | Specifies whether the ports has Breakout capabilities or is a Non-Control Port. |
Breakout Control Port (Active) | Specifies whether Breakout is active or disabled. |
Hardware is ETH Current HW addr | The MAC address of the interface. |
Physical | Displays the physical MAC address of the interface. |
Logical | Displays the logical MAC address (if any) of the interface. |
Port Mode | Displays the port mode: Router, VLAN access, switch, or trunk. |
Interface index | Index number, Metric, MTU size, duplex-full (auto) or half-duplex, minimum link speed in gigabits, and if the interface is up, broadcasting, and multicasting. |
VRF Binding | Show whether the interface is VRF bound and (if bound) with what VRF, if Label Switching is enabled or disabled, and if a virtual circuit is configured. |
DHCP client | The state of the DHCP client – whether this interface is connected to a DHCP server. |
Last Flapped | Date and time when the interface last flapped. |
Statistics last cleared | Date and time when the interface’s statistics were cleared. |
5 minute input rate | Input rate in bits/second and packets/second |
5 minute output rate | Output rate in bits/second and packets/second |
RX | Counters for unicast packets, multicast packets, broadcast packets, input packets, bytes, jumbo packets, runts, giants, CRC errors, fragments, jabbers, input errors, input with dribble input discards, and receive pause. |
TX | Counters for unicast packets, multicast packets, broadcast packets, output packets, bytes, jumbo packets, output errors, collisions, differed packets, input late collisions, output discards, and transmit pause. |
show interface capabilities
Use this command to display interface capabilities
Command Syntax
show interface (IFNAME|) capabilities
Parameters
IFNAME
Displays the name of a specific interface for which status and configuration data is desired.
Command Mode
Exec mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
#show interface xe1/1 capabilities
xe1/1
Speed(FD) : 10MB,100MB,1000MB,10GB,20GB,40GB
Interface : xgmii
Medium : copper
Loopback : none,MAC,PHY
Pause : pause_tx,pause_rx,pause_asymm
Flags : autoneg
Encap : IEEE,HIGIG,HIGIG2
Table 20-42 explains the show command output fields.
Table 20-42: show interface capabilities output details
Field | Description |
|---|
Interface number | The identifying ID number of the interface – eht0, xe1, etc. |
Speed (FD) | The Flexible Data-Rates (FD) of the interface |
interface | XAUI is a standard for extending the XGMII (10 Gigabit Media Independent Interface) between the MAC and PHY layer of Gigabit Ethernet. |
Medium | Members have to have the same medium type configured. This only applies to Ethernet port-channel. Copper, fiber optics, etc. |
Loop back | The loop back between the MAC and PHY layers. |
Pause | Pause transmit, pause receive, pause asymmetrically. |
Flags | Interface flags set for Auto-negotiation. |
Encap | Encapsulation – IEEE, HIGIG, and HIGIG2 specifications – HIGIG is a proprietary protocol that is implemented by Broadcom. The HIGIG protocol supports various switching functions. The physical signaling across the interface is XAUI, four differential pairs for receive and transmit (SerDes), each operating at 3.125 Gbit/s. |
show interface counters
Use this command to display the ingress and egress traffic counters on the interface.
Note: Counters are meant for debugging purpose and the accuracy of the transmit discard counter is not guaranteed in all scenarios.
Command Syntax
show interface (IFNAME|) counters (active|)
show interface cpu counters
Parameter
IFNAME
Interface name.
active
Statistics for link-up interfaces.
cpu
CPU interface.
Command Mode
Exec mode and Privileged Exec mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
#show interface xe1/1 counters
Interface xe1/1
Scope: both
Rx Packets: 1000
Rx Bytes: 1000000
Rx Unicast Packets: 1000
Rx Packets from 512 to 1023 bytes: 1000
Tx Packets: 3897
Tx Bytes: 249408
Tx Multicast Packets: 3897
Tx Packets with 64 bytes: 3897
Tx Packet rate: 1 pps
Tx Bit rate: 255 bps
#show interface cpu counters
CPU Interface
Tx Packets: 104508
Tx Bytes: 7106272
Tx Discard Packets: 89613672
Tx Discard Bytes: 5735237844
Rx Discard Packets: 11938
Table 20-43 explains the output fields.
Table 20-43: show interface counters output details
Field | Description |
|---|
Receive Counters | Rx Packets Rx Bytes Rx Unicast Packets Rx Multicast Packets Rx Broadcast Packets Rx Packets with 64 bytes Rx Packets from 65 to 127 bytes Rx Packets from 128 to 255 bytes Rx Packets from 256 to 511 bytes Rx Packets from 512 to 1023 bytes Rx Packets from 1024 to 1518 bytes Rx Packets from 1519 to 2047 bytes Rx Packets from 2048 to 4095 bytes Rx Packets from 4096 to 9216 bytes Rx Jumbo Packets Rx Discard Packets (not applicable for Qumran platform) Rx Packets with error Rx CRC Error Packets Rx Undersized Packets Rx Oversized Packets Rx Fragment Packets Rx Jabber Packets Rx MAC error Packets Rx Pause Packets Rx Unrecognized MAC Control Packets Rx Drop Events Rx Packet rate Rx Bit rate |
Transmit Counters | Tx Packets Tx Bytes Tx Unicast Packets Tx Multicast Packets Tx Broadcast Packets Tx Packets with 64 bytes Tx Packets from 65 to 127 bytes Tx Packets from 128 to 255 bytes Tx Packets from 256 to 511 bytes Tx Packets from 512 to 1023 bytes Tx Packets from 1024 to 1518 bytes Tx Packets from 1519 to 2047 bytes Tx Packets from 2048 to 4095 bytes Tx Packets from 4096 to 9216 bytes Tx Jumbo Packets Tx Discard Packets (not applicable for Qumran platform) Tx Packets with error Tx Collisions Tx Late Collisions Tx Excessive Collisions Tx Pause Packets Tx Packet rate Tx Bit rate |
CPU Interface Counters | Tx Packets Tx Bytes Tx Discard Packets Tx Discard Bytes Rx Discard Packets |
show interface counters drop-stats
Use this command to display the ingress and egress traffic discard reason counters on the interface.
Note: You can only display statistics for physical ports and cpu ports, but not for the out-of-band management (OOB) management port or logical interfaces.
Note: Drops in the CPU queue are listed under Tx Multicast Queue Drops, whether the packet is unicast or multicast
Command Syntax
show interface (IFNAME|) counters drop-stats
show interface cpu counters drop-stats
Parameter
IFNAME
Physical interface name
cpu
CPU interface
Command Mode
Exec mode and Privileged Exec mode
Applicability
This command was introduced before OcNOS version 1.3.1.
For Qumran devices, only error statistics are applicable and discard counters are not applicable. Only global level counters are available for advanced debugging using the command
show hardware-discard-counters.
Example
#show interface xe32/2 counters drop-stats
+---------------------+----------------+----------------+--------------------+
| Counter Description | Count | Last Increment | Last Increment Time |
+---------------------+----------------+----------------+--------------------+
Rx Bad CRC errors 0 0
Rx Undersize errors 0 0
Rx Oversize errors 0 0
Rx Fragments errors 0 0
Rx Jabbers errors 0 0
Rx Port Block Drops 6 1 2016 Nov 09 08:59:33
Rx Vlan Discards 0 0
Rx ACL/QOS Drops 0 0
Rx Policy Discards 0 0
Rx EGR Port Unavail 38784 5 2016 Nov 09 18:19:31
Rx IBP Discards 0 0
Tx Port Block Drops 359 1 2016 Nov 09 08:59:33
Tx Vlan Discards 0 0
Tx TTL Discards 0 0
Tx Unknown Discards 359 1 2016 Nov 09 08:59:33
Tx Ucast Queue Drops 0 0
Tx Mcast Queue Drops 0 0
+---------------------+----------------+----------------+--------------------+
Table 20-44 explains the output fields.
Table 20-44: show interface counters drop-stats output details
Field | Description |
|---|
Counter Description | Shows the type of packet and/or the reason why the packet was dropped. |
Count | The number of packets dropped for each reason. |
Last Increment | Number of packets dropped since this command was last entered. |
Last Increment Time | Date and time when the last packet was dropped. |
Rx Bad CRC errors | Received packets dropped because they didn’t pass the cyclic Redundancy Check (CRC). |
Rx Undersize errors | Number of received runt packets dropped. |
Rx Oversize errors | Number of received giant packets dropped |
Rx Fragments errors | Number of received packet fragments dropped |
Rx Jabbers errors | Received packets dropped because of jabber – long packet error. |
Rx Port Block Drops | Received packets dropped because port blocking is enabled (not applicable for Qumran platform). |
Rx Vlan Discards | VLAN received packets dropped because there is no VLAN configured on the port (not applicable for Qumran platform). |
Rx ACL/QOS Drops | Received packets match a field processing entry with a drop or color drop action, such as: User-configured ACL that denies traffic Service policy with a police action that drops the traffic received at a rate higher than the configured limit. (not applicable for Qumran platform) |
Rx Policy Discards | Received packets dropped because of device policies violated, such as a storm control rate violation (not applicable for Qumran platform). |
Rx EGR Port Unavail | No output port can be determined for these received packets. This counter increments along with other counter types in this table because it is a “catchall” for multiple types of discards as shown below (not applicable for Qumran platform): VLAN check failed MTU check failed ACL/QoS drops Policy discards Source MAC is null Destination IP/source IP address is null Source MAC address and destination MAC address are the same Forwarding lookup failure |
Rx IBP Discards | Ingress Back Pressure (ingress congestion) when the ingress packets buffer is full for an interface. (not applicable for Qumran platform) |
Tx Port Block Drops | Transmitted packets dropped because port blocking is enabled (not applicable for Qumran platform). |
Tx Vlan Discards | Transmitted VLAN packets dropped because there is no VLAN configured on the port (not applicable for Qumran platform). |
Tx TTL Discards | Transmitted packets discarded because their Time To Live (TTL) has ended. (not applicable for Qumran platform) |
Tx Unknown Discards | Transmitted packets dropped for unknown reason. May have something to do with the condition/configuration of the port at the other end of the connection (not applicable for Qumran platform). |
Tx Ucast Queue Drops | Transmitted packets dropped as a result of Unicast buffer overflow. |
Tx Mcast Queue Drops | Transmitted packets dropped as a result of Multicast buffer overflow. |
show interface counters error-stats
Use this command to display the ingress error traffic counters on the interface.
Command Syntax
show interface (IFNAME|) counters error-stats
Parameter
IFNAME
Interface name.
Command Mode
Exec mode and Privileged Exec mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
#show interface xe1/1 counters error-stats
+----------+-------------+--------+----------+---------+-----------+---------+
|Interface |Total errors |Bad CRC |Undersize |Oversize | Fragments | Jabbers |
+----------+-------------+--------+----------+---------+-----------+---------+
xe1/1 120 8 100 10 2 0
Table 20-45 explains the columns in the output.
Table 20-45: error traffic counters
Column | Description | Causes |
|---|
Interface | Name of the interface | Point of interconnection in network. |
Total errors | Total number of all types of errors | Number of errors in network. |
Bad CRC | Number of packets received by the port from the network, where the packets have no CRC or a bad CRC. | Packet data modified making the CRC invalid. |
Undersize | Total number of packets received that are less than 64 octets long (which exclude framing bits, but include the FCS) and have a good FCS value. | Bad frame generated by the connected device. |
Oversize | Number of packets received by the port from the network, where the packets were more than maximum transmission unit size. | Faulty hardware, dot1q, or ISL trunking configuration issues. |
Fragments | Total number of frames whose length is less than 64 octets (which exclude framing bits, but which include the FCS) and have a bad FCS value. | Ports are configured at half-duplex. Change the setting to full-duplex. |
Jabbers | Total number of frames whose length is more than the maximum MTU size. (which exclude framing bits, but which include FCS) and have a bad FCS value. | Ports are configured at half-duplex. Change the setting to full-duplex. |
show interface counters (indiscard-stats|outdiscard-stats)
Use this command to display the ingress and egress traffic discard reason counters on the interface.
Note: You can only display statistics for data ports and CPU ports, not for the out-of-band management (OOB) management port or logical interfaces.
Command Syntax
show interface (IFNAME|) counters (indiscard-stats|outdiscard-stats)
show interface cpu counters (indiscard-stats|outdiscard-stats)
Parameter
IFNAME
Physical Interface name.
indiscard-stats
Discard reasons for ingress dropped packets.
outdiscard-stats
Discard reasons for egress dropped packets.
cpu
CPU Interface.
Command Mode
Exec mode and Privileged Exec mode
Applicability
This command was introduced before OcNOS version 1.3.
This command is not available on Qumran platforms.
Examples
#show interface xe1/3 counters indiscard-stats
+---------------------+----------------+----------------+---------------------+
| Counter Description | Count | Last Increment | Last Increment Time |
+---------------------+----------------+----------------+---------------------+
STP Discards 0 0
Vlan Discards 0 0
ACL Drops 0 0
Policy Discards 0 0
EGR Port Unavail 1092867 1092867 2016 Oct 25 19:54:58
IBP Discards 0 0
+---------------------+----------------+----------------+---------------------+
#show interface counters indiscard-stats
+-------------+------------------+---------------+---------------+-----------------+------------------+--------------+--------------------+
| Interface | Port Block Drops | Vlan Discards | ACL/QOS Drops | Policy Discards | EGR Port Unavail | IBP Discards | Total Discards |
+-------------+------------------+---------------+---------------+-----------------+------------------+--------------+--------------------+
xe1 0 0 35703 0 11 0 35714
xe2 0 0 295744 0 13604 0 309348
xe3 0 0 9501 0 20405 0 29906
xe5 0 0 0 0 13602 0 13602
xe49/1 0 0 0 0 0 20658 20658
xe52/1 0 3 856029 10 13613 0 869642
xe54/1 0 5371 0 0 5371 0 5371
cpu 0 0 0 0 6 0 N/A
#show interface counters outdiscard-stats
+-------------+------------------+---------------+--------------+------------------+----------------+----------------+--------------------+
| Interface | Port Block Drops | Vlan Discards | TTL Discards | Unknown Discards | UcastQ Drops | McastQ Drops | Total Discards |
+-------------+------------------+---------------+--------------+------------------+----------------+----------------+--------------------+
xe1 0 0 0 204338 0 0 204338
xe2 0 0 0 1094368 0 0 1094368
xe3 0 0 0 818672 0 0 818672
xe52/1 0 0 0 1275156 0 0 1275156
xe54/1 0 0 0 13575 0 0 13575
cpu 0 0 0 0 N/A 1014224 N/A
Table 20-46 explain the fields in the command output.
Table 20-46: indiscard statistic output details
Statistic | Description |
STP Discards | Packets received when the ingress interface is not in STP forwarding state. |
Port Block Drops | Packets discarded on an ingress interface where port blocking is configured. |
VLAN Discards | VLAN tagged packets received on a port which is not a member of the VLAN or untagged packets received on a trunk port. |
ACL/QoS Drops | Incoming packets match a field processing entry with a drop or color drop action, such as: 1. User-configured ACL that denies traffic 2. Service policy with a police action that drops the traffic received at a rate higher than the configured limit |
Policy Discards | Device policies violated, such as a storm control rate violation, source or destination discards when L2 tagged traffic received on router interface. |
EGR (Egress) Port Unavail | No output port can be determined for this packet. This counter increments along with other counter types in this table because it is a “catchall” for multiple types of discards as shown below: 1. VLAN check failed 2. MTU check failed 3. ACL/QoS drops 4. Policy discards 5. Source MAC is null 6. Destination IP/source IP address is null 7. Source MAC address and destination MAC address are the same 8. Source MAC is configured as static on other interface 9. Forwarding lookup failure |
IBP Drops | Ingress Back Pressure (ingress congestion) when the ingress packet buffer is full for an interface. |
Total Discards | Total number of ingress dropped packets. |
Table 20-47 explain the fields in the command output.
Table 20-47: outdiscard statistics
Statistics | Description |
|---|
Port Block Drops | Packets discarded on an egress interface where port blocking is configured. |
VLAN Discards | Packets discarded because an invalid VLAN tag is encountered at an egress interface. |
TTL Discards | Packets discarded because the Time-To Live (TTL) of the outgoing packet has passed. |
Unknown Discards | Packets discarded for other possible reasons like ACL drop in egress or a policer drop in egress. Discards caused by congestion at queues and drops at queues are not counted under unknown discards. |
Unicast Queue Drops | Packets dropped in the unicast queues because of congestion. |
Multicast Queue Drops | Packets dropped in the multicast queues because of congestion. |
Total Discards | Total number of egress dropped packets. |
show interface counters protocol
Use this command to display protocol packets received at the CPU by the control plane.
Command Syntax
show interface (IFNAME|) counters protocol
Parameters
IFNAME
Interface name.
Command Mode
Exec mode and Privileged Exec mode
Applicability
This command was introduced before OcNOS version 1.3.
This command is not available on Qumran platforms.
Example
#show interface counters protocol
Interface ce1/1
lacp : 4
icmp6 : 5
Table 20-48 explain the fields in the command output.
Table 20-48: show interface counters protocol output details
Field | Description |
Interface | Name of the configured interface. |
lacp | Total number of lacp protocol in the interface. |
icmp6 | Total number of icmp6 protocol in the interface. |
show interface counters queue-drop-stats
Use this command to display dropped packets in the CPU queue and the last increment time.
Command Syntax
show interface cpu counters queue-drop-stats
Parameters
cpu
CPU interface.
Command Mode
Exec mode and Privileged Exec mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
show interface cpu counters queue-drop-stats
+-------------------+----------------+----------------+---------------------+
| Queue Name | Count | Last Increment | Last Increment Time |
+-------------------+----------------+----------------+---------------------+
arp 169735545 9145653 2017 Oct 23 14:33:54
Table 20-49 explain the fields in the command output.
Table 20-49: show interface counters queue-drop-stats output details
Field | Description |
Queue Name | Name of the protocol. |
Count | Number of arp protocols in the interface. |
Last Increment | Final increment number in the protocol. |
Last Increment time | Time of the last increment in the protocol. |
show interface counters queue-stats
Use this command to display transmitted and dropped packet and byte counts of individual queues.
Note: In Qumran devices, all packets dropped in a queue are counted (even policer drops).
Command Syntax
show interface (IFNAME|) counters queue-stats
show interface cpu counters queue-stats
Parameters
IFNAME
Interface name.
cpu
CPU interface.
Command Mode
Exec mode and Privileged Exec mode
Applicability
This command was introduced before OcNOS version 1.3.
Note: Default traffic counters are not supported on Qumran AX.
Example
#show interface counters queue-stats
D - Default Queue, U - User-defined Queue
+--------+----------------+------+-----------+------------+------------+---------------+
|Interface|Queue/Class-map|Q-Size|Output pkts|Output bytes|Dropped pkts|Dropped bytes |
+--------+----------------+------+-----------+------------+------------+---------------+
xe1/1 q1 (D) 0 12 1368 0 0
xe1/1 mc-q7 (D) 0 1 82 0 0
xe25 q1 (D) 0 6 684 0 0
#show interface xe1/1 counters queue-stats
D - Default Queue, U - User-defined Queue
+---------------+------+-------+- -------+------------+--------------+
|Queue/Class-map|Q-Size|Tx pkts| Tx bytes |Dropped pkts|Dropped bytes |
+---------------+------+-------+----------+------------+--------------+
q0 (D) 0 0 0 0 0
q1 (D) 0 12 1368 0 0
q2 (D) 0 0 0 0 0
q3 (D) 0 0 0 0 0
q4 (D) 0 0 0 0 0
q5 (D) 0 0 0 0 0
q6 (D) 0 0 0 0 0
q7 (D) 0 0 0 0 0
mc-q0 (D) 0 0 0 0 0
mc-q1 (D) 0 0 0 0 0
mc-q2 (D) 0 0 0 0 0
mc-q3 (D) 0 0 0 0 0
mc-q4 (D) 0 0 0 0 0
mc-q5 (D) 0 0 0 0 0
mc-q6 (D) 0 0 0 0 0
mc-q7 (D) 0 1 82 0 0
#show interface cpu counters queue-stats
E - Egress, I - Ingress, Q-Size is in bytes
+--------------------+--------+-----------------+-------------------+-----------------+-------------------+
| Queue/Class-map | Q-Size | Tx pkts | Tx bytes | Dropped pkts | Dropped bytes |
+--------------------+--------+-----------------+-------------------+-----------------+-------------------+
igmp (E) 800592 14519 987292 1304163 88683084
arp (E) 1250496 1008785 68597380 0 0
Table 20-50 explain the fields in the command output.
Table 20-50: queue flags detail
Flag | Meaning |
|---|
D | Default queue of the port. |
U | User defined queue of the port. |
E | Outgoing hello packet’s queue in the port. |
I | Incoming hello packet’s queue in the port. |
Q | Hello packet’s queue size in bytes. |
Table 20-51 explain the fields in the command output.
Table 20-51: show interface counters queue-stats output details
Field | Description |
|---|
Interface | A defined physical interface to which the queue is associated. |
Queue/Class-map | Queues associated with a QoS class-map. |
Q-Size | The size of a specified queue in bytes. |
Output pkts | The number of out bound packets residing in the queues. |
Output Bytes | The number of bytes in the outbound queue. |
Dropped pkts | The number of packets dropped because of queue overflow. |
Dropped bytes | The number of bytes dropped because of queue overflow. |
Tx pkts | The number of transmit packets contained in the out bound queue. |
Tx bytes | The number of transmit bytes contained in the out bound queue. |
show interface counters rate
Use this command to display the average traffic rate over the load interval of the interface.
Command Syntax
show interface (IFNAME|) counters rate (kbps|mbps|gbps|)
show interface cpu counters rate (kbps|mbps|gbps|)
Parameter
IFNAME
Interface name.
kbps
Kilobits per second.
mbps
Megabits per second.
gbps
Gigabits per second.
cpu
CPU interface.
Command Mode
Exec mode and Privileged Exec mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
#show interface counters rate
+-------------+---------------------------+-------------------------------+
| | Rx | Tx |
| Interface |---------------------------+-------------------------------|
| | bps | pps | bps | pps |
+-------------+---------------------------+-------------------------------+
xe1/1 548439552 1008160 544400 1000
#show interface cpu counters rate
Load interval: 30 second
+-------------------+--------------+-------------+--------------+-------------+
| CPU Queue(%) | Rx bps | Rx pps | Tx bps | Tx pps |
+-------------------+--------------+-------------+--------------+-------------+
isis ( 0%) - - 742 0
arp ( 0%) - - 6 0
Table 20-52 explain the fields in the command output.
Table 20-52: show interface counters rate output details
Field | Description |
|---|
Interface | The particular interface. |
RX | Number of hello packets received from the neighbor. |
TX | Number hello packets transmitted to the neighbor. |
bps | Bytes per second. |
pps | Packets per second. |
CPU Queue | CPU Queues used for various functions. In the example the CPU is maintaining queues for ARP and the IS-IS routing facilities. |
Load interval | The length of time for which data is used to compute load statistics. |
RX bps | Number of hello packets received from the neighbor in bytes per second. |
RX pps | Number of hello packets received from the neighbor in packets per second. |
TX bps | Number hello packets transmitted to the neighbor in bytes per second. |
Tx pps | Number hello packets transmitted to the neighbor in packets per second. |
show interface counters speed
Use this command to display the current average speed on the interface.
Command Syntax
show interface (IFNAME|) counters speed (kbps|mbps|gbps|)
Parameter
IFNAME
Interface name.
kbps
Kilobits per second.
mbps
Megabits per second.
gbps
Gigabits per second.
Command Mode
Exec mode and Privileged Exec mode
Applicability
This command was introduced in OcNOS-SP version 1.0.
Example
#show interface counters speed
* indicates monitor is active
+------------+--------------+--------------------+-------------------------------------------+
| | | Threshold(%) | Current average speed |
| interface | configured +--------------------+-------------+-------+-------------+-------+
| | speed ( bps) | Warning | Recovery | Rx ( bps) | % | Tx ( bps) | % |
+------------+--------------+---------+----------+-------------+-------+-------------+-------+
ce45 100000000000 90 80 0 0.00 0 0.00
xe7 10000000000 90 80 0 0.00 0 0.00
xe31 10000000000 90 80 0 0.00 0 0.00
xe33 10000000000 90 80 0 0.00 0 0.00
xe39 10000000000 90 80 0 0.00 0 0.00
xe40 10000000000 90 80 0 0.00 0 0.00
#
show interface counters summary
Use this command to display the summary of traffic counters on a specific interface or all interfaces.
Note: This command is supported for the out-of-band management (OOB) management interface.
Command Syntax
show interface (IFNAME|) counters summary
Parameter
IFNAME
Interface name.
Command Mode
Exec mode and Privileged Exec mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
#show interface xe1/1 counters summary
+-----------+-------------------------------+-------------------------------+
| | Rx | Tx |
| Interface |-------------------------------+-------------------------------|
| | packets | bytes | packets | bytes |
+-----------+---------------+---------------+---------------+---------------+
xe1/1 11032977 11032960000 61 3904
#show interface counters summary
+-------------+--------------------+--------------------+--------------------+--------------------+
| Interface | Rx packets | Rx bytes | Tx packets | Tx bytes |
+-------------+--------------------+--------------------+--------------------+--------------------+
eth0 206222 13756391 235123 337010937
po1 809121 72989094 825221 90605534
xe1/1 0 0 1 114
xe3/1 43 4730 21 2298
xe5/1 29 3178 21 2298
xe8 10 1076 14 1532
xe9/1 16 1760 21 2298
xe11/1 0 0 7 766
xe19/1 12426292 1298526692 6 620
xe21/1 13 1386 14 1532
xe28/1 3144 202370 21 2298
xe30/1 3161 202304 7 766
xe32/1 694067 61687838 710274 79315093
xe32/2 115054 11301256 114947 11290441
xe32/3 603759 51208946 620502 68865557
xe32/4 7 766 7 766
Table 20-53 explain the fields in the command output.
Table 20-53: show interface counters summary output details
Field | Description |
|---|
Interface | The particular interface. |
RX | Number of hello packets received from the neighbor. |
TX | Number hello packets transmitted to the neighbor. |
bps | Bytes per second. |
pps | Packets per second. |
RX bps | Number of hello packets received from the neighbor in bytes per second. |
RX pps | Number of hello packets received from the neighbor in packets per second. |
TX bps | Number hello packets transmitted to the neighbor in bytes per second. |
Tx pps | Number hello packets transmitted to the neighbor in packets per second. |
show interface fec
Use this command to display the FEC (forward error correction) statistics for an interface.
Note: You can only display FEC statistics for physical interfaces and not for management or logical interfaces.
Command Syntax
show interface (IFNAME|) fec
Parameters
IFNAME
Physical Interface name.
Default
None
Command Mode
Exec and Privileged Exec mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
#sh int ce54 fec
+-------------+--------+-----------+-------------+----------------------+------------------------+
| Interface | Config | HW Status | Oper Status | Corrected Block Count| Uncorrected Block Count|
+-------------+--------+-----------+-------------+----------------------|------------------------+
ce54 on cl91 cl91 0 12
#sh int ce53 fec
+-------------+--------+-----------+-------------+----------------------+------------------------+
| Interface | Config | HW Status | Oper Status | Corrected Block Count| Uncorrected Block Count|
+-------------+--------+-----------+-------------+----------------------|------------------------+
ce53 auto cl91 cl91 0 0
#sh int ce52 fec
+-------------+--------+-----------+-------------+----------------------+------------------------+
| Interface | Config | HW Status | Oper Status | Corrected Block Count| Uncorrected Block Count|
+-------------+--------+-----------+-------------+----------------------|------------------------+
ce52 off off off 0 0
Table 20-48 explain the fields in the command output.
Table 20-54: show interface fec
Field | Description |
Interface | Name of the configured interface. |
config | Configured value. |
HW Status | FEC currently programmed in HW. |
Oper Status | FEC currently operating over the link. |
Corrected Block Count | Number of the corrected block count. |
Uncorrected Block Count | Number of the uncorrected block count. |
show ip forwarding
Use this command to display the IP forwarding status.
Command Syntax
show ip forwarding
Parameters
None
Command Mode
Exec mode and Privileged Exec mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
The following is a sample output of the show ip forwarding command displaying the IP forwarding status.
#show ip forwarding
vrf (management) :IP forwarding is on
vrf (default) :IP forwarding is on
#
Table 20-55 explain the fields in the command output.
Table 20-55: show ip forwarding
Field | Description |
vrf (management) | Management VRF is for management purposes. IP forwarding packet is on. |
vrf (default) | The default VRF uses the default routing context for ip forwarding. IP forwarding packet is on. |
show ip interface
Use this command to display brief information about interfaces and the IP addresses assigned to them. To display information about a specific interface, specify the interface name with the command.
Command Syntax
show ip interface brief
show ip interface IFNAME brief
Parameters
IFNAME
Interface name.
brief
Brief summary of IP status and configuration.
Command Mode
Exec mode and Privileged Exec mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
The following is a sample output from the show ip interface brief command:
#show ip interface brief
'*' - address is assigned by dhcp client
Interface IP-Address Admin-Status Link-Status
eth0 *10.10.26.101 up up
lo 127.0.0.1 up up
lo.management 127.0.0.1 up up
xe1/1 10.1.1.1 up up
xe1/2 unassigned down down
xe1/3 unassigned down down
xe1/4 unassigned down down
xe2 unassigned up down
xe3/1 unassigned up up
xe3/2 unassigned down down
xe3/3 unassigned down down
Table 20-56 explain the fields in the command output.
Table 20-56: show ip interface output details
Field | Description |
|---|
Interface | Interface name, also specifies interface type (eth0, lo, xe1/1, and xe1/2). |
IP-Address | The IP address assigned to the interface. An asterisks indicates that the IP address was provided by DHCP. |
Admin-Status | Interface is up and functioning or down. |
Link-Status | Interface is connected and passing traffic. |
show ip prefix-list
Use this command to display the prefix list entries for IPv4 interfaces.
Syntax Description
show ip prefix-list
show ip prefix-list WORD
show ip prefix-list WORD seq <1-4294967295>
show ip prefix-list WORD A.B.C.D/M
show ip prefix-list WORD A.B.C.D/M longer
show ip prefix-list WORD A.B.C.D/M first-match
show ip prefix-list summary
show ip prefix-list summary WORD
show ip prefix-list detail
show ip prefix-list detail WORD
Parameters
WORD
Name of a prefix list.
A.B.C.D/M
IP prefix <network>/<length> (for example, 35.0.0.0/8).
first-match
First matched prefix.
longer
Lookup longer prefix.
<1-4294967295>
Sequence number.
detail
Detail of prefix lists.
summary
Summary of prefix lists.
Command Mode
Privileged Exec mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
The following is a sample output of the show ip prefix-list command showing prefix-list entries.
#show ip prefix-list
ip prefix-list myPrefixList: 3 entries
seq 5 permit 172.1.1.0/16
seq 10 permit 173.1.1.0/16
seq 15 permit 174.1.1.0/16
show ip route
Use this command to display the IP routing table for a protocol or from a particular table.
When multiple entries are available for the same prefix, NSM uses an internal route selection mechanism based on protocol administrative distance and metric values to choose the best route. All best routes are entered into the FIB and can be viewed using this command. To display all routes (selected and not selected), use the show ip route database command.
Use this command to see all subnets of a specified network if they are present in the routing table. Please use this command with mask information.
Command Syntax
show ip route A.B.C.D
show ip route (database|)
show ip route (database|) (bgp|connected|database|isis|fast-reroute|interface|isis|kernel|mbgp|mstatic|next-hop|ospf|rip|static)
show ip route summary
show ip route vrf WORD (database|)
show ip route vrf WORD (database|) (bgp|connected|isis|kernel|ospf|rip|static)
Parameters
A.B.C.D
Network in the IP routing table.
A.B.C.D/M
IP prefix <network>/<length>, for example, 35.0.0.0/8.
bgp
Border Gateway Protocol.
connected
Connected.
database
Routing table database.
fast-reroute
Fast reroute repair paths.
interface
Interface.
isis
IS-IS.
kernel
Kernel.
mbgp
Multiprotocol BGP routes.
mstatic
Multicast static routes.
next-hop
Next hop address.
ospf
Open Shortest Path First.
rip
Routing Information Protocol.
static
Static routes.
summary
Summarize all routes.
WORD
Routes for a Virtual Routing/Forwarding instance.
Command Mode
Exec mode and Privileged Exec mode
Applicability
This command was introduced before OcNOS version 1.3.
Example: Display FIB Routes
The following shows output for the best routes.
#show ip route
Codes: K - kernel, C - connected, S - static, R - RIP, B - BGP
O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
E - EVPN,
v - vrf leaked
* - candidate default
show ip route A.B.C.D/M longer-prefixes
Use this command to see all subnets of a specified network if they are present in the routing table. Please use this command with mask information.
Command Syntax
show ip route A.B.C.D/M longer-prefixes
Parameters
A.B.C.D/M
Command Mode
Exec-mode and Privileged exec-mode
Applicability
This command was introduced from OcNOS 1.3.6
Example
OcNOS#sh ip route
Codes: K - kernel, C - connected, S - static, R - RIP, B - BGP
O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2,
ia - IS-IS inter area, E - EVPN,
v - vrf leaked
- candidate default
IP Route Table for VRF "default"
C 10.1.1.0/24 is directly connected, eth1, 00:00:23
C 10.12.41.0/24 is directly connected, eth0, 00:00:23
S 55.0.0.0/8 [1/0] is directly connected, eth1, 00:00:23
S 55.0.0.0/12 [1/0] is directly connected, eth1, 00:00:23
S 55.0.0.0/24 [1/0] is directly connected, eth1, 00:00:23
S 55.1.0.0/16 [1/0] is directly connected, eth1, 00:00:23
S 55.1.1.0/24 [1/0] is directly connected, eth1, 00:00:23
C 127.0.0.0/8 is directly connected, lo, 00:00:23
Gateway of last resort is 10.30.0.11 to network 0.0.0.0
K* 0.0.0.0/0 via 10.30.0.11, eth0
O 9.9.9.9/32 [110/31] via 10.10.31.16, eth2, 00:18:56
K 10.10.0.0/24 via 10.30.0.11, eth0
C 10.10.31.0/24 is directly connected, eth2
S 10.10.34.0/24 [1/0] via 10.10.31.16, eth2
O 10.10.37.0/24 [110/11] via 10.10.31.16, eth2, 00:20:54
C 10.30.0.0/24 is directly connected, eth0
S 11.22.11.0/24 [1/0] via 10.10.31.16, eth2
O E2 14.5.1.0/24 [110/20] via 10.10.31.16, eth2, 00:18:56
S 16.16.16.16/32 [1/0] via 10.10.31.16, eth2
O 17.17.17.17/32 [110/31] via 10.10.31.16, eth2, 00:20:54
C 45.45.45.45/32 is directly connected, lo
O 55.55.55.55/32 [110/21] via 10.10.31.16, eth2, 00:20:54
C 127.0.0.0/8 is directly connected, lo
OcNOS#sh ip route 55.0.0.0/7 longer-prefixes
Routing entry for 55.0.0.0/8
Known via "static", distance 1, metric 0, External Route Tag: 0, best
directly connected, eth1
Routing entry for 55.0.0.0/12
Known via "static", distance 1, metric 0, External Route Tag: 0, best
directly connected, eth1
Routing entry for 55.0.0.0/24
Known via "static", distance 1, metric 0, External Route Tag: 0, best
directly connected, eth1
Routing entry for 55.1.0.0/16
Known via "static", distance 1, metric 0, External Route Tag: 0, best
directly connected, eth1
Routing entry for 55.1.1.0/24
Known via "static", distance 1, metric 0, External Route Tag: 0, best
directly connected, eth1
OcNOS#sh ip route 55.0.0.0/8 longer-prefixes
Routing entry for 55.0.0.0/8
Known via "static", distance 1, metric 0, External Route Tag: 0, best
directly connected, eth1
Routing entry for 55.0.0.0/12
Known via "static", distance 1, metric 0, External Route Tag: 0, best
directly connected, eth1
Routing entry for 55.0.0.0/24
Known via "static", distance 1, metric 0, External Route Tag: 0, best
directly connected, eth1
Routing entry for 55.1.0.0/16
Known via "static", distance 1, metric 0, External Route Tag: 0, best
directly connected, eth1
Routing entry for 55.1.1.0/24
Known via "static", distance 1, metric 0, External Route Tag: 0, best
directly connected, eth1
OcNOS#
OcNOS#sh ip route 55.0.0.0/11 longer-prefixes
Routing entry for 55.0.0.0/12
Known via "static", distance 1, metric 0, External Route Tag: 0, best
directly connected, eth1
Routing entry for 55.0.0.0/24
Known via "static", distance 1, metric 0, External Route Tag: 0, best
directly connected, eth1
Routing entry for 55.1.0.0/16
Known via "static", distance 1, metric 0, External Route Tag: 0, best
directly connected, eth1
Routing entry for 55.1.1.0/24
Known via "static", distance 1, metric 0, External Route Tag: 0, best
directly connected, eth1
OcNOS#
OcNOS#
OcNOS#
OcNOS#sh ip route 55.0.0.0/16 longer-prefixes
Routing entry for 55.0.0.0/24
Known via "static", distance 1, metric 0, External Route Tag: 0, best
directly connected, eth1
OcNOS#sh ip route 55.1.0.0/16 longer-prefixes
Routing entry for 55.1.0.0/16
Known via "static", distance 1, metric 0, External Route Tag: 0, best
directly connected, eth1
Routing entry for 55.1.1.0/24
Known via "static", distance 1, metric 0, External Route Tag: 0, best
directly connected, eth1
OcNOS#sh ip route 55.1.0.0/20 longer-prefixes
Routing entry for 55.1.1.0/24
Known via "static", distance 1, metric 0, External Route Tag: 0, best
directly connected, eth1
OcNOS#sh ip route 55.1.0.0/24 longer-prefixes
% Network not in table
OcNOS#
OcNOS#
OcNOS#
OcNOS#sh ip route 55.1.1.0/24 longer-prefixes
Routing entry for 55.1.1.0/24
Known via "static", distance 1, metric 0, External Route Tag: 0, best
directly connected, eth1
OcNOS#
Header
Each entry in this table has a code preceding it, indicating the source of the routing entry. For example, O indicates OSPF as the origin of the route and K indicates that the route has been learned from the kernel.
Table 20-57 shows these codes and modifiers.
Table 20-57 explain the fields in the command output.
Table 20-57: route codes and modifiers
Code | Meaning | Description |
|---|
K | kernel | Routes added through means other than by using the CLI; for example by using the operating system route command. Static routes added using kernel commands and static routes added using OcNOS commands are different. The kernel static routes are not redistributed when you give the redistribute static command in a protocol. However, the kernel static routes can be redistributed using the redistribute kernel command. |
C | connected | Routes directly connected to the local device that were not distributed via IGP. The device inherently knows of these networks, so there is no need to learn about these from another device. Connected routes are preferred over routes for the same network learned from other routing protocols. Routes for connected networks always exist in the kernel routing table but as an exception are not marked as kernel routes because OcNOS always calculates entries for these routes upon learning interface information from the kernel. |
S | static | Routes manually configured via CLI which are not updated dynamically by IGPs. |
The codes below are for routes received and dynamically learned via IGP neighbors. These networks are not directly connected to this device and were announced by some other device on the network. IGPs update these routes as the network topology changes. |
R | RIP | RIP routing process and enter Router mode. |
B | BGP | Route is from an Border Gateway Protocol. |
O | OSPF | Modifiers for OSPF: IA - OSPF inter area N1 - OSPF NSSA external type 1 N2 - OSPF NSSA external type 2 E1 - OSPF external type 1 E2 - OSPF external type 2 |
i | IS-IS | Modifiers for IS-IS: L1 - IS-IS level-1 L2 - IS-IS level-2 ia - IS-IS inter area |
Other modifiers: |
v | vrf leaked | The device has two or more VRFs configured and each has at least one interface bound to it. While each VRF will have its own routing table, the VRFs can learn each other’s routes. |
* | candidate default | Route has been added to the FIB. With equal cost paths to a destination, the router does per-packet or per-destination load sharing. An asterisk ("*") means that the route is being used at that instant for forwarding packets. If you run the same show ip route x.x.x.x command over and over, you might see the * moving between the route entries. |
> | selected route | When multiple routes are available for the same prefix, the best route. When multiple entries are available for the same prefix, OcNOS uses an internal route selection mechanism based on protocol administrative distance and metric values to choose the best route. OcNOS populates the FIB with the best route to each destination |
p | stale info | A route information that is marked stale due to graceful restart. |
After the codes, the header has default gateway information:
Gateway of last resort is 10.12.4.1 to network 0.0.0.0
The “gateway of last resort”, also called the default gateway, is a static route that routes IP address 0.0.0.0 (all destinations) through a single host (the gateway). The effect of setting a gateway is that if no routing table entry exists for a destination address, packets to that address will be forwarded to the gateway router.
Route Entry Fields
Table 20-58 explains the each route entry fields.
Table 20-58: route entry output details
Field | Description |
|---|
Codes and modifiers | As explained in Table 20-57. |
IP address | IP address of the remote network. |
Administrative distance and metric | The administrative distance determines how trustworthy this route is. If there is a similar route but with a smaller administrative distance, it is used instead, because it is more “trustworthy”. The smaller the administrative distance, the more trustworthy the route. Directly connected routes have an administrative distance of 0, which makes them the most trustworthy type of route.The metric varies from protocol to protocol, and for OSPF the metric is cost, which indicates the best quality path to use to forward packets. Other protocols, like RIP, use hop count as a metric. For neighboring routers, the metric value is 1. |
Next hop router IP address | This route is available through the next hop router located at this IP address. This identifies exactly where packets go when they match this route. |
Outgoing interface name | Interface used to get to the next-hop address for this route. |
Duration | Length of time that this route has been present in the routing table. This is also the length of time this route has existed without an update. If the route were removed and then re-added (if the cable was disconnected, for instance), this timer would begin again at 00:00:00. |
Route Entry Examples
O 10.10.37.0/24 [110/11] via 10.10.31.16, eth2, 00:20:54
• This route in the network 10.10.37.0/24 was added by OSPF.
• This route has an administrative distance of 110 and metric/cost of 11.
• This route is reachable via nexthop 10.10.31.16.
• The outgoing local interface for this route is eth2.
• This route was added 20 minutes and 54 seconds ago.
O E2 14.5.1.0/24 [110/20] via 10.10.31.16, eth2, 00:18:56
• This route is the same as the other OSPF route above; the only difference is that it is a Type 2 External OSPF route.
C 10.10.31.0/24 is directly connected, eth2
• This route is directly connected.
• Route entries for network 10.10.31.0/24 are derived from the IP address of local interface eth2.
K 10.10.0.0/24 via 10.30.0.11, eth0
• This route in the network 10.10.0.0/24 was learned from the kernel routing table (route was statically added using kernel commands).
• This route is reachable via nexthop 10.30.0.11.
• The outgoing local interface for this route is eth0.
K* 0.0.0.0/0 via 10.30.0.11, eth0
• This is a default route that was learned from the kernel (route was statically added using kernel commands).
• This route is reachable via nexthop 10.30.0.11.
• The local interface for this route is eth0.
Example: Display OSPF Routes
The following is the output with the ospf parameter:
#show ip route ospf
O 1.1.1.0/24 [110/20] via 2.2.2.1, eth2, 00:00:44
O IA 4.4.4.0/24 [110/21] via 2.2.2.1, eth2, 00:00:44
#
Example: Display Route Summary
The following is the output with the summary parameter.
#show ip route summary
IP routing table name is Default-IP-Routing-Table(0)
IP routing table maximum-paths is 4
Route Source Networks
kernel 1
connected 5
ospf 2
Total 8
FIB 2
Example: Display RIB Routes
The following shows displaying database routes.
#show ip route database
Codes: K - kernel, C - connected, S - static, R - RIP, B - BGP
O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
> - selected route, * - FIB route, p - stale info
K *> 0.0.0.0/0 via 10.30.0.11, eth0
O *> 9.9.9.9/32 [110/31] via 10.10.31.16, eth2, 00:19:21
K *> 10.10.0.0/24 via 10.30.0.11, eth0
O 10.10.31.0/24 [110/1] is directly connected, eth2, 00:28:20
C *> 10.10.31.0/24 is directly connected, eth2
S *> 10.10.34.0/24 [1/0] via 10.10.31.16, eth2
O 10.10.34.0/24 [110/31] via 10.10.31.16, eth2, 00:21:19
O *> 10.10.37.0/24 [110/11] via 10.10.31.16, eth2, 00:21:19
K * 10.30.0.0/24 is directly connected, eth0
C *> 10.30.0.0/24 is directly connected, eth0
S *> 11.22.11.0/24 [1/0] via 10.10.31.16, eth2
O E2 *> 14.5.1.0/24 [110/20] via 10.10.31.16, eth2, 00:19:21
O 16.16.16.16/32 [110/11] via 10.10.31.16, eth2, 00:21:19
S *> 16.16.16.16/32 [1/0] via 10.10.31.16, eth2
O *> 17.17.17.17/32 [110/31] via 10.10.31.16, eth2, 00:21:19
C *> 45.45.45.45/32 is directly connected, lo
O *> 55.55.55.55/32 [110/21] via 10.10.31.16, eth2, 00:21:19
K * 127.0.0.0/8 is directly connected, lo
C *> 127.0.0.0/8 is directly connected, lo
The codes and modifier at the start of each route entry are explained in
Table 20-57.
Routes in the FIB are marked with a *. When multiple routes are available for the same prefix, the best route is indicated with the > symbol. Unselected routes have neither the * nor the > symbol.
Route Database Entry Examples
This example shows 2 entries in the route database; one learned from the kernel and the other derived from interface information.
K * 10.30.0.0/24 is directly connected, eth0
C *> 10.30.0.0/24 is directly connected, eth0
• Both these routes are in the same network 10.30.0.0/24.
• The first route has originated from the kernel. The * indicates that it has been added to the FIB.
• The second route is derived from the IP address of local interface eth0. It is marked as a connected route. Since a connected route has the lowest administrative distance, it is the selected route.
S *> 10.10.34.0/24 [1/0] via 10.10.31.16, eth2
O 10.10.34.0/24 [110/31] via 10.10.31.16, eth2, 00:21:19
• The same prefix was learned from OSPF and from static route configuration.
• Static routes are preferred over OSPF routes, so the static route is selected and installed in the FIB.
Note: If the static route becomes unavailable, OcNOS automatically selects the OSPF route and installs it in the FIB.
Example: Display VRF Routes
The following is the output with the vrf parameter:
#show ip route vrf vrf31
Codes: K - kernel, C - connected, S - static, R - RIP, B - BGP
O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2,
ia - IS-IS inter area, E - EVPN,
v - vrf leaked
* - candidate default
IP Route Table for VRF "vrf31"
O 2.2.2.2/32 [110/2] via 21.1.1.2, vlan1.4, 00:01:29
O 10.1.1.0/24 [110/2] via 21.1.1.2, vlan1.4, 00:01:29
O 20.1.1.0/24 [110/2] via 21.1.1.2, vlan1.4, 00:01:29
C 21.1.1.0/24 is directly connected, vlan1.4, 00:02:54
C 31.31.1.1/32 is directly connected, lo.vrf31, 00:03:02
O 40.40.1.1/32 [110/3] via 21.1.1.2, vlan1.4, 00:00:43
C 127.0.0.0/8 is directly connected, lo.vrf31, 00:03:05
Gateway of last resort is not set
The following is the output with the vrf database parameter:
#show ip route vrf vrf31 database
Codes: K - kernel, C - connected, S - static, R - RIP, B - BGP
O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2,
ia - IS-IS inter area, E - EVPN,
v - vrf leaked
> - selected route, * - FIB route, p - stale info
IP Route Table for VRF "vrf31"
O *> 2.2.2.2/32 [110/2] via 21.1.1.2, vlan1.4, 00:01:32
O *> 10.1.1.0/24 [110/2] via 21.1.1.2, vlan1.4, 00:01:32
O *> 20.1.1.0/24 [110/2] via 21.1.1.2, vlan1.4, 00:01:32
C *> 21.1.1.0/24 is directly connected, vlan1.4, 00:02:57
O 21.1.1.0/24 [110/1] is directly connected, vlan1.4, 00:02:57
C *> 31.31.1.1/32 is directly connected, lo.vrf31, 00:03:05
O 31.31.1.1/32 [110/1] is directly connected, lo.vrf31, 00:03:00
O *> 40.40.1.1/32 [110/3] via 21.1.1.2, vlan1.4, 00:00:46
B > 50.1.1.0/24 [200/0] via 41.41.41.41, 00:00:18
C *> 127.0.0.0/8 is directly connected, lo.vrf31, 00:03:08
Gateway of last resort is not set
show ip vrf
This command displays routing information about VRFs.
Command Syntax
show ip vrf
show ip vrf WORD
Parameter
WORD
Virtual Routing and Forwarding name.
Command Mode
Exec mode and Privileged Exec mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
#show ip forwarding
vrf (management) :IP forwarding is on
vrf (default) :IP forwarding is on
show ipv6 forwarding
Use this command to display the IPv6 forwarding status.
Command Syntax
show ipv6 forwarding
Parameters
None
Command Mode
Exec mode and Privileged Exec mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
The following is a sample output of the show ipv6 forwarding command displaying the IPv6 forwarding status.
#show ipv6 forwarding
vrf (management) :IPv6 forwarding is on
vrf (default) :IPv6 forwarding is on#
show ipv6 interface brief
Use this command to display information about interfaces. To display information about a specific interface, include the interface name.
Command Syntax
show ipv6 interface brief
show ipv6 interface IFNAME brief
Parameters
IFNAME
Name of the interface.
Command Mode
Exec mode and Privileged Exec mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
#show ipv6 interface brief
Interface IPv6-Address Admin-Status
lo ::1 [up/up]
gre0 unassigned [admin down/down]
eth3 3ffe:abcd:104::1 [up/up]
3ffe:abcd:103::1
fe80::2e0:29ff:fe6f:cf0
eth1 fe80::260:97ff:fe20:f257 [up/up]
eth2 unassigned [admin down/down]
eth3 unassigned [admin down/down]
sit0 unassigned [admin down/down]
tun24 unassigned [admin down/down]
tunl0 unassigned [admin down/down]
Table 20-59 explains the each interface brief entry.
Table 20-59: show interface brief output details
Field | Description |
|---|
Interface | Name of the interface. |
IPv6-Address | IPv6 address. An asterisk (“*”) means the address was assigned by the DHCPv6 client. |
Admin-Status | Status of the interface: The first part of the field indicates if the interface is up. The second part indicates if the interface is running. |
show ipv6 route
Use this command to display the IP routing table for a protocol or from a particular table, including database entries known by NSM. When multiple entries are available for the same prefix, NSM uses an internal route selection mechanism based on protocol administrative distance and metric values to choose the best route. The best routes in the FIB can be viewed using show ipv6 route.
Command Syntax
show ipv6 route vrf WORD (database|)
show ipv6 route vrf WORD (database|) (bgp|connected|isis|kernel|ospf|rip|static)
show ipv6 route (database)
show ipv6 route (database) (bgp|connected|isis|kernel|ospf|rip|static)
show ipv6 route X:X::X:X
show ipv6 route X:X::X:X/M
show ipv6 route summary
Parameters
X:X::X:X
Network in the IP routing table.
X:X::X:X/M
Prefix <network>/<length>, e.g., 35.0.0.0/8
all
All IPv6 routes
bgp
Border Gateway Protocol.
connected
Connected.
database
IPv6 routing table database.
isis
IS-IS.
IFNAME
Interface name
kernel
Kernel.
ospf
Open Shortest Path First.
rip
Routing Information Protocol.
static
Static routes.
summary
Summarize all routes
WORD
Routes from a Virtual Routing and Forwarding instance
Command Mode
Exec mode and Privileged Exec mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
See
Table 20-57 and
Table 20-58 for an explanation of the codes and fields in the output.
#show ipv6 route
Codes: K - kernel route, C - connected, S - static, R - RIPng, O - OSPFv3,
I - IS-IS, B - BGP, > - selected route, * - FIB route, p - stale info.
C> * ::1/128 is directly connected, lo
C> * 3ffe:1::/48 is directly connected, eth1
C> * 3ffe:2:2::/48 is directly connected, eth2
#
show ipv6 prefix-list
Use this command to display the prefix list entries for IPv6 interfaces.
Syntax Description
show ipv6 prefix-list
show ipv6 prefix-list WORD
show ipv6 prefix-list WORD seq <1-4294967295>
show ipv6 prefix-list WORD X:X::X:X/M
show ipv6 prefix-list WORD X:X::X:X/M longer
show ipv6 prefix-list WORD X:X::X:X/M first-match
show ipv6 prefix-list summary
show ipv6 prefix-list summary WORD
show ipv6 prefix-list detail
show ipv6 prefix-list detail WORD
Parameters
WORD
Name of prefix list.
X:X::X:X/M
IP prefix <network>/<length> (for example, 35.0.0.0/8).
first-match
First matched prefix.
longer
Look up longer prefix.
<1-4294967295>
Sequence number of an entry.
detail
Detail of prefix lists.
summary
Summary of prefix lists.
Command Mode
Privileged Exec mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
The following is a sample output of the show ip prefix-list command showing prefix-list entries.
#show ip prefix-list
ip prefix-list myPrefixList: 3 entries
seq 5 permit 172.1.1.0/16
seq 10 permit 173.1.1.0/16
seq 15 permit 174.1.1.0/16
show hosts
Use this command to display the IP domain-name, lookup style and any name server.
Command Syntax
show hosts
Parameters
None
Command Mode
Exec mode and Privileged Exec mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
#show hosts
VRF: management
DNS lookup is enabled
Default domain : .com
Additional Domain : .in .ac
Name Servers : 10.12.3.23
Host Address
---- -------
test 10.12.12.67
test 10::23
* - Values assigned by DHCP Client.
Table 20-60 explains the output fields.
Table 20-60: show hosts fields
Entry | Description |
|---|
VRF: management | DNS configuration of specified VRF |
DNS lookup is enabled | DNS feature enabled or disabled |
Default domain | Default domain name used to complete unqualified host names (names without a dotted decimal domain name). |
Additional Domain | A list of default domain names used to complete unqualified host names. Each domain in the list is to be tried in turn. |
Name Servers | DNS server addresses that are used to translate hostnames to IP addresses. |
Host Address test 10.12.12.67 test 10::23 | Static hostname-to-address mappings in DNS. |
* - Values assigned by DHCP Client. | * in name-server indicates it has been learned dynamically. |
show running-config interface
Use this command to show the running system status and configuration for a specified interface, or a specified interface for a specified protocol.
Command Syntax
show running-config interface IFNAME
show running-config interface IFNAME bridge
show running-config interface IFNAME ip igmp
show running-config interface IFNAME ip multicast
show running-config interface IFNAME ip pim
show running-config interface IFNAME ipv6 ospf
show running-config interface IFNAME ipv6 rip
show running-config interface IFNAME ipv6 pim
show running-config interface IFNAME isis
show running-config interface IFNAME lacp
show running-config interface IFNAME ldp
show running-config interface IFNAME mpls
show running-config interface IFNAME mstp
show running-config interface IFNAME ospf
show running-config interface IFNAME ptp
show running-config interface IFNAME rip
show running-config interface IFNAME rstp
show running-config interface IFNAME rsvp
show running-config interface IFNAME stp
show running-config interface IFNAME synce
Parameters
bridge
Bridge.
ip
ipv6
isis
Intermediate System to Intermediate System.
lacp
Link Aggregation Control Protocol.
ldp
Label Distribution Protocol.
mpls
Multi-Protocol Label Switching.
mstp
Multiple Spanning Tree Protocol.
ospf
Open Shortest Path First.
ptp
Precision Time Protocol.
rip
Routing Information Protocol.
rstp
Rapid Spanning Tree Protocol.
rsvp
Resource Reservation Protocol.
stp
Spanning Tree Protocol.
synce
Synchronous Ethernet.
Command Mode
Privileged Exec mode and Config Mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
#show running-config interface eth1 bridge
!
interface eth1
switchport
bridge-group 1
switchport mode access
user-priority 3
traffic-class-table user-priority 2 num-traffic-classes 3 value 3 traffic-class-table user-priority 7 num-traffic-classes 1 value 2 traffic-class-table user-priority 7 num-traffic-classes 2 value 0 traffic-class-table user-priority 7 num-traffic-classes 3 value 0 traffic-class-table user-priority 7 num-traffic-classes 4 value 0 traffic-class-table user-priority 7 num-traffic-classes 5 value 0 traffic-class-table user-priority 7 num-traffic-classes 6
show running-config interface ip
Use this command to show the running system status and configuration for a specified IP.
Command Syntax
show running-config interface IFNAME ip (igmp|multicast|pim|)
Parameters
IFNAME
Interface name.
igmp
Internet Group Management Protocol.
multicast
Multicast.
pim
Protocol Independent Multicast.
Command Mode
Privileged Exec mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
#show running-config interface eth1 ip igmp
!
interface eth1
switchport
show running-config interface ipv6
Use this command to show the running system status and configuration for a specified IPv6 protocol.
Command Syntax
show running-config interface IFNAME ipv6 (mld|multicast|ospf|pim|rip|)
Parameters
IFNAME
Interface name.
mld
Multicast Listener Discovery
multicast
Multicast
ospf
Open Shortest Path First
pim
Protocol Independent Multicast
rip
Routing Information Protocol
Command Mode
Privileged Exec mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
#show running-config interface eth1 ipv6 rip
!
interface eth1
switchport
show running-config ip
Use this command to show the running system of IP configurations.
Command Syntax
show running-config ip (dhcp|mroute|route)
Parameters
dhcp
Dynamic Host Configuration Protocol.
mroute
Static IP multicast route.
route
Static IP route.
Command Mode
Privileged Exec mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
>enable
#show running-config ip route
!
ip route 3.3.3.3/32 eth3
ip route 3.3.3.3/32 eth2
ip route 200.0.0.0/16 lo
!
show running-config ipv6
Use this command to show the running system status and configuration for IPv6.
Command Syntax
show running-config ipv6 (access-list|mroute|neighbor|prefix-list|route|)
Parameters
access-list
Access list.
mroute
Static IPv6 Multicast route.
neighbor
Static IPv6 neighbor entry.
prefix-list
IPv6 prefix-list.
route
Static IPv6 route.
Command Mode
Privileged Exec mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
>enable
#show running-config ipv6 access-list
!
ipv6 access-list abc permit any
!
#show running-config ipv6 prefix-list
!
ipv6 prefix-list sde
seq 5 permit any
!
#show running-config ipv6 route
!
ipv6 route 3e11::/64 lo
ipv6 route 3e11::/64 eth2
ipv6 route fe80::/64 eth2
!
show running-config prefix-list
Use this command to display the running system status and configuration details for prefix lists.
Command Syntax
show running-config prefix-list
Parameters
None
Command Mode
Privileged exec mode, configure mode, router-map mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
>enable
(config)#show running-config prefix-list
!
ip prefix-list abc
seq 5 permit any
!
ip prefix-list as
description annai
!
ip prefix-list wer
seq 45 permit any
!
(config)#
shutdown
Use this command to shut down an interface.
Use the no form of this command to bring up an interface.
Command Syntax
shutdown
no shutdown
Parameters
None
Default
No default value is specified
Command Mode
Interface mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
The following example shows the use of the shutdown command to shut down the interface called eth3.
#configure terminal
(config)#interface eth3
(config-if)#shutdown
speed
Use this command to set the link speed of the interface.
Use the no parameter to set the speed to its default value.
On copper ports, auto-negotiation is enabled by default and force speed is not supported.
On fiber optic ports, auto-negotiation is disabled by default. Auto-negotiation is not supported on fiber optic medium/AOC for speeds 10g and beyond. IP Infusion Inc.does not recommend using auto speed on such transceivers. On DAC cables, both force and auto-negotiation are supported.
IP Infusion Inc. recommends configuring the same speed mode on both peers.
When an interface is configured with the speed auto option, the negotiated parameters are speed,
duplex,
flowcontrol, and
fec, each of which is configured separately. Please see the respective command for details.
Note: For 10g DAC/AOC, setting speed auto negotiates with a maximum of 1G.
Note: Interface speed setting is only supported on physical front-panel ports and not supported on Management interface eth0.
Note: Configuring or unconfiguring speed will reset FEC to auto mode.
Table 20-61 shows the IP Infusion Inc. recommendations regarding front-panel port speed and transceivers.
Table 20-61: Recommendatons
Suported/Recommended | Explanation |
|---|
Not Supported | When front panel port capability is less than the transceiver’s capability the behavior is undefined. |
Not Recommended | When the transceiver’s capability and front panel port capability is the same, reducing the speed is not recommended. |
Recommended | When the transceiver’s capability is less than the front panel port capability, the behavior is undefined and the link might even come up. So speed needs to be set to match the transceiver’s capability. |
Table 20-62 show examples with front-panel configurations:
Table 20-62: Front-panel configurations
Front Panel Port | Explanation |
|---|
Front Panel Port 100g | When 40g transceivers are used, make sure to use the command speed 40g. IP Infusion Inc. does not recommend using 40g on 100g speed transceivers. |
Front Panel Port 40g | 100g transceivers should not be used. |
Front Panel Port 25g | When 10g transceivers are used, make sure to use the port-group command to reduce the speed to 10g. IP Infusion Inc. does not recommend to use 10g on 25g speed transceivers. When using 1g transceivers, make sure to set the speed to 1g. Below 25g, port-speed can defer (10g or 1g) for ports under same port-group i.e. 1 port can have 1g & remaining 10g but 1 port 25g & remaining 10g not allowed. When "no speed" command is used at interface level it tries to set speed "25g" to one of the port of port-group while other may be at 10g or 1g speed which is not allowed. Use "no port-group" command in such case. |
Front Panel Port 10g | 25g transceivers should not be used. When using 1g transceivers, make sure to set the speed to 1g. |
Front Panel Port 1g | 10g/25g transceivers should not be used. |
Command Syntax
speed (10m | 100m | 1g | 2.5g | 10g | 20g | 25g | 40g | 50g | 100g | auto )
no speed
Parameter
10m
10 megabits
100m
100 megabits
1g
1 gigabit
2.5g
2.5 gigabits
10g
10 gigabits
20g
20 gigabits
25g
25 gigabits
40g
40 gigabits
50g
50 gigabits
100g
100 gigabits
auto
Negotiate the speed with a connected port
Default
No default value is specified
Command Mode
Interface mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
Enable auto-negotiation:
#configure terminal
(config)#interface xe0
(config-if)#speed auto
switchport
Use this command to set the mode of an interface to switched.
All interfaces are configured routed by default. To change the behavior of an interface from switched to routed, you must explicitly give the no switchport command.
Note: When you change the mode of an interface from switched to routed and vice-versa, all configurations for that interface are erased.
User should be prompted for confirmation, while executing switchport/no switchport command. To support this requirement, please refer the command enable/disable confirmation-dialog.
Use the no form of this command to set the mode to routed.
Command Syntax
switchport
no switchport
Parameters
None
Default
No default value is specified
Command Mode
Interface mode
Applicability
This command was introduced before OcNOS version 1.3.
Examples
#configure terminal
(config)#interface eth0
(config-if)#switchport
(config)#interface eth0
(config-if)#no switchport
#configure terminal
(config)#enable confirmation-dialog
(config)#interface xe5
(config-if)#switchport
Are you sure? (y/n): y
(config-if)#
(config-if)#exit
(config)#disable confirmation-dialog
(config)#
(config)#interface xe5
(config-if)#switchport
(config-if)#
switchport allowed ethertype
Use this command to indicate which types of traffic will be allowed on the switchport.
Note: A maximum of 5 Ethertype values can be assigned on an interface.
Command Syntax
switchport allowed ethertype {arp|ipv4|ipv6|mpls|ETHTYPE|log}
Parameters
arp
ARP traffic
ipv4
IPv4 traffic
ipv6
IPv6 traffic
mpls
MPLS traffic
ETHTYPE
Traffic of any Ethertype value (0x600 - 0xFFFF).
log
Log unwanted ethertype packets.
Default
No default value is specified
Command Mode
Interface mode
Applicability
This command was introduced before OcNOS version 1.3.
This command is not available on Qumran platforms.
Example
(config)#interface xe32/1
(config-if)#switchport
(config-if)#switchport allowed ethertype ipv4
(config-if)#switchport allowed ethertype 0x800
switchport protected
Use this command to enable or disable the protected port feature on an interface.
Command Syntax
switchport protected (community | isolated | promiscuous)
no switchport protected
Parameter
community
Community mode
isolated
Isolated mode type
promiscuous
Protected mode type
Default
Promiscuous
Command Mode
Interface mode
Applicability
This command was introduced in OcNOS-SP version 5.0.
Example
#configure terminal
(config)#interface xe1
(config-if)#switchport protected isolated
(config-if)#no switchport protected
(config)#interface po1
(config-if)#switchport protected promiscuous
(config-if)#no switchport protected
transceiver
Use this command to set the type of Small Form-factor Pluggable (SFP) transceiver inserted in the physical port.
Use the no form of this command to remove the setting.
Command Syntax
transceiver (1000base-sx|1000base-lx|1000base-ex|1000base-cx|10gbase-sr|10gbase-lr|10gbase-er|10gbase-cr|25gbase-sr|25gbase-lr|25gbase-er|25gbase-cr|40gbase-sr4|40gbase-lr4|40gbase-er4|40gbase-cr4|100gbase-sr4|100gbase-lr4|100gbase-er4|100gbase-cr4)
no transceiver
Parameters
1000base-cx
SFP 1000base-cx
1000base-ex
SFP 1000base-ex
1000base-lx
SFP 1000base-lx
1000base-sx
SFP 1000base-sx
100gbase-cr4
QSFP28 100gbase-cr4
100gbase-er4
QSFP28 100gbase-er4
100gbase-lr4
QSFP28 100gbase-lr4
100gbase-sr4
QSFP28 100gbase-sr4
10gbase-cr
SFP+ 10gbase-cr
10gbase-er
SFP+ 10gbase-er
10gbase-lr
SFP+ 10gbase-lr
10gbase-sr
SFP+ 10gbase-sr
25gbase-cr
SFP+ 25gbase-cr
25gbase-er
s
SFP+ 25gbase-er
25gbase-lr
SFP+ 25gbase-lr
25gbase-sr
SFP+ 25gbase-sr
40gbase-cr4
QSFP 40gbase-cr4
40gbase-er4
QSFP 40gbase-er4
40gbase-lr4
QSFP 40gbase-lr4
40gbase-sr4
QSFP 40gbase-sr4
Default
No default value is specified
Command Mode
Interface mode
Applicability
This command was introduced in OcNOS-SP version 5.0.
Examples
(config)#interface ce1/1
(config-if)#transceiver 40gbase-lr4