Fabric Manager and UCS

I am having some problems getting Fabric Manager 5.0(4d) to authenticate to UCS switches (6120XP's at code level 4.2(1)). We are using TACACS+ for the authentication and the UCS switches are configured within TACACS. In Fabric Manager we get the status message of "Unknown User or Password (Server,Client). Anyone run into this?

Hello,
you will need to setup snmp user/password on UCS 6120 with the same snmp user and password as the switches
setup snmp for UCS
1.     UCS-A# scope monitoring
2.     UCS-A/monitoring# enable snmp
3.     UCS-A/monitoring# set snmp community public
4.     UCS-A/monitoring# commit-buffer
5.     UCS-A/monitoring# create snmp-user admin
6.     UCS-A/monitoring/snmp-user# set aes-128 no
7.     UCS-A/monitoring/snmp-user# set auth md5
8.     UCS-A/monitoring/snmp-user# set password (same admin password as the
seed switch)
9.     UCS-A/monitoring/snmp-user# commit-buffer
After setup snmp/password on UCS, click re-discover button on FM or better remove fabric and then re-discover fabric

Similar Messages

Difference between Cisco DCNM and CISCO Fabric Manager

Hello Everyone,
I am new to Cisco SAN and just would like to know the differences between cisco DCNM and Cisco Fabric manager and which one is latest as of now.
regards
VINAY

Hi Viany,
Fabric Manager was renamed DCNM starting at 5.2.
Fabric Manager only monitors SAN Fabrics, while DCNM 5.2 and above can monitor both SAN Fabrics and Ethernet LANs.
Regards,
David

Can no longer open Fabric Manager Web Client 4.7(2b)

Hello
I have recently upgraded from Fabric Manager 3.3(2b) to 4.2(7b). I followed the correct path, so went from 3.3 to 4.1 and then from 4.1 to 4.2.
The application opens but I can not browse to the localhost address on either http or https and there are no Cisco related services running, or, even available. Additionally, the server is no longer listenning on port 80 or 443.
Does anyone know of what might be happenning here because at the moment, trying to get to the server from itself, or remotely, just brings up a "page cannot be displayed" error.
Many thanks in advance
Anthony
p.s. I have rebooted since the rebuild.

Hi
Yes, the PostgreSQL service has started but there is not even a Cisco Fabric Manager service visible, nor a Fabric Manager Web Client service. I can open Fabric Manager and it works, just no services and I cant open the Web GUI.
Thanks for replying
Anthony

Fabric Manager releases

Hi,
I currently manage 4 Cisco M9509 directors running SAN-OS 3.3(1a). I am managing the fabric using Fabric Manager 5.0.1(a). We intend to upgrade the SAN-OS version to the latest recommended release (possibly a staged upgrade where necessary) once we have discontinued the legacy HBA hardware that was holding us back. We do not use Fabric Manager Server (FMS). In addition, we will shortly be managing the estate using Windows 7 32-bit rather than Windows XP.
1) With this in mind, based on backward manageability what is the most recent releases of Fabric Manager that I should be using currently and what should I be using once we go to the most recent SAN-OS available for the m9509 directors?.
2) Should I be using Data Center Network Manager instead of Fabric Manager once I'm on the latest SAN-OS or should this only be used to replace larger installations that currently use Cisco FMS?.
The Cisco website states the following:
Note This Important Change
As of NX-OS 5.2, Cisco Fabric Manager and FMS will be known as Cisco Data Center Network Manager for SAN
Many thanks for any advice.

Hello Blue Yonder,
Since the switches are new it might be that they are shipping with new OUIs which certain versions of FabricManager don't recognize. A simple upgrade of FM will fix this issue.
More details can be found here: http://www.cisco.com/en/US/ts/fn/633/fn63302.html
HTH,
Kris

Trouble installing Fabric Manager 5.0.7 on 2008R2

Hello all,
We are about to upgrade our older MDS-9124s to MDS-9148s and I wanted to install the new Fabric Manager. I am trying to install version 5.0.7. I am having a couple issues but am not sure if they are all related. First if I try to select the install links from within start they do not work. The only way I can get the install to start is double clicking the jre file direct. The installation process starts and the dies at what appears to be trying to start postgresql with an error message that initdb cannot be processed because the libpq.dll file cannot be found. If I try to re-run the install it dies becuase the postgre user already exists. I can delete that local account and the installation process will restart only to once again die with the dll error.
Just for grins I ran the postgresql install seperate and it seems to go through a lot more prompts but figured this was not the proper way to get it installed so canceled it. I also tried running the install from the cmd line as I found in another post and it dies at basically the same point but has a net error message 2221. It looks at though this to means that the user created cannot be accessed so postgresql will not start.
I am disabling my virus software while trying all of these items.
Suggestions??/
Brent

@dynamoxxx,
This is a new install and I just completed getting it installed on Friday. I had to actually log onto the server as the local administrator to get it to install. An Admin equivalent account apparently was not good enough. Once I did that it completed just fine. I have come across another apparetly known isse and that is if you exit Fabric Manager and try to go directly back in a box pops up that says Fabric Manager is already running. This is apparently because java never shuts down. You kill the javaws servise and Fabric Manager starts back up without any issue. Of course this also works if you log off the server and back on. This was somthing that I talked with TAC about this morning and since they have quit working on Fabric Manager is not going to be fixed.
That brings me to DCNA. I am moving to Cisco Prime for the rest of my infrastructure and TAC says that DCNA is a part of that or that basically is DCNA. They were telling me that based upon the code level I am running (5.0(1a)) on my switches that Fabric Manager is better. If I was running newer 6.2 or 5.2 code then use the DCNM and apparently 5.2(8) is newer than 6.2. They also recommended me waiting until 5.2(8b) come out before upgrading the switches and then moving to DCNA. I will figure out that step once I get my SAN migration completed in a few weeks. Until then I am planning to keep what I have.
Brent

Nexus 1000v UCS Manager and Cisco UCS M81KR

Hello everyone
I am confused about how works the integration between N1K and UCS Manager:
First question:
If two VMs on different ESXi and different VEM but in the same VLAN,would like to talk each other, the data flow between them is managed from the upstream switch( in this case UCS Fabric Inteconnect), isn'it?
I created a Ethernet uplink port-profile on N1K in switch port mode access(100), I created a vEthernet port-profile for the VM in switchport mode access(100) as well. In the Fabric Interconnect I created a vNIC profile for the physical NICs of ESXi(where there are the VMs). Also I created the vlan 100(the same in N1K)
Second question: With the configuration above, if I include in the vNIC profile the vlan 100 (not as native vlan) only, the two VMs can not ping each other. Instead if I include in the vNIC profile only the defaul vlan(I think it is the vlan 1) as native vlan evereything works fine. WHY????
Third question: How it works the tagging vlan on Fabric interconnectr and also in N1K.
I tried to read differnt documents, but I did not understand.
Thanks

This document may help...
Best Practices in Deploying Cisco Nexus 1000V Series Switches on Cisco UCS B and C Series Cisco UCS Manager Servers
http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9902/white_paper_c11-558242.html
If two VMs on different ESXi and different VEM but in the same VLAN,would like to talk each other, the data flow between them is managed from the upstream switch( in this case UCS Fabric Inteconnect), isn'it?
-Yes. Each ESX host with the VEM will have one or more dedicated NICs for the VEMs to communicate with the upstream network. These would be your 'type ethernet' port-profiles. The ustream network would need to bridge the vlan between the two physicall nics.
Second question: With the configuration above, if I include in the vNIC profile the vlan 100 (not as native vlan) only, the two VMs can not ping each other. Instead if I include in the vNIC profile only the defaul vlan(I think it is the vlan 1) as native vlan evereything works fine. WHY????
- The N1K port profiles are switchport access making them untagged. This would be the native vlan in ucs. If there is no native vlan in the UCS configuration, we do not have the upstream networking bridging the vlan.
Third question: How it works the tagging vlan on Fabric interconnectr and also in N1K.
- All ports on the UCS are effectively trunks and you can define what vlans are allowed on the trunk as well as what vlan is passed natively or untagged. In N1K, you will want to leave your vEthernet port profiles as 'switchport mode access'. For your Ethernet profiles, you will want them to be 'switchport mode trunk'. Use an used used vlan as the native vlan. All production vlans will be passed from N1K to UCS as tagged vlans.
Thank You,
Dan Laden
PDI Helpdesk
http://www.cisco.com/go/pdihelpdesk

Hyper-V Fabric and Fabric Management Cluster

Dear All...........Would appreciate understanding of following:
What is the difference between Fabric Cluster and Fabric Management Cluster?
What virtual machines should be part of Fabric Cluster and Fabric Management Cluster respectively?
Thanks in advance.

It would be helpful if you provided a source from which you pulled those terms. They could mean just about anything without any context.
But I will take a stab at it based upon work I do with the Microsoft Private Cloud Fast Track program. In this reference architecture, a private cloud is being built. To manage the private cloud, a Hyper-V cluster is created and all the System
Center components required to manage the private cloud are installed on this cluster. This cluster is called the Fabric Management Cluster because from it all components of the Fabric, servers, storage, networking, VMs, policies, libraries, etc. are
managed.
Once that Fabric Management Cluster is established, any number of Fabric Clusters can be configured. For example, the Private Cloud could be configured for a business, and multiple business units have virtual systems deployed. The Fabric Management
manager could decide to build one large Fabric Cluster on which to deploy the various business unit machines, or the manager could create separate clouds, each consisting of its own Fabric Cluster. Each separate cloud could be dedicated to the use of
a single business unit.
Again, all conjecture on my part because you have not provided any context.
. : | : . : | : . tim

Cisco Fabric Manager database stops and refuses to start again

The database process - FMPersist - of Cisco Fabric Manager (3.02a) fails then I can't get it started again.
We're running on a Linux server and I'm attaching the FMPersist.log.

Part of our problem has been that the database is not robust enough to handle a large fabric like we have. We upgraded to version 3.12a and split the load across two servers (and database) - test on one and production on another - so the database doesn't shut down any more, but the continuing problem has been that it will stop refreshing data. We bounce the processes once a week to update the fabric information. We are not collecting any performance data.

Management vlan with the 1000V and UCS

If I want to use VLAN 10 for management, I would have to configure the following:
1000V -VM vEthernet port profile access port with VLAN 10, Ethernet uplink profile includes VLAN 10
UCS - vNIC in Service Profile, include VLAN 10, and include VLAN 10 in uplink trunk from UCS
Upstream switch: Include VLAN 10 in trunk port.
OK?
Now, this management VLAN, can I Iuse this for everything? I mean for 1000V management VLAN, vSPhere management, FI management and switch management? Or should for instance the 1000V management be different from the others?

Hi Atle,
Yes, what you have mentioned is the correct in terms of activities you need to carry out. However i would like to add a few:
1) define the vlan on the UCS - unless you do this you will not be able to add it to the vnic. Plus once you have the vlan defined it will automatiaclly get added to the trunk list on the uplinks ports (unless you l2-disjoint configured)
You can have the same vlan for all the management, unless you have certain traffic you would not like certain device to see / reach.
./Abhinav

Two Fabric redundancy and storage flapping

Hello!
I have a fairly new Nexus 5548 implementation, using the Nexus for stricly storage. I have two 5548s for two different Fabrics, for redundancy. They are two seperate fabrics, and the Nexus are not stacked so they are managed individually. When I have both Nexus online my VMware side starts flapping, and loosing storage which causes my ESXi hosts to lock up and VMs to go unresponsive. This does not happen 100% of the time, but it happens intermitentaly and sometimes is catestrophic to datacenter services. When I shut down one of the Nexus switches, storage comes back and everything is healthy.
All hosts are connected via 4GB FC (supposedly HP cant do 8GB without problems)
5/6 of my hosts are on HP c7000 enclosures via 10gb FlexFabric switches, the rest via UCS
Netapp clustered pair is the target. When the ESXi hosts loose storage, they are still flogi'd in to the storage and fabric
ESXi 5.0 w/newest (and correct) drivers. VMWare tech support sees no problems, other than the "storage is getting pulled from the host"
Newest firmware on everything HP & UCS
Nexus running 5.0(3)N2(2a)
Using per-iniator zoning
Fabric-A and Fabric-B are different VSANs
Any ideas? Do I have a design flaw in my fabric? HP, Cisco, Netapp, and VMware all pretty much have no clue. So this forum is a shot in the dark. Thanks for ANY ideas you guys can provide

could it be some kind of trespassing on the storage array ? LUNs start balancing between the controllers and eventually the host times out. Have you tried different failover (NMP) policy in ESXi ?

Dual 6500 and UCS

Hi all,
We have recently installed a UCS enviornment with 2 x 6100 units connected to our dual 6509 core. It is set up so that 2 x 10GigE uplinks connect from FAB-A to 6509-1 and 2 x 10GigE connect from FAB-B to 6509-2. Each of the 4 trunks to the 6509 enviorment are configured the same and truck the same 4 VLAN to FAB-A or FAB-B. We have 2 x UCS Chassis, each with 4 half-width servers. Each chassis has an A and B side, with 20GB going to FAB-A and 20GB going FAB-B.
The above UCS enviorment was installed by a 3rd party, while I configured the core-side of the links.
Our server team recently brought up a Windows server and I started seeing mac-flapping on one of our cores, between one of the 10GigE ports connected to FAB-A and the trunk link that exists between our 2 cores.
I'm a bit unsure about how, on the 6509 side, the ports should be configured.. I was told by the 3rd party that there is no 'active/standby' design, all of the trunks to each of the two 6100s are active 'all the time'. Our 6509 aren't running the VSS supervisors, just 'standard' sup720s running HSRP, with a trunk between the two.
I understand that more details is probably required, but I said i'd look into from a networking/core standpoint and the server guy is checking out his end, as as it stands he has the server in question connected to 2 vNICs, one on each of the 6100s, both 'up'.

Correct, Alan. With fabric failover, you can accomplish redundancy with only one vNIC and the server OS does not need to know about or manage anything to do with the failover. Brad has another post that goes into some detail on that.
http://bradhedlund.com/2010/09/23/cisco-ucs-fabric-failover/ With UCS in your environment, you will find his is a very good blog to follow.
You should make the vNIC primary on the fabric that is connected to the core which is the root bridge and has the primary HSRP or VRRP router interface of the VLAN the server is on and enable fabric failover. If the fabric fails and it goes out the other fabric to your other core, it will still be forwarded, but will have to cross the trunk between your cores to be routed. Making sure that the primary fabric for any given vNIC matches the primary router & root bridge for the access VLAN assigned to it will minimize the traffic crossing the trunk between your cores.
There are other redundancy options beside fabric failover which can work better with VSS or in situations where you have equipment capable of virtual port channels. Likely your server team had the server configured to spread its traffic between two interfaces, one on each fabric, for load balancing and redundancy. This is not the best scenario for uplinking to your dual non-VSS 6500s.

Connecting to UCS6120 from Fabric Manager using TACACS

Standalone Fabric Manager 5.0(4a)
UCS 1.4(3s)
I have to log into Fabric Manager using TACACS with SNMPv3 (company network security restriction).
I launch Fabric Manger using my TACACS account which connects to all the switches in my two fabrics using the same credentials.
I can connect to all MDS9513, MDS9222i, IBM Bladechassis FC switch modules and all NX5020 switches in the fabrics. Fabric Manager cannot connect to any of the eight UCS6120 switches in the fabrics, returning a status of Unknow User or Password(Server,Client).
This, I understand, requires the creation of a specific SNMP user, which is fine. However as I am logged into Fabric Manager using a single TACACS account, I cannot supply alternate credentials to a subset of switches in the fabric.
Is there a work around for this to enable management of the 6120s in FM? or am I missing something.
Thanks
Mike Taylor

Fabric Manager uses the same credentials to access all systems, these credentials will need to be valid on the UCS platform as well. Create a local SNMP user on UCS and check. This needs to be different from any non-snmp authentication accounts on UCS.
Note that FM cannot manage UCS. You will be able to view into UCS but not make changes. May not be an issue if UCSM is running end host mode. To make any changes, you will need to use the UCSM GUI or CLI or other tool for administration.
Thank You,
Dan Laden
PDI Helpdesk
http://www.cisco.com/go/pdihelpdesk

Fabric Manager - do I need to install server component?

Hi,
I would like to know if I need to install the server component of Fabric Manager, or if I can just use the client component to manage the switches directly.
I have 2 MDS 9120 switches which will be run as 2 separate fabrics. They will be used in a non-production environment and I will need to configure VSAN and zoning using pWWN. If I do need to install the server part, what is the benefit of using the licenced version over the unlicenced?
Thanks, Darren.

Darren,
The choice to install and licence the server component would be to manage your entire SAN fabric as a holistic centralized topology versus using the client which pretty much only allows you to view the fabrics individually within Fabric Manager.
For a small non-production environment like yours you will be fine, but if you find yourself in a situation where your fabric is becoming a larger Production enironment then I would recommend moving to the licenced server version.
regards
Alan

Cisco MDS 9513/9509 LDAP/AD Auth via SSH & Fabric Manager

Hello Folks,
I am trying to look for working config with LDAP auth over SSH. I know how to use them over TACACS+ & Radius. But due to other internal issue, currently I am trying to get the Cisco MDS to directly auth using LDAP/AD. Also, I see no option of LDAP/AD in FM(Fabric Manager), but just TACACS+, Radius, LocalFM and MDS. Do using MDS uses default auth(ie whatever AAA authentication is configured for ? or local DB on the switch). Does the new DCNM supports LDAP/AD auth on the GUI ?
Larger goal is SSH(CLI) & FM(GUI) using the same LDAP/AD auth. I understand the snmp-server user issue. But once I have SSH working over LDAP/AD I can figure that out to..
Here's what I need to ensure when using LDAP/AD auth
1) What is the exact config for this LDAP/AD auth
2) How do I ensure that network-admin & network-opertor roles are assigned when certain AD Groups Logins in Like ADMIN-AD-GROUP , OPERATOR-AD-GROUP --> trying to login to the switch
3) Also using SSL port for LDAP, do details are encrypted over the network.
4) Do I need to use the PASSWORD in paintext when BINDING the BaseDN ?, can it be an encrypted password.
Appreciate any info on this. Thanks for your time.

As of DCNM 6.1 (aka - Fabric Manager Server) we support LDAP authentication adding to existing Radius, TACACS+, local and switch authentications. You can upgrade from Fabric Manager 5.0 to DCNM 5.2 to DCNM 6.1 if you like to keep current performance, events, config data alive. We do recommend fresh install as we don't know what state your server dabatabase might be in. Including some links for you to help out with deployment and best practices (see release notes).
Resources:
Main Website:
http://www.cisco.com/go/dcnm
How To Video Series: http://www.cisco.com/en/US/prod/netmgtsw/ps6505/ps9369/cisco_dc_nm_video_library.html
Install and Licensing Guide:
http://www.cisco.com/en/US/products/ps9369/prod_installation_guides_list.html
Evaluation Licenses: http://tools.cisco.com/SWIFT/LicensingUI/Home?FormId=65
Download Linux and Windows Executables: http://www.cisco.com/cisco/pub/software/portal/select.html?&i=!m&mdfid=281722751
Data Sheets: http://www.cisco.com/en/US/prod/collateral/netmgtsw/ps6505/ps9369/data_sheet_c78-639737.html
Install Guide: http://www.cisco.com/en/US/products/ps9369/prod_installation_guides_list.html
Configure Guide: http://www.cisco.com/en/US/products/ps9369/products_installation_and_configuration_guides_list.html
API Programming Guide:
http://www.cisco.com/en/US/products/ps9369/products_programming_reference_guides_list.html
Reference Guide: http://www.cisco.com/en/US/products/ps9369/prod_technical_reference_list.html
Release Notes: http://www.cisco.com/en/US/products/ps9369/tsd_products_support_general_information.html

Changing Fabric name in Fabric Manager

How do you change the name of the Fabric in the Logical Domains section of Fabric Manager?

This is also something I'd be interested in seeing. I've got one fabric named correctly, the other after a switch dump took the name of a middle tier 9216i and won't switch back, despite the fact that I changed the principal priority on the 9509 to 1 and then made it the principal with a disruptive(nondisruptive didn't work either).
Cisco documentation is woefully inadequate in certain areas....Also, the error of fabric merge failed, "member mismatch" comes to mind.

Fabric Manager and UCS

Similar Messages

Maybe you are looking for