I walked into 2 alarms where 2 remote LSP sites survivable processors were not registered; However, the MG was. There was an issue in the region with the WAN circuit going down. Looks like the MG recovered fine, but CM showed both of those 8300's as unregistered. I was able to log into both of them and SP.. no issues. I restarted 1 of the CM's from SP and that didn't fix it. I then restarted the MM from the actual MG and that didn't work either. I couldn't reset the entire chassis due to business hours, but I went back into the 8300 and in server role changed the IP from the PROCR to a CLAN. CM rebooted after the change and that fixed it. What would I start with to understand why that happened in 2 different sites? Would it be MG F/W related? Weird because they were actually up and wonder if the MG unregistered if phones would have been able to register to the 8300.
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 Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
LSP Not Re-Registering
- Thread starter trilogy8
- Start date
montyzummer
IS-IT--Management
Just a thought , have the LSP`s actually been taking translations recently? could be the config`s are out.
What does a list trace RAS tell you on the core if you change the server back to Procr and reset sys 4 on the lsp?
Really need to be checking the logs to try and identify the issue , you should now after a successful registration to the CLAN able to identify what the issue is.
ACSS (UC/SBCE/SM/SME)
Not that they mean a thing anymore , get a brain dump pass the test crash the system.
What does a list trace RAS tell you on the core if you change the server back to Procr and reset sys 4 on the lsp?
Really need to be checking the logs to try and identify the issue , you should now after a successful registration to the CLAN able to identify what the issue is.
ACSS (UC/SBCE/SM/SME)
Not that they mean a thing anymore , get a brain dump pass the test crash the system.
- Thread starter
- #3
Translations are all current and up to date. I changed the server role IP back to the PROCR, restarted CM and it registered fine. This situation seems to be the sites both went survivable fine and when the WAN link recovered the MG returned fine, but the 8300 didn't for whatever reason. Weird that a full module reset wouldn't have made it come back either.
Is your core CM duplex? Got G650s?
If so, just a guess, At least 1 IPSI must be used in server arbitration - to say that in a CM Duplex with G650, you must allow the duplex to interchange back and forth if a specific IPSI isn't online. It can be a reason for an interchange.
Even if Procr is right, you might have entered the A and B servers wrong in the LSP config page and maybe they failed to recover because the main duplex interchanged from A to B and those 2 LSPs had good config for server A but not B.
Just a shot in the dark
If so, just a guess, At least 1 IPSI must be used in server arbitration - to say that in a CM Duplex with G650, you must allow the duplex to interchange back and forth if a specific IPSI isn't online. It can be a reason for an interchange.
Even if Procr is right, you might have entered the A and B servers wrong in the LSP config page and maybe they failed to recover because the main duplex interchanged from A to B and those 2 LSPs had good config for server A but not B.
Just a shot in the dark
- Status
Similar threads
- Locked
- Question
