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#<br />

Changing the VSM H<strong>os</strong>tname<br />

Example 9-7 shows how to change the Nexus 1000V VSM h<strong>os</strong>tname.<br />

Example 9-7. Changing the Nexus 1000V VSM H<strong>os</strong>tname<br />

Click here to view code image<br />

Change Nexus 1000V H<strong>os</strong>tname<br />

switch# conf t<br />

switch(config)# h<strong>os</strong>tname vsmvsm<br />

vsmvsm(config)# exit<br />

vsmvsm#<br />

Layer 3 Control<br />

The Nexus 1000V software release 4.0(4)SV1(2) adds the capability for Layer 3 Control<br />

between the VEMs <strong>and</strong> VSM; Layer 3 Control no longer requires the Control <strong>and</strong> Packet<br />

VLANs. Layer 3 Control capability offers the following capabilities <strong>and</strong> requirements:<br />

• The transport mode for the VSM domain can be configured for Layer 3.<br />

• The VEM VM kernel NIC must connect to the Layer 3 control port profile when<br />

adding the h<strong>os</strong>t to the Cisco Nexus 1000V DVS.<br />

• Only one VM kernel NIC can be assigned to the Layer 3 Control port-profile per h<strong>os</strong>t.<br />

• The VLAN assigned to the Layer 3 Control port profile must be a system VLAN.<br />

• The port-profile must be an access port profile; it cannot be a trunk port profile.<br />

• Different h<strong>os</strong>ts can use different VLANs for Layer 3 Control.<br />

Figure 9-41 shows the Cisco Nexus 1000V Series Architecture for L3 Control:

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

Saved successfully!

Ooh no, something went wrong!