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 John Tel on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

S8700 Duplication Link Down.

Status
Not open for further replies.

Freedom12

IS-IT--Management
Jan 19, 2008
41
PH
Hi All,

I was wondering if someone could spare me a piece of advice in our system that is having a problem. We have an obselete S8700 Server with CM 2.2.2 software patch activated 02.2.122.0-12809. It is Multi Connect. The problem started when there was an outage in power both server restarted without performing proper shutdown. After the server has been restored the duplication manager was down. Please see screenshot below of the details of the problem.

dadmin@server1> statapp
Watchdog 19/19 UP
TraceLogger 4/4 UP
ENV 1/1 UP
LicenseServer 4/4 UP
INADSAlarmAgen 1/1 UP
G3ALarmAgent 1/1 UP
GMM 5/5 UP
SNMPManager 1/1 UP
arbiter 3/3 UP
filesysncd 9/9 UP
dupmgr 0/1 Down
MasterAgent 1/1 UP
MIB2Agent 1/1 UP
MVSubAgent 1/1 UP
SME 9/9 UP
MCD 1/1 UP
CommunicaMgr 90/90 UP

I have replaced one of the S8700 to check the DAL Card and replaced the fiber cable also, I have performed remaster on the standby server and upon doing no success was attained. I can't seem to find where the problem relise? I might have overlook something and It is highly appreciated if someone could show me the right path.

Thanks in advance and Have a great day ahead of you!

Regards,
Renz
 
check the "copper" duplication link cable/connecitons, not only does the fiber have to work, the copper ethernet crossover cable also has to work.



Mitch

AVAYA Certified Expert
 
from the bash prompt do a "pingall -a" and see what fails.

Do this from both servers.

If the dup link passes then the copper link is okay.

The active server may require a controlled reboot as the service may not have restarted correctly.
 
Hi Mitch672 / billybobdan,

Thank you to you both for the time you have spent in listening in my inquiry. I have performed a pingall -a on both servers and this is the result.

Hostname IP Address Status

server2-cnb 192.152.255.202 Fail
server2-cna 192.152.254.202 Fail
ipsi-A01b 198.152.255.1 Pass
ipsi-A01a 198.152.254.1 Pass
server2-dup 192.11.13.14 Fail
server2 10.7.2.126 Fail

As of now only one server is running. I have one spare server and what I will do right now is put the spare server and the standby server link together standalone while the working server is ok. I will checked if the standby shadowing is up and the duplication link is up and perform save translation also. Do you think that this action step is ok.

Thank you both for your time and I will update you of the progress of this issue.

Thanks,
Freedom12
 
Hi Mitch672 / billybobdan,

Thanks for the 2nd opinion, you guys gave me another path to resolve the problem. As of now both servers are working as it is but I have experience one scenario where in when we tried to perform server interchanged, all the call and phones get disconnected which should not happen. Conducting server interchanged is seamless and we should not encounter this scenario. I tried to check bot software load string and both are identical. Do you have any suggestion as to what causes this problem. We will be doing another scheduled interchanged on our leanest time of service.

Hope to hear from you soon!

Thanks and Best Regards,
Freedom12
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top