Hello, I am having problems on a system with a CS1000 PRI GW. The MSDL Errors keep showing up intermintently. We think the trouble could be the customer doing port scans but we can't confirm. We have swapped out the Dch DB once, then when the trouble returned we changed out the Chassis, PRI GW card, and MGC. Trouble has not been back since but it is intermintent. See below. It's always this same loop.
DCH: 1 DISABLED (MSDL 72 0 2 SYS DSBL)
DCH: 2 DISABLED (MSDL 72 0 2 SYS DSBL)
MSDL112 MSDL 72 0 2
MSDL300 72 0 2 FROM: ENBL TO: SYS DSBL - NOT RESPONDING
TIME: 11:33:09
MSDL300 72 0 2 FROM: SYS DSBL - NOT RESPONDING TO: SYS DSBL - SELF TESTING
TIME: 11:33:09
MSDL300 72 0 2 FROM: SYS DSBL - SELF TESTING TO: SYS DSBL - SELFTESTS PASSE
D
TIME: 11:34:13
MSDL300 72 0 2 FROM: SYS DSBL - SELFTESTS PASSED TO: ENBL
TIME: 11:34:13
DCH: 2 EST CONFIRM TIME: 11:34:45 30/11/2011
DCH: 1 EST CONFIRM TIME: 11:34:47 30/11/2011
I have the system cloned in our lab and the closest I can come to replicating the trouble is to induce port scanning, inserting a duplicate IP address into the network, or just plain pulling the ELAN connector on the MGC. The thing is is that those tests are accompanied by the ELAN link down messages appearing, this is not seen when the trouble happens on site. I have a case open with Avaya but even they are struggling finding a true root cause. There are other threads related to this type of event but none have a true conclusion. If anyone has a test you want me to try I have non production system that I can play with. Suggestions welcome. Also, if anyone else having this same issue up for a conference call let me know.
DCH: 1 DISABLED (MSDL 72 0 2 SYS DSBL)
DCH: 2 DISABLED (MSDL 72 0 2 SYS DSBL)
MSDL112 MSDL 72 0 2
MSDL300 72 0 2 FROM: ENBL TO: SYS DSBL - NOT RESPONDING
TIME: 11:33:09
MSDL300 72 0 2 FROM: SYS DSBL - NOT RESPONDING TO: SYS DSBL - SELF TESTING
TIME: 11:33:09
MSDL300 72 0 2 FROM: SYS DSBL - SELF TESTING TO: SYS DSBL - SELFTESTS PASSE
D
TIME: 11:34:13
MSDL300 72 0 2 FROM: SYS DSBL - SELFTESTS PASSED TO: ENBL
TIME: 11:34:13
DCH: 2 EST CONFIRM TIME: 11:34:45 30/11/2011
DCH: 1 EST CONFIRM TIME: 11:34:47 30/11/2011
I have the system cloned in our lab and the closest I can come to replicating the trouble is to induce port scanning, inserting a duplicate IP address into the network, or just plain pulling the ELAN connector on the MGC. The thing is is that those tests are accompanied by the ELAN link down messages appearing, this is not seen when the trouble happens on site. I have a case open with Avaya but even they are struggling finding a true root cause. There are other threads related to this type of event but none have a true conclusion. If anyone has a test you want me to try I have non production system that I can play with. Suggestions welcome. Also, if anyone else having this same issue up for a conference call let me know.