Changing settings on IPSI

[rjblanch]

Hello,

After installing the latest firmware for my IPSI's, some of them have set themselves to Autonegotiation Enable.

When I try and set them to disable, it comes up with an error of "Disable auto negotiation failed".

Can anyone give me a clue of how this can be changed to disabled?

Regards

 

[mikeydidit]

I spoke with a friend this morning with Avaya. Apparently their is an issue with FW36 that may cause the IPSI to go into an auto negotiate. I was told you need to open a ticket and have it directed to tier 3 for help with this one. At present they do not have a new load to replace /fix the bugs in FW36.
Also this is from the read me files on FW 36.


++++++++++++++++++++++++++++
5) Known Problems.
++++++++++++++++++++++++++++

FW36 contains a bug that causes firmware downloads to TN2312AP and TN2312BP
hardware vintage 3 through 15 boards equipped with FW36 to be very slow;
e.g. ~10 minutes vs. 1.5 minutes. This will be corrected in the next
firmware release.


With this being said, I would NOT recommend that anyone download/use this load. With the serious bugs in this load, it should not be long before another load or patch for this load will be available.

"You don't stop playing because you get old. You get old because you stopped playing."

For the best response to a question, read FAQ222-2244.

 

[letman]

to reset ipsi's to disable auto negotiate try doing it in this order. TELNET TO IPSI FROM GO SHELL
1. telnetenable^port^1^ipaddress(192.etc)
2. telnet^ipaddress(192.etc)
3. ipsilogin
4. login=craft
5. password=serv1ces (1 is number one)
6. show^port^1 (list speed, duplex, and negotiation)
7. set^port^speed^1^100mb
8. set^port^duplex^1^full
9. set^port^negotiation^1^disable

 

[phonegoober]

letman,

Thanks for the tips.
question on bullet 1...

i do a telnetenable, but do i specifiy my port network or what?? or do i just do a:
telnetenable port 1 ipaddress 192.xx.xx.xx?

thanks

 

[bronco9955]

We had to busy the IPSI before we did the changes for it to take.

 

[CrossTalkTek]

to letman,

I have been following this thread as well,

Please respond to phonegoober's question, as I am interested in telneting as well.

what is that command, if you could reply, I would also be gratefull!

Thanks,

 

[qz01gs]

depending on the version of CM you have the command is also:

ipsisession -p followed by ipsi card ip address

think if its 2.0 or below its telnetenable -p ip address return

then type ipsilogin

then log in.

Its quite simple once logged in.

 

[phonegoober]

Thanks all.

I do a go shell.

then type in ipsession and it does not work.
It is not an avaiable choice via helop once if have done a go shell..

thoughts? using CM 3.0.

 

[letman]

step 1 should have been
telnetenable -p ipaddress (198 etc)
sorry about that. I am using CM 2.1

 

[phonegoober]

thanks.. actually, our version does not take telnetenable,
it takes ipsisession, then it give me a SSH key.

what do i do after that??

thx

 

[qz01gs]

just do telnet ip address of ipsi card hit return

your then on the ipsi card

ipsilogin

enter login

enter password

 

[jimbojimbo]

The quick fix is to go back to V31. We ran into this and have had some issues afterwards and in some cases were not able to get the boards to correctly lock down. Wait until vintage 37 or higher.

James Middleton
ACSCI/ACSCD/MCSE
Xeta Technologies
jim.middleton@xeta.com

 

[84Mike]

I just loaded version 36 onto an IPSI, and it did not change any of the settings. I was leary to install, but this was new cabinet, so no phones terminated yet. Went from FW30 to FW36 with no issues what-so-ever. Guess I was lucky this time.

 

[phonegoober]

84Mike,

Were you having an problems with "Santity Checks" and thus your upgrade to Firmware 36??

 

[84Mike]

No problems. I have a tech from Avaya coming today to install an update on my switch, and they recommended I update the firmware as well.

 

[tbg247]

Another tip for the tech, if he can' hardcode the IPSI to 100MBPS/ full duplex he needs to first set the speed to 10MBPS, save it, go back and then change speed to 100MBPS. It's a bug. I reported this to TierIV and they are going to write an MR. Let me know if this helps. Thanks.