Network Interface “speed” and “duplex” settings cannot be controlled properly after upgrading to TIBCO LogLogic LMI 4.8.x

Network Interface “speed” and “duplex” settings cannot be controlled properly after upgrading to TIBCO LogLogic LMI 4.8.x

book

Article ID: KB0076738

calendar_today

Updated On:

Products Versions
TIBCO LogLogic Log Management Intelligence 4.8.0, 4.8.0.1

Description

After upgrading to LogLogic LMI 4.8.0 or 4.8.0.1, network interfaces' speed and duplex settings cannot be managed via the GUI. The interfaces will be set to use auto negotiate only and attempts to change to a manually defined speed or duplex setting will be ignored.

The explanation is that during the upgrade to 4.8.x a network file containing configuration settings for the interfaces is created which did not exist in previous versions. However, the network file is not entirely working in 4.8.x after the upgrade and will not utilize the speed and duplex settings because of improper formatting. When the IP settings are reconfigured for the interface directly 4.8.x rebuilds the network configuration file and then that file is correctly formatted and will accept the speed and duplex settings from that point on.

This is resolved in a future LMI version.

Issue/Introduction

This article provides a workaround for when the network Interface “speed” and “duplex” settings cannot be controlled properly in the web GUI after an upgrade to LMI 4.8.x.

Resolution

A field solution is available to resolve the issue in the appliance allowing the speed and duplex settings to be changed successfully using the CLI until this defect is resolved in a future release.  The field solution requires first resetting the IP settings on the affected interface and then changing the speed duplex settings again afterwards.

 

1. Login as root in a serial or SSH console session (or, run su if already logged in via toor in a shell session).

2.  Use the “set ip” command to reset the IP address to the network interface in use, even though the IP address is already functioning presently.
For example:

> set ip 10.5.1.37 255.255.255.0 10.5.1.1 eth0

 Run save to commit this IP to the interface:
> save

 Answer the prompts that may appear asking whether the interface will be the default gateway for the appliance and whether a Blue Coat certificate should be generated.

3. Now use the same set command with the interface name as an argument to configure the duplex and auto-negotiation settings. You can use article 000005910 for reference.