# Interface Speed and Duplex after upgrade.

**URL:** <https://community.a10networks.com/t/interface-speed-and-duplex-after-upgrade/347>\
**Category:** ADC - Application Delivery\
**Tags:** interface\
**Created:** [November 12, 2015, 5:26pm UTC](https://community.a10networks.com/t/interface-speed-and-duplex-after-upgrade/347 "2015-11-12T17:26:43Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![rwilliams](https://avatars.discourse-cdn.com/v4/letter/r/74df32/32.png) [@rwilliams](https://community.a10networks.com/u/rwilliams)\
**Post date:** [November 12, 2015, 5:26pm UTC](https://community.a10networks.com/t/interface-speed-and-duplex-after-upgrade/347/1 "2015-11-12T17:26:43Z")

</div>

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  
&nbsp;&nbsp;enable  
&nbsp;&nbsp;lldp enable rx tx  
&nbsp;&nbsp;lldp notification enable  
&nbsp;&nbsp;lldp tx-dot1-tlvs link-aggregation vlan  
&nbsp;&nbsp;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?

---

<div class="post-metadata">

**Author:** ![dshin](https://avatars.discourse-cdn.com/v4/letter/d/f05b48/32.png) [@dshin](https://community.a10networks.com/u/dshin)\
**Post date:** [November 12, 2015, 6:01pm UTC](https://community.a10networks.com/t/interface-speed-and-duplex-after-upgrade/347/2 "2015-11-12T18:01:33Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![rwilliams](https://avatars.discourse-cdn.com/v4/letter/r/74df32/32.png) [@rwilliams](https://community.a10networks.com/u/rwilliams)\
**Post date:** [November 13, 2015, 8:57am UTC](https://community.a10networks.com/t/interface-speed-and-duplex-after-upgrade/347/3 "2015-11-13T08:57:52Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![rwilliams](https://avatars.discourse-cdn.com/v4/letter/r/74df32/32.png) [@rwilliams](https://community.a10networks.com/u/rwilliams)\
**Post date:** [November 30, 2015, 3:28pm UTC](https://community.a10networks.com/t/interface-speed-and-duplex-after-upgrade/347/4 "2015-11-30T15:28:16Z")

</div>

So an update on this.

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

Regards

Ryan

---

<div class="post-metadata">

**Author:** ![rwilliams](https://avatars.discourse-cdn.com/v4/letter/r/74df32/32.png) [@rwilliams](https://community.a10networks.com/u/rwilliams)\
**Post date:** [January 21, 2016, 12:59pm UTC](https://community.a10networks.com/t/interface-speed-and-duplex-after-upgrade/347/5 "2016-01-21T12:59:07Z")

</div>

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
