Dell Emulex Family of Adapters - Manual (Page 794)

OneCommand NIC Teaming and VLAN Manager User Manual P009415-01A Rev. A
5. OneCommand NIC Teaming Manager Command Line Interface
The Command Reference
794
Network Connection Name: J_ETH3
Alias: nic2 (unbound)
Device Manager Name: <AdapterName> #2
Network Connection Name: J_ETH1
Alias: nic3 (unbound)
Device Manager Name: <AdapterName> #3
Network Connection Name: J_ETH2
Alias: nic4 (unbound)
Device Manager Name: <AdapterName> #4
Network Connection Name: J_ETH4
Alias: nic5 (unbound)
Device Manager Name: Emulex OneConnect OCe11102[R]-I 2-port 10GbE SFP+ PCIe iS
CSI CNA
Network Connection Name: SLOT 2
Alias: nic6 (unbound)
Device Manager Name: Emulex OneConnect OCe11102[R]-I 2-port 10GbE SFP+ PCIe iS
CSI CNA #2
Network Connection Name: SLOT 2 2
Showing Teams
Note: If team members have different MTU sizes, a warning will appear. The MTU
warning will not affect the creation of the team.
Syntax
OCTeamCmd.exe show teams
Parameters
None.
Description
This command lists all teams including their team type, team members and assigned
VLANs. Teams are identified using the team name and network manager (network
connection name). If you get a warning about differing MTU sizes, your team is still
created. However, it is strongly recommended that you delete the team, correct the
MTU disparity, and then recreate the team.
Example
C:\Program Files\Emulex\NIC Teaming>OCTeamCmd.exe show teams
Device Manager Name: myteam
Network Connection Name: Ethernet 9
Connection Status: connected
Team type: Failover Automatic Failback: enabled
Reactivation delay: 30 seconds MTU: 1500