When you see that the physical link is down, there may be a When an internal loopback isĬonfigured, the physical loopback should come up without an alarm. The sample output shows that the link is up and there are noĪlarms in this loopback configuration. Link mode: Full-duplex, Flow control: Symmetric/Asymmetric, Remote fault: OKįlow control: Symmetric, Remote fault: Link OKĬoS transmit queue Bandwidth Buffer Priority Limitģ network-control 5 50000000 5 0 low none Queue counters: Queued packets Transmitted packets Dropped packetsĬAM destination filters: 0, CAM source filters: 0
元 incompletes: 0, L2 channel errors: 0, L2 mismatch timeouts: 0, FIFO errors: 0,Ĭarrier transitions: 1, Errors: 0, Drops: 0, Collisions: 0, Aged packets: 0,įIFO errors: 0, HS link CRC errors: 0, MTU errors: 0, Resource errors: 0 Last flapped : 23:40:04 PST (00:02:12 ago)ĭropped traffic statistics due to STP State:Įrrors: 0, Drops: 0, Framing errors: 0, Runts: 0, Policed discards: 0, Interface flags: SNMP-Traps Internal: 0x4000ĬoS queues : 8 supported, 4 maximum usable queuesĬurrent address: 00:1f:12:fe:c5:2e, Hardware address: 00:1f:12:fe:c5:2e MAC-REWRITE Error: None, Loopback: Enabled, Source filtering: Disabled,įlow control: Enabled, Auto-negotiation: Enabled, Remote fault: Onlineĭevice flags : Present Running Loop-Detected Link-level type: Ethernet, MTU: 1514, Speed: 1000mbps, BPDU Error: None, Sample Output show interfaces ge-4/0/6 extensive Physical interface: ge-4/0/6, Enabled, Physical link is Up Interface index: 144, SNMP ifIndex: 516, Generation: 147 Interface (CLI) operational mode command: show interfaces ( fe- fpc/ port | ge- fpc/ pic/ port) To verify that the status of the Fast Ethernet or GigabitĮthernet interface is up, use the following Junos OS command-line | gigether-options] hierarchy level, places the interface into Interfaces interface-name (fastether-options Simply including the loopback statement at the [edit There is no option to use a local or remote statement. On anĮthernet interface, you cannot create a remote loopback, therefore Of the PIC but does not test the transmit and receive ports. A local loopback tests the interconnection When you create a local loopback, you create an internal loop In configuration mode, go to the following hierarchy level: edit interfaces interface-name (fastether-options | gigether-options)Ĭonfigure the local loopback: [edit interfaces interface-name (fastether-options | set loopbackįor example: [edit interfaces fe-1/0/0 showįor example: [edit interfaces fe-1/0/0 commit The transmit port to the receive port, follow these steps:
To configure a local loopback without physically connecting Perform Steps 2 through 8 from Diagnose a Suspected Hardware Problem with a Fast Show interfaces (fe- fpc/pic/port | ge- fpc/pic/port ) extensive Interface (fe- fpc/pic/port | ge- fpc/pic/port count 100 rapidĬheck for Fast Ethernet or Gigabit Ethernet Interface Ping the Fast Ethernet or Gigabit Ethernet Interface Interface-name unit logical-unit-number family inet addressĬlear Fast Ethernet or Gigabit Ethernet InterfaceĬlear interfaces statistics fe- fpc/pic/port | ge- fpc/pic/port Show interfaces ge- fpc/pic/port [edit interfaces Show interfaces (fe- fpc/pic/port | ge- fpc/pic/port)Ĭonfigure a Static Address Resolution Protocol Table Verify That the Fast Ethernet or Gigabit Ethernet Interface-name (fastether-options | gigether-options)]
For Using Loopback Testing for Fast Ethernet and Gigabit Ethernetĭiagnose a Suspected Hardware Problem with a FastĬreate a Physical Loopback for a Fiber-Optic InterfaceĬonnect the transmit port to the receive port.Ĭreate a Loopback Plug for an RJ-45 Ethernet InterfaceĬross pin 1 (TX+) and pin 3 (RX+) together, and pin 2
0 kommentar(er)
