nexus 1000v host isolation

[igor.deribas]

Hello,

Please advice what could be a cause of such errors:

2013 Jun 20 10:55:15 N1000v %STP-2-SET_PORT_STATE_FAIL: Port state change req to PIXM failed, status = 0x41e800b2 [transaction timed out] vdc 1, tree id 0, num ports 3, ports  state FWD, opcode MTS_OPC_PIXM_SET_MULT_CBL_VLAN_BM_FOR_MULT_PORTS, msg id (1972200216), rr_token 0x758D6318

2013 Jun 20 10:55:15 N1000v %ETHPORT-5-IF_DOWN_NONE: Interface port-channel3 is down (None)

2013 Jun 20 10:55:16 N1000v %ETH_PORT_CHANNEL-5-PORT_DOWN: port-channel3: Ethernet5/1 is down

2013 Jun 20 10:55:16 N1000v %ETH_PORT_CHANNEL-5-PORT_DOWN: port-channel3: Ethernet5/2 is down

2013 Jun 20 10:55:16 N1000v %ETH_PORT_CHANNEL-5-PORT_DOWN: port-channel3: port-channel3 is down

2013 Jun 20 10:55:16 N1000v %ETH_PORT_CHANNEL-5-FOP_CHANGED: port-channel3: first operational port changed from Ethernet5/1 to none

2013 Jun 20 10:55:17 N1000v %ETHPORT-2-IF_DOWN_ERROR_DISABLED: Interface port-channel3 is down (Error disabled. Reason:STP set port state failure)

2013 Jun 20 10:55:17 N1000v %ETHPORT-2-IF_DOWN_ERROR_DISABLED: Interface port-channel3 is down (Error disabled. Reason:STP set port state failure)

2013 Jun 20 10:55:17 N1000v %ETHPORT-5-IF_DOWN_CFG_CHANGE: Interface Ethernet5/1 is down(Config change)

2013 Jun 20 10:55:17 N1000v %ETHPORT-5-IF_DOWN_CFG_CHANGE: Interface Ethernet5/2 is down(Config change)

2013 Jun 20 10:55:20 N1000v %ETHPORT-3-IF_DOWN_CHANNEL_ERR_DISABLED: Interface Ethernet5/1 is down (Channel error disabled)

2013 Jun 20 10:55:20 N1000v %ETHPORT-3-IF_DOWN_CHANNEL_ERR_DISABLED: Interface Ethernet5/2 is down (Channel error disabled)

Switch version is 4.2(1)SV1(4), port is in vPC-HM.

Problem is appaered after adding few VLANs and port-profiles in configuration.

Thanks.

[sprasath · Accepted solution]

Hi Igor,

This happens due to some communication issue between the VSM and the VEM while the VSM is trying to program the new VLANs on these interfaces. It's difficult to figure out what went wrong in this.

CSCtw56567 documents this behavior. As stated in the workaround section of the defect, possible workarounds are:

- Shut/no shut of the affected ports

- Assign the interfaces to a different port-profile.

Thanks,

Shankar

[igor.deribas]

Thank you Shankar!

In the bug I see

1st Found-In

4.2(1)SV1(5)

So it could be corrected cause I have 4.2(1)SV1(4)

Regards,

Igor

[sprasath]

Sure. I guess it's common for all codes. I'll follow up on this to see if we can change it.

Thanks,

Shankar