Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
I have a two MDS 9513 connected via FCIP tunnel. VSAN 100 is in allowed list and tunnel trunks properly.the zonesets show wwns across the links logging into fabric and i am even able to fcping successfully.there are two different storage arrays conne...
Trying to setup firewall rules between FabricManager and MDS switches.The documentation is not easy to understand and doesnt provide correct visuals Can anyone suggest which rules need to be opened i.e. source (FM or MDS) -> Destination (MDS or FM) -...
I need to statically route traffic between two switches (both MDS9513 running NxOS 4), across different FCIP links, depending on source and destination- VSAN 500 exists across both switches- both FCIP links are part of FCIP 500- VSAN 500 is allowed a...
One of my switch is showing unusual behaviour. Few ports went into "initialising" mode and refused to come up.Once I change the VSAN of the port, they come up well. If the VSAN is set back to original value, it again goes down.Event log shows followi...
Fabric manager not able to manage new 9124e switches. It is able to discover fabric using seed switches (9513) but all 9124e appear with Timeout (server,client) error. logs show that communication times out. Even if I try to select the switch and "re...
zoning was correctly done and both sites were connected properly.there was a port channel between the sites, i disabled on interface in the port channel and it got resolved.not sure why though
the RTT delay by each link is different and this is causing packets to arrive out of order.not sure if port channeling between two different links or different characteristics is good practive.
there is no direct procedure for this but you can make it easy.take config dump in text file or use cli filters (pipe,egrep,i filter) then you can edit it to create new config. at the same time to delete old config.then with a caution window,apply th...
perhaps you have sorted this out by now.consider using device aliases in new configuration as it stays valid across different vsans (need not define fabric aliases for each vsan)find-replace and copy-paste are great tool as suggested by Dynamoxxx, al...