Nexus 1010 + 1000v control vlan issue

Hi,
I have Nexus 1000v installed on nexus 1010. The nexus 1010 is in cluster and working fine. I have made network uplink option 3.
My VSM is configured to be on L3 mode. Hence I set control and packet vlan to 1 (on vsm). while creating the VSB too I have choosen control and packet vlan to be 1 (keeping in mind my mode will be L3).
Now The vsm is not coming up in HA. The redandancy log says degraded mode is true.
Is it because, the control packet coming from VSM after reaching the N1010, the packets are getting tagged with vlan 1. Since I have not set any native vlan on 1010, might be control vlan 1 is also tagged one. Is it this the case ?
help needed on this issue.
regards
Prasad K

Control vlan is a totally seperate VLAN then your System Console. The VLAN just needs to be available to the ESX host through the upstream physical switch and then make sure the VLAN is passed on the uplink port-profile that you assign the ESX host to.
We only need an interface on the ESX host if you decide to use L3 control. In that instance you would create or use an existing VMK interface on the ESX host.

Similar Messages

Nexus 1000v: Control VLAN must be same VLAN as ESX hosts?

Hello,
I'm trying to install nexus 1000v and came across the below prerequisite.
The below release notes for Nexus 1000v states
VMware and Host Prerequisites
The VSM VM control interface must be on the same Layer 2 VLAN as the ESX 4.0 host that it manages. If you configure Layer 3, then you do not have this restriction. In each case however, the two VSMs must run in the same IP subnet.
What I'm trying to do is to create 2 VLANs - one for management and the other for control & Data (as per latest deployment guide, we can put control & data in the same vlan).
However, I wanted to have all ESX host management same VLAN as the VSM management as well as the vCenter Management. Essentially, creating a management network.
However, from the above "VMWare and Host Prerequisites", does this means I cannot do this?
I need to have the ESX host management same VLAN as the control VLAN?
This means that my ESX host will reside in a different VLAN than my management subnet?
Thanks...

Control vlan is a totally seperate VLAN then your System Console. The VLAN just needs to be available to the ESX host through the upstream physical switch and then make sure the VLAN is passed on the uplink port-profile that you assign the ESX host to.
We only need an interface on the ESX host if you decide to use L3 control. In that instance you would create or use an existing VMK interface on the ESX host.

Nexus 1010/1000v L3 Mode Through ASA

Hi,
A question regarding the subject line. When deoploying redundant Nexus 1010 hardware appliances (VSM's) on the "inside" and Nexus 1000v's on your ESX hosts in the "DMZ" in Layer 3 mode which is seperated by an ASA, what VLAN's are actually need? Both from the inside and DMZ perspective. Specifically, do you actually need Control and Data/Packet VLAN's configured when using L3 mode. When you configure the SVS domin for L3 Transport you explicitly negate both Control and Data/Packet VLAN's?
Also, when configuring the 1000v in L3 mode is it best practice to have the system vlan the same as your management vlan, and also use the same vlan for the Vmkernal NIC. When setting up the Vmkernal NIC on the ESX host the only option available was to use the management vlan.

Hello Aaron,
The Nexus 1010s only communicate in L2 mode so you'll still need control, management & packet vlans between the two appliances. VSMs deployed in L3 mode collapse the control & packet vlans into the management network. Traffic between the VSM and ESX host will be tunneled over IP. Therefore you need to ensure IP connectivity between the VSM mgmt0 interface and the ESX host management vmk.
Yes, you will want to define the ESX vmk vlan as a system vlan on BOTH the vethernet & ethernet port-profiles.
Matthew

Nexus 1000V private-vlan issue

Hello
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:Standardowy;
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-parent:"";
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin:0cm;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:10.0pt;
font-family:"Times New Roman";
mso-ansi-language:#0400;
mso-fareast-language:#0400;
mso-bidi-language:#0400;}
I need to transmit both the private-vlans (as promiscous trunk) and regular vlans on the trunk port between the Nexus 1000V and the physical switch. Do you know how to properly configure the uplink port to accomplish that ?
Thank you in advance
Lucas

Control vlan is a totally seperate VLAN then your System Console. The VLAN just needs to be available to the ESX host through the upstream physical switch and then make sure the VLAN is passed on the uplink port-profile that you assign the ESX host to.
We only need an interface on the ESX host if you decide to use L3 control. In that instance you would create or use an existing VMK interface on the ESX host.

How to change Nexus 1010 and Nexus 1000v IP address

Hi Experts,
We had run two VSM and one NAM in the Nexus 1010. The Nexus 1010 version is 4.2.1.SP1.4. And the Nexus 1000v version is 4.0.4.SV1.3c. Now we must to change management IP address to the other one. Where can I find the SOP or config sample? And have anything I must to remind?

If it's only the mgmt0 IP address that you are changing, then you can just enter the new address under the mgmt0 interface. It will automatically sync with the VC.
I guess you are trying to change the IP address of the VC plus the management VLAN as well. One way of doing this is:
- From the Nexus 1000v, disconnect the connection to the VC (svs connection -> no connect)
- Change the VC IP address and connect to it (svs connection -> remote ip address)
- Change the Nexus 1000v mgmt0 address
- Change the mgmt VLAN on the N1010
- Change the mgmt address of the N1010
- Reconnect the Nexus 1000v back to the VC (svs connection -> connect)
Correspondingly, change the VLAN configuration on the upstream switch plus the connection to the VC as well.
Thanks,
Shankar

Nexus 1010 - Issue copying s/w onto device using SCP.

Hi
I'm trying to copy the new version of s/w ( nexus-1000v.4.2.1.SV1.4.iso) onto a Nexus 1010 switch using the command:
copy scp: bootflash:repository
The software starts to copy but unfortunately only gets to around 10% complete before failing. It's almost like it's getting stuck for some reason?
The file is quite large (163Mb), however, there is plenty of space on the disk (see below) so I cannot understand while this is happening.
switch# dir bootflash:repository
      16384     Nov 05 17:48:52 2010 lost+found/
156403712     Nov 05 17:52:02 2010 nam-4-2-1.iso
133965824     Nov 05 17:53:02 2010 nexus-1000v.4.0.4.SV1.3b.iso
Usage for bootflash://sup-local
305950720 bytes used
3685429248 bytes free
3991379968 bytes total
Does anyone have any suggestions as to why this is happening? Below is the exact output from the box:
switch# copy scp: bootflash:repository
Enter source filename: nexus-1000v.4.2.1.SV1.4.iso
Enter vrf (If no input, current vrf 'default' is considered):
Enter hostname for the scp server: 10.214.30.56
Enter username: 00000001
[email protected]'s
password:
nexus-1000v.4.2.1.SV1.4.iso                     9%   15MB   0.0KB/s - stalled -Read from remote host 10.214.30.56: Connection reset by peer
lost connection

Hi guys,
Any ideas on this?

Nexus 1010 HA Active with warm standby

I have deployed two 1010 appliances, the upstream switches are two 6509 wihtout VSS.
I cannot get the HA up.
Output of show module is:
Mod Ports Module-Type                       Model               Status
1    0      Nexus 1010 (Virtual Services App Nexus1010           active *
2    0      Virtual Supervisor Module                             powered-up
Mod Sw                Hw
1    4.2(1)SP1(3)      0.0
Mod MAC-Address(es)                         Serial-Num
1    00-19-07-6c-5a-a8 to 00-19-07-6c-62-a8 NA
Mod Server-IP        Server-UUID                           Server-Name
1    10.146.102.10    NA                                    NA
Output of show system redundancy status is :
Redundancy role
      administrative:   primary
         operational:   primary
Redundancy mode
      administrative:   HA
         operational:   None
This supervisor (sup-1)
    Redundancy state:   Active
    Supervisor state:   Active
      Internal state:   Active with warm standby
Other supervisor (sup-2)
    Redundancy state:   Standby
Error in getting supervisor and internal state of other supervisor.
and the output of show system internal redundancy info is:
My CP:
slot: 0
domain: 25
role:   primary
status: RDN_ST_AC
state: RDN_DRV_ST_AC_SB
intr:   enabled
power_off_reqs: 0
reset_reqs:     9
Other CP:
slot: 1
status: RDN_ST_SB
active: true
ver_rcvd: true
degraded_mode: true
Redun Device 0:
name: ha0
pdev: f37e8640
alarm: true
mac: ff:ff:ff:ff:ff:ff
tx_set_ver_req_pkts:   319
tx_set_ver_rsp_pkts:   0
tx_heartbeat_req_pkts: 61193
tx_heartbeat_rsp_pkts: 0
rx_set_ver_req_pkts:   0
rx_set_ver_rsp_pkts:   0
rx_heartbeat_req_pkts: 0
rx_heartbeat_rsp_pkts: 0
rx_drops_wrong_domain: 0
rx_drops_wrong_slot:   0
rx_drops_short_pkt:    0
rx_drops_queue_full:   0
rx_drops_inactive_cp: 0
rx_drops_bad_src:      0
rx_drops_not_ready:    0
rx_drops_wrong_ver:    0
rx_unknown_pkts:       0
Redun Device 1:
name: ha1
pdev: f37e8240
alarm: false
mac: 00:02:3d:70:19:81
tx_set_ver_req_pkts:   314
tx_set_ver_rsp_pkts:   0
tx_heartbeat_req_pkts: 61193
tx_heartbeat_rsp_pkts: 0
rx_set_ver_req_pkts:   0
rx_set_ver_rsp_pkts:   5
rx_heartbeat_req_pkts: 0
rx_heartbeat_rsp_pkts: 61165
rx_drops_wrong_domain: 0
rx_drops_wrong_slot:   0
rx_drops_short_pkt:    0
rx_drops_queue_full:   0
rx_drops_inactive_cp: 0
rx_drops_bad_src:      0
rx_drops_not_ready:    0
rx_drops_wrong_ver:    0
rx_unknown_pkts:       0
Can anyone please help in resolving this issue.
Regards,
Sabih

Hi Sabih,
For a Nexus 1010 pair to form HA redundancy, the communicate with each other via the Control VLAN. You would have specified this during your installation.
Can you verify that they are both utilizing the same Control VLAN.
n1010# show svs domain
Furthermore, ensure that this vlan is defined and forwarding, on the relevant ports, on the upstream 6509s.
Thanks,
Michael

Nexus 1010 HA

Hello
I have a problem with Nexus 1010 HA.
I have two Nexus 1010. One is configured as Primary and the other as Secondary.
I have a VSB (VSM type) created on both, enabled as Primary and Secondary respectively.
HA between VSMs works fine. But HA between Nexus is not working. Something is missed. Any ideas? Thank you!!!
Nexus 1010 - Primary
NX-1010-TB# sh system red status
Redundancy role
      administrative:   primary
         operational:   primary
Redundancy mode
      administrative:   HA
         operational:   None
This supervisor (sup-1)
    Redundancy state:   Active
    Supervisor state:   Active
      Internal state:   Active with no standby
NX-1010-TB# sh mo
Mod Ports Module-Type                       Model               Status
1    0      Cisco Nexus1010 Chassis           Nexus1010           active *
Mod Sw                Hw
1    4.2(1)SP1(2)      0.0
Mod MAC-Address(es)                         Serial-Num
1    00-19-07-6c-5a-a8 to 00-19-07-6c-62-a8 NA
Mod Server-IP        Server-UUID                           Server-Name
1    10.1.30.53       NA                                    NA
Nexus 1010 - Secondary
switch# sh sys red st
Redundancy role
      administrative:   secondary
         operational:   secondary
Redundancy mode
      administrative:   HA
         operational:   None
This supervisor (sup-2)
    Redundancy state:   Active
    Supervisor state:   Active
      Internal state:   Active with no standby
Other supervisor (sup-1)
    Redundancy state:   Not present
switch# sh module
Mod Ports Module-Type                       Model               Status
2    0      Cisco Nexus1010 Chassis           Nexus1010           active *
Mod Sw                Hw
2    4.2(1)SP1(2)      0.0
Mod MAC-Address(es)                         Serial-Num
2    00-19-07-6c-5a-a8 to 00-19-07-6c-62-a8 NA
Mod Server-IP        Server-UUID                           Server-Name
2    0.0.0.0          NA                                    NA
* this terminal session

Prasad,
This means that there is some sort of a communication issue between the two Nexus 1010 switches in the control VLAN. You should probably check the upstream configuration on the ports that connect to the 1010 links carrying the control traffic and also the links involved in the control path.
Thanks,
Shankar

Nexus 1010 HA Error

              Hi,
While I bring Up Secondary Nexus 1010 I am getting this error on primary
Error in getting supervisor and internal state of other supervisor.
sh redundancy status
Redundancy role
      administrative:   primary
         operational:   primary
Redundancy mode
      administrative:   HA
         operational:   None
This supervisor (sup-1)
    Redundancy state:   Active
    Supervisor state:   Active
      Internal state:   Active with warm standby
Other supervisor (sup-2)
    Redundancy state:   Standby
Error in getting supervisor and internal state of other supervisor.
On the redundant (standy ) unit I am getting this message
%SYSLOG-2-SYSTEM_MSG: Did not receive supstate notification in 180 seconds. Still waiting
What could be possible reason ? can this be a firmware mismatch ? Both are having same configuration for management control and packet vlan. Both are on same L2 network. If I disconnect the standby unit management cable, it will boot. But if management cable is connected, it will be stuck in the above phase.
regards
Prasad K

Prasad,
This means that there is some sort of a communication issue between the two Nexus 1010 switches in the control VLAN. You should probably check the upstream configuration on the ports that connect to the 1010 links carrying the control traffic and also the links involved in the control path.
Thanks,
Shankar

Nexus 1010 and Management

it is the first time that i install and configure a Nexus 1010.
After unpackaging, i have upgrade the BIOS, CMC and Firmware of the nexus 1010 (like a classical C-serie server)
The CIMC 's @IP is 10.10.0.100 ; I have connected the 10/100 Ethernet CIMC management port to my OOB network where we have all OOB interfaces from Nx7k and Nx5k.
Now i would want configure the Nx1010 in the topology "uplink type 3".
port 1 and 2 : mangement Vlan
port 3 to 6 : Control/packt Vlan and Data Vlan.
In the setup wizard, we have to configure the int Mgmt0 of Nx 1010.
In which network must be the Mgmt0 ; i am confused and mix up :
- CIMC mgmt from the C-series server
- mgmt0 int from nexus 1010 : by which physical interface goes throught this traffic : via "10/100 Ethernet CIMC management port" or via "Management vlan" ???
- Vlan management : this Vlan will allow to manager the VSB VSM-1 et VSM-2....
The Vlan management must not be the OOB network, must it ?
It is not clear for my mind ; i mix up all this mgmt
please help me !!!
many thank in advance.
NB : All the devices in our DC (Nx5k and Nx5K/Nx2K) have two management interface :
1 - OOB management via the pysical OOB port
2 - Inb management via a dedicated Vlan ; each device have 1 @IP in this Vlan (even the L2 Nx7k (without M1 card) via the cli "management")
How could i have the these mgmt for Nexus 1010 / CIMC / VSM ???
Last question : in order to upgrade the nx 1010, then download the nexus-1000v*.iso to bootflash:repository, which network/mgmt i have to used ???

Hi Delahais, could you resolve your concern? .. I have the same doubt

Nexus 1010 - No MGMT0 Access?

Hi all, I hope someone here can help!
I am setting up a Cisco Nexus 1010 appliance, but cannot access it through the MGMT0 interface!
What I am trying to do is copy over the 1000V .iso file to install a vsm, but I can not even ping the mgmt0 interface.
I have booted from the 4.2(1)SP1(3) iso, ran through the initial setup where I set the uplink type, domain id, vlan id and mgmt0 ip details.
Current config and sh tech attached
Let me know what other information I should post!
Kind regards, Ash.

Hi everyone,
I have a problem, similar to Ashley's in regards to reachability of N1010 in my lab...
I'm using network-uplink type 1 as it would be more than enough for my lab deployment. I have configured the CIMC and can reach/configure the device from there pretty easily. But, no matter how I try, I can't seem to get management access.
The N1010 is connected via it's Lom0 port to a Catalyst (at Fa0/10), which is configured as a trunk port. I'm using Vlan10 for all purposes...
The uplink switch has a configuration like this:
interface VLAN10
ip address 10.2.1.66 255.255.255.128
no ip directed-broadcast
no ip route-cache
interface FastEthernet0/10
description NEXUS_1010_TEST-LOM0
switchport trunk encapsulation dot1q
switchport trunk native vlan 10
switchport mode trunk
And the show running-config output from the Nexus1010 shows this:
!Command: show running-config
!Time: Tue Jun 5 21:21:59 2012
version 4.2(1)SP1(4)
no feature telnet
username admin password 5 $1$GW2TtGHE$oHUMu5em2..2XvSqJDlMb. role network-admin
banner motd #Nexus 1010#
ip domain-lookup
ip domain-lookup
switchname N1010-ANK
snmp-server user admin network-admin auth md5 0xbc6feda9b778b02e324d11adda844e5c
priv 0xbc6feda9b778b02e324d11adda844e5c localizedkey
vrf context management
ip route 0.0.0.0/0 10.2.1.126
vlan 1,10
port-channel load-balance ethernet source-mac
port-profile default max-ports 32
vdc N1010-ANK id 1
limit-resource vlan minimum 16 maximum 2049
limit-resource monitor-session minimum 0 maximum 2
limit-resource vrf minimum 16 maximum 8192
limit-resource port-channel minimum 0 maximum 768
limit-resource u4route-mem minimum 32 maximum 32
limit-resource u6route-mem minimum 16 maximum 16
limit-resource m4route-mem minimum 58 maximum 58
limit-resource m6route-mem minimum 8 maximum 8
network-uplink type 1
interface GigabitEthernet1
interface GigabitEthernet2
interface GigabitEthernet3
interface GigabitEthernet4
interface GigabitEthernet5
interface GigabitEthernet6
interface PortChannel1
interface mgmt0
ip address 10.2.1.40/25
interface control0
line console
boot kickstart bootflash:/nexus-1010-kickstart-mz.4.2.1.SP1.4.bin
boot system bootflash:/nexus-1010-mz.4.2.1.SP1.4.bin
boot kickstart bootflash:/nexus-1010-kickstart-mz.4.2.1.SP1.4.bin
boot system bootflash:/nexus-1010-mz.4.2.1.SP1.4.bin
svs-domain
domain id 200
control vlan 10
management vlan 10
svs mode L2
vnm-policy-agent
registration-ip 0.0.0.0
shared-secret **********
log-level info
In no way I can access the mgmt0 interface IP from the network, or vice-versa.
The weird part is, I can see the Nexus in CDP neighbours, and I also can see the mac address of the mgmt0 interface on the switch (along with a correct IP assignment in arp table).
DemoSW#sh cdp nei
Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge
                  S - Switch, H - Host, I - IGMP, r - Repeater
Device ID        Local Intrfce     Holdtme    Capability Platform Port ID
N1010-ANK(1157310Fas 0/10           126         S I       Nexus1010 control0
N1010-ANK(1157310Fas 0/10           126         S I       Nexus1010 mgmt0
N1010-ANK(QCI1614Fas 0/10           126          H        Nexus1010 eth0
DemoSW#
DemoSW#sh mac-address-table interface fa0/10
Non-static Address Table:
Destination Address Address Type VLAN Destination Port
0002.3d70.c800       Dynamic         10 FastEthernet0/10
0002.3d70.c801       Dynamic         10 FastEthernet0/10
0010.18cf.7886       Dynamic         10 FastEthernet0/10
36ce.bc88.c2d9       Dynamic         10 FastEthernet0/10
DemoSW#sh arp | incl 0002.3d70.c801
Internet 10.2.1.40               0   0002.3d70.c801 ARPA   VLAN10
DemoSW#ping 10.2.1.40
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.2.1.40, timeout is 2 seconds:
Success rate is 0 percent (0/5)
DemoSW#
Any ideas???

Nexus 1010 Telnet

Dear Friends,
I have setup a single nexus 1010. I have done the following
Assigned device role as primary
Assigned Mgmt 0 IP address
Assigned subnet mask
Assigned control, management vlan. Assigned Domain ID
Selected Option 1 for network topology
Enabled telnet & SSH
Now, When I try to ping or telnet to the management IP address by connecting by LAPTOP to Interface 1 (GigabitEthernet1), there is no response ?
What is the reason ?.
Basically How to do a telnet or SSH to a nexus 1010 mgmt 0 interface ? I am not using CIMC interface.
regards
Prasad

Ok. That trigged me even a more fundamental question. My undestanding is that three are total 7 ports on N1010.
2 LoM fixed port 10/100/1000
4 PCI port
1 CIMC port (the one port kept near to USB slots)
Mgmt 0 can only use the LoM interfaces (G1andG2) for sending traffic.... LoM is not separate port other than the 1-6 interface as per below link
http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9902/white_paper_c07-603623.html
The Cisco Nexus 1010 has six 1 Gigabit Ethernet interfaces available for network connectivity: two 1 Gigabit Ethernet LAN-on-motherboard (LOM) interfaces and four 1 Gigabit Ethernet interfaces, available through a PCI card "
I will update with my observation tommorow. Then I will come back with 1000v and DNM VSB integration quires

No export command in Nexus 1010

Hi all,
We want to do a backup of a virtual-service-blade in a Nexus 1010. The document we are following is:
http://www.cisco.com/en/US/docs/switches/datacenter/nexus1000/sw/4_2_1_s_p_1_3/software/configuration/guide/n1010_vsvcs_cfg_7backup.html
What we are supposed to do fron this document is to create a file named export-import, to shutdown the primary o secondary virtual service blades, and after it, to execute the command "export primary" o "export secondary", depending on which vsb we want to export.
========= DETAILED STEP IN THE DOCUMENT ================
n1010-1(config-vsb-config)# export secondary
Note: export started..
Note: please be patient..
Note: please be patient..
Note: please be patient..
Note: export completed...n1010-1(config-vsb-config)#
====================================================
The problem is that this "export" command is not available in our nexus 1010.
=========== NEXUS 1010 ===============================
N1010-MGMT(config-vsb-config)# export secondary
                                 ^
% Invalid command at '^' marker.
N1010-MGMT(config-vsb-config)#
N1010-MGMT(config-vsb-config)#
N1010-MGMT(config-vsb-config)# ?
description                 Virtual service blade description
disksize                    Configure disk size
enable                      Deploy/remove the virtual service blade
interface                   Configure virtual service blade interface vlan
no                          Negate a command or set its defaults
numcpu                      Configure numcpu
ramsize                     Configure ram size
shutdown                    Start/stop the virtual service blade
virtual-service-blade-type Select the virtual service blade type
end                         Go to exec mode
exit                        Exit from command interpreter
pop                         Pop mode from stack or restore from name
push                        Push current mode to stack or save it under name
where                       Shows the cli context you are in
=====================================================
The version of the nexus is the same than the document's one.
Document: 4.2(1)SP1(3) ==> Nexus 1010: version 4.2(1)SP1(2)
Software
loader:    version unavailable [last: loader version not available]
kickstart: version 4.2(1)SP1(2)
system:    version 4.2(1)SP1(2)
kickstart image file is: bootflash:/nexus-1010-kickstart-mz.4.2.1.SP1.2.bin
kickstart compile time: 1/27/2011 14:00:00 [01/28/2011 01:14:35]
system image file is:    bootflash:/nexus-1010-mz.4.2.1.SP1.2.bin
system compile time:     1/27/2011 14:00:00 [01/28/2011 04:13:25]
Hardware
cisco Nexus 1010 Chassis ("Cisco Nexus1010 Chassis")
   with 14665728 kB of memory.
Processor Board ID T023D700201
We don't know which can be the problem, wheter it can be a bug in the software, or we are doing something wrong.
Thank you

The export command was a new feature added in the 4.2(1)SP1(3) version of code. Your 1010 is one rev lower.
You'll need to upgrade the code on the 1010 to the latest code to get the export command.
The upgrade is pretty straight forward. Just download the code and follow the upgrade guide.
louis

Nexus 1010 Deployment Process

Hi,
Initially we deployed VSM on a VM and that was working fine. Now the customer has bought a 1010 appliance and wants us to configure VSMs on the 1010 appliance.
I just want to confirm that the steps that I can up with after going through cisco documents is the right approach.
1) Boot up 1010 appliance complete the intial configuration i.e.
     a) setup admin password and uplink type
     b) set control vlan id, domain id, mgmt id
     c) set the mgmt0 address
     d) configure the rest of the settings
2) Boot up 1010 secondary appliance and set the domain id and control vlan id and mgmt id.
After this I will be able to see the active and primary chassis in sh module.
after the initail configuration can the chasis be used as a VSM and can I directly configure port-profiles and deploy vem ?
Or do i need to install VSM as a VSB and then configure port-profiles and deploy vem?
And when I deploy VSM as a Virtual services blade i need to share the management network, what else should be taken care of ?
Regards,
Sabih

Hello Sabih,
The migration guides has exact steps for moving from a VSM on ESX environment to N1010. This process allows you to migrate the VSM w/o the need to reinstall / reconfigure on the N1010s.
http://www.cisco.com/en/US/docs/switches/datacenter/nexus1000/sw/4_2_1_s_p_1_3/software/configuration/guide/n1010_vsvcs_cfg_6migrate.html
The management, control, packet vlans need to be shared between the N1010/VSB & existing VSM for a successful migration.
Please let me know if you have any questions.
Matthew

Nexus 1010 Virtual Services Appliance and VN-Link Hardware

All,
We are deploying the Nexus 1010 Virtual Services Appliance for the purpose of using the Network Analysis Module (NAM). The 1010 hosts the VSM's necessary to deploy the 1000v switch in ESX. We would also like to use VN-Link in hardware whereby we "bypass" the virtual switch and use the 6120's for the switching. What I need to know is can the 1010 still analyze the network traffic using VN-Link hardware? VN-Link hardware doesn't appear to need a VSM so I am thinking the 1010 cannot monitor the traffic since there will be no 1000v to "attach" to. Can anyone shed some light on this?
Regards,
Ken

Ken
The NAM module present in the 1010 is not exclusive for Nexus1000v traffic.
Its there as part of an appliance which happens to be the VSM (1000v) and is configured on its own.
If you look at the Nexus1000v, the VSM (which is the 1010 and holds the NAM in this case) is *not* part of the VM data path.
It is looked up for initial virtual port (veth) instantiation but after that traffic doesn't go through it.
So to send VM data traffic to the NAM module for analysis, some other mechanism (like ERSPAN) is used to route data traffic from VM's to it.
The Nexus 1000v support ERSPAN.
Same logic applies that you have a NAM module somewhere else - the 1000v can send traffic to it via ERSPAN.
Looking at VN-link in hardware - It does have a VSM which is the FI itself.
The veth in this case is on the FI.
If the FI did support ERSPAN (which it doesn't currently) you could use the same NAM module or any other NAM module to send traffic to it.
So its not a limitation of VN-link in hw switching methodology vs 1000v switching, but the fact that the FI doesn't support an "export" mechanism yet.
Hope it help
Thanks
--Manish

Nexus 1010 + 1000v control vlan issue

Similar Messages

Maybe you are looking for