Issues with 2 x HP GbE2c and integration into a Cisco 3750

[Selman Haxhijaha]

I have 2 blade-enclosures with two Gbe switches. But for now I'm trying to put in place only 1 blade-enclosure, like in the picture.
I already did before the steps mantionet from you:
- connect one blade-chassis SW_B to the second 3750 only=> whats behaviour?
- connect the same blade-chassis SW_B to the first 3750 only (where normally SW_A should be connected) => whats behaviour?
It still does not activate the port.
I also tried to reconfigure another port just to see if the porti is bad, but no changes.
Configs from two catalyst 3750 are same. I have no doubt on Catalyst 3750 configuration.

[Pieter 't Hart]

so from the combinations
SW_A -> 3750-1 == OK
SW_B -> 3750-2 == notOK
SW_B -> 3750-1 == notOK
SW_A -> 3750-2 == ?? (no info in your posts)

focus lies on SW_B

in risk of asking something obvious,
- after making changes on the second GbE2 did you "apply" the changes?
- you are sure you've disabled the interconnecting ports 17 en 18?
on both switches?

If you
- erase the config of SW_B
"/maint/debug -> clrcfg"
- load SW_A config in SW_B
- disconnect SW_A (you may go as far as to remove from chassis)
- connect SW_B in place of SW_A
if still no good SW_B maybe defekt (config error not likely)

[Pieter 't Hart]

one other think, do you count the ports correctly?
port-21 is for both switches top right, it's not a symetrical setup.
see attached.

As for my suggestion to swap the switches physically, you could also try to swap only the interconnect modules first.

[Selman Haxhijaha]

After many days spent on this issue, finally I found out something interesting. SirWin was right, firmware is old and may be a bug. When i go via CLI to enable the port, it will remain as disabled. I went thru Onboard Administrator and via BBI to enable the port, the changes took effect immediately. I did this several times and got same results.
Thanks everybody on a help provided.

[Selman Haxhijaha]

If the port does not turn on via CLI, use BBI to enable it, I gues it is a bug of firmware version 2.0.0.