CISCO MDS 9124 SFP Compatibility

We recently received a number of spare SFPs in case of failure of the installed items. After having installed one of these SFPs in our test bed we receive the following notification:
%PORT-5-IF_DOWN_FCOT_VENDOR_NOT_SUPPORTED: %$VSAN 1%$ Interface fc1/1 is down (Error disabled - FCOT vendor not supported)
On checking the online documentation we located the following:
Error Message ETHPORT-5-IF_DOWN_FCOT_VENDOR_NOT_SUPPORTED: Interface [chars] is down (Error disabled - Fcot vendor not supported).
Explanation The inserted small form-factor pluggable (SFP) device is not supported.
Recommended Action Contact customer support for a list of authorized SFP vendors.
Introduced Cisco MDS SAN-OS Release 1.2(2a).
Does anyone know of any workarounds for this? Also does anyone know where we may locate a defnitive list of supported vendors [other than waiting on results from customer support].
Thanks

Hi Daniel,
As far as I know, only Cisco SFPs are supported.
Here is a link to the information on what SFPs are supported and where:
Cisco MDS 9000 Family Pluggable Transceivers Data Sheet
Best regards,
Jim

Similar Messages

  • Troubleshoot connectivity with Cisco MDS 9124

    Hello,
    I recentrly discovered that it's become impossible to connect to a CISCO MDS 9124, neither with SSH nor with Serial connection.
    What should i do please to resolve that issue please?
    Regards!

    Hi,
    Are you able to access the 9124 by Device Manager, web browser, telnet, or ssh when your laptop is directly connected to the mgmt0 interface and your laptop configured on the same subnet as the mgmt0 interface?
    What console settings, console cable, terminal emulator application are you using and does it work with another MDS9000?
    Regards,
    David

  • How to configure an external Cisco MDS 9124 Switch

    I have worked with some other Fibre switches before but not Cisco and was wondering if someone can pass me some quick info on how to configure the MDS 9124. I saw the Quick Guide and it briefly talked about config, but do I have to go thru hyperterminal to do the initial IP config? Is there a default one already I can use to get to the WebGUI. Some of the ones I worked with (like the ones that come with the Bladecenter) have a default IP, where I can enter the IP into the web browser and access the GUI right away and start doing configs.
    With the MDS 9124, can I do this? Or do I have to configure IP thru hyperterminal and then install Fabric Manager etc.
    Thanks in advance for any help!

    I assume that you actually read the guide:
    http://www.cisco.com/en/US/docs/storage/san_switches/mds9000/hw/9124/quick/quide/9124QSG.html
    Setup of the network is pretty clear. If the switch is brand new, you have to give it an IP address. Generally just follow the dotted line and don't vary except if you know what you are doing.
    Once its on the network, DM and FM can do the rest.
    The 9124e's don't have serial ports so the OA looks after that for you.

  • How to use MDS 9124 evaluation licences

    I have 2 MDS9124 fabric switches that have permanent licenses.  Currently the first switch has 16 ports enabled and in use and the second switch has 8 enabled and in use.  I am ordering a license for 8 more for the second switch but in the mean time I would like to use some of the other ports.
    Is there a way to activate the 120 day grace period on this switch to use the evaluation licenses for the other 8 to 16 ports?
    I have 3 VMware ESXi hosts that I want to connect to our storage and I already have the Cisco SFP's in place at this time.
    I use both CLI as well as Device Manager 5.0(1a).
    Any help would be appreciated.
    Thank you,
    Robert
    SHOW VERSION
    Cisco Nexus Operating System (NX-OS) Software
    TAC support: http://www.cisco.com/tac
    Copyright (c) 2002-2010, Cisco Systems, Inc. All rights reserved.
    The copyrights to certain works contained herein are owned by
    other third parties and are used and distributed under license.
    Some parts of this software are covered under the GNU Public
    License. A copy of the license is available at
    http://www.gnu.org/licenses/gpl.html.
    Software
      BIOS:      version 1.0.19
      loader:    version N/A
      kickstart: version 5.0(1a)
      system:    version 5.0(1a)
      BIOS compile time:       02/01/10
      kickstart image file is: bootflash:/m9100-s2ek9-kickstart-mz.5.0.1a.bin
      kickstart compile time:  12/25/2020 12:00:00 [02/21/2010 20:55:31]
      system image file is:    bootflash:/m9100-s2ek9-mz.5.0.1a.bin
      system compile time:     2/2/2010 17:00:00 [02/21/2010 21:40:51]
    Hardware
      cisco MDS 9124 (1 Slot) Chassis ("1/2/4 Gbps FC/Supervisor-2")
      Motorola, e500  with 516136 kB of memory.
      Processor Board ID JAF1521BLSG
      Device name: WMC-GW-FC-SW-01
      bootflash:     254464 kB
    Kernel uptime is 34 day(s), 0 hour(s), 27 minute(s), 59 second(s)
    Last reset
      Reason: Unknown
      System version:
      Service:
    SHOW LICENSE USAGE
    Feature                      Ins  Lic   Status Expiry Date Comments
                                     Count
    FM_SERVER_PKG                 No    -   Unused             -
    ENTERPRISE_PKG                No    -   Unused             -
    PORT_ACTIVATION_PKG           No    8   In use never       -
    10G_PORT_ACTIVATION_PKG       No    0   Unused             -
    --------------------------------------------------------------------------------Feature                      Ins  Lic   Status Expiry Date Comments
                                     Count
    FM_SERVER_PKG                 No    -   Unused             -
    ENTERPRISE_PKG                No    -   Unused             -
    PORT_ACTIVATION_PKG           No    8   In use never       -
    10G_PORT_ACTIVATION_PKG       No    0   Unused             -

    on the second switch to use another 8 ports.
    there isn't anyway to activate 120 Day grace period license for ports 9 throu 16
    Grace period licenses are for "feature" only not for "on demand ports"
    I think you can try requesting temp lisense for 8 ports block until permanent lisense is installed.
    for that you should contact licensing team ([email protected]) and see if that request can be accomodated.

  • Best Practices for multi-switch MDS 9124 Impelementations

    Hi,
    I was wondering if anyone had any links to best-practices guides, or any experience, building mutli-swtich fabrics with the Cisco MDS 9124 or similar (small) switches? I've read most of the FibreChannel books out there and they all seem pretty heavy on theory and FibreChannel protocol operations but lack when it comes to real-world deployment scenarios. Something akin to the Case Studies sections a lot of the CCIE literature has, but anything would be appreciated.
    Regards,
    Meredith Shaebanyan

    Hi Meridith
    www.Whitepapers.zdnet.com has links to good reading. It has links to items like:
    http://www.vmware.com/pdf/esx_san_cfg_technote.pdf is probably a typical SAN environment these days. It's basic and just put your 9124's in where the switches are.
    http://www.sun.com/bigadmin/features/hub_articles/san_fundamentals.pdf is for bigger SANs such as DR, etc.
    Things to consider with 9124's are:
    They can break so keep a good current backup on a tftp/ftp/scp server.
    Consider that if you have all the ports used, the two 8 port licences are not going to work on a replacement switch as they are bound to your hostid. The vendor that sold the switch should be able to get replacements quickly but you will lose time with them.
    Know exactly what the snmpserver command does as if you have your 9124 replaced and you load your backup config and you use Fabric Manager, it won't be able to manage the 9124 unless you change the admin password with snmpserver.
    9124/9134's don't have enough Buffer Credits to expand beyond about 10 km.
    Any ISL's used between switches should always be at least two and use Port Channels where possible.
    The 9124 or 9124e or 9134 are great value based switches. I keep a spare for training and emergencies. We use them in a core/edge solution and I am very satisfied with them. I have only had one failure with Cisco switches in the last 5 years and it was a 9140 that sat around for far too long doing nothing. The spare meant we were up and running in 30 minutes from the time we noticed the failure and got to the data centre. As there were two paths, no one actually noticed anything. My management system alerted me.
    Remember to make absolutely sure that any servers attached to the SAN have multipathing software. The storage array vendors (HDS, EMC, etc) can sell you the software such as HDLM or Powerpath. You can use an independent solution such as Veritas DMP. Just don't forget to use it.
    Follow the guidelines in the two documents and get some training as the MDS training is very good indeed. 5 days training and you will be confident about what to do in any sized SAN including Brocade and McData.
    A small SAN is just as satisfying as a large one. If in doubt, get a consultant to tell you what to do.
    Is that what you was after? I hope it was not too simple.
    Stephen

  • MDS 9124 -- Limited Command Set?

    I've got two MDS 9124 FiberChannel switches, and can SSH into them using RADIUS authentication with my domain admin user.
    I'm trying to do things, like update the license file, but lots of "normal" commands, like "copy" which is documented in the license update procedure, are missing. Page 1-6 of this PDF [command reference for SAN-OS 3.x] lists many more commands that I don't seem to have: http://www.cisco.com/en/US/docs/storage/san_switches/mds9000/sw/rel_3_x/command/reference/CR03.pdf
    The rest of this post will be (1) the output of "?" at the EXEC prompt, (2) the output of "?" at the Config prompt, (3) the output of "show version":
    FCSwitch01# ?
    Exec commands:
      attach      Connect to a specific linecard
      cd          Change current directory
      cfs         CFS parameters
      clear       Reset functions
      cli         CLI commands
      clock       Manage the system clock
      config      Enter configuration mode
      dir         List files in a directory
      discover    Discover information
      exit        Exit from the EXEC
      fcping      Ping an N-Port
      fctrace     Trace the route for an N-Port.
      find        Find a file below the current directory
      no          Disable debugging functions
      ping        Send echo messages
      pwd         View current directory
      send        Send message to open sessions
      show        Show running system information
      sleep       Sleep for the specified number of seconds
      ssh         SSH to another system
      tail        Display the last part of a file
      telnet      Telnet to another system
      terminal    Set terminal line parameters
      test        Test command
      traceroute  Trace route to destination
    FCSwitch01(config)# ?
    Configure commands:
      cli        CLI configuration commands
      do         EXEC command
      end        Exit from configure mode
      exit       Exit from configure mode
      hw-module  Enable/Disable OBFL information
      no         Negate a command or set its defaults
      username   Configure user information.
    FCSwitch01# show version
    Software
      BIOS:      version 1.0.12
      kickstart: version 3.3(1c)
      system:    version 3.3(1c)
      BIOS compile time:       09/10/07
      kickstart image file is: bootflash:/m9100-s2ek9-kickstart-mz.3.3.1c.bin
      kickstart compile time:  5/23/2008 19:00:00 [06/20/2008 04:29:52]
      system image file is:    bootflash:/m9100-s2ek9-mz.3.3.1c.bin
      system compile time:     5/23/2008 19:00:00 [06/20/2008 04:51:10]
    Hardware
      cisco MDS 9124 ("1/2/4 Gbps FC/Supervisor-2")
      Motorola, ppc8541 (e500) with 515032 kB of memory.
      Processor Board ID JAE1133U87Q
      bootflash: 250368 kB
    FCSwitch01   kernel uptime is 2 days 0 hour 24 minute(s) 48 second(s)

    Hi Jon,
    Do you have access to the radius server?  Can you set the shell:roles="network-admin" attribute on your account?
    Unfortunately if you don't remember the password of any accounts with network-admin you will need to do a password recovery which is a disruptive process.  Below are the instructions for the MDS:
    Power Cycling the Switch
    If you cannot start a session on the switch that has network-admin privileges, you must recover the administrator password by power cycling the switch.
    Caution This procedure disrupts all traffic on the switch. All connections to the switch will be lost for 2 to 3 minutes.
    Note You cannot recover the administrator password from a Telnet or SSH session. You must have access to the local console connection. See the "Starting a Switch in the Cisco MDS 9000 Family" section on page 5-2 for information on setting up the console connection.
    To recover a administrator password by power cycling the switch, follow these steps:
    Step 1 For Cisco MDS 9500 Series switches with two supervisor modules, remove the supervisor module in
    slot 6 from the chassis.
    Note On the Cisco MDS 9500 Series, the password recovery procedure must be performed on the active supervisor module. Removing the supervisor module in slot 6 ensures that a switchover will not occur during the password recovery procedure.
    Step 2 Power cycle the switch.
    Step 3 Press the Ctrl-] key sequence when the switch begins its Cisco NX-OS software boot sequence to enter the switch(boot)# prompt mode.
    Ctrl-]
    switch(boot)#
    Step 4 Change to configuration mode.
    switch(boot)# config terminal
    Step 5 Issue the admin-password command to reset the administrator password.
    switch(boot-config)# admin-password <new password>
    For information on strong passwords, see the "Characteristics of Strong Passwords" section.
    Step 6 Exit to the EXEC mode.
    switch(boot-config)# exit
    switch(boot)#
    Step 7 Issue the load command to load the Cisco NX-OS software.
    switch(boot)# load bootflash:m9500-sf1ek9-mz.2.1.1a.bin
    Caution If you boot a system image that is older than the image you used to store the configuration and do not use the install all command to boot the system, the switch erases the binary configuration and uses the ASCII configuration. When this occurs, you must use the init system command to recover your password.
    Step 8 Log in to the switch using the new administrator password.
    switch login: admin
    Password: <new password>
    Step 9 Reset the new password to ensure that is it is also the SNMP password for Fabric Manager.
    switch# config t
    switch(config)# username admin password <new password>
    switch(config)# exit
    switch#
    Step 10 Save the software configuration.
    switch# copy running-config startup-config
    Step 11 Insert the previously removed supervisor module into slot 6 in the chassis.

  • Cisco MDS 9148 compatibility with Finisar FTLF-8524-P2BNV SFP+

    Hello,
    I have a Cisco MDS 9148 switch with Finisar FTLF-8524-P2BNV SFP+ modules. I am told by the guys configuring the equipment that these modules are not identified in the switch interface.
    I am curious if there could be a compatibility problem (I have not found a compatibility list) or any other issue which could cause the behaviour.
    Thank you

  • Create port channel between UCS-FI and MDS 9124 (F Mode)

    Dear Team,
    We were trying to create  port channel between UCS FI and MDS 9124
    But the port channel not getting active in F mode on MDS 9124
    FI is in FC End Host Mode
    We have enabled FC uplink trunking on FI
    We have enabled NPIV on MDS
    We have enabled trunk on MDS
    FI and MDS in default VSAN
    To check we changed the FI mode to FC Switching mode and port channels became active but in E mode
    when we enabled FC uplink trunking on FI and FC Switching mode port channels became active in TE mode
    but in both the above cases showflogi database shows WWPN of SAN alone not showing any from FI.
    How to achive this?
    Have read that no need to change the swicthing mode to FC Switching mode and keep as FC Endhost mode
    SO how to achieve Port channel with F mode in MDS and FI ( Mode showing as NProxy)
    Does it has to do anything with MDS NX-OS version? (https://supportforums.cisco.com/thread/2179129)
    If yes how to upgrade as license for ports came along with Device and we do not have any PAC/PAK or license file as it came
    with license
    Also we have seen 2 files availabe for download (m9100-s2ek9-kickstart-mz.5.2.8b.bin and m9100-s2ek9-mz.5.2.8b.bin) which to use
    Thanks and Regards
    Jose

    Hi Jo Bo,
    what version of software if your MDS running?
    On your UCS do connect nxos and show inteface brieft and look at the mac address.
    it is possible that you might be hitting the bug below. if this is the case you might need to upgrade the firmware on your MDS.
    Add MAC OUI "002a6a", "8c604f", "00defb" for 5k/UCS-FI
    http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCty04686
    Symptom:
    Nexus switch unable to connect any other Nexus or other Cisco Switch in NPV mode with a F port-channel.   Issue might be seen in earlier 5.1 releases like
    5.1.3.N1.1a
    but not the latest
    5.1.3.N2.1c
    release. Issue is also seen in
    5.2(1)N1(1)
    and
    6.0(2)N1(1)
    and later releases.
    Conditions:
    Nexus configured for SAN PortChannels or NPIV trunking mode Nexus connected to UCS via regular F port channel where UCS in NPV mode  NPV edge switch: Port WWN OUI from UCS FI  or other Cisco manufactured switch:  xx:xx:00:2a:6a:xx:xx:xx   OR  xx:xx:8c:60:4f:xx:xx:xx
    Workaround:
    Turn-off trunking mode on Nexus 5k TF-port Issue does not happen with standard  F-PORT Remove SAN Portchannel config
    Further Problem Description:
    To verify the issue please collect  show flogi internal event-history errors  Each time the port is attempted OLS, NOS, LRR counters will increment. This can be determined via the following output,  show port internal info all show port internal event-history errors

  • Cisco MDS port channel with USC FI

    Hello,
    Can anyone help me to configure/troubleshoot Cisco MDS 9148 with Cisco USC ? M stuck in port channel..i have configured but interfaces are not coming UP.It is showing init state.
    My Topology is like,
    Nexus 5000-->USC FI (single FI) -->Cisco MDS 9148
                                                     --> Two Chassis
    Any help would be highly appreciated...
    Thanx

    TMC-UCSFI-A-A(nxos)# sh interface brief
    Interface  Vsan   Admin  Admin   Status          SFP    Oper  Oper   Port
                      Mode   Trunk                          Mode  Speed  Channel
                             Mode                                 (Gbps)
    fc1/31     1      NP     off     errDisabled      swl    --           --
    fc1/32     1      NP     off     errDisabled      swl    --           --
    Ethernet      VLAN   Type Mode   Status  Reason                   Speed     Port
    Interface                                                                   Ch #
    Eth1/1        1      eth  fabric up      none                        10G(D) --
    Eth1/2        1      eth  fabric up      none                        10G(D) --
    Eth1/3        1      eth  fabric up      none                        10G(D) --
    Eth1/4        1      eth  fabric up      none                        10G(D) --
    Eth1/5        1      eth  access down    SFP not inserted            10G(D) --
    Eth1/6        1      eth  access down    SFP not inserted            10G(D) --
    Eth1/7        1      eth  access down    SFP not inserted            10G(D) --
    Eth1/8        1      eth  access down    SFP not inserted            10G(D) --
    Eth1/9        1      eth  access down    SFP not inserted            10G(D) --
    Eth1/10       1      eth  access down    SFP not inserted            10G(D) --
    Eth1/11       1      eth  access down    SFP not inserted            10G(D) --
    Eth1/12       1      eth  access down    SFP not inserted            10G(D) --
    Eth1/13       1      eth  access down    SFP not inserted            10G(D) --
    Eth1/14       1      eth  access down    SFP not inserted            10G(D) --
    Eth1/15       1      eth  trunk  up      none                        10G(D) 100
    Eth1/16       1      eth  trunk  up      none                        10G(D) 100
    Eth1/17       1      eth  fabric up      none                        10G(D) --
    Eth1/18       1      eth  fabric up      none                        10G(D) --
    Eth1/19       1      eth  fabric up      none                        10G(D) --
    Eth1/20       1      eth  fabric up      none                        10G(D) --
    Eth1/21       1      eth  access down    SFP not inserted            10G(D) --
    Eth1/22       1      eth  access down    SFP not inserted            10G(D) --
    Eth1/23       1      eth  access down    SFP not inserted            10G(D) --
    Eth1/24       1      eth  access down    SFP not inserted            10G(D) --
    Eth1/25       1      eth  access down    SFP not inserted            10G(D) --
    Eth1/26       1      eth  access down    SFP not inserted            10G(D) --
    Eth1/27       1      eth  access down    SFP not inserted            10G(D) --
    Eth1/28       1      eth  access down    SFP not inserted            10G(D) --
    Eth1/29       1      eth  access down    SFP not inserted            10G(D) --
    Eth1/30       1      eth  access down    SFP not inserted            10G(D) --
    output ommitted
    TMC-UCSFI-A-A(nxos)#
    Here it shows that Fc1/31- 32 which are in trunk , status is errdisabled and admin trunk mode is off

  • Cisco 3925 and SFP modules

    I'm trying to install a MGBSX1 into the Cisco 3925 but it's doesn't seem it's detecting it for some reason.
    I've changed media type and I've tested with another SFP module (GLC-SX-MM) which works fine.
    Am I missing a command to enable this type of module on the Cisco 3925?
    Thanks

    Hi,
    Looking at the SFP compatability table for 39XX series routers.
    http://www.cisco.com/c/en/us/products/routers/3900-series-integrated-services-routers-isr/relevant-interfaces-and-modules.html#formfactor
    The MGBSX1 is NOT mentioned
    Looks like the MGBSX1 is only compatable with the Small Business switch family.
    http://www.cisco.com/c/dam/en/us/td/docs/interfaces_modules/csbna/mgb/quick_start/guide/Optical_Module_QSG_en-US.pdf
    Regards
    Alex

  • SG200 SFP Compatibility

    Hello,
    We want to connect SG200 to Catalyst 2960X via optical fibre. Now on our SG200 (SG200-50P-K9-EU) switches are using D-Link DEM-311GT SFP modules.
    We found module Cisco GLC-SX-MMD, that is compatible with Catalyst series switches, but there's no info about Small Business series. Someone has tried to run this module on Cisco SB?

    Hello,
    SG200 series support these SFP:
    http://www.cisco.com/c/en/us/products/collateral/switches/small-business-100-series-unmanaged-switches/data_sheet_c78-634369.html
    Product Ordering Number
    Description
    MFE Transceivers
    MFEBX1
    100BASE-BX-20U SFP transceiver for single-mode fiber, 1310 nm wavelength, supports up to 20 km
    MFELX1
    100BASE-LX SFP transceiver for single-mode fiber, 1310 nm wavelength, supports up to 2 km
    MFEFX1
    100BASE-FX SFP transceiver for multimode fiber, 1310 nm wavelength, supports up to 10 km
    MGE Transceivers
    MGBBX1
    1000BASE-BX-20U SFP transceiver for single-mode fiber, 1310 nm wavelength, supports up to 40 km
    MGBLH1
    1000BASE-LH SFP transceiver for single-mode fiber, 1310 nm wavelength, supports up to 40 km
    MGBLX1
    1000BASE-LX SFP transceiver for single-mode fiber, 1310 nm wavelength, supports up to 10 km
    MGBSX1
    1000BASE-SX SFP transceiver for multimode fiber, 850 nm wavelength, supports up to 550 m
    This link provides compatibility information:
    https://supportforums.cisco.com/document/140221/interconnect-cisco-sb-switch-and-catalyst-switch-sfp
    To interconnect a Small Business switch with Cisco Catalyst switch, you need to use Cisco Small Business SFP on the Small Business switches, and Cisco traditional SFP on Catalyst switches. And the SFP on both sides should follow the same IEEE standard. The mapping table is shown below.
    Cisco Small Business SFP
    Cisco traditional SFP
    GE Transceiver
    MGBSX1
    GLC-SX-MM
    SFP-GE-S
    MGBLX1
    MGBLH1
    GLC-LH-SM
    MGBBX1
    GLC-BX-D
    MGBT1
    GLC-T
    SFP-GE-T
    FE Transceiver
    MFEFX1
    GLC-FE-100FX
    GLC-GE-100FX
    MFELX1
    GLC-FE-100LX
    MFEBX1
    GLC-FE-100BX-D
    Thanks.
    Yiu Kay Lee
    Concentrix at Cisco
    .:|:.:|:. CISCO | Yiu Kay Lee | SMB Pre-Sales | [email protected] | Phone +1 (855) 354-7776

  • Shoul I upgrade MDS 9222i and MDS 9124 both have SANOS 3.3.2 to 3.3.5?

    Hi guys,
    I have 2 MDS 9222i, 2 MDS 9124 and 10 MDS Blades Switches (IBM Blades) all have SANOS 3.3.2.
    All those swicthes are attached to external drives (IBM DS4800) IBM requested to upgrade this DS4800 firmware level but in order to do that they told me that I need a new SANOS I plan to upgrade it to SANOS 3.3.5 can someone tell me if this SANOS works alright? or What SANOS do yoy recommend me?
    Thanks in advance

    The Cisco TAC will always defer to your Original Storage provided when asked which
    image to run, as they (the Original Storage providers) qualify our images for use with their
    devices.
    Regards,
    Ken

  • 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

  • Enabling NPIV in CISCO MDS 9500 Series

                       Hello!!!
    If i could get the response for my query.
    I need to enable NPIV as we have VM's to be created and allocate SAN storage to them so my CISCO MDS needs to have NPIV enabled. Following queries linked with this:
    1. Can i enabled NPIV on single Fibre Channel Port or it gets enabled on the complete SAN Switch
    2. Does enabling NPIV impact any other SAN operation. Also my 2- sites are connected via ISL, so is it important to enable NPIV across all my sites or i can enable it only at 1 site where my VM hosts are located.
    3. Any reference document for NPIV and related zoning concept.
    Thanks in advance.
    Faizul Mufti
    9958766711

    Hi,
    1. Can i enabled NPIV on single Fibre Channel Port or it gets enabled on the complete SAN Switch
    whole switch
    feature npiv
    2. Does enabling NPIV impact any other SAN operation. Also my 2- sites are connected via ISL, so is it important to enable NPIV across all my sites or i can enable it only at 1 site where my VM hosts are located.
    Will not impact any other SAN operation.  Non-disruptive.
    "feature npiv" is local to the switch, not fabric wide.  Use this command on any switch you want multiple flogi's on a single interface.
    3. Any reference document for NPIV and related zoning concept.
    I suggest zoning by pwwn
    Regards,
    David

  • ISCSI-to-FC routing in Cisco MDS 9000 Family

    Hi,
    I'm puzzled about support for iSCSI-to-FC routing in the MDS 9000 family. Earlier hardware such as the 9216i switch and the MPS-14/2 module had a feature to allow an iSCSI Initiator to connect transparently to an FC target. This equipment is now EOL and has been replaced by models such as the 9222i switch and the 18/4 Port Multiservice Module. The datasheets for these replacements strongly imply that they support iSCSI-to-FC routing in a similar way to the earlier products - for example "iSCSI for extension of the SAN to Ethernet attached servers - Extends the benefits of Fibre Channel SAN-based storage to Ethernet attached servers".
    I tried to find some hard technical info to confirm this. Chapter 4, "Configuring iSCSI" in "Cisco MDS 9000 Family NX-OS IP Services Configuration Guide Release 5.0(1a)" says that the feature is only available on the IP Storage Module, the 9216i switch, and the MPS-14/2 module, all of which are now EOL. It doesn't mention the replacement models in connection with this functionality, though they are mentioned elsewhere in the book for other features such as FC over IP. I've searched for documentation of the iSCSI support on the new models and the only document which seems relevant is this chapter - but it says it doesn't apply to these models.
    Do the replacement models support iSCSI-to-FC routing or not? The datasheets use wording nearly identical to the earlier models in this area, so I assume they do. If they do, how is it configured and where is it documented? I sent feedback on this to the documentation feedback address a while ago, but haven't had a reply.
    Many Thanks,
                                jjf

    The "Configuring iSCSI" chapter in both 3.3.3 and 4.1.1 documentation similarly talk about IPS and 14/2 modules but make no mention of 18/4, however I've used iSCSI on the 18/4 with both releases. I can only guess the same is true for 5.0 since I have yet to load 5.0 on any switches.
    In terms of other documentation I don't think there is any, but all the required information is presented in the "Configuring iSCSI" chapters however it's not the easiest thing to understand from the documentation. Following is the overview I sent to a teammate on how to setup iSCSI.
    1. configure Ethernet ports with ip addresses
      1a. add a route to the host, iSCSI client, via the gigabit interface 2. enable iscsi on the switch
      2a. enable iscsi on the module with the gige port
      2b. 'no shut' the iscsi interface corresponding to gige port
          e.g. gige3/4 -> iscsi3/4
      2c. no additional configuration of the interfaces is needed, although at some point turning on authentication would be a good idea
    3. create iscsi initiator
      3a. use the clients ip address as the initiator name, using the node name would be better but I haven't tried it that way so ymmv
          e.g. 'iscsi initiator ip-address xxx.xxx.xxx.xxx'
      3b. use a "system assigned" nwwn and set it static
          e.g. 'static pWWN system-assign'
      3c. allocate one "system assigned" pwwn and set it static
          e.g. 'static pWWN system-assign 1'
      3d. assign vsans, an iscsi initiator can be in more than one vsan
          e.g. 'vsan xxx'
    4. create targets
       spcsw1(config)# iscsi virtual-target name iqn.000190300646.fa02cb
       spcsw1(config-iscsi-tgt)# pwwn 50:06:04:8a:d5:f0:79:a1
       spcsw1(config-iscsi-tgt)# initiator ip address xx.xx.xx.xx permit
    5. zone the iscsi initiator's pwwn to the target pwwns, use 'sh iscsi initiator configured' to see the pwwn
    6. configure the hosts iscsi initiator, usually not much more than specifying the ip address of the gige port on the MDS

Maybe you are looking for