15. n Commands
15.1. nat
nat
Syntax
Full Contexts
Description
This command enables the dump or perform tools for NAT.
Supported Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
nat
Syntax
Context
Full Contexts
Description
Commands in this context clear NAT commands.
Supported Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
nat
Syntax
Context
Full Contexts
Description
Commands in this context display NAT related information.
Supported Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
nat
Syntax
Context
Full Contexts
Description
Commands in this context display NAT information.
Supported Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
15.2. nat-accounting-policy
nat-accounting-policy
Syntax
Context
Full Contexts
Description
This command displays NAT accounting policy information.
Parameters
Output
The following is an example output for this command.
15.3. nat-group
nat-group
Syntax
Context
Full Contexts
Description
This command lists all active member ISAs (or group members). Up to 16 group members can be displayed (16 is the supported number of LAG links). Members can share physical ISAs (MDAs) and the physical locality of the group members can be determined from the Mda column in the output.
The number of group members will be <=X and the actual number of displayed group members will depend on the configuration based calculation.
Parameters
Output
The following shows output examples.
Table 301: CPM Statistics Descriptions
Field | Description |
Transmitted frames | Displays the total number of transmitted frames on the CPM level. |
Transmission failures | Displays the transmission failures, for example due to missing route to the peer. |
Received frames | Displays the total number of received frames on the CPM level. |
Received failures (wrong peer) | Displays the received failures due to wrong peer. |
Keepalive timeouts | Displays the total number of keepalive timeouts. |
Table 302: ISA Statistics Descriptions
Field | Description |
State | Displays the state of the NAT inter-chassis redundancy member. |
Peer state | Displays the state of the peer. |
Local IP address | Displays the local IP address. |
Remote IP address | Displays the IP address of the remote client. |
Unsupported flows | Displays the flows other than TCP/UDP/ICMP in 1:1 NAT that are agnostic and by default created per subscriber by configuration on both nodes. There is no need to synchronize such flows. |
Tracked flows | Displays the TCP/UDP/ICMP flows. |
Tracked flows not synced | Displays the outstanding flows on the active node waiting to be synchronized (transient condition). On the standby node, all flows are in this state. |
Tracked flows pending | Displays the flows waiting to be acknowledged. |
Flows synced | Displays the flows that are synchronized. |
Flows marked to delete | Displays the flows marked to be deleted due to a timeout, deleted pinhole or simply as a result of an invoked clear command. |
Flows delete pending | Displays the flows waiting to be deleted due to a timeout, deleted pinhole or simply as a result of an invoked clear command. |
Time of last failure | Displays the time of the last ISA failure. |
Failure cause | Displays the cause of the ISA failure. |
Table 303: ISA Level Statistics Descriptions
Field | Description |
Transmitted frames | Displays all transmitted frames on the ISA level. |
Retransmitted frames | Displays the retransmitted frames due to loss (lack of acknowledgment). |
Transmitted flow create messages | Displays the transmitted flow create messages. |
Transmitted flow delete messages | Displays the transmitted flow delete messages. |
Transmitted ALG messages | Displays the transmitted application layer gateway messages. |
Received frames | Displays all frames received. |
Received flow create messages | Displays the received flow create messages. |
Received flow delete messages | Displays the received flow delete messages. |
Received ALG frames | Displays the received application layer gateway messages. |
Dropped flow create messages (no policy) | Displays the dropped flow create messages due to lack of policy. |
Dropped flow create messages (no port block) | Displays the dropped flow create messages due to block of port. |
Received fragments | Displays all fragments received. |
Table 304: Member State Descriptions
State | Descriptions |
Active | The member is actively serving traffic. |
Failed | The member is in a failed state where forwarding is not possible and L2-aware bypass redundancy mode is disabled. This event is normally associated with an MS-ISA failure. |
failedBypass | The member is in failed state and the subscribers that it was serving before the failover occurred are in a bypass mode. In a bypass mode, subscribers are normally routed according to the routing table in the inside routing context (as opposed to steered to MS-ISA where NAT is performed). The operator should ensure that the routing leads those subscribers to a centralized CGN node that serve as a backup device. This event is normally associated with an MS-ISA failure while the L2-aware bypass redundancy mode is enabled. |
activeBypass | The member transitions in this state after a recovery while the L2-aware bypass mode of operation is enabled. Some subscribers that this member was serving before the failover are in bypass mode, while others that came on-line after the restoration are actively being served by this member. |
Supported Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
nat-group
Syntax
Context
Full Contexts
Description
This command clears ISA nat-group commands related statistics or removes all the subscribers that are associated with a specific NAT group member.
Parameters
Supported Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
15.4. nat-policy
nat-policy
Syntax
Context
Full Contexts
Description
This command displays NAT policy information.
Parameters
Output
The following is sample output for this command.
Supported Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
15.5. neighbor
neighbor
Syntax
Full Contexts
Description
This command clears commands for a specific service.
For the 7450 ESS or 7750 SR, it clears the discovered IPv6 address of the neighboring CE associated with an Ipipe SAP. When IPv6CP comes back up following the execution of this command on an IPv6CP SAP, the node will check to see if an IPv6 address has been learned for the remote CE attached to the Ipipe service. If one has been learned, then this is used to bring up IPv6CP.
Parameters
Supported Platforms
All
neighbor
Syntax
Context
Full Contexts
Description
This command clears the discovered IPv6 address of the neighboring CE associated with an Ipipe SAP.
Supported Platforms
All
neighbor
Syntax
Context
Full Contexts
Description
This command displays PIM neighbor information.
Parameters
Output
The following output is an example of service PIM snooping neighbor information.
Supported Platforms
All
neighbor
Syntax
Context
Full Contexts
Description
This command clears PIM snooping neighbor information.
Parameters
Supported Platforms
All
neighbor
Syntax
Context
Full Contexts
Description
This command displays BGP neighbor information and can be entered with or without any parameters. Issuing the command without any parameters displays information for all BGP peers. When the command is issued with a specific IP address or ASN, information is displayed only for the specified peer or peers with the same AS.
When either received-routes or advertised-routes is specified, the routes exchanged with the specified peer are listed (see the second output example, below).
When either history or suppressed is specified, the routes learned from those peers that either have a history or are suppressed (respectively) are listed.
The “State” field displays the BGP peer’s protocol state. In addition to the standard protocol states, this field can also display the “Disabled” operational state, which indicates the peer is operationally disabled and must be restarted by the operator.
 | Note: The information generated by this command is not available by SNMP. |
Parameters
- as-num — 0 to 65535
- comm-val — 0 to 65535
- ext-comm — the extended community, defined as one of the following:
- {target | origin}:ip-address:comm-val
- {target | origin}:asnum:ext-comm-val
- {target | origin}:ext-asnum:comm-val
- bandwidth:asnum:val-in-mbps
- ext:4300:ovstate
- ext:value1:value2
- flowspec-set:ext-asnum:group-id
where:- target — route target
- origin — route origin
- ip-address — a.b.c.d
- ext-comm-val — 0 to 4294967295
- ext-asnum — 0 to 4294967295
- bandwidth — bandwidth
- val-in-mbps — 0 to 16777215
- ext — extended
- ext:4300 — origin verification
- ovstate — 0, 1, or 2 (0 for valid, 1 for not found, 2 for invalid)
- value1 — 0000 to FFFF
- value2 — 0 to FFFFFFFFFFFF
- flowspec-set — flow-spec set
- group-id — 0 to 16383
- well-known-comm — null | no-export | no-export-subconfed | no-advertise | llgr-stale | no-llgr | blackhole
- a.b.c.d (host bits must be 0)
- x:x:x:x:x:x:x:x [-interface]
- x:x:x:x:x:x:d.d.d.d [-interface]
- x: [0 to FFFF]H
- d: [0 to 255]D
- interface: up to 32 characters, mandatory for link local addresses
Output
The following output examples show BGP router information, and Table 305 describes the output fields for a BGP neighbor.
Table 305 describes the standard and detailed command output fields for a BGP neighbor.
Table 305: BGP Neighbor Fields
Label | Description |
Peer | The IP address of the configured BGP peer. |
Group | The BGP peer group to which this peer is assigned. |
Peer AS | The configured or inherited peer AS for the peer group. |
Peer Address | The configured address for the BGP peer. |
Peer Port | The TCP port number used on the far-end system. |
Local AS | The configured or inherited local AS for the peer group. |
Local Address | The configured or inherited local address for originating peering for the peer group. |
Local Port | The TCP port number used on the local system. |
Peer Type | External — Peer type configured as external BGP peers. Internal — Peer type configured as internal BGP peers. |
Bfd | Yes — BFD is enabled. No — BFD is disabled. |
Dynamic Peer | Yes — The session is dynamic (unconfigured). No — The session is statically configured. |
State | Idle — The BGP peer is not accepting connections. (Shutdown) is displayed in addition, if the peer is administratively disabled. Active — BGP is listening for and accepting TCP connections from this peer. Connect — BGP is attempting to establish a TCP connections from this peer. Open Sent — BGP has sent an OPEN message to the peer and is waiting for an OPEN message from the peer. Open Confirm — BGP has received a valid OPEN message from the peer and is awaiting a KEEPALIVE or NOTIFICATION. Established — BGP has successfully established a peering and is exchanging routing information. |
Last State | Idle — The BGP peer is not accepting connections. Active — BGP is listening for and accepting TCP connections from this peer. Connect — BGP is attempting to establish a TCP connections from this peer. Open Sent — BGP has sent an OPEN message to the peer and is waiting for an OPEN message from the peer. Open Confirm — BGP has received a valid OPEN message from the peer and is awaiting a KEEPALIVE or NOTIFICATION. |
Last Event | start — BGP has initialized the BGP neighbor. stop — BGP has disabled the BGP neighbor. open — BGP transport connection opened. close — BGP transport connection closed. openFail — BGP transport connection failed to open. error — BGP transport connection error. connectRetry — Connect retry timer expired. holdTime — Hold time timer expired. keepAlive — Keepalive timer expired. recvOpen — Receive an OPEN message. revKeepalive — Receive a KEEPALIVE message. recvUpdate — Receive an UPDATE message. recvNotify — Receive a NOTIFICATION message. None — No events have occurred. |
Last Error | Displays the last BGP error and subcode to occur on the BGP neighbor. |
Connect Retry | The configured or inherited connect retry timer value. |
Local Pref. | The configured or inherited local preference value. |
Min Route Advt. | The minimum amount of time that must pass between route updates for the same IP prefix. |
Min AS Originate | The minimum amount of time that must pass between updates for a route originated by the local router. |
Multihop | The maximum number of router hops a BGP connection can traverse. |
Damping | Disabled — BGP neighbor is configured not to dampen route flaps. Enabled — BGP neighbor is configured to dampen route flaps. |
Loop Detect | Ignore — The BGP neighbor is configured to ignore routes with an AS loop. Drop — The BGP neighbor is configured to drop the BGP peering if an AS loop is detected. Off — AS loop detection is disabled for the neighbor. |
MED Out | The configured or inherited MED value assigned to advertised routes without a MED attribute. |
Authentication | None — No authentication is configured. MD5 — MD5 authentication is configured. |
Next Hop Self | Disabled — BGP is not configured to send only its own IP address as the BGP nexthop in route updates to the specified neighbor. Enabled — BGP will send only its own IP address as the BGP nexthop in route updates to the neighbor. |
AggregatorID Zero | Disabled — The BGP Neighbor is not configured to set the aggregator ID to 0.0.0.0 in all originated route aggregates. Enabled — The BGP Neighbor is configured to set the aggregator ID to 0.0.0.0 in all originated route aggregates. |
Remove Private | Disabled — BGP will not remove all private AS numbers from the AS path attribute, in updates sent to the specified neighbor. Enabled — BGP will remove all private AS numbers from the AS path attribute, in updates sent to the specified neighbor. |
Passive | Disabled — BGP will actively attempt to establish a BGP connection with the specified neighbor. Enabled — BGP will not actively attempt to establish a BGP connection with the specified neighbor. |
Prefix Limit | No Limit — No route limit assigned to the BGP peer group. 1 to 4294967295 — The maximum number of routes BGP can learn from a peer. |
Hold Time | The configured hold time setting. |
Keep Alive | The configured keepalive setting. |
Active Hold Time | The negotiated hold time, if the BGP neighbor is in an established state. |
Active Keep Alive | The negotiated keepalive time, if the BGP neighbor is in an established state. |
Cluster Id | The configured route reflector cluster ID. None — No cluster ID has been configured. |
Client Reflect | Disabled — The BGP route reflector is configured not to reflect routes to this neighbor. Enabled — The BGP route reflector is configured to reflect routes to this neighbor. |
Preference | The configured route preference value for the peer group. |
Num of Flaps | The number of route flaps in the neighbor connection. |
Recd. Prefixes | The number of routes received from the BGP neighbor. |
Active Prefixes | The number of routes received from the BGP neighbor and active in the forwarding table. |
Recd. Paths | The number of unique sets of path attributes received from the BGP neighbor. |
Suppressed Paths | The number of unique sets of path attributes received from the BGP neighbor and suppressed due to route damping. |
Input Queue | The number of BGP messages to be processed. |
Output Queue | The number of BGP messages to be transmitted. |
i/p Messages | Total number of packets received from the BGP neighbor. |
o/p Messages | Total number of packets sent to the BGP neighbor. |
i/p Octets | Total number of octets received from the BGP neighbor. |
o/p Octets | Total number of octets sent to the BGP neighbor. |
Export Policy | The configured export policies for the peer group. |
Import Policy | The configured import policies for the peer group. |
Egress Engineering | Enabled — EPE is enabled for the BGP neighbor. Disabled — EPE is disabled for the BGP neighbor. |
The following output examples show SR IPv6 policy routes information for BGP neighbors in the BGP and BGP group contexts.
Table 306 describes the command output for both the standard and detailed information for a neighbor.
Table 306: Standard and Detailed BGP Neighbor Output Fields
Label | Description |
BGP Router ID | The local BGP router ID. |
AS | The configured autonomous system number. |
Local AS | The configured local AS setting. If not configured, then it is the same value as the AS. |
Flag | u — used s — suppressed h — history d — decayed * — valid i — igp e — egp ? — incomplete > — best |
Network | Route IP prefix and mask length for the route. |
Next Hop | BGP nexthop for the route. |
LocalPref | BGP local preference path attribute for the route. |
MED | BGP Multi-Exit Discriminator (MED) path attribute for the route. |
AS Path | The BGP AS path for the route. |
Egress Engineering | Enabled — EPE is enabled for the BGP neighbor. Disabled — EPE is disabled for the BGP neighbor. |
Supported Platforms
All
neighbor
Syntax
Context
Full Contexts
Description
Displays RIP neighbor interface information.
Parameters
Output
The following output is an example of standard RIP group information, and Table 307 describes the output fields.
Table 307: Standard Show RIP Neighbor Field Descriptions
Label | Description |
Neighbor | The RIP neighbor interface name. |
Adm | Down — The RIP neighbor interface is administratively down. Up — The RIP neighbor interface is administratively up. |
Opr | Down — The RIP neighbor interface is operationally down. Up — The RIP neighbor interface is operationally up. |
Primary IP | The primary IP address of the RIP neighbor interface. |
Send Mode | Bcast — Specifies that RIPv2 formatted messages are sent to the broadcast address. Mcast — Specifies that RIPv2 formatted messages are sent to the multicast address. None — Specifies that no RIP messages are sent (i.e., silent listener). RIPv1 — Specifies that RIPv1 formatted messages are sent to the broadcast address. |
Recv Mode | Both — Specifies that RIP updates in either version 1 or version 2 format will be accepted. None — Specifies that RIP updates will not be accepted. RIPv1 — Specifies that RIP updates in version 1 format only will be accepted. RIPv2 — Specifies that RIP updates in version 2 format only will be accepted. |
Metric In | The metric added to routes received from a RIP neighbor. |
Detailed Show RIP Neighbor Output
The following output is an example of detailed RIP group information, and Table 308 describes the output fields.
Table 308: Detailed Show RIP Neighbor Field Descriptions
Label | Description |
Neighbor | The RIP neighbor name. |
Description | The RIP neighbor description. No Description Available indicates no description is configured. |
Primary IP | The RIP neighbor interface primary IP address. |
Group | The RIP group name of the neighbor interface. |
Admin State | Down — The RIP neighbor interface is administratively down. Up — The RIP neighbor interface is administratively up. |
Oper State | Down — The RIP neighbor interface is operationally down. Up — The RIP neighbor interface is operationally up. |
Send Mode | Bcast — Specifies that RIPv2 formatted messages are sent to the broadcast address. Mcast — Specifies that RIPv2 formatted messages are sent to the multicast address. None — Specifies that no RIP messages are sent (i.e., silent listener). RIPv1 — Specifies that RIPv1 formatted messages are sent to the broadcast address. |
Recv Mode | Both — Specifies that RIP updates in either version 1 or version 2 format will be accepted. None — Specifies that RIP updates will not be accepted. RIPv1 — Specifies that RIP updates in version 1 format only will be accepted. RIPv2 — Specifies that RIP updates in version 2 format only will be accepted. |
Metric In | The metric value added to routes received from a RIP neighbor. |
Metric Out | The value added to routes exported into RIP and advertised to RIP neighbors. |
Split Horizon | Disabled — Split horizon disabled for the neighbor. Enabled — Split horizon and poison reverse enabled for the neighbor. |
Check Zero | Disabled — Checking of the mandatory zero fields in the RIPv1 and RIPv2 specifications are not checked allowing receipt of RIP messages even if mandatory zero fields are non-zero for the neighbor. Enabled — Checking of the mandatory zero fields in the RIPv1 and RIPv2 specifications and rejecting non-compliant RIP messages is enabled for the neighbor. |
Message Size | The maximum number of routes per RIP update message. |
Preference | The preference of RIP routes from the neighbor. |
Auth. Type | Specifies the authentication type. |
Update Timer | The current setting of the RIP update timer value expressed in seconds. |
Timeout Timer | The current RIP timeout timer value expressed in seconds. |
Export Policies | The export route policy that is used to determine routes advertised to all peers. |
Import Policies | The import route policy that is used to determine which routes are accepted from RIP neighbors. |
Supported Platforms
All
neighbor
Syntax
Context
Full Contexts
Description
This command resets the specified BGP peer or set of peers. By default, or when the hard option is specified, the TCP connection is torn down and the state of the BGP session returns to IDLE.
If the soft-route-refresh option is specified without an accompanying family parameter, then the session remains established and one ROUTE_REFRESH message is transmitted to the peer for each address family active on the session. If the soft-route-refresh option is specified with an accompanying family parameter, then the session remains established and a single ROUTE_REFRESH message is transmitted to the peer requesting that it resend only its routes belonging to that one address family.
SR OS routers respond to route refresh requests for any supported AFI/SAFI.
Parameters
- a.b.c.d
- x:x:x:x:x:x:x:x [-interface]
- x:x:x:x:x:x:d.d.d.d [-interface]
- x: [0 to FFFF]H
- d: [0 to 255]D
- interface: up to 32 characters, mandatory for link local addresses
Supported Platforms
All
neighbor
Syntax
Context
Full Contexts
Description
This command shows neighbor information.
Parameters
Output
The following output is an example of RSVP neighbor information.
Supported Platforms
All
neighbor
Syntax
Context
Full Contexts
Description
This command dumps RSVP neighbor information.
Parameters
Output
The following output is an example of MPLS RSVP neighbor details.
Supported Platforms
All
neighbor
Syntax
Context
Full Contexts
Description
This command displays PIM neighbor information. This can be important if an interface has more than one adjacency. For example, a LAN-interface configuration with three routers connected and all are running PIM on their LAN interfaces. These routers then have two adjacencies on their LAN interface, each with different neighbors. If the address ip-address parameter is not defined in this example, then the show command output would display two adjacencies.
Parameters
Output
The following output is an example of a PIM neighbor configuration. Table 309 provides PIM neighbor field descriptions.
Table 309: PIM Neighbor Fields
Label | Description |
Interface | The neighbor’s interface name. (W) indicates wildcard tunnels. |
Nbr DR Priority | The value of the neighbor's DR priority which is received in the hello message. |
Nbr Address | The neighbor’s address. |
Up Time | The time since this PIM neighbor (last) became a neighbor of the local router |
Expiry Time | The minimum time remaining before this PIM neighbor is aged out 0 — Means that this neighbor never ages out. This happens when the PIM neighbor sends a Hello message with holdtime set to `0xffff'. |
Hold Time | The value of the hold time present in the hello message |
DR Priority | The value of the neighbor's DR priority which is received in the hello message |
Tracking Support | Indicates if the T bit in the LAN prune delay option was present in the hello message. This indicates the neighbor's capability to disable join message suppression. |
LAN Delay | The value of the LAN delay field present in the hello message received from the neighbor |
Gen Id | A randomly generated 32-bit value that is regenerated each time PIM forwarding is started or restarted on the interface, including when the router itself restarts. When a hello message with a new GenID is received from a neighbor, any old hello information about that neighbor is discarded and superseded by the information from the new hello message. |
Override Intvl (ms) | The value of the override interval present in the Hello message |
Supported Platforms
All
neighbor
Syntax
Context
Full Contexts
Description
This command clears PIM neighbor data on a specified interface or IP address.
Parameters
Supported Platforms
All
neighbor
Syntax
Context
Full Contexts
Description
This command displays information about the IPv6 neighbor cache.
Parameters
Output
Neighbor Output — The following output is an example of IPv6 neighbor information, and Table 310 describes the fields.
Table 310: Neighbor Fields
Label | Description |
IPv6 Address | Displays the IPv6 address |
Interface | Displays the name of the IPv6 interface name |
MAC Address | Specifies the link-layer address |
State | Displays the current administrative state |
Exp | Displays the number of seconds until the entry expires |
Type | Displays the type of IPv6 interface |
Interface | Displays the interface name |
Rtr | Specifies whether a neighbor is a router |
Mtu | Displays the MTU size |
Supported Platforms
All
neighbor
Syntax
Context
Full Contexts
Description
This command clears IPv6 neighbor information.
Parameters
ipv6-address: | x:x:x:x:x:x:x:x (eight 16-bit pieces) |
x:x:x:x:x:x:d.d.d.d | |
x: [0 to FFFF]H | |
d: [0 to 255]D |
Supported Platforms
All
neighbor
Syntax
Full Contexts
Description
This command shows all OSPFv2 or OSPFv3 neighbor information.
Parameters
Output
The following output is an example of OSPF and OSPF3 neighbor information.
Supported Platforms
All
neighbor
Syntax
Full Contexts
Description
This command displays neighbor information. To reduce the amount of output, the user can select the neighbors on a given interface by address or name.
The detail option produces a large amount of data. It is recommended to use detail only when requesting a specific neighbor.
Parameters
Output
Standard OSPF Neighbor Output
Table 311 describes the standard command output fields for an OSPF neighbor.
Table 311: OSPF Neighbor Output Fields
Label | Description |
Nbr IP Addr | The IP address this neighbor is using in its IP Source Address. On addressless links, this will not be 0.0.0.0, but the address of another of the neighbor's interfaces. |
Nbr Rtr Id | A 32-bit integer uniquely identifying the neighboring router in the Autonomous System. |
Nbr State | Down — This is the initial state of a neighbor conversation. It indicates that there has been no recent information received from the neighbor. Attempt — This state is only valid for neighbors attached to NBMA networks. It indicates that no recent information has been received from the neighbor, but that a more concerted effort should be made to contact the neighbor. Init — In this state, an Hello packet has recently been seen from the neighbor. However, bidirectional communication has not yet been established with the neighbor (the router itself did not appear in the neighbor's Hello packet). Two Way — In this state, communication between the two routers is bidirectional. ExchStart — This is the first step in creating an adjacency between the two neighboring routers. The goal of this step is to decide which router is the master, and to decide upon the initial Database Descriptor sequence number. Exchange — In this state the router is describing its entire link state database by sending Database Description packets to the neighbor. Loading — In this state, Link State Request packets are sent to the neighbor asking for the more recent LSAs that have been discovered (but not yet received) in the Exchange state. Full — In this state, the neighboring routers are fully adjacent. These adjacencies will now appear in router-LSAs and network-LSAs. |
Priority | The priority of this neighbor in the designated router election algorithm. The value 0 signifies that the neighbor is not eligible to become the designated router on this particular network. |
RetxQ Len | The current length of the retransmission queue. |
Dead Time | The time until this neighbor is declared down, this timer is set to the dead router interval when a valid hello packet is received from the neighbor. |
No. of Neighbors | The number of adjacent OSPF neighbors on this interface. |
Detailed OSPF Neighbor Output
Table 312 describes the detailed command output fields for an OSPF neighbor.
Table 312: Detailed OSPF Neighbor Output Fields
Label | Description |
Neighbor IP Addr | The IP address this neighbor is using in its IP source address. On addressless links, this will not be 0.0.0.0, but the address of another of the neighbor's interfaces. |
Local IF IP Addr | The IP address of this OSPF interface. |
Area Id | A 32-bit integer uniquely identifying the area to which this interface is connected. Area ID 0.0.0.0 is used for the OSPF backbone |
Designated Rtr | The IP Interface address of the router identified as the Designated Router for the network in which this interface is configured. Set to 0.0.0.0 if there is no Designated router. |
Neighbor Rtr Id | A 32-bit integer uniquely identifying the neighboring router in the AS. |
Neighbor State | Down — This is the initial state of a neighbor conversation. It indicates that there has been no recent information received from the neighbor. Attempt — This state is only valid for neighbors attached to NBMA networks. It indicates that no recent information has been received from the neighbor, but that a more concerted effort should be made to contact the neighbor. Init — In this state, an Hello packet has recently been seen from the neighbor. However, bidirectional communication has not yet been established with the neighbor (the router itself did not appear in the neighbor's Hello packet). Two Way — In this state, communication between the two routers is bidirectional. Exchange start — This is the first step in creating an adjacency between the two neighboring routers. The goal of this step is to decide which router is the master, and to decide upon the initial Database Descriptor sequence number. Exchange — In this state the router is describing its entire link state database by sending Database Description packets to the neighbor. Loading — In this state, Link State Request packets are sent to the neighbor asking for the more recent LSAs that have been discovered (but not yet received) in the Exchange state. Full — In this state, the neighboring routers are fully adjacent. These adjacencies will now appear in router-LSAs and network-LSAs. |
Priority | The priority of this neighbor in the designated router election algorithm. The value 0 signifies that the neighbor is not eligible to become the designated router on this particular network. |
Retrans Q Length | The current length of the retransmission queue. |
Options | E — External Routes Support MC — Multicast Support N/P — Type 7 LSA Support EA — External Attribute LSA Support DC — Demand Circuit Support O — Opaque LSA Support |
Backup Desig Rtr | The IP Interface address of the router identified as the Backup Designated Router for the network in which this interface is configured. Set to 0.0.0.0 if there is no backup designated router. |
Events | The number of times this neighbor relationship has changed state, or an error has occurred. |
Last Event Time | The time when the last event occurred that affected the adjacency to the neighbor. |
Up Time | This value represents the uninterrupted time, in hundredths of seconds, the adjacency to this neighbor has been up. To evaluate when the last state change occurred see last event time. |
Time Before Dead | The time until this neighbor is declared down, this timer is set to the dead router interval when a valid hello packet is received from the neighbor. |
Bad Nbr States | The total number of OSPF packets received when the neighbor state was not expecting to receive this packet type since this interface was last enabled. |
LSA Inst fails | The total number of times an LSA could not be installed into the LSDB due to a resource allocation issue since this interface was last enabled. |
Bad Seq Nums | The total number of times when a database description packet was received with a sequence number mismatch since this interface was last enabled. |
Bad MTUs | The total number of times when the MTU in a received database description packet was larger than the MTU of the receiving interface since this interface was last enabled. |
Bad Packets | The total number of times when an LS update was received with an illegal LS type or an option mismatch since this interface was last enabled. |
LSA not in LSDB | The total number of times when an LS request was received for an LSA not installed in the LSDB of this router since this interface was last enabled. |
Option Mismatches | The total number of times when a LS update was received with an option mismatch since this interface was last enabled. |
Nbr Duplicates | The total number of times when a duplicate database description packet was received during the exchange state since this interface was last enabled. |
Supported Platforms
All
neighbor
Syntax
Full Contexts
Description
This command marks the neighbor as dead and re-initiates the affected adjacencies.
Parameters
Supported Platforms
All
neighbor
Syntax
Context
Full Contexts
Description
This command displays RIPng neighbor interface information.
Parameters
Output
The following output is an example of RIPng neighbor information.
Supported Platforms
All
15.6. neighbor-table
neighbor-table
Syntax
Context
Full Contexts
Description
This command dumps neighbor table entries for the specified HLE BD.
Parameters
Supported Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
15.7. neighbors
neighbors
Syntax
Context
Full Contexts
Description
This command display GSMP neighbor information.
Parameters
Output
The following output displays an example of service GSMP neighbor information.
These commands show the configured neighbors per service, regardless that there exists an open TCP connection with this neighbor. The admin state is shown because for a neighbor to be admin enabled, the service, gsmp node, group node and the neighbor node in this service must all be in the no shutdown state. Session gives the number of session (open TCP connections) for each configured neighbor.
The following table describes show service-id gsmp neighbors group output fields:
Table 313: Service-ID GSMP Neighbors Group Field Descriptions
Label | Description |
Group | The GSMP group name |
Neighbor | The neighbor IP address |
AdminState | The administrative state of the neighbor |
Sessions | The number of sessions (open TCP connections) for each configured neighbor |
Supported Platforms
All
15.8. netconf
netconf
Syntax
Context
Full Contexts
Description
This command displays active NETCONF SSH sessions.
Output
The following is an example of NETCONF information.
Table 314 describes the NETCONF output fields.
Table 314: NETCONF Output Fields
Label | Description |
Administrative State | Enabled — Indicates that NETCONF is enabled. Disabled — Indicates that NETCONF is disabled. |
Operational State | Up — Indicates that NETCONF is operational. Down — Indicates that NETCONF is not operational. |
Supported Platforms
All
15.9. network
network
Syntax
Context
Full Contexts
Description
This command displays network policy information.
Parameters
Output
The following output is an example of network QoS Policy information, and Table 315 describes the network QoS Policy output fields.
Table 315: Show QoS Network Output Fields
Label | Description |
Policy-Id | The ID that uniquely identifies the policy. |
Remark | True — Remarking is enabled for all packets that egress this router where the network policy is applied. The remarking is based on the forwarding class to DSCP and LSP EXP bit mapping defined under the egress node of the network QoS policy. False — Remarking is disabled. |
Description | A text string that helps identify the policy context in the configuration file. |
Forwarding Class/ FC Name | Specifies the default ingress forwarding class (configured using the network ingress default-action command) assigned to packets for which there is no other configured forwarding class classification. |
Profile | Specifies the default ingress packet profile (configured using the network ingress default-action command) assigned to packets for which there is no other configured packet profile classification. |
DSCP Mapping: | |
Out-of-Profile | Displays the DSCP used for out-of-profile traffic. |
In-Profile | Displays the DSCP used for in-profile traffic. |
LSP EXP Bit Mapping: | |
Out-of-Profile | Displays the LSP EXP value used for out-of-profile traffic. |
In-Profile | Displays the LSP EXP value used for in-profile traffic. |
Interface | Displays the interface name. |
IP Addr | Displays the interface IP address. |
Port-Id | Specifies the physical port identifier that associates the interface. |
Supported Platforms
All
15.10. network-domains
network-domains
Syntax
Context
Full Contexts
Description
This command displays network-domains information.
Parameters
Output
The following output is an example of network domain information.
Supported Platforms
All
15.11. network-queue
network-queue
Syntax
Context
Full Contexts
Description
This command displays network queue policy information.
Parameters
Output
The following output is an example of network-queue information.
Supported Platforms
All
15.12. next-hop
next-hop
Syntax
Context
Full Contexts
Description
Displays BGP next-hop information.
Parameters
- a.b.c.d (host bits must be 0)
- x:x:x:x:x:x:x:x (eight 16-bit pieces)
- x:x:x:x:x:x:d.d.d.d
- x: [0 to FFFF]H
- d: [0 to 255]D
Output
Show Next-Hop Output
Table 316 describes the command output fields for a BGP next hop.
Table 316: BGP Next Hop Output Fields
Label | Description |
BGP ID | The local BGP router ID. |
AS | The configured autonomous system number. |
Local AS | The configured local AS setting. If not configured, then the value is the same as the AS. |
Next Hop | The next-hop address. |
Resolving Prefix | Displays the prefix of the best next hop. |
Owner | Displays the routing protocol used to derive the best next hop. |
Preference | Displays the BGP preference attribute for the routes. |
Reference Count | Displays the number of routes using the resolving prefix. |
Resolved Next Hop | The IP address of the next hop. |
Supported Platforms
All
15.13. next-hop-id
next-hop-id
Syntax
Context
Full Contexts
Description
This command displays information for the specified replication segment next-hop of the P2MP SR tree.
Parameters
Supported Platforms
All
15.14. ntp
ntp
Syntax
Context
Full Contexts
Description
This command displays NTP protocol configuration and state.
Parameters
- x:x:x:x:x:x:x:x
- x:x:x:x:x:x:d.d.d.d
- x – [0 to FFFF] H
- d – [0 to 255] D
- x:x:x:x:x:x:x:x
- x:x:x:x:x:x:d.d.d.d
- x – [0 to FFFF] H
- d – [0 to 255] D
Output
The following output is an example of NTP information, and Table 317 describes the output fields.
Table 317: Show NTP Field Description
Label | Description |
Configured | yes — NTP is configured. no — NTP is not configured. |
Admin Status | yes — Administrative state is enabled. no — Administrative state is disabled. |
Server Enabled | yes — This node is configured to serve external clients. no — This node is not configured to server external clients. |
Stratum | Displays stratum level of this node. |
Oper Status | yes — The operational state is enabled. no — The operational state is disabled. |
Auth Check | Displays the authentication requirement. |
Server Authenticate | Yes — Authentication is mandatory on received requests. No — Authentication is not mandatory on received requests. |
Clock Source | Address of the chosen server. |
Auth Errors | Displays the number of authentication errors. |
Auth Errors Ignored | Displays the number of authentication errors ignored. |
Auth key Id Errors | Displays the number of key identification errors. |
Auth Key Type Errors | Displays the number of authentication key type errors. |
Current Date & Time | Current date and time as determined by the NTP process in the node. |
vRouter | The router instance containing the interface. |
Router | The router instance containing the address. |
Interface | The interface configured in NTP. |
Address | The address used for transmitted messages. |
Type | bcast — broadcast interface mcast — multicast interface bclnt — broadcast client srvr — server actpr — active peer paspr — passive peer |
Auth | Yes — Authentication in use. No — Authentication not in use. |
Poll | # — Current poll interval used on the interface. |
State | Reject — The peer is rejected and will not be used for synchronization. Rejection reasons could be the peer is unreachable, the peer is synchronized to this local server so synchronizing with it would create a sync loop, or the synchronization distance is too large. This is the normal startup state. Invalid — The peer is not maintaining an accurate clock. This peer will not be used for synchronization. Excess — The peer's synchronization distance is greater than ten other peers. This peer will not be used for synchronization. Outlier — The peer is discarded as an outlier. This peer will not be used for synchronization. Candidate — The peer is accepted as a possible source of synchronization. Selected — The peer is an acceptable source of synchronization, but its synchronization distance is greater than six other peers. Chosen — The peer is chosen as the source of synchronization. ChosenPPS — The peer is chosen as the source of synchronization, but the actual synchronization is occurring from a pulse-per-second (PPS) signal. |
Remote | The IP address of the remote NTP server or peer with which this local host is exchanging NTP packets. |
Reference ID | When stratum is between 0 and 15 this field shows the IP address of the remote NTP server or peer with which the remote is exchanging NTP packets. For reference clocks, this field shows the identification assigned to the clock, such as, “.GPS.” For an NTP server or peer, if the client has not yet synchronized to a server/peer, the status cannot be determined and displays the following codes: Peer Codes: ACST — The association belongs to any cast server. AUTH — Server authentication failed. Wait while the association is restarted. AUTO — Autokey sequence failed. Wait while the association is restarted. BCST — The association belongs to a broadcast server. CRPT— Cryptographic authentication or identification failed. The details should be in the system log file or the cryptostats statistics file, if configured. No further messages will be sent to the server. DENY — Access denied by remote server. No further messages will be sent to the server. DROP — Lost peer in symmetric mode. Wait while the association is restarted. RSTR — Access denied due to local policy. No further messages will be sent to the server. INIT — The association has not yet synchronized for the first time. MCST — The association belongs to a manycast server. NKEY — No key found. Either the key was never installed or is not trusted. RATE — Rate exceeded. The server has temporarily denied access because the client exceeded the rate threshold. RMOT — The association from a remote host running the ntpdc utility has had unauthorized attempted access. STEP — A step change in system time has occurred, but the association has not yet resynchronized. System Codes: INIT — The system clock has not yet synchronized for the first time. STEP — A step change in system time has occurred, but the system clock has not yet resynchronized. |
St | Stratum level of this node. |
A | y — Authentication is enabled. n — Authentication is disabled. |
Poll | Polling interval. |
Reach | Shows the reachability for the most recent polls (up to 8): Y — The NTP peer or server did respond in the indicated poll. No — The NTP peer or server did not respond in the indicated poll. |
Offset | The time between the local and remote UTC time, in milliseconds. |
Time Last Request Rx | The time at which the last request was received from the client. |
Supported Platforms
All
15.15. number-of-tunnels
number-of-tunnels
Syntax
Context
Full Contexts
Description
This command displays the number of tunnels that are operationally up for the specified tunnel and scope.
The following scope types are supported:
- per ISA
- per tunnel group
- per systemNote that L2TPv2 does not have a per-ISA scope.
The system collects statistics every hour for the past 24 hours per wall clock. A current value is also included in the output.
Parameters
esa-vm: | esa-id/vm-id | |
esa-id | 1 to 16 | |
vm-id | 1 to 4 |
Supported Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
number-of-tunnels
Syntax
Context
Full Contexts
Description
This command displays information for the number of IPsec tunnel statistics of the specified tunnel type and scope. The system collects statistics every hour for the last 24 hour according to the wall clock. The current value is also included in the output.
This command supports following scopes:
- per system
- per ISA
- per tunnel group
- per IPsec GW
The start time value in the output indicates the time when the results are collected.
Parameters
esa-vm: | esa-id/vm-id | |
esa-id | 1 to 16 | |
vm-id | 1 to 4 |
Output
The following is an example output of the show isa statistics ipsec-stats number of tunnels command.
Supported Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR