Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

CUPS version 7.0(3) netowrk failover

Hello I have presence installed on

HW Platform : 7835H2

Processors : 1

Type : Intel(R) Xeon(R) CPU 5140 @ 2.33GHz

CPU Speed : 2333

Memory : 2048 MBytes

Object ID : 1.3.6.1.4.1.9.1.584

OS Version : UCOS 4.0.0.0-9

However when I go to the cli and enter

set network failover enable, as soon as I connect the second NIC to the network I lose connectivity.

have you seen this? is network failover supported?

thanks

6 REPLIES

Re: CUPS version 7.0(3) netowrk failover

Right, you should lose connectivity briefly while it gets set. This is normal

New Member

Re: CUPS version 7.0(3) netowrk failover

I think I didn't explain properly.

Once I execute the command set network failover ena, i lost connectivity for 1 minute, then everything is normal. however when I connect the Second NIC to the Network, I lost the connectivity and it will never be restored. to fix it I have to pull out the patch cord on the Second NIC

New Member

Re: CUPS version 7.0(3) netowrk failover

please see

Pinging 10.11.1.17 with 32 bytes of data:

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Ping statistics for 10.11.1.17:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Documents and Settings\Cristobal>ping 10.11.1.17 -t

Pinging 10.11.1.17 with 32 bytes of data:

Reply from 10.11.1.17: bytes=32 time<1ms TTL=63

Reply from 10.11.1.17: bytes=32 time<1ms TTL=63

Reply from 10.11.1.17: bytes=32 time<1ms TTL=63

Reply from 10.11.1.17: bytes=32 time<1ms TTL=63

Reply from 10.11.1.17: bytes=32 time<1ms TTL=63

Reply from 10.11.1.17: bytes=32 time<1ms TTL=63

Reply from 10.11.1.17: bytes=32 time<1ms TTL=63

Reply from 10.11.1.17: bytes=32 time<1ms TTL=63

Reply from 10.11.1.17: bytes=32 time<1ms TTL=63

Reply from 10.11.1.17: bytes=32 time<1ms TTL=63

Reply from 10.11.1.17: bytes=32 time<1ms TTL=63

Reply from 10.11.1.17: bytes=32 time<1ms TTL=63

Reply from 10.11.1.17: bytes=32 time<1ms TTL=63

Reply from 10.11.1.17: bytes=32 time<1ms TTL=63

Reply from 10.11.1.17: bytes=32 time<1ms TTL=63

Reply from 10.11.1.17: bytes=32 time<1ms TTL=63

** Here is when I connect the 2nd NIC **

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

I never get the connectiviby bak

Re: CUPS version 7.0(3) netowrk failover

I think that is expected. Once it fails over to the second NIC, it will stay there until the server is rebooted or you pull the cable. I read somewhere this was expected behavior, but I could be wrong.

New Member

Re: CUPS version 7.0(3) netowrk failover

I rebooted the server and if both NICs are connected I don't have connectivity at all.

I need to pull the cable of the 2nd NIC to restore connectivity

Re: CUPS version 7.0(3) netowrk failover

ouch, that stinks. So i just remembered I was confused. On Gatekeepers when you failover to another clustered GK, it will stay on the secondary GK until it's rebooted or restarted. Confusing right?!.

Sounds like a bug to me. Sorry I couldnt help ya

159
Views
0
Helpful
6
Replies
CreatePlease to create content