Question on ProcR with DL360G7 servers 1

[gsaucier]

When I run ifconfig on my active server, serverA I can see the virtual IP address of the procr as eth2:0 but when I run the same command on the standby, serverB i cannot see the eth2:0.

ServerB cannot take voicemails but serverA can. Both my MAS systems point to my procr address.

ServerB can ping the procr ip address.

My question is: If a server is on standby should I still be able to see the virtual ip address?

BTW: I am running CM 5.2.1

I appreciate the help.

 

[gsaucier]

Also, what's weird is that when I look at ServerA's /etc/sysconfig/network-script there is no script to eth2:0.

 

[frankbil]

Hi gsaucier,

We've run into the same issue. Our system interchanged a few times and we found we could no longer get into our MM voicemail. Our support vendor found the same issue you are seeing, no virtual IP on eth2:0.

We're running DL370 G7 (S8800) with CM 5.2.1 Patch 13.

Once we forced an interchange back to Server A, we were able to access VM just fine. As soon as I hear back from them as to what the issue was, I'll post here, unless someone else beats me to it. With today a holiday for us, our support team was supposed to work on the issue all day today.

Each time we install a new patch, we perform a full disaster scenario test (i.e. Loss of WAN, Failover to ESS and back again, Interchanges, etc.). We do so b/c our Avaya system is EXTREMELY sensitive to the slightest WAN blip - even a BGP failover between redundant WAN routers.

We've only begun noticing the issue since upgrading to Patch 13, from Patch 7.

Cheers,
Bill

 

[gsaucier]

Bill-

I have been doing some testing in my lab equipment and I found the following:

The ifconfig command will only show what the server currently has as addresses, which is why we are unable to see it when the command is running on the standby. Further more, on my lab equipment there was no script to tell the server about the virtual address, so, I had to go into the web interface of that specific sever and look at the configurations.

What I found was that my current active had the configurations set to the virtual IP address but my standby was not. I just put in the proper info into my standby and it worked perfectly.

What I am figuring is that when the servers are originally setup through the web interface it does not create a script in the network-script directory (the reason why we couldn't find it.) And the only time where it would be there is if you setup the servers from the CLI manually.

I hope that helps!