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.

capability vxlan: no<br />

capability l3-vn-service: no<br />

port-profile role: none<br />

port-binding: static<br />

vsm# copy running-config startup-config<br />

[########################################] 100<br />

vsm#<br />

Note<br />

In the previous example, if the optional VMware port-group uplink name comm<strong>and</strong><br />

was used in the port-profile configuration, the name parameter would specify the<br />

name that is displayed in the vCenter Server. If the comm<strong>and</strong> is not used, the portprofile<br />

name will be used.<br />

Adding the VEM to a ESX vSphere H<strong>os</strong>t<br />

The VEM provides the Cisco Nexus 1000V Series with network connectivity <strong>and</strong><br />

forwarding capabilities, <strong>and</strong> each VEM acts as an independent switch from a forwarding<br />

perspective. The VEM is tightly integrated with VMware ESX <strong>and</strong> is installed on each. To<br />

add the VEM within vCenter, browse to Inventory > Networking <strong>and</strong> select the Cisco<br />

Nexus 1000V switch. Right-click, <strong>and</strong> select Add H<strong>os</strong>t, as shown in Figure 9-34.<br />

Note<br />

VMware update manager was installed prior to this configure; the manual VEM<br />

installation will not be shown.

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

Saved successfully!

Ooh no, something went wrong!