- #ATT ROUTER CONFIG SAYS ETHERNET STATUS 1000MBPS HOW TO#
- #ATT ROUTER CONFIG SAYS ETHERNET STATUS 1000MBPS MANUAL#
#ATT ROUTER CONFIG SAYS ETHERNET STATUS 1000MBPS MANUAL#
GigabitEthernet0/0/1 192.168.0.1 YES manual down downĮnter configuration commands, one per line. Router# show ip interface brief | include GigabitEthernet0/0/1 Input queue: 0/375/0/0 (size/max/drops/flushes) Total output drops: 0ĥ minute input rate 0 bits/sec, 0 packets/secĥ minute output rate 0 bits/sec, 0 packets/secģ14 packets input, 24637 bytes, 0 no bufferĠ input errors, 0 CRC, 0 frame, 0 overrun, 0 ignoredĠ output errors, 0 collisions, 6 interface resetsĠ lost carrier, 0 no carrier, 0 pause outputĠ output buffer failures, 0 output buffers swapped out Configure the interface in local loopback. Last clearing of "show interface" counters never Output flow-control is off, input flow-control is off
Reliability 255/255, txload 1/255, rxload 1/255įull Duplex, 1000Mbps, link type is auto, media type is LX GigabitEthernet0/0/0 is up, line protocol is up Interface link parameters must match at both ends of the link. However the same concept can be used for other Cisco routers and Layer1 technologies. The examples are pulled for an ethernet link on ASR1000 router. Do the same tests at the remote device and then contact Cisco TAC to check for any compatibility issues between the two devices. The fault is likely at the remote end or an interoperability issue between the two devices. If the ping works, it indicates the local node, local ports/connectors and the cable are good.If the Ping fails, it points to a cable or SFP problem.Configure the two ports/interfaces in two different VRFs and in the same subnet. Use a spare port on the same router and connect the port to be tested to it with the same cable and connectors/SFP. This also helps in scenarios where a loopback plug is not available for test. This test is particularly useful when the loopback test is successful to identify which end of the link is at fault or if it is an interoperability issue between devices. If this is the case contact Cisco TAC to troubleshoot it further. Failure of the port to come up or ping itself with a local loop indicates a problem with the Cisco Router. This test excludes the SFP and the cables in the packet path. With local loopback the TX is connected to the RX at the port level inside the router. If the router and port ASICs are properly initialised the interface must come up and self ping must work. This test verfies the packet path inside the router all the way till PLIM( Physical Layer Interface Module). Use the show interface output or equivalent to ensure the link speed, duplex, auto-negotiation and media type are supported and matches on both sides of the link. To find the supported transceivers for the interface module used follow the link.Ĭisco Gigabit Ethernet Transceiver Modules Compatibility MatrixĬonfigure the interface in local loopback Interface link parameters must match at both ends of the link This section discusses an easier way to isolate the failure to either the Layer 1 or Layer 2 or which endpoint device. Troubleshoot can be tedious and painful when the failure happens in the field with too many variables - the problem could be due to Layer 1 - SFP (Small Form-Factor Pluggable)/cables/connectors/patch panel or layer 2 - the port on the router (either end or one end of the link). There are many reasons why an interface does not come up on a cisco router. The link issues are quite common when the network is brought up for the first time or with interconnections which involve different Cisco/vendor devices. Refer to Cisco Technical Tips Conventions for more information on document conventions. Prerequisites RequirementsĪ knowledge of Virtual Routing and Forwarding (VRF) is required for this article.
#ATT ROUTER CONFIG SAYS ETHERNET STATUS 1000MBPS HOW TO#
This document describes how to troubleshoot interfaces that are down on router ethernet links.
0 kommentar(er)
