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.
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.