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.

Similar Messages

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

DCNM SAN 6.2 + Nexus 5500 not using interface mgmt

When trying to discover a newly setup fabric we have set the SVI of one of the Nexus 5500 switches as seed device in DCNM SAN server. Problem do seem to be the same in DCNM 6.2 as in DCNM 5.x, one can not use a SVI.... After adding the seed switch with the IP adress of the SVI it appears in the Admin->Data sources->Fabric with the ip address of the mgmt interface. Thing is that this ip address can not be reached from the DCNM SAN server since we have only used a cross over ethernet cable for peer-keepalive over the mgmt interfaces.
Is there a way in DCNM SAN 6.2 to force SAN management over a SVI instead of the mgmt interface?

Here is the solution:
in the menubar on the top, in the lower one go to Admin > Server Properties
scroll to the middle of the list, locate “fabric.managementIpOverwrite” and set it to false
restart the DCNM Servers

DCNM-SAN supporting FI

Using DCNM-SAN with UCS (2.1.2a); I created on all FC devices (MDS and N5k) a user "dcnmuser" with netadmin rights. I also created a snmp v3 user "dcnmuser" with UCSM. Then I did a fabric discovery with DCNM-SAN; I see the fabric, MDS, N5k and FI, however, the FI have a red arrow, which means not manageable.
Q. what could be wrong ? or is this really supported ?

Understood, thanks Robert
We only want to monitor UCS-FI with DCNM-SAN.
The release notes 6.1.2
http://www.cisco.com/en/US/docs/switches/datacenter/sw/6_x/dcnm/release/notes/dcnm_6_1_relnotes.html
are quite misleading:
Introduction
Cisco Data Center Network Manager combines the management of Ethernet and storage networks into a single dashboard to help network and storage administrators manage and troubleshoot health and performance across the following product families that run Cisco NX-OS software:
•Cisco MDS 9500 Series Multilayer Directors and Cisco MDS 9200 and 9100 Series Multilayer Switches
•Cisco Nexus 1000V Series Switches and Cisco Nexus 1010 Virtual Services Appliance
•Cisco Nexus 2000 Series Fabric Extenders
•Cisco Nexus 3000, 4000, 5000, and 7000 Series Switches
•Cisco Catalyst 6500 Series Switches
•Cisco UCS 6100 and 6200 Series Fabric Interconnects
•Cisco FireWall Service Module (FWSM)
Cisco DCNM-SAN Release 6.1(1b) and later releases do not support Cisco Nexus 5000 Series switches and UCS devices running Cisco NX-OS Release 4.1(3) or an earlier release.
However, Table 9 Hardware Features Supported by Cisco DCNM Release 6.1
doesn't show UCS FI !

DCNM-SAN: SAN Health Advisor

Hi there
Could someone please provide a link to download this tool?
We are trying to install the SAN Health Advisor tool, but the instructions do not state where to launch the installer.
The instructions we are following are here:
http://www.cisco.com/en/US/docs/switches/datacenter/mds9000/sw/5_2/configuration/guides/fund/DCNM-SAN-LAN_5_2/perfmon.html#wp1302248
Refer to the last section called "Installing the SAN Health Advisor Tool".
Thanks in advance.
John

John,
The SAN Health Advisor tool was integrated into DCNM-SAN in 5.2(1). You can get the same reports and information from DCNM-SAN. Seems that the section in your linked document was not updated. I have contacted the documentation team to update it accordingly.
-Seth

DCNM-SAN & VMware

Hello,
In the release notes for DCNM 5.2, it states that DCNM-LAN can be installed as a virtual machine. However, no where does it state that DCNM-SAN can be installed as a virtual machine. So my question is can DCNM-SAN be run as a VM? It would make sense that this would be allowed since LAN and SAN can now exist on the same box with 5.2 but it wouldn't make sense if SAN was not supported as a VM when LAN is. Thanks.

http://www.cisco.com/en/US/customer/docs/switches/datacenter/sw/5_x/dcnm/release/notes/dcnm_5_2_relnotes.html#wp61633
Supported as of 5.2 per the release notes above. And both can coexist in the same VM.
This is the validation from the release note:
The Cisco DCNM server can run within a virtual machine, and requires one of the supported Windows or Linux operating systems listed in this section.
Specifics for the host OS can be found in the release notes.
Hope that helps,
Cary Cube'
CSE, CISCO

DCNM-SAN: No fabrics found

Hi,
I have the following problem concerning DCNM-SAN.
I recently upgraded to DCNM 5.2.2c.
We came from a lower DCNM version, where Fabric Manager was not already included in the DCNM package.
I've uninstalled Fabric Manager as it was recommended by an upgrade manual from Cisco.
After some time, it was possible to install DCNM 5.2.2c.
The DCNM-LAN is working, but the DCNM-SAN isn't.
Unfortunately, I'm unable to access our SAN fabrics.
Our environment exists of Cisco MDS switches and a one server where DCNM-LAN and DCNM-SAN are installed.
When we open the DCNM-SAN client and try to login, I can login but I get an "There are no fabrics available for <username>@Radius" error.
With some investigation, I found out that we needed to have the "network-admin" role in ACS 4.2.
We have already had that role configured, so that couldn't be the case.
I also checked if the DCNM-SAN service was running, and it is.
Can somebody please help me out as we are not able to access the fabrics.
With kind regards,
Bart Mars

http://www.cisco.com/en/US/customer/docs/switches/datacenter/sw/5_x/dcnm/release/notes/dcnm_5_2_relnotes.html#wp61633
Supported as of 5.2 per the release notes above. And both can coexist in the same VM.
This is the validation from the release note:
The Cisco DCNM server can run within a virtual machine, and requires one of the supported Windows or Linux operating systems listed in this section.
Specifics for the host OS can be found in the release notes.
Hope that helps,
Cary Cube'
CSE, CISCO

DCNM SAN Client - SNMP Timeout

Hello Everyone,
right now iam struggling with the configuration of a DCNM SAN Client.
The Installation and licensing (with some trouble) has been finished few days ago.The DCNM LAN Client is working well and there are no problems with connectivity or timeouts. SSH and SNMPv3 are working fine for both Clients (SAN&LAN).
Discovering Fabrics for the DCNM SAN Client is working very well to. But when I start the DCNM SAN Client and open a session to a fabric it looks like this:
If I try to "edit local full zone database" it looks like this:
Tried to troubleshoot this behaviour but at the moment I am not able to figure out the problem.
Maybe someone in this community does?
Best Regards,
Sascha

This can be closed.
I got all answers... For the benefit of others who are searching answers for the same question:
1) I just downloaded the dcnm client for LAN ... is there a seperate client for SAN ? I dont see any download links for SAN... --- Yes .. DCNM SAN has a seperate client. After installation, you can open the DCNM page on http, and you would find the download links on top right corner for DCNM-LAN, SAN and device manager.
2) Is it possible to add brocade switches to DCNM-SAN? Does it require additional licenses? - I dont think this is possible
3) Can we use the fabric manager license "N5000FMS1k9" for DCNM SAN, or do we need "DCNM-SAN-N5K-K9" license for the nexus 5000? - Yes.. Use the same license and generate the PAK file. FMS licenses do work in DCNM-SAN..
Good luck

Error Java when installing DCNM 6.3

Hi my friend:
Some have this problem when installing DCNM 6.3 on windows 2012 R2 standard java 8.0
Thank for all
Marco.

Hi Marco,
When you get the fatal application error, can you click on details to see the full exception? Most commonly, you will see "Flexeraaxx$aaa: Windows DLL failed to load". If that is the case, then try running the DCNM installer in compatibility mode.
Right-click on the dcnm-installer-x65.exe file and select "Troubleshoot compatibility". Then, select "Troubleshoot program" -> Select "The program worked in earlier version of Windows but won't install or run now" -> Select Windows 7 or WIndows 8 -> Start the Program.
-Eric

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.

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

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

Installing DCNM-SAN as a VSB in Nexus 1010

Similar Messages

Maybe you are looking for