> -Original Message-
> From: juniper-nsp [mailto:juniper-nsp-boun...@puck.nether.net] On Behalf
> Of Saku Ytti
> Sent: Wednesday, August 14, 2013 12:34 PM
> To: juniper-nsp@puck.nether.net
> Subject: Re: [j-nsp] Mixed Cisco/Juniper MPLS network
>
> I'd only use separate blocks if I specifi
On (2013-08-14 12:22 -0400), Eric Van Tol wrote:
> I've not been able to reproduce it in the lab, but traffic to destinations
> that are on non-MPLS devices have "problems". Customers report slow
> bandwidth and/or page timeouts. I thought perhaps an MTU issue, but physical
> interface MTUs n
> -Original Message-
> From: juniper-nsp [mailto:juniper-nsp-boun...@puck.nether.net] On Behalf
> Of Saku Ytti
> Sent: Wednesday, August 14, 2013 11:49 AM
> To: juniper-nsp@puck.nether.net
> Subject: Re: [j-nsp] Mixed Cisco/Juniper MPLS network
> What is the issue if you allow non-MPLS devi
use a separate range and keep your network clean
On 2013-08-14 8:37 AM, Eric Van Tol wrote:
Hi all,
We've had MPLS running on our network for years using JUNOS and until only very
recently, we haven't had to deal with any of our Cisco equipment needing MPLS.
That changed when we started purch
In my experience, I have seen used the knob to only allocate labels for host
routes or use a prefix-list match that covers ALL your nodes loopback addresses
so that the prefix-list does not have to be constantly touched.
router# configure terminal
router(config)# mpls ldp label
router(config-l
On (2013-08-14 11:37 -0400), Eric Van Tol wrote:
> Is this the normal way of doing things, or is there something I am missing?
> I suppose we could assign a certain range of addresses out of our loopback
> subnet to be used solely for non-MPLS devices, but what happens when one day
> we need t
Hi all,
We've had MPLS running on our network for years using JUNOS and until only very
recently, we haven't had to deal with any of our Cisco equipment needing MPLS.
That changed when we started purchasing ME3600X switches so we could provide
VPN services in our metro fiber rings.
I'm trying
Hi Mathias,
We have experience something quite similar with out MX480 BRAS as well. Can
remember what version of Junos we were running but it was the "X" track
specifically for the subscriber management features instead of the "R" track.
It was a 3rd party copper SFP as well.
Regards
thong
8 matches
Mail list logo