Configuration, Design, and Troubleshooting of Cisco Nexus 1000 · • L3 control requires a VMKernel NIC We need an L3 interface to forward control traffic • Recommend using the

© 2013 Cisco and/or its affiliates. All rights reserved. 1

Cisco Support Community Expert Series Webcast:

Configuration, Design, and Troubleshooting of Cisco Nexus 1000

Louis Watta @mc68881rc Technical Leader

June 4, 2013

2 © 2013 Cisco and/or its affiliates. All rights reserved.

• Today’s featured expert is Cisco Support Engineer Expert

• Ask him questions now about Cisco Nexus 1000v

Louis Watta

Technical Leader in TS Incubation

3

Panel of Experts

Event Date: June, 2013

Robert Burns

Technical Leader Steve Winters

Customer Support Engineer


Today’s presentation will include audience polling questions

We encourage you to participate!


If you would like a copy of the presentation slides, click the PDF link in the chat box on the right or go to

https://supportforums.cisco.com/community/netpro/data-center/unified-computing

Or, https://supportforums.cisco.com/docs/DOC-33836







https://supportforums.cisco.com/docs/DOC-33836





Our panel of experts will be answering them later in the webcast


a) Nexus 1000V what is it?

b) I’ve heard of Nexus 1000V but not deployed it

c) I’ve played with it in a lab environment

d) I’m running it in production.

What is your level of experience with Nexus 1000v?


Configuration, Design, and Troubleshooting of Cisco Nexus 1000

Technical Leader

June 4, 2013

Louis Watta


• Current Nexus 1000V Releases and New Features

• Licensing

• Virtual Supervisor Module (VSM)

• Virtual Ethernet Module (VEM)

• Upgrades

• Cisco Nexus 1x10



• 5.2(1)SM1(5.1) Hyper-V only

Support for SCVMM 2012 SP1 and Windows Server 2012

• 4.2(1)SV2(1.1) - 2.1

New Features including VCPlugin, Vtracker

Cisco Trustsec Support (CTS)

License changes for Essential(free) and Advanced

• 4.2(1)SV1(5.x) - 1.5.x

1.5, 1.5.1a, and 1.5.2

1.5.2 first version to support ESXi 5.1


• License Changes

Essential (free)

Advanced (licensed)

• Cisco TrustSec Support

• vTracker

• VCPlugin

• VSM HA improvements

• VSMs split between Datacenters

• VEM remote branch support

• Enhanced Installer

• Enhanced Upgrades

Allows for configuration changes even if VSM is higher rev than VEM


• Increased Scale

128 VEM support per VSM

300 ports per host

4000+ ports per VSM

• VXLAN Evolution

Unicast mode

No multicast configuration required

Mac-address distribution

• VXLAN Gateway


• Openstack support

• KVM and XEN support

• Increase configuration limits

Even more increase in configuration limits

• Citrix NetScaler on Nexus 1110

• Imperva WAF on Nexus 1110



• All features but…

Cisco TrustSec (CTS)

DHCP snooping

IP Source Guard

Dynamic ARP Inspection

• You get 512 socket license

No expiration

• Default mode on new install

• Support Options

Pay Nothing – support is through the communities site off cisco.com

https://communities.cisco.com/community/technology/datacenter/nexus1000v

Pay for service contract

Cost is $39 per socket, per year for TAC support.


• For customers that want more security features

• Required for VSG

• Existing customers with licenses will be considered Advanced

No requirement to use Advanced mode

• Licensed customers can get Virtual Security Gateway(VSG) for free

Account team can submit request

Note VSG will no longer be sold separately


• Extra licenses to use in temporary situations

• 16 extra sockets

Sometimes more depending on number of licenses you’ve purchased

• Can only be used after a valid license is installed

• Not easy to tell which VEM is using an overdraft license


a) Essentials

b) Advanced

c) Not Sure

Which Licensing version do you think you will deploy?



• What is the Virtual Supervisor Module (VSM)

• Planning

• Installation

• Troubleshooting

22

Hypervisor Hypervisor Hypervisor

Modular Switch

…

Linecard-N

Supervisor-1 (Active)

Supervisor-2 (StandBy)

Linecard-1

Linecard-2

Ba

ck P

lan

e

VEM-N VEM-1 VEM-2

VSM: Virtual Supervisor Module

VEM: Virtual Ethernet Module

VSM-1 (active)

VSM-2 (standby)

Virtual Appliance

Network

Admin

Server

Admin

NX-OS

Control Plane

NX-OS

Data Plane


• VSM is a Virtual Machine

On ESXi

On Nexus 1x10

Hyper-V

• Control plane for the Nexus 1000V solution

• Responsible for

Programming and managing Virtual Ethernet Modules (VEM)

Communicating with Management Applications

VMware vCenter

Microsoft SCVMM 2012 SP1

• 1 VSM HA pair can manage 64 VEMs

• Coexist with VMware vSwitch, vDS, Microsoft Logical, Native Switch


• VSM is all Hyper-V or all ESXi VEM modules

No mixing of VEM modules currently allowed

• VSM can run anywhere

VSM attached to Hyper-V VEMs can run on ESXi

Nothing specific to the VSM VM to require it to run on a specific hypervisor

• Configs are slightly different


• Support the VSM on a VEM

• Support the VSM on any hypervisor native, logical, or distributed switch

• Support the VSM on any supported hypervisor (ESXi/Hyper-v)

• Keep VSMs on different hypervisor hosts

Use anti-affinity rules

• Storage wise we don’t care.

VSM can be hosted on network storage

26

hypervisor

VEM-2

VM VM VM

VSM

hypervisor

VEM-1

VM VM VM

VSM

hypervisor

VEM-2

VM VM VM

VSM

hypervisor

VEM-1

VM VM VM

VSM

vSwitch vSwitch

hypervisor

VEM-2

VM VM VM

hypervisor

VEM-1

VM VM VM

hypervisor

vSwitch

VM VM VM

VSM

Management Cluster

Data Cluster

VSMs on VEM VSMs on vSwitch

VSMs in Mgmt Cluster

27

• VSMs and VEMs spread across Datacenters

• VSMs can be split across DCs

New with 2.1

Requires L2 connectivity across DCI

10ms latency across DCI

• Not Supported with Hyper-V

Supported in a later release

VSM

VSM

hypervisor

VEM-1

VM VM VM

Local DC

hypervisor

VEM-2

hypervisor

VEM-4

VM VM VM

hypervisor

VEM-3

VM VM VM

Remote DC

VM VM

DCI

VM


• VSM on a Nexus 1010/X or 1110-S/X

It’s still a Virtual Machine

Up to 10 VSMs on one 1110-X

• Always deploy in pairs!

• 1x10 allows for Network team to own the virtualization platform

• 1x10s should go in the Aggregation Layer

• Stretched Model requires

L2 Connectivity

10ms latency

No Hyper-V support


• L3 Mode

We recommend L3 and it’s the default mode now

Easier to troubleshoot

Flexible

Requires an IP address be assigned to the VEM

Uses UDP port 4785 for both source and destination

• L2 mode

Requires L2 connectivity through Control interface to all VEM modules

L2 still supported on ESX

Not supported with Hyper-V


• Two options for the L3 control interface

Mgmt 0 (default)

Control 0

• Recommend mgmt 0

• Use control 0

To separate control and management traffic

• Mgmt and Control use different VRF

Mgmt 0 uses VRF management

Control 0 uses VRF default

• Primary and secondary VSM still need to be L2 adjacent

31

• For new installations use the Installer application

ESXi and Hyper-V

• ESXi

Installer can also migrate ESXi hosts to the N1KV

ISO and OVA still available Use for established VMware vSphere deployments

• Hyper-V

Installer or Template/ISO install methods

• Save inputs to a config file


• VSM connects to vCenter using SSL connection

Plugin that contains SSL cert

Unique extension ID for the VSM

• VSM talks to vCenter using its API

We push and pull data to/from vCenter

• VSMs get tied to a VMware Datacenter

Multiple VSMs tied to same DC is allowed

Can get confusing


• If you get “Extension key was not registered before it’s use”

Re-register the Extension Key with VMware vCenter

• If you get “Connection refused. connect failed in tcp_connect()”

VMware admin could have changed the http port

API communication is through port 80 with VMware vCenter

Find new port and change it on VSM


• Extension gets installed on SCVMM via a Provider Extension

Simple Windows installable file

• SCVMM pulls data from the VSM using our API

VSM has a REST API now

SCVMM pulls data once every 30 minutes (yes 30 minutes)

You can manually force a refresh in SCVMM

• VSMs get tied to a SCVMM Host Group

Multiple VSMs tied to same Host Group is allowed


• No persistent connection between VSM and SCVMM

Manually refresh through SCVMM to update

• Any connectivity errors should show in the “Jobs” Screen

• Verify Connectivity by accessing API from SCVMM host

http://<vsm-ip>/api/n1k

Remember to add admin credentials to SCVMM run-as accounts

Currently API can use local accounts only

Verify any proxies or firewalls

• If the extension does not show in SCVMM re-install the provider


• VSM requires 4GB RAM

• No stretched deployment support

Even with Nexus 1010/1110

Coming in later release

• Recommend VSM be on Microsoft Native vSwitch

• 64 VEM support, 2k veth ports

• Domain ids shrink from 4k to 1k

NXOS 5 issue

• L3 Control mode only


• L3 control is the preferred method

• Use mgmt 0 for control

• Primary and Standby VSM in same L2 domain!!!

Required even if VSMs are split between datacenters

• VSM on VEM is supported

• VSM primary to secondary latency max 10ms

10ms even for VSMs split between datacenters

• VSM to VEM latency 5-10ms

For VEMs at branch locations 100ms

• Use the clone option to backup your VSM!!



• Again we recommend L3 Control

• L3 control requires a VMKernel NIC

We need an L3 interface to forward control traffic

• Recommend using the ESXi management vmkernel nic

Requires you migrate the management interface to the VEM

Doesn’t require static routes on ESXi hosts

• Don’t create an L3 Vmkernel nic on same subnet as mgmt Vmkernel nic

40

• Don’t use multiple VMKs on the same subnet but virtual switches

• VMware uses a single TCP/IP stack for all VMK interfaces

• No way to direct traffic up a particular interface when they share the same subnet

• One interface gets picked for all traffic on that subnet

• Check out VMware KB article 2010877

VMware ESX

VEM-1

VMK1

192.168.10.200

VMK0

192.168.10.100

vSwitch


• VMware Update Manager(VUM) does all the work

• Requires HTTP server on the VSM

• Turn off the following VMware cluster settings

HA, DRS, and DPM

5.1 Seems to do this automatically

• VUM Logs on vCenter Server in

C:\Documents and Settings\Application Data\All Users\VMware\VUM\logs

• VEM modules get stored in

C:\ProgramData\VMware\VMware Update Manager\Data\hostupdate

CISCO directory comes from VSM

CSCO directory comes from VUM portal

Uninstalling VUM does not clean out the above directories


• With ESXi 5 use esxcli

Can be run remote or locally on the host

Local

esxi5.0# esxcli software vib install –v http://<VSM-IP-

Address>/cisco/vibs/VEM/4.1.0/VEM-4.1.0-patch01/cross_cisco-vem-v140-4.2.1.1.5.1.0-

3.0.1.vib

Remote

linux1# esxcli --server <server> software vib install -v http://<VSM-IP-

Address>/cisco/vibs/VEM/4.1.0/VEM-4.1.0-patch01/cross_cisco-vem-v140-4.2.1.1.5.1.0-

3.0.1.vib

• ESX/ESXi 4.1

Esxupdate (local)

esx4.1# esxupdate –b cross_cisco-vem-v140-4.2.1.1.5.1.0-2.0.1.vib update

Vihostupdate (remote)

linux1# vihostupdate –install –bundle cisco-vem-v140-4.2.1.1.5.1.0-2.0.1.zip --server

<server>

43

• Uses VUM or httpClient

• Tries VUM first

• httpClient needs to be enabled on every ESXi host

• Requires administrator privileges to the ESXi host

• VSM must be connected to vCenter


• VMware introduced Stateless ESXi with version 5

• ESXi PXE boots

• No information is stored on local disks

No place to install the VEM and store opaque data

• VEM module has to be built into the boot image

• Possible using VMware PowerCLI

• Instructions are in Install and Upgrade Guide

http://www.cisco.com/en/US/docs/switches/datacenter/nexus1000/sw/4_2_1_s_v_1_5_1/install_upgrade/vsm_vem/guide/n1000v_installupgrade.html




• Only L3 supported

• No special NIC required

• We talk to the Windows Server 2012 Management NIC

Management NIC can be assigned to a physical nic

Virtual NIC attached to Microsoft native or logical switch

Not recommended to connect Management NIC to VEM

• No special port-profile required

• Very easy configuration


• VEM is a simple Windows installation

• Manually double click the msi file and install

• SCVMM will automatically install VEM if it’s not manually installed

• Upgrades will leverage Windows Server Update Services (WSUS)

47

• VMK interface created on ESXi host

• Can the ESXi host ping the VSM control/mgmt interface

• Static route needed?

• Uplink profile created correctly

• L3 veth port-profile created correctly

• Check the opaque data


• Can you ping the control interface of the VSM?

~ # esxcfg-vmknic -l

Interface Port Group/DVPort IP Family IP Address Netmask Broadcast MAC Address MTU

TSO MSS Enabled Type

vmk0 VMkernel IPv4 172.18.217.180 255.255.255.0 172.18.217.255 00:18:fe:72:f2:aa 1500

65535 true STATIC

vmk2 34 IPv4 192.168.11.180 255.255.255.0 192.168.11.255 00:50:56:78:6f:52 1500

65535 true STATIC

ESXi VMK interfaces are special interfaces

Need to be created by VMware Admin

~ # vmkping 192.168.11.10

PING 192.168.11.10 (192.168.11.10): 56 data bytes

64 bytes from 192.168.11.10: icmp_seq=0 ttl=255 time=0.570 ms

64 bytes from 192.168.11.10: icmp_seq=1 ttl=255 time=0.420 ms

Verify Connectivity


• Only one default gateway is allowed by ESXi

Usually used by the VMK being used for management access

• Remember ESXi host 1 was using VMK 192.168.10.154

It needs to talk to 192.168.11.10

Requires a static route be defined

• Just like linux

route add –net 192.168.11.0 netmask 255.255.255.0 gw 192.168.10.1

• This is why we recommend moving mgmt and using it for VEM

50

• Check SVS domain parameters n1kv-l3# show svs domain

SVS domain config:

Domain id: 43

Control vlan: 1

Packet vlan: 1

L2/L3 Control mode: L3

L3 control interface: control0

• Verify control 0 n1kv-l3# show run int control 0

interface control0

ip address 192.168.11.10/24

• Verify VRF default n1kv-l3# show ip route

IP Route Table for VRF "default"

0.0.0.0/0, ubest/mbest: 1/0, pending

*via 192.168.11.1, control0, [1/0], 4d23h,

static

• Can the VSM ping the VMK interface n1kv-l3# ping 192.168.11.180 vrf default

PING 192.168.11.180 (192.168.11.180): 56 data

bytes

64 bytes from 192.168.11.180: icmp_seq=0 ttl=63

time=1.082 ms

64 bytes from 192.168.11.180: icmp_seq=1 ttl=63

time=0.841 ms


• Uplink needs to allow VLANs 10 and 11

• VLANs 10 and 11 need to be system vlans

n1kv-l3# show run port-profile uplink

port-profile type ethernet uplink

vmware port-group

switchport mode trunk

switchport trunk allowed vlan 10-11,150-152

channel-group auto mode on mac-pinning

no shutdown

system vlan 10-11

state enabled


• VMK1 interface needs to be migrated to this port-profile

• It must have capability l3control and system vlan n1kv-l3# show run port-profile L3-control-vlan11

port-profile type vethernet L3-control-vlan11

capability l3control

vmware port-group

switchport mode access

switchport access vlan 11

no shutdown

system vlan 11

state enabled

• Each VMK1 VLAN needs a new port-profile

So create another for VLAN 10

• VSM will not allow VMs to connect to this port-profile

VMK interfaces only


• Quite a bit simpler

• Verify SCVMM can talk to VSM

Verify API reachability

Check for proxies/firewalls

• Verify Logical Switch Compliance

Switch compliance can get out of whack

Verify compliance and remediate if necessary

• Restart the Nexus1000v Service

Restart the process on the Hyper-V Host


• Use L3 Control

• Use ESXi mgmt vmk interface for control

• Control network should have low latency and available bandwidth

10ms for local DC

100ms for branch office deployment

• On UCS make Service Profile does not contain “Dynamic VNICs”

VEM and VM-FEX are mutually exclusive



• First always read and follow the upgrade guides

Go in order

• Take a backup of the VSMs

On ESXi/Hyper-V use the clone to template option

On Nexus 1x10s use the export function

Backup the running-config

• Generate a tech-support before the upgrade

• If something goes wrong STOP and call TAC

• Use a maintenance window

VEM upgrades require ESXi hosts to be in Maintenance Mode


Starting Version

1.4 1.5 2.1 Combined VMware upgrade

Notes

1.3 Yes Yes* Yes* No 1.4 last version to support ESX

4.0

1.4 Yes Yes No 1.4 last version to support ESX

4.0

1.5 Yes Yes**

• Upgrade matrix tool http://www.cisco.com/web/techdoc/n1kv/upgrade/utility/n1kvmatrix.html

* Must upgrade to 1.4 first

** Combined upgrade only supported from 1.5.2 to 2.1 and VMware vCenter 5.0U1 or later

http://www.cisco.com/web/techdoc/n1kv/upgrade/utility/n1kvmatrix.html

http://www.cisco.com/web/techdoc/n1kv/upgrade/utility/n1kvmatrix.html


• Allows you to upgrade N1KV VEM and ESXi at the same time

• Requirements

VSM and VEMs must be at 1.5.2 or higher

vCenter and VUM servers must be at 5.0 Update 1 or higher

• Steps

Upgrade VSM to 2.1

Create an upgrade ISO image including new VEM module for ESXi

Set up a VUM Baseline

Update bulletin ID from VSM

Initiate upgrade from vCenter on the ESXi host


• Changes from 2.1

You can now Upgrade VSMs and make changes without upgrading VEMs

• Upgrade is similar to other Nexus switches

Copy new kickstart and system images

Run “install all”

“install all” does the following

Upgrade/Reboot the Secondary VSM

Switchover to Secondary VSM – It’s now the active VSM with VEMs attached

Upgrade/Reboot the old-Primary VSM

Attach old-Primary VSM as Secondary

• Requires no outage of the VSM


• If something is wrong after the VSM upgrade STOP

Call TAC

Roll back using backup method

Shutdown the VSM VMs

Power-on the Clones (ESXi), Import the backup (Nexus 1x10)

• Sometimes the VEM won’t connect to the Standby VSM

Try a “system switchover” once the old primary is upgraded

• Might want to verify Standby VSM before upgrade

Make sure VEMs can connect to standby

Use “system switchover” command


• VEM module upgrade kicked off on VSM

If VUM is installed everything is automatic

VSM communicates with vCenter to manage the upgrade

Host is placed in maintenance mode(if DRS is installed VMs are migrated off)

VEM is upgraded and host exits maintenance mode

Moves on to the next host

If VUM is not installed

Still initiate the process on the VSM

User manually places ESXi hosts in maintenance mode

Upgrade the VEM with esxcli command

Exit maintenance mode and move to the next host

• Always complete the upgrade

Issue the “vmware vem upgrade complete” command

This signals vCenter to use the new VEM when hosts are added


• Remember the VMware admin has to acknowledge upgrade in vCenter

• Don’t upgrade the VEMs by pushing a baseline

• Make sure you have DRS capacity

Need to be able to handle one ESXi host failure

• If a particular ESXi host fails

It’s usually because the host cannot go into maintenance mode

From vCenter attempt to put the host in maintenance mode

Troubleshoot any issues that prevent it

If an ESXi host is running a vCenter VM this can cause problems

• You can restart the VEM upgrade after it fails

It will only upgrade hosts that did not succeed



• Based off UCS C2x0 server

Provide 6 x 1G network connections

1110-X 2 x 10G (not active in current code)

10G available only on purchase. No upgrade available

• Virtual Service Blade (VSB) Support

1010/1110-S supports 6

1010/1110-X supports 10

• Current supported VSBs

Nexus 1000V VSM

Virtual Security Gateway (VSG)

Network Analysis Module (NAM)

Data Center Network Manager (DCNM)

Imperva WAF

Citrix NetScaler


• Must be deployed in pairs

No option for standalone

• Deploy in the Aggregation Layer

• Must be in the same L2 domain for management and control

• Uses same HA mechanism as VSM with domain id and control vlan

Do not overlap the domain id between a 1x10 and a VSM

• Not supported

Primary and Secondary VSM on same 1x10

Primary VSM on ESX and Secondary VSM on 1x10 or vice versa


VSB Import/Export

• Works with VSM, NAM, and VSG

• Can Import/Export both primary and secondary

• Export requires that VSB be shutdown

• Images are stored in “export-import/” dir on bootflash

Can be manually copied off to remote storage


• Network traffic is classed into 3 categories

• Management

Carries the mgmt 0 interface of the 1x10

Carries the mgmt 0 traffic for all VSMs installed

• Control

Carries all the control and packet traffic for the VSMs installed on the 1x10

Carries control traffic for HA between primary and secondary 1x10

• Data

Used by Virtual Service Blades (VSB) other than VSM

• 5 Network Topologies you can choose


Uplink

Type

Management VLAN Control VLAN Data VLAN

1 Ports 1 and 2 Ports 1 and 2 Ports 1 and 2

2 Ports 1 and 2 Ports 1 and 2 Ports 3-6

3 Ports 1 and 2 Ports 3-6 Ports 3-6

4 Ports 1 and 2 Ports 3 and 4 Ports 5 and 6

Flexible There is no traffic segregation based on traffic class


• If you are not planning on using other VSBs

Topology 3 gives best bandwidth and redundancy for control VLAN

Negative is that is harder to configure

• Flexible allows any configuration

Recommend port-channels

Remember VSM latency is key over bandwidth

• Use VPC or VSS upstream if you have it


Use the Q&A panel to submit your questions. Experts will start responding those


• N1K Download and 60-day Eval: www.cisco.com/go/1000vdownload

• N1K Product Page: www.cisco.com/go/1000v

• N1K Community: www.cisco.com/go/1000vcommunity

• N1K Twitter www.twitter.com/official_1000V

• N1K Webinars: www.cisco.com/go/1000vcommunity

• N1K Case Studies: www.tinyurl.com/n1k-casestudy

• N1K Whitepapers www.tinyurl.com/n1k-whitepaper

• N1K Deployment Guide: www.tinyurl.com/N1k-Deploy-Guide

• N1K on UCS Best Practices: www.tinyurl.com/N1k-On-UCS-Deploy-Guide

• VXLAN Web Conference: www.brighttalk.com/webcast/279/41277

http://www.cisco.com/go/1000vdownload

http://www.cisco.com/go/1000v

http://www.cisco.com/go/1000vcommunity

http://www.twitter.com/official_1000V

http://www.cisco.com/go/1000vcommunity

http://www.tinyurl.com/n1k-casestudy



http://www.tinyurl.com/n1k-whitepaper



http://www.tinyurl.com/N1k-Deploy-Guide





http://www.tinyurl.com/N1k-On-UCS-Deploy-Guide









http://www.cisco.com/go/1000vdownload


a) Basic L2 switching

b) Security features like ACLs, DHCP snooping, IP Sourceguard, etc..

c) Monitoring features like Netflow, SNMP, SPAN, and ERSPAN

d) Cross platform hypervisor support

e) Advanced features like vpath and integration with ASA1000v, VSG, and Cloud Services Router

f) VXLAN

Which Features of the Nexus 1000v interest you the most?


Expert responding some of your questions verbally. Use the Q&A panel to continue asking your questions


A. Coca-Cola Bottling Company is preparing to use the Cisco Nexus 1000V Switch, which resides on the server to deliver VN-Link virtual machine-aware network services.

B. Coca-Cola Bottling Company plans on using The Cisco Nexus 1000V to simplify collaboration within the IT department by clearly separating responsibilities for the server group and network group.

C. Coca-Cola Bottling Company plans on using the Cisco Nexus 1000V Switch to enable vMotion to work properly by giving server specialists the freedom to move hosts around without concerning themselves with quality of service and security settings.

D. A and B only

E. A, B, and C

Cisco Nexus 1000 and Coca-Cola… What do they have in common?


Those who fill out the Evaluation

Survey will enter a raffle for the

chance to win:

$50 Amazon Gift Card

To complete the evaluation, please click on link

provided in the chat or in the pop-up once the

event is closed.


If you have additional questions, you can ask them to Louis. He will be answering from June 4 to June 14, 2013 https://supportforums.cisco.com/thread/2220674

You can watch the video or read the Q&A 5 business days after the event at https://supportforums.cisco.com/community/netpro/ask-the-expert/webcasts

https://supportforums.cisco.com/thread/2220674



https://supportforums.cisco.com/community/netpro/ask-the-expert/webcasts






English

Tuesday July 9, at 8:00 a.m. San Francisco (PST) 11:00 a.m. New York (EST) 5:00 p.m. Paris (CEST) 8:30 p.m. Bangalore (IST)

Join Cisco Experts: Amit Singh and Vijay Rao

During the live event, Cisco subject matter experts Amit Singh and Vijay Rao will focus on the simplified "Upgrade Process"& "Focussed Support" from Cisco to Migrate to version 9.1. They would also talk about the changes made to the Licensing model of UCL/CUWL.

Registration opens on June 10 @

https://supportforums.cisco.com/community/netpro/expert-corner#view=webcasts

Topic: Upgrading Cisco Unified Communications Manager

(CUCM) to Version 9.1 (Drive to 9)

https://supportforums.cisco.com/community/netpro/expert-corner





Spanish

Tuesday June 12, at

7:00 a.m. San Francisco (PST)

9:00 a.m. Mexico City (CST)

10:00 a.m. New York (EST)

4:00 p.m. Paris & Madrid (CEST)

Join Cisco Expert: Hector Carranza

During this live event, expert Hector Carranza will give an introduction to Multiprotocol Label Switching (MPLS) and explain how MPLS combines the intelligence of routing protocols with the performance offered by the technologies Layer 2 in order to provide high-capacity services over IP networks. Carranza will also discuss the benefits of MPLS compared to those provided by other technologies used before and will describe scalability and configuration basics necessary to implement MPLS.

Register @


Topic: Introduction to Multiprotocol Label Switching

(MPLS): Uses and Benefits





Portuguese

Tuesday June 18 at

7:00 a.m. San Francisco (PST)

10:00 a.m. New York (EST)

11:00 a.m. Brasilia City

3:00 p.m. Lisbon and London

4:00 p.m. Paris & Madrid (CEST)

Join Cisco Expert: Marcio Teixaira Ferreira

During this live event, you'll learn basic concepts and fundamentals of Border Gateway Protocol (BGP) with Cisco expert Marcio Teixeria Ferreira. He will cover important topics such as when and why to use BGP, common configuration scenarios, and how to troubleshoot common issues.

Register @


Topic: Border Gateway Protocol (BGP): Fundamentals,

Configuration, and Troubleshooting





Russian

Wednesday June 19, at

9:00 a.m. Paris (CEST)

11:00 a.m. Moscow

Join Cisco Expert: Mike Shchekotilov

During this session Cisco subject-matter expert Mike Shchekotilov will talk about certificates and secure integration of Cisco Unified Communications Manager, Cisco TelePresence Video Communication Server, and Cisco TelePresence Content Server. He will then provide a live demo of implementing certificates on the servers using Microsoft Active Directory as certificate authority.

Register @


Topic: Secure Communication and Certificates in Cisco

Unified Communications Manager and

Cisco TelePresence






English Jabber for Windows 9.2 - Configuration and Features

With Cisco expert Maqsood Mushtaq

Learn and ask questions about how to install, configure, and troubleshoot Cisco

Jabber for Windows 9.2

Ends June 14, 2013

Cisco Unified Wireless and Cisco Unified Access

With Cisco experts Richard Hamby, Patrick Croak, and Nicholas Tate

Learn and ask questions about the Cisco Wireless portfolio of controllers, access

points, and latest WLAN features.

Ends June 14, 2013

Topic: Wireless LAN Controllers

With Cisco expert Nicolas Darchis

Learn and ask questions about how to configure and troubleshoot Cisco Wireless

LAN Controllers (WLC)

Starts June 17, 2013

Topic: How to Configure and Troubleshoot Open Shortest Path First (OSPF)

With Cisco expert Vignesh Rajendran

Learn and ask questions about how to configure and troubleshoot OSPF


Topic: Installing & Configuring Cisco Prime Collaboration 9.0

With Cisco experts Aashish Jolly and Abhijit Singh Anand

Learn about install best practices for Cisco Prime Collaboration 9.0 covering the

different deployment models available.


Join the discussion for these Ask The Expert Events at:

https://supportforums.cisco.com/community/netpro/expert-corner#view=ask-the-experts









• Cisco Live offers unparalleled opportunities to increase your knowledge of Cisco products and solutions. Educational content is spread across four programs:

Technical Education

IT Management

Developer Network Program

Service Provider

• The week also includes a full slate of Innovation Sessions, Keynotes, Super Sessions, and multiple opportunities to meet one-on-one with Cisco experts.

• We will be in the World of Solutions in Services area located in front of Data Center.

• More information: https://supportforums.cisco.com/community/netpro/idea-center/cisco-live-orlando-2013

https://supportforums.cisco.com/community/netpro/idea-center/cisco-live-orlando-2013












If you speak Spanish, Portuguese, Japanese, Polish or Russian,

we invite you to ask your questions and collaborate in your

language:

• Spanish https://supportforums.cisco.com/community/spanish

• Portuguese https://supportforums.cisco.com/community/portuguese

• Japanese https://supportforums.cisco.com/community/csc-japan

• Polish https://supportforums.cisco.com/community/etc/netpro-polska

• Russian https://supportforums.cisco.com/community/russian

https://supportforums.cisco.com/community/spanish

https://supportforums.cisco.com/community/portuguese

https://supportforums.cisco.com/community/csc-japan



https://supportforums.cisco.com/community/etc/netpro-polska



https://supportforums.cisco.com/community/russian


https://supportforms.cisco.com

http://bit.ly/facebookcsc

http://bit.ly/twittercsc

http://bit.ly/youtubecsc

http://bit.ly/googlecsc

http://bit.ly/linkedincsc

Newsletter Subscription: http://bit.ly/newscsc

http://bit.ly/itunescsc

http://bit.ly/androidcsc

https://supportforms.cisco.com/


A. Coca-Cola Bottling Company is preparing to use the Cisco Nexus 1000V Switch, which resides on the server to deliver VN-Link virtual machine-aware network services.

B. Coca-Cola Bottling Company plans on using The Cisco Nexus 1000V to simplify collaboration within the IT department by clearly separating responsibilities for the server group and network group.

C. Coca-Cola Bottling Company plans on using the Cisco Nexus 1000V Switch to enable vMotion to work properly by giving server specialists the freedom to move hosts around without concerning themselves with quality of service and security settings.

D. A and B only

E. A, B, and C

Cisco Nexus 1000 and Coca-Cola… What do they have in common?

Thank You for Your Time

Please Take a Moment to Complete the Evaluation

Thank you.