[Contents] [Prev] [Next] [Index] [Report an Error] [No Frames]


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:

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

baseline ip udp

baseline tcp

IP show Commands

You can monitor the following aspects of IP using show ip commands:


To Display
Command

Access lists

show access-list

show ip as-path-access-list

ARP

show arp

General IP information

show ip

IP addresses

show ip address

Community lists

show ip community-list

Routing table

show ip forwarding-table slot

show forwarding-table route-holddown

Interfaces

show ip interface

Shared IP interfaces

show ip interface shares

Protocols

show ip protocols

Redistribution policies

show ip redistribute

Routes

show ip route

Interfaces and next hops

show ip route slot

Socket statistics

show ip socket statistics

Static routes

show ip static

TCP ACK, RST, and SYN protection status

show tcp ack-rst-and-syn

Black hole threshold information

show tcp path-mtu-discovery

TCP statistics

show tcp statistics

Traffic

show ip traffic

UDP statistics

show ip udp statistics

Profiles

show ip profile

Route maps

show route-map

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

show arp

show forwarding-table route-holddown

show ip

show ip address

show ip as-path-access-list

show ip community-list

show ip forwarding-table slot

show ip interface

If 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 thing—the same packets dropped because of fabric congestion—but 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

show ip profile

show ip protocols

show ip redistribute

show ip route

host1#show ip route
Protocol/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 type2
  L- MPLS label, V- VR/VRF, *- indirect next-hop
 
  Prefix/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.30               
                           31.31.31.2      110/3      ATM2/0.31               
10.10.10.0/24      Connect 10.10.10.1      0/0        ATM2/0.10               
20.20.20.0/24      Connect 20.20.20.1      0/0        ATM2/0.21            
4.4.4.4/32         Bgp     2.2.2.2*        200/2      
                           3.3.3.3*        200/2      
5.5.5.5/32         Bgp     4.4.4.4*        20/2       

host1#show ip route 4.4.4.4 detail
Protocol/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 type2
  L- MPLS label, V- VRF

4.4.4.4/32   Type: Bgp   Distance: 200   Metric: 0   Tag: 0
   Indirect NHop: virtual-router: pe1 
   Address 1.1.1.1 Type Bgp Index 1
      NHop: 10.10.10.2 IfIndx: 28 Intf: ATM2/0.10 
      NHop: 20.20.20.2 IfIndx: 28 Intf: ATM2/0.20 
 
   Indirect NHop: virtual-router: pe1
   Address 2.2.2.2 Type Bgp Index 2
      NHop: 10.10.10.2 IfIndx: 28 Intf: ATM2/0.10 
      NHop: 20.20.20.2 IfIndx: 28 Intf: ATM2/0.20 

show ip route slot

show ip socket statistics

show ip static

host1#show ip static
Prefix/Length      Next Hop    Met   Dist   Tag    Intf                Verify
1.1.1.2/32         1.1.1.2        0     1        0 FastEthernet4/0     2 up
1.1.1.2/32         1.1.1.2        0     1        0 FastEthernet4/1
10.10.133.17/32    10.6.128.1     1     1        0 unresolved          1 down
11.11.11.11/32     3.3.3.3        0     1        0 unresolved          1 down(lr)

show tcp ack-rst-and-syn

show tcp resequence-buffers

TCP Resequence Buffer Management Configuration

TCP Resequence Buffer Management State

show tcp path-mtu-discovery

show tcp paws

show tcp statistics

        The following events can be recorded:


Fast Timeout

Did a PRU_CONNECT

2MSL Timeout

Did a PRU_CONNECT2

Retransmit Timeout

Did a PRU_DISCONNECT

Persist Timeout

Did a PRU_ACCEPT

Received FIN packet

Did a PRU_SHUTDOWN

Received SYN packet

Did a PRU_RCVD

Received Retransmission

Did a PRU_SEND

Transmit a FIN packet

Did a PRU_ABORT

Transmit a SYN packet

Did a PRU_SENSE

Retransmit a packet

Did a PRU_RCVOOB

Did a PRU_ATTACH

Did a PRU_SENDOOB

Did a PRU_DETACH

Did a PRU_SOCKADDR

Did a PRU_BIND

Did a PRU_PEERADDR

Did a PRU_LISTEN

The keepalive timer popped. An 8-bit argument that describes how the timer was handled:

  • Ignored because the session was not established (that is, not in the OPEN state)
  • Ignored due to idle-timeout considerations
  • A packet was sent
  • Ignored because the connection did not have the keepalive option set OR the connection was in the process of closing

show ip traffic

show ip udp statistics

show profile brief

show route-map


[Contents] [Prev] [Next] [Index] [Report an Error] [No Frames]