One-sided link down Cisco - HP GbE2 Switch

[Pieter 't Hart]

I've got a HP CLI reference from 2007 where example output allready shows "Software: Version 3.2.0".

so your "2.1.0" seems a little behind.

[Ivo_W]

it is, it is.

Prob. 2004.

I got a case running for this @ HP as well but haven't had any response yet.

[Ivo_W]

As I've got some servers semi-active on that blade chassis, I'm currently replacing my config to try the nonegotiate port-channel setting first.

If that doesn't succeed I'll look into an firmware update.
I've downloaded the latest now (3.2.12.0).

But as it's quite a big difference I'm a bit hessitative to upgrade now, and perhaps have a saved config which doesn't apply at several points anymore.

I'll post my findings here.

[Ivo_W]

the nonegotiate option doesn't seem to cut it.

see attached file for info

[Ivo_W]

For future reference by anyone reading this.

I have just upgraded firmware and boot image
old: boot 2.1.0
old: firm 2.1.0

actions:
firmware to 3.1.0
boot to 3.2.0
reset switch
firmware to 3.2.0
reset switch
firmware to 3.2.12
boot to 3.2.12
reset switch

old config is still working *pfew*

Next step: testing the new config.

[Pieter 't Hart]

did you test if the l2 submenu is present now?

[Ivo_W]

It is!

LOTS of new options...omg!

[Ivo_W]

It's working!

Although it probably had nothing to do with the firmwareversions.

It was (at least part) a Cisco side misconfig.

The port-channel had storm-control specifically configured @ 10%.

The physical port had not.
Unfortunatly that meant it was set to standard with is stormcontrol @100%.

So stormcontrol mismatch, oops!

I will post the config from both here lateron

[Ivo_W]

I promised to post the end config here for others to profit from.

Turns out it was a two-part problem (isn't it always?).

The link between the Cisco 6506 (in VSS mode) with port-channel enabled, wouldn't show as up or connected,
while the HP Blade Switch GbE2 would show as up.

Only when the HP Blade SWitch's firmware was up to date I had some results:
The portchannel's status changed into 'suspended' mode, indicating that ther was a link!

The suspended mode was due to a misconfig: stormcontrol on the interface was not set, and thus 100%.
Storm control on the portchannel was set to 10%, and hence a misconfig.

The log showing the misconfig:
#sh log
...
*Sep 30 11:12:29.587 GMT: %EC-SW1_SP-5-CANNOT_BUNDLE2: Gi1/2/10 is not compatible with Po31 and will be suspended (Bcast Supp. Level of Gi1/2/10 is 100.0%, Po31 is 10.0% )
...

Config of the portchannel:
interface Port-channel31
description HP Blade encl 3 SW A
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1,100,200
switchport mode trunk
switchport nonegotiate
flowcontrol receive desired
storm-control broadcast level 10.00
storm-control multicast level 10.00

Config of the interface(s):
interface GigabitEthernet1/2/10
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1,100,200
switchport mode trunk
switchport nonegotiate
storm-control broadcast level 10.00
storm-control multicast level 10.00
channel-group 31 mode on

#sh etherchannel 31 summary
Group Port-channel Protocol Ports
------+-------------+-----------+-----------------------------------------------
31 Po31(SU) - Gi1/2/10(P) Gi2/2/10(D)

(1 port down as it is not fysically connected yet)

Port 20 and 22 are the trunk ports on the Blade Switch side:
/c/port 20
tag ena
/c/port 20/gig
fctl both
speed 1000
mode full
auto off
/c/port 22
tag ena
/c/port 22/gig
fctl both
speed 1000
mode full
auto off

And VLAN spanning tree and trunk info:
/c/port 20
tag ena
/c/port 20/gig
fctl both
speed 1000
mode full
auto off
/c/port 22
tag ena
/c/port 22/gig
fctl both
speed 1000
mode full
auto off

Status info, showing the cross trunk up (Trunk 1) and the uplink trunk up (Trunk 2), 1 port fysically not connected yet:
>> Layer 2# trunk
Trunk group 1: Enabled
Protocol - Static
port state:
17: STG 1 forwarding
18: STG 1 forwarding

Trunk group 2: Enabled
Protocol - Static
port state:
20: STG 1 DOWN
22: STG 1 forwarding

I hope this is of use to anyone running into similar problems.
Thanks to Pieter for thinking with me on this problem!

[Pieter 't Hart]

thanks for reporting back Ivo,
regards,
Pieter