On 11/7/11 17:58 , Jared Mauch wrote:
Juniper doesn't believe security bugs should be public. You must be a
customer with support to access their portal.
Cisco has a good policy. You can view any security bugs and get fixes
regardless of your contract status.
In either case there are a
Hello experts
is there anyway to get syslog message when VPLS VC is up?
now i can see VC down message only.
thanks
*Soongoon Lee** /** CCIE #17724*
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
Hello Experts,
During the configuration for vlan and vlan l3-interfaces we observed
error: device vlan not found.
Following is configuration which i did on MX80 (11.2R3):
interfaces {
ge-0/0/0 {
unit 0 {
family bridge {
interface-mode access;
arent you missing the interface in your bridge-domain ?
On 11 November 2011 11:46, saurabh sood saurabh...@gmail.com wrote:
Hello Experts,
During the configuration for vlan and vlan l3-interfaces we observed
error: device vlan not found.
Following is configuration which i did on MX80
When using the new-style MX L2 commands, the bridge-domains do not require
you to add the interface.
However you need to use the bridge-domains knob routing-interface to
point to the irb interface.
Also on the MX you need to create interface irb.601 and not vlan.601
Thank you,
--
Doug Hanks -
So today I created a mesh of L2VPNs interconnecting virtual-routers on 5
SRX650s and J6350s.
I did the 3 650s as a trial, then added 2 J6350s later because, well, I could.
Configuring a triangle of RSVP-signalled paths, BGP neighbours, and logical
tunnels, wasn't too bad. Adding 2 more points
On 11/11/2011 11:42 AM, Mike Williams wrote:
So. VPLS. Point-to-multiple-point. Virtual LAN. Brilliant!
I haven't yet found any documentation that I can actually understand though.
Note: The site range value must be greater than the largest site identifier.
is especially confusing. Range is
In Juniper's BGP-based VPLS, you do not need to create pseudowires in-between
the VPLS instances. As long as you have one master LSP (usuallyan RSVP one)
in-between two PEs, BGP will then (by detecting which VPLS instance is
announced from which device), automatically build an inner tunnel
We use both LDP- and BGP-signalled in our environment, with
LDP-signalled providing somewhat of a 'poor-man's hub and spoke'. The
spokes are configured to only build pseudowires to the hub, and the
hub builds back to all spokesworks for our particular use case.
Anyhow, BGP
BTW, (although it's an offtopic quite a bit) let me ask if there is anyone
here who ever deployed/mantined LDP VPLS + external BGP autodiscovery in
real life for more or less large-scale network? How was it? Any gotchas
worth to be aware of?
12.11.2011 6:47 пользователь David Ball
10 matches
Mail list logo