Cisco MDS 9148 fcalias PWWN update

One of the network/hba modules died on one of our blade and we had to replace it. Because of this I need to update the PWWN for the FCALIAS. It's been a while but I think it is simple as getting in to the fcalias, adding the new pwwn and removing the old one. Can someone please verify or correct?
config t
fcalias name BLADE_ESX_HBA1 vsan 2
  no pwwn 10:00:00:00:00:00:00:60
     pwwn 10:00:00:00:00:00:d0:60
Any suggestions or best practices are welcome! thanks. 

Hi Dennis,
If zone mode is "basic":
switch# show zone status vsan 2
VSAN: 2 default-zone: deny distribute: active only Interop: default
    mode: basic merge-control: allow
    session: none
    hard-zoning: enabled broadcast: unsupported
    smart-zoning: disabled
    rscn-format: fabric-address
switch# conf t
Enter configuration commands, one per line.  End with CNTL/Z.
switch(config)# fcalias name BLADE_ESX_HBA1 vsan 2
switch(config-fcalias)# no member pwwn 10:00:00:00:00:00:00:60
switch(config-fcalias)# member pwwn 10:00:00:00:00:00:d0:60
switch(config-fcalias)# end
switch# show fcalias vsan 2
fcalias name BLADE_ESX_HBA1 vsan 2
  pwwn 10:00:00:00:00:00:d0:60
switch#  copy running-config startup-config
If zone mode is "enhanced":
switch# show zone status v 2
VSAN: 2 default-zone: deny distribute: full Interop: default
    mode: enhanced merge-control: allow
    session: none
    hard-zoning: enabled broadcast: unsupported
    smart-zoning: disabled
    rscn-format: fabric-address
switch# conf t
Enter configuration commands, one per line.  End with CNTL/Z.
switch(config)# fcalias name BLADE_ESX_HBA1 vsan 2
switch(config-fcalias)# no member pwwn 10:00:00:00:00:00:00:60
Enhanced zone session has been created. Please 'commit' the changes when done.
switch(config-fcalias)# member pwwn 10:00:00:00:00:00:d0:60
switch(config-fcalias)# exit
switch(config)# zone commit vsan 2
switch(config)# exit
switch# show fcalias vsan 2
fcalias name BLADE_ESX_HBA1 vsan 2
  pwwn 10:00:00:00:00:00:d0:60
switch#  copy running-config startup-config

Similar Messages

  • Cisco MDS 9148 Inventory Collection

    Hi
    I get the following error on an inventory collection of a MDS 9148 (NOS 5.0.4). I have tried deleting and recreating the device.
    RME 4.3.1
    RICS0001:Internal Error,unable to process the collected data from the device.
    [ Thu Dec 30  13:48:46 GMT 2010 ],INFO ,[Thread-15],com.cisco.nm.rmeng.util.logger.XDILogger,77,com.cisco.nm.xms.xdi.pkgs.LibInventory.PortInterfaceAGI_RFC1213_HelperMethods,getIfTableEntriesFromDevice,759,Entry speed after if block: 1000000000 Index value : 101191680
    [ Thu Dec 30  13:48:46 GMT 2010 ],INFO ,[Thread-15],com.cisco.nm.rmeng.util.logger.XDILogger,77,com.cisco.nm.xms.xdi.pkgs.SharedInventoryWireless.AssetAGI_CISCO_ENTITY_ASSET_Mib,g$eval,58,com.cisco.nm.xms.xdi.pkgs.SharedInventoryWireless:AssetAGI_CISCO_ENTITY_ASSET_MIB:g$eval:populating AssetAG attributes, begins...
    [ Thu Dec 30  13:48:53 GMT 2010 ],ERROR,[Thread-15],com.cisco.nm.rmeng.util.logger.XDILogger,57,com.cisco.nm.xms.xdi.pkgs.SharedInventoryWireless.AssetAGI_CISCO_ENTITY_ASSET_Mib,g$eval,64,com.cisco.nm.xms.xdi.pkgs.SharedInventoryWireless:AssetAGI_CISCO_ENTITY_ASSET_MIB:g$eval:AssetAG Collection aborted com.cisco.nm.xms.xdi.ags.system.CollectionFailedDeviceSensed: java.lang.ArrayIndexOutOfBoundsException: 5 >= 5
    [ Thu Dec 30  13:48:55 GMT 2010 ],INFO ,[Thread-15],com.cisco.nm.rmeng.inventory.ics.core.CollectionController,549,DP time is 20 seconds for 172.23.32.129
    [ Thu Dec 30  13:48:55 GMT 2010 ],ERROR,[Thread-15],com.cisco.nm.rmeng.inventory.ics.server.InvDataProcessor,458,
    java.lang.NullPointerException
    at com.cisco.nm.rmeng.inventory.ics.invdata.containment.ContainmentAGInvData.compare(ContainmentAGInvData.java:103)
    at com.cisco.nm.rmeng.inventory.ics.server.InvDataProcessor.processContainmentAG(InvDataProcessor.java:864)
    at com.cisco.nm.rmeng.inventory.ics.server.InvDataProcessor.processInvData(InvDataProcessor.java:330)
    at com.cisco.nm.rmeng.inventory.ics.core.CollectionController.run(CollectionController.java:923)
    at java.lang.Thread.run(Thread.java:595)
    [ Thu Dec 30  13:48:55 GMT 2010 ],ERROR,[Thread-15],com.cisco.nm.rmeng.inventory.ics.core.CollectionController,935, Exception occured in process method while processing: 172.23.32.129 null
    ICSException
    at com.cisco.nm.rmeng.inventory.ics.server.InvDataProcessor.processInvData(InvDataProcessor.java:473)
    at com.cisco.nm.rmeng.inventory.ics.core.CollectionController.run(CollectionController.java:923)
    at java.lang.Thread.run(Thread.java:595)
    [ Thu Dec 30  13:48:55 GMT 2010 ],INFO ,[Thread-15],com.cisco.nm.rmeng.inventory.ics.core.CollectionController,1191,No Trap
    [ Thu Dec 30  13:48:55 GMT 2010 ],INFO ,[Thread-15],com.cisco.nm.rmeng.inventory.ics.core.CollectionController,1203,CALLING SELF TEST
    [ Thu Dec 30  13:48:55 GMT 2010 ],INFO ,[Thread-15],com.cisco.nm.rmeng.inventory.ics.core.CollectionController,1207,DONE WITH SELF TEST

    Hi Naem,
    have just read the othre reply's, the intresting bit it is in the MDF.
    - <DEVICE NAME="Cisco  MDS 9148 Multilayer Fabric Switch" MDFID="282867260" CISCOMDFID="282867260">
    <SYSOID OID="1.3.6.1.4.1.9.12.3.1.3.841" NAME="OID:1.3.6.1.4.1.9.12.3.1.3.841" />
    The device adds ok, I just can not run an Inventory but can run a backup !
    Thanks

  • Using Cisco MDS 9148 switch for switching and routing

    Hi Gurus,
    Can you please advice me! Can i configure interface trunking, routing and dhcp services on the Cisco MDS 9148 switch?
    Thanks for your response!!

    Tommy,
    MDS9148 is a Storage SAN Fibre Channel switch, it doesn't support Ethernet, IP, VLANs, VLAN trunking, 802.1Q, IP routing, DHCP. It's meant for Fibre Channel connectivity between Fibre Channel server HBAs and Fibre Channel storage.
    Roman

  • 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

  • Login CLI Cisco MDS 9148 Multilayer

    When I try to enter the Cisco MDS 9148 Multilayer switch through the command line, new is not yet configured, shows the following message:
    mdssw4 login: cisco                   
    Password:         
    Login incorrect               
        THIS IS A DEPARTMENT OF DEFENSE  COMPUTER  SYSTEM.  THIS COMPUTER SYSTEM                                                                            
        AND ALL RELATED  EQUIPMENT AND NETWORKS ARE PROVIDED ONLY FOR AUTHORIZED                                                                            
        US GOVERNMENT USE.  DOD COMPUTER SYSTEMS MAY BE MONITORED FOR ALL LAWFUL                                                                            
        PURPOSES,  INCLUDING  ENSURING  AUTHORIZED  USE, FOR  MANAGEMENT  OF THE                                                                            
        SYSTEM, TO FACILITATE  PROTECTION  AGAINST  UNAUTHORIZED  ACCESS, AN                                                                      
        VERIFY  SECURITY  FEATURES OR  PROCEDURES.  ALL  INFORMATION,  INCLUDING                                                                            
        PERSONAL  INFORMATION,  PLACED  ON OR  SENT  OVER  THIS  SYSTEM,  MAY BE                                                                            
        MONITORED.              
        USE OF THIS DOD COMPUTER SYSTEM, AUTHORIZED OR UNAUTHORIZED, CONSTITUTES                                                                            
        CONSENT TO MONITORING OF THIS SYSTEM.  UNAUTHORIZED  USE MAY SUBJECT YOU                                                                            
        TO CRIMINAL  PROSECUTION.  EVIDENCE OF UNAUTHORIZED USE COLLECTED DURING                                                                            
        MONITORING  MAY BE USED FOR  ADMINISTRATIVE,  CRIMINAL, OR OTHER ADVERSE                                                                            
        ACTION.      
    how do I get the username and password.

    good one ;)

  • Cisco MDS 9148 compatibity with EMC VNX 5300

    Hi Cisco ,
    We have 2 MDS 9148 switches running on NX-OS 5.0(1a). These switches are connected to EMC VNX 5300 currently running on 05.31 version.
    We are planning to upgrade both Switches and VNX. 
    So my query to you guys is, I am thinking to upgrade Switch to NX-OS 5.2(8c). Will this 5.2(8c) support the VNX 5300 05.32 version.
    Please suggest.
    Pranav.

    Please check
    http://www.emc.com/interoperability
    and
    http://www.cisco.com/c/en/us/td/docs/switches/datacenter/mds9000/interoperability/matrix/intmatrx/Matrix1.html

  • Interconnecting MDS 9148 with 2 different Fiber Providers

    Hi
    I would like discuss the following issue :
    We have 2 HP SAN EVA 8400 ( one at the production site and one at our Disaster Recovery site ) replicating using a fiber channel service from ( 2* FC dark fiber from PROVIDER A )
    They are linked together  with 4 Cisco MDS 9148 Multilayer Fabric Switch (2 fabric ). 
    We have recently purchased a new fiber service ( 2* 1Gb FC managed service from PROVIDER B) in order to create a port channel  with the 2 running ones and we have some problem.
    We disconnected the PROVIDER A FC ( running for 10 years now )  and left the SAN replication during a couple of days running with the new PROVIDER B 1 Gb FC to make sure the link was stable and we had no issue.
    Then we tried to connect the 2 FC together from the 2 providers and tried to create a Port channel.
    However we discovered that to create a PortChannel, interfaces must have the same configurations ( speed, mode, rate )
    In our case , the interface FC 1/1 using PROVIDER A link is running at 4 Gb and the interface FC 1/2 using PROVIDER B is running at 1 Gb
    PROVIDER A dark fiber
    PROVIDER B fiber managed service
    fc1/1 is trunking
        Hardware is Fibre Channel, SFP is CWDM-1550
        Port WWN is 20:01:00:05:9b:72:b1:60
        Peer port WWN is 20:01:00:05:9b:72:b1:a0
        Admin port mode is E, trunk mode is on
        snmp link state traps are enabled
        Port mode is TE
        Port vsan is 1
        Speed is 4 Gbps
        Rate mode is dedicated
        Transmit B2B Credit is 32
        Receive B2B Credit is 32
        B2B State Change Number is 14
        Receive data field Size is 2112
        Beacon is turned off
        Trunk vsans (admin allowed and active) (1)
        Trunk vsans (up)                       (1)
        Trunk vsans (isolated)                 ()
        Trunk vsans (initializing)             ()
        5 minutes input rate 4416 bits/sec, 552 bytes/sec, 6 frames/sec
        5 minutes output rate 91616 bits/sec, 11452 bytes/sec, 11 frames/sec
          51537358280 frames input, 50955393731852 bytes
            0 discards, 0 errors
            0 CRC,  0 unknown class
            0 too long, 0 too short
          223256095067 frames output, 408667816663528 bytes
            32 discards, 0 errors
          34 input OLS, 36 LRR, 51 NOS, 0 loop inits
          53 output OLS, 35 LRR, 45 NOS, 0 loop inits
          32 receive B2B credit remaining
          32 transmit B2B credit remaining
          28 low priority transmit B2B credit remaining
        Interface last changed at Fri Dec 14 17:02:48 2012
    fc1/2 is trunking
        Hardware is Fibre Channel, SFP is short wave laser w/o OFC (SN)
        Port WWN is 20:02:00:05:9b:72:b1:60
        Peer port WWN is 20:02:00:05:9b:72:b1:a0
        Admin port mode is E, trunk mode is on
        snmp link state traps are enabled
        Port mode is TE
        Port vsan is 1
        Speed is 1 Gbps
        Rate mode is dedicated
        Transmit B2B Credit is 32
        Receive B2B Credit is 32
        B2B State Change Number is 14
        Receive data field Size is 2112
        Beacon is turned off
        Trunk vsans (admin allowed and active) (1)
        Trunk vsans (up)                       (1)
        Trunk vsans (isolated)                 ()
        Trunk vsans (initializing)             ()
        5 minutes input rate 48 bits/sec, 6 bytes/sec, 0 frames/sec
        5 minutes output rate 48 bits/sec, 6 bytes/sec, 0 frames/sec
          39496053 frames input, 2696451760 bytes
            0 discards, 0 errors
            0 CRC,  0 unknown class
            0 too long, 0 too short
          167653989 frames output, 230540944084 bytes
            70 discards, 0 errors
          40377 input OLS, 345 LRR, 4248 NOS, 0 loop inits
          5186 output OLS, 1154 LRR, 39568 NOS, 0 loop inits
          32 receive B2B credit remaining
          32 transmit B2B credit remaining
          28 low priority transmit B2B credit remaining
        Interface last changed at Fri Dec 14 16:50:42 2012
    So we tried to force the FC 1/1 to run at 1 Gb ( same speed as FC 1/2 ) to create the PortChannel, by doing the basic command on the interface : Switchport speed 1000
    Since that , our SAN is logging every 10/15 minutes the following errors :
    ---------- Problem Found: CUST: CA informational: EVA8400_LIVE: Write resources on the inter site link have been reduced. at Fri 14 Dec 2012 17:21:04 GMT+01:00 ----------
    ---------- Problem Found: CUST: CA warning: EVA8400_DR: Excessive out of order message rate on the inter site link. at Fri 14 Dec 2012 17:27:04 GMT+01:00 ----------
    ---------- Problem Found: CUST: CA warning: EVA8400_DR: Excessive data exchange retry rate on the inter site link. at Fri 14 Dec 2012 17:41:34 GMT+01:00 ----------
    ---------- Problem Found: CUST: CA warning: EVA8400_LIVE: Excessive data exchange retry rate on the inter site link. at Fri 14 Dec 2012 17:41:49 GMT+01:00 ----------
    We have the following questions :
    Have you already seen that kind of situation ?
    Is there a best practice  to reduce the interface speed in order to create the PortChannel with identical interface setup ?
    Your help and advice would be much appreciated.
    Regards

    the RTT delay by each link is different and this is causing packets to arrive out of order.
    not sure if port channeling between two different links or different characteristics is good practive.

  • How to use syslog with a MDS 9148

    Hi,
    I'm looking for some informations regarding MDS-9148 and syslog.  I need for some security needs, to send the events of a cisco MDS-9148 into a syslog server.
    I did the following commands:
    config t
    logging server xxx.xxx.xxx.xxx
    logging commit 
    --> When i executed the command "logging commit", the switch has return to me the following error message:
         CFS distribution is not enabled for logging
    It's a FC switch, so the only IP link should be for the management.
    Must i do something related with CFS to enable logging events to syslog server ?  I've checked with our network admin that uses Nexus switch and he doesn't seem to use CFS for it's logging to a syslog server.
    Thank you,
    Chris

    Hi Paresh,
    Thank you for you answer.  It confirm what our network admin showed me.  However, it is not working i'm still getting the the message: CFS distribution is not enabled for logging
    If i run the command: show cfs status, i receive the following information
    Distribution : Enabled
    Distribution over IP : Disabled
    IPv4 multicast address : xxx.xxx.xxx.xxx
    IPv6 multicast address : xxxx::xxxx:xxxx
    Distribution over Ethernet : Disabled
    We are pretty sure we aren't using CFS.  In one of our datacenter, we got 2 switchs 9148 configured with NPV.  The other datacenter  has only 1 switch per fabric. 
    Am i getting the CFS message because it is actually "Enabled" ?
    I did a show runnin-config cfs, to see if there was a configuration done of CFS, but there is none.
    Can i "Disable" it without causing issue ?
    Thank you for the help you can provide,
    Chris

  • 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

  • Fabric Interconnect To MDS 9148 FC Port Channel/Trunks

    Is it possible to create both a Port Channel and Trunk on a Cisco MDS 9148? Yes correct?
    Or can I only trunk between the 2 MDS switches and not the MDS to Fabric Interconnect?
    These FC links would be connected to a 2248XP Fabric Interconnect carrying multiple VSANs from the MDS to the Fabric Interconnect.
    Thanks

    Hello,
    Yes, you can have trunk links grouped into port channel ( F port-channel trunking ) between FI and MDS.
    http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/gui/config/guide/2.0/b_UCSM_GUI_Configuration_Guide_2_0_chapter_0101.html
    Padma

  • 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

  • Cisco MDS 9418 switch doubt

    Hi Team,
    We have an issue, whether the cisco MDS 9418 switch supports FCIP feature.
    We are planning to migrate the data from our old data center over WAN to the EMC VNX storage box in other location.
    In our old data center we have 2 FC cisco switches connected to the EMC clariion storage array. Inorder to replicate data from clariion box to EMC VNX box over WAN ,it can be done via FCIP.
    I wanted to know if we can use insert the FCIP converters into these MDS 9418 switch or do we need to have separate FCIP converters.
    Do we need FCIP converters on both sides for doing replication over FCIP.
    For clear understanding please see the attachment.
    Will waiting for your response......
    Regards,
    Pranav.

    Hi,
    Since the 9148 does not have IP interfaces, something will be needed to tunnel the FC into IP (FCIP) such as an MDS 9222i, which has both FC interfaces and GigE interfaces and supports FCIP.
    Regards,
    David

  • LMS and MDS 9148

    Unable to collect Inventory for a MDS 9148, following error :
    RICS0001:Internal Error,unable to process the collected data from the device.
    I have deleted the item and re-created
    LMS 3.2 ; RME 4.3.1
    MDF and devices up todate.

    Hi Jo,
    This is out of the file 172.23.32.129/130 are the two MDS's
    [ Tue Jun 07  09:31:04 BST 2011 ],INFO ,[Thread-15],com.cisco.nm.rmeng.util.logger.XDILogger,77,com.cisco.nm.xms.xdi.pkgs.SharedInventoryWireless.AssetAGI_CISCO_ENTITY_ASSET_Mib,g$eval,58,com.cisco.nm.xms.xdi.pkgs.SharedInventoryWireless:AssetAGI_CISCO_ENTITY_ASSET_MIB:g$eval:populating AssetAG attributes, begins...
    [ Tue Jun 07  09:31:04 BST 2011 ],INFO ,[Thread-21],com.cisco.nm.rmeng.util.logger.XDILogger,77,com.cisco.nm.xms.xdi.pkgs.SharedInventoryWireless.AssetAGI_CISCO_ENTITY_ASSET_Mib,g$eval,58,com.cisco.nm.xms.xdi.pkgs.SharedInventoryWireless:AssetAGI_CISCO_ENTITY_ASSET_MIB:g$eval:populating AssetAG attributes, begins...
    [ Tue Jun 07  09:31:11 BST 2011 ],ERROR,[Thread-15],com.cisco.nm.rmeng.util.logger.XDILogger,57,com.cisco.nm.xms.xdi.pkgs.SharedInventoryWireless.AssetAGI_CISCO_ENTITY_ASSET_Mib,g$eval,64,com.cisco.nm.xms.xdi.pkgs.SharedInventoryWireless:AssetAGI_CISCO_ENTITY_ASSET_MIB:g$eval:AssetAG Collection aborted com.cisco.nm.xms.xdi.ags.system.CollectionFailedDeviceSensed: java.lang.ArrayIndexOutOfBoundsException: 5 >= 5
    [ Tue Jun 07  09:31:11 BST 2011 ],ERROR,[Thread-21],com.cisco.nm.rmeng.util.logger.XDILogger,57,com.cisco.nm.xms.xdi.pkgs.SharedInventoryWireless.AssetAGI_CISCO_ENTITY_ASSET_Mib,g$eval,64,com.cisco.nm.xms.xdi.pkgs.SharedInventoryWireless:AssetAGI_CISCO_ENTITY_ASSET_MIB:g$eval:AssetAG Collection aborted com.cisco.nm.xms.xdi.ags.system.CollectionFailedDeviceSensed: java.lang.ArrayIndexOutOfBoundsException: 5 >= 5
    [ Tue Jun 07  09:31:12 BST 2011 ],INFO ,[Thread-15],com.cisco.nm.rmeng.inventory.ics.core.CollectionController,549,DP time is 20 seconds for 172.23.32.129
    [ Tue Jun 07  09:31:12 BST 2011 ],ERROR,[Thread-15],com.cisco.nm.rmeng.inventory.ics.server.InvDataProcessor,458,
    java.lang.NullPointerException
        at com.cisco.nm.rmeng.inventory.ics.invdata.containment.ContainmentAGInvData.compare(ContainmentAGInvData.java:103)
        at com.cisco.nm.rmeng.inventory.ics.server.InvDataProcessor.processContainmentAG(InvDataProcessor.java:864)
        at com.cisco.nm.rmeng.inventory.ics.server.InvDataProcessor.processInvData(InvDataProcessor.java:330)
        at com.cisco.nm.rmeng.inventory.ics.core.CollectionController.run(CollectionController.java:923)
        at java.lang.Thread.run(Thread.java:662)
    [ Tue Jun 07  09:31:12 BST 2011 ],ERROR,[Thread-15],com.cisco.nm.rmeng.inventory.ics.core.CollectionController,935, Exception occured in process method while processing: 172.23.32.129 null
    ICSException
        at com.cisco.nm.rmeng.inventory.ics.server.InvDataProcessor.processInvData(InvDataProcessor.java:473)
        at com.cisco.nm.rmeng.inventory.ics.core.CollectionController.run(CollectionController.java:923)
        at java.lang.Thread.run(Thread.java:662)
    [ Tue Jun 07  09:31:12 BST 2011 ],INFO ,[Thread-15],com.cisco.nm.rmeng.inventory.ics.core.CollectionController,1191,No Trap
    [ Tue Jun 07  09:31:12 BST 2011 ],INFO ,[Thread-15],com.cisco.nm.rmeng.inventory.ics.core.CollectionController,1203,CALLING SELF TEST
    [ Tue Jun 07  09:31:12 BST 2011 ],INFO ,[Thread-15],com.cisco.nm.rmeng.inventory.ics.core.CollectionController,1207,DONE WITH SELF TEST
    [ Tue Jun 07  09:31:12 BST 2011 ],INFO ,[Thread-21],com.cisco.nm.rmeng.inventory.ics.core.CollectionController,549,DP time is 20 seconds for 172.23.32.130
    [ Tue Jun 07  09:31:12 BST 2011 ],ERROR,[Thread-21],com.cisco.nm.rmeng.inventory.ics.server.InvDataProcessor,458,
    java.lang.NullPointerException
        at com.cisco.nm.rmeng.inventory.ics.invdata.containment.ContainmentAGInvData.compare(ContainmentAGInvData.java:103)
        at com.cisco.nm.rmeng.inventory.ics.server.InvDataProcessor.processContainmentAG(InvDataProcessor.java:864)
        at com.cisco.nm.rmeng.inventory.ics.server.InvDataProcessor.processInvData(InvDataProcessor.java:330)
        at com.cisco.nm.rmeng.inventory.ics.core.CollectionController.run(CollectionController.java:923)
        at java.lang.Thread.run(Thread.java:662)
    [ Tue Jun 07  09:31:12 BST 2011 ],ERROR,[Thread-21],com.cisco.nm.rmeng.inventory.ics.core.CollectionController,935, Exception occured in process method while processing: 172.23.32.130 null
    ICSException
        at com.cisco.nm.rmeng.inventory.ics.server.InvDataProcessor.processInvData(InvDataProcessor.java:473)
        at com.cisco.nm.rmeng.inventory.ics.core.CollectionController.run(CollectionController.java:923)
        at java.lang.Thread.run(Thread.java:662)
    [ Tue Jun 07  09:31:12 BST 2011 ],INFO ,[Thread-21],com.cisco.nm.rmeng.inventory.ics.core.CollectionController,1191,No Trap
    [ Tue Jun 07  09:31:12 BST 2011 ],INFO ,[Thread-21],com.cisco.nm.rmeng.inventory.ics.core.CollectionController,1203,CALLING SELF TEST
    [ Tue Jun 07  09:31:12 BST 2011 ],INFO ,[Thread-21],com.cisco.nm.rmeng.inventory.ics.core.CollectionController,1207,DONE WITH SELF TEST

  • Two New MDS 9148 - redundancy

    Hi,
    We have two new MDS 9148 switch for our DC. I have little knowlege about cisco MDS Swtiches. I am planning for 1+1 redundancy for this MDS switches.
    Connectivity :
                  ____________MDS SW01 __________Storage      
    Server ----|
                  |____________MDS SW02__________Storage
    1 . what type connection we need to config MDS swtiches ?
    2. How Sw02 know when sw01 fails, need to run any protocol or track any inferface?
    3. Any doc for Cisco Basic best practices for MDS 9148 switch?

    Hi Sankar,
    You will want to setup two seperate fabrics like this:
    A path loss will be be handled by the operating system's multipathing software.
    The config guides are here:
    http://www.cisco.com/en/US/products/ps5989/products_installation_and_configuration_guides_list.html
    Some whitepapers that may help are here (more for larger designs):
    http://www.cisco.com/en/US/products/ps5990/prod_white_papers_list.html

Maybe you are looking for