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 traffic comming and it does not send any traffic via those > redundant paths, basically breaks any potential loop. If the primary link is > down then the switch starts forwarding traffic via the next preferred link. > > If you have a diagram and you turn it upside down, then your upstream > switches now become downstream! Let's think it that way.
Yeah, definitely a perspective thing. > But in case you want to control the loop when you connect with customer, you > want to run RTG on your device! If you trust your customer doing the right > thing then you can have the customer switch to connect to more than one of > your devices, and run RTG on his switch. If he does not configure it properly > then you are open to the loop again. But i remember Jeff stating that the switches in the cabinets itself are managed by him and that the customers are "only" able to connect/disconnect cables on said switch(es) In that case i would configure RTG/flexlink on the cabinet/access switch. In either case if a customers loops (on) his own switch/switches there could be pps storm comming from this switch and you would have to mitigate that with stormcontrol limits or other kind of policers. This should not be different wheter you run rtg on the core or the access layer. If you have to connect "hostile" switches (configured by a customer) than i totally agree with you. regards Tobias _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
