C240 M3 with VIC 1225 VMware network issue

Just got my hands on a few C240 M3′s with the VIC 1225 adapter and began setting them up as a VMware 5.1 U1 cluster. I’ve configured 8 vNICs per host: 2 for Management, 2 for VMotion, 2 for iSCSI, and 2 for VM traffic. Each pair of vNICs has one pinned to uplink 0 and the other to uplink 1. vNICs are set to trunk mode in the VIC since I am tagging multiple VLANs from VMware. The hosts are physically connected to a stacked pair of Cisco 4500-X switches; physical uplink 0 to one switch, uplink 1 to the other switch. Switch ports are trunked to allow the VLANs we plan to use. Portfast is enabled. VMware vSwitches using Source Port ID for Load Balancing and the vNICs are active/active for Management and VM traffic. No port channel or Etherchannel is configured on the swtiches.
After creating a VM for vCenter and joining the hosts to it, I started migrating existing VMs from an old cluster and saw odd network behavior. It seems whenever a VM or vmkernel interface are on any vNIC pinned to the same physical uplink on the same host, they can’t talk to each other.
Example: VM1 and VM2 are on host 1. VM1′s network adapter is pinned to vNIC1 using VLAN 10 which uses physical uplink 0. VM2′s network adapter is pinned to vNIC2 using VLAN 10 which uses physical uplink 1. VM1 and VM2 can ping each other. If I move VM2′s network adapter to any vNIC that uses physical uplink 0, just like VM1, then VM1 and VM2 can no longer ping each other. Or if host 1′s management IP is pinned to vNIC 1 on physical uplink 0, any VM on host 1 using a vNIC also pinned to physical uplink 0 cannot ping the host.
Anyone have any ideas? Is something configured incorrectly on the switch? On the VIC?
Thanks!

Hello Michael,
I assume VIC is operating Classical Ethernet ( CE ) mode and VM1 and VM2 are in different vswitchs for the non-working scenario, ( where there vNICs used by vSwitch are pinned to physical uplink ) .
If this is the scenario, the frames have to be switched upstream switch and needs to be forwarded back on the same switch interface. Any IEEE standards based switch will not forward such traffic flow.
You might want to take advantage of Adapter-FEX or adapt changes to design to accommodate such traffic flows.
HTH
Padma

Similar Messages

C240 M3 with VIC 1225 managed with UCSM: Failure Reason: not enough vNIC available

Hello,
I have problems in creating a working service profile with more than one vNIC/NIC.
I have a shiny new C240 server with a UCS VIC 1225 network card in PCI Slot 2. The server is directly connected to the two Fabric Interconnects (6248UP). 2 Direct attached cables with no FEX ("Direct Connect Mode Cluster Setup"). Firmware version is 2.2(1d). After setting the FI port to server role the server is flawlessly discovered. And shows up in the UCSM-GUI. And I see the VIC 1225 adapter that has 2 DCE Interfaces.
Now, when I try to create Service Profile for this server by choosing "Hardware Based Service Profile" (with Create default vNICs [X] and Create Default vHBA [ ]) I get the following error:
I am able to create a working profile with one vNIC in one fabric, but a soon as I try to add a second vNIC I get the error above.
What I expected was, that it is possible to map more than one vNIC/NIC into the server profile. At leat 2 NICs, one in each fabric.
I would be great if there is someone to bring some light in the darkness thats around me. Any hints or pointers to obvious documentation would be great.
Kind regards,

Hello,
thanks for your answer. And you are probably correct.
I can add aditional vnics to fabric A but not to fabric B. And even trying to add a single nic to Fabric B does not work.
I changed the ports for this server on the fabric interconnects and rebooted the FI but it did not help.
When I look at the General Tab of my server and then on Connection Details I see:
Conection Path: A, B
Connection Status: A
Managing Instance: A
My conclusion is, I have a problem with the Connection Path B of my C240..

UCS C420M3 server with VIC 1225 , Cant see LOM ethernet ports

Hi Guyz,
we have C420M3 server with VIC 1225 connected on PCIe slot, with Fabric Interconnet.
After installing OS & drivers , vNICs created on VIC 1225 by service profile appear, but 4 gig ports on Server LOM dont appear.
Any Idea.?
Thank

If you integrate your rack server to UCSM, you will be able to use the LOM ports ONLY for Mgmt traffic, that is when you integrate the server in "Dual Wire Mode".
There is no need (unless you have one for an special reason I am not considering in this very moment) to use the LOM ports once you have integrated the server, precisely cause the VIC 1225 is a not a regular NIC card, nor a regular HBA, it is actually a CNA (Converged Network Adapter) which basically lets you do in one card, what you would do with two (meaning "what you would do with a separate NIC and HBA")
When you have a VIC card, you actually have the option to create up to 256 virtual interfaces (that's the capability of the hardware, always limited by the OS used, please keep that in mind), that is the reason why, after the server is integrated, you totally depend on the interfaces set in the Service Profile instead of the physical interfaces.
Find more info here:
http://www.cisco.com/c/en/us/products/interfaces-modules/unified-computing-system-adapters/models-comparison.html
Do you have a particular reason for using the LOM ports instead of creating 2 additional virtual interfaces in the Server's Service Profile?
-Kenny

Cisco UCS C220 with VIC 1225

Hello,
We have Cisco UCS C220 M3 with VIC 1225 card installed. We connected only one 10G port of VIC 1225 to Nexus 5548UP switch. But I do not see this port on switch and in CIMI the status for this port shows Link Down. I wanted to to iSCSI boot from storage NetApp FAS2240 but since I don't see this port on my Nexus switch I am unable to do boot from NetApp. I tried both ports on VIC 1225 with same result. Please I need help in this matter. I know I am missing something very simple but can't figure this out.
Thanks,
Salman

Hi Kenny,
Here is the answers:
-What slot is this card installed in?
Mezzenine
-How many CPUs does the server have installed? (1 OR 2 CPUs can make the difference)
2x 2.90 GHz E5-2690/135W 8C/20MB Cache/DDR3 1600MHz
-Is the PCIe slot enabled in BIOS? << Let us know if you don't know how to check it from CIMC
I believe I did. Server>BIOS>BIOS advanced> PCIe (Let me know if this correct)
-Have you confirmed that the cable is good?
I have changed four cables. I am using SFP-H10GB-CU2M= Twinax cable.
-If the switch does not even see the port and CIMC says it is down, have you confirmed the switch port is properly configured?
CIMI says “Link Down” in VIC adapter General area. The switch interface config has only “switchport mode access” in default vlan 1.
-What is the firmware running on the server and the OS?
We upgraded the firmware with latest ucs-c220-huu-1.5.4-3.iso.
Let me share with you the complete BoM of the server:
UCSC-C220-M3S              1x UCS C220 M3 SFF w/o CPU mem HDD PCIe PSU w/ rail kit
UCS-CPU-E5-2690              2x 2.90 GHz E5-2690/135W 8C/20MB Cache/DDR3 1600MHz
UCS-MR-1X082RY-A    16x 8GB DDR3-1600-MHz RDIMM/PC3-12800/dual rank/1.35v
CAB-9K10A-UK              2x Power Cord 250VAC 10A BS1363 Plug (13 A fuse) UK
UCSC-PCIE-CSC-02    1x           Cisco VIC 1225 Dual Port 10Gb SFP+ CNA
UCSC-PCIE-QSFP              1x Qlogic QLE8242-CU Dual Port 10 GbE FCoE CNA
UCSC-HS-C220M3              2x Heat Sink for UCS C220 M3 Rack Server
UCSC-RAIL1              1x Rail Kit for C220 C22 C24 rack servers

C240 with VIC 1225 : enable Failover

Hi,
I have a C240M3 with a VIC 1225. I would want to enable failover.
In order that, i have to enable NIV mode. But it seems to me that i could not.
Why ????
how to solve this issue ???
C240-FCH1749V0VC /chassis/adapter # set
cli         CLI options
description Adapter description
fip-mode     Enable/disable FIP
vntag-mode   Enable/disable VNTAG
niv-mode not present.....
C240-FCH1749V0VC /chassis # show adapter 2 detail
PCI Slot 2:
   Product Name: UCS VIC 1225
   Serial Number: FCH17457ESH
   Product ID: UCSC-PCIE-CSC-02
   Adapter Hardware Revision: 6
   Current FW Version: 2.1(3a)
   VNTAG: Disabled
   FIP: Enabled
   Configuration Pending: no
   CIMC Management Enabled : yes
   VID: V03
   Vendor: Cisco Systems Inc
   Description:
   Bootloader Version: 2.1(3a)
   FW Image 1 Version: 2.1(3a)
   FW Image 1 State: RUNNING ACTIVATED
   FW Image 2 Version: 2.1(3a)
   FW Image 2 State: BACKUP INACTIVATED
   FW Update Status: Idle
   FW Update Error: No error
   FW Update Stage: No operation (0%)
   FW Update Overall Progress: 0%
C240-FCH1749V0VC /chassis #
any detail on NIV
My C240 is connect to Catalyst 3750.
Many thx.
Nicolas.

Hello Kenny,
My main question is « how to use and to configure failover on VIC 1225 ». I have already configure failover on B-serie but never on c-series
For more details (please see diagram in attach), my issue is that my C240 on DRP site (just 40 metres from main site) is connected to local switch (C3560) and to LAN core (C4506 on main site). This connection on 2 Catalyst devices seems to be a problem for vSphere :
i could see that : as soon as I connect the 2 ports, C240 lost connection to vCenter ; CIMC is still pinging.
I could read on ucsguru forum, someone has the same issue with 2 catalyst.
I do not have a lot of time for this deployment and installation. So, I told me to use actif/passif should be the faster way. If I connect only a cable (by shuting/ no shuting an interface on a catalyst), it works. In order to do that, automatically, I would want to implement failover on VIC1225
Any suggestion on my issue is welcome.
Many thanks.
Nicolas.

Solaris 10 with Qlogic card facing network issue

Dear Community,
I am facing network issue with one of M5000 server
card vender is qlogic and switch is brocarde,
if we reset the port from switch side, it will work for nearly 2 hours. after that ping will stop.
here is the details. and there is no error on messages.
bash-3.2# dladm show-dev
bge0            link: up        speed: 1000 Mbps       duplex: full
bge1            link: unknown   speed: 0     Mbps       duplex: unknown
qlge2           link: up        speed: 10000 Mbps       duplex: full
qlge3           link: unknown   speed: 10000 Mbps       duplex: half
bash-3.2# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
        inet 127.0.0.1 netmask ff000000
bge0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
        inet 172.16.200.52 netmask ffffff00 broadcast 172.16.200.255
        ether 0:21:28:d6:41:10
qlge2: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
        inet 172.16.200.51 netmask ffffff00 broadcast 172.16.200.255
        ether 0:c0:dd:29:7f:68
port is showing as UP
what is the steps to diaganose this issue.
Network also same physical layer.
card : Qlogic
Switch : Brocade

*** moderation ***
Thread locked.
You are already discussing your HBA-to-switch configuration issues in your recent and very active forum thread:
https://community.oracle.com/thread/3687788
Stay there. Keep all information in a single location.
You will get additional responses when people choose to respond.

Low printer with lomg processing times ; network issues

Hello,
We are running ECC6 on HP-UX 11.23/Oracle 10.2
We have configured all our printers ( more than 300) using the host spool access method L : Print Locally using LP/LPR.
Every day, we have the same printers with the sames "low printers" :
sm21 syslog shows ;
Printer WRAL Temporarily Locked Due to Connection Problem
Spool Process logs indicates ;
Fri Feb 17 11:09:37 2012
Warning: lpq on printer WRAL took 16 seconds!
RSPOSYSLOG:
SYSLOG written: CODE FBL, locat 28, param WRAL&16&
There are several notes that indicate how to deactivate the printer pooling, but still, the best thing to do is to pinpoint the
root cause of the issue, .....which we haven't
I checked the spool distribution times in transaction STAD, I have unusuallyhigh "processing times" values.
But I can't underdstand it.
Is it a network processing time ?
Our network team tell us that there is nothing abnormal, but is there a way to check from SAP , any netwok issue with the printers ?
Thanks
Edited by: Raoul Shiro on Feb 17, 2012 5:09 PM

Hi,
For log "Printer WRAL Temporarily Locked Due to Connection Problem", it means
that for a period of xxx seconds (parameter rspo/lpq/temp_disable_time) no query or printing from sap for this printer are done anymore.
This has no influence on the printout from any other application. The only effect is that the printer is 'disabled' within sap.
The idea behind this concept is to prevent that a slow query can slow down the overall print performance of one server. During the query the spool wp cannot do anything else. In this time no printout to any printer from this server can be done.
It would seem that the problem is outside of the R/3 system and is at UNIX or printer level. Perhaps you had a temporary Network or printer problem. You can test by executing the lpstat query to this printer at OS level.
You can find out the exact lpstat query that your system uses, by looking at the system parameters 'rspo/host_spool/query'.
The parameter &P in the command will be substituted by the host device name.
If everything is correct in your unix spooler then it is very likely that the printer is not working correctly, so the unix spooler can't send print jobs to this printer, Therefore SAP blocks this printer for a certain time trying not to overload the unix spool queue.
You might want to temporarily turn off the query but if there is a problem with a specific printer or OS problem, this
will not be reported back to R/3.
Some SAP notes:
385794 - Connection problems with network access methods
20924 - Parameter settings for remote printing
Regards,
Vincent

UCS C-Series VIC-1225 to Nexus 5000 setup

Hello,
I have two nexus 5000 setup with a vpc peer link. I also have an cisco c240 m3 server with a vic-1225 card that will be running esx 5.1. I also have some 4 2248 fabric extenders. I have been searching for some best practice information on how to best setup this equipment. The nexus equipment is already running, so its more about connecting the c240 and the vic-1225 to the nexus switches. I guess this is better to do rather than to connect to the fabric extenders in order to minmize hops?
All documention I have found involves setup/configuration etc with fabric interconnects which I dont have, and have been told that I do not need. Does anyone have any info on this? and can point me in the right direction to setup this correctly?
More specifically, how should I setup the vic-1225 card to the nexus? just create a regular vpc/port-channel to the nexuses? use lacp and set it to active?
Do I need to make any configuration changes on the vic card via the cimc on the c240 server to make this work?

Hello again, Im stuck
This is what I have done. I have created the vPC between my esx host and my two nexus 5000 switches, but it doesnt seem to come up:
S02# sh port-channel summary
Flags: D - Down        P - Up in port-channel (members)
        I - Individual H - Hot-standby (LACP only)
        s - Suspended   r - Module-removed
        S - Switched    R - Routed
        U - Up (port-channel)
        M - Not in use. Min-links not met
Group Port-       Type     Protocol Member Ports
      Channel
4     Po4(SD)     Eth      LACP      Eth1/9(D)
vPC info:
S02# sh vpc 4
vPC status
id     Port        Status Consistency Reason                     Active vlans
4      Po4         down* success     success                    -
vPC config:
interface port-channel4
switchport mode trunk
switchport trunk allowed vlan 20,27,30,50,100,500-501
spanning-tree port type edge trunk
vpc 4
interface Ethernet1/9
switchport mode trunk
switchport trunk allowed vlan 20,27,30,50,100,500-501
spanning-tree port type edge trunk
channel-group 4 mode active
Im unsure what I must configure on the cisco 240M3(esx host) side to make this work. I only have the two default interfaces(eth0 and eth1) on the vic-1225 installed in the esx host, and both have the vlan mode is set to TRUNK.
Any ideas on what I am missing?
Message was edited by: HDA

Issues configuring VIC 1225 in C240

I'm trying to configure a C240 server with the VIC 1225 installed.
First off, I'd like to know if it's even possible to use this without Fabric Interconnects or Nexus switches. Assume I'm just hooking them up to some regular 10GbE switches. I can change this but wante to have a better idea of my design decisions - not a lot of info regarding when the VIC 1225 can or should be used outside this context.'
Secondly, I am following the directions here:
http://www.cisco.com/en/US/docs/unified_computing/ucs/c/sw/cli/config/guide/1.4.1/b_Cisco_UCS_C-Series_CLI_Configuration_Guide_141_chapter_01001.html#task_3C31BD7B25BF4CF6839B7B12DE014482
I've verified that the VIC is installed in slot 1 visually as well as through the output below, but the output below isn't what I expected per the documentation. I'm not able to get into the scope of this adapter, and it's showing up in "show pci-adapters" and not "show adapters". It's like it's not even being recognized as a VIC.
Any help would be appreciated.
ucs-c240-m3 /chassis # scope adapter 1Error: Managed object does not exist, use show command to list valid targetsucs-c240-m3 /chassis # scope network-adapter 1Error: Managed object does not exist, use show command to list valid targetsucs-c240-m3 /chassis # scope pci-adapter 1% Incomplete commanducs-c240-m3 /chassis # scope pci-adapter 1 <CR> Press Enter keyucs-c240-m3 /chassis # scope adapter          Cisco Systems UCS Virtual Interface Card dimm-summary     Information common to all DIMMs fan-policy       Fan Policy parameters firmware         Get all Components Firmware flexflash        Cisco FlexFlash Controller gpu              Show GPU cards present in the system hdd              Host local hard disk drive network-adapter Show network adapters present in the system storageadapter   RAID Controllerucs-c240-m3 /chassis #

Matt,
The VIC 1225 is fully supported as a stand-alone card outside of UCSM and by default it runs in Classical Ethernet mode which means it's supported with any IEEE standard 10GE switch.
The VIC is not supported in Slot 1 in the C240, it is supported in Slot 2 or 5
(http://www.cisco.com/en/US/docs/unified_computing/ucs/c/hw/C240/install/replace.html#wp1337242).
Without being installed in the proper slots, the NC-SI connector at the end of the PCIe bus will not be conencted and the CIMC has no interface to to configure the card. Once you have installed it in a supported slot you should be able to scope chassis and show the adapter. Then scope to the adapter as shown below
ucs-c240-m3# scope chassis
ucs-c240-m3 /chassis # show adapter
PCI Slot Product Name   Serial Number Product ID     Vendor
2        UCS VIC 1225   FCH162974VP    UCSC-PCIE-C... Cisco Systems Inc
ucs-c240-m3 /chassis # scope adapter 2
ucs-c240-m3 /chassis/adapter #
Once you are able to see your VIC let me know if you have additional questions.
Steve McQuerry
UCS - Technical Marketing

C460 Rack Server with two VIC 1225 - UCSM vNIC placement policy

I am trying to integrate C460 having 2 VIC 1225 cards with UCSM. The objective is to have 2 ethernet interfaces assigned to each VIC , one per FI.
vNIC 1 on VIC 1 - FI A failover to FI B
vNIC 2 on VIC 1 - FI B failover to FI A
vNIC 3 on VIC 2 - FI A failover to FI B
vNIC 4 on VIC 2 - FI B failover to FI A
I have created a service profile with 4 vNICs and assigned to C460. When the UCSM is configured to use the system default for vNIC/vHBA placement policy, all 4 vNICs are assigned to one VIC. When trying to place them manually with 2 on vCon1 and 2 on vCon2, I am seeing insufficient resource error. Both the VIC are recognized and UCSM server tab shows both of them as adapters.
Could someone please let me know how to achieve it?
Thanks!

The C460 has an integrated BCM 57711 which would also be recognized by the system. What's most likely happening is that the VIC 1225s are on vCon1 and vCon3 and the BCM card is on vCon2, since FF is not supported on the Broadcom adapter this would cause the association to fail. Try placing the manual placement with vCon1 and vCon3 and see if this clears up the issue.
Steve McQuerry
UCS - Technical Marketing

C460-M2 with 2 VIC-1225, managed by UCSM

C460-M2 with 2 VIC-1225; all documents show only one VIC-1225 (which has to be in PCI slot nr.1) single wire managment with a UCS FI ?
Is this a limitation ? or must the second VIC-1225 be connected to a switch outside the FI ?
Walter.

I received the following answer
Good question Walter. The documentation is confusing. If running the C460 as part of a UCS integration, only 1 card is supported.Although the server supports 2 cards , slot 1 & 2 according to the specsheet. The datasheet states that upto 3 VIC can be supoprted int he server.
The Cisco CCW config tool allows you to configure 2 VIC1225 in the C460.
From the 460 spechseet.
http://www.cisco.com/en/US/prod/collateral/ps10265/ps10493/ps11587/spec_sheet_c17-662220.pdf
Page 24
The C460 server accommodates the Cisco 1225 Virtual Interface card, which is supported only in slots 1 and 2. Note, however, that if the server is running UCSM, only slot 1 is supported for the VIC card.
■ The Cisco Card NIC mode is currently supported only with a Cisco 1225 VIC (UCSC-PCIE-CSC-02) that is installed in PCIe slot 1.
■ The C460 server accommodates the Cisco 1225 Virtual Interface card, which is supported only in slots 1 and 2. Note, however, that if the server is running UCSM, only slot 1 is supported for the VIC card.
From the datasheet
http://www.cisco.com/en/US/prod/collateral/modules/ps10277/ps12571/data_sheet_c78-708295.html
System Requirements
The Cisco UCS VIC 1225 is designed for use only on Cisco UCS C-Series Rack Servers. A single Cisco UCS VIC 1225 is supported on Cisco UCS C260 M2, C460 M2, C220 M3, C240 M3, C22 M3, and C24 M3 rack servers. Up to three Cisco UCS VIC 1225 cards are supported on these servers depending on the slot configuration.
Anyone at Cisco want to clarify the above?
Message was edited by: NABIL YAGHI

Strange Networking Issue with OES

Since moving our entire infrastructure from Netware to OES, I've been trying to figure out a very strange issue. We are a K-12 school system with a data center at the central offices and a single server at each school. The data center has the servers that run all the centralized stuff, including the Master replicas for [root], the DA's for SLP, etc. We noticed that sometimes a school's server will drop out of the SLP tables. When that happens, we also cannot SSH to the school's server from the central servers. We can SSH to it from any other machine on the same subnet as the central servers. The central servers can ping it, but no UDP/TCP traffic can pass between them (no web traffic, etc). We finally realized it only happens when the ISP that serves that school has a brief blip or outage of some sort. The only way we have found to get the servers talking again is to reboot the central servers.
We have tried:
Restarting almost all services on central servers
Stopping and restarting networking
Switching to runlevel 1 and then back
Stopping firewall and/or shutting it off completely
Checking hosts.deny files
Disabling virus scanner (McAfee Enterprise)
Changing vmware network drivers from E1000 (known issue with vSphere 5.1) to VMXNET3
All servers run on HP Proliant servers (blades at central office, towers at schools) running vSphere 5.1. Links between the central office and schools are all 100Mbps fiber via two different ISP (depending on the school's location). A restart of the central office server fixes it every time. I am out of ideas now and at a loss as to why this happens when a WAN link goes down. We thought it was just isolated to one ISP, but it was just that that particular ISP is not quite as reliable as the other. We had an extended power outage at a school served by another ISP over the weekend and saw the same issue with that server after power was restored.
Any ideas or suggestions at where else we should be looking? We also run ZCM 11 at each school and the central office. When this happens, those servers never lose connectivity with each other and with the OES servers on each end. The ZCM servers run on the same vSphere host as the OES servers.

On 04/08/2014 12:26 PM, jmlester wrote:
>
> Since moving our entire infrastructure from Netware to OES, I've been
> trying to figure out a very strange issue. We are a K-12 school system
> with a data center at the central offices and a single server at each
> school. The data center has the servers that run all the centralized
> stuff, including the Master replicas for [root], the DA's for SLP, etc.
> We noticed that sometimes a school's server will drop out of the SLP
> tables. When that happens, we also cannot SSH to the school's server
To be clear, while i think this correlation is possible, I do not see any
possibility of causality in here unless your SSH client is somehow using
SLP to resolve the SSH server, which seems very unlikely. I'm not sure if
you're trying to state that SLP is the cause of the SSH stuff, but I do
not think you are.
> from the central servers. We can SSH to it from any other machine on
> the same subnet as the central servers. The central servers can ping
> it, but no UDP/TCP traffic can pass between them (no web traffic, etc).
Hmmm........... so routing works, and the server is even responding to
requests made to it (presumably, or something else is), but SSH is not
responding, or something is preventing it from responding.
> We finally realized it only happens when the ISP that serves that school
> has a brief blip or outage of some sort. The only way we have found to
> get the servers talking again is to reboot the central servers.
>
> We have tried:
>
> - Restarting almost all services on central servers
> - Stopping and restarting networking
> - Switching to runlevel 1 and then back
> - Stopping firewall and/or shutting it off completely
> - Checking hosts.deny files
> - Disabling virus scanner (McAfee Enterprise)
> - Changing vmware network drivers from E1000 (known issue with vSphere
> 5.1) to VMXNET3
>
>
> All servers run on HP Proliant servers (blades at central office, towers
> at schools) running vSphere 5.1. Links between the central office and
> schools are all 100Mbps fiber via two different ISP (depending on the
> school's location). A restart of the central office server fixes it
> every time. I am out of ideas now and at a loss as to why this happens
> when a WAN link goes down. We thought it was just isolated to one ISP,
> but it was just that that particular ISP is not quite as reliable as the
> other. We had an extended power outage at a school served by another
> ISP over the weekend and saw the same issue with that server after power
> was restored.
>
> Any ideas or suggestions at where else we should be looking? We also
> run ZCM 11 at each school and the central office. When this happens,
> those servers never lose connectivity with each other and with the OES
> servers on each end. The ZCM servers run on the same vSphere host as
> the OES servers.
I'd get a LAN trace from both sides at the same time. At the very least,
run tcpdump as shown below on both the central office machine as well as
the remote machine to see how the packets differ when trying different
things. If you do a test and do not see output on both sides, do it again
writing it to a file and post somewhere for us to review. Note: since
it's an SSH problem I would either NOT SSH into the system, or I'd be sure
to limit the tcpdump capture/output to something specific to the
connection being tested. Tracing something over which you are sending the
tracing data is never fun since every packet picked up causes another
packet to be generated, to be picked up, to be generated.... ad infinitum.
To see tcpdump output with limited details on the screen:
Code:
sudo /usr/sbin/tcpdump -n -s 0 -i any -vv
To write tcpdump output to a file:
Code:
sudo /usr/sbin/tcpdump -n -s 0 -i any -w /tmp/problem-20140408.cap
While filtering when capturing is typically not desired, you can do it by
adding something like 'host 10.1.2.3' to the list of tcpdump parameters at
the end of either of those two commands. The reason filtering during
capturing is not desired is that you may miss something.... the SLP
traffic, DNS, ARP, ICMP error showing the exact problem, etc.
Good luck.
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...

Very Strange Network Issue With Two Guests on 2012 R2 Hyper-V Failover Cluster

Hi all. We're having a odd issue with two guests on our 2012 R2 failover cluster.
In a nutshell, if we shutdown a particular server (I'll call it Server A) another totally different server (Server B) on the same node loses it's network connectivity to the domain. If we start server A back up, network connectivity returns on server B.
At first I thought server A might be running a service that was somehow linked to server B, so I decided to disable server A's NIC. Interestingly, that had no affect on server B's connectivity.
The next step I tried was pausing server A and again, no adverse affect on server B's connectivity.
Next step was to live migrate server A to another node. This action did
cause server B to lose its network connection.
One other clue is that if I ping server B from either of the Hyper-V hosts in the cluster, I never lose network connection to server B.
So I would suspect this is some network issue on the cluster, but I'm kind of at a loss where to go from here.
Has anyone seen this behavior before or does anyone have any troubleshooting suggestions I can try?
Thanks!
George Moore

Hi Sir,
I'v never seen this before .
>>Next step was to live migrate server A to another node. This action did
cause server B to lose its network connection.
They are connecting to same virtual switch ?
First please run cluster validation to check if there is any error .
If it is ok , please try the following items for troubleshooting :
1. shutdown serverA serverB
2. then add another virtual NIC for serverB
3. start server B check if the issue happens to both "old" and "new" virtual NIC .
In addition , you can live migrate both A and B to another node , then try to live migrate A to the original node .
If the issue persists , I would suggest you to remove that virtual switch on both nodes then re-create them .
Best Regards,
Elton Ji
If it is not the answer please unmark it to continue
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] .

Network issue with initial connections on Hyper-V

This is the opposite of all the other networking issues I have seen with Hyper-V- anyone run into this?
I am running Hyper-V on a Server Core installation, and have had the same issue when I used Server 2012R2 as when I used Server 2008R2 on the same server as a virtual host. The server is an HP ProLiant DL360 Gen8 with 2x 8-core processors, 32 GB RAM. The
VM is sized and configured to stay within 1 NUMA node. It uses a single port of the 4-port HP/Broadcom 331 NIC, with all the TCP LSO settings disable at the switch, host, and guest, same with the power management settings. We have ProxyARP on the network,
so I have set the ArpRetryCount key to 0.
I have seen it happening with and without SR-IOV enabled. The guest OS is an RDS server, so for the sake of our CAL's it has to stay at Server 2008R2. I have set up a HOSTS file to mitigate this problem, as it seems to be a DNS issue- Here's what happens:
The first time I visit a resource, the server will timeout. An example not in our HOSTS file does this consistently: If I go to https://mail.mydomain.com/OutlookWebAccess, it spins for a couple of minutes before timing out. I hit refresh and the page loads
immediately. This server is colocated in-house, as is the mailserver. I'd say it is a DNS issue at some level, but I'd like to know what level it is- Is it just timing out trying to cache the DNS request, or is there a performance issue with a DNS server on
the network? (All of our DNS is AD-integrated running on DC's).
Here is where I'm seeing this:
Internet Explorer- described above
Salient Interactive Miner- at the login screen, it searches for a database and times out. If I go to the setup and enter the IP address, it still times out. It will not find the database server until I quit and restart the program. If this is the same issue,
it would obviously not be a DNS problem.
I DON'T see it in GP9 connecting to a datasource
Prior to setting up the HOSTS file, I saw this in Windows Explorer connecting to network shares on the same LAN segment.
This appears to only happen to the Hyper-V guest OS. As a best practice, whenever Windows Update runs, I update the Integration Components.
I have the bindings properly ordered on the guest VM, with the network adapter the goes to the physical NIC first, and IPv4 ordered before IPv6.
All updates are isntalled, and the firmware is at it's latest revision.
Any ideas?

Hi Daniel,
" This appears to only happen to the Hyper-V guest OS. "
Do you mean that any other hosts can access the network resource normally except these VMs ?
If yes , my suggestion is to disable the VMQ on the physical NIC for the VMs , then try test again .
Best Regards
Elton Ji
If it is not the answer please unmark it to continue
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.

Issue with LDAP Connection becuase of Network issue

Hello All,
We have some network issues going on which is causing the NIC (Network interface card) to failover to another NIC. Due to this failover SUN access manager's LDAP connection pool fills up and we see errors in logs "Directory is down". We have to restart the Access manager to resolve this issue which refresh the connection pool of LDAP.
Now we have set the setting as recommended in admin guide/tuning guide. Like
1. Set event connection idle timeout to less that firewall or loadbalancer idle timeout value.
2. event connection retry count and interval on perticular error code.
Despite of above settings its not working out. Is there other way to get all the stale connections back to the LDAP pool without restarting the server?
Or something which handles the network failover or failback?
Regards
Chetan Kulshrestha

The user search name is the value you should be looking at in the LDAP attributes, that's the one that it will send to LDAP on a logon attempt. If you changed this value after mapping a group, I'm not sure but you may have to remap the group to get the change.
So on the LDAP side verify the user search attribute = the username you expect to login with (i.e. cn, samaccountname, uid, etc)
Regards,
Tim

C240 M3 with VIC 1225 VMware network issue

Similar Messages

Maybe you are looking for