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

Active cpu gone to standby mode and standby cpu gone to active mode.

Status
Not open for further replies.

R.b. Shrestha

Systems Engineer
Apr 25, 2018
15
NP
Hello everyone,
I got a problem that the active cpu gone to standby mode and standby cpu gone to active mode. Because of this I am not able to connect the system via the Hipath Expert Access. Please help me to make it as before.
 
Use the customer LAN IP Address not the Atlantic LAN (192.0.2.x) address
 
Thank you so much. Now I am able to connect the cpu. But how can I connect the cpu via previous IP ? I was connecting it via 192.168.74.10.
 
I do not know your setup there.
You will get the fixed 'Atlantic LAN' on both Processors
(192.0.2.x/24)
If the system is on your (Customer) LAN then you should have a listing of IP addresses that it is contactable on and use those.
 
Typically each processor has it's own IP address, then there's an address that's used for "whichever processor is active". You should use that address normally, because there's usually no reason to get into the standby processor. So to answer your question about "how can I connect to the CPU via previous IP"... you shouldn't need to. I'm thinking that maybe the processor lost the network connection with caused the system to swap. So you're likely not able to connect using the old IP address until you get that fixed.

LoPath
Maintain HiPath 4000 V5 & V6, OpenScape Xpert V4 & V6, OpenScape Xpressions V7, OpenScape Contact Center V8, OpenScape Voice V9
 
You don't mention your hardware or software levels, but I assume it's V6, V7 or V8, and you are DSCXLV2 or Ecoserver.

If the Active/Standby swapped over, the telephony made a restart, which doesn't mean the ADP/Assistant did, althought from your description, I suppose it probably did.

You should check "uptime" on each processor, to see if the old Active node made a full reboot, in which case, why did it crash? Check /var/log/messages for that time period.

If your admin node made a reboot and Assistant loaded on the other node, and now you can't access Assistant, it sounds like possibly your customer lan connection is missing from that node, or maybe it's connected but config is wrong on data switch side. You should check if you can ping the physical eth0 address for each processor.
 
DIS-SIGNL:SYSTEM;

and you will see the restart times of the processors.

If they switched then no telephone calls should have been affected, however the Administration and Data Server (ADS the dash dot) would have logged you off.

Do you have access to anyone locally with more knowledge on the system -
 
Signl:system and maybe sta-hista:Search for the time period of the switchover. You would only have been logged off from ADP if the ADP itself restarted.

It could be the two events are unrelated. You have assumed the switchover caused the problem but it may not be so. Is Assistant accessible OK? Maybe it just needs a Comwin connection first from Assistant, Expert Access. Have you changed the PC you are connecting from ?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top