One of our uplink ethernet FI-6120 connected to J*N*R switch..
1. when we set the J*N*R switch port to trunk mode, the uplink ethernet always down,(we test the connection using ping) how to solved this ? or any basic information?
2. right now the switch's port is in access mode. the strange is .. connections from the outside network is suddenly broken and we must ping from blade server to gateway to make the connection up again . every time the connection from outside network is broken we must ping from blade to gw,
this is not hapen to other ethernet uplink (connected to cisco switch)
1) Are all VLANs on UCS loosing connectivity or is it just a particular VLAN which does when you enable trunk on the upstream switch. If its just one VLAN, it could be a native vlan miss-match on either side causing this issue.
2) If i understand it correctly, you have uplinks going to two different type of upstream switches one to the J switches and one to CISCO..correct? Is so did you could be in the l2-disjoint situation if you are not running version 2.0 and have not configured the l2-disjoint properly.
Also, please keep in mind that since you have configured each of the Cisco and J*n*r switch uplinks to only carry a single VLAN, make sure that every single vnic on all blades each only have a single VLAN.
I am not very sure about the required config on the J switch but here is something which can help you. All uplinks on the FI are configured as trunk ports even though you allow only one vlan. Hence traffic comming out of the interfaces will be tagged (unless the vlan is native).
Make sure with the l2-disjoint config you have added the vlans correctly to the correct uplink interfaces. please rememebr vlan 1 will be allowed on all interfaces so do not used vlan 1.
Here is a command which you can use to check the DR for each vlan (DR is the interface which is going to recieve and frwd the broadcast and multicast traffic - e.g. arp brcst) :
(nxos)# show platform software enm internal info vlandb id x
(replace x with the vlan number)
Can you make sure the DR for the vlan where you are having issues is on the interface going to the correct switch (either J or cisco)
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...