Single router for P/PE functions
Hello, I'm pretty confident that a router can be used to perform P & PE functions simultaneously. What about from a best practice perspective? Is this something that should be completely avoided? Why? We're considering doing this as a temporary workaround but we all know temporary usually lasts a long time. I'd like to know what kind of mess awaits if we let this one go. Thanks, Serge __________________________________________________________________ Yahoo! Canada Toolbar: Search from anywhere on the web, and bookmark your favourite sites. Download it now http://ca.toolbar.yahoo.com.
Kinda depends on what you're doing exactly, but like Erik said, it certainly possible and depending on your particular needs, it might not be much of an issue at all. Can you describe your scenario a bit more? --WM On Thu, Sep 3, 2009 at 10:20 AM, Serge Vautour <sergevautour@yahoo.ca>wrote:
Hello,
I'm pretty confident that a router can be used to perform P & PE functions simultaneously. What about from a best practice perspective? Is this something that should be completely avoided? Why? We're considering doing this as a temporary workaround but we all know temporary usually lasts a long time. I'd like to know what kind of mess awaits if we let this one go.
Thanks, Serge
__________________________________________________________________ Yahoo! Canada Toolbar: Search from anywhere on the web, and bookmark your favourite sites. Download it now http://ca.toolbar.yahoo.com.
-- William McCall, CCIE #25044
We're trying to save on Transport links. Instead of multi-homing each PE to 2 Ps, we're considering building a ring: P-PE-PE-PE-P. This ring follows the transport ring. Each link would be engineering to make sure it can handle all of the traffic from all 3PEs in case of a failure. As the network grows, we could get individual transport links from PE-P. Apart from bandwidth, I was curious if there were other problems I related to doing this that I wasn't thinking of. Thanks for all the replies. Much appreciated. Serge ________________________________ From: William McCall <william.mccall@gmail.com> To: Serge Vautour <serge@nbnet.nb.ca> Cc: nanog@nanog.org Sent: Friday, September 4, 2009 1:07:40 AM Subject: Re: Single router for P/PE functions Kinda depends on what you're doing exactly, but like Erik said, it certainly possible and depending on your particular needs, it might not be much of an issue at all. Can you describe your scenario a bit more? --WM On Thu, Sep 3, 2009 at 10:20 AM, Serge Vautour <sergevautour@yahoo.ca> wrote:
Hello,
I'm pretty confident that a router can be used to perform P & PE functions simultaneously. What about from a best practice perspective? Is this something that should be completely avoided? Why? We're considering doing this as a temporary workaround but we all know temporary usually lasts a long time. I'd like to know what kind of mess awaits if we let this one go.
Thanks, Serge
__________________________________________________________________ Yahoo! Canada Toolbar: Search from anywhere on the web, and bookmark your favourite sites. Download it now
-- William McCall, CCIE #25044 __________________________________________________________________ Ask a question on any topic and get answers from real people. Go to Yahoo! Answers and share what you know at http://ca.answers.yahoo.com
What if there is a problem from software, filter, mis-configuration from one of the routers ? It will affect whole ring network, not just that problem router. Also if there is routing protocol bounce because of link flapping, it will be propagate through the ring forever. Alex Serge Vautour wrote:
We're trying to save on Transport links. Instead of multi-homing each PE to 2 Ps, we're considering building a ring: P-PE-PE-PE-P. This ring follows the transport ring. Each link would be engineering to make sure it can handle all of the traffic from all 3PEs in case of a failure. As the network grows, we could get individual transport links from PE-P.
Apart from bandwidth, I was curious if there were other problems I related to doing this that I wasn't thinking of. Thanks for all the replies. Much appreciated.
Serge
________________________________ From: William McCall <william.mccall@gmail.com> To: Serge Vautour <serge@nbnet.nb.ca> Cc: nanog@nanog.org Sent: Friday, September 4, 2009 1:07:40 AM Subject: Re: Single router for P/PE functions
Kinda depends on what you're doing exactly, but like Erik said, it certainly possible and depending on your particular needs, it might not be much of an issue at all.
Can you describe your scenario a bit more?
--WM
On Thu, Sep 3, 2009 at 10:20 AM, Serge Vautour <sergevautour@yahoo.ca> wrote:
Hello,
I'm pretty confident that a router can be used to perform P & PE functions simultaneously. What about from a best practice perspective? Is this something that should be completely avoided? Why? We're considering doing this as a temporary workaround but we all know temporary usually lasts a long time. I'd like to know what kind of mess awaits if we let this one go.
Thanks,
Serge
__________________________________________________________________ Yahoo! Canada Toolbar: Search from anywhere on the web, and bookmark your favourite sites. Download it now
On Thu, 3 Sep 2009, Serge Vautour wrote:
I'm pretty confident that a router can be used to perform P & PE functions simultaneously. What about from a best practice perspective? Is this something that should be completely avoided? Why? We're considering doing this as a temporary workaround but we all know temporary usually lasts a long time. I'd like to know what kind of mess awaits if we let this one go.
Collapsing P/PE functions certainly saves CAPEX, the downside is that you might need to reload your PE (affecting customers) due to a core feature upgrade or bug fix, or the other way around. With separate P and PE functions and PEs being dual attached to two Ps, you can reboot P layer with minimal end customer impact. I'd imagine that in smaller networks it makes more sense to collapse compared to larger network, because a smaller network has fewer customers to be affected by each router problem. It's basically "put all the eggs in one basket" kind of issue, it's easier to carry around but you lose more when something happens. -- Mikael Abrahamsson email: swmike@swm.pp.se
participants (4)
-
Alex H. Ryu -
Mikael Abrahamsson -
Serge Vautour -
William McCall