UCS blade m420 m3

Similar Questions

• Monitoring of virtual machines running on the UCS blades

  We are in the process of migration of servers HP rack to Cisco UCS blades. I have 4 blades UCS running ESXi and dΘmarrez from SAN. We have configured in HP SIM HP servers to monitor hardware issues and the status of the VM. Now Let's watch the material of the UCS in UCS Manager, but I still need to monitor the status of virtual machines. I looked at existing Solarwinds NPM we have all our ESXi HP servers to Solarwinds. What I've discovered, is that we cannot add the individual to NPM ESXi blades, because we can not configure SNMP (or we).

  Which means that migrate us from HP servers for UCS blades, we lose the ability to monitor the State of the CPU and VM.

  How people monitor their virtual machines in an environment of UCS?

  Thank you.

  We monitor our UCS ESXi 5 with SNMP hosts and use Solarwinds NPM.  It works well.  These are the commands that we send through our VMA (free VMware) server to a new host.

  vicfg-snmp - root server - username - password it

  vicfg-snmp - root server - username - password you @162.

  vicfg-snmp - root server - username - password e

  There's probably a way to do it on the console of the host, but I don't know what it could be.

• UCS-blade not boot from local drive

  Hello world

  I have a UCS-blade and UCSM with version 2.1 (1st), I create the startup policy to boot from the local disk and raid 1.

  The problem is that when starting the Server Blade show me the screen in SHELL, in other words starting the server in UEFI mode, I need enter the word "EXIT" to get into the 'ESXi', the version of the ESXi is 5.1.0.

  Attach image

  Anyone have any suggestions

  

  

  THK for help me!

  Joshua,

  I would like to know which model server you use and if the ESXi version you have installed is the customized version of Cisco ESXi?

  I bet it's a new facility... It seems that the server does not see a boot image, even if it looks like the strategy of starting point actually on local disks, but I saw strange things how to get when the not custom ESXi .iso image is used.

  Try to use the custom version found here.

  https://my.VMware.com/Web/VMware/details?downloadGroup=Cisco-ESXi-5.1.0-GA-25SEP2012&ProductID=285

  And compatibility with one of my favorite tools:

  http://www.Cisco.com/Web/TechDoc/UCS/interoperability/matrix/matrix.html

  I hope this helps you, if he did, he notes.

  -Kenny

  Cisco support community is also present in Spanish:

  https://supportforums.Cisco.com/community/Spanish/data_center

• the UCS blade iscsi initialization cannot install windows server

  Hi all

  I have a problem when I try to install windows server 2008 in the storage of nexenta using iSCSI via ucs b-series, but his works well when I install ESXi 5.5. I can't find disk under windows server installation, and I see all the LUNS in ESXi what im create before nexenta storage and work when I install it.

  This vnic iSCSI Configuration:
  ----------------------------
  vnic_id: 13
  LINK_STATE: to the top

  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 address: 192.168.1.59
  Subnet mask: 255.255.255.0
  Gateway: 192.168.1.5

  Cfg of target:
  Target the Idx: 0
  State: ISCSI_TARGET_READY
  State of PREV: ISCSI_TARGET_DISABLED
  Target error: ISCSI_TARGET_NO_ERROR
  IQN: iqn.2010 - 08.org.illumos:02:windowsboot
  IP address: 192.168.1.49
  Port: 3260
  Starting logical unit number: 6
  Ping statistics: success (986.646ms)

  Info session:
  session_id: 0
  host_number: 0
  bus_number: 0
  target_id: 0

  can anyone help me to solve this problem?

  Thanks in advance - Fabre

  ENIC / fnic driver must be installed. they are not part of any Windows operating system.

  they can be found in

  Home downloads
  Products
  Servers - unified Computing
  Series B UCS Blade Server Software
   
  Unified Computing System (UCS) Drivers - 2.2 (3)

  ISO image of drivers based on the UCS 
  UCS-bxxx - drivers. 2.2.3.iso

  Depending on the version of the UCS.

• Cisco UCS blades ¦ smbiosDump command returns "undefined, but can be defined.

  Hello community.

  I installed ESXi on a series B UCS blade but were unable to enumerate the UUID (set via Service profile) with the... smbiosDump, more than command.

  All other fields back properly for the serial number, etc... but no UUID. UUID returns: "undefined, but can be defined.    Is this a problem of ESXi and UCS?

  (NOTE, with ESX classic, dmidecoe ¦ more command lists the UUID perfectly.)

  Thoughts, comments, suggestions, input welcome.

  Best of all,

  Jason

  of cpaggen: esxcfg-info | grep UUID

• Hi ALL, did any attempt on the virtual computer NETWORK load balancing using HYPERV on UCS blades

  I try to configure the CASE server cluster by using the Unicast NLB on the virtual machine on different blades on the UCS, it works for awhile, then he abandoned packages.

  I heard that this screenplay of unicast is not supported in the UCS when she used END-host mode in the fabric interconnet...? any attempted before.

  Would it, I use the multicast mode is that something needs to be done on the FBI62020 or the LAN switch upstream. ??

  Header note I found on the implementation of UCS for mulitcast NLBL:

  Microsoft NLB can be deployed in 3 modes:

  Unicast

  Multicast

  IGMP multicast

  For series B UCS deployments, we have seen that the multicast and IGMP multicast work.

  IGMP multicast mode seems to be the more reliable deployment mode.

  To do this, the monitoring settings:

  All NLB Microsoft value "Multicast IGMP" nodes.  Important!  Check ths by logging into EACH node independently.  Do not rely on the MMC of NLB snap.

  An IGMP applicant must be present on the VLAN of NLB.  If PIM is enabled on the VIRTUAL LAN that is your interrogator.  UCS cannot function as applicant IGMP.  If an interrogator of functioning is not present, NLB IGMP mode will not work.

  You must have a static ARP entry on cheating it upstream pointing IP address Unicast NLB on the multicast MAC address NETWORK load balancing.  This need will set up, of course, on the VLAN of the NLB VIP. The key is that the routing for the NLB VLAN interface must use this ARP entry as a unicast IP ARP response may not contain a multicast mac address. (Violation of the RFC 1812)  Hosts on the NLB VLAN must also use the static entry.  You may have several entries ARP.  IOS can use a function of 'alias' of ARP. (Google it.)

  How Microsoft NLB works. -The truncated for brevity Mac addresses.

  TOPOLOGY OF NLB MS

  NETWORK VLAN 10 = subnet 10.1.1.0/24 IP load balancing

  VIP = 10.1.1.10 NETWORK LOAD BALANCING

  Arp entry static switch advanced IP 10.1.1.10 upstream to MAC 01

  NLB VIP (MAC 01, IP 10.1.1.10)

  NODE-A (AA, MAC IP:10.1.1.88)

  NŒUD-B (MAC BB, IP:10.1.1.99)

  Using the IGMP snooping and interrogator VLAN snooping table is filled with the mac NLB address and groups pointing to the appropriate L2 ports.

  MS NLB nodes will send the responses of IGMP queries.

  This snooping table could take 30 to 60 seconds to complete.

  Host on VLAN 200 (10.200.1.35) sends traffic to NETWORK VIP (10.1.1.10) load balancing

  It goes of course to VLAN 10 interface that uses the static ARP entry to resolve to address MAC 01 VIP NETWORK load balancing.

  Since it is a multicast frame destination it will be forward by the IGMP snooping table.

  The framework will arrive at ALL NLB nodes. (NŒUD-A & NŒUD-B)

  NLB nodes will use its load balancing algorithm to determine which node will manage the TCP session.

  Only one NLB node will respond to this host with TCP ACK to start the session.

  NOTES

  This works in a VMware with N1k, standard vSwtich and vDS environment. Where surveillance IGMP is not enabled, the framing for VIP MAC NETWORK load balancing will be flooded.

  NLB can only work with TCP-based services.

  As stated previously mapping an IP unicast to a multicast mac address is a violation implied by RFC 1812.

  TROUBLESHOOTING

  Make sure your interrogator is working. Just to clarify that this does not mean that it is actually at work.

  Wireshark lets check that IGMP queries are received by the NLB nodes.

  Make sure that the ARP response works as expected.  Once Wireshark again is your friend.

  Look at the paintings IGMP snooping. Validate the L2 ports appearing as expected.

  CSCtx27555 [Bug-preview for CSCtx27555] Unknown multicast with destination outside the range MAC 01:xx: are deleted. (6200 FI fixed in 2.0.2m)

  IGMP mode not affected.

  CSCtx27555    Unknown multicast with destination outside the range MAC 01:xx: are deleted.

  http://Tools.Cisco.com/support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtx27555

  fixed in 2.0(2m)

  Solution: Change the NLB mode of operation of "Multicast" to "multicast IGMP', which modifies balancing load NETWORK VIP MAC at 0100.5exx.xxx Beach, allows to transfer occur as expected.

  Q: and if I switch to switch mode, which means all of the profile and the settings on the servers are completely exhausted and I need to recreate them. ???

  A:Cisco Unified Computing System Ethernet switching Modes

  http://www.Cisco.com/en/us/solutions/collateral/ns340/ns517/ns224/ns944/whitepaper_c11-701962.html

  -There is no impact on the configuration, you have done service profiles.  they will continue to work as expected.  Mode selector has the FI behave more like a conventional switch.  Most notable is that Spanning tree will be activated and if you have several uplinks yew, tree covering weight will begin to block redundant paths.

  You need to review your topology and what impact tree covering weight.  Generally, we at the switch port upstream defined as "edge master", you want to delete this line.

  For pre-production and laboratory environment, PDI can help qualified with the planning, design and implementation partners.  Given to review the IDP site and open a case if you need more detailed assistance.

• About discovery M1 B200 UCS blade - Bug found with 1.4(2b)

  Hello

  I m test some hardware UCS composed to interconnect two 6120xp and two chassis, each chassis have two blades One is B250 M1 in Slot 1 and 2 and the other are B200 M1 in Slot 3

  I was at one point running the B200 M1 blade in each chassis without any problem until the time came to test XenServer. After that I was done with the test I driving the service profile I believe before you turn off the blade.

  From there curiously service profile was unrelated, but I couldn't turn off the two B200 M1 blade, so I tried to reset the and I even had to reinstall the two blades. Once those two servers were never available, always on and cannot be turned off with the following status, when occurs a discovery

  Overall State would be ' discovery-a failed ' and the current task status details shows:

  "Configuration of the main fabric interconnection access to Server 2/3 (WSF-STADIUM: sam:dme:ComputeBladeDiscover:ConfigFeLocal).

  The WSF, I get the following:

  Result of remote Invocation: end-point-not available

  Remote Invocation error code: 1002

  Remote Invocation Description: port remote eth (2/1/2) is not created

  Any help is appreciated. I spend a lot of time trying to find something on the Cisco technical support site or forums without success.

  Thank you

  Maher

  I just open a TAC case on the same issue.  It is caused by a bug fixed in 1.43i - background process cause more queue MTS block. (CSCtq03411).

  Temporary workaround until you can update is to ssh in the interconnection and connect to the local-mgmt and deliver orders pmon stop and then start pmon.  This will cause an interruption of service.  No configuration change is possible until this is done.

• increase the UCS blade server port

  Hello world

  I have a client with the following UCS environment:

  2 FI 6120

  2 chassis 5108

  6 B200M2

  Each chassis 5108 have 2 Fex 2104 and each 2104 a 2 10 G (cable Twinaxial) a link to each fabric Inteconnect 6120.

  If we increase the number of Serverport for each chassis 5108 from 4 to 8 (each fex will be 4 uplink), could we destroy the traffic to the blade?

  Is there a better procedure for this activity?

  Concerning

  Dino

  Hi Dino,

  I'm not sure what you mean exactly by destory traffic towards the blades? Are you talking about any loss (eth and fc) connectivity for the blades for this upgrade activity? If so yes there will be. You can connect the cables between the FI and the IOM and the same brand, that ports are srever ports having no impact, but you can use the new links you will need to re - emphasize the chassis which is a disruptive process and trigger a restart of the blades.

  As for the procedure:

  (1) connect the ports between IOM and YEW,

  (2) mark ports on the FI as ports on the server,

  (3) re - ack frame that has these new ports configured (as mentioned, make sure that the blades on the frame are closed before you re - ack)

  I hope this helps!

  . / Afonso

• Cisco UCS blade failover less computer state

  Hello

  One of my clients is looking for failover of the blade so that the profile service & OS will be moved on the seeamlessly of the blade without any manual intervention.

  I tried my best & created the pool of four blades & service profile for the same thing. Out of four blades of service profile is assigned to the three blades. Rest one's spare... Seems good

  Now the test started... According to my knowledge, I showed the failover.

  I put the server out of service in the UCS Manager & service profile started to move to the other blade... It seems good.

  But the customer is not happy with this scenario...

  Customer deleted one of the blade of the pool & now the service profile has not moved to another blade to spare in the pool.

  Is this possible? I never heard of this... upward on the events of cisco or docs... etc.

  Please advise... Looking forward to hear as soon as POSSIBLE.

  Kind regards

  Gopi G

  + 91-9818122788

  Hello

  If you move a SP of one blade to the other that the following must be taken into account

  -is within a domain UCS or cross domain UCS (compare for example global pools, overall SP as part of the UCS central)

  -Material blade in line a (number of adapters I/O, family of processor (VMware EVC!), structure of PCI bus); no problem, if the blade of the target has for example more memory...

  -FC zoning is no problem, will be automatically moved

  In summary, moving to an SP works within a domain of UCS, as well as in any field of the UCS, so carefully planned and executed.

• NO DRIVERS FOR UCS BLADE B200 M4 (missing ethernet controller) with W2012R2.

  We have installed windows 2012 R2 x 64 picture in a B200 M4 (2.2.7b) blade. We have installed all the drivers of Cisco web page, but that one THAT CISCO VIC ETHERNET INTERFACE (20gbps) pilot was found. The other Ethernet controller was not found in the .iso image file (UCS-bxxx-pilots - windows.2.2.7.iso).

  Can someone help us with these drivers?

  The id of the part is UCSB-MLOM - 40G - 03

  capture.jpg

  

  Thank you

  All ethernet interfaces, which represent the vNIC you created in your service profile, will use a single driver.  Make sure that you have installed the chipset drivers intel \ucs-bxxx-drivers-windows.2.2.7.iso\ChipSet\Intel\B200M4\W2K12R2\ and then confirm you need to install the driver of vic.  When the driver chipset and vic are installed, your ethernet interfaces must map all just as network several adapters of VIC.

  Additionally, make sure that you have not created vNIC dynamic (which may appear as follows in the Device Manager) in your service profile, unless you create for your VM - Fex NIC hyperV environment.  For VM-Fex/dynamic vNIC, there is a specific process to create these, so the Windows hyperV host does not see in Device Manager and is only visible in hyperV guestVMs.

  Thank you

  Kirk...

• ESXi 5.1 and UCS blades

  Hello

  I heard that there is a performance extremely questions degradedation with Vpshere5.1 currently running on the blades of the UCS, I wonder if anyone has confirm this or has any documented information on this. I am running vsphere5.0 and I really want to go to 5.1 but if there is really any questions I've heard that it can be in my best interest not to upgrade.

  Thank you!!!

  I have not heard this either.

• Uplinks ESX on a blade of UCS

  After installing ESX on UCS Blade (adapter type is Palo, the number of network cards is 2) sometimes I see that the uplinks are vmnic2 and vmnic3 (output of esxcfg-NICS - l)

  Where are the output of esxcfg-vswitch - l shows the uplink as vmnic0, and it also generates a warning saying there is no such thing as vmnic0.

  This happens not all the time. Anyone know why this might be happening?

  I saw this happen a little when you do not have NICs as the first devices in the vNIC/vHBA Placement. By default, we put the HBAs first sometimes ESX doesn't like it and will the NPI as vmnic2 and 3. If you move the network above the HBA cards, they come as a vmnic0 and vmnic1. I have always to reorganize and put my NIC before my storage.

  Louis

• How to set up zones and zone sets to UCS

  Hello

  Engineer of a reseller create two types of areas, zoning based on pWWN and zoning based on the interface.

  Based on the interface areas have been added to a zone set.

  The basic pWWN areas should be added to the whole of the area?

  Example:

  Storage system, 1 set

  Storage controller a 0 pWWN channel is 21:00:00:d0:23:09:5 c: 6 c, connect to the a 5 port switch

  Storage controller A channel 1 pWWN is 22:00:00:d0:23:09:5 c: 6 c, connect to the port of switch B 5

  Storage controller B 0 pWWN channel is 21:00:00:d0:23:19:5 c: 6 c, connect to the a 6 port switch

  The B channel 1 pWWN storage controller is 22:00:00:d0:23:19:5 c: 6 c, connect to the port of switch B 6

  9148 MDS, 2 games

  UCS 6140XP, 2 games

  UCS 5108, 6 games

  UCS B250 M2, 45 sets

  the area on the switch A configuration:

  Name vsan 801 hz_1_5_6 box
  Member of the interface fc1/1 swwn 20:00:00:05:73:bb:7 b: 10
  Member of the interface fc1/5 swwn 20:00:00:05:73:bb:7 b: 10
  Member of the interface fc1/6 swwn 20:00:00:05:73:bb:7 b: 10

  Name vsan 801 hz_2_5_6 box
  Member of the interface fc1/2 swwn 20:00:00:05:73:bb:7 b: 10
  Member of the interface fc1/5 swwn 20:00:00:05:73:bb:7 b: 10
  Member of the interface fc1/6 swwn 20:00:00:05:73:bb:7 b: 10

  area name PS01-HBA0 vsan 801
  Member pwwn 20:00:00:21:01: ff: 00:bf
  Member pwwn 21:00:00:d0:23:09:5 c: 6 c
  Member pwwn 21:00:00:d0:23:19:5 c: 6 c

  area name PS02-HBA0 vsan 801
  Member pwwn 20:00:00:21:01: ff: 00:af
  Member pwwn 21:00:00:d0:23:09:5 c: 6 c
  Member pwwn 21:00:00:d0:23:19:5 c: 6 c

  area name PS03-HBA0 vsan 801
  Member pwwn 20:00:00:21:01: ff: 00:8f
  Member pwwn 21:00:00:d0:23:09:5 c: 6 c
  Member pwwn 21:00:00:d0:23:19:5 c: 6 c

  area name PS04-HBA0 vsan 801
  Member pwwn 20:00:00:21:01: ff: 00:9f
  Member pwwn 21:00:00:d0:23:09:5 c: 6 c
  Member pwwn 21:00:00:d0:23:19:5 c: 6 c

  area name PS05-HBA0 vsan 801
  Member pwwn 20:00:00:21:01: ff: 00:6f
  Member pwwn 21:00:00:d0:23:09:5 c: 6 c
  Member pwwn 21:00:00:d0:23:19:5 c: 6 c

  area name PS06-HBA0 vsan 801
  Member pwwn 20:00:00:21:01: ff: 00:7f
  Member pwwn 21:00:00:d0:23:09:5 c: 6 c
  Member pwwn 21:00:00:d0:23:19:5 c: 6 c

  area name PS07-HBA0 vsan 801
  Member pwwn 20:00:00:21:01: ff: 00:4f
  Member pwwn 21:00:00:d0:23:09:5 c: 6 c
  Member pwwn 21:00:00:d0:23:19:5 c: 6 c

  area name PS08-HBA0 vsan 801
  Member pwwn 20:00:00:21:01: ff: 00:5f
  Member pwwn 21:00:00:d0:23:09:5 c: 6 c
  Member pwwn 21:00:00:d0:23:19:5 c: 6 c

  area name PS09-HBA0 vsan 801
  Member pwwn 20:00:00:21:01: ff: 00:2f
  Member pwwn 21:00:00:d0:23:09:5 c: 6 c
  Member pwwn 21:00:00:d0:23:19:5 c: 6 c

  area name PS10-HBA0 vsan 801
  Member pwwn 20:00:00:21:01: ff: 00:3f
  Member pwwn 21:00:00:d0:23:09:5 c: 6 c
  Member pwwn 21:00:00:d0:23:19:5 c: 6 c

  name zoneset801 801 vsan zone set
  Member hz_1_5_6
  Member hz_2_5_6

  configuration of the switch box B:

  Name vsan 802 hz_1_5_6 box
  Member of the interface fc1/1 swwn 20:00:00:05:73:b7:8e:d8
  Member of the interface fc1/5 swwn 20:00:00:05:73:b7:8e:d8
  Member of the interface fc1/6 swwn 20:00:00:05:73:b7:8e:d8

  Name vsan 802 hz_2_5_6 box
  Member of the interface fc1/2 swwn 20:00:00:05:73:b7:8e:d8
  Member of the interface fc1/5 swwn 20:00:00:05:73:b7:8e:d8
  Member of the interface fc1/6 swwn 20:00:00:05:73:b7:8e:d8

  area name PS01-HBA1 vsan 802
  Member pwwn 20:00:00:21:01: ff: 01:8f
  Member pwwn 22:00:00:d0:23:09:5 c: 6 c
  Member pwwn 22:00:00:d0:23:19:5 c: 6 c

  area name PS02-HBA1 vsan 802
  Member pwwn 20:00:00:21:01: ff: 01:9f
  Member pwwn 22:00:00:d0:23:09:5 c: 6 c
  Member pwwn 22:00:00:d0:23:19:5 c: 6 c

  area name PS03-HBA1 vsan 802
  Member pwwn 20:00:00:21:01: ff: 01:6f
  Member pwwn 22:00:00:d0:23:09:5 c: 6 c
  Member pwwn 22:00:00:d0:23:19:5 c: 6 c

  area name PS04-HBA1 vsan 802
  Member pwwn 20:00:00:21:01: ff: 01:7f
  Member pwwn 22:00:00:d0:23:09:5 c: 6 c
  Member pwwn 22:00:00:d0:23:19:5 c: 6 c

  area name PS05-HBA1 vsan 802
  Member pwwn 20:00:00:21:01: ff: 01:4f
  Member pwwn 22:00:00:d0:23:09:5 c: 6 c
  Member pwwn 22:00:00:d0:23:19:5 c: 6 c

  area name PS06-HBA1 vsan 802
  Member pwwn 20:00:00:21:01: ff: 01:5f
  Member pwwn 22:00:00:d0:23:09:5 c: 6 c
  Member pwwn 22:00:00:d0:23:19:5 c: 6 c

  area name PS07-HBA1 vsan 802
  Member pwwn 20:00:00:21:01: ff: 01:2f
  Member pwwn 22:00:00:d0:23:09:5 c: 6 c
  Member pwwn 22:00:00:d0:23:19:5 c: 6 c

  area name PS08-HBA1 vsan 802
  Member pwwn 20:00:00:21:01: ff: 01:3f
  Member pwwn 22:00:00:d0:23:09:5 c: 6 c
  Member pwwn 22:00:00:d0:23:19:5 c: 6 c

  area name PS09-HBA1 vsan 802
  Member pwwn 20:00:00:21:01: ff: 01:0f
  Member pwwn 22:00:00:d0:23:09:5 c: 6 c
  Member pwwn 22:00:00:d0:23:19:5 c: 6 c

  area name PS10-HBA1 vsan 802
  Member pwwn 20:00:00:21:01: ff: 01:1f
  Member pwwn 22:00:00:d0:23:09:5 c: 6 c
  Member pwwn 22:00:00:d0:23:19:5 c: 6 c

  name zoneset802 802 vsan zone set
  Member hz_1_5_6
  Member hz_2_5_6

  All areas not added to all areas are actually not used, depending on whether the areas that aren't yet in all of areas are required, yes you will have to add them in.

  However, the WWPN you have listed do not seem to use the Cisco format recommended for pools WWPN (20:00:00:25:B5:xx:yy:zz) and maybe you are not pools or areas are not associated with UCS? If they are indeed UCS related areas then yes add to all areas, but plan instead to use the pools if this is the case.

  My suggestion would be to use all fields WWPN and not mix with the interface areas.

  On each MDS switch, create a zone that contains only the two WWPN in the storage controllers, ideally using an easy to identify the alias. This ensures that the ports of SAN can still see each other. Then, create an additional area for each UCS blade that contains the WWPN of the Pool WWPN blade, as well as the above mentioned storage area. This allows the vHBA to see the ports of SAN.

  Here is a reference document, that you may find useful.

  http://www.Cisco.com/en/us/docs/storage/san_switches/MDS9000/SW/San-OS/quick/guide/qcg_zones.html

• UCS KVM

  Hello

  I create firewall rules for the connection of console KVM UCS. The firewall is deployed between the end user and UCS mgmt 0.

  but I'm not sure that the destination for firewall rules. (source (end-user)-> destination tcp 2068)

  destination: ucs mgmt IPs + cluster ip or UCS blades ext-mgmt ip pool of managers?

  Please help confirm.

  Thank you very much!

  Destination IP is mgmt IP pool Beach indeed.

• Nexus 1000v, UCS, and Microsoft NETWORK load balancing

  Hi all

  I have a client that implements a new Exchange 2010 environment. They have an obligation to configure load balancing for Client Access servers. The environment consists of VMware vShpere running on top of Cisco UCS blades with the Nexus 1000v dvSwitch.

  Everything I've read so far indicates that I must do the following:

  1 configure MS in Multicast mode load balancing (by selecting the IGMP protocol option).

  2. create a static ARP entry for the address of virtual cluster on the router for the subnet of the server.

  3. (maybe) configure a static MAC table entry on the router for the subnet of the server.

  3. (maybe) to disable the IGMP snooping on the VLAN appropriate in the Nexus 1000v.

  My questions are:

  1. any person running successfully a similar configuration?

  2 are there missing steps in the list above, or I shouldn't do?

  3. If I am disabling the snooping IGMP on the Nexus 1000v should I also disable it on the fabric of UCS interconnections and router?

  Thanks a lot for your time,.

  Aaron

  Aaron,

  The steps above you are correct, you need steps 1-4 to operate correctly.  Normally people will create a VLAN separate to their interfaces NLB/subnet, to prevent floods mcast uncessisary frameworks within the network.

  To answer your questions

  (1) I saw multiple clients run this configuration

  (2) the steps you are correct

  (3) you can't toggle the on UCS IGMP snooping.  It is enabled by default and not a configurable option.  There is no need to change anything within the UCS regarding MS NLB with the above procedure.  FYI - the ability to disable/enable the snooping IGMP on UCS is scheduled for a next version 2.1.

  
  
  This is the correct method untill the time we have the option of configuring static multicast mac entries on
  
  the Nexus 1000v.  If this is a feature you'd like, please open a TAC case and request for bug CSCtb93725 to be linked to your SR.
  
  This will give more "push" to our develpment team to prioritize this request.
  Hopefully some other customers can share their experience.
  Regards,

  Robert