On 11/Nov/16 00:44, Clarke Morledge wrote:
>
> Right now, we do employ redundant routing engines (1300s and 1800s),
> but mostly with ISSU in mind. The failure rate for routing engines,
> even with the older hard disk models, has been rather low, in our
> experience. So, the primary benefit has
I would like revisit a previous thread here:
http://www.gossamer-threads.com/lists/nsp/juniper/58555
With the new RE-S-X6-64G routing engine, is part of the goal here to
provide a method to eliminate the need for a redundant routing engine in
the MX?
Right now, we do employ redundant routing
Sure, you could mitigate some of that with enforcing w/ever at the
boundaries, but hopefully you are starting to see how a simple QoS policy
design on a single node is blowing up into managing hundreds/thousands of
ports and making sure you trust your VoIP telephone, but not the
workstation behind
Thanks Andrey, you mentioned ... "You could end up in a DoS situation
where some rouge source send 1gbps worth of packets matching your priority
class"
Is this where a properly controlled QoS Trust Boundary comes into
play?...like not trusting what ingresses that boundary, classifying and
remark
Thanks for the sample. I will give it a try.
> On Nov 10, 2016, at 9:26 AM, Dan White wrote:
>
> On 11/10/16 08:55 -0600, kwor...@gmail.com wrote:
>> Hi, I’m trying to get rid of an old Redback SMS device in our network and
>> I would like to replicate it’s functionality on an MX. We have some
On 11/10/16 08:55 -0600, kwor...@gmail.com wrote:
Hi, I’m trying to get rid of an old Redback SMS device in our network and
I would like to replicate it’s functionality on an MX. We have some
legacy subscribers that come in via Ethernet in the SVLAN model, i.e. an
outer tag that identifies the M
Hi, I’m trying to get rid of an old Redback SMS device in our network and I
would like to replicate it’s functionality on an MX. We have some legacy
subscribers that come in via Ethernet in the SVLAN model, i.e. an outer tag
that identifies the MSAN and then an inner tag for each subscriber. C
Hello,
Yes, site range set to 100, but I'm planning to remove it, as default is 64K.
Best regards,
Misak Khachatryan,
Network Administration and
Monitoring Department Manager,
GNC- ALFA CJSC
1 Khaghaghutyan str., Abovyan, 2201 Armenia
Tel: +374 60 46 99 70 (9670),
Mob.: +374 55 19 98 40
URL:
Small correction:
After more thorough examination site 5 seems not working, instead site
17. So it seems site ID's 1-15 not working, like first label block.
Best regards,
Misak Khachatryan,
Network Administration and
Monitoring Department Manager,
GNC- ALFA CJSC
1 Khaghaghutyan str., Abovyan, 22
Hello,
we have MPLS network solely built on Juniper MX routers. We have 2
route reflectors, 16 PE routers, and of course lot of VPLS configured.
Recently we decided to try Mikrotik for some non critical and low
bandwidth sites. Statically configured VPLS connected to Juniper VPLS
via mesh groups w
10 matches
Mail list logo
