This is a basic diagram of our currently operational fabric: ( "|" represents FC optical links)
| | |
We would like to interconnect MDS9124 with another MDS9124 switch to provide redundancy in case one of the switches stops working. We have created one additional VSAN and use that VSAN for the fabric. Physically, we would connect servers and storage to the other MDS switch with optic cables as well, since we have dual port HBA's. How do we go about configuring the other switch since this model doesn't support High Availability? We will create ISL trunk, convert ISL ports to E ports and specify our VSAN that will be shared. Any additional configuration for this solution? The goal is to connect servers to storage in a way that supports failure of one SAN switch. Thank you for your answers!
do make sure to review your configuration before you remove ISL between the two switches, if you have storage array connected to switch A and server connected to switch B ..i am sure you know what will happen when you remove ISL link.
Currently, there is no ISL link, physical connections are connected the way you described and second MDS has default configuration. We configure the second switch similar to first, and multipath software on server (MS MPIO) will handle the redundancy?
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...