[j-nsp] L2circuit martini issue....!
FAHAD ALI KHAN
fahad.alikhan at gmail.com
Wed Jan 24 05:16:41 EST 2007
Well Alex it will help in CE-CE link tracking.....and PE will never know any
thing.....!
But consider a scenario, On PE-A clinet hav two last miles, one primary and
other backup. We configure L2Circuit and set Pri lastmile as primary link
and secondary lastmile as protected one (under the protocol l2circuit
hierarchy). So If PE didnt know abt it and put down Primary link's CCC/TCC,
client cannot use secondary Lastmile.
In this case use of every CE-CE link tracking methodologies will fail.....?
Regards
Fahad Ali Khan
On 1/24/07, Alex <alex.arseniev at gmail.com> wrote:
>
> Fahad,
> If you are looking for End-to-End failure detection for L2VPN where PE-CE
> links are Ethernet then You can do it either with BFD or IP SLA Cisco
> feature. Please be aware than BFD/IP SLA do not actually bring down the
> interface/subinterface, they either tear down IGP adjacencies (BFD), remove
> static routes (BFD/IP SLA) or disable PBR (IP SLA).
> HTH
> Cheers
> Alex
>
>
> ----- Original Message -----
> *From:* FAHAD ALI KHAN <fahad.alikhan at gmail.com>
> *To:* Alex <alex.arseniev at gmail.com>
> *Cc:* juniper-nsp <juniper-nsp at puck.nether.net>
> *Sent:* Wednesday, January 24, 2007 8:24 AM
> *Subject:* Re: [j-nsp] L2circuit martini issue....!
>
>
> Thanx Alex....!
>
> FREEK works....but there comes another issue like that....as we transport
> VLAN-TCC and VLAN-CCC clients. If there lastmile goes down.....VLAN BPDUs
> will still recieve over Turnk port (Switch to Juniper). So it coz L2Circuit
> to remain up.
>
> I look for the Ethernet/VLAN OAM that defines in 802.3ah. but its
> implementation is not possible on all layer 2 Switches.
> Also work on these standards are still in process.
>
> can u ppl tell me, Is there any other thing that can help me to detect the
> end to end failure for Layer 2 VPNs (CCC or TCC) like FREEK do for FR. Im
> looking for OAM or BFD....features.....does they can solve the issue.....!
>
> Regards
>
> Fahad Ali Khan
>
>
>
>
More information about the juniper-nsp
mailing list