H3C - MSTP interoperability with PVST+

If you want PVST to interoperate with MSTP, you need to the Cisco to interoperate with an ieee 802.1 standard BPDU packet and not the proprietary PVST packet.  The only way to have the Cisco 6500 running PVST+ to send standard 802.1 packets is to ensure that the native vlan is equal to 1.

The other possibility is to do nothing and have each pass-through their bpdu packets which are unknown in the other environment.   To make your life easier, have only one connection between both environments.

Also, standardize the STP port costs in both platforms.

On the HP-A switches:
[H3C] stp pathcost-standard dot1t

On Cisco:
(config)# spanning-tree pathcost method long

Also consider other link protection methods such as loop detect and DHCP snooping.

stp instance 0 priority 4096 (on core only)

stp pathcost-standard dot1t

stp enable

stp region-configuration

region-name HP

revision-level 1

active region-configuration

loopback-detection enable

loopback-detection multi-port-mode enable

poe legacy enable pse 4

int g1/0/1

  undo enable snmp trap updown

  undo enable log updown

  loopback-detection enable

  loopback-detection action shutdown

  storm-constrain broadcast pps 300 50

  storm-constrain control block

  poe enable

  dhcp-snooping

  dhcp enable

on uplink ports – NOT in interface bridge-aggregate

dhcp-snooping trust

Better yet, just use IRF.  With IRF just turn on STP as a port protection method. No need for instances as LACP cross switch gives dual active links.  

Management clusters are prone to human errors as it is easier to change something on the
wrong port.   Much better a private address per device.  IRF is the way to go.  It offers:

·         dual uplinks (one from each switch) with LACP
·         redundancy
·         no failover time
·         fully used aggregates.