Hi,
Am 31.01.2013 10:47, schrieb Huan Pham:
> Upstream or Downstream is from your perspective. RTG does not run between
> devices, so it does not care if the redundant paths are connected to upstream
> or downstream!! All it cares is that if the primary link is up, the the SW
> blocks all traff
Hi Tobias,
Upstream or Downstream is from your perspective. RTG does not run between
devices, so it does not care if the redundant paths are connected to upstream
or downstream!! All it cares is that if the primary link is up, the the SW
blocks all traffic comming and it does not send any traff
Hi,
Am 31.01.2013 03:06, schrieb Huan Pham:
> The simplest solution is redundant trunk group (RTG). Pls check if your
> switches facing customer support it.
>
> On Cisco, i think you can use "interface backup" command to do the same.
>
> The down side with these solutions is customers have to
Hi Jeff,
> The question is now how to proceed and how to improve the setup generally?
>From what you've described, it sounds like there is a misconfiguration or bug
>*somewhere* amongst your 3 vendors. As painful as it will probably be to
>locate, that is probably the best place to start.
-
Hi
Without going into your details, I think the fundamental issue here is you rely
on customer to do the right thing: RSTP or MSTP. In this case, You need to
allow customer to take part into your spanning tree domain. If they
miss-configure it, then you've got a loop!
Changing from RSTP to MST
Hello list,
I'm currently a little stuck and might need some help in order to decide
how to improve the current setup. We are running a network where all
customer vlans are bridged because the same Vlan is usually required in
different areas in the network. This is the setup:
Room A:
6 matches
Mail list logo