dump
tools
This command enables the context to display information for debugging purposes.
n/a
auto-discovery [detail] [log]
tools>dump
This command allows you to view all progress and event logs stored by ADP.
n/a
displays detailed information about the system, ports, and ADP instructions
displays all detailed progress and event logs with timestamps
cflowd
tools>dump
This command enables dump tools for Cflowd.
n/a
cache aggregate {src-dst-proto | src-dst-proto-port} family {ipv4 | ipv6}
cache all family {ipv4 | ipv6}
tools>dump>cflowd
This command displays the contents of the Cflowd active cache. This information can be displayed either in raw form where every flow entry is displayed or in an aggregated form.
n/a
displays the raw active cache flow data with no aggregation.
displays the aggregated active cache flow data
src-dst-proto — aggregates the active flow cache based on the source and destination IP address and the IP protocol value
src-dst-proto-port — aggregates the active flow cache based on the source and destination IP address, IP protocol value, and the source and destination port numbers
specifies which IP address family flow data should be displayed
ipv4 — displays the IPv4 flow data
ipv6 — displays the IPv6 flow data
The following output is an example of Cflowd cache information, and Table: Tools Dump Cflowd Cache Field Descriptions describes the fields.
Output Example*A:NOK1>config>router# /tools dump cflowd cache aggregate src-dst-proto family ipv4
Cache dump aggregation in progress, please wait...
Current time: 03/21/2019 17:15:46
--------------------------------------------------------------------------------
Proto Source Address Pkt-Cnt Start
Destination Address Byte-Cnt
--------------------------------------------------------------------------------
TCP 10.40.1.5 11741 03/21/2019 17:13:35
3.1.38.1 2700430
--------------------------------------------------------------------------------
Label |
Description |
---|---|
Proto |
The IPv4 or IPv6 protocol type |
Source Address |
The source IP address of the flow (IPv4 or IPv6) |
Destination Address |
The destination IP address of the flow (IPv4 or IPv6) |
Intf/Ingr |
The ingress interface associated with the sampled flow (only displayed with the raw (all) output) |
Intf/Egr |
The egress interface associated with the sampled flow (only displayed with the raw (all) output) |
S-Port |
The source protocol port number |
D-Port |
The destination protocol port number |
Pkt-Cnt |
The total number of packets sampled for the associated flow |
Byte-Cnt |
The total number of bytes of traffic sampled for the associated flow |
Start |
The system time when the first packet was sampled for the associated flow |
Flags |
The IP flag value from the sampled IP flow header (only displayed with the raw (all) output) |
ToS |
The ToS byte values from the sampled IP flow header (only displayed with the raw (all) output) |
(Src) Mask |
The IP route mask for the route to the flow source IP address associated with the flow (only displayed with the raw (all) output) |
(Dst) Mask |
The IP route mask for the route to the flow destination IP address associated with the flow (only displayed with the raw (all) output) |
(Src) AS |
The ASN associated with the route to the flow source IP address associated with the flow (only displayed with the raw (all) output) |
(Dst) AS |
The ASN associated with the route to the flow destination IP address associated with the flow (only displayed with the raw (all) output) |
vRtr-ID |
The Virtual Router ID associated with the reported IP flow (only displayed with the raw (all) output) |
packet-size protocol [clear]
tools>dump>cflowd
This command displays packet size distribution for sampled IP traffic. Values are displayed in decimal format (1.0 = 100%, 500 = 50%). Separate statistics are maintained and shown for IPv4 and IPv6 traffic.
The clear option clears the cache after the packet size statistics are displayed.
n/a
specifies the type of Cflowd packet information to display
clears the cache after the packet size statistics are displayed
The following output is an example of Cflowd packet size information.
Output ExampleNOK-12# tools dump cflowd packet-size ipv4
IP packet size distribution (801600 total packets):
1-32 64 96 128 160 192 224 256 288 320 352 384 416 448 480
.000 .250 .000 .000 .010 .100 .500 .090 .000 .000 .000 .000 .000 .000 .000
512 544 576 1024 1536 2048 2560 3072 3584 4096 4608 9000
.000 .000 .000 .050 .000 .000 .000 .000 .000 .000 .000 .000
top-flows protocols [clear]
tools>dump>cflowd
This command displays the top 20 (highest traffic volume) flows for IPv4, IPv6, or MPLS traffic types collected since the Cflowd top-flow table was last cleared or initialized.
The clear option clears the cache after the packet size statistics are displayed.
n/a
specifies the type of Cflowd packet information to display
clears the cache after the packet size statistics are displayed
The following output is an example of Cflowd top flow information, and Table: Tools Dump Cflowd Top Flows Field Descriptions describes the fields.
Output Example*A:7705:Dut-A# tools dump cflowd top-flows ipv4
The top 20 IPv4 unicast flows seen by cflowd are:
Current Time: 04/01/2019 17:44:17
Last Cleared Time: 04/01/2019 17:38:36
ifIndexContext: global
Intf/Ingr SrcIP Intf/Egr DstIP Pro ToS
I-vRtrID S-Port Msk AS E-vRtrID D-Port Msk AS Flgs Pkts
NextHop Pkt-Size Time
--------------------------------------------------------------------------------
2 150.2.1.2 1 150.1.1.2 6 0x00
1 10 /24 300 1 20 /24 200 0x00 25
1.20.1.2 46 0
--------------------------------------------------------------------------------
*A:7705:Dut-A# tools dump cflowd top-flows ipv6
The top 20 IPv6 unicast flows seen by cflowd are:
Current Time: 04/01/2019 17:44:24
Last Cleared Time: 04/01/2019 17:38:36
ifIndexContext: global
SrcIP Intf/Ingr S-Port I-vRtrID ToS
DstIP Intf/Egr D-Port E-vRtrID Flags
Nexthop Pkts Pkt-Size Proto Time
--------------------------------------------------------------------------------
::9602:102 2 10 1 0x03
::9601:102 1 20 1 0x00
::114:102 25 60 6 0
--------------------------------------------------------------------------------
*A:7705:Dut-
Label |
Description |
---|---|
Intf/Ingr |
The ingress interface ID |
SrcIP |
The source IP address of the flow (IPv4 or IPv6) |
Intf/Egr |
The egress interface ID |
DstIP |
The destination IP address of the flow (IPv4 or IPv6) |
Pro |
The protocol type for the flow |
ToS |
The Type of Service/DSCP bits field markings |
Flgs |
The protocol flag markings |
Pkts |
The total number of packets sampled for this flow since the statistics were last cleared |
I-vRtr-ID |
The vRouter context the flow was sampled in |
S-Port |
The source protocol port number |
Mask |
The route prefix length for route to source IP address |
AS |
The autonomous systems number for the source route (the AS is either the originating AS or peer AS depending on the Cflowd configuration) |
D-Port |
The destination protocol port number |
Mask |
The route prefix length for route to destination IP address (forwarding route) |
AS |
The autonomous systems number for the destination route (the AS is either the originating AS or peer AS depending on the Cflowd configuration) |
NextHop |
The next-hop address used to forward traffic associated with the flow |
Pkt-Size |
The average packet size of sampled traffic associated with this flow (total number of packets sampled/volume of traffic sampled) |
Time |
The number of seconds the flow has been active |
top-protocols protocols [clear]
tools>dump>cflowd
This command displays the summary information for the top 20 protocol traffic flows in the Cflowd cache. All statistics are calculated based on the data collected since the last clearing of the Cflowd statistics.
If the clear option clears the cache after the top protocol statistics are displayed.
n/a
specifies the type of Cflowd packet information to display
clears the cache after the packet size statistics are displayed
The following output is an example of Cflowd top protocol traffic information, and Table: Tools Dump Cflowd Top Protocols Field Descriptions describes the fields.
Output Example
NOK1# tools dump cflowd top-protocols
The top 20 IPv4 protocols seen by cflowd are:
Current Time: 08/29/2011 15:36:15
Last Cleared Time: 08/29/2011 15:35:08
Protocol ID Total Flows Packets Bytes Packets Duration % Total
-------- Flows /Sec /Flow /Pkt /Sec /Flow Bandwidth
--------------------------------------------------------------------------------
UDP 2 0 6 100 0 6 75%
pr1 1 0 6 64 0 6 24%
--------------------------------------------------------------------------------
TOTALS 3 0 6 88 0 6 100%
Label |
Description |
---|---|
Protocol ID |
The IPv4 or IPv6 protocol type. The protocol ID is either the protocol name or the decimal protocol number. |
Total Flows |
The total number of flows recorded since the last clearing of Cflowd statistics with this protocol type |
Flows/Sec |
The average number of flows detected for the associated protocol type (Total flows/number of seconds since last clear) |
Packets/Flow |
The average number of packets per flow (Total number of packets/total flows) |
Bytes/Pkt |
The average number of bytes per packet for the associated protocol type (Total number of bytes for the associated protocol/total number of packets for the associated protocol) |
Packets/Sec |
The average number of packets for the associated protocol type (Number of packets/number of seconds since last clear) |
Duration/Flow |
The average lifetime of a flow for the associated protocol type (Number of seconds since last clear/total flows) |
% Total Bandwidth |
The percentage of bandwidth consumed by the associated protocol type (Total protocol bytes/total bytes of all flows) |
control-queues failures
tools>dump
This command displays information about failed control queues.
n/a
The following output is an example of control queue failures, and Table: Control Queues Failures Field Descriptions describes the fields.
Output Example*A:NOK1# /tools dump control-queues failures
Ingress SF queue Size Free Buf Alloc Failures
------------------------------------------------------------
MDA Startup 1250 1250 0
SF Large High priority 1024 1024 0
SF Small High priority 8192 8192 0
SF Large Med priority 1024 1024 0
SF Small Med priority 8192 8192 0
SF Large Low priority 1024 1024 0
SF Small Low priority 8192 8192 0
SF Cflowd 8192 8192 0
Label |
Description |
---|---|
Ingress SF queue |
The ingress control queue |
Size |
The size of the control queue, in packets |
Free |
The remaining space in the control queue |
Buf Alloc Failures |
The number of recorded control queue failures |
eth-ring ring-index [clear]
tools>dump
This command displays Ethernet ring information.
n/a
specifies an Ethernet ring index
clears stored information for the specified Ethernet ring
gnss port-id
tools>dump
This command displays GNSS satellite signal strength information.
n/a
specifies the port ID in the format slot/mda/port
The following output is an example of GNSS information.
Output ExampleA:ALU-1># tools dump gnss 1/3/1
======================
Satellites
======================
SVID Signal-Strength
C/No (dB-Hz)
----------------------
31 50
23 48
29 47
26 45
16 45
3 45
9 44
14 42
74 40
27 40
22 40
75 33
65 31
83 26
84 24
----------------------
Entries found: 15
======================
A:ALU-1>#
lag lag-id lag-id
tools>dump
This command displays Link Aggregation Group (LAG) information.
n/a
the LAG identifier, expressed as a decimal integer
ldp-treetrace {prefix ip-prefix/mask | manual-prefix ip-prefix/mask} [path-destination ip-address] [trace-tree]
tools>dump
This command displays treetrace information. The prefix command displays automated treetrace results only if ldp-treetrace is enabled at the oam-test level. The manual-prefix command displays results discovered by a previously run ldp-treetrace manual test.
Path information displayed by the ldp-treetrace command supports SNMP. The 7705 SAR stores this information in the TIMETRA-OAM-TEST-MIB tmnxOamLTraceHopInfoTable object.
n/a
specifies the IP prefix and subnet mask
specifies the destination IP address
The following outputs are examples of ldp-treetrace information.
Note: The tools dump ldp-treetrace prefix command displays entries only if ldp-treetrace is enabled using the configure test-oam ldp-treetrace no shutdown CLI command.
Output ExampleThe following example shows automated ldp-treetrace results. This command collects all information but displays a summary of the ECMP paths indexed by the path destination (PathDst), which is the IP address used in the LSP Ping message to probe a specific ECMP path to the destination FEC.
*A:ALU-1># tools dump ldp-treetrace prefix 10.12.12.10/32
Discovered Paths:
===================
Id PathDst Egr-NextHop Reply-Rtr-Addr DisCovery-Time
discoveryTtl ProbeState ProbeTmOutCnt RtnCode
=== ================ ================ ================ ===============
001 10.1.0.5 10.10.1.2 10.12.12.10 12/19/2006 05:11:01
007 OK 00 EgressRtr
002 10.1.0.9 10.10.1.2 10.12.12.10 12/19/2006 05:11:01
007 OK 00 EgressRtr
003 10.1.0.15 10.10.1.2 10.12.12.10 12/19/2006 05:11:01
007 OK 00 EgressRtr
004 10.1.0.19 10.10.1.2 10.12.12.10 12/19/2006 05:11:01
007 OK 00 EgressRtr
005 10.1.0.24 10.10.1.2 10.12.12.10 12/19/2006 05:11:01
007 OK 00 EgressRtr
…….
051 10.1.0.243 10.10.1.2 10.12.12.10 12/19/2006 05:11:01
007 OK 00 EgressRtr
052 10.1.0.247 10.10.1.2 10.12.12.10 12/19/2006 05:11:01
007 OK 00 EgressRtr
053 10.1.0.252 10.10.1.2 10.12.12.10 12/19/2006 05:11:01
007 OK 00 EgressRtr
054 10.1.0.255 10.10.1.2 10.12.12.10 12/19/2006 05:11:01
ldp-treetrace discovery state: Done
ldp-treetrace discovery status: ' OK '
Total number of discovered paths: 54
Total number of probe-failed paths: 0
Total number of failed traces: 0
Output Example
The following example shows an automated ldp-treetrace with a path destination. This command displays the details of the label stack at each hop by filtering on a specific ECMP path.
tools dump ldp-treetrace prefix 10.12.12.10/32 path-destination 10.1.0.5
FEC: 10.12.12.10/32 PathDst: 10.1.0.5
==================================================
Protocol Legend: L - LDP, R - RSVP, U - Not Applicable
HopId HopAddr TTL Label1 Label2 Label3 Label4 Label5
===== ================ === ======= ======= ======= ======= =======
277 10.12.12.10 007 000000L 000000U 000000U 000000U 000000U
223 10.1.1.17 006 001609L 000000U 000000U 000000U 000000U
196 10.2.1.2 005 001609L 000000U 000000U 000000U 000000U
187 10.2.1.1 004 001609L 000000U 000000U 000000U 000000U
184 10.1.1.11 003 001609L 000000U 000000U 000000U 000000U
183 10.1.1.1 002 001609L 000000U 000000U 000000U 000000U
182 10.10.1.2 001 001609L 000000U 000000U 000000U 000000U
Total number of Hops: 7
mpls-resources
tools>dump
This command displays FEC-to-NHLFE (next hop label forwarding entry) and ILM (incoming label message) information for MPLS.
n/a
persistence
tools>dump
This command enables the context to display persistence information.
n/a
dhcp-server [record record-key]
tools>dump>persistence
This command displays persistence information for the DHCP server.
n/a
specifies the record identification number
The following output is an example of DHCP server persistence information, and Table: DHCP Server Persistence Field Descriptions describes the fields.
Output ExampleA:7705# tools dump persistence dhcp-server
-----------------------------------
Persistency File Info
-----------------------------------
Filename : cf3:\dhcp_serv.001
ClientDescr : dhcp-server
UserDataSize : 372
DataPadding : 128
NumberOfEntries : 4112
FileSize : 8225
Version : 0001
Entries in use : 9
State : ACTIVE
Record Key Output Example
A:7705# tools dump persistence dhcp-server record 0x1
-----------------------------------
Persistency File Record
-----------------------------------
Filename : cf3:\dhcp_serv.001
Key : 00000001
Last Update : 2013/07/12 11:45:37 (UTC)
Action : ADD
Data
service Id : 0
server : defaultDhcpServer
IP : 10.1.1.20
MAC : 00:11:22:33:01:07
XID : 0x0cbe9d53
start time : 2013/07/12 11:45:37 (UTC)
expires : 2013/07/21 11:45:37 (UTC)
failctrl : local
opt60 len : 3
opt82 len : 0
Label |
Description |
---|---|
Filename |
The name and location of the persistence information file |
ClientDescr |
The description of the client |
UserDataSize |
The size of the user data, in bytes |
DataPadding |
The size of the data padding, in bytes |
NumberOfEntries |
The number of entries in the persistence information file It is a combination of leases given and may also contain DHCP servers configured |
FileSize |
The total size of records in the persistence information file, in blocks of 512 bytes |
Version |
The version of the persistence information file |
Entries in use |
The number of entries currently in use |
State |
The state of the persistence information file |
Key |
The record key number |
Last Update |
The date and time of the last record update |
Action |
The action taken during the last record update |
Data |
|
service Id |
The service ID number |
server |
The DHCP server name |
IP |
The IP address of the lease |
MAC |
The MAC address associated with the lease |
XID |
The transaction ID (XID) used in DHCPDISCOVER packets |
start time |
The start time and date of the current lease |
expires |
The expiry time and date of the current lease |
failctrl |
The failure control (not supported on the 7705 SAR) |
opt60 len |
The length of the DHCP option 60 message |
opt82 len |
The length of the DHCP option 82 message |
summary
tools>dump>persistence
This command displays persistence summary information.
n/a
The following output is an example of persistence summary information, and Table: Persistence Summary Field Descriptions describes the fields.
Output ExampleA:7705# tools dump persistence summary
=====================================================================
Persistence Summary on Slot A
=====================================================================
Client Location Entries in use Status
---------------------------------------------------------------------
dhcp-server cf3:\dhcp_serv.001 2 ACTIVE
=====================================================================
Persistence Summary on Slot B
=====================================================================
Client Location Entries in use Status
---------------------------------------------------------------------
dhcp-server cf3:\dhcp_serv.001 2 ACTIVE
Label |
Description |
---|---|
Client |
The name of the client |
Location |
The name and location of the persistence information file |
Entries in use |
The number of entries in use |
Status |
The status of the persistence information file |
port port-id discard [clear]
tools>dump
This command displays invalid Layer 2 packets that have been discarded for the specified port. Reasons for packet discards include an invalid VLAN identifier or an invalid Etype. The CLI shows the header for the invalid VLAN identifier and invalid Etype.
n/a
specifies the port ID in the format slot/mda/port
clears the packets after viewing
ppp port-id
tools>dump
This command displays PPP information for a port.
n/a
specifies the port ID
Syntax: port-id slot/mda/port[.channel]
bundle bundle-type-slot/mda.bundle-num
bundle keyword
type ima, ppp
bundle-num 1 to 32
service
tools>dump
This command enables the context to display service information.
n/a
evpn usage
tools>dump>service
tools>dump>service>id
This command displays the consumed EVPN resources for the system or for a specified service.
The following output is an example of EVPN usage for the system and a specified service.
Output ExampleFor the system:
*A:PE71# tools dump service evpn usage
EVPN usage statistics at 000 02:01:03.810:
MPLS-TEP : 5
VXLAN-TEP : 0
Total-TEP : 5/ 8191
Mpls Dests (TEP, Egress Label + ES + ES-BMAC) : 16
Vxlan Dests (TEP, Egress VNI) : 0
Total-Dest : 17/131071
Sdp Bind + Evpn Dests : 20/196607
ES L2/L3 PBR : 0/ 32767
*A:PE71#
For a specific service:
*A:PE71# tools dump service id 7 evpn usage
Evpn Tunnel Interface IP Next Hop: N/A
*A:PE71#
id service-id
tools>dump>service
This command enables the context to display information for the specified service.
n/a
specifies an existing service ID
evpn-mpls [clear]
tools>dump>service>id
This command displays the EVPN-MPLS data for the specified service.
clears the EVPN-MPLS data for the specified service
ip-transport ipt-id
tools>dump>service>id
This command enables the context to display information for a specific IES or VPRN IP transport subservice.
n/a
specifies the IP transport subservice physical port identifier
remote-host host-id check-tcp
tools>dump>service>id>ip-transport
This command displays information for a TCP connection check to a remote host for the specified service.
n/a
specifies the remote host identifier
displays information for a TCP connection check to a remote host
loopback
tools>dump>service>id
This command displays loopback information for a SAP or an SDP bind for the specified service.
n/a
sap sap-id
tools>dump>service>id>loopback
This command displays loopback information for a specified SAP in the specified service.
n/a
specifies the SAP binding identifier
sdp sdp-id:vc-id
tools>dump>service>id>loopback
This command displays loopback information for a specified SDP binding in the specified service.
n/a
specifies the SDP binding identifier
the virtual circuit identifier
sap sdp-id stats [clear]
tools>dump>service>id
This command displays SAP information for the specified service.
n/a
specifies the SAP binding identifier
clears statistics after viewing
displays statistics associated with this SAP
The following output is an example of the discard statistics, and Table: Service SAP Field Descriptions describes the fields.
Output ExampleA:7705# tools dump service id 200 sap 1/X3/6:100 stats
===========================================================
Service Id 200 SAP 1/X3/6:100 VPLS Ingress Debug Stats
===========================================================
total number of discarded packets | 1
total number of discarded bytes | 996
number of discards due to source suppression | 0
number of discards due to split horizon | 0
number of discards due to mesh to mesh | n/a
number of discards due to unknown DA | 0
number of discards due to unknown SA | 0
number of discards due to service MTU | 0
number of discards due to STP not in fwding state | 1
number of other discards | 0
===========================================================
Service Id 200 SAP 1/X3/6:100 VPLS Egress Debug Stats
===========================================================
total number of discarded packets | 0
number of unicast discards due to pool exhaustion | 0
number of multicast discards due to pool exhaustion | 0
number of unicast discards due to queue overflow | 0
number of multicast discards due to queue overflow | 0
number of other discards | 0
Label |
Description |
---|---|
total number of discarded packets |
The total number of discarded ingress or egress packets for the specified SAP or SDP binding |
total number of discarded bytes |
The total number of discarded ingress bytes for the specified SAP or SDP binding |
number of discards due to source suppression |
The total number of ingress discards due to source suppression for the specified SAP or SDP binding |
number of discards due to split horizon |
The total number of ingress discards due to split horizon for the specified SAP or SDP binding |
number of discards due to mesh to mesh |
The total number of ingress discards due to mesh-to-mesh forwarding for the specified mesh SDP |
number of discards due to unknown DA |
The total number of ingress discards due to an unknown destination address for the specified SAP or SDP binding |
number of discards due to unknown SA |
The total number of ingress discards due to an unknown source address for the specified SAP or SDP binding |
number of discards due to service MTU |
The total number of ingress discards due to the packet size exceeding the configured maximum transmission unit for the specified SAP or SDP binding |
number of discards due to STP not in fwding state |
The total number of ingress discards due to an inactive VPLS endpoint determined by the Spanning Tree Protocol for the specified SAP |
number of other discards |
The total number of ingress or egress discards that do not match a listed category |
number of unicast discards due to pool exhaustion |
The total number of egress unicast discards due to pool exhaustion for the specified SAP or SDP binding |
number of multicast discards due to pool exhaustion |
The total number of egress multicast discards due to pool exhaustion for the specified SAP or SDP binding |
number of unicast discards due to queue overflow |
The total number of egress unicast discards due to queue overflow for the specified SAP or SDP binding |
number of multicast discards due to queue overflow |
The total number of egress multicast discards due to queue overflow for the specified SAP or SDP binding |
sap sdp-id[:vc-id] stats [clear]
tools>dump>service>id
This command displays SDP binding information for the specified service.
n/a
specifies the SDP binding identifier
specifies the virtual circuit identifier
clears statistics after viewing
displays statistics associated with the specified SDP
network-latency-measurement
tools>dump>service>id
This command displays minimum, current, and maximum latency measurement values.
n/a
The following output is an example of network latency measurement information.
Output ExampleA:SAR18-11-2# tools dump service id 100 network-latency-measurement
------------------------------------------------------------------------------------
Path Average Latency Measurements (us)
------------------------------------------------------------------------------------
Spoke-sdp Min Current Max Last-update
121:100 450 500 600 02/21/23 20:17:14
122:200 350 600 800 02/21/23 20:17:14
....
The "Path Average Latency Measurements" output is only shown if the Cpipe has a timestamp. If a path is up but has not completed the first latency measurement, "NA" is displayed. If a path that was up goes down, the last valid value is displayed.
For Cpipes with PW redundancy, only the active path average latency measurement is shown; other paths are not shown.
If a path is administratively down, "NA" is displayed.
Label |
Description |
---|---|
Path Average Latency Measurements (us) | |
Spoke-sdp |
Identifies the spoke SDP associated with the Cpipe |
Min |
The minimum latency value at the time of the last update |
Current |
The current latency value at the time of the last update |
Max |
The maximum latency value at the time of the last update |
Last-update |
The time that the latency values were last updated |
ipsec-tunnel ipsec-tunnel-name stats
tools>dump>service
This command displays the IPSec tunnel information.
the name of the IPSec tunnel
displays statistics associated with the IPSec tunnel
The following output is an example of IPSec tunnel information, and Table: IPSec Tunnel Field Descriptions describes the fields.
Output Example*A:7705:Dut-A# tools dump service ipsec-tunnel tunnelPrivateSide_1.1 stats
=================================================================
Discard Stats for Ipsec-Tunnel tunnelPrivateSide_1.1 (tunnelId 1 svcId 1001)
=================================================================
Outbound Discard Stats:
Security policy misses | 0
Invalid security association | 0
Sequence number wrap errors | 0
Buffer exhaustion errors | 0
IP-frag buffer exhaustion errors | 0
Enqueue errors | 0
Tunnel peer-ip-address not reachable | 0
Tunnel peer-ip-address next-hop not reachable via IP| 0
Egress uplink interface does not support encryption | 0
Drop Too Big/Df-set Pkts | 0
Other discards | 0
=================================================================
Inbound Discard Stats:
Authentication failures | 0
Security policy misses | 0
NATT UDP ports mismatch (src/dst) | 0
IP Proto mismatch | 0
Tunnel and SPI cross validation errors | 0
IP fragmented packets (Unsupported) | 0
Padding failures | 0
NULL SeqNum | 0
Enqueue errors | 0
Sequence number too old in window (Anti-Replay) | 0
Duplicated sequence number in window (Anti-Replay) | 0
Buffer exhaustion errors | 0
Other discards | 0
=================================================================
Field |
Description |
---|---|
Outbound Discard Stats: |
|
Security policy misses |
The number of outbound packets discarded because of a security policy miss that can occur when a clear text packet source or destination IP address does not match any security policy entry for the IPSec tunnel. Discards are due to either an incorrect policy configuration or a packet that should have been denied entry to the tunnel. |
Invalid security association |
The number of outbound packets discarded because of an invalid security association (SA). Discards can be due to an IKE failure to negotiate the SA, an incorrect configuration in the SA for manual keying, or incomplete IPSec tunnel negotiation. |
Sequence number wrap errors |
The number of outbound packets discarded because the IPSec tunnel anti-replay sequence number has exceeded the maximum value allowed prior to completion of an SA re-keying |
Buffer exhaustion errors |
The number of outbound packets discarded because buffers were not available before packets were sent to the encryption engine queue. This condition can occur when the encrypting MDA is experiencing buffer congestion. |
IP-frag buffer exhaustion errors |
The number of outbound packets discarded because buffers were not available when fragmentation occurred before encryption on the packet. This condition can occur when the encrypting MDA is experiencing buffer congestion. |
Enqueue errors |
The number of outbound packets discarded because the encryption engine queue was full. This condition can occur when the encrypting MDA is experiencing buffer congestion. |
Tunnel peer-ip-address not reachable |
The number of outbound packets discarded because a route to the peer gateway IP address cannot be found. This can occur due to a network design issue or a temporary network outage. |
Tunnel peer-ip-address next-hop not reachable via IP |
The number of outbound packets discarded because the IPSec tunnel peer gateway route next hop is not in the supported IP next-hop or MPLS tunnel next-hop list. This can occur due to a network design issue or a temporary network outage. |
Egress uplink interface does not support encryption |
The number of outbound packets discarded because the outgoing interface for this IPSec tunnel is on an MDA that does not have encryption hardware. This can be due to a network design issue. |
Drop Too Big/Df-set Pkts |
The number of outbound packets discarded because a clear text packet cannot be fragmented when the do-not-fragment (DF) flag is set in the IP packet header and the outgoing IP interface MTU is too small for the encrypted packet |
Other discards |
The number of outbound packets discarded because of miscellaneous internal errors related to:
|
Inbound Discard Stats: |
|
Authentication failures |
The number of inbound packets discarded because of an inability to authenticate the packet with the current authentication key |
Security policy misses |
The number of inbound packets discarded because either:
|
NATT UDP ports mismatch (src/dst) |
The number of inbound packets discarded because the source or destination UDP port for NAT-T is different from the configured UDP port |
IP Proto mismatch |
The number of inbound packets discarded because of an IP protocol mismatch that can occur when NAT-T is configured and the protocol is not UDP or when NAT-T is not configured and the protocol is not ESP |
Tunnel and SPI cross validation errors |
The number of inbound packets discarded because the source or destination IP address of an encrypted packet does not match the expected IPSec gateway source or destination IP address for the SPI |
IP fragmented packets (Unsupported) |
The number of inbound packets discarded because the encrypted packet was fragmented. Fragmentation is not supported on IPSec encrypted packets. |
Padding failures |
The number of inbound packets discarded because a padding error was detected on the encrypted packet |
NULL SeqNum |
The number of inbound packets discarded because the sequence number is 0 (invalid as per RFC 4303) |
Enqueue errors |
The number of inbound packets discarded because the decryption engine queue is full. This condition can occur when the decrypting MDA is experiencing buffer congestion. |
Sequence number too old in window (Anti-Replay) |
The number of inbound packets discarded because the sequence number is lower than the lowest sequence number in the anti-replay window and therefore is considered too old |
Duplicated sequence number in window (Anti-Replay) |
The number of inbound packets discarded because a packet’s sequence number is duplicated. Duplicate sequence numbers are not allowed in an anti-replay window. |
Buffer exhaustion errors |
The number of inbound packets discarded because buffers were not available before packets were sent to the decryption engine queue. This condition can occur when the decrypting MDA is experiencing buffer congestion. |
Other discards |
The number of inbound packets discarded because of miscellaneous internal errors related to:
|
loopback
tools>dump>service
This command displays all active Ethernet SAP loopbacks on the node. Only internal loopback mode is supported.
n/a
bgp-evpn
tools>dump>service
This command enables the context for service system information.
bgp-evpn
tools>dump>service>system
This command enables the context for BGP-EVPN service system information.
ethernet-segment name evi value df
tools>dump>service>system>bgp-evpn
This command displays information on the computed DF PE for a specified EVI.
specifies the name of the Ethernet segment
specifies the EVI
keyword for designated forwarder
The following output is an example of Ethernet segment information.
Output Example*A:PE2# tools dump service system bgp-evpn ethernet-segment "ESI-71" evi 1 df
[07/15/2015 21:52:08] Computed DF: 192.0.2.72 (Remote) (Boot Timer Expired: Yes)
vpls-fdb-stats [clear]
tools>dump>service
This command displays the VPLS FDB statistics.
clears the VPLS FDB statistics after viewing
The following output is an example of VPLS FDB statistics, and Table: System-Limits Field Descriptions describes the fields.
Output Example*A:Sar18 Dut-B# tools dump service vpls-fdb-stats
Service Manager VPLS FDB info at 042 02:39:08.680:
Statistics last cleared at 000 00:00:00.000
Statistic | Count
--------------------------+-------------
FdbEntriesInUse | 0
TotalFdbEntries | 65535
FdbMimDestIdxInUse | 0
TotalFdbMimDestIdxEntries | 511
FdbIsidIdxInUse | 0
TotalFdbMimIsidIdxEntries | 16384
MacAddMsgs | 0
MacDeleteMsgs | 0
MacQueryMsgs | 0
UnknownMsgs | 0
MalformedMsgs | 0
FailedMsgs | 0
FdbHwTableFull | 0
FdbHwLimitExceeded | 0
FdbTableFull | 0
FdbLimitExceeded | 0
FdbMimDestIdxExhausted | 0
MacAddReqs | 0
DupMacAddReqs | 0
DroppedMacAddReqs | 0
FailedMacAddReqs | 0
MacDelReqs | 0
DupMacDelReqs | 0
DroppedMacDelReqs | 0
FailedMacDelReqs | 0
system-limits
tools>dump
This command displays the resource limits of the current system configuration.
The system-limits command is only available on the following 7705 SAR systems:
7705 SAR-8 Shelf V2
7705 SAR-18
n/a
The following output is an example of system limits information, and Table: System-Limits Field Descriptions describes the fields.
Output ExampleA:7705# tools dump system-limits
| Limit
--------------------------------------+-----------
IPv4 FIB Table Size | 65536
IPv6 FIB Table Size | 32768
Max Number of Network Interfaces | 256
Max Number of Service Interfaces | 1024
Max Number of Total Interfaces | 1024
Max Number of IPv6 Network Interfaces | 255
Max Number of IPv6 Service Interfaces | 384
Max Number of IPv6 Total Interfaces | 384
VPRN Instances Supported | 62
VPLS Instances Supported | 64
Max Number of BGP Peers | 320
Max Number of IP/Mac Filters | 512
Label |
Description |
---|---|
IPv4 FIB Table Size |
The maximum number of IPv4 addresses allowed in the forwarding information base table (FIB). IPv4 router interfaces that are on cards equipped with hardware to support larger tables will have a higher maximum number of addresses than on cards that are not equipped with this hardware. |
IPv6 FIB Table Size |
The maximum number of IPv6 addresses allowed in the forwarding information base table (FIB). IPv6 router interfaces that are on cards equipped with hardware to support larger tables will have a higher maximum number of addresses than on cards that are not equipped with this hardware. |
Max Number of Network Interfaces |
The maximum number of IPv4 network interfaces allowed on an adapter card |
Max Number of Service Interfaces |
The maximum number of IPv4 service interfaces allowed on an adapter card |
Max Number of Total Interfaces |
The maximum number of total IPv4 interfaces allowed on a system |
Max Number of IPv6 Network Interfaces |
The maximum number of IPv6 network interfaces allowed on an adapter card |
Max Number of IPv6 Service Interfaces |
The maximum number of IPv6 service interfaces allowed on an adapter card |
Max Number of IPv6 Total Interfaces |
The maximum number of total IPv6 interfaces allowed on a system |
VPRN Instances Supported |
The total number of VPRN instances that are supported |
VPLS Instances Supported |
The total number of VPLS instances that are supported |
Max Number of BGP Peers |
The maximum number of BGP peers |
Max Number of IP/Mac Filters |
The maximum number of IP/MAC filters |
system-resources slot-number
tools>dump
This command displays system resource information.
n/a
specifies a specific slot to view system resources information
The following output is an example of system resources information, and Table: System-Resources Field Descriptions describes the fields.
Output Example*A:7705# tools>dump system-resources 1/1
Mda-1/1 Resource Usage
| Total | Allocated | Free
-------------------------------+-----------+-----------+------------
Access Ingress Queues | 2048 | 0 | 2048
Egress Queues | 2112 | 0 | 2112
Access Egress Queues | 2048 | 0 | 2048
Network Egress Queues | 2048 | 0 | 2048
SAP Objects | 512 | 0 | 512
VPLS SAP Objects | 128 | 0 | 128
(1/1/1) | 128| 0| 128
(1/1/2) | 128| 0| 128
(1/1/3) | 128| 0| 128
(1/1/4) | 128| 0| 128
(1/1/5) | 128| 0| 128
(1/1/6) | 128| 0| 128
(1/1/7) | 128| 0| 128
(1/1/8) | 128| 0| 128
Network Interfaces | 128 | 0 | 128
Filters | 32 | 0 | 32
Service Interfaces | 512 | 0 | 512
IpV6 Network Interfaces | 128 | 0 | 128
IpV6 Service Interfaces | 512 | 0 | 512
Shaper Groups | 64 | 0 | 64
Label |
Description |
---|---|
Access Ingress Queues |
The number of access ingress queues allowed on an adapter card (total, allocated, and free) |
Egress Queues |
The number of egress queues allowed on an adapter card (total, allocated, and free) |
Access Egress Queues |
The number of access egress queues allowed on an adapter card (total, allocated, and free) |
Network Egress Queues |
The number of network egress queues allowed on an adapter card (total, allocated, and free) |
SAP Objects |
The number of SAP objects allowed on an adapter card (total, allocated, and free) |
VPLS SAP Objects |
The number of VPLS SAP objects allowed on an adapter card (total, allocated, and free) |
Network Interfaces |
The number of network interfaces allowed on an adapter card (total, allocated, and free) |
Filters |
The number of filters allowed on an adapter card (total, allocated, and free) |
Service Interfaces |
The number of service interfaces allowed on an adapter card (total, allocated, and free) |
IpV6 Network Interfaces |
The number of IPv6 network interfaces allowed on an adapter card (total, allocated, and free) |
IpV6 Service Interfaces |
The number of IPv6 service interfaces allowed on an adapter card (total, allocated, and free) |
Shaper Groups |
The number of shaper groups allowed on an adapter card (total, allocated, and free) |
testhead test-name test-name [test-owner test-owner]
tools>dump
This command displays Y.1564 test head debug statistics.
n/a
specifies a Y.1564 test by name
specifies a Y.1564 test owner