Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Update software for Nortel Baystack 450-24T 1

Status
Not open for further replies.

augustin

Programmer
Jun 18, 2003
26
RO
I have a stack with 8 units of BayStack 450-24T switches.
All units have:
HW:RevL FW:V1.48 SW:v4.2.0.16 ISVN:2

I want to update the agent with v4.2.0.022 for entire stack.
Can I do it for all units at one time? I mean, I connect with telnet through a port ( not a specific one ) of the stack and start the tftp process.
 
Yes, if you download b4504202.img to the Stack, all 8 switches are upgraded.

I tried to remain child-like, all I acheived was childish.
 
Thanks!
Where could I download the latest version of Nortel's Optivity Switch Manager?
 
Your Nortel sales rep should cheerfully sell you Optivity Switch Manager.

I tried to remain child-like, all I acheived was childish.
 
i'm also looking for latest OSM version for personal use.
it's very important for me to make some tests.
thank's for your help.
 
i'm also looking for latest OSM version for personal use.
it's very important for me to make some tests.
thank's for your help.
j2mm@ifrance.com
 

I'm interrested by using autoupdate script in win2000 with baystack450 devices.
i have installed ActivePerl and tftp server .I have changed all of the variables in the file autoupdate_conf
I have changed also the system_objectid with the value I founded by telneting a Baystack 450 switch and choosing "system Characteristique" in the main menu.
sysObjectID: 1.3.6.1.4.1.45.3.35.1
when i execute the autoupdate it show this error message in the log file :
Description: BayStack 450-24T HW:RevL FW:V1.48 SW:v4.2.0.22 ISVN:2
sysObjectID: .1.3.6.1.4.1.45.3.35.1
-> Error: expected sysObjectID 1.3.6.1.4.1.45.3.35.1 skipping device!
what that means?
 
It looks like the leading dot in your sysObjectID config file entry is missing. Technically full OIDs start with a dot, but I should fix the next version so leading dots can be omitted... thanks for the feedback.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top