Hardware is TenGigE, address is 65 (bia 65) TenGigE0/0/1/1 is up, line protocol is up Success rate is 100 percent (10000/10000), round-trip min/avg/max = 1/1/5 msĬheck Interface Counters RP/0/RSP0/CPU0:ASR9001-F# show interfaces tenGigE 0/0/1/1 Pings with timeout=0 may result in system instability andĬontrol protocol flaps resulting in traffic impact.ĭO you really want to continue : y RP/0/RSP0/CPU0:ASR9001-F# clear counters tenGigE 0/0/1/1Ĭlear "show interface" counters on this interface This clears counters on both the interface and controller. RP/0/RSP0/CPU0:ASR9001-F(config-if)# end Clear Counters RP/0/RSP0/CPU0:ASR9001-F(config-if)# loopback internal This is traffic impacting RP/0/RSP0/CPU0:ASR9001-F# configure It can find problems with the CPU, fabric path, NP and transceiver, but it cannot find optical or transit problems. This is a basic test that can be performed without access to a remote site. The below examples use this interface: RP/0/RSP0/CPU0:ASR9001-F# show run int tenGigE 0/0/1/1 Internal loops can be done remotely, but don't provide as much information.Įxternal loops must be performed at the site, but give the greatest amount of information. There are two primary kinds of loopbacks: internal and external. When necessary, loopbacks can be used to find problems with line cards, fabric, Network Processors (NPs), transceivers, or optical transit paths. Using Loopbacks to Test Ethernet Interfaces
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |