Interface Speed and Duplex after upgrade.

Hi All,

I have recently upgraded our 3030S from 2.7.2P6 to 4.0.1. I followed the upgrade procedure in the release documentation including parsing the backup through the python migration script.

I encountered many issue when I rebooted and the applied the restoration of the config from the script. one of which is that I can no longer set the speed/duplex on an interface.

Below is the config of an interface prior to the upgrade:
interface ethernet 1
speed 1000
duplexity Full
lldp enable rx tx
lldp notification enable
lldp tx-dot1-tlvs vlan link-aggregation
lacp trunk 2 mode active

after the upgrade the config was as below:
interface ethernet 1
enable
lldp enable rx tx
lldp notification enable
lldp tx-dot1-tlvs link-aggregation vlan
trunk-group 2 lacp

when I try changing the speed or duplex I get the following message:
device1(config-if:ethernet:1)#speed 1000
Can not set the interface speed.
device1(config-if:ethernet:1)#duplexity full
Can not set the interface duplexity.

I have tried stripping out all of the config from the interface and shutting the interface down. Still can't set the speed duplex.

I have also tried other interfaces on the device and it is the same result.

Any ideas?

Comments

  • dshindshin Member
    edited November 2015
    Hi rwilliams,

    This is a known problem in 4.0.1 in the non-FPGA devices. When using a 1GB copper SFP adapter, the port renders to be unusable. We have a fix for the problem and I suggest that you contact A10 support to get your problem resolved.

    The bug id is 190318.

    Genard
  • rwilliamsrwilliams Member
    edited November 2015
    Hi Genard,

    the build for the upgrade was as follows:

    version 4.0.1, build 214

    With regards to you comment, I am seeing this issue on the built 1GB Ethernet ports on the 3030S. I am not currently using any SFP modules or ports. Would the bug id 190318 also cover the normal RJ45 ports on the device?

    Ryan
  • rwilliamsrwilliams Member
    edited November 2015
    So an update on this.

    This has been confirmed as a bug (id 264334) and I am currently waiting on a fix.

    Regards

    Ryan
  • rwilliamsrwilliams Member
    edited January 2016
    Further Update.

    Bug (id264334) will be fixed in the next OS code 4.1 which is estimated for release for 31/3/2016

    Regards

    Ryan
Sign In or Register to comment.