nsu

[deanmulley]

after upgrading a 3300 lx controler to 5.2 latest version the nsu didnt fully update.
the nsu was running dpns and it flashed orange (marching) then when red and stayed red on links 1-0.
after consideration it was decided to re flash the nsu.
we down loaded the document from mitel online and this does not seem to work .we have tryed it via eathernet and by serial.

 

[paterson]

I had a similar problem recently. Did you upgrade the database in the NSU before upgrading the 3300? This step would have been in the FCI for the newest release.

The procedure for flashing the NSu can be very fussy. You need to do every step and configure the boot parameters extactly as is listed. Make sure that when you have stopped the Auto-Boot, that you enter the boot parameters as listed in Fiure 2 "Boot Parameters for Method A".

Boot Device : qu -this will set the nsu up for TCP/IP
Inet on ethernet -: this is where you statically assign an IP address for the NSU. Don't forget to enter in the subnet mask. ie. 192.168.1.5:ffffff00

The commands at the Vxworks prompt are case sensitive as well.

When I had the problem, I forgot to enter in the Boot Device "qu", so the NSU was not active for TCP/IP signals from my laptop.

Hope that helps.

 

[deanmulley]

i hadnt upgraded the datbase as it was dpnss and the tech hand book and foc say you only have to update if pri ect...

i had copied the comands correctly...(4 times)

it came back with an error cannot bind tcp or something like that.

also when it states to ftp to the nsu address it came back with error number.....?

also tryd to upgrade software agin to no avail.....:0(

 

[paterson]

After you have made the changes to the boot parameters on the NSU through Vxworks, typed R to format the NSU, rebooted the NSU, stopped the Auto-boot again, and typed Q, then you should get a message back that the TCP is attached and FTP Deamon has started. (not sure of the exact message). Typing "Q" at the prompt will instruct the NSU to listen for TCP/IP and FTP signals.

At that point, you should be able to open your DOS command prompt and "ping" the IP address of the NSU, assuming that you have connected with a X-over cable directly to the NSU and you assigned an IP address to the NSU (I would also statically assign an IP address to your PC nic port as well, making sure that both are different from each other and on the same subnet). Sorry, I don't mean to insinuate that you don't know, I just don't know what skill set you are at!

If you don't get a reply from the "ping" to the ip address of the NSU, then the NSU was not set up properly. You will need to go back to the start and begin again. If you do get a reply on the "ping", then continue on with the steps. Make sure that the NSU files from either the Software Cd or Download are available in a folder on your C drive.

Within the DOS command, change the directory to the folder containg the NSU files and follow the steps outlined. If you get to this point, then you should be fine.

When you do get the NSU up and running, you will need to reload a database into it. Hopefully, you took a backup of the NSU with IMAT or you will have to start from scratch.

 

[deanmulley]

good point......when we tryed to ping the nsu we had no reply even though we had addresses on the nsu and host pc in the same scope and the same sub net,one thing i noted was that when the nsu boot file was set to flash (top comand line)we had eathernet activity but as soon as we changed it to qu this stoped.does this mean binding of tcp is done at as certain point?
we also had copied the 4 files into the nsuflash directory on the c drive of the host pc.but as there was no eathernet activity this was never going to work.

so are you saying that you still need to back up the database with imat even if it is dpnss?

 

[paterson]

I actually have never set up a system with dpnss, so I would not know for sure. I usually practice backing up anything that I am upgrading, you know... Cover Your Butt!

If you had put "qu" in the device field, typed in an IP address for the NSU (such as 192.168.1.5:ffffff00), typed "R" at the prompt, rebooted the NSU, then after rebooting and after stopping the auto-boot again you typed "Q" AND then still had problems with the binding of tcp.... Well I am not sure where to go from here. I have never had a problem with this procedure. I have had problems with the E2T card on the 3300 with the Flags field. 0x0 tells the device to use the static settings and 0x40 tells the device to look for DHCP. Maybe something to look at.

Other than that, I would make sure that ALL the boot parameters look like Figure 2 Method A. If all is good then I would try Mitel Tech support if you have access.

Good Luck!

 

[deanmulley]

thanks for your input mitel guy...i have a new nsu turning up monday...after a lot of rangling with mitel tech....they say its just a one off that this nsu isnt responding....next time we will set it up slowly,slowly catchy monkey style