Nexus 1010 and DCNM
All,
According to the Cisco Press release a couple of weeks ago:
"The Nexus 1010 provides an NX-OS based appliance platform for hosting virtual services. This platform now supports two additional services: the Cisco Virtual Security Gateway which provides VM-level segmentation in a multi-tenant virtualized data center, and the Cisco Data Center Network Management Center."
Does anyone know when the DCNM is going to be available for use in the 1010? I can't seem to find any documentation or software on the subject.
Thanks,
Ken
Hi,
DCNM 5.1(1) and above releases support Nexus 1010.
http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/dcnm/release/notes/dcnm_5_1_relnotes.html#wp122525
Thanks,
Ravikumar
Similar Messages
-
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
-
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 -
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,
EmreAndrew,
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. -
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,
EmreHi Andrew,
Great news, thanks... Looking forward for the release -
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,
KenKen
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 -
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 advanceHi,
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,
SabihHi 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 -
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 sessionPrasad,
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 youThe 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 KControl 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. -
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 AppFirst 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 -
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 KPrasad,
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/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 -
Hi all,
I tried to boot nexus 1010, but only cimc can login. The serial console did not show any information, and still no response. So I tried to connect keyboard and monitor, both are no response. In addition, the nic port is down too.
Have any idea? Or who to troubleshooting it?
Sent from Cisco Technical Support iPhone AppHello Padma,
Has this server worked before ?
-> Yes.
Are you able to access the N1010 host CLI interface by doing SSH to CIMC IP address ?
-> Yes.
ssh admin@ "connect host" did not show any response, and console can not return to CIMC.
Sent from Cisco Technical Support iPhone App
Maybe you are looking for
-
I want to change my macbook hard drive to a bigger drive
I want to change my macbook hard drive to a bigger drive, its a duo core. I would like to know what make is best and where do i get the tools for it eg screwdriver, static protector . Where do I order my drive from. Can I change my drive on this mode
-
Any help with crashing project?
Hello, I am a little new to Premiere pro but I don't feel this is a PEBCAC problem. I have been working for 2 weeks on a project and everything has been fine. I exported my sequence the other day and nothing to report, all good. Today I open the
-
Am running Firefox 7.0.1 now. Normal memory usage is 157mb but when running Facebook (not running apps nor games), it goes up to 553mb Why?
-
Video files with transparent edges needed for menu.
Hi, I am making a DVD menu using a PSD as the main background. In this background is a television at an angle. I need to position a video clip so that it appears to be playing in the TV. I have painstakingly angled the video footage in FCP to match t
-
What happened to the multi-touch imac
I heard from several people that apple has patented the idea of a multi-touch imac. Is apple actually going to build it?