Deployment Solution

 View Only

SQL/Altiris Connections and Teaming NICs 

Sep 18, 2007 12:02 PM

A couple of weeks ago we noticed that we were having a problem with our Deployment Server losing its connection to the SQL server every couple of hours. We were at a loss as to what was going on. The only information we could see was in the event viewer on our Altiris server which showed us exactly what time we would lose the connection. It turns out that about a week earlier we upgraded our main HP switch in the server and figured there must be some correlation between this and our Altiris/SQL communication problem. It turns out that since we team the NICs on our SQL server the two network cables needed to be in the same switch. We put the network cables for the SQL server back on the same switch and all has been well since. Just wanted to pass this along in case anyone else has had a similar problem. I know I racked my brain for a good week on this.

Statistics
0 Favorited
0 Views
0 Files
0 Shares
0 Downloads

Tags and Keywords

Comments

Sep 19, 2007 08:53 AM

You can use HP teaming across switches. I have my teaming configured in NFT mode, with packet tagging enabled. On my procurve switches I have nolacp configured, and I have two 2Gb trunks between the switches. As long as your spanning tree isn't blocking communication between switches, it's absolutely possible to team between them.
An easy way to test this is to assign an IP to each nick in the team and ping them from another host first connected to one switch and then from the other.

Related Entries and Links

No Related Resource entered.