How to configure NIC settings in TIBCO LogLogic LMI without using the web GUI
Article ID: KB0076740
Updated On:
| Products | Versions |
|---|---|
| TIBCO LogLogic Log Management Intelligence | all versions |
Description
LogLogic LMI provides two ways to change NIC settings when not using the web GUI. However, one way is persistent and the other way is not. Persistent means the settings will be preserved through a reboot.
Issue/Introduction
This article explains 2 methods for specifying NIC settings without using the GUI. One way is persistent and the other way is non-persistent.
Resolution
A common (and non-recommended) means for changing NIC settings is with the ethtool command from the toor shell. The recommended and persistent method to change the NIC setting on the LogLogic appliance is from the root CLI as shown below.
Persistent Example
From the root CLI shell:
$ su root
> help set
Usage: set eth<n> [10baseT-FD | 10baseT-HD | 100baseTx-FD | 100baseTx-HD | 1000baseTx-FD | 1000baseTx-HD | auto]
Change setting for network interface named eth<n>
where n is a single digit.
> set eth0 100baseTx-FD auto
> save
This will save eth0 settings at 100Mbps, Full Duplex and Auto-negotiate = on. It will also be persistent across reboots.
Non- Persistent Example
From the toor shell:
$ ethtool -s eth0 speed 100 duplex full autoneg on
This command will set eth0 to 100 Mbps, Full Duplex and Auto-negotiate = on. However, this is the non-persistent method for changing NIC settings.
The bottom line is use the root CLI method for persisting NIC changes.
Note:
Leaving the optional “auto” out of the CLI command is equivalent to turning auto-negotiate to “off.” However, depending upon other NIC settings and capabilities, you may not be able to manipulate the auto-negotiate setting.
Note:
You also want to make sure the remote connection at the network switch is set to the same speed and duplex of the appliance NIC. If auto-negotiate is “on” at the remoteconnection then it should also be “on” at the appliance. If it is “off” at the external connection, it should be “off” at the appliance. It is “off” then the speed and duplex must be identical at both ends.
Persistent Example
From the root CLI shell:
$ su root
> help set
Usage: set eth<n> [10baseT-FD | 10baseT-HD | 100baseTx-FD | 100baseTx-HD | 1000baseTx-FD | 1000baseTx-HD | auto]
Change setting for network interface named eth<n>
where n is a single digit.
> set eth0 100baseTx-FD auto
> save
This will save eth0 settings at 100Mbps, Full Duplex and Auto-negotiate = on. It will also be persistent across reboots.
Non- Persistent Example
From the toor shell:
$ ethtool -s eth0 speed 100 duplex full autoneg on
This command will set eth0 to 100 Mbps, Full Duplex and Auto-negotiate = on. However, this is the non-persistent method for changing NIC settings.
The bottom line is use the root CLI method for persisting NIC changes.
Note:
Leaving the optional “auto” out of the CLI command is equivalent to turning auto-negotiate to “off.” However, depending upon other NIC settings and capabilities, you may not be able to manipulate the auto-negotiate setting.
Note:
You also want to make sure the remote connection at the network switch is set to the same speed and duplex of the appliance NIC. If auto-negotiate is “on” at the remoteconnection then it should also be “on” at the appliance. If it is “off” at the external connection, it should be “off” at the appliance. It is “off” then the speed and duplex must be identical at both ends.
Feedback
Yes
No
Powered by
