UC on UCS with iSCSI

Hi,
I was wondering if there is any update regarding UC on UCS support for booting from iSCSI SAN?
I would like to implement the follwoing scenario: B-Series Chassis with an ESX 5.1 B200M3 Server which hosts UC Apps (UCSM 2.1).
Could we boot that server from iSCSI SAN (network running 10Gb, no-drop QoS policy for boot vNICs)?
According to the link below, only FC SAN is supported, is that still correct? Is this feature enhancement on the roadmap?
http://docwiki.cisco.com/wiki/UC_Virtualization_Supported_Hardware#Storage
Thanks!
Dmitri

Hello Dmitri,
UCS servers supports iSCSI boot for ESXi.
Please check here for minimum HW / SW requirements
https://supportforums.cisco.com/docs/DOC-18756
HCL - HW / SW / FW Matrix
http://www.cisco.com/en/US/products/ps10477/prod_technical_reference_list.html
UCSM config guide
http://www.cisco.com/en/US/products/ps10281/products_installation_and_configuration_guides_list.html
Padma

Similar Messages

ISCSI Booting Win2k8R2 on UCS with EqualLogic

We've been testing iSCSI booting on UCS with 2.0(1t) and the Palo M81KR with an EqualLogic PS6010. We are connecting through a 10GbE switch via an uplink port. However, we've hit a snag and want to see if anyone else has gotten around this.
The EQL shows connections from UCS when booting; however, Windows does not have the Palo drivers and doesn't show the target disk. When adding the M81KR driver, the connection gets dropped so Windows still does not show the target disk.
We've tried connecting the array directly to an appliance port on the FI but got some ENM source pinning failed error, a different issue at this point.
We've also tried slipstreaming all UCS drivers into the Windows media but that doesn't let us proceed either.
We've gotten RHEL6 to install so we know the configuration is viable.

Hello Thomas,
The EQL shows connections from UCS when booting; however, Windows does not have the Palo drivers and doesn't show the target disk. When adding the M81KR driver, the connection gets dropped so Windows still does not show the target disk.
There is small trick to make the target disks visible after installing the right drivers. Please make sure that after re-mapping the W2K8 ISO image, click Refresh button on the Installer screen and verify the outcome.
http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/b/os/windows/install/2008-vmedia-install.html#wp1059547
Driver location in driver ISO image
http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/b/os/windows/install/drivers-app.html#wp1014709
Padma

UCS-B: iSCSI performance with M51KR-B BCM57711 vs Palo M81KR

Cisco pushes M81KR card saying that there's no reason to use anything else. What about systems with iSCSI storage (ESXi boots from local drive, VMs are on iSCSI storage, no iSCSI boot)? Is there any performance advantages to using BCM57711 card? It has iSCSI TOE, while M81KR does not, isn't this enough of a reason to use BCM57711 for iSCSI environments?

Roman,
You are correct that the current generation of M81KR VIC does not have the TOE for iSCSI as the broadcom card does. However our adaptors are designed with adequate resources to provide similar performance.
Let me see if I can dig up some performance metrics so you can compare.
Regards,
Robert

Prblem with iSCSI on Win Server 2012R2 with HyperV role

Hi all,
I have some problems with iSCSI on Win server. The problem is the following.
When I restart server it cannot find the path with VMs configuration and VMs can't start. After few minutes all problems are gone and HyperV can find everything but I must start VMs manually.
The server is DELL R710 with Broadcom NICs. I tried to configure LAN interfaces for iSCSI in two ways. First - from OS and second - from Broadcom BACS with disabled NDIS/Ethernet and enabled iSCSI. The results are the same.
I have two more servers connected to the storage in the same way and everything is fine there.
Events are following:
1. Source MSiSCSI. ID 108
Status 0x00001069 determining that device interface \\?\{8e7bd593-6e6c-4c52-86a6-77175494dd8e}#MsVhdHba#1&3030e83&0&01#{2accfe60-c130-11d2-b082-00a0c91efb8b} does not support iSCSI WMI interfaces. If this device is not an iSCSI HBA then this error
can be ignored.
2. Source bxois. ID 1
Initiator failed to connect to the target. Target IP address and TCP Port number are given in dump data.
3. Source MSiSCSI. ID 113
iSCSI discovery via SendTargets failed with error code 0xefff0003 to target portal *10.10.45.36 0003260 B06BDRV\L4SC&PCI_163914E4&SUBSYS_02351028&REV_20\5&2457021e&0&30050200_0 10.10.45.37.
4. Source Hyper-V-Config. ID 4096
The Virtual Machines configuration 72D1CB1A-A7E3-425A-A709-DA9F6BF0E1A9 at 'I:\VM\exch01-t' is no longer accessible: The system cannot find the path specified. (0x80070003).
5. Source SMagent. ID 1
Message from SM agent service: SMagent: The SMagent service attempted to start but terminated. Possible causes include: [1] The access virtual disk is disabled in NVSRAM. [2] No RAID controller modules with compatible firmware were found. [3] The default
logical unit number (LUN) assigned to the access virtual disk (typically 7 or 31) is not in the range supported by the host or is already in use by the host for another device. See your storage management documentation for more details.
The Host Context Agent did NOT start because 0 RAID controller modules were found.


Hi Sergey,
>>When I restart server it cannot find the path with VMs configuration and VMs can't start. After few minutes all problems are gone and HyperV can find everything but I must start VMs manually.
As a workaround you can set the "startup delay" for VMs .
>>Initiator failed to connect to the target. Target IP address and TCP Port number are given in dump data.
The possible cause may be the network stack is not fully prepared when the initiator was trying to connect to persistent targets. The initiator will try to connect. When the network stack is fully prepared, the connection should be successfully established.
If you receive this error when the iSCSI target device that is listed on the
Favorite Targets tab no longer exists, you can resolve this issue by removing the iSCSI target device from the list of favorite targets.
If you receive this error, and you cannot access an iSCSI target device that is still configured on the network, make sure that the client computer has network connectivity to the iSCSI target. Additionally, make sure that name resolution is working correctly.
If you have successfully connected to your iSCSI target device despite this error, it indicates that the connectivity issue was temporary. Therefore, you can safely ignore this Error event.
https://support.microsoft.com/kb/976072?wa=wsignin1.0
Best Regards
Elton JI
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Windows 2008 R2 cluster with iSCSI storage.

We have a 2 node cluster setup with iSCSI storage. Is there a way to set the storage so that it becomes active on a specific node, when that node is online? The storage is failing over properly but we have to do a manual failover to get the
server back on the "primary" node.

We have a 2 node cluster setup with iSCSI storage. Is there a way to set the storage so that it becomes active on a specific node, when that node is online? The storage is failing over properly but we have to do a manual failover to
get the server back on the "primary" node.
Actually it's a way it should work from the very beginning... Make sure you did not disable automatic fallback. See for more information:
Configure Failover and Failback Settings for a Clustered Service or Application
http://technet.microsoft.com/en-us/library/dd197473(v=ws.10).aspx
Good luck!
StarWind Virtual SAN clusters Hyper-V without SAS, Fibre Channel, SMB 3.0 or iSCSI, uses Ethernet to mirror internally mounted SATA disks between hosts.

3 Node Failover Cluster With iSCSI

Is there any information available on the steps to create a 3 node failover cluster with iSCSI storage? Is there a step-by-step guide? I looked around but couldn't find much. Thanks!

Hi SCPSTech,
The 3 node cluster create steps same with 2 node, you can refer the following step by step white paper create the 2 node cluster then add the another node to cluster.
Configuring Failover Clusters with Windows Storage Server 2008
http://blogs.technet.com/b/storageserver/archive/2009/12/17/configuring-failover-clusters-with-windows-storage-server-2008.aspx
Add a Server to a Failover Cluster
http://technet.microsoft.com/en-us/library/cc730998.aspx
More information:
Add or Remove Nodes in a SQL Server Failover Cluster (Setup)
http://msdn.microsoft.com/en-us/library/ms191545.aspx
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

UCS with C-Series Servers

What do we need to create a standalone UCS with 3 x C210 servers

Connection options will be anything compatible with the Nexus 5000 series of switches and FEXs. This can be Optics or Copper (Twinax).
In choosing one over the other I would base it mainly on distance requirements.
If you can connect the 6100's and FEXs within 10m then go with twinax cable.
- Twinax is about 1/10th the cost of optical transceivers and OM3 fibre cable.
- Twinax uses less power (0.1W for twinax vs. 1W per fibre)
- Twinax has lower latency than fibre.
If you need a length longer than 10m then optics would be your only choice.
Full details on transceiver compatibility here:
http://cisco.biz/en/US/prod/collateral/switches/ps9441/ps10110/data_sheet_c78-568589_ps9670_Products_Data_Sheet.html
Regards,
Robert

Port-Channel MDS & UCS with a particular vsan

I am having trouble setting up a port-channel between MDS & UCS with a particular vsan. I was able to get a port-channel setup on VSAN 1 between and MDS9513 5.0(4d) and UCS 6120 XP 4.2 (1). When I try to do it with a specifc VSAN it fails. I set the VSAN on the 9513 interfaces and created the port-channel but it looks like it still wants to default to VSAN 1 when I do a sh int. I have added the same VSAN on the UCS side as well. I have tried to see if could set the vsan on the port-channel but it doesn't look like that command is offered. Any ideas?

Hello
Having no exp of UCS switches, this may be a bit off, but....
The vsan the port channel PORTS are in is of no consequence. The VSAN's that are allowed to traverse the trunk are the important bits. i.e:
interface port-channel 1
switchport trunk allowed vsan 1
switchport trunk allowed vsan add 60
switchport trunk allowed vsan add 80
Steven

SOLARIS 10 with iSCSI Problem "not a block device"

Hi Guys.
I almost reached it to build an iscsi connection with a Netgear readynas 2100.
But I have still one Point which makes me a Problem!!!
Everything works, except mounting the device....
It always Sais me: "not a block device"
At the bottom you can see an output of the whole configuration that I did.
Has anybody maybe a tip for me? Thanks in advance, Mischa
login as: root
Using keyboard-interactive authentication.
Password:
Last login: Fri Dec 18 01:18:30 2009 from pnm
Sun Microsystems Inc. SunOS 5.10 Generic January 2005
Sourcing //.profile-EIS.....
root@sun001 # iscsiadm list discovery
Discovery:
Static: disabled
Send Targets: disabled
iSNS: disabled
root@sun001 # iscsiadm modify discovery -s enable
root@sun001 # iscsiadm modify discovery -t enable
root@sun001 # iscsiadm modify discovery -i enable
root@sun001 # devfsadm
root@sun001 # devfsadm -C
root@sun001 # ping 172.16.251.215
172.16.251.215 is alive
root@sun001 # iscsiadm list discovery
Discovery:
Static: enabled
Send Targets: enabled
iSNS: enabled
root@sun001 # iscsiadm add discovery-address 172.16.251.215
root@sun001 # iscsiadm list discovery-address
Discovery Address: 172.16.251.215:3260
root@sun001 # iscsiadm list discovery-address -v
Discovery Address: 172.16.251.215:3260
Target name: iqn.2009-12.Z-NAS-B0204:znaszim
Target address: 172.16.251.215:3260, 1
root@sun001 # format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c1t60014052E198270014ED001000000000d0 <DEFAULT cyl 65267 alt 2 hd 255 sec 63> znaszim1
/scsi_vhci/disk@g60014052e198270014ed001000000000
1. c3t0d0 <DEFAULT cyl 17747 alt 2 hd 255 sec 63>
/pci@7b,0/pci1022,7458@11/pci1000,3060@2/sd@0,0
2. c3t2d0 <DEFAULT cyl 17747 alt 2 hd 255 sec 63>
/pci@7b,0/pci1022,7458@11/pci1000,3060@2/sd@2,0
Specify disk (enter its number): ^C
root@sun001 # dev
devattr devfree devfsadm devinfo devlinks devnm devreserv
root@sun001 # dev
devattr devfree devfsadm devinfo devlinks devnm devreserv
root@sun001 # dev
devattr devfree devfsadm devinfo devlinks devnm devreserv
root@sun001 # devfsadm -c iscsi
root@sun001 # iscsiadm list target -S
Target: iqn.2009-12.Z-NAS-B0204:znaszim
Alias: LIO Target
TPGT: 1
ISID: 4000002a0000
Connections: 1
LUN: 0
Vendor: LIO-ORG
Product: FILEIO
OS Device Name: /dev/rdsk/c1t60014052E198270014ED001000000000d0s2
root@sun001 # mkdir /export/iscsi
root@sun001 # mount /dev/rdsk/c1t60014052E198270014ED001000000000d0s2 /export/iscsi/
mount: /dev/rdsk/c1t60014052E198270014ED001000000000d0s2 not a block device
root@sun001 #
-----------------------------------------------------------------

Ok. Sorry i have to explaine it in an other way.
The Storage Device is a Netgear Ready NAS 2100.
Netgear Ready NAS with a Linux os.
The OS Supports different Protocols like: CIFS / FTP / HTTP/ iSCSI etc...
Now im trying to use an other protocoll (cifs) to store the data on the Netgear NAS.
i found smbclient and was able to open a connection to the NAS.
root@sun001 # /usr/sfw/bin/smbclient //172.20.0.51/video_net -U usrvideo
Password:
Domain=[Z-NAS-A0111] OS=[Unix] Server=[Samba 3.4.5]
smb: \> ls
. D 0 Tue Feb 23 11:12:04 2010
.. D 0 Thu Feb 18 10:38:52 2010
172.22.1.58.lnk A 747 Fri Feb 19 19:18:37 2010
172.22.1.55.lnk A 747 Fri Feb 19 18:41:07 2010
65535 blocks of size 33553920. 65535 blocks available
smb: \>
Is there a way to mount the smb connection when the server starts up?
I have to find a way to attach the NAS like a local folder...
And that is why i choose iSCSI before..
Regards
mischa
Edited by: mischu on Feb 26, 2010 2:34 AM

Cisco UCS with FEX system Component requirements

Hi ,
I am looking for quick suggestion for required components to have a VMware vSAN implemented using FEX system with maximum Fabric trough put. Ideally a configuration for without multipath using single Fabric switch and later on to be able to upgrade to Multipath fabric.
We are in great rush to provide POC concept and was looking if you folks can suggest me on this. If need be you want to talk to me more in detail I can available.
Appreciate your help here.
Who can I reach to able to pull up build and quote the configurations for implementing complete UCS solution.
Are these below components absolutely required ?
2 x Nexus 2232PP 10GE Fabric Extenders
The Cisco Nexus 2232PP 10GE provides 32 x 10Gb loss-less low latency Ethernet and Fiber Channel Over Ethernet (FCoE) Small Form-Factor Pluggable Plus (SFP+) server ports and eight 10 Gb Ethernet and FCoE SFP+ uplink ports in a compact 1 rack unit (1RU) form factor. They enable Seamless inclusion of UCS rack servers into UCS Manager domain with UCS blade servers when connected to the UCS 6200 Fabric Interconnects, providing converged LAN, SAN, and management connectivity.
We currently have these below servers :
2 x UCSC-BASE-M2-C460
        524 GB RAM
        No SSDs
        No VIC Card
        4 x SAS 1 TB Drives
        1 x L1 Intel 1 Gbps Ethernet Adapter
        1 x L2 10Gbps Ethernet Adapter
        1 x LSI Mega RAID SAS 9240-8i (no RAID 5 support, Need a card that supports RAID5)
1 x UCSC-C240-M3L
        132 GB RAM
        30 TB SAS HDD
        1 x VIC Card
        1 x Intel I350 Gigabit Ethernet Card with 4 ports
        1 x LSI Mega RAID SAS 9240-8i (no RAID 5 support, Need a card that supports RAID5)
1 x 5548UP Nexus Switch ( Will I be able to use this switch in place of Nexus 2232PP 10GE Fabric Extenders to achieve complete UCS solution)

Cisco UCS Manager 2.2 supports an option to connect the C-Series Rack-Mount Server directly to the Fabric Interconnects. You do not need the Fabric Extenders. This option enables Cisco UCS Manager to manage the C-Series Rack-Mount Servers using a single cable for both management traffic and data traffic.
If you need high performance low latency (storage, for VMware VSAN), direct connection to UCS Fabric Interconnect and/or N5k is recommended.

UCS with UCCX 8.5

Hello I need help!
What are the recommendation to install CCX-85 over UCS-CS210M2-VCD2.
can anyone help me?
Best Regards.

Can you eleborate your on your question? What exactly are you looking for?
CCX 8.5 is supported on this hardware with 3 different deployment sizes (OVA files) 100, 300 and 400 as documented here:
http://docwiki.cisco.com/wiki/Virtualization_for_Unified_CCX
http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#Cisco_Unified_Contact_Center_Express
HTH,
Chris

Migration win2008r2 to new domain with ISCSI NAS

Hello
I need to move entire server from abc.com domain to zyz.com domain, but the server has an attached iscsi nas (maybe is a qnap).
the permission were done with windows not the nas GUI. I worries would be the permission being removed.
I will be using quest migration tool but still not feeling great about it.
what are my changes of losing permission or maybe needing to do the iscsi under windows.?
thank you

Hello,
this require the change to the other new forest with ADMT, free from Microsoft or other migration tools.
If the users, machines etc. are migrated and the trust is still available you can use robocopy for the data to migrate to the other domain.
http://blogs.msmvps.com/mweber/2010/03/25/migrating-active-directory-to-a-new-forest/
https://jorgequestforknowledge.wordpress.com/2014/06/19/microsoft-released-an-admt-version-to-also-support-w2k12r2/
Best regards
Meinolf Weber
MVP, MCP, MCTS
Microsoft MVP - Directory Services
My Blog: http://blogs.msmvps.com/MWeber
Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.
Twitter:

Ucs blade iscsi boot cannot install windows server

Hi all,
i have some problem when i try to install windows server 2008 in nexenta storage using iSCSI via ucs b-series, but its working fine when i install ESXi 5.5. i cannot find drive on windows server installation, and in ESXi i can see all LUN what im create before in nexenta storage and working when i install it.
this vnic iSCSI Configuration:
vnic_id: 13
          link_state: Up
       Initiator Cfg:
     initiator_state: ISCSI_INITIATOR_READY
initiator_error_code: ISCSI_BOOT_NIC_NO_ERROR
                vlan: 0
         dhcp status: false
                 IQN: test:iqn.2014-11.com.:8
             IP Addr: 192.168.1.59
         Subnet Mask: 255.255.255.0
             Gateway: 192.168.1.5
          Target Cfg:
          Target Idx: 0
               State: ISCSI_TARGET_READY
          Prev State: ISCSI_TARGET_DISABLED
        Target Error: ISCSI_TARGET_NO_ERROR
                 IQN: iqn.2010-08.org.illumos:02:windowsboot
             IP Addr: 192.168.1.49
                Port: 3260
            Boot Lun: 6
          Ping Stats: Success (986.646ms)
        Session Info:
          session_id: 0
         host_number: 0
          bus_number: 0
           target_id: 0
does anyone can help me to solve this issue?
thanks in advance - fadli

enic / fnic driver have to be installed; they are not part of any Windows OS.
they can be found in
Downloads Home
Products
Servers - Unified Computing
UCS B-Series Blade Server Software
Unified Computing System (UCS) Drivers-2.2(3)
ISO image of UCS-related drivers
ucs-bxxx-drivers.2.2.3.iso
depending on the UCS version.

UCS with vsphere to BFS on IBM XIV

Hello,
It seems that IBM XIV storage has a limitation around the minimum LUN size, which appears to be 17 GB. Taking into consideration that one of the added values of UCS is the boot from SAN using the service profiles, and that most of the UCS implementations are based on VMware (the OS of which, ESXi barely needs 300 MB of installation), that means one has to underutilize 17GB LUNs for ESXi booting, which might be a waste of money. I was wondering whether anyone here found the same issue in their customers and whether does this also happen in other disk arrays (EMC Symmetrix for instance), or only in IBM XIV.
Thanks a lot,

Dani,
Also check out this blog. I thought you maybe able to get around this by creating a thin provisioned pool, and then creating multiple LUN's for your ESXi hosts in that pool, however, it looks like on the first write to that LUN it is going to attempt to take the 17GB min LUN size.
I think you maybe stuck with the 17GB LUN per host. I will say that some other storage vendors do not have this 'limitation', this is due to the XIV architecture.
http://patrickv.info/wordpress/2009/07/ibm-xiv-thin-provisioning/
Regards,
Jeremy

Use xsan with iscsi

I am looking for a solution to use a iscsi target from freenas with mac server via xsan. Is there a howto?
BR
Homer

So even with 10.0.1 there's still no way of using non-Xsan networkdrives for sharing files ?

UC on UCS with iSCSI

Similar Messages

Maybe you are looking for