22.05.2017 Views

nx.os.and.cisco.nexus.switching.2nd.edition.1587143046

Nexus Switching 2nd Edition

Nexus Switching 2nd Edition

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

vsm# show svs domain<br />

SVS domain config:<br />

Domain id: 989<br />

Control vlan: 102<br />

Packet vlan: 102<br />

L2/L3 Control mode: L2<br />

L3 control interface: NA<br />

Status: Config not pushed to VC.<br />

vsm#<br />

Note<br />

The configuration has not been pushed to virtual center as the status is “Config not<br />

pushed to VC,” so the configuration needs to be completed.<br />

Registering the Nexus 1000V Plug-In to VMware Virtual Center Management Application<br />

The VSM maintains a communication link to VMware vCenter Server. The communication<br />

link is used to maintain definitions <strong>and</strong> propagate port profiles to the VMware virtual center.<br />

The Cisco Nexus 1000V uses a VMware vCenter Server plug-in to properly display a<br />

representation of the Cisco Nexus 1000V. The Cisco Nexus 1000V plug-in is an XML file<br />

that is downloaded from the VSM’s management IP address using a web browser; the XML<br />

plug-in must be installed before the VSM can communicate to the VMware vCenter Server.<br />

A common question is, “What if the connection between the VSM <strong>and</strong> VMware virtual<br />

center goes down?” If the connection between the VSM <strong>and</strong> VMware vCenter Server is<br />

disrupted, changes made on the VSM will not be propagated to VMware Virtual Center; the<br />

VEMs will still continue to forward traffic on the data plane. The VSM ensures that any<br />

configuration changes have been made during this period of disruption; the changes will be<br />

propagated when the communication link is restored.<br />

1. Obtain the IP address/DNS information of the Virtual Center Server. The following<br />

example shows how to verify IP Address/DNS h<strong>os</strong>t information on the VMWare<br />

vCenter server:<br />

Click here to view code image<br />

C:\Documents <strong>and</strong> Settings\Administrator>ipconfig<br />

Windows IP Configuration<br />

Ethernet adapter vCenter Server:<br />

Connection-specific DNS Suffix . :<br />

IP Address. . . . . . . . . . . . : 10.86.182.234<br />

Subnet Mask . . . . . . . . . . . : 255.255.255.0<br />

Default Gateway . . . . . . . . . : 10.1.4.1<br />

2. Verify IP connectivity between the VMware virtual center management station <strong>and</strong> the<br />

Cisco 1000V, as demonstrated in the following example:

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!