TRANSLATIONS NOT UPDATING ON LSP'S

[manofdos]

I recently just swapped an ICC and an LSP. We now have 1 ICC and 3 LSP's.

The LSP's are registered and the media gateways are registered and the system works fine.

However, the translations aren't synching across the LSP's.

I have it enabled under system-parameters maintenance.

I've also tried filesync -e and filesync -a <IP add>

I receive an error

Library Initialization: 111

All systems are on CM 3.1.4.642.

Any Ideas?

Thanks,

Bill

 

[Darthion]

try running "save translations all" from the site administration screen or native configuration manager.

Never follow without confirmation of the leader's knowledge...

Never give away what you really want to retain...

 

[manofdos]

Yea I've done that. It doesn't error out or anything but when you do a list surviavable processor it doesn't show that the translations have been updated.

 

[macsnail]

Most common reasons LSP will not sync

1) Wrong software version (ie. main newer then LSP)
2) Wrong patches on the LSP they all need to match
3) Wrong size of memory selected for the LSP
4) Firewall blocking the translation ports
5) problem was with the lenght (size) of the MTU packets configured in the router
6) add the primary and back up 8710 IP address in the 8300 configure server tab

 

[Midstream]

Two more things to try would be to make sure the time of day is the same on all and not off by a couple of minutes. Also make sure the latest versions of SID/MID licenses are on each respective machine.

 

[manofdos]

Same exact software on all 4 systems is loaded.

Same exact patches are loaded

There isn't a firewall between locations

IP address is set on configure server page for all lsp's

Date/Time is correct on all systems

All Licenses are current

Macsnail: not sure what you mean by correct memory size. I can only enter and IP address and network region for lsp's

when I'm in a shell and I type filesync -e

Which is supposed to enable filesyncing from the processor I get

Library Initialization Failed: 111

I don't think it has anything to do with the LSP's at that point. It's supposed to come back and ask which LSP's to sync with.


Any Other Ideas????

I appreciate all the help.


Thanks,

Bill

 

[Midstream]

Is there anyone within your organization that knows how to use Wireshark? Maybe you want to turn on mirroring on the port that serves the LSP, monitor the traffic with Wireshark and see what happens when you do a "save trans lsp" from the main. Does the traffic hit the LSP? I know you said you didn't have a firewall between sites. Perhaps Wireshark will shed some light on what's holding this up. You sound like you're pretty savy with Linux.

 

[manofdos]

rockspop: Thanks for the reply. I did run wireshark and the traffic isn't even being sent to the lsp's. It seems like the database on the ICC is corrupt. The Save Trans comes back successful though.

This ICC used to be an LSP and it's the same error you get if you run the command on the LSP which shouldn't have a database to begin with.

When I goto run a file sync status in the maintenance web I get an error that the file doesn't exist.

It seems like an issue from the LSP to ICC conversion that never created the database. I don't know where to begin to create this database.

It feels almost as if I missed a crucial step in the conversion process.

I apprecaite everyone's input. Has anyone converted an LSP to an ICC?

Thanks,

Bill

 

[Midstream]

I did five LSP to ICC conversions last spring in 8 days. What a roadtrip that was!

What I did was just load each from scratch.

Did you do something like this?
site type then type now
1 ICC LSP
2 LSP ICC
3 LSP LSP
4 LSP LSP

You swapped an ICC with an LSP, all your LSP's are registering properly, but are not getting the save trans updates?

You obviously have the MGC list properly administered, but did you administer the file sync address change in each of the LSP's?

 

[Mitch672]

I would backup the XLN (Translations), and the CMM (Audix), make sure you have the license/password files, and know all of the IP information, also make sure you have all f the patches need (for CM and CMM/SES if you are using that)

I would then reload the Main S8300 from scratch, put in the CD, reload, repatch it, reload the license/password file, then load in the XLN & CMM files to the /var/homne/ftp/pub directory, and restore them. Then get into the CM, and issue a "reset system 4" to load the translations.

See if that works any better for you.

Mitch


Mitch

AVAYA Certified Expert