1 Rookie

 • 

10 Posts

July 24th, 2018 03:00

Hello Daniel,

thanks for your fruitful answer.

The KB article on setup is exactly the one I had previously read, but, as you can see, it does not answer all my questions, to which satisfaction you have provided me interesting input.

As I got it, there is no particular order of the tengigabit ports for the cables, provided the resulting topology is a ring. Right?

Also, if I have correctly understood, the N1548 will become a mere extension of the N1524 and, therefore, will sport no IP or whatsoever.

What I haven't understood is what happens to the slave switch, should the master one die. You wrote that it detaches from the stack, which is obvious. There are still unsatisfied questions:

1. Does this imply that it will have a wiped away config? Or will it still have some?

2. Will it then have an IP? Or just serial console access? Or neither? If neither, will it need to be reset?

Btw, LAG would be a fine and elegant idea, the problem is that the uplink device is a Peplink 30 load balancer, and this model does not support LAG on LAN ports.

3. is there a way, apart from LAG, to map a port on slave switch just like an existing one on the master one which activates just in case of death of master switch, as a fallback? In that case bringing connectivity back would be as easy as moving one cable e.g. from port 1/0/1 to port 2/0/1.

Thanks!

Pasha

1 Rookie

 • 

10 Posts

July 26th, 2018 01:00

Thank you for your interesting answer!

Actually I have zero experience with STP, so my question is: should it be supported even on the Peplink or does it suffice to have it on the switches? This, because, of course, the peplink doesn't support it too.

In case the two switches would suffice, how would you configure the two ports on them?

Thanks

Pasha

1 Rookie

 • 

10 Posts

July 27th, 2018 03:00

Thanks,

I had already went though that man page, and not only the STP is only within a VPN WAN only scope, but, in any case, available only on higher models and not on Peplink 30.

But I think you gave me the right clue about ip policy route-map, looks like we're on the right path to make things work! Now, the vlan that talks with uplink is vlan 255 over a single port on N1524. When the N1548 will be stacked, besides allocating another port to vlan 255 on it, should I set the "ip policy route-map" over just the vlan or specifying ports or what?

Could you make a syntax example for this situation? Say ports are current 1/0/1 and future 2/0/1.

Thank you very much :)

Pasha

1 Rookie

 • 

10 Posts

July 31st, 2018 08:00

Thank you, I will use this approach.

Have a nice day!

No Events found!

Top