cbennett912

Hi all, thanks in advance...

I Have two 8710s, 2 LSPs, and 1 ESS... Running CM 3.0.1 with the xxx.346 Pack and the 10994 update for the ESS.

Everytime I do a 'save trans ess' it fails, then gives a file/sync alarm followed by a platform alarm. No one has been able to resolve this, so I figured I'd give this a shot since there are very savy folks here. The unusual thing is that we had a controlled outage a few weeks back and as part of the process we saved the translations and it did go to the ESS. Since then, nothing.

The LSPs sync fine. I'm at a loss, any help would be great! Thanks...

stubborne

what does "status ess clusters" return?

__________________
Stu

PBXtech.info

 

cbennett912

As I mentioned, we only have one ESS. Cluster ID 3 (I'm pretty sure). 6-4 was the last it worked. I attached the info.

Thanks man!
-Charlie

Attached Files

S8710 GEDI Print Preview.pdf (7.2 KB, 17 views)

stubborne

Do you have any ESS errors or alarms (disp alarms, disp err)... also if you display events (denial), look for ESS in description. Mainly, troubleshooting is limited to IP connectivity issues which doesn't seem to be your problem since it's registered. Have you reset the ESS? That might be a good plan.. Also, do you have maintenance (disp sys maint) set up to update the ESS?

__________________
Stu

cbennett912

Yeah, the ESS is set to update daily.

Save Translation: daily
Update LSP and ESS Servers When Saving Translations: y

I've powered off the 8500 and rebooted it, same results. I also looked into any possible firewall in place that could be blocking it, and there is none.

I found no events that are related to the ESS either.

The other simple thing I noticed was if I change my ASA password, it doesn't update the ESS. I still need to login to the ESS and change it there as well. I guess I wasn't aware that security information was exchange in translations, but that would make sense I guess since the two LSPs have no issue like this.

The ESS does work as well. We forced and outage and everything failed-over to the ESS and worked fine. But recent updates weren't taking effect. Probably since the trans it has in it are old.

I've had this escalated at Avaya, but everyone seems stumped right now :) OH JOY!

Thanks for your help! If you can think of anything else to try let me know, either way I'll post the resolution once it happens.
-Charlie

stubborne

I believe as long as you can ping and telnet you should be ok. You could try from SAT interface or from linux command line...

Definately software corruption on either side if ip connectivity and translations are good.

__________________
Stu

PBXtech.info

 

cbennett912

Yes indeed. We can ping, and we can telnet. But we can not FTP. I was told the translations are passed to the ESS via FTP. That could be the issue. But I thought I had remembered that CM uses different port to save trans. And if I recall, it was different between version of CM as well. But that's not the latest info we have, so it appears that the FTP process is stuck or corrupted. Still no resolution yet, but (hopefully) further ahead. Thanks for your help!

oni_lucent

I had a similar problem and we discovered that the problem was with the lenght (size) of the MTU packets configured in the router.

I don´t know if it helps, but who knows?!

Cheers