After upgrading to 5.1.1 our Nexus 7010 does not like the 3rd party HP SFP+ Copper cables anymore:
gebData-2# sh int ethernet 1/18 transceiver
transceiver is present
type is 10Gbase-(unknown)
name is WL GORE
part number is 487660-001
revision is C
serial number is 011910-144
nominal bitrate is 10300 MBit/sec
Link length supported for copper is 7 m
cisco id is --
cisco extended id number is 4
gebData-2# sh int statu | i 1/18
Eth1/18 -- sfpInvali routed full auto 10Gbase-(un
Is there a new "transceiver unsupported" comand or are 3rd party SFP disallowed now.
Okay, so if you're a customer with a large data center using third-party server infrastructure at the edge (such as HP BladeSystems) and you have a large investment in HP SFP+ DACs that have been working fine with your Cisco Nexus infrastructure, you are royally hosed.
This is totally unacceptable.
HP are equally as guilty, as they apparently also do not allow third-party DACs to connect to their Virtual Connect modules.
A correctly rated SFP+ module is a correctly rated SFP+ module, whether or not it is sold by this manufacturer, or that manufacturer.
Yet customers stand by and accept this anti-competitive behavior from their hardware vendors, hurting only themselves. We will be hammering our Cisco and HP reps about this fiasco.
Topology & Design:
Two ACI fabrics
Stretching VLANs using OTV
Both fabrics are advertising BD subnets into same routing domain
Some BDs(or say VLANs) are stretched, but some are not.
Endpoints can move betwee...
VMware Trunk Port Group is supported from ACI version 2.1
VMM integration must be configured properly
ASA device package must be uploaded to APIC
ASAv version must be compatible with ACI and device package version
Topology &Design:Traffic flow within same fabric:Endpoint moves to Fabric-2Bounce Entry Times OutTraffic Black-holedSummarySolutionAppendix:
In the Previous articles of ACI Automation, we are using Postman/Newman a...