cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
33863
Views
16
Helpful
7
Replies

command failed: port not compatible [port mode] On Nexus 93K

CiscoPurpleBelt
Level 6
Level 6

Attemtping to put a port-channel into ports eth1/51-52 on a Nexus 93180 but receive the stated error.

I have tried numerous things and can't see to find out what is wrong. Any ideas?

1 Accepted Solution

Accepted Solutions

ashfaq82
Level 1
Level 1

Bug ID : CSCvn01573 


Switch# interface port-channel 10

Switch(config-if)# no switchport
Switch(config-if)# ip address 1.1.1.1/31

(config-if)#exit
Switch# interface Ethernet1/10

Switch(config-if)#   no switchport

Switch(config-if)#   logging event port link-status

Switch(config-if)#   channel-group 10 mode active

command failed: port not compatible [Duplex Mode]


Solution/work around.... config the all physical member interfaces first and then at the end configure the port channel. Use below as a reference.


Switch# interface Ethernet1/10

Switch(config-if)#   no switchport

Switch(config-if)#   logging event port link-status

Switch(config-if)#   channel-group 10 mode active

(config-if)#exit

Switch# interface port-channel 10

Switch(config-if)# no switchport
Switch(config-if)# ip address 1.1.1.1/31

View solution in original post

7 Replies 7

balaji.bandi
Hall of Fame
Hall of Fame

Paste the config here  :

 

try adding command  : 

switchport trunk allowed vlan xxx ( xxx where your vlan number)
config t 

interface eth1/51

 switchport mode trunk

switchport trunk allowed vlan xxx

channel-group yyy mode active

add other config

 

 

 

BB

***** Rate All Helpful Responses *****

How to Ask The Cisco Community for Help

Hello,

 

in addition to the other post, check the hardware and software restrictions mentioned below for 100G ports:

 

• Port-channels are not supported on generation 1 100G line cards (N9K-X9408PC-CFP2) or generic
expansion modules (N9K-M4PC-CFP2).
• Port-channels are supported on devices with generation 2 (and later) 100G interfaces. (7.0(3)I3(1) and
later)

Ok let me look and get back to you.
Different question, so let's say I have 2x 9k nexus as core in vpc domain, and 2 pairs of 93k in vpc domains as access layer - so dual sided vpc topolgy. Should you track core links under vpc configs on access switches, then on core switches track edge router/out bound device links under vpc config? See attached doc for similar topology.
http://www.cisco.com/c/en/us/support/docs/switches/nexus-7000-series-switches/200996-vPC-Object-Tracking.html#anc3

gavincreach
Level 1
Level 1
I am seeing this as well on 93108 nexus. I have other ports using vpc fine, only on the vpc peer link do I see this issue.

Hello,

 

I seem to recall that you have to disable the port channel interface before adding a new member interface...

ashfaq82
Level 1
Level 1

Bug ID : CSCvn01573 


Switch# interface port-channel 10

Switch(config-if)# no switchport
Switch(config-if)# ip address 1.1.1.1/31

(config-if)#exit
Switch# interface Ethernet1/10

Switch(config-if)#   no switchport

Switch(config-if)#   logging event port link-status

Switch(config-if)#   channel-group 10 mode active

command failed: port not compatible [Duplex Mode]


Solution/work around.... config the all physical member interfaces first and then at the end configure the port channel. Use below as a reference.


Switch# interface Ethernet1/10

Switch(config-if)#   no switchport

Switch(config-if)#   logging event port link-status

Switch(config-if)#   channel-group 10 mode active

(config-if)#exit

Switch# interface port-channel 10

Switch(config-if)# no switchport
Switch(config-if)# ip address 1.1.1.1/31

Pretty old I figured it out long time ago but thanks

Review Cisco Networking products for a $25 gift card