5.x force 100Mbit/Full duplex

[mhellman]

I've configured the management interface of a 5.x 4235 sensor to be 100Mbit/full. It is still HALF duplex according to dmesg output and I am still seeing collisions in proc/net/cisco/ge0_1.info. Does anybody know if setting this via the CLI actually works (you can't set the management interface settings via GUI..only the sensing interface)?

TIA,

Matt

[mhellman]

I found what seems to be a pretty elegant way to do this with 5.x, although whether Cisco supports this is doubtful. I have a ticket open on why the actual "conf t" way does not work, but in the interim here is what I am doing:

The /etc/init.d/ids_functions script sources the file /etc/options.conf. You can enter your options here.

I added the following lines to /etc/options.conf for each type of sensor (YMMV with regards to interface configuration on your sensors):

IDS-4235: E1000_OPTIONS="Speed=0,100 Duplex=0,2"

IDS-4240: E100_OPTIONS="e100_speed_duplex=4,0"

IDS-4250: E1000_OPTIONS="Speed=0,100 Duplex=0,2"

IDS-4250-SX: E1000_OPTIONS="Speed=0,100,0 Duplex=0,2,0"

IDS-4255-K9: E100_OPTIONS="e100_speed_duplex=4,0"

[cjuba]

How do I access this file to change these settings?

[mhellman]

You must get access to the filesystem via a normal shell. Here are the high-level steps...don't forget what I said about support;-)

1) create a user account with the "service" role.

2) login via ssh.

3) su to root

4) vi /etc/options.conf and add entry

5) reboot

[mhellman]

I certainly hope this is my last post regarding this issue, especially given the probable lack of interest by the group. I don't have (and probably won't) the time to figure out why, but in order to force full duplex in 5.0(4) you must do the above AND configure the interface as such using "conf t". Doing either one alone won't get the job done. (The exception seems to be the newer appliances, /etc/options.conf was working fine for those).

Matt

[a.arndt]

Sorry if I'm asking an obvious question, but did you configure the interface on the (I'll assume) switch you connected your sensor to in a likewise fashion?

When ever this happens to us, it's because we didn't configure both ends of the link to the same speed and duplex settings...

I hope this helps,

Alex Arndt

[mhellman]

I didn't have our netadmin group verify, but our standard is 100/Full...no autoneg. Since I was seeing late collisions on the interface, I assumed it was configured as such. The collisions have gone away since changing to 100/Full but you're right, I should verify with our netadmin group.

Matt