Those are two devices at different locations. No stacks, just standalone switches. Simplest configs ever - just vlans and LACP LAGs, no L3 routing, just in-band management and snmp.
No changes recently were made. I think those issues are related to our telnet script grabbing signal levels from transceivers. But it is very strange anyhow.
Still passing traffic and graphing graphs by snmp but no management, e.g. no telnet, no ssh, no console.
pk2016
4 Posts
0
July 11th, 2018 12:00
Hello!
Those are two devices at different locations. No stacks, just standalone switches. Simplest configs ever - just vlans and LACP LAGs, no L3 routing, just in-band management and snmp.
No changes recently were made. I think those issues are related to our telnet script grabbing signal levels from transceivers. But it is very strange anyhow.
Still passing traffic and graphing graphs by snmp but no management, e.g. no telnet, no ssh, no console.
Still see some syslog messages on syslog server.
pk2016
4 Posts
0
July 12th, 2018 07:00
Hello! Reboot was performed, and switch is accessible now.
Buuut ..
Is it really enterprise or telecom firmware with those bugs?
pk2016
4 Posts
0
July 31st, 2018 03:00
I think so.
No, it is not the only bug, but it is most annoying