02-08-2022 04:00 PM
Hi All,
I had a few questions regarding setting negotiation to auto.
I currently have setup a HundredGigE on one of the port, and this is what it looks like -
ladjfcisco5011#show interfaces HundredGigE 0/0/0/21
Tue Feb 8 23:32:06.777 UTC
HundredGigE0/0/0/21 is down, line protocol is down
Interface state transitions: 0
Hardware is HundredGigE, address is 6c8b.d339.4f5a (bia 6c8b.d339.4f5a)
Internet address is Unknown
MTU 1514 bytes, BW 100000000 Kbit (Max: 100000000 Kbit)
reliability 255/255, txload 0/255, rxload 0/255
Encapsulation ARPA,
Full-duplex, 100000Mb/s, link type is force-up
output flow control is off, input flow control is off
Carrier delay (up) is 10 msec
loopback not set,
Last input never, output never
Last clearing of "show interface" counters never
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 total input drops
0 drops for unrecognized upper-level protocol
Received 0 broadcast packets, 0 multicast packets
0 runts, 0 giants, 0 throttles, 0 parity
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 packets output, 0 bytes, 0 total output drops
Output 0 broadcast packets, 0 multicast packets
0 output errors, 0 underruns, 0 applique, 0 resets
0 output buffer failures, 0 output buffers swapped out
0 carrier transitions
From above, my understanding is that "link type is force-up" means autonegotiation is turned off and this is "forced" mode.
To change this, I tried to change it to `negotiation auto` and when I hit commit, it won't let me commit, and gives the following warning -
ladjfcisco5011(config-if)#commit
Tue Feb 8 22:38:41.709 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/RP0/CPU0:ladjfcisco5011(config-if)#
RP/0/RP0/CPU0:ladjfcisco5011(config-if)#
RP/0/RP0/CPU0:ladjfcisco5011(config-if)#show configuration failed
Tue Feb 8 22:38:47.073 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 HundredGigE0/0/0/21
negotiation auto
!!% 'GIRO' detected the 'warning' condition 'The configuration is not supported on this interface'
!
end
Is there another way to set negotiation to true?
02-08-2022 04:30 PM
Hi
Auto is only supported on Giga, according to this doc:
"The negotiation auto command is available on Gigabit Ethernet interfaces only. "
can you share a 'show run int HundredGigE 0/0/0/21'
02-08-2022 04:46 PM
Appreciate the prompt reply.
Here's what I get after running the commands -
RP/0/RP0/CPU0:ladjfcisco5011#conf terminal
Wed Feb 9 00:12:53.088 UTC
RP/0/RP0/CPU0:ladjfcisco5011(config)#show run int HundredGigE 0/0/0/21
Wed Feb 9 00:13:05.222 UTC
interface HundredGigE0/0/0/21
fec standard
!
Now, I saw in the link as well, "The negotiation auto command is available on Gigabit Ethernet interfaces only". But in examples, it tries to enable auto negotiation for a port enabled for HundredGigE. (Hence the confusion)
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide