UCS connection to McData SAN infrastructure

Hi,
I'm trying to connect an UCS to a SAN based on McData SAN switches. I configured the WWN pools and the vHBAs. The SAN Admin told me, NPV is on the port activated and NPIV is supported.
On the swicthes, my WWPNs are visible and the SAN Admin configured the zoning and the presentation already. If I rescan the the SAN on my ESX, I can't see any path or presentated LUNs at all. LIP reset with no success.
in the past, I had access to the whole environment and there was no special configuration to get this working. At this time I was working with Brocade/HP SAN switches. Today I'm only responsible for the UCS an the vSphere environment and the other admins have no experience with UCS.
Any tips or hints will be very helpfull tu get this working. Do I have to make any special configurations? Does anyone have experience with UCS and McData SAN and can share the needed configurations with me?
Kind Regards
Bastian

Hi,
many thanks for your help.
show npv flogi-table shows:
SERVER                                                                  EXTERNAL
INTERFACE VSAN FCID             PORT NAME               NODE NAME       INTERFAC
E
vfc791    1000 0x636215 20:00:00:25:b5:10:a1:00 20:00:00:25:b5:10:c1:00 fc2/1
vfc793    1000 0x636214 20:00:00:25:b5:10:a1:01 20:00:00:25:b5:10:c1:03 fc2/1
vfc795    1000 0x636217 20:00:00:25:b5:10:a1:02 20:00:00:25:b5:10:c1:01 fc2/1
vfc797    1000 0x636218 20:00:00:25:b5:10:a1:03 20:00:00:25:b5:10:c1:02 fc2/1
vfc805    1000 0x636216 20:00:00:25:b5:10:a1:04 20:00:00:25:b5:10:c1:04 fc2/1
UCSM Version is 2.1(3a)
adapter 1/1/1 # connect
adapter 1/1/1 (top):1# attach-fls
adapter 1/1/1 (fls):1# vnic
vnic ecpu type state   lif
8    1    fc   active  5
9    2    fc   active  6
adapter 1/1/1 (fls):2# login 8
lifid: 5
  ID   PORTNAME                 NODENAME                 FID
adapter 1/1/1 (fls):3# lunmap 8
adapter 1/1/1 (fls):4# lunlist 8
% Command not found
adapter 1/1/1 (fls):5# login 9
lifid: 6
  ID   PORTNAME                 NODENAME                 FID
adapter 1/1/1 (fls):6# lunmap 9
adapter 1/1/1 (fls):7#
No output at login doesn't sound good. Is this a fault of PLOGI didn't done correct? lunlist command not found is strange. Did this commend only works after successful login?
Kind Regards
Bastian

Similar Messages

  • Cisco UCS an McData SAN Switch

    Hallo zusammen,
    wir versuchen eine Verbindung zwischen ESX auf einem UCS und einem NetApp Metrocluster herzustellen. SAN Infrastruktur basiert auf McData SAN Switchen.
    In der Vergangenheit habe ich die komplette Infratruktur mit HP/Brocade SAN Switchen administriert ohne Probleme. Hier waren keine speziellen Einstellungen notwendig. WWN Pools und vHBA und die Verbindung stand.
    Der SAN Admin meinte NPV sei auf dem Port aktiviert und NPIV wird unterstützt. Er sieht auch meine WWPNs und hat das Zoning am SAN konfiguriert. Leider sehen unsere ESX Server keine präsentierte LUN.
    Für Tipps und Infos zur notwendigen Konfiguration wäre ich sehr dankbar. vSphere Umgebung läuft auf 5.5, UCS auf 2.1. Ich habe bereits alle Einstellungen unter UCS getestet. Ich habe auch ein bisschen mit den VSANs gespielt, was aber in der Vergangenheit nie notwendig war. FIs laufen im End Host Mode. ESX Rescan zeigt keine Pfade oder Target, LIP hat auch keinerlei Änderungen gebracht.
    Da ich auf die SAN Konfiguration keinen Zugriff habe möchte ich zunächst sicher gehen, dass ich am UCS nichts vergessen habe. Switching Mode sollte kein Thema sein.
    Viele Grüße
    Bastian

    From your putty Logs, I don't see any issues...
    e1/17 and e1/21 are both up.  I also don't see any blocked VLANs.  Where's this "ENM Loop" you speak of?
    Ethernet1/21 is up
      Hardware: 1000/10000 Ethernet, address: 547f.eeda.6f9c (bia 547f.eeda.6f9c)
      Description: U: Uplink
    RE-SLCFI1-A(nxos)# sh int trunk
    Port          Native  Status        Port
                  Vlan                  Channel
    Eth1/17       500     trunking      --
    Eth1/21       501     trunking      --
    Port          Vlans Allowed on Trunk
    Eth1/17       1,5,500,999
    Eth1/21       1,501,999
    Port          Vlans Err-disabled on Trunk
    Eth1/17       none
    Eth1/21       none
    Port          STP Forwarding
    Eth1/17       1,5,500,999
    Eth1/21       1,501,999

  • UCS connecting to SAN switches

    I've configued UCS direct connecting into the SAN before, but not SAN switches.  My understanding of the main differences between the two is this:
    1) With SAN switches, you configure vSANs.  To do this go to SAN tab -> SAN Cloud and configure your vSAN ID's here.  Then in your vHBA template, configure it to use the appropriate vSAN ID you configured under SAN cloud.  Anything else to do here?
    2) Whereas with direct attached storage you connect FI-A to SPA and SPB and FI-B to SPA and SPB, with san switches FI-A goes to 'switch-1' and FI-B goes to 'switch-2'.  Is this correct?  If so, anyone know why it has to be this way?

    No problem, tbone-111
    As far as I know, only two vHBAs are supported at this time.  It's best to use 1 from the A-side and 1 from the B-side.
    The vHBAs that are used depend on which wwpns you zoned to your boot luns.
    For the example below, assume the following convetions:
    1.) my vHBAs are named, vHBA_A1, vHBA_B1, vHBA_A2, vHBA_B2 (A for A-side fabric, and B for B-side)
    2.) vHBA_A1 is the first HBA on my A side, and vHBA_B1 is the first HBA on B side
    AND
    3.) These HBAs' wwpns are zoned properly to my boot LUNs' Storage Processor (SP) ports on the FC Switch
    AND
    4.) These HBAs' wwpns are LUN masked properly on my array
    Those are logical ANDs, by the way, they must ALL be true to prevent headaches later on.
    5.) Disk Array SP ports A0 and B1 are connected to my A Fabric FC switch.  B0 and A1 are connected to my B Fabric.
    6.) This example boot policy will have the A Fabric be the primary boot path
    -FYI, best practice to have at least 2 SAN Boot policies (1 for A-side and 1 for B-side, and evenly distribute among your Service Profiles).
    In my boot policy, I check the enforce vHBA naming option and specify my vHBAs names (sorry I don't have screenshots available.  just started with a new company and don't have lab access yet).
    My SAN Primary setting might be: Primary Target: A0's wwpn and Secondary Target: B1's wwpn
    My SAN Secondary setting might be: Primary Target: B0's wwpn and Secondary Target: A1's wwpn
    It would be a good idea to confer with your Storage Admins while you are setting up the first couple of servers to boot on each Fabric to help with any troubleshooting.
    If zoning and LUN masking are configured correctly, you should see WWPNs listed during the UCS Server Boot sequence at the point where the FC Boot driver is being loaded.
    Of course, get Cisco TAC on the line if you run into any obstacles that you cannot get past.
    I hope that helps,
    Trevor
    ======================================================================================
    If my answers have been helpful in any way, please rate accordingly.  Thanks!
    Message was edited by: Trevor Roberts Jr

  • Ask the Expert: Cisco UCS Troubleshooting Boot from SAN with FC and iSCSI

    Welcome to this Cisco Support Community Ask the Expert conversation. This is an opportunity to learn and ask questions about Cisco UCS Troubleshooting Boot from SAN with FC and iSCSI with Vishal Mehta and Manuel Velasco.
    The current industry trend is to use SAN (FC/FCoE/iSCSI) for booting operating systems instead of using local storage.
    Boot from SAN offers many benefits, including:
    Server without local storage can run cooler and use the extra space for other components.
    Redeployment of servers caused by hardware failures becomes easier with boot from SAN servers.
    SAN storage allows the administrator to use storage more efficiently.
    Boot from SAN offers reliability because the user can access the boot disk through multiple paths, which protects the disk from being a single point of failure.
    Cisco UCS takes away much of the complexity with its service profiles and associated boot policies to make boot from SAN deployment an easy task.
    Vishal Mehta is a customer support engineer for Cisco’s Data Center Server Virtualization TAC team based in San Jose, California. He has been working in the TAC for the past three years with a primary focus on data center technologies such as Cisco Nexus 5000, Cisco UCS, Cisco Nexus 1000v, and virtualization. He has presented at Cisco Live in Orlando 2013 and will present at Cisco Live Milan 2014 (BRKCOM-3003, BRKDCT-3444, and LABDCT-2333). He holds a master’s degree from Rutgers University in electrical and computer engineering and has CCIE certification (number 37139) in routing and switching and service provider.
    Manuel Velasco is a customer support engineer for Cisco’s Data Center Server Virtualization TAC team based in San Jose, California. He has been working in the TAC for the past three years with a primary focus on data center technologies such as Cisco UCS, Cisco Nexus 1000v, and virtualization. Manuel holds a master’s degree in electrical engineering from California Polytechnic State University (Cal Poly) and VMware VCP and CCNA certifications.
    Remember to use the rating system to let Vishal and Manuel know if you have received an adequate response. 
    Because of the volume expected during this event, our experts might not be able to answer every question. Remember that you can continue the conversation in the Data Center community, under subcommunity Unified Computing, shortly after the event. This event lasts through April 25, 2014. Visit this forum often to view responses to your questions and the questions of other Cisco Support Community members.

    Hello Evan
    Thank you for asking this question. Most common TAC cases that we have seen on Boot-from-SAN failures are due to misconfiguration.
    So our methodology is to verify configuration and troubleshoot from server to storage switches to storage array.
    Before diving into troubleshooting, make sure there is clear understanding of this topology. This is very vital with any troubleshooting scenario. Know what devices you have and how they are connected, how many paths are connected, Switch/NPV mode and so on.
    Always try to troubleshoot one path at a time and verify that the setup is in complaint with the SW/HW interop matrix tested by Cisco.
    Step 1: Check at server
    a. make sure to have uniform firmware version across all components of UCS
    b. Verify if VSAN is created and FC uplinks are configured correctly. VSANs/FCoE-vlan should be unique per fabric
    c. Verify at service profile level for configuration of vHBAs - vHBA per Fabric should have unique VSAN number
    Note down the WWPN of your vhba. This will be needed in step 2 for zoning on the SAN switch and step 3 for LUN masking on the storage array.
    d. verify if Boot Policy of the service profile is configured to Boot From SAN - the Boot Order and its parameters such as Lun ID and WWN are extremely important
    e. finally at UCS CLI - verify the flogi of vHBAs (for NPV mode, command is (from nxos) – show npv flogi-table)
    Step 2: Check at Storage Switch
    a. Verify the mode (by default UCS is in FC end-host mode, so storage switch has to be in NPIV mode; unless UCS is in FC Switch mode)
    b. Verify the switch port connecting to UCS is UP as an F-Port and is configured for correct VSAN
    c. Check if both the initiator (Server) and the target (Storage) are logged into the fabric switch (command for MDS/N5k - show flogi database vsan X)
    d. Once confirmed that initiator and target devices are logged into the fabric, query the name server to see if they have registered themselves correctly. (command - show fcns database vsan X)
    e. Most important configuration to check on Storage Switch is the zoning
    Zoning is basically access control for our initiator to  targets. Most common design is to configure one zone per initiator and target.
    Zoning will require you to configure a zone, put that zone into your current zonset, then ACTIVATE it. (command - show zoneset active vsan X)
    Step 3: Check at Storage Array
    When the Storage array logs into the SAN fabric, it queries the name server to see which devices it can communicate.
    LUN masking is crucial step on Storage Array which gives particular host (server) access to specific LUN
    Assuming that both the storage and initiator have FLOGI’d into the fabric and the zoning is correct (as per Step 1 & 2)
    Following needs to be verified at Storage Array level
    a. Are the wwpn of the initiators (vhba of the hosts) visible on the storage array?
    b. If above is yes then Is LUN Masking applied?
    c. What LUN number is presented to the host - this is the number that we see in Lun ID on the 'Boot Order' of Step 1
    Below document has details and troubleshooting outputs:
    http://www.cisco.com/c/en/us/support/docs/servers-unified-computing/ucs-b-series-blade-servers/115764-ucs-san-tshoot-00.html
    Hope this answers your question.
    Thanks,
    Vishal 

  • Cannot create iSCSI connection to HP4300 SAN [OVM3.1.1]

    I have set up OVM 3.1.1 on oracle 11g SE. I have on OVS with three bonded networks...One for Management, Storage, and the third for VM vlan networks. Now I need to set up some storage. My SAN is an HP P4300. I found that the initiator for my OVS is
    OVM1:iqn.1988-12.com.oracle:6d6be5deab82
    Inside the console for my SAN, I create a server object and enter the initiator OVM1:iqn.1988-12.com.oracle:6d6be5deab82 into it.
    I get a message that it is not in the standard format.... but I continue.
    Now back to OVM, I try to discover my SAN. Enter the name, ISCSI SAN, Gengeric, and the IP address of the SAN. I then select the OVS. After the job is launched....it fails
    I tried the initiator without the OVM1: making the standard format....but it still failed. I do not have chap selected to eliminate that.
    I appears to be an authentication thing....so it must be the initiator (Can it be changed to delete the OVM1:)
    What am I missing.....this should be pretty simple......
    Job Construction Phase
    begin()
    begin()
    Appended operation 'Storage Array Validate' to object '0004fb0000090000309e760f71aec824 (HP4300_1)'.
    Appended operation 'Storage Array Discover Info' to object '0004fb0000090000309e760f71aec824 (HP4300_1)'.
    Appended operation 'Storage Server Discover Capabilities' to object '0004fb0000090000309e760f71aec824 (HP4300_1)'.
    Appended operation 'Storage Server Discover Access Groups' to object '0004fb0000090000309e760f71aec824 (HP4300_1)'.
    Operation 'Storage Array Discover Info' was not added, it already exists on object '0004fb0000090000309e760f71aec824 (HP4300_1)'.
    Appended operation 'Storage Array Discover Storage Elements' to object '0004fb0000090000309e760f71aec824 (HP4300_1)'.
    Appended operation 'ISCSI Storage Array Discover Targets' to object '0004fb0000090000309e760f71aec824 (HP4300_1)'.
    commit()
    Completed Step: COMMIT
    Objects and Operations
    Object (CREATED): [IscsiStorageArray] 0004fb0000090000309e760f71aec824 (HP4300_1)
    Operation: Storage Array Validate
    Operation: Storage Array Discover Info
    Operation: Storage Server Discover Capabilities
    Operation: Storage Server Discover Access Groups
    Operation: Storage Array Discover Storage Elements
    Operation: ISCSI Storage Array Discover Targets
    Object (IN_USE): [StorageArrayPlugin] oracle.generic.SCSIPlugin.GenericPlugin (1.1.0) (Oracle Generic SCSI Plugin)
    Object (CREATED): [AccessGroup] Default access group @ HP4300_1 @ 0004fb0000090000309e760f71aec824 (Default access group @ HP4300_1)
    Object (IN_USE): [Server] 35:37:33:31:32:32:55:53:45:31:35:33:52:30:4c:32 (OVM1)
    Job Running Phase at 22:40 on Thu, Oct 4, 2012
    Job Participants: [35:37:33:31:32:32:55:53:45:31:35:33:52:30:4c:32 (OVM1)]
    Actioner
    Starting operation 'Storage Array Validate' on object '0004fb0000090000309e760f71aec824 (HP4300_1)'
    Operation 'Storage Server Discover Capabilities' was not added, it already exists on object '0004fb0000090000309e760f71aec824 (HP4300_1)'.
    Operation 'Storage Server Discover Access Groups' was not added, it already exists on object '0004fb0000090000309e760f71aec824 (HP4300_1)'.
    Completed operation 'Storage Array Validate' completed with direction ==> DONE
    Starting operation 'Storage Array Discover Info' on object '0004fb0000090000309e760f71aec824 (HP4300_1)'
    Setting Context to model only in job with id=1349408417858
    Setting Context to default in job with id=1349408417858
    Completed operation 'Storage Array Discover Info' completed with direction ==> DONE
    Starting operation 'Storage Server Discover Capabilities' on object '0004fb0000090000309e760f71aec824 (HP4300_1)'
    Setting Context to model only in job with id=1349408417858
    Setting Context to default in job with id=1349408417858
    Completed operation 'Storage Server Discover Capabilities' completed with direction ==> DONE
    Starting operation 'Storage Server Discover Access Groups' on object '0004fb0000090000309e760f71aec824 (HP4300_1)'
    Completed operation 'Storage Server Discover Access Groups' completed with direction ==> DONE
    Starting operation 'Storage Array Discover Storage Elements' on object '0004fb0000090000309e760f71aec824 (HP4300_1)'
    Completed operation 'Storage Array Discover Storage Elements' completed with direction ==> LATER
    Starting operation 'ISCSI Storage Array Discover Targets' on object '0004fb0000090000309e760f71aec824 (HP4300_1)'
    Setting Context to model only in job with id=1349408417858
    Job Internal Error (Operation)com.oracle.ovm.mgr.api.exception.FailedOperationException: OVMAPI_B000E Storage plugin command [storage_plugin_discover] failed for storage server [0004fb0000090000309e760f71aec824] failed with [com.oracle.ovm.mgr.api.exception.FailedOperationException: OVMAPI_4010E Attempt to send command: storage_plugin_discover to server: OVM1 failed. OVMAPI_4004E Server Failed Command: storage_plugin_discover oracle.generic.SCSIPlugin.GenericPlugin, Status: OSCPlugin.TargetDiscoveryEx:'Failure to get the targets: iscsiadm: Login failed to authenticate with target \niscsiadm: discovery login to 172.21.2.12 rejected: initiator error (02/01), non-retryable, giving up\niscsiadm: Could not perform SendTargets discovery.\n'
    Thu Oct 04 22:40:34 CDT 2012
    Thu Oct 04 22:40:34 CDT 2012] OVMAPI_4010E Attempt to send command: storage_plugin_discover to server: OVM1 failed. OVMAPI_4004E Server Failed Command: storage_plugin_discover oracle.generic.SCSIPlugin.GenericPlugin, Status: org.apache.xmlrpc.XmlRpcException: OSCPlugin.TargetDiscoveryEx:'Failure to get the targets: iscsiadm: Login failed to authenticate with target \niscsiadm: discovery login to 172.21.2.12 rejected: initiator error (02/01), non-retryable, giving up\niscsiadm: Could not perform SendTargets discovery.\n'
    Thu Oct 04 22:40:34 CDT 2012
    Thu Oct 04 22:40:34 CDT 2012
    Thu Oct 04 22:40:34 CDT 2012
    at com.oracle.ovm.mgr.action.StoragePluginAction.processException(StoragePluginAction.java:1371)
    at com.oracle.ovm.mgr.action.StoragePluginAction.discoverISCSIStorageArrayTargets(StoragePluginAction.java:218)
    at com.oracle.ovm.mgr.discover.ovm.IscsiStorageArrayTargetsDiscoverHandler.query(IscsiStorageArrayTargetsDiscoverHandler.java:30)
    at com.oracle.ovm.mgr.discover.ovm.IscsiStorageArrayTargetsDiscoverHandler.query(IscsiStorageArrayTargetsDiscoverHandler.java:19)
    at com.oracle.ovm.mgr.discover.ovm.DiscoverHandler.execute(DiscoverHandler.java:61)
    at com.oracle.ovm.mgr.discover.StorageServerDiscover.handleDiscover(StorageServerDiscover.java:77)
    at com.oracle.ovm.mgr.discover.StorageServerDiscover.discoverStorageServer(StorageServerDiscover.java:53)
    at com.oracle.ovm.mgr.op.physical.storage.IscsiStorageArrayDiscoverTargets.discoverIscsiStorageArrayTargets(IscsiStorageArrayDiscoverTargets.java:47)
    at com.oracle.ovm.mgr.op.physical.storage.IscsiStorageArrayDiscoverTargets.action(IscsiStorageArrayDiscoverTargets.java:38)
    at com.oracle.ovm.mgr.api.collectable.ManagedObjectDbImpl.executeCurrentJobOperationAction(ManagedObjectDbImpl.java:1009)
    at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:330)
    at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:290)
    at com.oracle.odof.core.storage.Transaction.invokeMethod(Transaction.java:822)
    at com.oracle.odof.core.Exchange.invokeMethod(Exchange.java:245)
    at com.oracle.ovm.mgr.api.physical.storage.IscsiStorageArrayProxy.executeCurrentJobOperationAction(Unknown Source)
    at com.oracle.ovm.mgr.api.job.JobEngine.operationActioner(JobEngine.java:218)
    at com.oracle.ovm.mgr.api.job.JobEngine.objectActioner(JobEngine.java:309)
    at com.oracle.ovm.mgr.api.job.InternalJobDbImpl.objectCommitter(InternalJobDbImpl.java:1140)
    at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:330)
    at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:290)
    at com.oracle.odof.core.BasicWork.invokeMethod(BasicWork.java:136)
    at com.oracle.odof.command.InvokeMethodCommand.process(InvokeMethodCommand.java:100)
    at com.oracle.odof.core.BasicWork.processCommand(BasicWork.java:81)
    at com.oracle.odof.core.TransactionManager.processCommand(TransactionManager.java:773)
    at com.oracle.odof.core.WorkflowManager.processCommand(WorkflowManager.java:401)
    at com.oracle.odof.core.WorkflowManager.processWork(WorkflowManager.java:459)
    at com.oracle.odof.io.AbstractClient.run(AbstractClient.java:42)
    at java.lang.Thread.run(Thread.java:662)
    Caused by: com.oracle.ovm.mgr.api.exception.FailedOperationException: OVMAPI_4010E Attempt to send command: storage_plugin_discover to server: OVM1 failed. OVMAPI_4004E Server Failed Command: storage_plugin_discover oracle.generic.SCSIPlugin.GenericPlugin, Status: org.apache.xmlrpc.XmlRpcException: OSCPlugin.TargetDiscoveryEx:'Failure to get the targets: iscsiadm: Login failed to authenticate with target \niscsiadm: discovery login to 172.21.2.12 rejected: initiator error (02/01), non-retryable, giving up\niscsiadm: Could not perform SendTargets discovery.\n'
    Thu Oct 04 22:40:34 CDT 2012
    Thu Oct 04 22:40:34 CDT 2012
    at com.oracle.ovm.mgr.action.ActionEngine.sendCommandToServer(ActionEngine.java:507)
    at com.oracle.ovm.mgr.action.ActionEngine.sendUndispatchedServerCommand(ActionEngine.java:459)
    at com.oracle.ovm.mgr.action.ActionEngine.sendServerCommand(ActionEngine.java:385)
    at com.oracle.ovm.mgr.action.StoragePluginAction.discoverISCSIStorageArrayTargets(StoragePluginAction.java:214)
    ... 32 more
    Caused by: com.oracle.ovm.mgr.api.exception.IllegalOperationException: OVMAPI_4004E Server Failed Command: storage_plugin_discover oracle.generic.SCSIPlugin.GenericPlugin, Status: org.apache.xmlrpc.XmlRpcException: OSCPlugin.TargetDiscoveryEx:'Failure to get the targets: iscsiadm: Login failed to authenticate with target \niscsiadm: discovery login to 172.21.2.12 rejected: initiator error (02/01), non-retryable, giving up\niscsiadm: Could not perform SendTargets discovery.\n'
    Thu Oct 04 22:40:34 CDT 2012
    at com.oracle.ovm.mgr.action.ActionEngine.sendAction(ActionEngine.java:798)
    at com.oracle.ovm.mgr.action.ActionEngine.sendCommandToServer(ActionEngine.java:503)
    ... 35 more
    FailedOperationCleanup
    Starting failed operation 'ISCSI Storage Array Discover Targets' cleanup on object 'HP4300_1'
    Complete rollback operation 'ISCSI Storage Array Discover Targets' completed with direction=HP4300_1
    Rollbacker
    Executing rollback operation 'ISCSI Storage Array Discover Targets' on object '0004fb0000090000309e760f71aec824 (HP4300_1)'
    Complete rollback operation 'ISCSI Storage Array Discover Targets' completed with direction=DONE
    Executing rollback operation 'Storage Server Discover Access Groups' on object '0004fb0000090000309e760f71aec824 (HP4300_1)'
    Complete rollback operation 'Storage Server Discover Access Groups' completed with direction=DONE
    Executing rollback operation 'Storage Server Discover Capabilities' on object '0004fb0000090000309e760f71aec824 (HP4300_1)'
    Complete rollback operation 'Storage Server Discover Capabilities' completed with direction=DONE
    Executing rollback operation 'Storage Array Discover Info' on object '0004fb0000090000309e760f71aec824 (HP4300_1)'
    Complete rollback operation 'Storage Array Discover Info' completed with direction=DONE
    Executing rollback operation 'Storage Array Validate' on object '0004fb0000090000309e760f71aec824 (HP4300_1)'
    Complete rollback operation 'Storage Array Validate' completed with direction=DONE
    Objects To Be Rolled Back
    Object (CREATED): [IscsiStorageArray] 0004fb0000090000309e760f71aec824 (HP4300_1)
    Object (IN_USE): [StorageArrayPlugin] oracle.generic.SCSIPlugin.GenericPlugin (1.1.0) (Oracle Generic SCSI Plugin)
    Object (CREATED): [AccessGroup] Default access group @ HP4300_1 @ 0004fb0000090000309e760f71aec824 (Default access group @ HP4300_1)
    Object (IN_USE): [Server] 35:37:33:31:32:32:55:53:45:31:35:33:52:30:4c:32 (OVM1)
    Object (CREATED): [VolumeGroup] Generic_iSCSI_Volume_Group @ 0004fb0000090000309e760f71aec824 (Generic_iSCSI_Volume_Group)
    Write Methods Invoked
    Class=InternalJobDbImpl vessel_id=3071 method=addTransactionIdentifier accessLevel=6
    Class=IscsiStorageArrayDbImpl vessel_id=3080 method=addAdminServer accessLevel=6
    Class=ServerDbImpl vessel_id=1265 method=addStorageServer accessLevel=6
    Class=IscsiStorageArrayDbImpl vessel_id=3080 method=validate accessLevel=6
    Class=IscsiStorageArrayDbImpl vessel_id=3080 method=refresh accessLevel=6
    Class=InternalJobDbImpl vessel_id=3071 method=setCompletedStep accessLevel=6
    Class=InternalJobDbImpl vessel_id=3071 method=setAssociatedHandles accessLevel=6
    Class=IscsiStorageArrayDbImpl vessel_id=3080 method=setValidated accessLevel=6
    Class=IscsiStorageArrayDbImpl vessel_id=3080 method=addJobOperation accessLevel=6
    Class=IscsiStorageArrayDbImpl vessel_id=3080 method=addJobOperation accessLevel=6
    Class=IscsiStorageArrayDbImpl vessel_id=3080 method=setCurrentJobOperationComplete accessLevel=6
    Class=IscsiStorageArrayDbImpl vessel_id=3080 method=nextJobOperation accessLevel=6
    Class=InternalJobDbImpl vessel_id=3071 method=setContext accessLevel=6
    Class=IscsiStorageArrayDbImpl vessel_id=3080 method=lock accessLevel=6
    Class=IscsiStorageArrayDbImpl vessel_id=3080 method=createVolumeGroup accessLevel=6
    Class=VolumeGroupDbImpl vessel_id=3092 method=setName accessLevel=6
    Class=VolumeGroupDbImpl vessel_id=3092 method=setFoundryContext accessLevel=6
    Class=VolumeGroupDbImpl vessel_id=3092 method=onPersistableCreate accessLevel=6
    Class=VolumeGroupDbImpl vessel_id=3092 method=setLifecycleState accessLevel=6
    Class=VolumeGroupDbImpl vessel_id=3092 method=setRollbackLifecycleState accessLevel=6
    Class=VolumeGroupDbImpl vessel_id=3092 method=setStorageArray accessLevel=6
    Class=VolumeGroupDbImpl vessel_id=3092 method=setSimpleName accessLevel=6
    Class=VolumeGroupDbImpl vessel_id=3092 method=lock accessLevel=6
    Class=InternalJobDbImpl vessel_id=3071 method=setContext accessLevel=6
    Class=IscsiStorageArrayDbImpl vessel_id=3080 method=setCurrentJobOperationComplete accessLevel=6
    Class=IscsiStorageArrayDbImpl vessel_id=3080 method=nextJobOperation accessLevel=6
    Class=InternalJobDbImpl vessel_id=3071 method=setContext accessLevel=6
    Class=IscsiStorageArrayDbImpl vessel_id=3080 method=setAbility accessLevel=6
    Class=IscsiStorageArrayDbImpl vessel_id=3080 method=setAbility accessLevel=6
    Class=IscsiStorageArrayDbImpl vessel_id=3080 method=setAbility accessLevel=6
    Class=IscsiStorageArrayDbImpl vessel_id=3080 method=setAbility accessLevel=6
    Class=IscsiStorageArrayDbImpl vessel_id=3080 method=setAbility accessLevel=6
    Class=IscsiStorageArrayDbImpl vessel_id=3080 method=setAbility accessLevel=6
    Class=IscsiStorageArrayDbImpl vessel_id=3080 method=setAbility accessLevel=6
    Class=IscsiStorageArrayDbImpl vessel_id=3080 method=setAbility accessLevel=6
    Class=IscsiStorageArrayDbImpl vessel_id=3080 method=setAbility accessLevel=6
    Class=IscsiStorageArrayDbImpl vessel_id=3080 method=setAbility accessLevel=6
    Class=IscsiStorageArrayDbImpl vessel_id=3080 method=setAbility accessLevel=6
    Class=IscsiStorageArrayDbImpl vessel_id=3080 method=setAbility accessLevel=6
    Class=IscsiStorageArrayDbImpl vessel_id=3080 method=setAbility accessLevel=6
    Class=IscsiStorageArrayDbImpl vessel_id=3080 method=setAbility accessLevel=6
    Class=InternalJobDbImpl vessel_id=3071 method=setContext accessLevel=6
    Class=IscsiStorageArrayDbImpl vessel_id=3080 method=setCurrentJobOperationComplete accessLevel=6
    Class=IscsiStorageArrayDbImpl vessel_id=3080 method=nextJobOperation accessLevel=6
    Class=IscsiStorageArrayDbImpl vessel_id=3080 method=setCurrentJobOperationComplete accessLevel=6
    Class=IscsiStorageArrayDbImpl vessel_id=3080 method=nextJobOperation accessLevel=6
    Class=InternalJobDbImpl vessel_id=3071 method=setTuringMachineFlag accessLevel=6
    Class=IscsiStorageArrayDbImpl vessel_id=3080 method=setCurrentOperationToLater accessLevel=6
    Class=InternalJobDbImpl vessel_id=3071 method=setTuringMachineFlag accessLevel=6
    Class=InternalJobDbImpl vessel_id=3071 method=setContext accessLevel=6
    Class=IscsiStorageArrayDbImpl vessel_id=3080 method=nextJobOperation accessLevel=6
    Class=InternalJobDbImpl vessel_id=3071 method=setFailedOperation accessLevel=6
    Class=IscsiStorageArrayDbImpl vessel_id=3080 method=nextJobOperation accessLevel=6
    Class=StorageArrayPluginDbImpl vessel_id=1657 method=nextJobOperation accessLevel=6
    Class=AccessGroupDbImpl vessel_id=3086 method=nextJobOperation accessLevel=6
    Class=ServerDbImpl vessel_id=1265 method=nextJobOperation accessLevel=6
    Class=IscsiStorageArrayDbImpl vessel_id=3080 method=nextJobOperation accessLevel=6
    Class=IscsiStorageArrayDbImpl vessel_id=3080 method=nextJobOperation accessLevel=6
    Class=IscsiStorageArrayDbImpl vessel_id=3080 method=nextJobOperation accessLevel=6
    Class=IscsiStorageArrayDbImpl vessel_id=3080 method=nextJobOperation accessLevel=6
    Class=IscsiStorageArrayDbImpl vessel_id=3080 method=nextJobOperation accessLevel=6
    Class=InternalJobDbImpl vessel_id=3071 method=addTransactionIdentifier accessLevel=6
    Class=IscsiStorageArrayDbImpl vessel_id=3080 method=setName accessLevel=6
    Class=IscsiStorageArrayDbImpl vessel_id=3080 method=setFoundryContext accessLevel=6
    Class=IscsiStorageArrayDbImpl vessel_id=3080 method=onPersistableCreate accessLevel=6
    Class=IscsiStorageArrayDbImpl vessel_id=3080 method=setLifecycleState accessLevel=6
    Class=IscsiStorageArrayDbImpl vessel_id=3080 method=setRollbackLifecycleState accessLevel=6
    Class=IscsiStorageArrayDbImpl vessel_id=3080 method=setStoragePlugin accessLevel=6
    Class=StorageArrayPluginDbImpl vessel_id=1657 method=addStorageServer accessLevel=6
    Class=IscsiStorageArrayDbImpl vessel_id=3080 method=setAdminHostname accessLevel=6
    Class=IscsiStorageArrayDbImpl vessel_id=3080 method=setAdminUsername accessLevel=6
    Class=IscsiStorageArrayDbImpl vessel_id=3080 method=setAdminPassword accessLevel=6
    Class=IscsiStorageArrayDbImpl vessel_id=3080 method=setSimpleName accessLevel=6
    Class=IscsiStorageArrayDbImpl vessel_id=3080 method=createAccessGroup accessLevel=6
    Class=AccessGroupDbImpl vessel_id=3086 method=setName accessLevel=6
    Class=AccessGroupDbImpl vessel_id=3086 method=setFoundryContext accessLevel=6
    Class=AccessGroupDbImpl vessel_id=3086 method=onPersistableCreate accessLevel=6
    Class=AccessGroupDbImpl vessel_id=3086 method=setLifecycleState accessLevel=6
    Class=AccessGroupDbImpl vessel_id=3086 method=setRollbackLifecycleState accessLevel=6
    Class=AccessGroupDbImpl vessel_id=3086 method=setSimpleName accessLevel=6
    Class=AccessGroupDbImpl vessel_id=3086 method=setStorageServer accessLevel=6
    Class=IscsiStorageArrayDbImpl vessel_id=3080 method=setDescription accessLevel=6
    Class=IscsiStorageArrayDbImpl vessel_id=3080 method=setAccessHost accessLevel=6
    Class=IscsiStorageArrayDbImpl vessel_id=3080 method=setUsername accessLevel=6
    Class=IscsiStorageArrayDbImpl vessel_id=3080 method=setPassword accessLevel=6
    Class=IscsiStorageArrayDbImpl vessel_id=3080 method=setUseChapAuth accessLevel=6
    Completed Step: ROLLBACK
    Job failed commit (internal) due to OVMAPI_B000E Storage plugin command [storage_plugin_discover] failed for storage server [0004fb0000090000309e760f71aec824] failed with [com.oracle.ovm.mgr.api.exception.FailedOperationException: OVMAPI_4010E Attempt to send command: storage_plugin_discover to server: OVM1 failed. OVMAPI_4004E Server Failed Command: storage_plugin_discover oracle.generic.SCSIPlugin.GenericPlugin, Status: OSCPlugin.TargetDiscoveryEx:'Failure to get the targets: iscsiadm: Login failed to authenticate with target \niscsiadm: discovery login to 172.21.2.12 rejected: initiator error (02/01), non-retryable, giving up\niscsiadm: Could not perform SendTargets discovery.\n'
    Thu Oct 04 22:40:34 CDT 2012
    Thu Oct 04 22:40:34 CDT 2012] OVMAPI_4010E Attempt to send command: storage_plugin_discover to server: OVM1 failed. OVMAPI_4004E Server Failed Command: storage_plugin_discover oracle.generic.SCSIPlugin.GenericPlugin, Status: org.apache.xmlrpc.XmlRpcException: OSCPlugin.TargetDiscoveryEx:'Failure to get the targets: iscsiadm: Login failed to authenticate with target \niscsiadm: discovery login to 172.21.2.12 rejected: initiator error (02/01), non-retryable, giving up\niscsiadm: Could not perform SendTargets discovery.\n'
    Thu Oct 04 22:40:34 CDT 2012
    Thu Oct 04 22:40:34 CDT 2012
    Thu Oct 04 22:40:34 CDT 2012
    com.oracle.ovm.mgr.api.exception.FailedOperationException: OVMAPI_B000E Storage plugin command [storage_plugin_discover] failed for storage server [0004fb0000090000309e760f71aec824] failed with [com.oracle.ovm.mgr.api.exception.FailedOperationException: OVMAPI_4010E Attempt to send command: storage_plugin_discover to server: OVM1 failed. OVMAPI_4004E Server Failed Command: storage_plugin_discover oracle.generic.SCSIPlugin.GenericPlugin, Status: OSCPlugin.TargetDiscoveryEx:'Failure to get the targets: iscsiadm: Login failed to authenticate with target \niscsiadm: discovery login to 172.21.2.12 rejected: initiator error (02/01), non-retryable, giving up\niscsiadm: Could not perform SendTargets discovery.\n'
    Thu Oct 04 22:40:34 CDT 2012
    Thu Oct 04 22:40:34 CDT 2012] OVMAPI_4010E Attempt to send command: storage_plugin_discover to server: OVM1 failed. OVMAPI_4004E Server Failed Command: storage_plugin_discover oracle.generic.SCSIPlugin.GenericPlugin, Status: org.apache.xmlrpc.XmlRpcException: OSCPlugin.TargetDiscoveryEx:'Failure to get the targets: iscsiadm: Login failed to authenticate with target \niscsiadm: discovery login to 172.21.2.12 rejected: initiator error (02/01), non-retryable, giving up\niscsiadm: Could not perform SendTargets discovery.\n'
    Thu Oct 04 22:40:34 CDT 2012
    Thu Oct 04 22:40:34 CDT 2012
    Thu Oct 04 22:40:34 CDT 2012
    at com.oracle.ovm.mgr.action.StoragePluginAction.processException(StoragePluginAction.java:1371)
    at com.oracle.ovm.mgr.action.StoragePluginAction.discoverISCSIStorageArrayTargets(StoragePluginAction.java:218)
    at com.oracle.ovm.mgr.discover.ovm.IscsiStorageArrayTargetsDiscoverHandler.query(IscsiStorageArrayTargetsDiscoverHandler.java:30)
    at com.oracle.ovm.mgr.discover.ovm.IscsiStorageArrayTargetsDiscoverHandler.query(IscsiStorageArrayTargetsDiscoverHandler.java:19)
    at com.oracle.ovm.mgr.discover.ovm.DiscoverHandler.execute(DiscoverHandler.java:61)
    at com.oracle.ovm.mgr.discover.StorageServerDiscover.handleDiscover(StorageServerDiscover.java:77)
    at com.oracle.ovm.mgr.discover.StorageServerDiscover.discoverStorageServer(StorageServerDiscover.java:53)
    at com.oracle.ovm.mgr.op.physical.storage.IscsiStorageArrayDiscoverTargets.discoverIscsiStorageArrayTargets(IscsiStorageArrayDiscoverTargets.java:47)
    at com.oracle.ovm.mgr.op.physical.storage.IscsiStorageArrayDiscoverTargets.action(IscsiStorageArrayDiscoverTargets.java:38)
    at com.oracle.ovm.mgr.api.collectable.ManagedObjectDbImpl.executeCurrentJobOperationAction(ManagedObjectDbImpl.java:1009)
    at sun.reflect.GeneratedMethodAccessor1005.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:330)
    at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:290)
    at com.oracle.odof.core.storage.Transaction.invokeMethod(Transaction.java:822)
    at com.oracle.odof.core.Exchange.invokeMethod(Exchange.java:245)
    at com.oracle.ovm.mgr.api.physical.storage.IscsiStorageArrayProxy.executeCurrentJobOperationAction(Unknown Source)
    at com.oracle.ovm.mgr.api.job.JobEngine.operationActioner(JobEngine.java:218)
    at com.oracle.ovm.mgr.api.job.JobEngine.objectActioner(JobEngine.java:309)
    at com.oracle.ovm.mgr.api.job.InternalJobDbImpl.objectCommitter(InternalJobDbImpl.java:1140)
    at sun.reflect.GeneratedMethodAccessor1340.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:330)
    at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:290)
    at com.oracle.odof.core.BasicWork.invokeMethod(BasicWork.java:136)
    at com.oracle.odof.command.InvokeMethodCommand.process(InvokeMethodCommand.java:100)
    at com.oracle.odof.core.BasicWork.processCommand(BasicWork.java:81)
    at com.oracle.odof.core.TransactionManager.processCommand(TransactionManager.java:773)
    at com.oracle.odof.core.WorkflowManager.processCommand(WorkflowManager.java:401)
    at com.oracle.odof.core.WorkflowManager.processWork(WorkflowManager.java:459)
    at com.oracle.odof.io.AbstractClient.run(AbstractClient.java:42)
    at java.lang.Thread.run(Thread.java:662)
    Caused by: com.oracle.ovm.mgr.api.exception.FailedOperationException: OVMAPI_4010E Attempt to send command: storage_plugin_discover to server: OVM1 failed. OVMAPI_4004E Server Failed Command: storage_plugin_discover oracle.generic.SCSIPlugin.GenericPlugin, Status: org.apache.xmlrpc.XmlRpcException: OSCPlugin.TargetDiscoveryEx:'Failure to get the targets: iscsiadm: Login failed to authenticate with target \niscsiadm: discovery login to 172.21.2.12 rejected: initiator error (02/01), non-retryable, giving up\niscsiadm: Could not perform SendTargets discovery.\n'
    Thu Oct 04 22:40:34 CDT 2012
    Thu Oct 04 22:40:34 CDT 2012
    at com.oracle.ovm.mgr.action.ActionEngine.sendCommandToServer(ActionEngine.java:507)
    at com.oracle.ovm.mgr.action.ActionEngine.sendUndispatchedServerCommand(ActionEngine.java:459)
    at com.oracle.ovm.mgr.action.ActionEngine.sendServerCommand(ActionEngine.java:385)
    at com.oracle.ovm.mgr.action.StoragePluginAction.discoverISCSIStorageArrayTargets(StoragePluginAction.java:214)
    ... 32 more
    Caused by: com.oracle.ovm.mgr.api.exception.IllegalOperationException: OVMAPI_4004E Server Failed Command: storage_plugin_discover oracle.generic.SCSIPlugin.GenericPlugin, Status: org.apache.xmlrpc.XmlRpcException: OSCPlugin.TargetDiscoveryEx:'Failure to get the targets: iscsiadm: Login failed to authenticate with target \niscsiadm: discovery login to 172.21.2.12 rejected: initiator error (02/01), non-retryable, giving up\niscsiadm: Could not perform SendTargets discovery.\n'
    Thu Oct 04 22:40:34 CDT 2012
    at com.oracle.ovm.mgr.action.ActionEngine.sendAction(ActionEngine.java:798)
    at com.oracle.ovm.mgr.action.ActionEngine.sendCommandToServer(ActionEngine.java:503)
    ... 35 more
    End of Job
    ----------

    Great! That makes since......but did not solve my problem.....The iSCSI initiator is in the correct format. When it is listed in the Web GUI, it adds the server name to the beginning. But I tried it with out the server name and it still
    error ed out. I rebooted the node, deleted the server from the manager and rediscovered the server.....still same problem.
    I used the same initiator address from the vm server and named my workstation initiator with it. I talked with my SAN tech support, but I was the first one who has call that uses Oracle VM ......but they have no idea what the problem could be... I was able to connect to my SAN using the oracle initiator (from my windows 7) box...... so this definitely points to the vm server...
    but what could be the problem..... I can ping the SAN from the server....????
    Thanks,

  • MDS FC Port mode for UCS connectivity

    Hi,
    A little question on admin mode of the MDS switch port which is connected to a UCS Fabric Interconnect.
    The switch is a MDS 9509 running SAN OS v3.3, we have enabled NPIV on the MDS switch. Currently the port's admin mode is 'auto' and its operational mode is 'F'.
    Therefore is it safe to change the admin mode to 'F' or is it better to keep 'auto' as it is.
    Cheers,
    Kisanka

    Thanks Jeramy. Since the final operational mode is F, is it safe to administratively set the mode to 'F'

  • Problems importing connections from a SAN directory

    Is anybody having a problem importing connections from a directory that's on a SAN?
    My network is setup so that the Application Data directory is out on a SAN and when SQL Developer opens up the file dialog, current directory is listed as C:\ and entry in the file name field is file://<server>/<path to my stuff>/Application Data/SQL Developer/. This looks fine but when I click on the "Open" button to get the directory listing, an error dialog pops up with the following message:
    The directory C:\file:\<server>\<path to my stuff>\Application Data\SQL Developer is not accessible. Please select a different directory.
    When I change the current directory to the drive that maps the SAN location, I get the same message only with C: replaced with another drive letter.
    If I had to guess, the dialog is not processing the file:// protocol indicator properly before it attempts to get the directory listing. Does anyone have a work around?

    Other users also had problems with network shares, so you're right that might very well be the cause of your problems.
    As workaround, try mapping the settings folder to a local drive. Add this to \sqldeveloper\bin\sqldeveloper.conf:
    AddVMOption -Dide.user.dir=C:\sqldeveloperHope that helps,
    K.

  • UCS connected to multiple FC fabrics?

    Hi,
    I *think* it is possible, yet I cannot find any diagram / documentation confirming this:
    Is it OK to connect UCS Fabric Interconnect modules to more than one FC fabric? (namely 2 Brocade fabrics per module?)
    Am I correct in my thinking that creating separate VSANs for each fabric should do the trick?
    Thanks & regards,
    Radek

    Radek, yes it is possible. I did this recently at one of my customers, we connected a Brocade and QLogic fabric to both UCS FIs. We put the Brocade FC ports and vHBAs in one VSAN and he QLogic in the other. It was very cool because this allowed the customer to access both fabric from a single serer without having to ISL the 2 fabric together.

  • Unable to connect a Netapp San to a Cisco Catalyst in 10Gb

    I have a Cisco Catalyst 4507R with a WS-X4606-X2-E and X2-10GB-SR to be connected to a Netapp SAN and it does not work.
    With show interface transceiver detail it seems that the power sent by netapp is good but the link stay in dwon down state
    Any help?

    down/down is related to layer 1 issue. Make sure the SFP is correct on both ends (and same type: LR vs SR) and also make sure you are using the right fiber. You can loop back on the same catalyst both sfps with the cable to see if the link comes up.

  • Issues with SmartPhones not connecting to Cisco LWAP infrastructure

    Has anyone observed any issues in getting wifi-enabled smartphones to connect to the Cisco LWAP wireless infrastructure?
    In this particular case, the system is operating essentially as a hot-spot (i.e.: No layer 2 security between the LWAP and the smartphone.)
    One of the SmartPhone models having problems is the Samsung i730.
    I found an FAQ at the Verizon site (attached):
    Exerpt from:
    http://support.vzw.com/devices/samsung_sch-i730/faq.html#item66 <http://support.vzw.com/devices/samsung_sch-i730/faq.html#item66>
    "Why doesn't the i730 connect to my wireless access point (AP) /router?
    The i730 supports wireless access points that transmit a 128bit preamble not 130bit preamble. Some wireless access points send a 130bit (i.e. Cisco, Linksys, etc). To address this issue you can upgrade the firmware in your wireless access point by simply going to the wireless access point manufacturer's website and downloading the latest firmware and upgrade instructions."
    Full article:
    http://support.vzw.com/devices/samsung_sch-i730/faq.html <http://support.vzw.com/devices/samsung_sch-i730/faq.html>
    I am wondering what version of LWAP firmware would address the 128-bit issue.
    Any thoughts?
    Thanks,
    John

    Try out the latest firmware for the controllers 4.0.206.0. This might solve the issue.

  • UCS connectivity options

    We are close to implementing UCS into our existing data center. We have a pair of 4506-Es and were planning to run VSS. Well, i found out today that several of our line cards are unsupported and VSS will not work. The two 4500s are running HSRP. I'm wondering what my options are for connecting the two Cisco 6248 FIs to my two 4500s. I'm really dissapointed to find out VSS won't work. We have two 12 port SFP+s line cards in the 4500s. I was hoping to have 4 10G uplinks from each FI to each Core. Now it looks like i might have to settle for a STP design with active/standby? Do i have any other options?

    If i was building from ground up Nexus would be the way to go.
    I got final clarification from an SE that there are unsupported line cards as far as VSLgoes.....and not overall VSS function. The way it sounded is if i had these "unsupported" line cards in the chassis they would no longer function. After clarification....they are not compatible with VSL links. I just need to use the supervisor uplinks.

  • Copying data to a SAN attached to UCS

    Hi Folks,
    We have a 2 5108 chassis with 3 B200 blades each and 2 fabric interconnect 6248. This UCS connects to a hitachi storage array. The virtual machines configured use VMware.
    I am not very familiar with the SAN aspect and I wanted an idea on how we can migrate 4TB of data to the Hitachi Storage array . The external storage device which consists of the 4TB of data has a USB connection but the UCS system does not.
    Can you give some options as to how this is normally done or can be done? Other than the USB.
    Thanks

    Is your Hitachi array connected directly to UCS, or via a SAN, and if yes, what kind of SAN (Brocade, Cisco) ?
    One can connect a dongle (KVM local I/O cable) to any blade, and get 2 external USB connections:
    The KVM local I/O cable ships with every UCS 5100 Series blade server chassis accessory kit. The KVM local I/O cable provides a connection into the server, providing a DB9 serial connector, a VGA connector for a monitor, and dual USB ports for a keyboard and mouse. With this cable, you can create a direct connection to the operating system and the BIOS running on the server.
    I believe this could be misused to temporarly connect your storage for data transfer, although a very ugly solution.

  • Best Way To Connect 6120 FICs And B250/200M2s To 2 SANs

    We have x2 6120 FICs  connected currently to an EMC CX4 via x4 FC links in the expansion module of each FIC. We have x2 FC links in each FIC left over.  We have a new VNX SAN and in order  to migrate our vSphere infrastructure from the old SAN to the new SAN, I  need some advice on the best manner in which to have the B250 M2s and  B200 M2s with their M81KRs be able to 'see' & communicate with both SANs in order to accomplish the migration.  I have seen some discussion on adding HBA's and 'pinning' them to the appropriate FC links & I have also seen some discussion about using VSANs.  The last time we did this, we just daisy chained the new SAN via the old but we were keeping the same SAN switches.  In our current scenario, we will need to hook the FIC's to the new SAN switches regardless.  Any thoughts or help will be greatly appreciated.
    Thank you.

    The following procedure has been done many times with success
    - don't use pinning, it's a management nightmare
    - use separate physical links and VSAN's to connect the new SAN
    - create additional vhba in the service profile, and move them to the new VSAN
    This allows you to migrate, read from the old storage, and write to the new one (e.g. with storage vmotion)

  • Connecting UCS to IBM DS4700, FC zoning

    I am trying to accomplish connecting my UCS to an older SAN that I have to migrate data off.  I currently have a UCS system that is connected to an EMC VNX using 8G FC.  The zoning for this is configured in my UCS.  All works well with the connection to the VNX and I have dual active/active paths working. What I am trying to do is connect a second SAN to my UCS system, a IBM DS4700.  This DS4700 currently has a Brocade FC Switch connected to it, which then connects to a IBM bladecenter chassis.
    I configured a second VSAN for the IBM array and configured the port on my fabric interconnect with that VSAN.  I went into the IBM array and I could see the UCS WWN for my HBA, so I connected it to my UCS.  When I did this, I had an unexpected result.  My VMWare ESXi host on the UCS could see all the datastores on the IBM DS4700 BUT lost connection to all the ones on the VNX.  Also, on the IBM DS4700, all of my paths failed over to the controller that had the host connection from the UCS.  I tried to fail them back over to the other controller but they wouldn't move until I disconnected the UCS from IBM DS4700.  Once disconnected from the UCS, everything went back to normal on both sides.
    Does any one have an idea on how I am setup wrong here?  The ESX host on the UCS could see the datastores on the IBM so it is somewhat correct but it caused all sorts of problems.
    Thanks in advance.

    yes, zones are created on UCS.
    Ok, so you don't have enough host ports to connect Controller A and Controller B to each FI. Since you are experiencing some odd failovers i would do this than. Since this is a migration effort and will not be a permanent configuration you can try this route ..connect both controllers to just one FI:
    UCS FI FABRIC A:
    IBM DS4700 Controller A - Host Port 2
    IBM DS4700 Controller B - Host Port 2
    this will ensure that UCS servers have access to both controllers so if a LUN on DS4700 happens to failover to another controller, UCS servers can still connect to it. 
    @dynamoxxx

  • UCS SAN LUN access problem

    Hi All
    i have UCS manger 4.3q, 2xFI 6140 and connected to Cisco MDS 9509 v4.2( 4 FC link from FIA to MDS A, and 4 FC uplink from FIB to MDS B) and connected to SUN SAN storagetek 6140(one FC port to MDS A from SP1 and one FC port to MDS B from SP2), i created service profile with 2 VHBA for FIA and FIB (with different VSAN), after that we installed ESXi 4.1 on local disk but when we tried to brows LUN created on SAN we can not.
    from both FI we can see WWPn:WWPN for each VHBA in created server, from MDS also i can see floggi output for SAN (WWN,WWPN) as target and Server VhBA as initiater.
    i make all possible isolation even i disbaled FC of FI B, and till now we can not access LUN on  SAN, as per SAN admin LUNS created and mapped correctly, so appreciate your support to solve this.
    Many thanks.

    Hi
    From your statement, I understand that you are using SUN SAN storagetek as disk array storage. Cisco does not list the SUN SN storagetek in their interoperablity matix and this could be one of the reason. Pleas go through the link below.
    http://www.cisco.com/en/US/docs/switches/datacenter/mds9000/interoperability/matrix/Matrix8.html#wp323848
    Ram

Maybe you are looking for

  • How can I minimise the file size of a greyscale image ?

    Hi, What methods are there for making as small as possible the file size of a greyscale image. I need to keep the resolution at 200pixels per inch. The image is going to be big, 5835mm wide and 1780mm tall ! Some of them have some fine soft detail so

  • Hi, how do I erase my mac?

    Hi, I am taking my iMac tomorrow to get the hard disk changed due to the Segate recall. Mine is working fine, but I want to prevent future problems. However, I do not want to take my T1 disk almost full with personal data... I have already made two c

  • Mail.app

    I am currently using another email client (Mulberry), and because this is no longer being updated I'll have to migrate. So I'm considering Mail. I do have some questions, however, that someone may be able to answer. For various reasons I don't use IM

  • What is the use of FOLDER NODE in SMARTFORMS?

    what is the use of FOLDER NODE in SMARTFORMS? please explain.

  • Prob with Updation of Primary Key field '' SPRPS '' in PA2001. Plz HELP

    Can anyone please tell me how to update a primary key field in HR Tables (PA2001 and PA2002). I need to update sprps field in both the tables. I used HR_Infotype_Operation function module, but still it is not updating the field. Pls find the followin