Virtual Connect Uplink set shutdown on cisco due to BPDU

[Andrew_Read]

We have two pairs of VC Enet modules.
Modules 1,2,5 and 6

We are waiting on the 10G CX stacking links to arrive (seems a commonly missed config item). So we have temporarily used Cat6 crossovers to link the modules vertically. i.e. module 1 to 5 and module 2 to 6)

We have only one SUS defined on 1 VC module.

All was working well (a few days running sucesfully in this config) until tonight when the cisco 3750 that the blade uplinks to shutdwon both ports in the portchannel group. The cisco detected a spanning loop:

SPANTREE-2-BLOCK_BPDUGUARD: Received BPDU on port Port-channel10 with BPDU Guard enabled. Disabling port.

I'm not sure if it is a coincidence, but I upgraded the Onboadrd Admin to 2.25 (Rel 1 Aug 08) today.

(The blade unit is not in production yet, so please forgive the non-redundant SUS configuration)

I tried just bringing one port up at a time, and only having one member in the SUS. Neither fixed the problem.

I have (temporarily) fixed the issue by powering off the second set of VC Enet modules (5,6)

Can anyone help as to where I have gone wrong with the setup?

Regards,

Andrew

[Lmm_1]

VC behaves as an edge device on the network and since VC does not participate in the
spanning tree, it doesnâ t transmit BPDUs on VC uplinks. Anyways you can check the customer advisory below.

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c01277065〈=en&cc=us&taskId=101&prodSeriesId=3331044&prodTypeId=15351

rgds,

[Andrew_Read]

thanks,

The firmware is more recent than in the advisory. The nature of the spanning tree loop was more than transient.
Has anyone else come across this?