Solved

Adding a new node to stack do not replicate configuration ports to new ports added

  • 22 September 2020
  • 5 replies
  • 66 views

Hello

First of all, my apologies if this question has been solved before.

When we test adding a new node to X440G2 stack I realize that the new ports added are no configured properly based on our custom configuration.

Is there any way to extend the settings automatically to all new ports?

 

Thanks in advance

icon

Best answer by Miguel-Angel RODRIGUEZ-GARCIA 28 September 2020, 18:43

Pionio,

 

It is functioning as designed.

The switch is not supposed to guess what config we want when we add a new node.

If you replace a unit by another one you can transfer the config but for an new added one one you’ll have to do it manually.

Mig

 

View original

5 replies

Userlevel 4

Which port-configuration do you mean? How should the stack know how to configure the new switch ports?

Best regards
Stefan

Hello Stefan

 

Custom configuration ports:

 

configure port 1:1 rate-limit flood broadcast 200
configure port 1:1 rate-limit flood multicast 200

...

enable netlogin ports 1:1-46 mac
configure netlogin ports 1:1 mode mac-based-vlans

If I add a new node stack, the new ports added have default config and custom config will be applied manually.

 

Best regards

Userlevel 6
Badge +1

Pionio,

 

It is functioning as designed.

The switch is not supposed to guess what config we want when we add a new node.

If you replace a unit by another one you can transfer the config but for an new added one one you’ll have to do it manually.

Mig

 

Two Stacks i can see ports 1:48 to 4:48 on stack one & ports 1:48 to 3:48 on stack 2

have been advised not to make a single stack how do i link them so i can see all ports across from a single console connection ie add all ports from single vLan

They currently linked with the default Vlan and passing data between the two stacks i just can see the ports without two connection ..Thanks

Userlevel 6
Badge +1

Peter,

Two stacks mean two stacks and one single console means one single console.

As one stack has one console connection you cann’t manage both from the same connection (console/SSH).

I wouldn’t put 150+200 ports on one single VLAN.

The golden rule written in fiery letters in the sky is: “remove all ports from the Default VLAN(1)”

Mig

Reply