Cisco ping loopback4/30/2024 Success rate is 100 percent (5/5), round-trip min/avg/max = 20/22/24 ms Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms Received 448 broadcasts, 0 runts, 0 giants, 0 throttlesĠ input errors, 0 CRC, 0 frame, 0 overrun, 0 ignoredĠ input packets with dribble condition detectedģ173300 packets output, 605343966 bytes, 0 underrunsĠ output errors, 0 collisions, 0 interface resetsĠ lost carrier, 0 no carrier, 0 pause outputĠ output buffer failures, 0 output buffers swapped out Input queue: 1/75/0/0 (size/max/drops/flushes) Total output drops: 0ĥ minute input rate 257000 bits/sec, 165 packets/secĥ minute output rate 255000 bits/sec, 163 packets/secģ170656 packets input, 604643921 bytes, 0 no buffer Last clearing of "show interface" counters 04:53:18 Output flow-control is XON, input flow-control is XON Hardware is PQ3_TSEC, address is 982 (bia 982) GigabitEthernet0/2 is up, line protocol is up Loopback3 10.250.230.204 YES manual up upĭescription Router Integrity Enterprise Template rollout for BOA AUDIT Feb 2005 GigabitEthernet0/2 10.251.63.9 YES NVRAM up up GigabitEthernet0/0 unassigned YES NVRAM administratively down down Interface IP-Address OK? Method Status Protocol Interface loopback 6 port-name mangement soarwinds ip address 10.100.0.We have 2 3945/15.0(1)M7 connected via gig interface to upstream routers (4 routers running MPLS BGP in core, dedicated for IP SLA probes) and we can ping physical interface IP just fine no delay but when ping loopback interface ping response time latency varies any where from 1 ms to 22 ms and we are looking for ways to find out if something in control plane of 3900 is causing this delay, any help is much appreciated. I can ping 10.19.0.1/2 and it works puzzling. I created a new loopback addres 10.100.0.1/.2 and I was not able to ping from one another.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |