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!

LSP Issue on CM 3.1.1

Status
Not open for further replies.

Arklite

Technical User
Dec 3, 2004
58
GB
I have 43 LSP's with a primary controller of S8710 pair. The CM on all Media servers is 3.1.1 load R013x.01.1.628.7 and this has the update 11640 applied.
My problem is that I had to temporarily remove one of the LSP's from the network.
Anyway this was fine until I come to reinstate it. Now although the G700 in registered to the Primary,can receive filesync's OK and drops back to LSP when required the LSP does not appear in the "list survivable-processor" screen on the CM, even though you can view it via "display Survivable xxxxx or change Survivable xxxx".?

I have tried removing the LSP and Gateway translations from CM and then rebooting the G700 but still the G700/LSP works fine but doesnt show up in the status screen.
In Linux I can see the LSP in the file "lspNodeList" contained in /etc/opt/defty folder. And when I remove the translations it is removed from this file so I know the correct files are being updated, but the CM will not now show the LSP.
So could there be a registry somewher which needs purging or could this be another CM bug?
Does anybody out there have any similar experiences or thoughts on the reuse of a node-name? Any comments would be greatly appreciated.
 
Try re-administering the LSP in the main system with a different name and in a different row of the LSP table...

Petran.
 
Petran
I have already tried re-administering but this had no effect.
Please note that this is CM 3.1
so there is no LSP Table. Its administered via add/change survivable-processor so you cant pick your position in the list.
 
Then it looks like a bug so contact Avaya or a Businesspartner..


Petran.
 
I am curious on an update as well sine I have CM3.1 going into a facility iwth LSP.

Thank You!
 
This solution is running a 24hour contact centre.
I have decided to try a reset sys 4 before esculating this to Avaya, as I know this is the first thing they will ask, So I am covering all the bases.
The reset has been scheduled for next Friday as we have a 7 day "change request" window so watch this space!
 
Arklite, what happened after the reboot?
Does it solve your problem. I am experience exactly same problem and I will appreciate if you ca share your experience. The G700 is registered, the disp lsp shows the s8300 in service/idle, but the translation field still empty and no translations on the s8300.
Quick answer will be appreciate, I am trying to get the system running for Monday morning.

Thanks in advance
 
Seems to me that this is a good situation to bring into the lab.
 
Yes I can confirm.
After the reset system 4 the LSP was again visible in the
survivable-Processor screen.
Avaya had no comment on this action, however the customer has
decided to upgrade to cm3.1.2 in the next two weeks, so I an going to try this test again by removing and adding a test LSP we now have in the LAB. I am interested to see if it been addressed if not acknowledeged.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top