Windows 2008 R2 on Cisco UCS B200M networking problems

This is driving me completely nuts.  Let me start by saying I am new to blade servers and Cisco UCS.  I did take an introduction class, and it seemed straight-forward enough.  I have a chassis with two B200M blades, on which I am trying to configure two Windows 2008 R2 servers, which I will eventually make Hyper-V servers.  This is all in a test environment, so I can do anything I want to on them.
Right now I have installed W2008 directly on hard disks on the B200M hardware.
The problem is this: even though I think I've configured the network hardware correctly, using the Cisco VIC driver software, I cannot get networking to work in any reliable way.  I cannot even get ping to work consistantly.  I can ping my local server address, but I cannot ping my gateway (HSRP address).  When I try, I get a "Reply from 10.100.1.x: Destination host unreachable (x being each particular server's last octet). I CAN, however, ping the individual IP addresses of the core switches.  I can also ping some, but not all, the other devices that share the servers' subnet.  There are no errors being generated, the arp tables  (for those devices I can ping) look good, netstat looks OK.  But I cannot get outside the local subnet...
Except when I can.
There are times when I can get all the way out to the Internet, and I can download patches from Microsoft.  When it works, it works as expected.  But if I reboot the server, oftentimes networking stops working.  Yet another reboot can get things going again.  This happens even though I've made no changes to either the UCS configs or the OS.
I cannot figure out any reason when it works at some times and not at others.  I've made sure I have a native VLAN set, I've tried pinning to specific ports on the Fabric Interconnects.  There is just no rhyme or reason to it.
Anyone know of where I can look?  I'm very familiar with Windows on stand-alone boxes (although it's no longer my area of expertise), and I manage a global WAN (BGP, OSPF, Nexus 7k, etc.) so I'm no dummy when it comes to networking, but I am utterly stumped on this one.        

The problem was this: while the NICs on the blade server are called vNIC0 and vNIC1, Windows was calling vNIC1 "Local Area Connection" and vNIC0 "Local Area Connection 2".  So what I configured on UCS did not match what I was configuring in Windows.  Completely, utterly ridiculous.
Anyway, networking is working now without any issues.  Thanks for you suggestion; it did get me looking in the right direction.

Similar Messages

  • Ethernet controller driver not installing after Windows Server 2008 installation on Cisco UCS blade

    I am using MDT 2010 to deploy Windows Server 2008 to a Cisco UCS B200 blade. The OS and hotfixes install with no problem. The system reboots and attempts to connect to the deployment share to continue with the task sequence and I receive an error stating
    "A connection to the deployment share could not be made. The following networking device did not have a driver installed. PCI\VEN_1137&DEV_0043&SUBSYS_00481137&REV_A2"
    The driver in question is the driver for the Ethernet controller for the UCS blade. More specifically, it is the network driver for the Palo card in the UCS Chassis. When I Ignore or Abort the install, I am able to manually install the driver and restart the
    task sequence. The build then completes successfully with no further issue. I just cannot seem to automate the driver install. Has anyone dealt with this type of issue?

    Vik and stealthfield - thank you for your responses.
    I was preparing a script to manually move the driver into the c:\windows\inf location when I had to stop to create a new task sequence for a different build. It was while building this task sequence that I found the soulution to the problem.
    In the Post Install -> Inject Drivers step of the Task Sequence, I noticed that it was executing a command of type "Inject Drivers" with a selection profile of "All Drivers" and "Install only matching drivers
    from the selection profile" selected.         
    I changed this to run a command of type "Run Command Line" and specified that it execute "%Scriptroot%\ZTIdrivers.wsf". I noticed that this was selected in one of my other builds that was working properly, so I thought I'd
    give it a try. - IT WORKED.
    So to sum up, the solution was to change the type of command being executed in the "Post Install -> Inject Drivers" step of the task sequence. After this change, the machine came up and continued the task sequence with no further issues.
    Thanks again for the responses - They were helpful and I do appreciate it.

  • Slow printing from windows 2008 R2 with Cisco 6509

    Dear All,
    I am having a wiered issue in my network. We have a windows 2008 R2 print server. Normal documents print's fine. If you print a image or pdf file, it takes a long time to print. For example a 2 MB PDF image with two page took me 10 minutes to print. The data from the server to the physical printer is really slow. To test it, i have loaded the driver on another windows 2008 R2 and the result is same slowness. We uses Xerox Colorqube 9303 printers.
    I have tried most options from microsoft which didnt help. I have installed a windows 2012 server to test if its specific to windows 2008, but the result remains same. Printing from a windows PC is perfectly fine; 32 bit PCs we have.
    I have seen someone got a solution to this by disabling ip local-proxy-arp, this is not enabled nor available in my switch.
    I have 6509 as core switch with IOS 12.2(33)SXH8. Does anybody come across such a scenario? Is there any special port configuration required for windows 2008 R2 to work normal?
    A sample interface configuration is given below
    GigabitEthernet1/10 is up, line protocol is up (connected)
      Hardware is C6k 1000Mb 802.3, address is c89c.1dd9.2619 (bia c89c.1dd9.2619)
      Description: ***Connect-to-Server-form***
      MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec,
         reliability 255/255, txload 1/255, rxload 1/255
      Encapsulation ARPA, loopback not set
      Keepalive set (10 sec)
      Full-duplex, 1000Mb/s, media type is 10/100/1000BaseT
      input flow-control is off, output flow-control is on
      Clock mode is auto
      ARP type: ARPA, ARP Timeout 04:00:00
      Last input never, output 00:00:13, output hang never
      Last clearing of "show interface" counters never
      Input queue: 0/2000/88/0 (size/max/drops/flushes); Total output drops: 0
      Queueing strategy: fifo
      Output queue: 0/40 (size/max)
      5 minute input rate 0 bits/sec, 0 packets/sec
      5 minute output rate 151000 bits/sec, 30 packets/sec
         10067885 packets input, 4366947776 bytes, 0 no buffer
         Received 36631 broadcasts (2569 multicasts)
         0 runts, 0 giants, 0 throttles
         11 input errors, 1 CRC, 0 frame, 77 overrun, 0 ignored
         0 watchdog, 0 multicast, 0 pause input
         0 input packets with dribble condition detected
         251401032 packets output, 96130506019 bytes, 0 underruns
         0 output errors, 0 collisions, 5 interface resets
         0 babbles, 0 late collision, 0 deferred
         0 lost carrier, 0 no carrier, 0 PAUSE output
         0 output buffer failures, 0 output buffers swapped out
    Any help would be really appreciated.
    Thanking you in advance.
    Prince Mathew

    Hello
    Printing from a windows PC is perfectly fine; 32 bit PCs we have.
    - Printing directly from a computer which has the locally installed driver is printing fine.- it does seem to suggest the server or the network- however locally installed print drivers work fine so the communication to the printer from the client over the network seem to be okay.
    However the centrally installed print drivers means the processing job is now  with the server which is between the printer and client
    Whats the RTT from client and server and client to printer .etc?  - perform a extended ping to validate connectivity between all 3
    Have you hardcoded the server port to the nic setting of the server - Are the speed/duplex settings manually applied to the servers  if so make sure they are also manually set on the switch ports realting to these servers - this is apllicable to the printers too.
    Is the same driver used locally is also on the printer server correct?
    Whats printing protocol ( RAW) and port being used on the printer server
    Do you have print pooling setup on the server -(typo in last post)
    Are these printer shared in A/D and deployed by GPO -are the correct permissions set on these shares
    Check the printer permission on the spool folder also - users need at least read & execute privileges
    Have you manually cleared the print spooler folder and restarted the spooler service on the server?
    Are the print jobs being render to the clients or is the server taking the load of processing the print job?
    Any printer queue priorites set?
    res
    Paul
    Please don't forget to rate any posts that have been helpful.
    Thanks.

  • Cisco UCS Director Login Problem

    Hello Community,
    I have recently installed Cisco UCS Director 5.1. According to the documentation the initial login requirements are admin for username and admin for password, see image;
    http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/ucs-director/vsphere-install-guide/5-1/b_Installing_UCSDirector_on_vSphere_5_1/b_Installing_UCSDirector_on_vSphere_5_1_chapter_010.html
    However, authentication keeps on failing.
    Any ideas?
    Cheers
    Carlton

    Sergey,
    If this is a real I2C issue, you may still see the same behavior on 2.0.x release if the I2C bus was not cleared before the upgrade. (in this moment I don't know if you recently performed an upgrade on the system or not)
    I2C bus tranports information about the different components of the Unified System, this, meaning Chassis, IOMs, Fans, PSU, etc...  What happens is that all those components try to send theit status update while other do the same and then the I2C bus gets overwhelmed, and then noone can really report their real status, so we usually recommend the customer ro reseat all major components, one at the time, to clear the bus and then do the upgrade, if that is not done before the upgrade, it still should be done after.
    Try reseating the Fans and PSU, one at the time, leaving a minute in between and then, IOMs one at the time, leaving three minutes in between and begining with the subordinate to cause minimun disruption.
    If this does not clear the situation, then you will need to remove one of the components already mentioned, one at the time and do a "show tech-support chassis # all brief" to see what the I2C bus reports segment by segment (chassis, Fans, PSUs...) once you remove a component and the errors on each segment stop incrementing you will have your faulty piece of hardware, and a TAC case will be needed to send a replacement.
    For further analysis or assistance, I strongly recommend a TAC case to be opened.
    -Kenny

  • Cisco ucs 5108 thermal problem

    si
    Hi everyone!
    I've installed my first UCS system: 2 UCS 5108 & 2 UCS 6248
    In first chassys  six blade-servers (2 - b230 m2& 4 b200 m2). In second - 5 b200 m2. I've got two air conditioners in server room working on their maximum. For the last week i've received three faults on first chassis (Fault Code: F0411). IOM temperature was about 45-46. After that i've mooved 3 blade-servers to second chassis until i solve this problem.
    UCSM version - 2.0.2r
    Everything is quite good, except thermal problem. All blade-servers discovered, 0 errors and critical.

    Sergey,
    If this is a real I2C issue, you may still see the same behavior on 2.0.x release if the I2C bus was not cleared before the upgrade. (in this moment I don't know if you recently performed an upgrade on the system or not)
    I2C bus tranports information about the different components of the Unified System, this, meaning Chassis, IOMs, Fans, PSU, etc...  What happens is that all those components try to send theit status update while other do the same and then the I2C bus gets overwhelmed, and then noone can really report their real status, so we usually recommend the customer ro reseat all major components, one at the time, to clear the bus and then do the upgrade, if that is not done before the upgrade, it still should be done after.
    Try reseating the Fans and PSU, one at the time, leaving a minute in between and then, IOMs one at the time, leaving three minutes in between and begining with the subordinate to cause minimun disruption.
    If this does not clear the situation, then you will need to remove one of the components already mentioned, one at the time and do a "show tech-support chassis # all brief" to see what the I2C bus reports segment by segment (chassis, Fans, PSUs...) once you remove a component and the errors on each segment stop incrementing you will have your faulty piece of hardware, and a TAC case will be needed to send a replacement.
    For further analysis or assistance, I strongly recommend a TAC case to be opened.
    -Kenny

  • Oracle Express and Windows 2008 Server

    I successfully installed the Oracle Database 10g Express Edition on our new Windows 2008 Server. However, after install I can not open the Database Home Page in IE 7.0? The problem description I get when I click on the Diagnose Connection is "127.0.0.1" is not set up to establish a connection on port "8080" on this computer.
    The server is also a domain controller, DNS server and DHCP server.
    Is this version compatible with Windows 2008 Server?
    Is it a DNS problem or may be a security problem?
    Heinrich

    I have not tried it on Windows 2008. But the challenges with your configuration could be endless. Here are some common issues:
    1) XE must be installed by a local machine administrator, not a domain administrator
    2) XE requires several ports (1521, 8080)
    3) Firewalls and antivirus are known to crash the install
    4) Often 3) will block the installation of the database
    Note that XE does not use any form of HTTP listener - the database listener does the bassic work and passes HTTP requests into the database. So no Apache or IIS requires with XE.

  • Unable to load driver for Storage for Windows 2008 UCS B230 M2

    I am trying to Boot from SAN windows 2008 R2. I  have configured and connected the Cisco UCS Chassis and FI to our Network & Storage .I am  having problem to install Windows 2008 R2 Server on Blades as it is not able to see Storage LUN while installation .I downloaded drivers from Cisco Support Site.
    I tried drivers from ISO ucs-bxxx-drivers.2.1.3 latest version but Windows is showing driver is available but not installing the driver I am getting the following error and not showing the LUN hard disk to select the installation.
    Windows is unabe to locate storage LUN. I am able to LUN while booting process.
    I am not sure where I am doing wrong.or I am chosing wrong driver.

    I don't see the error message either, but to install W2008 on a boot lun, you must
    1) do the zoning of the vhba (initiator) to the pwwn of the storage subsystem port (target)
    2) the lun masking / mapping has to be setup
    3) fnic driver has to be installed
    Therefore, if you don't see your boot lun, either 1) and or 2) has to be fixed
    then
    4) only one path should be configured (e.g. fabric a), because no multipathing is available during installation, this is very important, and necessary for W2003, 2008 and 2012
    and
    5) if you see the boot lun, and can install, but the boot fails, the problem is the boot policy !
    Very easy ! Good luck !

  • VLAN Tagging from Windows on UCS B200m Server

    We have two B200m blades that we have installed with Windows 2008 R2 and need to determine if the current driver set available for the MK81R/MK82R for Windows 2008 R2 supports VLAN tagging from inside of Windows.  If anyone could point me in the right direction I would surely appreciate it!

    Windows has never been a great OS for trunking multiple VLANs.  The best way to set an individual adapter to a certain VLAN is to set it as the Native VLAN on the UCSM side.  The order of the vNICs seen in the UCSM and the order that windows sees them is not always the same so match them up by MAC address, then set the Native VLAN to the correct one on the vNIC within the UCSM and you should be all set within Windows.
    Drivers can be found on the Cisco.com Support page, under
    Downloads Home
    Products
    Unified Computing and Servers
    Cisco UCS B-Series Blade Server Software
    Unified Computing System (UCS) Drivers

  • Installing windows server 2008 on UCS C210 M2 problem

    Please help me in this issue
    My new server Cisco UCS C210 M2, that has only one hard disk and I need to set up windows server 2008 R2 SP1
    When I making the installation in the windows installation stage, the completing installation part the server is hanging and stop in this state
    I tried to change the windows image and still the same problem
    I need to know please if there are a certain criteria like PCI configuration or any change on this server hardware before installing windows server 2008 R2
    I searched in the below links
    http://www.cisco.com/en/US/docs/unified_computing/ucs/os-install-guides/windows/CSERIES-WINDOWS_chapter_01.html#reference_9858434220524A52A039038C9449D775
    http://www.cisco.com/en/US/docs/unified_computing/ucs/os-install-guides/windows/CSERIES-WINDOWS_chapter_011.html#t_installationonaninternaldrive

    when restaring the windows after that it give me the below message in the attached image from the KVM consol

  • Windows 2008 r2 ethernet problem on UCS

    i have installed windows 2008 R2 on a B440 M2 and having issues with the network. not able to ping even the default gateway or any other servers on the same network/vlan
    an esx server in the same VLAN works fine.
    i know this is only partial information, but was wondering if there was some config off the top that i am missing
    p.s. my chassis has the palo card

    The most common issue I see in this instance is that the servrice profile associated with Windows does not have the associated vlan marked as native.
    - Confirm the service profile has the appropiate vlan
    - Confirm the vlan is marked as native
    - Can the windows OS ping other hosts on the same subet in the same UCS chassis
    - Is there an impact if you force traffic over fabric A or B.
    HTH,
    Dan

  • Just like HP servers, does Cisco UCS C-Series Standalone supports Network Fault Tolerance ?

    Just like HP servers, does Cisco UCS C-Series Standalone supports Network Fault Tolerance ? if yes then, where can i find this option
    Windows :- 2k8 R2

    Just like HP servers, does Cisco UCS C-Series Standalone supports Network Fault Tolerance ? if yes then, where can i find this option
    Windows :- 2k8 R2

  • Windows 2008 in UCS B200 Blade NIC VLAN problem

    Hello Experts,
    I've installed Windows 2008 Enterprise on Bare-metal UCS B-200 M2 server with VIC M81KR Mezannine card. UCS Manager version is 1.3(c).
    The Problem that I have is that I cannot define VLANs on the NIC adapter inside Windows. is this a problem with the NIC driver ?
    ( Other NIC cards in other machine for example, have Advnaced Tab in the network configuration where we can define VLANs ).
    ( in this situation, Windows is un-aware of the VLANs so all the traffic going out will be untagged and FI sending it to the native VLAN on the network).
    Attached is a screenshot of the NIC properties in Windows. Your help is highly appreciated on this.
    Regards,
    Mohammad

    Thank you for your answer Padma.
    I have simple requirement for this to work. I have two blades windows installed on them and NICs having IPs from the range of VLAN 100 ( IP range : 192.168.100.x). Now I need to reach these two windows machines from other subnets ( subnet VLAN 2 for example / range 192.168.2.x ).
    In this scenario, I cannot reach these two windows machines until I define VLAN 100 as native ( default ) in vNIC configuration in the service profile of the balde. ( I understand that windows is sending the traffic un-tagged and because VLAN 100 is the native VLAN in UCS manager, it will forward this un-tagged traffic to VLAN 100 where it is routed to VLAN 2 in our case ).
    Do you have any other suggestions for other configuration for these windows machine to be reached from different VLANs in our network ?
    Thanks,
    Mohammad

  • How to install Cisco Work 3.2 on Windows 2008 Server Standard R2

    Hi Everyone,
    I have got Cisco Works LAN Management 3.2. But the problem is that i have a Windows 2008 Server Standard R2 and when i try to install, it fails. What I read from the below link is that it supports
    "Windows 2008 Server Standard and Enterprise Edition with Service Pack 1 and 2. Both 32-bit and 64-bit operating systems are supported on the above versions."
    http://www.cisco.com/en/US/partner/prod/collateral/netmgtsw/ps6504/ps6528/ps2425/data_sheet_c78-534877.html
    Please help me out on how i should install on the Windows 2008 Server Standard R2. If there is any patch or any other way out.
    Awaiting your response.
    Farid

    Hi ,
    LMS 3.2 is not supported on Windows 2008 Server Standard R2.
    here is the supported platoform for LMS 3.2
    http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/3.2/install/guide1/prereq.html#wp1110367
    Thanks,
    Gaganjeet

  • Slow network printing on Windows 2008 Server

    Hi,
    We are just testing/configuring a Windows 2008 (x64) server to replace an aging Windows 2000 file & print server.
    I have added the print services role and added a network TCP/IP printer (a HP Laserjet 2200).
    When I print to this printer from either the server (via print test page) or from a client, it takes around 30 seconds before the print will start to print. On our Windows 2000 server, this would print immediately.
    I have insalled the HP 2200 driver that came with Windows 2008.
    Anyone any ideas where to find the problem causing the delay?
    Thanks,
    Kenny

    Hello,
    I have done some research and I find firewall component of the antivirus software such as Mcafee might cause similar network delay issues.
    If you have installed AV softwares on Windows Server 2008, please try uninstalling it temperately and test whether this will make any difference.
    Moreover, You could also try disabling TCP Chimney Offload, RSS, Receive Window Auto-Tuning Level on Windows Server 2008 one by one to see whether it makes any difference.
    To disable TCP Chimney Offload, follow these steps:
    a.   Use administrative credentials to open a command prompt.
    b.   At the command prompt, type the following command, and then press ENTER:
           netsh int tcp set global chimney=disabled
    To disable RSS, follow these steps:
    a.   Use administrative credentials to open a command prompt.
    b.   At the command prompt, type the following command, and then press ENTER:
           netsh int tcp set global RSS=disabled
    To disable 'Receive Window Auto-Tuning Level', follow these steps: :
    a.   Use administrative credentials to open a command prompt.
    b.   At the command prompt, type the following command, and then press ENTER:
           netsh interface tcp set global autotuninglevel=disabled
    I hope this helps. Thanks.
    Regards,
    Neo Zhu

  • Cannot ping windows 2008 r2 while it is possible for another machine in the same network

    Hi,
    Recently I have set up a new server with windows 2008 r2 enterprise OS which is a domain member server. 
    At network layer I have two networks one with 192.168.1.0/22 and another with 10.0.0.0/24 network IDs.
    My problem is that I cannot ping the newly installed server from a specific machine. Server's IP address is 192.168.1.56 and the specific machine's IP address is 10.0.0.12 and it is a windows XP machine. Of course I have to say that this problem belongs
    only to this WinXP machine and all the layer 3 issues are tested and correct. This issue happens while at the same time I can ping domain controller which also is a windows 2008 r2 enterprise box and its IP address is 192.168.1.53. It turns more complicated
    when I learned I can ping the winxp machine and connect to it from new server through remote desktop. Firewall also is not the obstacle because I turned it off completely. 
    Can anybody help me fix the problem?
    TIA
    Bijan

    Hi,
    Check the path ping from xp machine to server its timing out after reaching 192.168.1.254 , What kind of a device is 192.168.1.254 IP belongs to.
    Tracing
    route to sp45newfs.ph45.local [192.168.1.56]
    over
    a maximum of 30 hops:
    0  B15-333.PH45.LOCAL [10.0.0.12]
    1  192.168.1.254
    2     *        *        *
    Computing
    statistics for 50 seconds...
              Source to Here   This Node/Link
    Hop
     RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
    0                                           B15-333.PH45.LOCAL [10.0.0.12]
                                  0/ 100 =  0%   |
    1    0ms     0/ 100 =  0%     0/ 100 =  0%  (192.168.1.254)----------(Which device has this IP)
                                100/ 100 =100%   |
    2  ---     (100/ 100 =100% )---(100% loss)    0/ 100 =  0%  B15-333.PH45.LOCAL [0.0.0.0]
    Trace
    complete.
    Regards,
    Srivishnu.K

Maybe you are looking for