Search

1 to 10 of 92
Sort by

Discussion Post
MPLS was Stuck sometimes or new router joins into this backbone.

Hi, Sometimes, my backbone will be suck and need to reboot RE. Or when I add new router into my backbone. It will be stuck again. While this issue happens, first, I can't ping 8.8.8.8 by certain IP of this new router, but some IP can. MPLS label exists normally. Then...

4A7DA6EC-2645-4FFD-96A3-C0C058459E10-1-Configuration.rtf


Discussion Post
BFD over RSVP LSP isn't coming up

Hello everybody, I hope you are safe wherever you are. I am configuring BFD over rsvp-based LSP but it is not coming up, I have spent a lot of time checking, can anybody spot where the problem is? Here is the configuration: pe1: path te tunnel path1 ( ...



Discussion Reply
RE: Route is not getting installed in Routing-instance

Hi , As per the documet JUNOS checks the vpnv4 routes against the vrf import policies. If the vpnv4 route matches one of the policies, it is added to the bgp.l3vpn.0 routing table otherwise it will not show in the bgp.l3vpn.0 routing table. bgp.l3vpn.0 — To determine whether to...


Discussion Post
Redistribution of MP-BGP Routes into OSPF

HI Team, i'm running ospf as PE(Juniper)-CE(Cisco) protocol and trying to import routes learned from MP-BGP into ospf but it is not working . routing-instances ( A ( instance-type vrf; interface em2.0; route-distinguisher 100:1; vrf-import import to A; vrf-export export to PE4; vrf...



Discussion Reply
RE: Route is not getting installed in Routing-instance

Hi, Thanks for your responce. i have few questions:- 1. how to use OR expresion inside communities. 2. i have read that " bgp.l3vpn.0 —Stores routes learned from other PE routers. Routes in the bgp.l3vpn.0 routing table are copied into a Layer 3 VRF when there is a...


Discussion Post
Route is not getting installed in Routing-instance

Hi Team, i'm facing an issue where juniper is connected with CISCO (PE router) and receiving two routes( 7.7.7.7 and 77.77.77.77) with route-target 100:1. i have created a policy to match the route target and applied in the routing-instance but route is not available in routing-instance...