Scott Boysen
    [Subscriber Members]
    Hi all. I have an LSP site that is not saving trans (for months now!). We have a call server fail and got a replacement from our BP. The failed server was on CM5; LSP was also on CM5 and saving fine before the failure. The replacement server is 5.2. So due to the version mismatch, the LSP stopped syncing. We upgraded the LSP to 5.2 but it still will not save.

    Can I find out why it is not or see error logs? My BP has tried to help unsuccessfully so far. Even a save trans all or save trans lsp will not work. We have network connectivity and that is all fine. I am stumped (as is my BP) as to why this is not saving anymore.

    Any thoughts?
    AvayaTier3 bsh bshamilton
    [Subscriber Members]
    LSP's do not save translations. LSP servers receive translations, and filesync from the main server. There are several things to look at to determine why a filesync is failing. Do you see filesync FSY alarms in the main? Is the LSP registered to the Main? Is the LSP host media-gateway registered to the main or the LSP?
    Scott Boysen
    [Subscriber Members]
    I do not see any alarms for file sync. We have verified that the CM version is the same; have verified the time is the same on both servers (within a few seconds); we have updated the license file. What else can I check?
    MR X
    [Subscriber Members]
    Are u sure that LSP is registered successfully to the Main?
    Try to make reset system 4 for the LSP
    Ashish Mishra
    [Subscriber Members]
    Do a filesync -w -a lsp trans from Main server CLI and see what is the error message you receive.

    u could also go to /var/log/ecs and then do a grep "FILESYNC" 2012-03*.log|more to check the exact error message.

    Please post the output of these 2 commands.
    Scott Boysen
    [Subscriber Members]
    filesync -w -a lsp trans RESULT:
    -bash: 172.19.0.251: No such file or directory

    If I do the same command without the "" I get:
    Library Initialization failed: 111

    In trying to go to /var/logs/ecs I get:
    -bash: /var/logs/ecs: No such file or directory
    AvayaTier3 bsh bshamilton
    [Subscriber Members]
    filesync -w -a lsp trans RESULT:
    -bash: 172.19.0.251: No such file or directory

    If I do the same command without the "" I get:
    Library Initialization failed: 111

    In trying to go to /var/logs/ecs I get:
    -bash: /var/logs/ecs: No such file or directory

    These commands can be run from Main server linux bash prompt:

    /opt/ecs/sbin/filesync -w -a lsp 172.19.0.251 trans

    cd /var/log/ecs
    cd /var/log/ecs/filesync
    AvayaTier3 bsh bshamilton
    [Subscriber Members]
    LSP's do not save translations. LSP servers receive translations, and filesync from the main server. There are several things to look at to determine why a filesync is failing. Do you see filesync FSY alarms in the main? Is the LSP registered to the Main? Is the LSP host media-gateway registered to the main or the LSP?

    Can you answer these questions about registration of the media-gateway and LSP?
    Scott Boysen
    [Subscriber Members]
    /opt/ecs/sbin/filesync -w -a lsp 172.19.0.251 trans results in:
    Library Initialization failed: 111

    I don't know how to actually look at the logs in the /var/log/ecs directory (or any directory really). I tried the grep command earlier posted but it doesn't result in anything, just a new command line. I am not all that familiar with CLI or direct commands - was never taught any of that unfortunately.

    As far as I can tell the LSP is registered to the main. I can tell this by doing the "list surv" and I get the following:

    Name Type IP Address Reg Act Translations Net
    Updated Rgn

    Toronto_S8300 LSP 172.19.0.251 y n 22:00 8/18/2011 2

    How can I find this info? I am not familiar with how to check this...
    Is the LSP host media-gateway registered to the main or the LSP?

    I do not see any FSY alarms. I will look again but I have never seen one.
    AvayaTier3 bsh bshamilton
    [Subscriber Members]
    Do you have other LSP that have up to date translations when you do list survive?
    Scott Boysen
    [Subscriber Members]
    I do not. This is my only LSP site currently on this system. Again, it used to be fine before my main site's call server failure. Once we got the replacement server (and updated CM 5.2.x) the LSP stopped syncing (prob due to CM version mismatch).

    I listed my media gateways and I do see that the LSP gateway is registered.

    Should I attempt to remove and re-add it? Not sure of the implications to the site if I do so...not really well versed on this subject...
    AvayaTier3 bsh bshamilton
    [Subscriber Members]
    I do not. This is my only LSP site currently on this system. Again, it used to be fine before my main site's call server failure. Once we got the replacement server (and updated CM 5.2.x) the LSP stopped syncing (prob due to CM version mismatch).

    I listed my media gateways and I do see that the LSP gateway is registered.

    Should I attempt to remove and re-add it? Not sure of the implications to the site if I do so...not really well versed on this subject...

    Does the media-gateway for the LSP show not registered?

    If so, login to the lsp SAT and do reset system 4. This will force the media-gateway to register to the main and then you should be able to do Command: save translation all from the main and get translations to go to the LSP.
    Scott Boysen
    [Subscriber Members]
    Ok I did that and my SAT connection dropped. But is the system supposed to reboot? It did not...as far as I can tell.

    LSP Media Gateway is still not registered.
    AvayaTier3 bsh bshamilton
    [Subscriber Members]
    Ok I did that and my SAT connection dropped. But is the system supposed to reboot? It did not...as far as I can tell.

    LSP Media Gateway is still not registered.

    It sounds like you need some help. I sent you a Private message the other day and you did not respond. Call me if I can help.
    Scott Boysen
    [Subscriber Members]
    Thanks, bsh! I have to give my BP another shot at this - they are also unable to figure it out. If they can't do it then I will see if I can get approval for your assistance. What a pain in the ass this is...
    Paul Harris
    [Subscriber Members]
    Scottb did you ever resolve this issue i am having a similar issue, i think it may be down to the pathces on the lsp being different to the core (latest levels on lsp) or that the license is not enterprise at the core as yet so multinational locations is not switched on.

    Any help appreciated
    Scott Boysen
    [Subscriber Members]
    No resolution yet. My Avaya BP is still working on it and going to escalate to Avaya apparently. We tried backing up the main site and then restoring that backup to the LSP and that did get current translations saved onto the LSP. But it is still not syncing by itself nor with a save trans command.

    If I get any new info I will post it.
    Paul Harris
    [Subscriber Members]
    No resolution yet. My Avaya BP is still working on it and going to escalate to Avaya apparently. We tried backing up the main site and then restoring that backup to the LSP and that did get current translations saved onto the LSP. But it is still not syncing by itself nor with a save trans command.

    If I get any new info I will post it.

    Thanks i think ill at least try backing up and restoring the files. did you do a full backup by any chance then restore from that file?
    AvayaTier3 bsh bshamilton
    [Subscriber Members]
    You will turn your LSP into a brick if you restore the LSP os, security, from the main backup.

    The only thing you would want do a restore with would be the xln backup from the main to the LSP.
    Scott Boysen
    [Subscriber Members]
    I just backed up the ACP translations to restore to the LSP, not a full backup. I was really only interested in getting the updated trans into the LSP in case it went active. That is really the only issue I am having. It works flawlessly otherwise.
    Scott Boysen
    [Subscriber Members]
    Listen to bsh - the man knows what he is talking about. I should clarify, by BP actually did the backup/restore. It was the xln backup only. I am in no way suggesting this as a fix. Just letting you know what my BP is doing to try to fix.
    Paul Harris
    [Subscriber Members]
    Listen to bsh - the man knows what he is talking about. I should clarify, by BP actually did the backup/restore. It was the xln backup only. I am in no way suggesting this as a fix. Just letting you know what my BP is doing to try to fix.

    Thanks guys, translations only i understand
    Scott Boysen
    [Subscriber Members]
    RESOLUTION :: escalate to Avaya

    My BP was unable to resolve the issue. So they opened a ticket with Avaya and they were able to fix it. It took several hours of cleaning up old CM4 files that were apparently interfering.

    Noteworthy: this server was a replacement server for one that failed last year. It was our BP's test/spare server that they sold us since we needed something ASAP. I am thinking that since this was configured for them prior to being configured for me, that there were leftover files that needed to be cleaned. Avaya said it was a mess.

    All is well now though...even though I have to pay for the Avaya hours...ha
    Greg Millar
    [Subscriber Members]
    I have a main S8500 which failed and had to be rebuilt (unfortunately the backups had failed and were not valid). Now that the main is restored and we added back in the s8300 and g350, they are registered, but the LSP will not receive translations. The s8500 and s8300 have the same release.

    [login to unmask email]> /opt/ecs/sbin/filesync -w -a lsp 10.20.80.2 trans
    Return status: 11 (Error encountered)

    On CM it does not return an error it just says "success" for either "save trans all" or "save trans lsp"

    Does anyone have any ideas?
    Mike Burke
    [Subscriber Members]
    We had one LSP which was not updating on a newly installed CM6. A reboot that was initiated b/c the time was wrong by about 10 years and we started the NTP daemon. After the reboot which took a long time, the translations successfully updated.

    Things that we checked.
    Survivable-processor's were registered
    Media-Gateway's were registered.
    Times were sync'd

    Does anyone know what the accepted practice for the NTP Daemon on LSP's is? Ours all seem to be stopped, however this does not seem to affect translation updates.
    husasa husasa
    [Subscriber Members]
    Scottb did you ever resolve this issue i am having a similar issue, i think it may be down to the pathces on the lsp being different to the core (latest levels on lsp) or that the license is not enterprise at the core as yet so multinational locations is not switched on.

    ____________________________________
    Love life, stay healthy and enjoy every day
    http://www.mmolive.com/
    http://www.mmohome.com/

    All Times America/New_York


    Copyright © '.date("Y").'The International Avaya User Group. All Rights Reserved

    All material, files, logos and tradarks within this site are properties of their respective organizations.


    Terms of Service - Privacy Policy - Contact