Services fail to start with HP NIC Teaming

I enabled HP NIC Teaming on a number of our servers. On systems where
services log on with a domain account, rather than with the local system
account, those services fail to start when the system is rebooted. They can
be started using services.msc after logging onto the system. Those same
services do start normally after a reboot if NIC Teaming is disabled.

The systems are all running Windows Server 2003 SP-1. The HP NIC Teaming
driver is cpqteam.sys, v8.10.00.0, which is part of the most recent HP
ProLiant Support Pack 7.40b.

My hypothesis is that this is a timing issue. It probably takes longer for
the HP NIC Teaming driver to establish network connectivity than it does for
the drivers for the physical NICS when they are not teamed. Thus with NIC
Teaming enabled, the services logging on with domain accounts are trying to
start before network connectivity to the domain controller is available to
authenticate them.

My question is how to block these services from starting until full network
connectivity with HP NIC Teaming is established.

--
Jeffry A. Spain
Network Administrator
Cincinnati Country Day School

Since it is an HP product, and it appears you have several HP servers, then
I would deduce you have HP support - why not give them a call? We use the
network bridging option that is native to Win2k3, and it seems to work just
fine in the situation you're describing?

--

Star Fleet Admiral Q @ your service!
Google is your friend!
http://www.google.com


"jaspain" <(E-Mail Removed)> wrote in message
news:84E4EFF6-4BDD-4848-B1C4-(E-Mail Removed)...
>I enabled HP NIC Teaming on a number of our servers. On systems where
> services log on with a domain account, rather than with the local system
> account, those services fail to start when the system is rebooted. They
> can
> be started using services.msc after logging onto the system. Those same
> services do start normally after a reboot if NIC Teaming is disabled.
>
> The systems are all running Windows Server 2003 SP-1. The HP NIC Teaming
> driver is cpqteam.sys, v8.10.00.0, which is part of the most recent HP
> ProLiant Support Pack 7.40b.
>
> My hypothesis is that this is a timing issue. It probably takes longer for
> the HP NIC Teaming driver to establish network connectivity than it does
> for
> the drivers for the physical NICS when they are not teamed. Thus with NIC
> Teaming enabled, the services logging on with domain accounts are trying
> to
> start before network connectivity to the domain controller is available to
> authenticate them.
>
> My question is how to block these services from starting until full
> network
> connectivity with HP NIC Teaming is established.
>
> --
> Jeffry A. Spain
> Network Administrator
> Cincinnati Country Day School

Thanks. We are pursuing an answer to to problem on a number of fronts. Can
you provide documentation references for the bridging to which you refer?
Bridging the NICs isn't what we are doing, rather link aggregation with LACP.

"Admiral Q" wrote:

> Since it is an HP product, and it appears you have several HP servers, then
> I would deduce you have HP support - why not give them a call? We use the
> network bridging option that is native to Win2k3, and it seems to work just
> fine in the situation you're describing?

Any errors in the Event Viewer? This case study may help,
Case Study - Troubleshooting NIC Teaming
Event ID 7000 - The service cannot be started

Situation: After you configure HP NIC Teaming and reboot the server, you may receive the following message “At least one service or driver failed during system startup. Use Event Viewer to examine the event for details�...

http://www.chicagotech.net/troublesh...ventid7000.htm


Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
"jaspain" <(E-Mail Removed)> wrote in message news:84E4EFF6-4BDD-4848-B1C4-(E-Mail Removed)...
I enabled HP NIC Teaming on a number of our servers. On systems where
services log on with a domain account, rather than with the local system
account, those services fail to start when the system is rebooted. They can
be started using services.msc after logging onto the system. Those same
services do start normally after a reboot if NIC Teaming is disabled.

The systems are all running Windows Server 2003 SP-1. The HP NIC Teaming
driver is cpqteam.sys, v8.10.00.0, which is part of the most recent HP
ProLiant Support Pack 7.40b.

My hypothesis is that this is a timing issue. It probably takes longer for
the HP NIC Teaming driver to establish network connectivity than it does for
the drivers for the physical NICS when they are not teamed. Thus with NIC
Teaming enabled, the services logging on with domain accounts are trying to
start before network connectivity to the domain controller is available to
authenticate them.

My question is how to block these services from starting until full network
connectivity with HP NIC Teaming is established.

--
Jeffry A. Spain
Network Administrator
Cincinnati Country Day School

Thanks. On one of my affected systems, the first error in the System Event
Log after restart is 5719 from the Netlogon service indicating that no logon
servers are available. Then there are error 7000 entries for both services
that authenticate with domain user accounts. The Application Event Log also
contains error 1053 from Userenv indicating that group policy processing has
been aborted.

The case study looks promising, however I have no C:\Utils\DualNIC folder
and no Teaming-CDP.cmd anywhere on the system. I'll look for these on the
Internet, but please let me know if you are aware of a source for them.

--
Jeffry A. Spain
Network Administrator
Cincinnati Country Day School


"Robert L [MS-MVP]" wrote:

> Any errors in the Event Viewer? This case study may help,
> Case Study - Troubleshooting NIC Teaming
> Event ID 7000 - The service cannot be started
>
> Situation: After you configure HP NIC Teaming and reboot the server, you may receive the following message “At least one service or driver failed during system startup. Use Event Viewer to examine the event for details�...
>
> http://www.chicagotech.net/troublesh...ventid7000.htm

In this case, I would re-do the Teaming.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
"jaspain" <(E-Mail Removed)> wrote in message news:B5F21788-1D63-4AA6-9989-(E-Mail Removed)...
Thanks. On one of my affected systems, the first error in the System Event
Log after restart is 5719 from the Netlogon service indicating that no logon
servers are available. Then there are error 7000 entries for both services
that authenticate with domain user accounts. The Application Event Log also
contains error 1053 from Userenv indicating that group policy processing has
been aborted.

The case study looks promising, however I have no C:\Utils\DualNIC folder
and no Teaming-CDP.cmd anywhere on the system. I'll look for these on the
Internet, but please let me know if you are aware of a source for them.

--
Jeffry A. Spain
Network Administrator
Cincinnati Country Day School


"Robert L [MS-MVP]" wrote:

> Any errors in the Event Viewer? This case study may help,
> Case Study - Troubleshooting NIC Teaming
> Event ID 7000 - The service cannot be started
>
> Situation: After you configure HP NIC Teaming and reboot the server, you may receive the following message “At least one service or driver failed during system startup. Use Event Viewer to examine the event for details�...
>
> http://www.chicagotech.net/troublesh...ventid7000.htm

I'm going to call HP support about it. The teaming driver gets installed as
part of the HP Support Pack. Having installed that a number of times on
various machines, I don't think a reinstall will help. There aren't any
installation options that I am aware of that relate to this.
--
Jeffry A. Spain
Network Administrator
Cincinnati Country Day School


"Robert L [MS-MVP]" wrote:

> In this case, I would re-do the Teaming.

To see if I could speed up the initialization of the NIC Teaming driver, I
tested configurations of the switch and server that would remove various
negotiated parameters of the physical links and the IP configuration.

I tested one of the servers, a DL360 G2, with the eight combinations of
speed/duplex settings 100/full or auto, LACP negotiation (configured on the
Catalyst 6500 switch) off or on (active), and IP address DHCP or static.

To avoid the having the services with domain user credentials fail, I had to
set either a static IP address or fixed 100/full speed/duplex settings or
both.

With LACP negotiation off, the NIC Teaming driver generated some warnings in
the event log, but this did not result in errors in any other services.

For my purposes, setting the speed/duplex to fixed settings and leaving the
IP address dynamic (we use DHCP reservations) will probably work the best.

I also spoke to HP support (case 3214364324). According to them, the
Teaming-CDP.cmd script is proprietary to Cisco and their Media Convergence
Server product, and thus not available to me. What it does remains an
unknown. This is the script referred to by Robert L in his previous post at
http://www.chicagotech.net/troublesh...ventid7000.htm. What appears to
be the original documentation from Cisco is at
http://www.cisco.com/univercd/cc/td/...r/hp_team7.htm.

Thus I believe I have a satisfactory resolution to this issue and a better
understanding of the factors involved. I appreciate your everyone's input.
Thanks. Jeff.
--
Jeffry A. Spain
Network Administrator
Cincinnati Country Day School