- Community Home
- >
- Servers and Operating Systems
- >
- BladeSystem
- >
- BladeSystem Virtual Connect
- >
- Auto NIC failover scripts for Windows & Linux?
-
- Forums
-
Blogs
- Alliances
- Around the Storage Block
- Behind the scenes @ Labs
- HPE Careers
- HPE Storage Tech Insiders
- Infrastructure Insights
- Inspiring Progress
- Internet of Things (IoT)
- My Learning Certification
- OEM Solutions
- Servers: The Right Compute
- Shifting to Software-Defined
- Telecom IQ
- Transforming IT
- Infrastructure Solutions German
- L’Avenir de l’IT
- IT e Trasformazione Digitale
- Enterprise Topics
- ИТ для нового стиля бизнеса
- Blogs
-
Quick Links
- Community
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Contact
- Email us
- Tell us what you think
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Enterprise.nxt
- Marketplace
- Aruba Airheads Community
-
Forums
-
Blogs
-
InformationEnglish
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
02-26-2012 07:26 PM
02-26-2012 07:26 PM
Auto NIC failover scripts for Windows & Linux?
Stan was looking for a NIC failover test script:
*****************
Looking for a simple solution for a large financial company…
They have many C7000 enclosures, win2kX, and linux with teamed NICs, dual paths, redundant switches, etc.
They are asking if we have a script or (semi)automated method, to cause a failover on the NICs, ( Network A -> Network B) to validate, test in-frequently, to verify that all failover networks are working correctly? This would include doing the failover and verifing network conectivity on Network B, for example….
An automated or manually kicked off script would be the ideal, vs manual intervention on the various servers….
Wondering if someone has tackled this?
****************
From Chris:
*************
I don’t have a script, nor had anyone request this. However, just thinking off the top of my head, you can use NETSH in Windows to disable a specific connection, and ifconfig down eth# (or if-down if the distro is Red Hat based) in Linux. I wouldn’t suggest a customer do this during production hours, but rather during maintenance windows (if possible.)
************
And from Mike:
**************
As part of our Network Configuration Utility, we ship a utility called SetLACState.exe. It can be used to disable/enable a Local Area Connection (LAC) in windows.
***************
Any other suggestions?
- Tags:
- NIC
Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2019 Hewlett Packard Enterprise Development LP