Ethernet Switching
Highlighted
Ethernet Switching

LINK

[ Edited ]
‎05-27-2020 01:31 AM

hi all,

How to list the interfaces that are 100% not being used anymore on the Ex9200 series?

Secondly, can "LINK" be indicated not being used? 

I tried the following one...But I am not sure there are more accurate ones?

 

>show interfaces extensive | match "^Phy.*Down|: LINK" | except control
Physical interface: xe-2/0/18, Enabled, Physical link is Down
  Active alarms  : LINK
  Active defects : LINK
Physical interface: ge-2/0/28, Enabled, Physical link is Down
  Active alarms  : LINK
  Active defects : LINK
Physical interface: xe-3/0/26, Enabled, Physical link is Down
  Active alarms  : LINK
  Active defects : LINK
Physical interface: xe-3/0/34, Enabled, Physical link is Down
  Active alarms  : LINK
  Active defects : LINK

 

4 REPLIES 4
Highlighted
Ethernet Switching

Re: LINK

‎05-27-2020 01:41 AM

Hi Arix,

 

The match condition you have specified looks good and  will list all the interfaces which are down. when you include "LINK" this will show if there are any alarms present on the interfaces. If you want to check briefly for alarms you can use "show interfaces diagnostics optics <interface-name>"

 

>show interfaces extensive | match "^Phy.*Down|" | except control

 

If this solves your problem, please mark this post as "Accepted Solution" so we can help others too

 

Kudos are appreciated too 

 

Regards,

Nadeem

 

Highlighted
Ethernet Switching

Re: LINK

‎05-27-2020 02:20 AM

Hello Arix,

 

Greetings,

 

You can use the command you mentioned to list all the interfaces which are Down.

Regarding the "LINK" indicated below :

Physical interface: xe-2/0/18, Enabled, Physical link is Down
  Active alarms  : LINK
  Active defects : LINK

These are the Link alarms on the local interfaces and mostly due to physical layer issue. 

 

The errors might be occurring and any counters that are incrementing. The only alarm associated with Fast Ethernet or Gigabit Ethernet interfaces is the LINK alarm. A LINK alarm indicates a physical problem. To isolate where the physical problem might be occurring, conduct loopback testing. See Checklist for Using Loopback Testing for Fast Ethernet and Gigabit Ethernet Interfaces for information on conducting a loopback test.

 

You can also see Remote on the Active Alarms which means the issue is with the peer end device.

Reference Links:

https://www.juniper.net/documentation/en_US/junos/topics/topic-map/ethernet-fast-and-gigabit-link-al...

https://www.juniper.net/documentation/en_US/junos/topics/example/security-interface-alarm-configurin...

 

I hope this helps. Please mark this post "Accept as solution" if this answers your query.

 

Kudos are always appreciated! Smiley Happy

 

Best Regards,

Lingabasappa H

 

Highlighted
Ethernet Switching

Re: LINK

‎05-27-2020 02:46 AM

Can I ask 

You mean xe interface is a Gigabit Ethernet interface? 

 

Physical interface: xe-2/0/18, Enabled, Physical link is Down
  Active alarms  : LINK
  Active defects : LINK

 

Highlighted
Ethernet Switching

Re: LINK

‎05-27-2020 02:58 AM

Hello Arix, 

 

If i am getting your question right, are you asking if XE is a Gigabit Ethernet interface?

 

Yes, Its a 10-gigabit ethernet (xeinterface.

 

Physical interface: xe-2/0/18, Enabled, Physical link is Down
  Active alarms  : LINK
  Active defects : LINK

 As you can see above there are Link errors, need to check the physical layer issue to solve the problem. Try changing the cables, and check. if the alarm exists, try using a different optics, and check.

 

Also, you can check if there are any issues with the peer end.

 

  • Remove the optics, clean it, and insert it back again.  
  • Perform a hard loop/soft loop and check the behavior of the optics.

https://www.juniper.net/documentation/en_US/junos/topics/topic-map/ethernet-fast-and-gigabit-loopbac...

  • Try using another known working optics[Transceiver]  for the same port.
  • Remove the optics present in the port xe-2/0/18 and insert it in a known working port which is physically UP and working fine.
  • Try to change the cables and also try doing the same troubleshooting on the peer device. 

I hope this helps. Please mark this post "Accept as solution" if this answers your query.

 

Kudos are always appreciated! Smiley Happy

 

Best Regards,

Lingabasappa H

Feedback