• July 21, 2019, 08:24:04 PM
Welcome, Guest. Please login or register. Registration is free.
Did you miss your activation email?

Author Topic: Nortel 5510-48T  (Read 5263 times)

0 Members and 1 Guest are viewing this topic.

Offline ivow

  • Rookie
  • **
  • Posts: 3
Nortel 5510-48T
« on: October 25, 2013, 08:24:06 AM »
Hello All,

I'm having some issues with a 5510-48T and I'm trying to troubleshoot but I can't seem to find the traceroute command. Some forums say that the command is hidden but for me it's not working.

switch1#traceroute 8.8.8.8
                ^
% Invalid input detected at '^' marker.

switch1#exec traceroute 8.8.8.8
                 ^
% Invalid input detected at '^' marker.

does anyone know if it is even possible and what the command for a traceroute is on a Nortel 5510-48T

Thanks in advance


Offline Telair

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 965
Re: Nortel 5510-48T
« Reply #1 on: October 26, 2013, 05:59:10 PM »
What software are you running on your switch?  The switch I had to run it on was running software v6.0.3.009 ( it's old, I know ).  Traceroute certainly is a command that is available to use from the enabled prompt.

CONSOLESW1#traceroute 192.168.1.1

traceroute to 192.168.1.1, 10 hops max, 40 byte packets
 1  10.1.209.10       1.491 ms   1.397 ms   1.222 ms
 2  10.1.200.1        1.313 ms   1.671 ms   1.239 ms
 etc....

Offline Paul L

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 754
    • paulaleroux
    • Paul's Networking blog
Re: Nortel 5510-48T
« Reply #2 on: October 27, 2013, 05:31:48 PM »
Telair is spot on.  You are most likely running v4.0 (or earlier) code.

commands like. Show run, Copy run, Telnet, traceroute didn't come along till later versions of v4 or v5.

If you are actually running v3 or v4 here is the upgrade path

4.1 -> 5.0-> 6.0 -> 6.2.4 > 6.3.2 (current); you will also need to upgrade diag image to 6.0.0.6 before upgrading to 6.0.0.14.   diag 6.0.0.18 is the most current
ACSS- Avaya Enterprise Routing Switch  #8

Offline CptnBlues63

  • Sr. Member
  • ****
  • Posts: 100
Re: Nortel 5510-48T
« Reply #3 on: October 28, 2013, 04:28:14 PM »
Telair is spot on.  You are most likely running v4.0 (or earlier) code.

commands like. Show run, Copy run, Telnet, traceroute didn't come along till later versions of v4 or v5.

If you are actually running v3 or v4 here is the upgrade path

4.1 -> 5.0-> 6.0 -> 6.2.4 > 6.3.2 (current); you will also need to upgrade diag image to 6.0.0.6 before upgrading to 6.0.0.14.   diag 6.0.0.18 is the most current

Is v6.3.2 fixed?

There were certain things that were fixed in v6.2.7 that weren't in 6.3.1  (Like the shared ports losing their duplex setting after a reboot)  Have they crosspatched 6.3.2 with 6.2.7 to get all those lots fixes back?  If not, it may be better to stop at 6.2.7 and leave the 6.3 stream alone until all fixes are back in it. 

Offline Telair

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 965
Re: Nortel 5510-48T
« Reply #4 on: October 28, 2013, 06:46:17 PM »
No, v6.3.2 does not have the fixes from v6.2.7 integrated in to it yet.  I am hoping for a v6.3.3 soon that will have the fixes applied from v6.2.7 .

Offline CptnBlues63

  • Sr. Member
  • ****
  • Posts: 100
Re: Nortel 5510-48T
« Reply #5 on: October 30, 2013, 10:39:12 AM »
No, v6.3.2 does not have the fixes from v6.2.7 integrated in to it yet.  I am hoping for a v6.3.3 soon that will have the fixes applied from v6.2.7 .

Bummer! 

I saw 6.3.2 came out but didn't bother with deploying it after discovering they hadn't fixed the issues with 6.3.1.  I was hopeful 6.3.2 would address those issues.

The majority of my switches I have are now on 6.2.7 but I have some on 6.3.1 that I had upgraded before finding out the shared port duplex issue was back in that revision.  I downgraded the switches that suffered from that bug but left the ones where it wasn't an issue alone.

In case anybody is curious, that particular bug only seems to affect copper connections in the shared ports.  With the switches I have connected using fiber optic, the duplex doesn't change if the switch reboots.  But the ones where I have copper running to a media converter, those did change from Full to Half duplex when rebooted.

Offline telecom116

  • Sr. Member
  • ****
  • Posts: 217
Re: Nortel 5510-48T
« Reply #6 on: October 31, 2013, 10:26:08 AM »
Yes, I long-ago was burned by the shared-port duplex issue; my MetroE connections just happen to require 10 full duplex fixed - and happens to be on the last port at 9 sites (ouch).   I too am disappointed by the lack of code updates to fix outstanding issues in both the ERS5000 6.3 and the ERS4800 5.6 code (last updated in April).  On the latter I actually had an open issue ticket that was closed when it was supposed to be included in the next release - and that was some time ago.

Offline Imran ta

  • Rookie
  • **
  • Posts: 4
Re: Nortel 5510-48T
« Reply #7 on: November 03, 2013, 01:18:05 AM »
Hi,

One of the best code in the entire Avaya 5000 series is 6.2.6.
Code 6.3.2 is new but not diagnosed as like 6.2.6,,,,,

I believe and as i heard from avaya guys, it is the most stable version as of now.
 yes, issue like copper duplex is resolved in 6.2.6 but re occurred  in 6.3.1.

6.3.2 needs some time, to prove its robustness