In our lab I'm trying to get a CSS11503 with Gig over coper ports (SCM-2GE) to talk to a cat 4k fast ethernet port via cat5 straight-through. But no luck. Do those ports speak only with other Gig over copper switch ports? Or is there a way to get it to talk to the cat4k's fastethernet ports? Thanks.
Here is the output from phy? Notice that the 100 Mbits settings are only allowed for 10/100 ports. Also the AUTO setting will not work for these Gig over copper ports.
CSS11503(config-if[ 1/1])# phy ?
100Mbits-FD 10/100 ports only. Set to 100 Mbits/s, Full-Duplex
100Mbits-HD 10/100 ports only. Set to 100 Mbits/s, Half-Duplex
10Mbits-FD 10/100 ports only. Set to 10 Mbits/s, Full-Duplex
10Mbits-HD 10/100 ports only. Set to 10 Mbits/s, Half-Duplex
1Gbits-FD-asym Gigabit ports only. Set to Full duplex with asymmetric
pause toward link partner
1Gbits-FD-no-pause Gigabit ports only. Set to Full duplex with no pause
1Gbits-FD-sym Gigabit ports only. Set to Full duplex with symmetric
1Gbits-FD-sym-asym Gigabit ports only. Set to Full duplex with symmetric and
asymmetric pause toward local device
auto-negotiate Allow the interface to auto-negotiate speed and duplex
Thanks. But no - I had already tried a cross-over cable and this did not solve the issue. I eventually located a GigE blade for the Cat4k and *that* is the issue. The gig ports on a CSS are (surprisingly) not compatible with Fast Ethernet ports. I say surprisingly as every workstation I've bought for the last 3-4 years that has had a 10/100/1000 card as worked fine with fast ethernet. Seems like Cisco went out of its way to make CSS Gig ports not compatible. Maybe to force upgrading! Can't figure WHY they would select an interface incompatible with Fast Ethernet. Maybe their marketing team was in on that as a way to spur cheap customers to more expensive switches.
BTW - it was a straight-through cable from the CSS to the Gig port on the Catalyst that brought link light.
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...