- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- Dualport NIC cards
ProLiant Servers (ML,DL,SL)
1753797
Members
9093
Online
108805
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-07-2001 04:00 PM
тАО01-07-2001 04:00 PM
Dualport NIC cards
What are the autoexec.ncf commands to enable a secondary NIC port (on a seperate switch) to act as a failover device?
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-28-2001 04:00 PM
тАО01-28-2001 04:00 PM
Re: Dualport NIC cards
depends on if you are using NFT.NLM or CPQANS.LAN for the Teaming Driver.
CPQANS.LAN replaces NFT.NLM and is the latest.
Here is example using CPQANS.LAN
EXAMPLE #1 Simple NFT TEAM
==========================
The following is an example of an NFT Team that consists of a Gigabit
adapter and a Compaq Fast Ethernet adapter. The Gigabit adapter is the primary adapter
and the Compaq Fast Ethernet adapter is the secondary. Note that only an
NFT mode Team can combine a Compaq Gigabit adapter and a Compaq Fast
Ethernet adapter. See the NWTEAM.txt file for information about mixing adapters.
For simplicity, only the default frame type 802.2 is used. By default,
CPQANS uses the frame type 802.2. So, you do not need to specify
802.2 on the command line. Also by default, CPQANS uses the
NFT mode. In this example, only one instance of each adapter is present
in the system, so you do not need to specify a slot number.
Also, this example checks the "status" of the Team after each command.
1. Load CPQANS.LAN to form the basis of a Team. For this example,
CPQANS is only loaded once. If multiple frame types are used,
CPQANS is loaded once for each frame type.
LOAD CPQANS FRAME=ETHERNET_802.2
Now, check the status of the Team.
LOAD CPQANS STATUS
2. Load the base driver for each adapter and frame type for the Team. As
this example only uses 802.2, each adapter has its base driver
loaded only once.
LOAD N1000
LOAD N100
3. When you load CPQANS.LAN, it looks like a protocol, so you can
bind it to the physical adapter. Bind CPQANS.LAN to each physical adapter
in the Team. Notice the key word "PRIMARY." For performance
reasons the Compaq Gigabit adapter should be the primary adapter.
BIND CPAQNS N1000 PRIMARY
BIND CPQANS N00
Now, check the status of the Team. Notice that the Team now
has two adapter instances with the Team. Also notice that the Team is
in the "UNCOMMITED" state. The Compaq Gigabit adapter is the "PRIMARY."
LOAD CPQANS STATUS
4. The "COMMIT" command finalizes the Team. Since we have not chosen
the mode of the Team, it is NFT by default.
LOAD CPQANS COMMIT
Now, check the status of the Team. Notice that NFT is now
the Team mode and that the Team is now in the "committed" state.
No changes to the Team can be made once the Team is "committed".
LOAD CPQANS STATUS
5. Now that the Team is in the "commit" state, the CPQANS Team
appears as a virtual adapter. You may now bind a protocol to CPQANS.
Always make sure that your adapters and CPQANS are using the same
frame type!
BIND IPX CPQANS NET=102
Now, check the status of the Team.
LOAD CPQANS STATUS
CPQANS.LAN replaces NFT.NLM and is the latest.
Here is example using CPQANS.LAN
EXAMPLE #1 Simple NFT TEAM
==========================
The following is an example of an NFT Team that consists of a Gigabit
adapter and a Compaq Fast Ethernet adapter. The Gigabit adapter is the primary adapter
and the Compaq Fast Ethernet adapter is the secondary. Note that only an
NFT mode Team can combine a Compaq Gigabit adapter and a Compaq Fast
Ethernet adapter. See the NWTEAM.txt file for information about mixing adapters.
For simplicity, only the default frame type 802.2 is used. By default,
CPQANS uses the frame type 802.2. So, you do not need to specify
802.2 on the command line. Also by default, CPQANS uses the
NFT mode. In this example, only one instance of each adapter is present
in the system, so you do not need to specify a slot number.
Also, this example checks the "status" of the Team after each command.
1. Load CPQANS.LAN to form the basis of a Team. For this example,
CPQANS is only loaded once. If multiple frame types are used,
CPQANS is loaded once for each frame type.
LOAD CPQANS FRAME=ETHERNET_802.2
Now, check the status of the Team.
LOAD CPQANS STATUS
2. Load the base driver for each adapter and frame type for the Team. As
this example only uses 802.2, each adapter has its base driver
loaded only once.
LOAD N1000
LOAD N100
3. When you load CPQANS.LAN, it looks like a protocol, so you can
bind it to the physical adapter. Bind CPQANS.LAN to each physical adapter
in the Team. Notice the key word "PRIMARY." For performance
reasons the Compaq Gigabit adapter should be the primary adapter.
BIND CPAQNS N1000 PRIMARY
BIND CPQANS N00
Now, check the status of the Team. Notice that the Team now
has two adapter instances with the Team. Also notice that the Team is
in the "UNCOMMITED" state. The Compaq Gigabit adapter is the "PRIMARY."
LOAD CPQANS STATUS
4. The "COMMIT" command finalizes the Team. Since we have not chosen
the mode of the Team, it is NFT by default.
LOAD CPQANS COMMIT
Now, check the status of the Team. Notice that NFT is now
the Team mode and that the Team is now in the "committed" state.
No changes to the Team can be made once the Team is "committed".
LOAD CPQANS STATUS
5. Now that the Team is in the "commit" state, the CPQANS Team
appears as a virtual adapter. You may now bind a protocol to CPQANS.
Always make sure that your adapters and CPQANS are using the same
frame type!
BIND IPX CPQANS NET=102
Now, check the status of the Team.
LOAD CPQANS STATUS
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-01-2001 04:00 PM
тАО02-01-2001 04:00 PM
Re: Dualport NIC cards
Mark provided the best answer for this, way to go Mark.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP