Fabric Manager - switches status - No Traps.

Greetings,
When I am looking at the Fabric in Fabric Manager, the switches present information like name, etc.. and tere is a Status entry. I see Status of No Traps. What does it mean?
Stephen

If you get yellow text 'No Traps' in FM client means that the FM has not registered trap address on this switch successfully and hence not receiving traps from those switches. It may be that the trap address table is full (max is 10 entries) on the switch. If table is full, then delete any stale/unused addresses in the switch. The FMS's next periodic poll will add it's trap address to the switch and the 'No Traps' warning will go away after this. Try
refreshing the Switch table in the FM client to see an updated status.
And also check the Switches remain manageable even when "No Traps" is displayed. Then you are hitting bug CSCta72679. To workaround this Rediscovering the Fabric will change the status back to "ok" but this is only a temporary solution.

Similar Messages

  • Timeout for Switch on Fabric Manager

    I am getting timeouts for switch connectivity on Fabric Manager. The error in the log is below. Would this be a firewall issue?
    An authentication problem? Or a configuration problem?
    %SNMPD-3-ERROR: SNMP log error : usm_process_in_msg : SNMP UDP authentication failed for 172.x.x.x
    Within Fabric Manager under Status the message shows timeout(Server)

    is there a firewall in between?
    which ports have you opened?
    I am trying to gather ports needed for firewall but documentation has not been helpful. but make sure that udp port 2162 is opened from switch to FM server and same port has been manually specified on switch snmp config

  • Fabric Manager not on switches.

    Greetings,
    I just took delivery of some 9216A's and found that Fabric Manager is not on them anymore. Device Manager is but for how long?? I have to download FM or get it for the non existant CD's. When did that start? Being a typical Cisco end user means I never get a login to download software as my vendor is supposed to look after me. It was much easier when it was on the switch. Perhaps not everyone works in sites with easy access to the internet...
    Stephen

    Thanks for the reply. Now I am keen to work out why it is so big. I hope it not just bloated for the sake of it.
    Stephen

  • Need SNMP OID for MSTP status in Cisco SG300-28MP 28-port Gigabit Max-PoE Managed Switch

    Hi,
    I have configured redundant network using two Cisco SG300-28MP 28-port Gigabit Max-PoE Managed Switch through MSTP & it's working fine.
    I need OID of MSTP status from which I can monitor which Switch is active and which one is in standby mode.
    Please help.
    Thanks,
    Harsha 

    Hi Harsha,
    check these OID's:
    http://tools.cisco.com/Support/SNMP/do/BrowseOID.do?objectInput=1.3.6.1.4.1.9.9.500.1.2.1.1.6&translate=Translate&submitValue=SUBMIT
    http://tools.cisco.com/Support/SNMP/do/BrowseOID.do?objectInput=cRFStatusUnitState&translate=Translate&submitValue=SUBMIT&submitClicked=true
    Thanks-
    Afroz
    **Ratings Encourages Contributors ***

  • Need SNMP OID of MSTP status for Cisco SG300-28MP 28-port Gigabit Max-PoE Managed Switch

    Hi,
    I have configured redundant network using two Cisco SG300-28MP 28-port Gigabit Max-PoE Managed Switch through MSTP & it's working fine.
    I need OID of MSTP status from which I can monitor which Switch is active and which one is in standby mode.
    Please help.
    Thanks,
    Harsha 

    Hi Harsha,
    check these OID's:
    http://tools.cisco.com/Support/SNMP/do/BrowseOID.do?objectInput=1.3.6.1.4.1.9.9.500.1.2.1.1.6&translate=Translate&submitValue=SUBMIT
    http://tools.cisco.com/Support/SNMP/do/BrowseOID.do?objectInput=cRFStatusUnitState&translate=Translate&submitValue=SUBMIT&submitClicked=true
    Thanks-
    Afroz
    **Ratings Encourages Contributors ***

  • Any issues running 3.3(4b) Fabric Manager on 3.3(1c) switches?

    I'm doing a little pre SAN-OS upgrade work (and changing out my FM Server backend DB from Postgres to Oracle 10g) and I see that the clone option is back (finally) in 3.3.(4b) fabric manager.
    We've run newer versions of Fabric Manager before, ran 3.1.x on a 3.0.x fabric for a while so I'm just wondering if I could upgrade my production management FM server (not just data collection but management) from the current SAN OS to a newer one before I install SAN-OS 3.3(4b) on my switches?  It should be backwards compatible but . . . just wondering if someone else has the scars from this sort of activity.

    Yeah that's the answer I'm getting from Cisco too.  We've had some real flakey behaviour at odd times lately (zone sets that are inserted into the active zoneset but disappear when you try to activate, zone set renames that dont' take etc.) which all seem to be Java issues (i.e . it's slow and flakey and you're rdp'd to the FM server so that's in there too.)  But we need to redo the FM server anyway and thought I'd make sure it was o.k. to upgrade at the same time.

  • 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 Server discovery issue

    Hi,
    I installed Fabric manager server and trying to discover a fabric.
    after entering the user and password for the SNMP v3 I am getting SNMP timeout.
    the user is configured on the switch and "snmp-server host" was created for the fabric manager server
    in order to receive traps (using port 1163).
    in the snmp-log i am getting an error about a timeout but no other information besides:
    no SNMP/TCP support.
    (I am attaching the log...)
    does anyone knows what can I do?
    Thanks!

    Looked at your log.  you may have firewall in between.  There are many connections timeout using TCP/UDP. Talk to you network team. snmpv2/v3 need to be allowed.
    2011.07.11 16:21:16  WARN  [snmp.tcp] connect timed out
    java.net.SocketTimeoutException: connect timed out
                at java.net.PlainSocketImpl.socketConnect(Native Method)
                at java.net.PlainSocketImpl.doConnect(Unknown Source)
                at java.net.PlainSocketImpl.connectToAddress(Unknown Sour
    2011.07.11 16:21:16  ERROR [snmp.udp] request sending error: <16:21:11 10.5.125.250, 1836974547 GET u=null >
    com.cisco.dcbu.lib.snmp.SnmpException: send PDU: no SNMP/TCP support. connect timed out
                at com.cisco.dcbu.lib.snmp.SnmpSession.writePDU(SnmpSession.java:709)

  • 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

  • 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 won't Start

    I upgraded to 3.1(2a) and then I reinstalled Fabric Manger and Device Manager. Fabric Manager won't start, error is "Unable to connect to server! Admin login from 127.0.0.1 failed". Device Manager is fine.

    I am running into the same situation but with FM(3.0.2a) on a Windows Server 2003. We are using Citrix for FM client login. Looking at the windows services FM server services is in running status. The second login attempt would work, not sure why?
    When log in locally via windows remote desktop connection we get these error dialogs "ERROR Open Fabric - Fabric Manager 3.0(2a) Error in register for events: Connection refused to host: 10.1.x.x;nested exception is:java.net.ConnectException: Connection timed out: connect
    and
    NoSuchOject: no such object in table
    After clear these dialogs the second attempt with work.
    I can see login issues from remote client but even locally on the server? Any suggestions?
    Thanks,

  • 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

Maybe you are looking for