My Fibre Channel/SAN experience was nil until a few weeks ago. However, I have planty of experience on Cisco Ethernet routers and switches etc.
I'm sure I read somwehere that these switches are "so easy to set-up and training is not required"....yeah, right!
Well, we did create a new VSAN (10) and moved the 8 ports into the new VSAN. Created a zone and added all the 8 ports using their FCid's. Then created a zoneset and added the zone into the zonest and activated the zoneset.
It is my understanding that this should have worked BUT this was done by a 3rd party at the end of last week and they said that it didn't.
The other thing they tried was to leave the 8 ports in VSAN 1 and did a "default-zone permit" which should have opened up the 8 ports to each other. Tis did not work either.
show int brief - to get the interfaces that are working.
show zoneset active - to look at the active zoneset.
show zone vsan 10 - to see what is in the vsan 10.
show flogi database vsan 10 - to see what has logged into the fabric for vsan 10.
Basically, if you can see the interfaces and they are up and the interfaces are in a zone in an active zoneset, thats all you really need --- unless all the stuff you has does not understand fabrics which is probably unlikely.
Also, check out some of the debug options.
There is nothing simple about SAN-OS but it can be easy to setup quickly.
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...