Host xxxx currently has no management network redundancy - warning

[Bluemoon404]

I have a service console port which has two physical NICs attached. I have two ESX 4 servers which are clustered.

I have a yellow triangle over the cluster and a warning:

Host xxxx currently has no management network redundancy

[Bluemoon404]

OK I have just made a change.

I now have two service console ports each with a single physical NIC attatched configured the exact same on both ESX servers

Same error showing on the cluster host xxxx has no management network redundancy.

Confused.

[krowczynski]

You have to create a second service console port in you network config, because you are using HA I suppose!

MCP, VCP

[krowczynski]

You dont need two service consoles or two networks for your service console,

All you need is to add a standby NIC on vSwitch that has your service console on it,

MCP, VCP

[Bluemoon404]

My first config had one service console port and two nics but it was complaining of management network redundancy.

My second config had two service console ports each with a nic and again it complained of management network redundacy.

Has anyone ever managed to set this up on VC 4.0 with ESX 4.0 servers without it complaining of network redundancy?

[krowczynski]

>> Has anyone ever managed to set this up on an ESX 4.0 without it complaining of network redundancy?

Not recommendes and I would not do so!!

MCP, VCP

[Bluemoon404]

it turns out that it had nothing to do with the console port. I only had one nic on my vmotion switch.