I have a 9513 and a 9509 ISL'd in a single fabric. The Eports are in VSAN 2, and all the zones are in VSAN 1. ( I know this is not best practice, and is going to be fixed) Anyway, after making the 9513 the principle switch, and shutting down all blades in the 9509, VSAN 1 segments in Fabric Manager. I have done the following so far:
made the 9513 the principle switch
checked every zone in the zone set for VSAN 1 for discrepencies between what is contained in each switch. they are identical.
I don't know how to keep the VSAN from segmenting.
No.. VSAN 1 is not trunked. VSAN 2 was at one time. VSAN 2
was used for the ISL Trunk between the switches. But that trunk has been deleted. Right now, in order to keep VSAN 1 from segmenting, i have a couple of cables running between the switches as Eports. But if i remove them, VSAN 1 will segment.
I got it fixed.. IT ended up that Fabric Manager was just being stupid. When i was removing the switch from the ISL partnership, fabrci manager was still seeing both sets of zone sets and interpreting that as a "segmented VSAN". All i had to do was remove bot hswitches from fabric manager and then rediscover just the remaining switch. problem solved...
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
In the Previous articles of ACI Automation, we are using Postman/Newman as the Rest API tool to automate the ACI Configuration.
In this article I’m going to discuss on usin...
One of the first steps in building your ACI Fabric is to go through Fabric Discovery. While Fabric Discovery is usually a straightforward process, there are various issues that may prevent you from discovering an ACI switch. This article wil...