Re: In a module A9K-24X10GE-1G-TR, we can not configure a interface in speed 100 or 10

paulo.cabello · ‎06-17-2019

I have router ASR-9010, 6.2.3 IOS-XR version with 3 modules A9K-24X10GE-1G-TR.

Previously we set 12 interfaces in 10G and 12 in 1G(10/100/100)

hw-module location 0/0/CPU0 port-mode 12X10,12X1
hw-module location 0/1/CPU0 port-mode 12X10,12X1
hw-module location 0/2/CPU0 port-mode 12X10,12X1

But now, we can not configure in speed 10 or 100

RP/0/RSP0/CPU0:ROUTER_ASR9010#sh run int Gi0/0/0/12
Mon Jun 17 09:53:38.279 UTC
interface GigabitEthernet0/0/0/12
shutdown
transceiver permit pid all
!

RP/0/RSP0/CPU0:ROUTER_ASR9010#conf t
Mon Jun 17 09:53:40.142 UTC
RP/0/RSP0/CPU0:ROUTER_ASR9010(config)#interface GigabitEthernet0/0/0/12
RP/0/RSP0/CPU0:ROUTER_ASR9010(config-if)#speed 100
RP/0/RSP0/CPU0:ROUTER_ASR9010(config-if)#commit
Mon Jun 17 09:53:50.279 UTC

% Failed to commit one or more configuration items during a pseudo-atomic operation. All changes made have been reverted. Please issue 'show configuration failed [inheritance]' from this session to view the errors
RP/0/RSP0/CPU0:ROUTER_ASR9010(config-if)#exit
RP/0/RSP0/CPU0:ROUTER_ASR9010(config)#sh conf failed
Mon Jun 17 09:53:58.174 UTC
!! SEMANTIC ERRORS: This configuration was rejected by
!! the system due to semantic errors. The individual
!! errors with each failed configuration command can be
!! found below.

interface GigabitEthernet0/0/0/12
speed 100
!!% 'Ether' detected the 'warning' condition 'The configuration is not supported on this interface'
!
end

RP/0/RSP0/CPU0:ROUTER_ASR9010(config)#end

Aleksandar Vidakovic · ‎06-17-2019

Ports on this line card can operate in 10Gbps or 1Gbps mode. Can you please point me to a reference where we claim support for 100Mbps and 10Mbps mode? If there are any, they need to be corrected.

/Aleksandar

paulo.cabello · ‎06-17-2019

Aleksandar

We need to migrate some legacy boxes that work in 10 or 100.
In the configuration mode, these speeds are available

RP/0/RSP0/CPU0:ROUTER_ASR9010(config)#interface GigabitEthernet0/0/0/12
RP/0/RSP0/CPU0:ROUTER_ASR9010(config-if)#speed ?
10 Ethernet is 10Mb
100 Ethernet is 100Mb
1000 Ethernet is 1Gb
RP/0/RSP0/CPU0:ROUTER_ASR9010(config-if)#duplex ?
full Full duplex
half Half duplex
RP/0/RSP0/CPU0:ROUTER_ASR9010(config-if)#end
Uncommitted changes found, commit them before exiting(yes/no/cancel)? [cancel]:no
RP/0/RSP0/CPU0:ROUTER_ASR9010#sh platform
Mon Jun 17 12:26:21.303 UTC
Node Type State Config State
-----------------------------------------------------------------------------
0/RSP0/CPU0 A9K-RSP880-LT-TR(Active) IOS XR RUN PWR,NSHUT,MON
0/RSP1/CPU0 A9K-RSP880-LT-TR(Standby) IOS XR RUN PWR,NSHUT,MON
0/0/CPU0 A9K-24X10GE-1G-TR IOS XR RUN PWR,NSHUT,MON
0/1/CPU0 A9K-24X10GE-1G-TR IOS XR RUN PWR,NSHUT,MON
0/2/CPU0 A9K-24X10GE-1G-TR IOS XR RUN PWR,NSHUT,MON
RP/0/RSP0/CPU0:ROUTER_ASR9010#

paulo.cabello · ‎06-17-2019

Aleksandar

We need to migrate some legacy boxes that work in 10 or 100.
In the configuration mode, these speeds are available

RP/0/RSP0/CPU0:ROUTER_ASR9010(config)#interface GigabitEthernet0/0/0/12
RP/0/RSP0/CPU0:ROUTER_ASR9010(config-if)#speed ?
10 Ethernet is 10Mb
100 Ethernet is 100Mb
1000 Ethernet is 1Gb
RP/0/RSP0/CPU0:ROUTER_ASR9010(config-if)#duplex ?
full Full duplex
half Half duplex
RP/0/RSP0/CPU0:ROUTER_ASR9010(config-if)#end
Uncommitted changes found, commit them before exiting(yes/no/cancel)? [cancel]:no
RP/0/RSP0/CPU0:ROUTER_ASR9010#sh platform
Mon Jun 17 12:26:21.303 UTC
Node Type State Config State
-----------------------------------------------------------------------------
0/RSP0/CPU0 A9K-RSP880-LT-TR(Active) IOS XR RUN PWR,NSHUT,MON
0/RSP1/CPU0 A9K-RSP880-LT-TR(Standby) IOS XR RUN PWR,NSHUT,MON
0/0/CPU0 A9K-24X10GE-1G-TR IOS XR RUN PWR,NSHUT,MON
0/1/CPU0 A9K-24X10GE-1G-TR IOS XR RUN PWR,NSHUT,MON
0/2/CPU0 A9K-24X10GE-1G-TR IOS XR RUN PWR,NSHUT,MON
RP/0/RSP0/CPU0:ROUTER_ASR9010#

Aleksandar Vidakovic · ‎06-17-2019

hi Paulo,

I see where the misunderstanding comes from. It is very difficult to remove commands from the parser chain in function of what the HW supports. At this moment, the best we can do is to check the HW capability when the command is applied. Were you trying this with a copper or optical SFP?

/Aleksandar

paulo.cabello · ‎06-17-2019

Aleksandar
We try with a copper transceiver (RJ45)

NAME: "module mau GigabitEthernet0/0/CPU0/12", DESCR: "Unknown pluggable optics"
PID: N/A, VID: N/A, SN: MTC1724092K

RP/0/RSP0/CPU0:ROUTER_ASR9010#sh controllers gigabitEthernet 0/0/0/12 all
Mon Jun 17 14:54:38.063 UTC
Operational data for interface GigabitEthernet0/0/0/12:

State:
Administrative state: disabled
Operational state: Down (Reason: Initializing, true state not yet known)
LED state: Off

Phy:
Media type: Four-pair Category 5 UTP PHY, full duplex
Optics:
Vendor: CISCO-METHODE
Part number: SP7041-E
Serial number: MTC1724092K
Wavelength: 0 nm
Digital Optical Monitoring:
Transceiver Temp: 31.000 C
Transceiver Voltage: 3.320 V

Christian

Aleksandar Vidakovic · ‎06-18-2019

That SFP is ok to use for 10/100/1000Mbps, but the controller on this line card apparently doesn't support 10/100Mbps. Have you considered cheaper options for connecting legacy gear? An NV satellite would be a much cheaper option, while you would still keep the look and feel of configuring all interfaces directly on asr9k. Alternatively, if you have a A9K-MOD line card the A9K-MPA-20X1GE supports 100Mbps.

paulo.cabello · ‎06-21-2019

Aleksandar

Thanks for your reply.

Sad but true, this linecard not support speed 10 or 100. We opened a case with the TAC and they confirmed this diagnosis

:(

Christian

@Aleksandar Vidakovic wrote:
That SFP is ok to use for 10/100/1000Mbps, but the controller on this line card apparently doesn't support 10/100Mbps. Have you considered cheaper options for connecting legacy gear? An NV satellite would be a much cheaper option, while you would still keep the look and feel of configuring all interfaces directly on asr9k. Alternatively, if you have a A9K-MOD line card the A9K-MPA-20X1GE supports 100Mbps.

Aleksandar Vidakovic · ‎06-17-2019

hi Paulo,

I see where the misunderstanding comes from. It is very difficult to remove commands from the parser chain in function of what the HW supports. At this moment, the best we can do is to check the HW capability when the command is applied. Were you trying this with a copper or optical SFP?

/Aleksandar