UCS C Series SAN Boot

Hi All,
How to configure SAN Boot on the UCS C Series platform ?
On B Series, we can configure the boot order from vHBA, but on the UCS C Series I found nothing.
The C Series SAN boot had being enabled and also the boot target was configured on the vHBA properties, but the C Series can't boot from SAN
Attached are the detailed of the configuration on C Series
Please help, if you have C Series boot from SAN succesfully
Thanks,
Gofi

Hi Padma,
Yes, that will be the flogi into the upstream switch.
Below are the configurations of Nexus 5K, while I used 2 N5k as the upstream FCoE switch
N5K1# sh run int vfc113
!Command: show running-config interface vfc113
!Time: Wed Jun 17 03:21:56 2009
version 5.2(1)N1(5)
interface vfc113
  bind interface Ethernet113/1/1
  switchport trunk allowed vsan 10
  no shutdown
N5K1# sh run int eth113/1/1
!Command: show running-config interface Ethernet113/1/1
!Time: Wed Jun 17 03:22:05 2009
version 5.2(1)N1(5)
interface Ethernet113/1/1
  switchport mode trunk
  switchport trunk allowed vlan 10,120,125,130,135,200-201
N5K1# sh run | sec fex
feature fex
fex 113
  pinning max-links 1
  description "FEX0113"
  fcoe
fex 123
  pinning max-links 1
  description "FEX0123"
N5K1# sh feature | i fcoe
fcoe                  1         enabled
fcoe-npv              1         disabled
N5K2# sh run int vfc123
!Command: show running-config interface vfc123
!Time: Wed Jun 17 03:24:12 2009
version 5.2(1)N1(5)
interface vfc123
  bind interface Ethernet123/1/1
  switchport trunk allowed vsan 20
  no shutdown
N5K2# sh run int eth123/1/1
!Command: show running-config interface Ethernet123/1/1
!Time: Wed Jun 17 03:24:29 2009
version 5.2(1)N1(5)
interface Ethernet123/1/1
  switchport mode trunk
  switchport trunk allowed vlan 20,120,125,130,135,200-201
N5K2# sh run | sec fex
feature fex
fex 113
  pinning max-links 1
  description "FEX0113"
fex 123
  pinning max-links 1
  description "FEX0123"
  fcoe
N5K2# sh feature | i fcoe
fcoe                  1         enabled
fcoe-npv              1         disabled
The CNA server connected to FEX Nexus 2K, while the Nexus uplinks are controlled by 2 Nexus 5Ks (vPC on the N5K)
Any suggestions ?
Thanks,
Gofi

Similar Messages

  • UCS 1.4(3M) BIOS Issue ? no network/san boot when diskless

    Recreated faithfully on multiple  blades and chassis with VIC cards.  Have many SAN boot nodes in  production and testing and after upgrading firmware this week anytime I  apply my store policy of "diskless" to a blade I lose the ability to  boot from network.  After much effort to work around comes down to no  matter what I do with diskless storeage policy, the configured boot  order will never become the actual boot order.  In the BIOS all network  boot options/reference are invisible, cannot enable nor add to options.   Upon removing diskless storeage profile and applying "any other that I  have" I see in FST that it's powering up internal storage, starting up  and updating pre-boot environments, and other things related that  connected the dots.  Returning to BIOS all reference and options have  returned as I expected due to actual boot order screen updating to match  configured order and hba's of course login the fabric right away, boot  is fine.   While I can faithfully replice across many, many blades, they  are all the models with same mezz running 1.4.3 so curious if anyone  else is seeing, particuaraly now with new version out, as I have done  last few weeks without issues leading me towards the firmware. 
       In a nut shell I see that when going diskless this is actually shutting  down the storage/raid controller.  i can see that clearly but no bios  access to it and not sure what else is or why it's affecting network and  hba also since I cannot see, it's shutting more down than low powering  drive side raid.  I use different profiles due to some blades having  disks removed,  some retain them.  moving a san boot service-profile  dynamically around multiple chassis will fail to associate with errors  on some due to disk setup and all that.  some i have disks pulled and  diskless based on documentation and best practices as this customer  needed several san boot only blades in that pool.  But yes if I use a  storage profile allowing "any disk config" for association whether it  has disks, no disks, raided drives, replaces the diskless policy in same  service profile it faithfully follows my boot order and boots via hba's  across multiple blades, up to about 8 or 10 as of today.....b200-m2's  with vic's
    thx
    dave

    My UCS manager firmware and Adapter is 1.3.1p,
    the boot policy has been set to Boot to SAN,
    I checked "Hardware and Software Interoperability Matrix for UCS System Release 1.3.1"
    It seems the 1.3.1 only can support the "windows 2008 r2 x64 w/Hyper-v",
    so, I updated the UCS manager Bios and the adpter firmware to 2.0, but the I/O module still is 1.3.1p
    I can install the "windows 2008 r2 x64" successfuly...
    Now, my concern is I have a mix component software versions on my ucs blade(I used the UCS manager 1.3.1, IO module 1.3.1, the UCS Bois 2.0.1 and the adapter 2.0.1)
    will the mix component software versions cause some other issues? Dose anyone can give me some suggestion?
    Thanks a lot

  • San Boot Win2K8 R2 SP1 x64 on UCS blades B with M81KR installation issue

    I am trying to install a storage San Boot Win2K8 R2 SP1 x64 on UCS blades,(There are only 1 path to the OS installation drive during the installation.)
        I loaded drivers for the M81K2 following the "UCS Windows Install Guide" , and I can see the LUN I mapped from XIV. I was able to create and format partitions, make it online, but when
        I try to install, windows gives the error:"Windows cannot be installed to this disk. The computer's hardware may not support booting to this disk. Ensure that the disk's controller is enabled in the computer's BIOS menu." 
    any one know this issue?
    Thanks

    My UCS manager firmware and Adapter is 1.3.1p,
    the boot policy has been set to Boot to SAN,
    I checked "Hardware and Software Interoperability Matrix for UCS System Release 1.3.1"
    It seems the 1.3.1 only can support the "windows 2008 r2 x64 w/Hyper-v",
    so, I updated the UCS manager Bios and the adpter firmware to 2.0, but the I/O module still is 1.3.1p
    I can install the "windows 2008 r2 x64" successfuly...
    Now, my concern is I have a mix component software versions on my ucs blade(I used the UCS manager 1.3.1, IO module 1.3.1, the UCS Bois 2.0.1 and the adapter 2.0.1)
    will the mix component software versions cause some other issues? Dose anyone can give me some suggestion?
    Thanks a lot

  • UCS Central - Making Boot Policy - SAN boot target Provisioning

    Gents
    Some objects is always related to the domains and need to be provisioned in global like
    VLANs: but we can did it by Provisioning VLANs with UCS Central Using VLAN ID Aliasing.
    VSANs: the same idea in VLAN ID Aliasing.
    Boot Policy adding SAN boot target : what about this issue how can I provision it so I can configure it globally in abstract way then it will take targets depend on domain during associating the global service profile.

    @Gmonroy
    Thanks for support
    But if I need to make a global Service profile temp so I can deploy SF from it in any domain, and if  I referenced this service profile temp to one boot policy so i need to unbind each service profile created from this temp to associate a different boot policy in each domain ? " I will lose the benefit of updating service profile template "
    Or I have to create different template per domain ? " I will lose the key benefit of  centralizing Templates in UCS central"
    Or there is any workaround to deply this senario. 

  • B230-M2 - MK81KR - Win 08 R2 San Boot

    Chaps.
    I need to SAN boot this server with Win 08 R2 on the metal.
    Service profile works with VMware, so the Zoning/Masking is correct.
    On install from 08 Disk, no Hard Drives shown, I loaded the Cisco Storage Driver, now I see the Lun twice, Disk1
    Unpartitioned space and Disk2  Unpartitioned space.
    There is a Bios not enabled warning when I try to install.
    UCS Version 1.4.3Q
    Driver Disk : 1.4.1
    Please assist
    Danie

    No change on either option.
    On the CD sequence.
    I clicked load driver, mounted the 1.4.3 Drivers cd, browsed to Windows\Storage\Cisco\MK81KR\Win08R2\64
    I listed the driver.
    I then mounted the Win08 cd, and clicked next to load the driver, it could not find the path, as I had un-mounted the driver disk, so remounted 1.4.3, clicked next, green bas flashed a couple of times, and I got to the Where do you want to install screen. My 40GB disk showed as offline.
    Mounted the Win08 Disc, and clicked refresh, twice....
    Disk stayed offline, show details on the error allowed me to bring the disk online.
    Now the error stated that the BIOS is not setup for booting of this controller, ignored the warning, and clicked next.
    Setup was unable to create a new system partition or locate an existing system partition.
    I can create and delete partitions manually.
    EFI disabled and the same install sequence, same results
    Thanx

  • XenServer 6.1 SAN boot on B200M2

    I'm new to XenServer.  We have UCS with B200M2's with the M81KR CNA in them.  We primarily use VMware ESXi and we SAN boot all of those machines.  We have had no issue SAN booting ESXi servers.  I've created a new serivce profile template for the XenServer's and brought up a couple machines.  I've allocated the storage and when I got to install XenServer it doesn't see the boot LUNs.  I know the storage is allocated properly.  I can see the LUNs when the blade is booting and I can install ESXi onto the boot LUNs without issue.  The issue is with XenServer seeing the LUN.  I did the F2 > mulitpath option that it says to do in the Appendix of the install guide for XenServer but that makes no difference.  What needs to be done to have XenServer see a boot LUN on a B200M2?

    6.0
    Please see the UCS Support Matrix tool for further info:
    http://www.cisco.com/web/techdoc/ucs/interoperability/matrix/matrix.html
    Support is coming in the upcoming UCSM 2.1 release before the end of the year (tentatively).  I'm just confirming if support will be included in a future 2.0.x patch or not.
    Regards,
    Robert

  • SAN Boot Target-Cisco folks, please advise

    Hi:
    Just want to know the difference of the following 2 configurations for SAN Boot for UCS with 2 WWPNs being presented from SAN Storage
    Array: I know 1 will work, but how about Option 2????
    Cisco UCS manual DOES NOT go into the details needed.
    1.
    SAN Primary, SAN Target Primary- vHBA-A - Fabric A
    SAN Secondary, SAN Target Primary - vHBA-B - Fabric B
    VS
    2.
    SAN Primary, SAN Target Primary - vHBA-A - Fabric A
    SAN Secondary, SAN Target Secondary  - vHBA-B - Fabric B
    Thanks.
    KP Sim

    I don't think the system will let you introduce a secondary target on the second vHBA if you haven't defined a primary target for that vHBA.
    SAN boot works as follows if you have a policy with 4 targets and 2 vHBAs:
    1. try primary vHBA, first (primary) target
    2. if that doesn't work, try secondary target on primary vHBA
    3. if that doesn't work, switch to secondary vHBA, primary target
    4. if that doesn't work, try secondary target on secondary vHBA

  • UCS B series IOM firmware upgarde.

    Dear Experts;
    We have one BUG in our UCS B series server as below link.
    https://tools.cisco.com/bugsearch/bug/CSCue49366/?reffering_site=dumpcr
    The work around is to do the IOM  firmware upgarde.
    As teher are several Firmware are associated with the  UCS system how to knwo the dependency and how to know which firmware is compatible with the uCS server.
    Please assist me to get teh proper IOM firmware .I opened one TAC and they are telling TAC doesn't support this we have to contact cisco AS team and we don't have cisco AS team contract.
    Regards
    Debashis

    Dear Walter;
    Really appreciated your expert technical advice.
    I have one small question as below if you can answer it..
    As per the existing setup..
    This UCS system is connected with the EMC storage Model:VMAX-1SE  Version:5876.
    We have no idea if   UCS firmware version 2.1(3c) is compatible with the MC storage Model:VMAX-1SE  Version:5876..
    I have opened the TAC and also went through the Compatibility matrix where it mentioned as attached and to conatct EMC vendor.
    We opened case with EMC they are telling contact Cisco and Cisco TAC telling contact EMC.
    IS there any way we can know this?
    Note as per the attachment:
    5. Direct Connect FC/FCoE topologies are supported with this array.
    6. Non-default adapter settings are typically required by storage vendors and found on their support list.
    7.Multiple array and switch models supported with UCS by the storage vendor are on their support list.
    12.iSCSI Boot is supported Both Appliance and Uplink ports are supported unless otherwise noted.
    26. Supported for NFS/CIFS access via appliance ports on the Fabric Interconnect

  • PXE Errors - new install of CUCM on UCS C series servers

    Hi All
    I'm in a middle of production install of CUCM , CUWL and IM and Presence on Cisco UCS Servers C220 and C240.
    Until last friday I borught the CUCM cluster along with CUWL server online and lastly just completed the install of IM and Presence PUB left home.
    Then tried logging on Sunday from home via vSphere client unable to connect to these boxes and the webURL's either of apps didn't work.
    I presumed something and then tried to gain access via CIMC port and after launching KVM console I see the attached PXE errors.?
    I'm not sure why this happend all of a sudden nothing changed in the boot order nor in the network.
    Please send me into right direction....this structure I had up and running from last one week and phones registered too.
    Thanks
    Mohammed

    Never mind I figured it out myself and you'll surpised how fragile the UCS C series servers are as I was running them on single power supply and the inside hardware was acting weird for this purpose and once I connected the second power supply and rebooted the server the vmware loads and everything is back online.
    How strange this issue was ...
    Thanks
    Mohammed

  • 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 B-Series Latest Version New Features

    Welcome to this Cisco Support Community Ask the Expert conversation. This is an opportunity to learn and ask questions about the Cisco UCS Manager 2.2(1) release, which delivers several important features and major enhancements in the fabric, compute, and operational areas. Some of these features include fabric scaling, VLANs, VIFs, IGMP groups, network endpoints, unidirectional link detection (UDLD) support, support for virtual machine queue (VMQ), direct connect C-Series to FI without FEX, direct KVM access, and several other features.
    Teclus Dsouza is a customer support engineer from the Server Virtualization team at the Cisco Technical Assistance Center in Bangalore, India. He has over 15 years of total IT experience. He has worked across different technologies and a wide range of data center products. He is an expert in Cisco Nexus 1000V and Cisco UCS products. He has more than 6 years of experience on VMware virtualization products.  
    Chetan Parik is a customer support engineer from the Server Virtualization team at the Cisco Technical Assistance Center in Bangalore, India. He has seven years of total experience. He has worked on a wide range of Cisco data center products such as Cisco UCS and Cisco Nexus 1000V. He also has five years of experience on VMware virtualization products.
    Remember to use the rating system to let Teclus and Chetan 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 May 9, 2014. Visit this forum often to view responses to your questions and the questions of other Cisco Support Community members.

    Hi Jackson,
    Yes its is possible.    Connect the storage array to the fabric interconnects using two 10GB links per storage processor.  Connect each SP to both fabric interconnects and configure the ports on the fabric interconnect as “Appliance” ports from UCSM
    For more information on how to connect Netapp storage using other protocols like iSCSI or FCOE  please check the url below.
    http://www.cisco.com/c/en/us/products/collateral/servers-unified-computing/ucs-6100-series-fabric-interconnects/whitepaper_c11-702584.html
    Regards
    Teclus Dsouza

  • UCS C series maximum hard drive size

    Looking for info on the maximum hard drive size support on teh UCS C series.  I have a C200M2 that I added a 4TB drive, I have updated the server to the latest firmware and BIOS however the server shows the drive size is 2TB.

    Hi!  and welcome to the community mate!
    Here is the table that shows the supported disk's PID for the C200 server:
    http://www.cisco.com/c/dam/en/us/products/collateral/servers-unified-computing/ucs-c-series-rack-servers/c200m2_sff_specsheet.pdf
    If you successfully installed ONE HDD of 4GB and made it work, you were lucky cause I don't see any disk with that size, I have not even seen a disk of that size for UCS yet.
    I am wondering if perhaps you installed 4 disks of 1TB and configured them in RAID 1 which would explain the reason for the size to go down to half of the capacity of the array as RAID 1 is a mirror.
    Let me know if I misunderstood you.
    Rate ALL helpful answers.
    -Kenny

  • Solaris 10 SAN Boot issue

    During Solaris 10 Installation on a SAN Based disk, SUN Fire V10 was not rebooting after the first CD installation. It does memory dump...

    I really don't like san boot for operating system. You have too many points of failure for the basic operation.
    Anyway, during installation, ensure that you access the disk using just one path (using zoning for example). After you enable and configure MPxIO, you could enable other paths.

  • SAN boot disk in a cluster node?

    As far as I remember, SC requires local boot disk.
    Is it possible to use the SAN boot disk? Can this configuration work being just not supported by SUN or there is some technical limitation ?
    I am thinking of low price configuration with two diskless X2100s + HBAs and SAN storage. Possible?
    thanks
    -- leon

    As far as I remember, SC requires local boot disk.
    Is it possible to use the SAN boot disk? Can this
    configuration work being just not supported by SUN or
    there is some technical limitation ?The rule for boot disks gos like this:
    Any local storage device, supported by the base platform as a boot device, can be used as a boot device for the server in the cluster as well. A shared storage device cannot be used as a boot device for a server in a cluster. It is recommended to mirror the root disk. Multipathed boot is supported with Sun Cluster when the drivers associated with SAN 4.3 (or later) are used in conjunction with an appropriate storage device (i.e. the local disks on a SF v880 or a SAN connected fiber storage device).
    So your boot disk can be in a SAN as long the base platform supports it as a boot disk and it is not configured as a shared lun in the SAN (i.e. visible to other nodes than the one that uses it as boot disk).
    I am thinking of low price configuration with two
    diskless X2100s + HBAs and SAN storage. Possible?You need to check the support matrix of the storage device you plan to use, if it is supported as a boot device for the X2100 + HBA. If the answer is yes, you just must make sure that this lun is only visible to that X2100.
    Greets
    Thorsten

  • Solaris Patching/SAN Boot

    I have just created an ABE on a SAN device, upgraded it and then booted from it.
    Its been a long journey, and involved a SR with oracle.
    I was new to it and am astonished at how hard it has been. Not hard in the sense that anything was over complicated, but the tangle mess of patch levels and gathering information on server firmware, SAN boot, HBA firmware, patches etc has been a nightmare. Not sure whether its me just new to patching solaris 10 etc, but I have literally trawled through a couple of dozen documents, countless web browsing and a few grey hairs  just to achieve this.
    I will hold my hand up, some of it was of our own making - I was patching a system that had not been touched in a number of years.
    Anyone had a similar experience or does it get easier?!?!?

    I really don't like san boot for operating system. You have too many points of failure for the basic operation.
    Anyway, during installation, ensure that you access the disk using just one path (using zoning for example). After you enable and configure MPxIO, you could enable other paths.

Maybe you are looking for