-Original Message-
From: [EMAIL PROTECTED] [mailto:juniper-nsp-
[EMAIL PROTECTED] On Behalf Of Jonathan Looney
Sent: 30 October 2007 06:06 PM
To: Roman Shibrick
Cc: juniper-nsp@puck.nether.net
Subject: Re: [j-nsp] GRE over IPsec on J-series
Roman,
On newer versions of IOS
Not sure what you're after here, but if you just do a commit
synchronise on the master RE, the backup RE will have the same config
(which is of course recommended)
cheers
Sean
Youness El Wardi wrote:
Hi guys,
We are installing a new RE on our J20 juniper GGSN. I believe this new
RE will
show configuration chassis
no-source-route;
redundancy {
failover {
on-loss-of-keepalives;
on-disk-failure;
}
graceful-switchover {
enable;
}
}
And under system just do commit sync
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL
Hi all,
According to this page:
http://www.juniper.net/techpubs/software/junos/junos84/swconfig84-servic
es/id-10028063.html#id-10028063
the ASM for the M7i does not support lt- interfaces. However, when I
configure one, it seems to work just fine:
admin# show logical-routers blah
interfaces
Youness El Wardi writes:
Can any one advice or send an example of a router with 2 Res configured?
Also you'll want to make the re0 and re1 configuration groups
for any local RE-specific config:
groups {
re0 {
system {
host-name foo-re0;
}
interfaces {
On 31/10/2007, Farhan Jaffer [EMAIL PROTECTED] wrote:
3) What is the usual practice of providers while using L2VPN, will this
small range of VLAN Ids enough for them? OR there are other techniques?
In our case, we just treat L2VPNs as transparent, and let the
customer send whatever they
1) Encapsulation extended-vlan-ccc is only for the purpose of using extended
VLANs (or large number of VLANs) OR there are other differences as well?
You can't have IP subinterfaces with extended-vlan-ccc.
2) What is the valid VLAN IDs range when using extended-vlan-ccc encap?
There are
7 matches
Mail list logo
