Nexus 1010 no vsb present

Hi
I have a customer with a pair of Nexus 1010s that they have been testing. After lots of rebooting and pulling of cables etc as they test redundancy things have gone pear shaped. Now the VSBs seem to have disappeared.
Show module says VSB not present on the primary and the secondary.
Show running config has a section like this:
virtual-service-blade NAME1-1010
virtual-service-blade-type name VSM-1.0
etc
I dont see anywhere in the config a line like
virtual-service-blade-type new iso-file
Does the above line show up in a show run ?
Also where are the ISO files stored as a show boot doesnt show them, tehre are some bin files but no .iso files.
Thanks
Regards
Pat

Seems like you are bringing up the setup for first time.
Initially when you bring up Nexus1010, there will not be any VSB present. They need to be deployed using
VSB enable cli.
The running confiig that you are looking seems okie. Looks like you just associated a template with VSB.
You need to proceed further deploy VSB. Please refer to docs for the same.
"new" doesnt appear in running config. It translates to "name" which is template name that iso-file contained.
ISO files are present in bootflash:repository/ folder. If they are not there for some reason, you can download latest releases from CCO link for N1k and NAM.

Similar Messages

Installing DCNM-SAN as a VSB in Nexus 1010

Hi everyone,
I'm trying to install DCNM-SAN as a VSB in Nexus 1010, as I've read on the release notes that since 5.2.x release the distribution is done via a single image and there's an image available right now for 5.2(2)...
But, although I've tried numerous times (together with reading a lot through the two available documents - Installation and licensing guide and Fundamentals), every time I create a new vsb with these images, it becomes a DCNM-LAN install.
I have yet to have any prior experience with DCNM, so I might be missing something.
Any ideas? What am I missing? Am I trying to do something that is not supported? Or, am I just missing a critical point there?
NOTE: This is currently a lab topology, but I have a customer that's very keen on using DCNM-SAN with their MDS switches. And I feel that having this on a the 1010 as a vsb is the best way to do it, if it can be done, with regards to having network staff not deal with servers etc.
Thanks,
Emre

Andrew,
We are a little frustrated with the VSB version of DCNM-SAN, it does not appear possible to manage fabric without advanced licensing for the switches, in the licensing guides for DCNM it lists essentials capability that should include port, switch, and fabric-level configuration. On the windows version we can manage the fabric unlicensed as long as we do it from the server direcly or in previous versions if we are running stand alone. These options do not appear to exist for the VSB version. Is there any plan to include any essentials capability in the VSB/OVF versions of the DCNM-SAN. If this is not planned, the documentation should be changed to state that essentials functions are only available in the Windows version.

DCNM-SAN as Nexus 1010 VSB

Does anybody know if (and when) DCNM-SAN will be available as a Nexus 1010 VSB, as it is with DCNM-LAN now?
PS: Here is my previous question on how (as I wrongly assumed it was possible, looking at the documentation), which was answered by Padma (a generous and kind Cisco employee).
Thanks,
Emre

Hi Andrew,
Great news, thanks... Looking forward for the release

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

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 + 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.

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 can not erase export-import folder

Hi Expert,
After we import the backup vsb. We try to erase the export-import folder. But system show "Device or resource busy". So we can not execute more export or import command. Please reference the below image and help us to fix this issue.
Ps. The Nexus 1010 version is "4.2.1.SP1.4"

Hello Meng,
I was able to recreate this problem in the lab. It appears it only occurs when importing a secondary VSB. A 'system switchover' of the N1010s frees the NFS locks. Not an ideal workaround, but a workaround.
CSCtz44247 has been opened for this problem.
Matthew

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 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

Nexus 1010, out of band

We are installing Nexus 1010 using the topology 3 connection and we will configure VSB DCNM.
1st Question
Topology 3, use the interfaces 1 and 2 for traffic management vlan and I want to know if I can connect these interfaces to my segment from out of band or needs to go connected on the segment from server.
2nd Question
we are going to configure DCNM on Nexus 1010 which must have comunication with the management interfaces from the other nexus switch through of the network out of band. Management interfaces of VSMS should be on the same network OOB? or must be on another network?
Thanks in advance

Hi,
Yes, it is possible. When you login as admin and you want to get to another vdc, you just use this command:
switchto vdc
This will take to the that vdc. If you want to switch back to the admin vdc, you just type "switchback"
HTH

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 - 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 weird HA mechanism

Hello guys,
We are in the middle of the installation of 2 Nexus 1010 appliances.
the two appliances have a failover mechanism where you have only one address for the cluster of appliance. I don't think that it is a good idea because the Vsm on the appliance already has its own HA mechanism. on the contrary, the appliance HA mechanism is confusing because you can only access by telnet the primary appliance. What if your active VSM is running on the secondary appliance? how to access Out of band to this one?
It would make more sense to me if each appliance 1010 would be standalone?
am I missing something here? any ideas on why we use Ha for the Nexus 1010?
Thank you
laurent
Sent from Cisco Technical Support iPad App

First of all. According to the documentation Nexus 1010 is not supported in standalone scenario.
• The HA standalone role is not supported for the Cisco Nexus 1010.
• Cisco Nexus 1010 is not supported in the non HA mode.
http://www.cisco.com/en/US/partner/docs/switches/datacenter/nexus1000/sw/4_2_1_s_p_1_4_a/install_upgrade/guide/n1010_installupgrade_install.html#wp1065391
I see the HA mechanism between N1010 as a way how to manage them. Nothing more, nothing less. N1000V on top of them do have their HA mechanism. I am able to reach standby N1010 VSM either by:
ssh to the LOM port of the standby N1010, then connect host and then login virtual-service-blade or
ssh to the N1010 cluster address and then login virtual-service-blade secondary
Petr
Message was edited by: Petr Mojzisek

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 no vsb present

Similar Messages

Maybe you are looking for