Monitoring IP
This section explains how to set a statistics baseline and use the show commands to view your IP configuration and monitor IP interfaces and statistics.
System Event Logs
To troubleshoot and monitor IP, use the following system event logs:
- ipAccessListIP access list matching
- ipEngineIP chassis manager
- ipGeneral IP general information
- ipIfCreatorIP interface creator events
- ipInterfaceIP interface events
- ipNhopTrackerGeneralNext-hop tracker for IP shared interfaces
- ipProfileMgrIP profile manager events
- ipRoutePolicy IP routing policy events
- ipRouteTableIP routing table events
- ipTrafficIP frame transmit and receive events
- ipTunnelIP tunnel events
For more information about using event logs, see the JUNOSe System Event Logging Reference Guide.
Establishing a Baseline
IP statistics are stored in system counters. The only way to reset the system counters is to reboot the router. You can, however, establish a baseline for IP statistics by setting a group of reference counters to zero.
baseline ip
- Use to set a statistics baseline for IP statistics. Baselining is not supported for IP socket statistics.
- The router implements the baseline by reading and storing the statistics at the time the baseline is set and then subtracting this baseline whenever baseline-relative statistics are retrieved.
- Use the delta keyword with IP show commands to specify that baselined statistics are to be shown.
- Example
host1#baseline ipThere is no no version. baseline ip udp
- Use to set a statistics baseline for UDP statistics.
- The router implements the baseline by reading and storing the statistics at the time the baseline is set and then subtracting this baseline whenever baseline-relative statistics are retrieved.
- Use the delta keyword with IP show commands to specify that baselined statistics are to be shown.
- Example
host1#baseline ip udpThere is no no version. baseline tcp
- Use to set a statistics baseline for all (both IPv4 and IPv6) TCP statistics or for only IPv4 or IPv6 statistics.
- The router implements the baseline by reading and storing the statistics at the time the baseline is set and then subtracting this baseline whenever baseline-relative statistics are retrieved.
- Use the ip keyword to implement a baseline for only IPv4 statistics.
- Use the delta keyword with IP show commands to specify that baselined statistics are to be shown.
- Example 1
host1#baseline tcpExample 2 host1#baseline ip tcpThere is no no version. IP show Commands
You can monitor the following aspects of IP using show ip commands:
To set a statistics baseline for IP interfaces, use the baseline tcp and baseline ip udp commands. Use the delta keyword with IP show commands to specify that baselined statistics are to be shown.
You can use the output filtering feature of the show command to include or exclude lines of output based on a text string that you specify. See JUNOSe System Basics Configuration Guide, Chapter 2, Command-Line Interface, for details.
show access-list
host1#show access-listIP Access List 1:permit ip 172.31.192.217 0.0.0.0 0.0.0.0 255.255.255.255permit ip 12.40.0.0 0.0.0.3 0.0.0.0 255.255.255.255deny ip 0.0.0.0 255.255.255.255 0.0.0.0 255.255.255.255IP Access List 2:permit ip 172.19.0.0 0.0.255.255 0.0.0.0 255.255.255.255deny ip 0.0.0.0 255.255.255.255 0.0.0.0 255.255.255.255IP Access List 10:permit ip 0.0.0.0 255.255.255.255 0.0.0.0 255.255.255.255IP Access List 11:deny ip 0.0.0.0 255.255.255.255 0.0.0.0 255.255.255.255show arp
- AddressIP address of the entry
- AgeTime to live for this entry in seconds
- Hardware AddrPhysical (MAC) address of the entry
- InterfaceInterface-specifier of the entry (for example, fastEthernet6/0 is an Ethernet interface on slot 6, port 0)
- *Indicates that an ARP entry was added because of an arp validate command, rather than just an arp command.
host1#show arpAddress Age Hardware Addr Interface172.31.192.217 21340 00d0.58f2.67e0 loopback1192.168.1.0 20730 00e0.09ed.5312 fastEthernet6/0 *192.168.1.1 12550 00e0.b06a.4c75 fastEthernet6/0 *192.168.1.217 21600 0090.1a00.0230 fastEthernet6/0 *192.168.1.255 21600 00f0.c2d1.1200 fastEthernet6/0 *12.40.0.2 24320 0020.6393.4233 atm5/0.1172.18.2.1 21600 0020.bed2.8738 atm5/1.1172.18.2.2 21600 0020.5b91.60f2 atm5/1.1172.31.192.206 21600 00d0.43b5.1032 atm5/1.1show forwarding-table route-holddown
- Use to display the configured hold-down time allotted after an initial routing table change for the accumulation and subsequent distribution of a set of routing table updates to the line modules. The default value is 3 seconds; the range of values is 030 seconds.
- A higher hold-down setting can enhance SRP performance; however, a higher setting can also delay the implementation of routing table changes on the line modules.
- A hold-down timer value of zero (0) distributes an update after each change to the routing table.
- Example
host1#show forwarding-table route-holddownHold-down timer value is 3 seconds.show ip
- IP Router IdRouter ID number
- Router NameRouter name
- Default TTLDefault IP TTL (time-to-live) value
- Reassemble TimeoutAmount of time (in minutes) IP waits for missing packet fragments before it drops the fragments it is holding
- SA Validate TrapWhether the source address validation trap is enabled
host1#show ipIP Router Id: 192.168.1.155Router Name: defaultDefault TTL: 60Reassemble Timeout: 30SA Validate Trap: falseshow ip address
- Use to display detailed or summary information about a particular IP interface.
- Specify a VRF name to view information for only that VRF.
- Use the brief keyword to display summary information about the interface.
- Use the detail keyword to display detailed information about the interface.
- Field descriptions
- Network ProtocolsNetwork protocols configured on this interface
- Internet addressIP address and subnet mask of this interface
- Broadcast addressBroadcast address of this interface
- Operational MTUMTU of this interface
- Administrative MTUValue of the MTU if it has been administratively overridden using the configuration
- Operational speedSpeed of the interface
- Administrative speedValue of the speed if it has been administratively overridden using the configuration
- Discontinuity TimeValue of the SysUpTime when the interface statistics last started being valid
- Router advertisementStatus of router discovery advertisement: enabled, disabled
- Proxy ArpStatus of the feature: enabled, disabled
- Administrative debounce-timeConfigured debounce behavior, enabled or disabled. If enabled, indicates time in milliseconds that the router waits before generating an up or down event in response to a state change in the interface. If the state changes back before the debounce timer expires, no state change is reported.
- Operational debounce-timeCurrent debounce behavior, enabled or disabled. If enabled, indicates time in milliseconds that the router waits before generating an up or down event in response to a state change in the interface. If the state changes back before the debounce timer expires, no state change is reported.
- Access routingAccess route addition: enabled, disabled
- Multipath modeEqual cost multipath mode method: hashed, round-robin
- In Received Packets, BytesTotal number of packets and bytes received on this interface
- Unicast Packets, BytesUnicast packets and bytes received on the IP interface; link-local received multicast packets (non-multicast-routed frames) are counted as unicast packets
- Multicast Packets, BytesMulticast packets and bytes received on the IP interface which are then multicast-routed are counted as multicast packets
- In Policed Packets, BytesPackets and bytes that were received and dropped because of rate limits
- In Error PacketsNumber of packets received with errors
- In Invalid Source Address PacketsPackets received with invalid source address (for example, spoofed packets)
- In Discarded PacketsPackets received that were discarded for reasons other than rate limits, errors, and invalid source address
- Out Forwarded Packets, BytesTotal number of packets and bytes that were sent from this interface
- Unicast Packets, BytesUnicast packets and bytes that were sent from this interface
- Multicast Routed Packets, BytesMulticast packets and bytes that were sent from this interface
- Out Scheduler Drops Committed Packets, BytesOutgoing packets and bytes dropped by the scheduler even though they had a committed traffic contract
- Out Scheduler Drops Conformed Packets, BytesOutgoing packets and bytes dropped by the scheduler even though they conformed to the traffic contract
- Out Scheduler Drops Exceeded Packets, BytesOutgoing packets and bytes that were dropped by the scheduler because they exceeded the contract
- Out Policed Packets, BytesOutgoing packets and bytes dropped because of rate limiters
- Out Discarded PacketsOutgoing packets that were discarded for reasons other than those dropped by the scheduler and those dropped because of rate limits
host1#show ip address 10.6.136.73fastEthernet0/0 is up, line protocol is upNetwork Protocols: IPInternet address is 10.6.136.73/255.255.128.0Broadcast address is 255.255.255.255Operational MTU = 0 Administrative MTU = 0Operational speed = 1 Administrative speed = 0Discontinuity Time = 5766Router advertisement = disabledProxy Arp = disabledAdministrative debounce-time = 10 mSecsOperational debounce-time = disabledAccess routing = disabledMultipath mode = hashedIn Received Packets 2849, Bytes 759428Unicast Packets 2849, Bytes 759428Multicast Packets 0, Bytes 0In Policed Packets 0, Bytes 0In Error Packets 0In Invalid Source Address Packets 0In Discarded Packets 0Out Forwarded Packets 1866, Bytes 84650Unicast Packets 1866, Bytes 84650Multicast Routed Packets 0, Bytes 0Out Scheduler Drops Committed Packets 0, Bytes 0Out Scheduler Drops Conformed Packets 0, Bytes 0Out Scheduler Drops Exceeded Packets 0, Bytes 0Out Policed Packets 0, Bytes 0Out Discarded Packets 0show ip as-path-access-list
host1#show ip as-path-access-listAS Path Access List 1:permit .*AS Path Access List 2:deny .*AS Path Access List 3:permit _109_deny .*AS Path Access List 4:permit _109$deny .*AS Path Access List 10:deny _109$permit ^108_deny .*show ip community-list
host1#show ip community-listCommunity List 1:permit 752877569 (11488:1)permit 752877570 (11488:2)permit 752877571 (11488:3)permit 752877572 (11488:4)Community List 2:permit 4294967043 (local-as)show ip forwarding-table slot
- Use to display details on the forwarding table for a specific line module, including the memory used by each virtual router configured on the line module and free memory available on the module.
- The Load Errors field records any failed routing table distribution attempt as an error. Attempts can fail for many reasons during normal operation; a failed attempt does not necessarily indicate a problem. It is normal to see many Load Errors per day.
- If the Status field does not indicate Valid, then the routing table distribution has failed constantly for that VR. It is normal and appropriate behavior for the Status field to indicate Valid while the Load Error field increases daily.
- Field descriptions
- Free MemoryAmount of routing table memory free on the line module, in kilobytes
- Virtual RouterName of the virtual routers configured on the line module
- Memory (KB)Amount of routing table memory consumed by the virtual router, in kilobytes
- Load ErrorsCount of errors made while loading the routing table on the line module
- StatusWhether the routing table for the virtual router is valid
host1#show ip forwarding-table slot 9Free Memory = 3,166KBVirtual Router Memory Load Errors Status(KB)---------------- --------- ------------- --------vr1 4128 0 Validvr2 3136 0 Validvr3 2256 0 Validdefault 1024 0 Valid-----------------------------------------------------------show ip interface
- Use to display the current state of all IP interfaces or the IP interfaces you specify.
- The default is all interface types and all interfaces.
- The show-virtual-router-keyword displays virtual router information.
- Field descriptions
- interfaceInterface type and interface specifier
- interface statusStatus of the interface
- line protocolStatus of the line protocol
- DescriptionText description or alias if configured for the interface
- Link up/down trapStatus of SNMP link up/down traps on the interface
- Internet addressIP address of the interface
- IP Statistics Rcvd:
- local destinationFrames with this router as their destinations
- hdr errorsNumber of packets containing header errors
- addr errorsNumber of packets containing addressing errors
- unkn protoNumber of packets received containing unknown protocols
- discardsNumber of discarded packets
- reasm okNumber of reassembled packets
- reasm reqNumber of requests for reassembly
- reasm failsNumber of reassembly failures
- frag okNumber of packets fragmented successfully
- frag reqNumber of frames requiring fragmentation
- frag failsNumber of packets unsuccessfully fragmented
- generatedNumber of packets generated
- no routesNumber of packets that could not be routed
- discardsNumber of packets that could not be routed that were discarded
- errorsError packets received
- dst unreachPackets received with destination unreachable
- time exceedPackets received with time-to-live exceeded
- param probsPackets received with parameter errors
- src quenchSource quench packets received
- redirectReceive packet redirects
- echo reqEcho request (ping) packets
- echo rpyEcho replies received
- timestamp reqRequests for a timestamp
- timestamp rpyReplies of timestamp requests
- addr mask reqMask requests sent
- addr mask rpyMask replies sent
- errorsError packets sent
- dst unreachPackets sent with destination unreachable
- time excdPackets sent with time-to-live exceeded
- param probsPackets sent with parameter errors
- src quenchSource quench packets sent
- redirectSend packet redirects
- timestamp reqRequests for a timestamp
- timestamp rpyReplies to timestamp requests
- addr mask reqAddress mask requests
- addr mask rpyAddress mask replies
- Unicast Packets, BytesUnicast packets and bytes received on the IP interface; link-local received multicast packets (non-multicast-routed frames) are counted as unicast packets
- Multicast Packets, BytesMulticast packets and bytes received on the IP interface which are then multicast-routed are counted as multicast packets
- In Forwarded Packets, BytesPackets and bytes forwarded into an output IP interface
- In Total Dropped Packets, BytesTotal number of packets and bytes that were dropped on the interface; sum of all the drop reasons indented below this field
- In Policed PacketsPackets discarded on a receive IP interface because of token bucket limiting, a drop action in a policy, or discarded MAC validation packets
- In Invalid Source Address PacketsPackets discarded on a receive IP interface due to invalid IP source address (sa-validate enabled)
- In Error PacketsPackets discarded on a receive IP interface due to IP header errors
- In Discarded PacketsPackets discarded on the ingress interface due to a configuration problem rather than a problem with the packet itself
- In Fabric Dropped PacketsPackets discarded on a receive IP interface due to internal fabric congestion
- Unicast Packets, BytesUnicast packets and bytes forwarded out the IP interface
- Multicast Routed Packets, BytesMulticast packets and bytes forwarded out the IP interface
- Out Requested Packets, BytesPackets and bytes requested to be forwarded out an IP interface
- Out Total Dropped Packets, BytesTotal number of packets and bytes that were discarded on the egress interface; sum of all the drop reasons indented below this field
- Out Scheduler Drops Committed Packets, BytesPackets and bytes dropped by the scheduler even though they had a committed traffic contract
- Out Scheduler Drops Conformed Packets, BytesPackets and bytes dropped by the scheduler even though they conformed to the traffic contract
- Out Scheduler Drops Exceeded Packets, BytesPackets and bytes dropped by the scheduler because they exceeded the contract
- Out Policed PacketsPackets discarded on the egress interface due to rate limiting
- Out Discarded PacketsPackets discarded on the egress interface due to a configuration problem rather than a problem with the packet itself
- Out Fabric Dropped PacketsPackets dropped due to internal fabric congestion
host1#show ip interface detailfastEthernet 0/0fastEthernet0/0 is up, line protocol is upDescription: boston00 fast ethernet interfaceLink up/down trap is disabledInternet address is 1.1.1.2/255.255.255.0IP statistics:Rcvd: 0 local destination0 hdr errors, 0 addr errors0 unkn proto, 0 discardsFrags: 0 reasm ok, 0 reasm req, 0 reasm fails0 frag ok, 0 frag creates, 0 frag failsSent: 31656835 generated, 0 no routes, 0 discardsICMP statistics:Rcvd: 0 errors, 0 dst unreach, 0 time exceed0 param probs, 0 src quench, 0 redirect,0 echo req, 31656816 echo rpy0 timestmp req, 0 timestmp rpy0 addr mask req, 0 addr mask rpySent: 0 errors, 0 dst unreach, 0 time excd0 param probs, 0 src qnch, 0 redirect0 timestamp req, 0 timestamp rpy0 addr mask req, 0 addr mask rpyIn Received Packets 246220, Bytes 344624800Unicast Packets 246162, Bytes 344621410Multicast Packets 58, Bytes 3390In Forwarded Packets 245464, Bytes 343566400In Total Dropped Packets 756, Bytes 1058400In Policed Packets 756In Invalid Source Address Packets 0In Error Packets 0In Discarded Packets 0In Fabric Dropped Packets 0Out Forwarded Packets 117, Bytes 87297Unicast Packets 117, Bytes 87297Multicast Routed Packets 0, Bytes 0Out Requested Packets 117, Bytes 87297Out Total Dropped Packets 0, Bytes 0Out Scheduler Drops Committed Packets 0, Bytes 0Out Scheduler Drops Conformed Packets 0, Bytes 0Out Scheduler Drops Exceeded Packets 0, Bytes 0Out Policed Packets 0Out Discarded Packets 0Out Fabric Dropped Packets 0If you are losing packets because of fabric congestion, you can use the In Fabric Dropped Packets and Out Fabric Dropped Packets statistics to help determine the location of the bottleneck. Both statistics count the same thingthe same packets dropped because of fabric congestionbut in different directions.
At any given time, the total number of packets dropped in the fabric for all interfaces in the chassis is equal to the sum of all In Fabric Dropped Packets for all interfaces in the chassis, which equals the sum of all Out Fabric Dropped Packets for all interfaces in the chassis.
Packets not dropped for another listed reason are considered to have been dropped in the fabric. The router calculates In Fabric Dropped Packets by subtracting the total number of inbound packets dropped for all other reasons from the In Total Dropped Packets number. The router calculates Out Fabric Dropped Packets by subtracting the total number of outbound packets dropped for all other reasons from the Out Total Dropped Packets number.
The router calculates In Total Dropped Packets by subtracting In Forwarded Packets from In Received Packets. The router calculates Out Total Dropped Packets by subtracting Out Forwarded Packets from Out Received Packets. These statistics are reported while traffic is moving through the router. The router can get false statistics based on packets being forwarded or received after polling and based on which of the statistics is reported first. For example, In Forwarded Packets can be reported as greater than In Received Packets. Rather than displaying In Total Dropped Packets as a negative value, the command displays it as the sum of all drop reasons other than fabric drops; fabric drops are reported as 0, but might actually be nonzero. If you halt traffic, the In Total Dropped Packets and Out Total Dropped Packets values are always correct.
show ip interface shares
- Use to display information about shared IP interfaces.
- If you specify an IP interface specifier, the command displays information only for that interface and any shared IP interfaces associated with it.
- Field descriptions
- InterfaceInterface specifier or name of the interface
- IP-AddressIP address associated with the interface
- StatusOperational state of the interface
- ProtocolState of the protocol running on the interface
- Virtual RouterVirtual router in which the interface is configured
host1#show ip interface shares briefInterface IP-Address Status Protocol Virtual Routernull0 255.255.255.255/32 up upfastEthernet0/0 10.13.5.17/24 up uploopback100 202.1.1.1/24 up upatm4/0.1 10.1.1.1/24 up upip si0 Unnumbered up up vr-aip si1 Unnumbered up up vr-b:vrf-1Example 2 host1#show ip interface shares brief atm 4/0.1Interface IP-Address Status Protocol Virtual Routeratm4/0.1 10.1.1.1/24 up upip si0 Unnumbered up up vr-aip si1 Unnumbered up up vr-b:vrf-1Example 3For a description of the following fields, see the show ip address command host1#show ip interface shares atm 4/0.1atm4/0.1 is up, line protocol is upNetwork Protocols: IPUnnumbered Interface on loopback100( IP address 202.1.1.1 )Operational MTU = 1500 Administrative MTU = 0Operational speed = 155520000 Administrative speed = 0Discontinuity Time = 0Router advertisement = disabledAdministrative debounce-time = disabledOperational debounce-time = disabledAccess routing = disabledMultipath mode = hashedIn Received Packets 120, Bytes 12000Unicast Packets 60, Bytes 6000Multicast Packets 60, Bytes 6000In Policed Packets 0, Bytes 0In Error Packets 0In Invalid Source Address Packets 0Out Forwarded Packets 101, Bytes 5252Unicast Packets 101, Bytes 5252Multicast Routed Packets 0, Bytes 0Out Scheduler Drops Committed Packets 0, Bytes 0Out Scheduler Drops Conformed Packets 0, Bytes 0Out Scheduler Drops Exceeded Packets 0, Bytes 0Out Policed Packets 0, Bytes 0ip si0 is up, line protocol is upNetwork Protocols: IPVirtual Router vr-aLayer 2 interface atm4/0.1Unnumbered Interface on loopback100( IP address 202.1.1.1 )Operational MTU = 1500 Administrative MTU = 0Operational speed = 155520000 Administrative speed = 0Discontinuity Time = 0Router advertisement = disabledAdministrative debounce-time = disabledOperational debounce-time = disabledAccess routing = disabledMultipath mode = hashedIn Received Packets 0, Bytes 0Unicast Packets 0, Bytes 0Multicast Packets 0, Bytes 0In Policed Packets 0, Bytes 0In Error Packets 0In Invalid Source Address Packets 0Out Forwarded Packets 101, Bytes 5252Unicast Packets 101, Bytes 5252Multicast Routed Packets 0, Bytes 0Out Scheduler Drops Committed Packets 0, Bytes 0Out Scheduler Drops Conformed Packets 0, Bytes 0Out Scheduler Drops Exceeded Packets 0, Bytes 0Out Policed Packets 0, Bytes 0ip si1 is up, line protocol is upNetwork Protocols: IPVirtual Router vr-b:vrf-1Layer 2 interface atm4/0.1...Out Policed Packets 0, Bytes 0Example 4 host1#show ip interface shares ip si0ip0 is up, line protocol is upNetwork Protocols: IPLayer 2 interface atm4/0.1Unnumbered Interface on loopback100( IP address 202.1.1.1 )Operational MTU = 1500 Administrative MTU = 0Operational speed = 155520000 Administrative speed = 0Discontinuity Time = 0Router advertisement = disabledAdministrative debounce-time = disabledOperational debounce-time = disabledAccess routing = disabledMultipath mode = hashedIn Received Packets 0, Bytes 0Unicast Packets 0, Bytes 0Multicast Packets 0, Bytes 0In Policed Packets 0, Bytes 0In Error Packets 0In Invalid Source Address Packets 0Out Forwarded Packets 101, Bytes 5252Unicast Packets 101, Bytes 5252Multicast Routed Packets 0, Bytes 0Out Scheduler Drops Committed Packets 0, Bytes 0Out Scheduler Drops Conformed Packets 0, Bytes 0Out Scheduler Drops Exceeded Packets 0, Bytes 0Out Policed Packets 0, Bytes 0show ip profile
- IP profileProfile name
- IP addressIP address and subnet mask of the interface or none if the interface is unnumbered
- Unnumbered interfaceSpecifier for the unnumbered interface or none if the interface is numbered
- RouterRouter name
- Directed BroadcastEnabled or disabled
- ICMP RedirectsEnabled or disabled
- Access Route AdditionEnabled or disabled
- Network Address TranslationEnable or disable; domain location (inside or outside)
- Source-Address ValidationEnabled or disabled
- Ignore DF BitEnabled or disabled
- Administrative MTUMTU size
- Auto DetectRouter automatically detects packets that do not match any entries in the demultiplexer table; enabled or disabled
- Auto ConfigureDynamic creation of subscriber interfaces on a primary IP interface; enabled or disabled
- IP FlowStatsEnabled or disabled
host1#show ip profile fooIP profile : fooIP address : noneUnnumbered interface : noneRouter :Directed Broadcast : EnabledICMP Redirects : DisabledAccess Route Addition : EnabledNetwork Address Translation: Enabled, domain insideSource-Address Validation : EnabledIgnore DF Bit : DisabledAdministrative MTU : 0Auto Detect : DisabledAuto Configure : DisabledAuto Detect : DisabledIP FlowStats : Enabledshow ip protocols
- RedistributingProtocol to which BGP is redistributing routes
- Default local preferenceLocal preference value
- IGP synchronizationStatus of IGP synchronization: enabled, disabled
- Always compare MEDStatus of multiexit discrimination: enabled, disabled
- Router flap dampingStatus of route dampening: enabled, disabled
- Administrative DistanceExternal, internal, and local administrative distances
- Neighbor AddressIP address of the BGP neighbor
- Neighbor Incoming/Outgoing update distribute listNumber of the access list for outgoing routes
- Neighbor Incoming/Outgoing update prefix listNumber of the prefix list for incoming or outgoing routes
- Neighbor Incoming/Outgoing update prefix treeNumber of the prefix tree for incoming or outgoing routes
- Neighbor Incoming/Outgoing update filter listNumber of filter list for incoming routes
- Routing for NetworksNetwork for which BGP is currently injecting routes
- System Id6-byte value of the system
- IS-TypeRouting type of the router: Level 1, Level 2
- DistanceAdministrative distance for IS-IS learned routes
- Address SummarizationAggregate addresses defined in the routing table for multiple groups of addresses at a given level or routes learned from other routing protocols
- Routing for NetworksNetwork for which IS-IS is currently injecting routes
- Router IDOSPF process ID for the router
- DistanceAdministrative distance for OSPF learned routes
- RedistributingProtocol to which OSPF is redistributing routes
- Address SummarizationAggregate addresses defined in the routing table for multiple groups of addresses at a given level or routes learned from other routing protocols
- Routing for NetworksNetwork for which OSPF is currently injecting routes
- Router Administrative StateRIP protocol state. Enable means that the interface is allowed to send and receive updates. Disable means that the interface, if it is configured, is not enabled to run yet.
- System versionRIP versions allowed for sending and receiving RIP updates. The router version is currently set to RIP1, which sends RIP version 1 but will receive version 1 or 2. If the version is set to RIP2, the router will send and receive version 2 only. The default is configured for RIP1.
- Update intervalCurrent setting of the update timer (in seconds)
- Invalid afterCurrent setting of the invalid timer (in seconds)
- hold down timeCurrent setting of the hold down timer (in seconds)
- flushed intervalCurrent setting of the flush timer (in seconds)
- Filter applied to outgoing route updateAccess list applied to outgoing RIP route updates
- Filter applied to incoming route updateAccess list applied to incoming RIP route updates
- Global route mapRoute map that specifies all RIP interfaces on the router
- DistanceValue added to RIP routes added to the IP routing table; the default is 120.
- InterfaceInterface type on which RIP protocol is running
- RedistributingProtocol to which RIP is redistributing routes
- Routing for NetworksNetwork for which RIP is currently injecting routes
host1#show ip protocolsRouting Protocol is "bgp 100"Redistributing: ospfDefault local preference is 100IGP synchronization is enabledAlways compare MED is disabledRouter flap damping is disabledAdministrative Distance: external 20 internal 200 local 200Neighbor(s):Address 1.1.1.1Outgoing update distribute list is 2Outgoing update prefix list is efgIncoming update prefix tree is abcIncoming update filter list is 1Routing for Networks:192.168.1.0/24Routing Protocol is "isis isisOne"System Id: 0000.0000.0011.00 IS-Type: level-1-2Distance: 115Address Summarization:NoneRouting for Networks:fastEthernet0/0Routing Protocol is "ospf 1" with Router ID 192.168.1.151Distance is 110Redistributing: isisAddress Summarization:NoneRouting for Networks:192.168.1.0/255.255.255.0 area 0.0.0.0Routing Protocol is "rip"Router Administrative State: enableSystem version RIP1: send = 1, receive = 1 or 2Update interval: 30 secondsInvalid after: 180 secondshold down time: 120 secondsflushed interval: 300 secondsFilter applied to outgoing route update is not setFilter applied to incoming route update is not setNo global route mapDistance is 120Interface Tx Rx AuthfastEthernet0/0 1 1,2 noneRedistributing: ospfRouting for Networks:192.168.1.0/255.255.255.0show ip redistribute
- ToProtocol that routes are distributed into
- FromProtocol that routes are distributed from
- statusRedistribution status
- route map numberNumber of the route map
host1#show ip redistributeTo ospf, From static is enabled with route map 4To ospf, From connected is enabled with route map 3show ip route
- Use to display the current state of the routing table, including routes not used for forwarding.
- You can display all routes, a specific route, best route to a resolved domain name, all routes beginning with a specified address, routes for a particular protocol (BGP, IS-IS, OSPF, or RIP), locally connected routes, internal control routes, static routes, or summary counters for the routing table.
- Field descriptions
- Protocol/Route type codesProtocol and route type codes for the table that follows
- PrefixIP address prefix of network destination
- LengthNetwork mask length for prefix
- Next HopIP address of the next hop to the route, whether it is a local interface or another router
- DistAdministrative distance for the route; see Table 6
- MetNumber of hops
- IntfInterface type and interface specifier
host1#show ip routeProtocol/Route type codes:I1- ISIS level 1, I2- ISIS level2,I- route type intra, IA- route type inter, E- route type external,i- metric type internal, e- metric type external,O- OSPF, E1- external type 1, E2- external type2,N1- NSSA external type1, N2- NSSA external type2L- MPLS label, V- VR/VRF, *- indirect next-hopPrefix/Length Type Next Hop Dist/Met Intf------------- ---- -------- -------- ------172.16.2.0/24 Bgp 192.168.1.102 20/1 fastEthernet0/010.10.0.112/32 Static 192.168.1.1 1/1 fastEthernet0/010.1.1.0/24 Connect 10.1.1.1 0/1 atm3/0.100Example 2 host1#show ip route staticProtocol/Route type codes:I1- ISIS level 1, I2- ISIS level2,I- route type intra, IA- route type inter, E- route type external,i- metric type internal, e- metric type external,O- OSPF, E1- external type 1, E2- external type2,N1- NSSA external type1, N2- NSSA external type2L- MPLS label, V- VR/VRF, *- indirect next-hopPrefix/Length Type Next Hop Dist/Met Intf------------- ---- -------- -------- --------------10.10.0.112/32 Static 192.168.1.1 1/1 fastEthernet0/0Example 3 host1#show ip route summaryUnicast routes:8 total routes, 576 bytes in route entries0 isis routes0 rip routes3 static routes2 connected routes1 bgp routes0 ospf routes2 other internal routes0 access routes0 internally created access host routesLast route added/deleted: 2::4/128 by BGPAt MON FEB 04 2008 14:18:25 UTCUnicast routes used only for Multicast RPF check:0 total routes, 0 bytes in route entries0 isis routes0 rip routes0 static routes0 connected routes0 bgp routes0 ospf routes0 other internal routes0 access routes0 internally created access host routes0 mbgp routes0 dvmrp routesLast route added/deleted: null by InvalidAt MON FEB 04 2008 14:18:04 UTCMPLS tunnel routes (not used for forwarding):3 total routes, 216 bytes in route entries1 bgp tunnel routes1 ldp tunnel routes1 rsvp tunnel routesLast route added/deleted: 2::4/128 by BGP TunnelAt MON FEB 04 2008 14:18:26 UTCExample 4 host1#show ip route allProtocol/Route type codes:I1- ISIS level 1, I2- ISIS level2,I- route type intra, IA- route type inter, E- route type external,i- metric type internal, e- metric type external,O- OSPF, E1- external type 1, E2- external type2,N1- NSSA external type1, N2- NSSA external type2L- MPLS label, V- VR/VRF, *- indirect next-hopPrefix/Length Type Next Hop Dist/Met Intf------------- ---- -------- -------- ------0.0.0.0/0 Static 192.168.1.1 1/1 fastEthernet0/0 1.1.1.1/32 I2-E-i 192.168.1.105 115/10 fastEthernet0/0 6.6.6.0/24 Static 192.168.1.1 1/1 fastEthernet0/0 6.33.5.0/24 Static 0.0.0.0 1/1 loopback2 8.8.8.0/24 I2-E-i 192.168.1.105 115/10 fastEthernet0/0 9.9.9.9/32 I2-E-i 192.168.1.105 115/10 fastEthernet0/0 10.0.0.0/8 I2-E-i 192.168.1.105 115/10 fastEthernet0/0 10.10.0.156/32 Static 192.168.1.1 1/1 fastEthernet0/0 11.1.1.1/32 I2-E-i 192.168.1.105 115/10 fastEthernet0/0 11.11.11.12/32 I2-I-i 192.168.1.105 115/10 fastEthernet0/0 22.2.0.0/16 I2-I-i 92.168.1.105 115/10 fastEthernet0/0 34.0.0.0/8 I2-E-i 192.168.1.105 115/10 fastEthernet0/0 172.20.32.0/24 Static 192.168.1.1 1/1 fastEthernet0/0 174.20.32.0/24 I2-I-i 192.168.1.105 115/20 fastEthernet0/0 176.20.32.0/24 Connect 176.20.32.1 0/1 loopback1 192.168.1.0/24 Connect 192.168.1.214 0/1 fastEthernet0/0 201.1.1.0/24 I2-E-i 192.168.1.105 115/10 fastEthernet0/0 201.2.1.0/24 I2-E-i 192.168.1.105 115/10 fastEthernet0/0 201.3.1.0/24 I2-E-i 192.168.1.105 115/10 fastEthernet0/0 202.1.1.1/32 I2-E-i 192.168.1.105 115/10 fastEthernet0/0 207.1.1.0/24 I2-E-i 192.168.1.105 115/10 fastEthernet0/0Example 5Indirect Next Hop (* displayed) host1#show ip routeProtocol/Route type codes:I1- ISIS level 1, I2- ISIS level2,I- route type intra, IA- route type inter, E- route type external,i- metric type internal, e- metric type external,O- OSPF, E1- external type 1, E2- external type2,N1- NSSA external type1, N2- NSSA external type2L- MPLS label, V- VR/VRF, *- indirect next-hopPrefix/Length Type Next Hop Dst/Met Intf------------------ ------- --------------- ---------- ------------------------21.21.21.2/32 Static 0.0.0.0 1/0 loopback0[V:pe2]2.2.2.2/32 O-I 30.30.30.2 110/3 ATM2/0.3031.31.31.2 110/3 ATM2/0.3110.10.10.0/24 Connect 10.10.10.1 0/0 ATM2/0.1020.20.20.0/24 Connect 20.20.20.1 0/0 ATM2/0.214.4.4.4/32 Bgp 2.2.2.2* 200/23.3.3.3* 200/25.5.5.5/32 Bgp 4.4.4.4* 20/2host1#show ip route 4.4.4.4 detailProtocol/Route type codes:I1- ISIS level 1, I2- ISIS level2,I- route type intra, IA- route type inter, E- route type external,i- metric type internal, e- metric type external,O- OSPF, E1- external type 1, E2- external type2,N1- NSSA external type1, N2- NSSA external type2L- MPLS label, V- VRF4.4.4.4/32 Type: Bgp Distance: 200 Metric: 0 Tag: 0Indirect NHop: virtual-router: pe1Address 1.1.1.1 Type Bgp Index 1NHop: 10.10.10.2 IfIndx: 28 Intf: ATM2/0.10NHop: 20.20.20.2 IfIndx: 28 Intf: ATM2/0.20Indirect NHop: virtual-router: pe1Address 2.2.2.2 Type Bgp Index 2NHop: 10.10.10.2 IfIndx: 28 Intf: ATM2/0.10NHop: 20.20.20.2 IfIndx: 28 Intf: ATM2/0.20show ip route slot
- Use to display the interface and next hop for an IP address in the routing table of a line module.
- A next hop is displayed only for protocols where ARP is used to resolve the addresses, such as for fastEthernet, gigabitEthernet, bridged Ethernet over ATM, and so on.
- Field descriptions
- IP addressAddress reachable via the interface
- InterfaceInterface type and specifier associated with the IP address; displays "Local Interface" if a special interface index is present in the routing table for special IP addresses, such as broadcast addresses
- Next HopIP address of the next hop router to reach the IP address; displays "---" if no next hop is associated with the IP address; displays "Down" if the ECMP set for a specific route on a slot is down
host1#show ip route slot 6 10.10.0.231IP address Interface Next Hop------------ ---------------- ------------10.10.0.231 fastEthernet 6/0 10.10.0.231Example 2 host1#show ip route slot 9 90.248.1.2IP address Interface Next Hop------------ ---------------- ------------90.248.1.2 serial9/23:2 ---Example 3 host1#show ip route slot 9 90.249.255.255IP address Interface Next Hop------------ ---------------- ------------90.249.255.255 Local Interface ---show ip socket statistics
- Use to display basic information about BSD sockets that have been instantiated in the VR in whose context you issue the command. The information includes the connection information (source and destination IP address and port numbers), socket type, the options in effect on the socket, and the socket's state.
- Use the detailed keyword to display blocks of extensive information about every socket, such as how many times various APIs have been called and the socket event log. The detailed keyword displays information about only the sockets that are associated with the VR in whose context you issue the command or sockets that are not associated with any VR.
- Baselining is not supported for this command.
- Field descriptions
- socketNumber ipAddress:portNumber --> ipAddress:portNumberSocket and the IP address and port number for each end of the connection, with the E-series router shown on the left and the remote peer on the right
- typeType of connection: SOCK_STREAM (uses TCP) or DGRAM (datagram; uses UDP)
- optsOptions set on the individual sockets
- SO_DEBUGTurn on debugging; has no effect
- SO_ACCEPTCONNSocket can accept incoming connections
- SO_REUSEADDRAllow reuse of the local address
- SO_KEEPALIVEDo keepalives on the connection
- SO_DONTROUTEDo not route packets, use interface addresses
- SO_BROADCASTBroadcasts can be sent over the socket
- SO_USELOOPBACKBypass the hardware if/when possible
- SO_LINGERLinger on a close() if data is present
- SO_OOBINLINELeave received out-of-band data in-line
- SO_REUSEPORTAllow reuse of local port
- so_stateState of each socket; knowledge of BSD Sockets API is useful to understand this information
- SS_NOFDREFNo file table reference any more
- SS_ISCONNECTEDSocket is connected to a peer
- SS_ISCONNECTINGSocket is in process of connecting to peer
- SS_ISDISCONNECTINGSocket is in process of disconnecting
- SS_CANTSENDMORESocket cannot send more data to peer
- SS_CANTRCVMORESocket cannot receive more data from peer
- SS_RCVATMARKSocket at mark on input
- SS_PRIVSocket is privileged for broadcast, raw
- SS_NBIOSocket allows nonblocking operations
- SS_ASYNCSocket allows asynchronized I/O notifications
- SS_ISCONFIRMINGSocket is deciding to accept connection request
- pending xmit byte count = 0 recv countNumber of bytes that are pending to be sent (queued up) and received
- Keep alive idle timeNumber of seconds before TCP sends an initial keepalive probe to an idle remote node
- keep alive poll timeInterval in seconds at which TCP sends keepalive probes to idle remote nodes
- Additional state flagsState of the following flags in the socket_stats structure: ss_Bound, ss_BindError, ss_ListenOk, ss_ListenError, ss_AcceptOk, ss_AcceptError, ss_RsAcceptOk, ss_RsAcceptError, ss_ConnectOk, ss_ConnectErrors, ss_ConnectToOk, ss_ConnectToError, ss_CalledShutdown, and ss_CalledRsSocreate.
- Counters that show how often the indicated routine has been called: so_SendtoCalls, so_SendMsgCalls, so_SendCalls, so_SockWriteCalls, so_SendErrors, so_SentBytes, so_BsdCloseNotClosed, so_RecvBytes, so_RecvErrors, so_RecvFroms, so_Recvs, so_RecvMsgs, so_Reads
- Socket Event Log (most recent at bottom)Event log on this socket. Each one shows a call to a particular function within the socket library. Includes a repetition counter that displays only nonzero values.
- Call to sofree()Call included because in some circumstances an sofree() call does not result in the socket being destroyed (and memory being returned to the free pool)
- Call to rsSocket()Call to create the socket using rsSocket() as opposed to socket()
- Call to socket()8-bit value indicating how the call went
- Call to connect()8-bit value indicating how the call went
- Call to listen()8-bit value indicating how the call went
- Call to accept()8-bit value indicating how the call went
- Call to bind()8-bit value indicating how the call went
- Call to connectto()8-bit value indicating how the call went
- Call to rsAccept()8-bit value indicating how the call went
- Call to sobind()8-bit value indicating how the call went
- Call to solisten()8-bit value indicating how the call went
- Call to soclose()8-bit value indicating how the call went
- Call to soabort()8-bit value indicating how the call went
- Call to soaccept()8-bit value indicating how the call went
- Call to soconnect()8-bit value indicating how the call went
- Call to soconnect2()8-bit value indicating how the call went
- Call to sodisconnect()8-bit value indicating how the call went
- Call to soshutdown()8-bit value indicating how the call went
- Call to sowakeup()8-bit value indicating what kind of wakeup it is. 1 (SELREAD) indicates that data is available on the socket for the application. 2 (SELWRITE) means that more buffer space is available and the application can queue up more data to be transmitted.
- Call to soclose()8-bit value indicating how the call went
- Call to sendto()16-bit value indicating the return status
- Call to write()16-bit value indicating the return status
- Call to sendmsg()16-bit value indicating the return status
- Call to send()16-bit value indicating the return status
- Call to recvfrom()16-bit value indicating the return status
- Call to recv()16-bit value indicating the return status
- Call to recvmsg()16-bit value indicating the return status
- Call to read()16-bit value indicating the return status
host1#show ip socket statistics5 10.13.5.70:23 --> 10.10.132.71:2000type: 1 (SOCK_STREAM)opts = 13 SO_DEBUG SO_REUSEADDR SO_KEEPALIVEso_state = 177 SS_NOFDREF SS_CANTSENDMORE SS_CANTRCVMORE SS_PRIV18 0.0.0.0:23 --> 0.0.0.0:0type: 1 (SOCK_STREAM)opts = 7 SO_DEBUG SO_ACCEPTCONN SO_REUSEADDRso_state = 128 SS_PRIVExample 2Additional fields displayed by detailed keyword host1#show ip socket statistics detailed18 0.0.0.0:23 --> 0.0.0.0:0type: 1 (SOCK_STREAM)opts = 7 SO_DEBUG SO_ACCEPTCONN SO_REUSEADDRso_state = 128 SS_PRIVpending xmit byte count = 0 recv count 0Keep alive idle time = 14400 keep alive poll time = 150Additional state flags:so_Boundso_ListenOkss_CalledRsSocreateso_SendtoCalls = 0so_SendMsgCalls = 0so_SendCalls = 0so_SockWriteCalls = 0so_SendErrors = 0so_SentBytes = 0so_BsdCloseNotClosed = 0so_RecvBytes = 0so_RecvErrors = 0so_RecvFroms = 0so_Recvs = 0so_RecvMsgs = 0so_Reads = 0Socket Event Log (most recent at bottom)rssocketsobind - 0bind - 0solisten - 0listen - 0show ip static
- Use to display the status of static routes in the routing table.
- You can specify an IP mask that filters specific routes.
- Field descriptions
- PrefixIP address prefix
- LengthPrefix length
- Next HopIP address of the next hop
- MetNumber of hops
- DistAdministrative distance of the route; see Table 6
- TagTag value of the route
- IntfInterface type and interface specifier
- VerifyStatus of the RTR or BFD operation associated with the specified static route; this field is blank if the verify (BFD) or verify rtr (RTR) keywords were not specified as part of the ip route command. The display can include the following:
- BFD up/downCurrent status of the associated BFD operation
- operation numberNumber of the associated RTR operation
- up/downCurrent status of the associated RTR operation
- (lr)Indicates that although the associated RTR operation is currently down, the router will install this route in the routing table, provided that no other static route to the same network prefix is available; this field appears for an RTR operation that is down when the last-resort keyword is specified as part of the ip route verify rtr command
host1#show ip staticPrefix/Length Next Hop Met Dist Tag Intf Verify1.1.1.2/32 1.1.1.2 0 1 0 FastEthernet4/0 2 up1.1.1.2/32 1.1.1.2 0 1 0 FastEthernet4/110.10.133.17/32 10.6.128.1 1 1 0 unresolved 1 down11.11.11.11/32 3.3.3.3 0 1 0 unresolved 1 down(lr)show tcp ack-rst-and-syn
host1#show tcp ack-rst-and-synTCP Ack Rst and Syn Protection is ENABLEDshow tcp resequence-buffers
- Use to display the configuration, current per-VR, and per-router state of the TCP resequencing buffer management functions.
- Use the vrfName variable to specify a specific VRF for which you want to view information.
- Field descriptions
TCP Resequence Buffer Management Configuration
- Global MaximumNumber of buffers that can be on the reordering queues of all connections in all virtual routers
- Default Per-VR MaximumDefault maximum number of buffers for all connections in a single VR
- Default Connection MaximumDefault maximum number of buffers for each connection in each virtual router
- This VR MaximumMaximum number of outstanding resequencing buffers in the current VR
- This VR Connection MaximumMaximum number of outstanding resequencing buffers on any one connection in this VR
TCP Resequence Buffer Management State
- High WaterLargest number of outstanding resequencing buffers that the router has experienced since the last reset
- High WaterLargest number of outstanding resequencing buffers for the current virtual router since the last reset
- Buffers Discarded Because Global Limit ExceededNumber of resequencing buffers discarded because the global limit was reached
- Buffers Discarded Because VR Limit ExceededNumber of resequencing buffers that have been discarded in this virtual router because the virtual router buffer limit was reached
host1#show tcp resequence-buffersTCP Resequence Buffer Management ConfigurationGlobal Maximum: ###Default Per-VR Maximum: 250Default Connection Maximum: 15This VR Maximum: 300This VR Connection Maximum: 15TCP Resequence Buffer Management StateGlobal buffers in use: 5High Water: 15VR Buffers in use: 17High Water: 32Buffers Discarded Because Global Limit Exceeded: 25Buffers Discarded Because VR Limit Exceeded: 15show tcp path-mtu-discovery
- TCP PMTU DiscoveryState of the PMTUD functions (ENABLED or DISABLED)
- Administrative Minimum MTUAdministrative minimum PMTU that is supported or none if there is no minimum
- Administrative Maximum MTUAdministrative maximum PMTU that is supported or none if there is no maximum
- Timer 1Value of timer 1 in minutes
- Timer 2Value of timer 2 in minutes
- Black Hole Detect ThresholdNumber of retransmissions allowed before TCP/PMTUD assumes that there is a black hole and attempts to reduce impact in the MSS
- # ICMP TooBigsNumber of ICMP Too Big messages that have been received
- # ICMP TooBigs for unk. connectionsNumber of ICMP Too Big messages that have been received which were not for a valid connection
host1#show tcp path-mtu-discoveryTCP PMTU Discovery is ENABLEDAdministrative Minimum MTU: 512Administrative Maximum MTU: 65535Timer 1: 10 minutesTimer 2: 2 minutesBlack Hole Detect Threshold: 0 retransmissions# ICMP TooBigs: 0# ICMP TooBigs for unk. connections: 0show tcp paws
host1#show tcp pawsTCP PAWS is disabledshow tcp statistics
- Use to display all TCP statistics.
- Baselining is supported for this command.
- Use the ip keyword to display only IPv4 statistics.
- Use the ipv6 keyword to display only IPv6 statistics.
- Use the brief keyword to display summary information or the detailed keyword to display extensive information.
- Use the diagnostic keyword to display diagnostic information collected on the TCP statistics in addition to the detailed information. This command shows information only for the connections that are active within the context of the VR in which you issue the command.
- Field descriptions
- attemptedNumber of outgoing TCP connections attempted
- acceptedNumber of incoming TCP connections accepted
- establishedNumber of TCP connections established
- total pktsTotal number of packets received
- in-sequence pktsNumber of packets received in sequence
- bytesNumber of bytes received
- chksum err pktsNumber of checksum error packets received
- authentication err pktsNumber of authentication error packets received
- bad offset pktsNumber of bad offset packets received
- short pktsNumber of short packets received
- duplicate pktsNumber of duplicate packets received
- out of order pktsNumber of packets received out of order
- total pktsTotal number of packets sent
- data pktsNumber of data packets sent
- bytesNumber of bytes sent
- retransmitted pktsNumber of packets retransmitted
- retransmitted bytesNumber of bytes retransmitted
- Source address/port local portShows the 32 most recent TCP connection attempts that were rejected, including the remote node's IP address and port, the local port for the connection attempt, and the number of identical attempts that have been received on that port in a row. The reason for rejection is not given. This information may be useful in tracking down DoS attacks.
- # connection-reqs rejectedTotal number of connection attempts that have been rejected
- # connection-reqs pendingCurrent number of connection attempts that are pending, awaiting additional data from the peer
- # sonewconn calls that failNumber of calls to sonewconn that have failed. This statistic often indicates that either a socket connection limit has been reached or that there was no memory to hold the socket data structures.
- Local addrLocal address of the TCP connection
- Local portLocal port number of the TCP connection
- Remote addrRemote address of the TCP connection
- Remote portRemote port number of the TCP connection
- StateCurrent state of the TCP connection
- AuthenticationAuthentication status of the TCP connection
- total pktsTotal number of packets sent on the TCP connection
- data pktsNumber of data packets sent on the TCP connection
- bytesNumber of bytes sent on the TCP connection
- retransmitted pktsNumber of packets retransmitted on the TCP connection
- retransmitted bytesNumber of bytes retransmitted on the TCP connection
- total pktsTotal number of packets received on the TCP connection
- in-sequence pktsNumber of packets received in sequence on the TCP connection
- bytesNumber of bytes received on the TCP connection
- chksum err pktsNumber of checksum error packets received on the TCP connection
- bad offset pktsNumber of bad offset packets received on the TCP connection
- short pktsNumber of short packets received on the TCP connection
- duplicate pktsNumber of duplicate packets received on the TCP connection
- out of order pktsNumber of packets received out of order on the TCP connection
- Diagnostics: PRU_ Operations countersNumber of calls for each of the indicated PRU_operations within the TCP service API. These are per-connection statistics.
- Wildcard MatchesNumber of packets received that matched this TCP connection due to wildcard matching. Matching is expected for listening server connections, such as Telnet, but is not expected for established connections. This is a per-connection statistic.
- Rcv'd Packets after connection closedNumber of packets received on the connection after the connection has been closed (and before the data structure gets removed). This is a per-connection statistic.
- Connect request rejectedNumber of times an incoming connection request was not approved. This is a per-connection statistic.
- Connect request approval pendingNumber of times that an incoming connection request was held pending, waiting for a subsequent packet. This is a per-connection statistic.
- New soconnect failedNumber of times a SONEWCONN() was tried on a listening connection and failed. This is a per-connection statistic.
- # Write-WakeupsNumber of times a "write wakeup" occurred on the connection. This is a per-connection statistic.
- # Read wakeupsNumber of times a "read wakeup" occurred on the connection. This is a per-connection statistic.
- # receives after closeNumber of packets received with data after the connection entered the close-wait state. This is a per-connection statistic.
- Retransmit timerCurrent value of the retransmit timer
- Persistence timerCurrent value of the persistence timer
- Keepalive timerCurrent value of the keepalive timer
- 2MSL timerCurrent value of the 2MSL (max segment lifetime) timer
- tcpDisconnect()sNumber of times BsdTcp::tcpDisconnect() was called. This is a per-connection statistic.
- keep T/O pre-estabNumber of times the keepalive timer expired before the connection reached the established state. This is a per-connection statistic.
- tcpkeeptimeo_idleNumber of times the keepalive timer popped, but no keepalive was sent because of connection idle-time considerations. This is a per-connection statistic.
- TCP Connection Event Log (most recent at bottom)Event log for the TCP connection. It shows the last 32 events that occurred on the connection. The most recent event is at the bottom of the list. This is per-connection data.
The following events can be recorded:
The keepalive timer popped. An 8-bit argument that describes how the timer was handled:
- RSTs ackedNumber of RSTs received and then acknowledged by the TCP stack.
- Bogus RSTsNumber of RSTs that were judged to be invalid (that is, their timer expired) and therefore ignored
- SYNs ackedNumber of SYNs received and then acknowledged by the TCP stack.
- Bogus SYNsNumber of RSTs that were judged to be invalid (that is, their timer expired) and therefore ignored
- Data Insertions rejectedNumber of packets received and dropped because they are believed to have been inserted by an attacker
- PMTUDStatus of path MTU discovery on the virtual router: enabled or disabled
- Administrative Minimum MTUMinimum MTU that is enabled on any connection; a value of "none" indicates that the minimum is zero (0)
- Administrative Maximum MTUMaximum MTU that is enabled on any connection; a value of "none" indicates that the maximum is 65535
- Timer 1Amount of time the virtual router waits after receiving an ICMP Too Big message before attempting to increase the path MTU
- Timer 2Amount of time the virtual router waits after successfully increasing the MTU before attempting to increase it more
- # ICMP TooBigsNumber of ICMP Too Big messages that the router has received. When PMTU is disabled, this counter does not increase.
- # ICMP TooBigs for unk. connectionNumber of ICMP Too Big messages that the router has received for TCP connections that do not exist. When PMTU is disabled, this counter does not increase.
- PMTU Increase AttemptsNumber of attempts the router has made to increase the PMTU
- Black Hole Detect ThresholdNumber of successive transmissions that must occur on a connection before that connection treats retransmissions as indications that something is wrong
- Override MSSMSS that is advertised to peers, overriding the MSS that is derived from the interface MTU. This line does not appear in the output if you do not set the value.
- PMTUStatus of MTU/MSS on this virtual router: enabled or disabled
- MSS in effectMSS currently being used for transmission to the peer. This number changes while various network events occur to cause the router to increase or decrease its estimate of the MSS.
- Calculated MSS to peerMSS that path MTU discovery has calculated (if PMTUD is enabled) to the peer
- MSS received from peerMSS that the peer received in a TCP MSS option. If no option is received, the value is zero (0).
- Application set MSSMSS that an application might have set for the connection
- Xmit Interface MSSMSS for the interface used to transmit packets to the peer; calculated as the interface MTU minus the size of the TCP and IP headers.
- MSS Sent to PeerMSS that has been advertised to the peer
- "ICMP DestUn, Frag Req'd and DF Set" messagesNumber of ICMP "Destination Unreachable: Fragmentation Required and DF set" messages that the router has received
- Number of attempts to increase PMTUNumber of times the router has attempted to increase the PMTU by probing with a packet that is larger than the known MTU
- Time to next increase attemptAmount of time, in seconds, until the router retries to increase the MTU
- Black Hole Detection StateState of the black hole detection mechanism: none, detecting, probable, or unknown
- Buffers OutstandingNumber of buffers currently on the connection reordering queue
- High WaterMost buffers that have ever been on the connection reordering queue
- Buffers discardedNumber of buffers that were discarded because keeping them would have exceeded the connection maximum
- TCP PAWS is [enabled/disabled]Status of the TCP PAWS option; enabled indicates that PAWS is functioning normally (default mode) for TCP segments; disabled indicates that PAWS is disabled for TCP segments
host1#show ip tcp statisticsTCP Global Statistics:Connections: 7358 attempted, 4 accepted, 7362 established0 dropped, 14718 closedRcvd: 75923 total pkts, 53608 in-sequence pkts, 3120303 bytes0 chksum err pkts, 0 authentication err pkts, 0 bad offset pkts0 short pkts, 0 duplicate pkts, 0 out of order pktsSent: 82352 total pkts, 44404 data pkts, 657095 bytes34 retransmitted pkts, 487 retransmitted bytesTCP Session Statistics:Local addr: 0.0.0.0, Local port: 23Remote addr: 0.0.0.0, Remote port: 0State: LISTEN Authentication: NoneRcvd: 4 total pkts, 0 in-sequence pkts, 0 bytes0 chksum err pkts, 0 bad offset pkts, 0 short pkts0 duplicate pkts, 0 out of order pktsSent: 0 total pkts, 0 data pkts, 0 bytes0 retransmitted pkts, 0 retransmitted bytesLocal addr: 192.168.1.250, Local port: 23Remote addr: 10.10.0.77, Remote port: 2170State: ESTABLISHED Authentication: NoneRcvd: 61 total pkts, 34 in-sequence pkts, 41 bytes0 chksum err pkts, 0 bad offset pkts, 0 short pkts0 duplicate pkts, 0 out of order pktsSent: 64 total pkts, 45 dataLocal addr: 192.168.1.250, Local port: 23Remote addr: 10.10.0.77, Remote port: 2170State: ESTABLISHED Authentication: NoneRcvd: 61 total pkts, 34 in-sequence pkts, 41 bytes0 chksum err pkts, 0 bad offset pkts, 0 short pkts0 duplicate pkts, 0 out of order pktsSent: 64 total pkts, 45 data pkts, 2304 bytes0 retransmitted pkts, 0 retransmitted bytesLocal addr: 192.168.1.250, Local port: 23Remote addr: 192.168.1.139, Remote port: 1038State: ESTABLISHED Authentication: NoneRcvd: 295 total pkts, 159 in-sequence pkts, 299 bytes0 chksum err pkts, 0 bad offset pkts, 0 short pkts0 duplicate pkts, 0 out of order pktsSent: 281 total pkts, 210 data pkts, 3089 bytes0 retransmitted pkts, 0 retransmitted bytesExample 2Additional fields displayed by diagnostic keyword host1#show ip tcp statistics diagnostic...Global Diagnostic DataUnknown Connection logSource address/port -> local port128.127.126.125/124 -> 8080 count: 3111.111.111.111/222 -> 3333 count: 4# connection-reqs rejected: 0# connection-reqs pending: 0# sonewconn calls that fail: 0...Diagnostics:PRU_ Operations counters:PRU_ATTACH: 0PRU_DETACH: 0PRU_BIND: 1PRU_LISTEN: 1PRU_CONNECT: 0PRU_ACCEPT: 0PRU_DISCONNECT: 0PRU_SHUTDOWN: 0PRU_RCVD: 0PRU_SEND: 0PRU_ABORT: 0PRU_CONTROL: 0PRU_SENSE: 0PRU_RCVOOB: 0PRU_SENDOOB: 0PRU_SOCKADDR: 0PRU_PEERADDR: 0PRU_CONNECT2: 0PRU_FASTTIMO: 0PRU_SLOWTIMO: 0PRU_PROTORCV: 0PRU_PROTOSEND: 0Wildcard Matches: 2Rcv'd Packets after connection closed: 0Connect request rejected: 0Connect request approval pending 0New soconnect failed 0# Write-Wakeups: 0# Read wakeups 0# receives after close 0Retransmit timer: 0Persistance timer: 0Keepalive timer: 02MSL timer: 0tcpDisconnect()s: 0keep T/O pre-estab: 0tcpkeeptimeo_idle: 0...TCP Connection Event Log (most recent at bottom)TCPS_ELOG_PRU_ATTACHTCPS_ELOG_PRU_BINDExample 3Additional fields displayed by detailed keyword host1#show ip tcp statistics detailed...RST/SYN-Ack Protection is: ENABLEDRSTs acked: 0...Bogus RSTs: 0SYNs acked: 0...Bogus SYNs: 0Data Insertions rejected: 0PMTUD Information: PMTUD: ENABLEDAdministrative Minimum MTU: 512Administrative Maximum MTU: noneTimer 1: 10 minutesTimer 2: 2 minutes# ICMP TooBigs: 0# ICMP TooBigs for unk. connection: 0PMTU Increase Attempts: 17Black Hole Detect Threshold: 50 retransmissions...MTU/MSS InformationENABLED on this connectionMSS in effect: 536Calculated MSS to peer: 536MSS received from peer: 0Application set MSS: 0Xmit Interface MSS: 0MSS Sent to Peer: 0"ICMP DestUn, Frag Req'd and DF Set" messages: 0Number of attempts to increase PMTU: 0Time to next increase attempt: 0 secondsBlack Hole Detection State: none...Out-of-order Packet Queue InformationBuffers Outstanding: 25High Water: 28Buffers discarded: 15...TCP-Paws is disabledshow ip traffic
- Use to display statistics about IP traffic.
- You can use the ipTraffic log to show consumable IP traffic to the SRP module; the traffic is filterable per router and IP interface. You can show ICMP, TCP, and UDP traffic with the icmpTraffic, udpTraffic, and tcpTraffic logs.
- Field descriptions
- router IdRouter ID number
- totalNumber of frames received
- local destinationFrames with this router as their destination
- hdr errorsNumber of packets containing header errors
- addr errorsNumber of packets containing addressing errors
- unkn protoNumber of packets received containing unknown protocols
- discardsNumber of discarded packets
- reassembledNumber of reassembled packets
- reasm timed outNumber of reassembled packets that timed out
- reasm reqNumber of requests for reassembly
- reasm failsNumber of reassembly failures
- frag okNumber of fragmented packets reassembled successfully
- frag failNumber of fragmented packets reassembled unsuccessfully
- frag createsNumber of packets created by fragmentation
- forwardedNumber of packets forwarded
- generatedNumber of packets generated
- out discNumber of outbound packets discarded
- no routesNumber of packets that could not be routed
- routing discardsNumber of packets that could not be routed and were discarded
- totalTotal number of ICMP packets received
- errorsNumber of error packets received
- dst unreachNumber of packets received with destination unreachable
- time exceedNumber of packets received with time-to-live exceeded
- param probsNumber of packets received with parameter errors
- src quenchNumber of source quench packets received
- redirectsNumber of receive packet redirects
- echo reqNumber of echo request (ping) packets
- echo rpyNumber of echo replies received
- timestamp reqNumber of requests for a timestamp
- timestamp rpyNumber of replies to timestamp requests
- addr mask reqNumber of mask requests received
- addr mask rpyNumber of mask replies received
- totalTotal number of ICMP packets sent
- errorsNumber of error packets sent
- dest unreachNumber of packets sent with destination unreachable
- time excdNumber of packets sent with time-to-live exceeded
- param probNumber of packets sent with parameter errors
- src quenchNumber of source quench packets sent
- redirectsNumber of send packet redirects
- echo reqNumber of echo request (ping) packets
- echo rpyNumber of echo replies sent
- timestamp reqNumber of requests for a timestamp
- timestamp rpyNumber of replies to timestamp requests
- addr mask reqNumber of address mask requests sent
- addr mask rpyNumber of replies to address mask requests
- totalTotal number of UDP packets received
- checksumNumber of checksum error packets received
- no portNumber of packets received for which no E-series router application listener was listening on the destination port
- attemptedNumber of outgoing TCP connections attempted
- acceptedNumber of incoming TCP connections accepted
- establishedNumber of TCP connections established
- droppedNumber of TCP connections dropped
- closedNumber of TCP connections closed
- currently establishedNumber of TCP connections currently established
- total pktsTotal number of TCP packets received
- in-sequence pktsNumber of packets received in sequence
- bytesNumber of bytes received
- chksum err pktsNumber of checksum error packets received
- authentication err pktsNumber of authentication error packets received
- bad offset pktsNumber of packets received with bad offsets
- short pktsNumber of short packets received
- duplicate pktsNumber of duplicate packets received
- out of order pktsNumber of packets received out of order
- total pktsTotal number of TCP packets sent
- data pktsNumber of data packets sent
- bytesNumber of bytes sent
- retransmitted pktsNumber of packets retransmitted
- retransmitted bytesNumber of retransmitted bytes
- OSPF StatisticsProvides statistics on OSPF
- IGMP StatisticsProvides statistics about queries, reports sent or received
- ARP StatisticsNot supported for this version of the router
host1#show ip trafficIP statistics: Router Id: 172.31.192.217Rcvd: 97833 total, 171059 local destination0 hdr errors, 0 addr errors167 unkn proto, 0 discardsFrags: 4 reassembled, 30 reasm timed out, 8 reasm req0 reasm fails, 145 frag ok, 0 frag fail290 frag createsSent: 15 forwarded, 25144 generated, 0 out disc0 no routes,0 routing discardsRoute: 57680 routes in table0 timestamp req, 0 timestamp rpy0 addr mask req, 0 addr mask rpyICMP statistics:Rcvd: 561 total, 0 errors, 15 dst unreach0 time exceed, 0 param probs, 0 src quench0 redirects, 0 echo req, 0 echo rpy0 timestamp req, 0 timestamp rpy0 addr mask req, 0 addr mask rpySent: 463866 total, 0 errors, 163676 dest unreach0 time excd, 0 param prob, 0 src quench20 redirects, 463846 echo req, 0 echo rpy0 timestamp req, 0 timestamp rpy0 addr mask req, 0 addr mask rpyUDP Statistics:Rcvd: 93326 total, 0 checksum errors, 90610 no portSent: 0 total, 0 errorsTCP Global Statistics:Connections: 7358 attempted, 4 accepted, 7362 established0 dropped, 14718 closedRcvd: 75889 total pkts, 53591 in-sequence pkts, 3120283 bytes0 chksum err pkts, 0 authentication err pkts, 0 bad offset0 short pkts, 0 duplicate pkts, 0 out of order pktsSent: 82318 total pkts, 44381 data pkts, 656321 bytes34 retransmitted pkts, 487 retransmitted bytesOSPF Statistics:IGMP Statistics:ARP Statistics:show ip udp statistics
- totalTotal number of UDP packets received
- checksumNumber of checksum error packets received
- no portNumber of packets received for which no E-series router application listener was listening on the destination port
host1#show ip udp statisticsUDP Statistics:Rcvd: 39196 total, 0 checksum errors, 29996 no portSent: 210 total, 0 errorsshow profile brief
host1#show profile briefProfile :footrillprofile4show route-map
- Use to display the configured route maps.
- The displayed information includes the instances of each access list such as match and set commands.
- Example
host1(config)#route-map westford permit 10host1(config-route-map)#match community 44host1(config-route-map)#set local-pref 400host1(config-route-map)#exithost1(config)#exithost1#show route-map westfordroute-map 1, permit, sequence 10Match clauses:match community 44Set clauses:set local-pref 400