In Cisco switches, you can utilize terminal monitor to alert when a goes up or down. How can you enable this on Extreme switches?

[Timothy_Clifton]

Our organization has recently converted from Cisco to Extreme Networks Switches. In Cisco switches, you can utilize terminal monitor to view messages over telnet that alert when a link on a port goes up or down. How can you enable the same type of service on Extreme switches?

[Paul_Poyant]

GTAC Knowledge articles:
https://gtacknowledge.extremenetworks.com/articles/How_To/SecureStack-Message-Generation-when-the-Po...
https://gtacknowledge.extremenetworks.com/articles/How_To/Summit-Message-Generation-when-the-Port-Li...

[Paul_Poyant]

You are seeking to "view messages over telnet that alert when a link on a port goes up or down", on the B5-Series.

code:

set logging default severity 7

code:

set logging application System level 7

code:

set logging local console enable file enable

...should in the output of a '

code:

show logging buffer

' yield messaging like this, visible via a Serial, Telnet, or SSH management session:

<

code:

166

>

code:

Aug 22 05:24:00 10.1.1.1-1 TRAPMGR[145562672]: traputil.c(475) 527 % Link Up: Unit: 1 Slot: 0 Port: 1

<

code:

166

>

code:

Aug 22 05:24:04 10.1.1.1-1 TRAPMGR[145562672]: traputil.c(475) 528 % Link Down: Unit: 1 Slot: 0 Port: 1

This feature was broken for a time in the 6.61 firmware line, but fixed again with f/w 6.61.08.0013+:
"

code:

17479

code:

Resolved an issue with link up/down messages not displaying on the local console.

"

But I suspect that you are looking for something that dynamically pops any logged messages into the management session when they occur. That feature is not currently supported on the SecureStacks for Telnet or SSH sessions. On the S/N/K/7100 Series, the command to toggle this feature on or off is '

code:

set logging here enable

|

code:

disable

' (disabled by default).

It's also worth noting that bumping the logging severity up to debug=7 on a permanent basis on the SecureStacks is not recommended, because over time it can be destabilizing to the stack. So, use as needed and then revert back to default logging levels when done.

[Timothy_Clifton]

Yes, I was looking for logging that would report via SSH.

[BrandonC]

Hi Timothy,

These commands are both for EXOS. In EOS, I believe you can do this with the command:
set logging local console enableI believe this will only apply to the console port though, not the SSH session.

-Brandon