On this topic I can
highly recommend the book "MPLS-Enabled Applications: Emerging Developments and
New Technologies"
BR,
Angel Bardarov
JNCIE-M #266
CCIE #21516
-Original Message-
From: juniper-nsp-boun...@puck.nether.net
[mailto:juniper-nsp-boun...@puck.nether.net] On Beh
fferent
encapsulations for many different customers.
For info about lt interfaces take a look on this page:
http://www.juniper.net/techpubs/software/junos/junos93/swconfig-services/configuring-a-logical-tunnel-interface.html#id-14359583
Regards,
Angel Bardarov
Marcus Eide wrote:
Angel,
Thanks,
kets : 35
Output packets: 34
Regards,
Angel Bardarov
Marcus Eide wrote:
Hi,
I don't know if this is even possible, but I thought I'd ask you: Does
anyone know if it's possible to connect an l2circuit to an vrf type
routing-instance?
I found some information that stated this co
Marcus Eide wrote:
Hi angel,
Thank you. This is actually a typo, from when I copy/pasted the config. I
checked my config again and I do have lt-1/2/0.1 in the routing-instance.
Do you have Tunnel (or similar) PIC in your box? You can configure lt
interfaces but without the PIC traffic can
PLS :)
And it's not poor mans feature - actually you'll get a lot of
operational benefits.
Regards,
Angel Bardarov
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Marcus Eide wrote:
Hi,
I don't know if this is even possible, but I thought I'd ask you: Does
anyone know if it's possible to connect an l2circuit to an vrf type
routing-instance?
I found some information that stated this could be done with logical tunnel
interfaces, so I tried the following:
Hi,
For restrictions about FR DLCIs take a look on to this page:
http://www.juniper.net/techpubs/software/junos/junos92/swconfig-network-interfaces/data-link-connection-identifiers-on-channelized-interfaces.html#id-11044428
Regards,
Angel Bardarov
[EMAIL PROTECTED] wrote:
Hello ..
Im using a
nk:
http://www.juniper.net/techpubs/software/junos/junos91/swconfig-network-interfaces/unicast-rpf-and-default-routes.html
Angel Bardarov
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
with 1 PEM - it will feed RE, CB and
FPC slots 0,1 and 2. You need second PEM to provide power for FPC slots
3-7. You have to install power modules in slots PEM1 and PEM3.This
scheme doesn't provide redundancy.
And please check juniper's documentation for more
able if this is stable for production
networks and how will behave Junos 9.0 with small CF cards and DRAM
(IGP, many BGP peers and so on). And I doubt you will receive J-TAC
support in case of need.
My advice is simply upgrade your RE's hardware accordingly.
Regards,
Angel Bardarov
David Ba
into issues getting an LX link up with a Cisco 6500. Possibly some
> autonegotiation problem?
>
You can turn it off on C6500:
MSR28(config-if)#speed nonegotiate
BTW - why you think it is an autonegotiation problem? What is the output
of "show interfaces&
escription l2circuit_termination;
encapsulation ethernet-ccc;
peer-unit 1;
family ccc;
}
unit 1 {
description vpls_instance;
encapsulation ethernet-vpls;
peer-unit 0;
Regards,
Angel Bardarov
David Ball wrote:
> I
ion check-out failed
With 100 ms interval the convergence is around 400 ms and you can't have
more than 20 groups. You can have more than 20 if these additional
groups don't use "fast interval" feature.
Regards,
Angel
Gard Undheim wrote:
> Hi
>
> Thanks for the ans
Take a look at this link
http://www.juniper.net/techpubs/software/junos/junos85/swconfig85-policy/id-10568390.html#id-10568390
Angel
David Ball wrote:
> I have 2 Gig links on different PICs added to an 802.3ad agg
> ethernet bundle for a customer. They're an L2VPN customer so
er.net/training/certification/books.html
Angel
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
/junos85/swconfig85-vpns/id-11192646.html#id-11192646
Angel
David Ball wrote:
> I've read what docs I can find regarding Sham links for OSPF, but am
> still not seeing what I feel are the expected results. Here's my
> topology:
>
> cisco2651---T640---T640---M10 (Gig
ize 1500 bytes
20:21:31.239070 Out 0:14:f6:28:d4:5d > 1:0:5e:0:0:5, ethertype 802.1Q
(0x8100), length 82: vlan 11, _*p 6,*_ ethertype IPv4, 10.0.4.5 >
224.0.0.5: OSPFv2, Hello, length: 44
^C
1 packets received by filter
0 packets dropped by kernel
That way you can see vlan tag, .1p bits, et
> higher JunOS version. So my quesion is what version of JunOS can i
> install, i have red some things about 8 version but i am not sure if
>
You can safely use the latest one ;)
Angel
___
juniper-nsp mailing list ju
tput from "show route advertising-protocol bgp ..."
Angel
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
raffic won't be forwarded over the
MPLS cloud.
Can you post the output from "show vpls connections detail"?
Angel
Yevgeniy Voloshin wrote:
> Hi All,
>
> now I am trying to configure VPLS on only one router(m7i) with 2
> suninterfaces(ge-0/1/0.100 and ge-0/1/0.200) pointin
rt of DE, FECN and BECN bits
from one PE to other PE is needed. But according to Juniper docs this
will limit the number of supported L2 VPNs and L2circuits.Does
anybody knows about such restrictions?
//Best regards,
Angel Bardarov
/
///
___
junipe
After little search I found it - its a bug - PR#95358 is related to
Channelized T3 PICs. Altough I have 10x CHE1 IQ the behavior is the
same. After changing dlci 20 to 200 frame relay switching takes place
and ping is OK.
Angel Bardarov
___
juniper
no success:
[EMAIL PROTECTED] show protocols connections
interface-switch fr {
interface e1-2/0/0.20;
interface ds-2/0/4:1.20;
}
Does anybody have any clue what may be the problem? Is it a bug or I'm
missing something?
/Best regards,
Angel Bardarov
Senior Specialist
Backbone Networks
Fix
nect unchanalized E1 interface to FR resource in FRS card.
Regards,
Angel Bardarov
FAHAD ALI KHAN wrote:
> In our current Network Newbridge 3600 are used for Serial
> Aggregation.Beforemigration to MPLS,Intercity E1s was terminated on
> NB3600 and the NB3600s
> were managed via NMS b
24 matches
Mail list logo