Nexus 9932PQ - Breakout configuration

AndiBuchmann157 · ‎11-08-2018

Hi Team,

i got a question regarding the (re-) configuration of the breakout module on Nexus 9932PQ.

In the environment are running two Nexus 9932PQ as a core switch. The two devices are connected via 2x40Gig.

First of all we have (big) maintenance window, so there is now time pressure while doing this. Interfaces 1-8 are configured as Breakoutports with the command "interface breakout module 1 port 1-8 map 10g-4x".

We need one those interfaces as a native 40G interface, which basically means we need to convert one port, for example, port 8 back to 40G.

Now my question:

Can i simply to this by entering: "no interface breakout module 1 port 8 map 10g-4x" or is it necessary to remove the configuration of the complete module with by entering " "no interface breakout module 1 port 1-8 map 10g-4x"

I know that i need to power off and power on the module (and copy run start) after removing the config of the breakout-ports.

Thanks in advance!
Andreas

mojafri · ‎11-08-2018

Hi @AndiBuchmann157,

Command "no interface breakout module 1 port 8 map 10g-4x" will work perfectly fine. You don't have to remove the whole breakout config. It will only affect port-8, moreover in runn-conf you will see "8" getting removed.

Something like this in below eg.:

N9K-C9332PQ-1(config)# sh run | sec break
interface breakout module 1 port 6,8-12 map 10g-4x
N9K-C9332PQ-1(config)# no interface breakout module 1 port 9 map 10g-4x
N9K-C9332PQ-1(config)# sh run | sec break
interface breakout module 1 port 6,8,10-12 map 10g-4x

Please rate if you find it helpful.

Regards,

MJ

AndiBuchmann157 · ‎11-08-2018

Thank you!
So after entered the command i gave in my first post / you mentioned i still will see later:

Eth1/1/1-4

Eth1/2/1-4

Eth1/3/1-4

...

Eth1/7/1-4

and starting then Eth1/8, Eth1/9, Eth1/10 and so on, right?

--> Which means my Eth1/8 will just work as a native 40G Interface beginning from this point.

Another question:

Why exactly are the most right six ports (Eth1/27 - 32) of the 9332PQ marked yellow? I checked the following output (Eth1/26):

Core-xyz# show int eth1/26  capabilities
Ethernet1/26
  Model:                 N9K-C9332PQ
  Type (SFP capable):    unknown
  Speed:                 40000
  Duplex:                full
  Trunk encap. type:     802.1Q
  Channel:               yes
  Broadcast suppression: percentage(0-100)
  Flowcontrol:           rx-(off/on),tx-(off/on)
  Rate mode:             dedicated
  Port mode:             Routed,Switched
  QOS scheduling:        rx-(none),tx-(4q)
  CoS rewrite:           yes
  ToS rewrite:           yes
  SPAN:                  yes
  UDLD:                  yes
  MDIX:                  no
  TDR capable:           no
  Link Debounce:         yes
  Link Debounce Time:    yes
  FEX Fabric:            yes
  dot1Q-tunnel mode:     yes
  Pvlan Trunk capable:   yes
  Port Group Members:    none
  EEE (efficient-eth):   no
  PFC capable:           yes
  Buffer Boost capable:  yes
  Speed group capable:   yes
  Breakout capable:      yes

compared to Eth1/27 (marked yellow):

Core-xyz# show int eth1/27  capabilities
Ethernet1/27
  Model:                 N9K-C9332PQ
  Type (SFP capable):    QSFP-H40G-ACU10M
  Speed:                 10000,40000
  Duplex:                full
  Trunk encap. type:     802.1Q
  Channel:               yes
  Broadcast suppression: percentage(0-100)
  Flowcontrol:           rx-(off/on),tx-(off/on)
  Rate mode:             dedicated
  Port mode:             Routed,Switched
  QOS scheduling:        rx-(none),tx-(4q)
  CoS rewrite:           yes
  ToS rewrite:           yes
  SPAN:                  yes
  UDLD:                  yes
  MDIX:                  no
  TDR capable:           no
  Link Debounce:         yes
  Link Debounce Time:    yes
  FEX Fabric:            no
  dot1Q-tunnel mode:     yes
  Pvlan Trunk capable:   yes
  Port Group Members:    105-128
  EEE (efficient-eth):   no
  PFC capable:           yes
  Buffer Boost capable:  no
  Speed group capable:   yes
  Breakout capable:      no

From the output above i see that those ports are not capable of connecting a FEX or Breakoutcables - what are the other major differences i need to know right there?

Thanks.

mojafri · ‎11-08-2018

--> Which means my Eth1/8 will just work as a native 40G Interface beginning from this point.

Yes

--> Why exactly are the most right six ports (Eth1/27 - 32) of the 9332PQ marked yellow?

Those are called uplink port- does vxlan routing. Also called ALE port- more can be found here: https://www.cisco.com/c/en/us/products/collateral/switches/nexus-9000-series-switches/white-paper-c11-732452.html

--> From the output above i see that those ports are not capable of connecting a FEX or Breakoutcables - what are the other major differences i need to know right there?

https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/ale_ports/b_Limitations_for_ALE_Uplink_Ports_on_Cisco_Nexus_9000_Series_Switches.html

Don't forget to mark answers as correct if it solves your problem. This helps others find the correct answer if they search for the same problem

Regards,

MJ