Thanks Penney! as a workaround i changed the interface name to fit in the allowed length. But did not understand the logic of restricting the length up to 10 characters, when kernel can support up to 15 characters for an interface name. 

Thanks,
Ankush
From: Penney, Don <Don.Penney@windriver.com>
Sent: 27 August 2020 19:14
To: Rai, Ankush <Ankush.Rai@commscope.com>; starlingx-discuss@lists.starlingx.io <starlingx-discuss@lists.starlingx.io>
Subject: RE: [Starlingx-discuss] Is there any workaround to use interface name of length more than 10?
 

I think the interface name length is set to 10 characters to allow for VLAN support, where the resulting name would be an interface with name INTF.VLAN (with VLAN up to 4 digits), and the max length allowed by the kernel is 15 characters.

 

From: Rai, Ankush <Ankush.Rai@commscope.com>
Sent: Wednesday, August 26, 2020 2:25 PM
To: starlingx-discuss@lists.starlingx.io
Subject: [Starlingx-discuss] Is there any workaround to use interface name of length more than 10?

 

Hi,

 

I am trying to bring up All-In-One-Duplex deployment.  And as part of controller-1 configuration, setting OAM interface name of length 11 is failing.

 

> OAM_IF=enp59s0f1d1

> system host-if-modify controller-1 $OAM_IF -c platform

> Interface enp59s0f1d1 has name length greater than 10.

 

Thanks,
Ankush