UCS (PALO) VIC - associate a host

Similar Questions

• Impossible to connect from my VIC to the host using the host name.

  Hi guys,.

  When I try to log in from my VIC to the host, I get this message (see photo) but if I use the work just the IP address. I check my DNS and host VMware was not there so I created a PTR record that connects the IP with hostname, I update the DNS, but still nothing happens. Any idea?

  Thank you.

  I was almost positive it is a dns issue...

  You can test the host name of the workstation that you are trying to connect from? try clearing your cache dns on the local workstation-

  > ipconfig/flushdns

  If for some reason that doenst work, and then add the host name of the node to your hosts file

  -

• Drivers Windows 2003 Palo (VIC)

  Anyone know if there is a driver Windows 2003 VIC? I background on Windows 2008 x 64 one on the UCS downloads page.

  Jeremy

  Windows 2003 is not an operating system that is supported for the VIC card and that's why drivers are not available.

  The support of the OS is made to http://www.cisco.com/en/US/prod/collateral/ps10265/ps10280/data_sheet_c78-525049.html

  -Matt

• How to associate a host file extension with a request for comments in Unity mode on a Windows host?

  Hi all

  I have a computer with VMware Player 3.1.1 Windows host computer. The unit mode works very well with Windows and Linux VMs.

  I would like to associate a file extension in my host for an application in a guest such as when I try to open these files, it starts the application in the comments. Merge, is that on a MAC, I read that it was possible with a Linux host, but I can't find anything on a Windows host.

  Is it possible to do this?

  Thank you for all.

  Concerning

  Franck

  This is one officially supported by characteristic on the merger only. It certainly doesn't work on Windows hosts. While you can run an application in the comments, you can't run an application and give him additional command line parameters.

• Generational UCS/VMWare

  Hello

  I'm looking for clarification on how the Palo VIC presents the vNIC, how say/control which card vNIC to which ports physical and how best to configure my environment for VMWare.

  Summary of material:

  Blades (full-width) B250 with 2 cards of Palo VIC

  5108 chassis with double FEX (double uplinks from each FEX)

  2 x 6120 controllers with 2 x 10 Gbit links rising each to a pair of Nexus s 5020

  Summary of the software:

  UCS 1.3.0 boot loader, the kernel/system 4.1 version (3) N2(1.2d)

  VMWare vSphere Enterprise Plus 4.1

  According to my interpretation, Cisco and VMWare recommend against bandwidth limiting the interfaces - but prefer to go with actions and ability to burst.

  Therefore, my desired construction is the following:

  for each of the 4 available in B250 blade 10gbit interfaces, I want to have 2 vNIC (1 for VM distributed vSwitch [6Gbit minimum actions, 802. 1 q trunks], 1 for iSCSI [4 Gbit minimum actions, access port/no 802. 1 q trunk]). This means that my Service profile must define 8 vNIC altogether.

  Q1: How can I make sure that I get 1 'data' and 1 'iscsi' vNIC per physical port?

  Q2: how to set a policy to set the minimum bandwidth on each vNIC?

  Q3: How do I control/make sure the binding order correct so that I can script my configuration of vSphere?

  Generation of VMWare will be vswitch distributed containing all the 'data' vNIC, allowing control of network IO with actions defined to manage the various allowances for groups of data ports, console and VMotion. The vNIC iSCSI will each receive a VMKernel port dedicated.

  Thank you very much in advance for any help.

  Our installation program is not the same, but the principles can be applied as we also CIV.  To make sure that we had the installation of ports properly, I put into service six vNIC in UCSM to each host.  I put in service the first vNIC of fabric and the second vNIC fabric B - do not check the box "Fabric Failover"...  Repeat for other network cards for four.  This will give you 4 vNIC by fabric.  Note MAC addresses and which tissue they are attached.

  Then, in case of VC and to configure your hosts, enter the network cards and line up the vmnic and MAC addresses so that you know how they trace.  When you configure your vSwitches, just make sure you add a vmnic from fabric and a fabric vmnic B.    Do this for the Service Console, vmkernel and VM switches.

  If you make this unique environment of VIC inas, it will ensure that your vswitches are attached to every tissue.  I guess you can do this same thing with two VICs, since each card may appear independently in UCSM.

  As for the bandwidth mgmt and others, check out http://bradhedlund.com/ its recent messages are on the networks of the UCS.

  Adam

• Options to upgrade to a blade in a UCS

  My UCS system is running 2.2 (3 c), one near my blade, which 2.2(1b) running.

  I need to get that a blade is upgraded to 2.2 (3 c). Everything is already there.

  After reading the instructions on the following page:
  http://www.cisco.com/c/en/us/support/docs/servers-unified-computing/ucs-b200-m1-blade-server/110260-ucs-upgrade-bios-00.html, it seems that 'the way' update the firmware of the just a blade is to:

  1. Create a strategy to host the firmware specifying the correct component firmware,
  2. Associate the host firmware this policy to:
     1. A Service profile that is already associated with the blade (which will cause a reboot) OR
     2. A profile Service that I then associated with the blade when I want it to apply & reboot.

  Just so I understand my options, it is the only way to update the firmware on a blade, or is there a more direct way that does not involve policies and profiles of boards?

  Now that I look at really into it, creating a policy package host Firmware and applying it to the service of the server profile may be easier that separately, updating firmware of the adapter, BIOS, Board and controller of CIMC firmware. But I would still like to know my options.

  Thank you

  You can do it manually, but it will ask you to do in the specific order that is necessary to complete it successfully, if you don't do it in a specific order, you can end up causing internal dependencies to be messed up p, which is why we recommend the HFP... a step and the system supports the internal dependencies...

  I don't see an option easier than HFP.

  To do it manually, go to server > install firmware and update the firmware and then activate it.

  HTH,

  -Kenny

• Host network IO performance

  Hello

  I am Setup VN-Link in HW to UCS and wondered what the HOST IO NETWORK PERFORMANCE in Port profile properties mean. The options are 'None' and 'High Performance'. I found no information on such a feature. I know that VN-Link in HW improves the performance of network of networks of VM, but I thought that needed no specific configuration, simply to allow VN-Link in HW...

  Basically, I would like to know the difference in Exchange for this option to ZERO or to HIGH PERFORMANCE.

  Thank you very much

  Hello

  Currently, the box does nothing but when ESX supports VMdirecpath with VMotion in their next release, this option will be valid.

  In the VM - FEX (VN-link hw) * today * the virtual adapter held a virtual machine through the MEC to access data and VMotion etc is available.

  When ESX supports this checkbox is set, the virtual card will go to the vNIC directly without going through the MEC and Vmotion will be supported.

  It will be useful.

  -Matt

• 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.

• UCS < 1.4.2b >, N1K and uplink

  Hi all

  I have a UCS (cluster) connected in vPC mode to a Nexus 7010.

  UCS 4.1U1 VMware ESXi, N1K with EHM PC blade-based UCS NIC is 71KR.

  Question is what happens if the two uplink of interconnection fails? I mean maybe cut fibres or stuff like that. N1K channel will be still two active link?

  Maybe the redundancy is performed by re arping for finding a mac (i've got UCS in switch mode) address, but I'm not sure. I saw a feature in the new version for a link status tracking rising full failure handling system (how?).

  last question about redundancy... what happens if a UCS IOM resets? I have some traffic disruption?

  TNX

  Dan

  Dan,

  Just to be clear, check the following:

  -UCS in switch mode

  -Adapters M71KR

  -N1k using Mac-pinning (I guess)

  -Connectivity upstream of each FI is a VPC to a pair of N7Ks.

  In this case, the N1K has no visibility of uplinks UCS.  See all your hosts VEM are two uplinks for each host (a session each fabric interconnect.)  If one of the two uplinks fails on interconnection, traffic will be the uplink remaining on this FI re-hairpin.  If the TWO uplinks on a financial institution fail, then UCS will be down (called the link at the bottom) server links and traffic should be routed through the MEC is another uplink will the other.  You can change this behavior to follow links to Server (for local switching only) but the default action of UCSM's close links to corresponding server if there are no links available on a financial institution.   Make sense?

  Now, in the last version of N1K here (1.4) is a new feature called followed by the State of the network (NST) for use with VPC - HM (such as Mac pinning).  This feature will allow to test the connectivity of a VLAN sends a probe packet and expect to get fired on another group of liaison rising/sup.   If you have a network VLAN which SHOULD be identified, you can follow with TSN.  If the network becomes unavailable, you can choose to close the uplink and re - route traffic to an another uplink.  This is useful to detect failures beyond the first jump (which would be the interconnections) as a failure somewhere in your N7K level or beyond.

  Setup Guide: http://www.cisco.com/en/US/partner/docs/switches/datacenter/nexus1000/sw/4_2_1_s_v_1_4/interface/configuration/guide/n1000v_if_5portchannel.html#wp1284321

  White paper: https://communities.Cisco.com/docs/doc-20657

  Order code: http://www.cisco.com/en/US/docs/switches/datacenter/nexus1000/sw/4_2_1_s_v_1_4/command/reference/n1000v_cmds_t.html#wp1295608

  For your last question about a failure/reset of the IOM, the cards corresponding to each blade will lose connectivity.  This is redundancy at the host level comes into play to reroute traffic.  In the case of your hosts N1K VEM, they would simply be re - route traffic on the access road to functional IOM of the chassis.

  Another point to consider is the M71 and M81 adapters support Fabric Failover.  He is tilting at the adapter level if there is a failure with any device between the adapter and uplink (like the IOM or FI).  Fabric failover is a configurable option adapter which re - will route traffic in Menlo ASIC adapters to the fabric in the 'other', such that the host will NOT see one of the two ports down.  Without switch fabric, a failure of a MOI or FI consider the adapter and this port would descend.  FF only adds a level of redundancy in the adapter without having to rely on any OS host grouping/failover.  M51KR, M61 KR and M72KR adapters do NOT support this feature.

  Kind regards

  Robert

• Associated error - "Server features are not compatible with UCS below.

  Hi all

  I am tempted to associate a SPG which the UCS field but get the following error. Under the general tab:

  There are not enough global resources.
  field of the UCS has no server corresponding to this service profile features.

  And under the status tab:

  Descriptor of the stage: analysis of changes impact(FSM-STAGE:sam:dme:LsServerConfigure:AnalyzeImpact)

  Tent: 0

  Previous state: ConfigureFail

  Remote control Err Code: 5

  Distance Err Description: Server features are not compatible with UCS below.

  Distance Inv result: resources-out of stock

  The field of the UCS that I associate this GSP which is an existing domain, I have just signed up with Central UCS. I created and associated with a GSP scheme a UCS of greenfield in another area data center.

  The two areas are running UCSM 2.2 (6 d). Central UCS is 1.4(1a).

  I found a bug that suggests this may be due to the presence of a policy to Boot, but the workaround solution (remove the startup policy) does not work in this case.

  So, anyone know what might be going on here?

  Thank you

  Richard

  Richard,

  Please check the following bug: CSCuy07572

  You can use the global default and should work completely correctly.

  You can choose the version that is required here.

  Non-policy default will be a problem.

  Thank you

  Yoga

• 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.

• Without change to the FC switch to mode mode end-host FC

  In the window of maintenance last night, I was going to spend one of my systems UCS switch FC FC end-host Mode. The intention was to be able to reach the storage systems via an external FC SAN, instead of the current situation where storage is directly attached to the FIs. The UCS system in question is redundant fabric 6248UP of interconnections, blades are all of the B200M2 or the B200M3, and infrastructure (UCSM, FIs and IOM) running version 2.2(3a).

  The plan was relatively simple. First of all, I would like to change FI B mode end-host FC. Once this has been done re - I would record vHBAs the blades attached to the fabric B in my storage system, so that they could access their storage via the external SAN. Then I go through all the blade servers and ensure that they had access to storage multipath healthy and tolerant, how I would like to repeat the process for FI.

  It turned out to be a disaster, however. Once I started the process of change FI B FC end-Host mode, FIs times restarted, and all servers access storage and network. When they came again, both of them had changed the fashionable end-host FC, which means that none of the blades had access to their storage volumes more. So there is nothing to do but to return the change. Yet once, two FIs restarted at the same time and they both returned to the top in switching mode of CF. A few hours later, after have rebooted most of blade servers and cleaning applications having failed, we were in normal production.

  So what I was asking here why on Earth the two of my FIs restarted at the same time. Is this a known bug? The user interface would certainly think one can ignore at a time as I had planned, because the CF implemented end-Host Mode action link is on the page of each individual FI in UCSM (under hardware-> connections-> interconnection fabric A fabric / B). (So the action Set FC Switching Mode of link, incidentally.) Also, when I click on this link, I get a warning saying local ' are you sure you want to set the mode of end-host FC? If you select Yes , the fabric of interconnection will restart and this application will disconnect'. Note the use of the singular here; the warning refers to an single fabric of interconnection, which is perfectly logical that the change was requested only on one two FIs.

  Torus

  I quite understand your point!

  The wording is misleading, because it is not in order with a completed receipt one.

  That's why Kenny of the TAC wrote the answer above.

  In my opinion, the documentation must be corrected.

• Update VSAN task configuration failed for ALL 3 ESXI hosts

  I enabled VSANS on the cluster, but the task of updating VSAN configuration failed with the below error

  Operation failed, the diagnostic report: not associate the host to the cluster VSAN (Exec command "/etc/init.d/vsanvpd restart" succeeded, but came back with zero State: 1).

  On all esxi hosts 3, I can see a warning

  Host is in an active VSAN cluster but doesn't have a Service of active VSAN

  Please help me fix this isseu... I need all the VSAN here experts... I do not find a troubleshooting for this issue.

  This information was supposed to do in the VSAN Release Notes, although I must admit that I don't check that they exist.

  Here's a post I made on the memory requirements which came into force for GA

  Part 14 & #8211 VSAN. Memory of the host requirements. CormacHogan.com

• Error when you try to upgrade a previously installed to the last ESXi 4.1 VIC VIC

  Everyone knows about this problem with ESXi 4.1?

  After installing ESXi 4.1 (new installation on host - not upgraded), at the opening of the VIC on a workstation and connect to the new host ESXi 4.1, it tries to upgrade the VIC as usual, but fails, retune the error: "customer support required files cannot be retrieved from the server.  The identification process will now stop.  Details: the request failed due to a failure of the connection. »

  So I tried to install the VIC by accessing pages web host.  When you click on "Download vSphere Client", he tries to click on the following link (http://vsphereclient.vmware.com/vsphereclient/2/5/8/9/0/2/VMware-viclient-all-4.1.0-258902.exe), instead of download the VIC to the host.  When you try to download the VIC of the host, I tried the IP address and the DNS name, the two are unable to point to the correct location.

  Any thoughts?

  Thank you

  I think I've read that with ESX 4.1 you can not download the VIC of the ESX host, more - you must download from the VMware site.

  I downloaded the 4.1 VIC from VMware and installed without problem for me...

• FEX-Uplink Failover, loadbalancing

  I would like to understand more of the technology within a vblock
  I have a few questions gradually

  So I'm out. pls be patient and thank you in advance...

  VBlock 720 with the following generic configuration

  Switch 2 x Cisco 5000 Series
  2 x FI 6248
  6 x chassis 5108
  FEX 2204
  VIC 1240 (no Mezzanine Card)
  8 x M3 blade, 2 CPU

  uplinks of 4 x 10 G of each FEX to FI (port channel)
  uplink of 8 x 10 G of each FI for Ciso 5000 series swith (vpc)

  Assumptions:

  All chassis are completely fill

  Each blade has consistient thoroughput of bandwidth, but 6 GB

  1. When the blades connect to FEX A and B FEX, are active active connections?
  2. For exampleIs blades 1 and 5 has made the fallen on the same ports on the same FEX FEX?
  3. What is the method that load balances blade ping?
  4. Assume 1 Uplink fails between FEX and FI, is the uplink 1 on FEX B overexploited.
  5. How the virtual machine decides which ANC port to send traffic?

  She now...

  See online

  When the blades connect to FEX A and B FEX, are active active connections?

  I assume you mean of FEX = IOM in the chassis;

  Yes the two fabrics are active; all VIC are double hosted the fabric a and b

  For exampleIs blades 1 and 5 has made the fallen on the same ports on the same FEX FEX?

  You have the choice between static pinning (made by UCS Manager) blade slot to an Uplink of IOM, or set a port between IOM and fabric channel interconnection; port channel is the preferred mode.

  Static pinning depends on model of IOM, 2204 / 2208 and the number of uplinks, for example

  2204-4 uplinks

  slot 1 and 5--> uplink 1 chassis

  2 and 6-> uplink 2 chassis slot

  ......

  2208-8 uplinks

  Chassis slot 1-> uplink 1

  Chassis slot 2-> uplink 2

  ......

  Pinning static if a rising fails, the fabric slots correspondent has or b, are declining. There is no repinning for remaining uplinks; grouping and multipathing will take the appropriate action.

  If you have a port-channel, and you lose a link, no problem, as long as there is at least a link to the top; your bandwidth will decrease, but th vnic/vhba are still in place

  What is the method that load balances blade ping?

  Don't understand; To be more specific

  Assume 1 Uplink fails between FEX and FI, is the uplink 1 on FEX B overexploited.

  Yes, in principle. but you will have to design oversubscription from end to end in any case!

  How the virtual machine decides which ANC port to send traffic?

  It depends on the hypervisor; Take, for example, VMware ESXi and vswitch: load balancing can be configured by switch and / or port-group; important caveat: do not hash IP as interconnection of fabric does not support the Protocol LACP; by default, the original virtual¨port code.