FCoE – Waiting for flogi… Last week I was working on a pair of Nexus 5596s and for the life of me could not get a CNA to login to the fabric. I kept getting the following error: 2012 Jul 6 11:36:33 ANR-N5K-A %PORT-5-IF_TRUNK_DOWN: %$VSAN 664%$ Interface vfc1, vsan 664 is down (waiting for flogi) After reconfiguring the vfc and pulling my hair out, I contacted Cisco TAC and learned the error of my ways. The…
Read MoreBooting UCS C from FlexFlash We installed a few UCS C220M3s the other day and opted to boot from the 16GB FlexFlash SD card. The confusing part of the FlexFlash is that it’s broken down into four partitions: SCU — The server can access the Cisco UCS Server Configuration Utility. Drivers — The server can access the Cisco drivers. HV — The server can access a user-installed hypervisor. HUU — The server can access the Cisco…
Read MoreDMVPN as a Redundant Network Solution Recently I redesigned a network to take advantage of DMVPN. This customer had the need for high availability between their main office and branches with the advent of cloud-based applications that their organization used. For instance, they needed the branch to be able to connect back to the main office if their MPLS connection failed as well as failover Internet connectivity through the MPLS network in the event that the…
Read MoreNexus FCoE Design and Configuration I have been deploying more and more FCoE solutions on Nexus 5500s lately and thought it best to write down my design/config here for reference the next time I perform a deployment. What always throws me is that the vPC is intelligent enough to keep the FCoE VLANs isolated per FC storage best-practices (i.e. VLAN 11 on Fabric A, VLAN 12 on Fabric B), but allows the Data VLAN (i.e. VLAN…
Read MoreUpgrading the Nexus 1000v to SV1(3) I performed my first Nexus 1000v upgrade last week, upgrading from SV1(2) to SV1(3). It was relatively painless, but definitely worth reading about what is involved. Read on… Prerequisites: download Nexus 1000v 4.0(4)SV1(3) software save the config (copy run start) back up the config clone primary VSM virtual machine Upgrade the VSMs Do this on the primary VSM (it will automatically be synced to standby): Copy bin files to primary…
Read MoreSNMP Perl Scripts Occasionally I need to access a switch with goofed up AAA configuration or a bunch of switches that I want to execute the same commands on. When I used to work for a big Fortune 500 company this became more of a necessity, so I wrote the following Perl script to copy and push configuration to the devices in question. I found myself needing this script again as I prepared hundreds…
Read MoreSetting Up Alert Notification of Server Status Changes in Cisco Unity Connection We recommend that you configure the Cisco Unified Real-Time Monitoring Tool to send notifications for the following Cisco Unity Connection alerts: AutoFailbackFailed AutoFailbackSucceeded AutoFailoverFailed AutoFailoverSucceeded NoConnectionToPeer SbrFailed More info # http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/9x/cluster_administration/guide/9xcuccagx/9xcuccag005.html
Read MoreCisco Nexus B22HP FEX Deployment Guide It seems that Cisco hasn’t completed ticked off HP with their UCS line of servers, because they were able to collaborate on a fabric extender for the HP C-series chassis, the Nexus B22HP. A fabric extender is a Cisco Nexus switch (typically a Nexus 2000) that is managed via an upstream Nexus 5500 switch. It allows you to scale out your top of rack (TOR) switches and still manage them…
Read MoreCisco UCS Direct-Attached SAN New in Cisco UCS firmware 2.1 is the ability to directly-attached a fiber-channel SAN to the Fabric Interconnects; to see all the other cool features head on over to UCS Guru’s blog. A few years ago, Cisco supported this very briefly before changing their minds because your sole method of governing access to the SAN was LUN Masking and not zoning. In firmware 2.1 Cisco flipped the switch and added support for…
Read MoreSo what is VXLAN and why do we need it? Well put simply it’s VLAN with an X in the middle 🙂 the X standing for eXtensible. VXLAN was a joint project between Cisco, VMware, Redhat and Citrix which is why it has been so widely adopted, and underpins the majority of SDN offerings. And as to why we need it, well that’s mainly to address two limitations of using regular VLANs. Scale and Flexibility….
Read More
Introduction Cloud computing services have grown exponentially in