Upgrade SAN-OS to NX-OS

I recently purchased a pair of MDS 9216i switches for my CCIE Data Center studies, as they will suit me for the majority of my storage studies (minus FCoE). The MDS’s shipped with old code, SAN-OS 3.0, and I needed them upgraded to at least NX-OS per the blueprint. For a lab with disruptive capabilities, this is super easy to do.

I quickly found these resources, which walked me through the upgrade:


First, a quick show version to see what I’m currently running:



Configuring IP Multicast in Sparse-mode with Auto-RP

Goal: Multicast across VLANs and across Layer 3 hops to other campus locations and verify shared-tree stream to the Rendezvous Point (RP).

Below is a diagram and basic configuration I used for sparse-mode multicasting utilizing auto-rp. I chose sparse-mode because of performance and scalability reasons for my one-to-many multicasting needs (streaming live events from a few sources).

I’m using the 6500 in Site A as my sole RP in this setup, strictly for simplicity. (FYI, the 6500 is actually a VSS cluster). Site B and Site C are over a MetroE connection across geographically diverse locations.

IGMP snooping is usually enabled by default on Cisco switches, but I have it disabled on the network, only allowing IGMP snooping on specified VLANs.

I used VLC to test multicasting, streaming source as rtp:// with a TTL of 6.

NOTE: I had to modify the global VLC settings on my source PC to get this to work. Do not forget to do this if testing with VLC! This mod can be found in VLC Preferences > Stream Output > Access Output > Hop Limit.


Unable to access Wireless LAN Controller after CLI initial setup

When running through the initial configuration of my new Cisco Wireless LAN Controller (WLC), I unknowingly left my management vlan id untagged. Once I racked and patched the WLC on the corporate network to continue configuration I was not able to reach it, couldn’t even ping it. To get access to the WLC I added this to the trunk port configured for the controller

Switch(config-if)# switchport trunk native vlan VLANX
(where VLANX is the vlan in which the management IP address you configured for your WLC resides.)

Upon doing this you should be able to access your WLC via ICMP and HTTP