Change for L2 to L3 svs mode on an existing deployment

[jkuhne]

Hello,

We are currently running L2 svs mode in the lab and I would like to change to L3 mode with the specific configuration additons below.
(not worried about a dedicated control vlan at the moment since this is functional testing).

My question is, will there be any impact to moving to L3 svs mode?  I am expecting this change to only impact control traffic between the VSM and VEM.  We currently have mutliple networks/vlans trunked in on the uplink and I don't want to impact the switching behavior there.

Thanks in advance

Jay

// Current vmkernel interface

port-profile type vethernet 10.201.112.x

  vmware port-group

  switchport access vlan 794

  switchport mode access

  no shutdown

  system vlan 794

  max-ports 128

  state enabled

// Proposed addition

  capability l3control

  capability l3-vservice

// Current svs config

svs-domain

  domain id 4014

  control vlan 794

  packet vlan 794

  svs mode L2

// Proposed change

svs-domain

  svs mode L3 interface mgmt0

[manir]

Hi,

Yes you are right. Its only for how the VSM and VEM will communicate.

Addition to svs mode, the control vlan and packet vlan config in svs-domain should be removed using the commands "no control vlan" and "no packet vlan".

svs-domain

     no control vlan

     no packet vlan

     svs mode L3 interface mgmt0

Before making the svs-domain config change you will need to disconnect the svs connection to vCenter, make the changes and then re-connect it.
A detailed migration guide is availalble in the below link.

Cisco Nexus 1000V Installation and Upgrade Guide, Release 4.2(1)SV2(2.1x) Series  - Upgrading the Cisco Nexus 1000V  [Ci…

Also the capability l3-vservice is not mandatory unless you are using any vsg/vpath services.

Regards,
Manikanta