Author Archives: Joost van der Made

About Joost van der Made

CCIE #19958 Voice, Wireless and Data Center CCSI #35056 for more info about me.

CCIE Data Center Passed

This blog was my personal blog to study for the CCIE Data Center and can contain some mistakes . 😉 I passed the lab at June 27 2013 and now I ain’t posting on this blog anymore. If you want to know new stuff regarding Data Center of whatever, please have a look at : …

Read more »


OTV Header Format Some consideration must be given to the MTU across the transport infrastructure. Consider the OTV packet header layout. A 42 byte OTV header is added and the DF (Don’t Fragment) bit is set on ALL OTV packets. The DF bit is set because the Nexus 7000 does not support fragmentation and reassembly. …

Read more »

vPC Role

There are two defined vPC roles: primary and secondary.vPC role defines which of the two vPC peer devices processes Bridge Protocol Data Units (BPDUs) and responds to Address Resolution Protocol (ARP).Use role priority <value> command (under vPC domain configuration context) to force vPC role to primary for a dedicated peer device.<value> ranges from 1 to …

Read more »


Identify iSCSI traffic : class-map type qos class-iscsimatch protocol iscsimatch cos 4class-map type queuing class-iscsimatch qos-group 4policy-map type qos iscsi-in-policyclass type qos class-fcoeset qos-group 1class type qos class-iscsiset qos-group 4 policy-map type queuing iscsi-in-policyclass type queuing class-iscsibandwidth percent 10class type queuing class-fcoebandwidth percent 10class type queuing class-defaultbandwidth percent 80policy-map type queuing iscsi-out-policyclass type queuing class-iscsibandwidth …

Read more »

iSCSI Ports

iSCSI uses TCP (typically TCP ports 860 and 3260).

Nexus 1000v Config for UCS with iSCSI boot.

Inside UCS, all VLANs are trunked and not native, EXCEPT the iSCSI VLAN; The iSCSI NICs needed to be set as the Native VLAN to allow the hardware to boot from the iSCSI devices, since there was no OS to allow us to assign a specific VLAN until after boot; Inside the Standard vSwitches that …

Read more »

N1KV Layer 3 mode

Change svs mode from Layer 2 to Layer 3 in Cisco Nexus 1000V. The configuration in the highlighted code is optional to change svs mode from Layer 2 to Layer 3. Note switch(config)# svs-domain switch(config-svs-domain)# no control vlan Warning: Config saved but not pushed to vCenter Server due to inactive connection! switch(config-svs-domain)# no packet vlan Warning: …

Read more »

N1Kv installation on an UCS System

If you are installing a Cisco Nexus 1000V in an environment where the upstream switch does not support static port channels, such as the Cisco Unified Computing System (UCS), you must use the channel-group auto mode on mac-pinning command instead of the channel-group auto mode command

N1K VEM Upstream Switch Prerequisites

The following spanning tree prerequisites apply to the switch upstream from the Cisco Nexus 1000V on the ports connected to the VEM spanning-tree port type edge trunk spanning-tree bpdu filter spanning-tree bpdu guard.

Nexus1000v VSM/VEM communication over Layer3

Over Layer 3 (recommended): Communication between the VSM and the VEM is done through Layer 3, using the management interface of the VSM and a VMkernel interface of the VEM. Layer 3 connectivity mode is the recommended mode. The Layer 3 mode encapsulates the control and packet frames through User Datagram Protocol (UDP). This process requires …

Read more »