• September 18, 2020, 10:08:04 PM
Welcome, Guest. Please login or register. Registration is free.
Did you miss your activation email?

Author Topic: Telnet Access to the Avaya ERS 5520 Switches  (Read 5337 times)

0 Members and 1 Guest are viewing this topic.

Offline eosuorah

  • Jr. Member
  • **
  • Posts: 34
Telnet Access to the Avaya ERS 5520 Switches
« on: June 20, 2013, 10:18:21 AM »
Hello All,

Has anyone seen an issue where you cannot access the Avaya ERS 55XX Series via Telnet?

I am able to ping the VLAN IP Interfaces on these Switches. However, Telnet Access no longer works.

I'm sure that Telnet was not disabled at all. And I have not performed any upgrades on these Switches.

I can access the 45XX Series just fine but not the 5520 Switches.

I came across an article on the Internet about the same issue. See below:

http://www.mincey.org/cms/node/19

Any ideas?



Offline TankII

  • Hero Member
  • *****
  • Posts: 556
Re: Telnet Access to the Avaya ERS 5520 Switches
« Reply #1 on: June 20, 2013, 10:28:40 AM »
When running 6.1.X code, and polling Telnet via WhatsUP Gold, telnet will stop responding due to a session limit not clearing.  It's in the 6.2.1 release notes, I believe.
It *may* recover if you disable all other telnet-based polling, but most likely will require a reboot.

TankII

Offline eosuorah

  • Jr. Member
  • **
  • Posts: 34
Re: Telnet Access to the Avaya ERS 5520 Switches
« Reply #2 on: June 20, 2013, 11:15:45 AM »
Thanks Tankll.

Tried looking into the Release Note 6.2.1 but couldn't find anything related to this.

Could the COM Server also be responsible for this? I ask because I doubt that the Customer uses Whatsup Gold.

Offline TankII

  • Hero Member
  • *****
  • Posts: 556
Re: Telnet Access to the Avaya ERS 5520 Switches
« Reply #3 on: June 20, 2013, 12:45:16 PM »
I looked in the 6.2.2 RN, and it's not there.  I do know we encountered it in 6.1.1.1 and had to jump to 6.2.1 once the CR was processed by Nortel.
Do they have any other monitoring tool that might be scanning port 23 on a regular basis? 

TankII

Offline eosuorah

  • Jr. Member
  • **
  • Posts: 34
Re: Telnet Access to the Avaya ERS 5520 Switches
« Reply #4 on: June 20, 2013, 01:22:29 PM »
The only management platform that I know about is the COM Server.

Offline telecom116

  • Sr. Member
  • ****
  • Posts: 217
Re: Telnet Access to the Avaya ERS 5520 Switches
« Reply #5 on: June 20, 2013, 01:42:15 PM »
The fix is in the 6.2.4 release.
http://downloads.avaya.com/css/P8/documents/100154016

Telnet task no longer accepts connection when polling with WhatsUp Gold (wi00847828)

I'd at least upgrade to at least 6.2.5 or 6.2.6 (latest in the 6.2.x code train).  I seem to remember some significant issues were fixed in 6.2.5; 6.2.6 fixed a specific issue I experienced where port duplex settings on the shared copper/SFP ports did not survive a reboot; both are extremely stable releases.
« Last Edit: June 20, 2013, 01:45:52 PM by telecom116 »

Offline eosuorah

  • Jr. Member
  • **
  • Posts: 34
Re: Telnet Access to the Avaya ERS 5520 Switches
« Reply #6 on: June 20, 2013, 02:06:48 PM »
Thx telecom116. Highly appreciated.
Will advice the Customer to upgrade.

However, I doubt that they manage using WhatsUp Gold. I know they have the Avaya COM Server. Which I believe does polling to these Servers. Could this be responsible as well?

Offline telecom116

  • Sr. Member
  • ****
  • Posts: 217
Re: Telnet Access to the Avaya ERS 5520 Switches
« Reply #7 on: June 20, 2013, 05:19:51 PM »
I believe it probably can be any kind of access like this that uses telnet to gather running config information or to confirm that Port 23 access is still working.  I've had telnet access "die" on ES/ERS switches before; my assumption is some sort of memory leak.  We use HP Network Automation, formerly Opsware (also OEMd as a Cisco product) which accesses the switch CLI to gather configuration info every six hours.

Offline eosuorah

  • Jr. Member
  • **
  • Posts: 34
Re: Telnet Access to the Avaya ERS 5520 Switches
« Reply #8 on: June 27, 2013, 09:37:59 PM »
Finally upgraded to Release 6.3.

This resolved the Telnet access issue.