Hi All
Happy New Year 2008.
Starting from today I move to http://adisubrata.wordpress.com
This blog will still active but i will not post anymore.
Powered by ScribeFire.
Frodo# show interfaces ge-3/3/0
description interface to customer
per-unit-scheduler; ß share or per-unit schedulers
vlan-tagging;
unit 0 {
vlan-id 100;
family inet {
address 192.168.1.1/30;
}
}
unit 1 {
vlan-id 101;
family inet {
address 192.168.1.5/30;
}
}
Frodo# show class-of-service
I just browsing some kind of film from www.indowebster.com and found that some of Traditional Indonesian Assets has to be claimed by another.
You can see the Film in Bahasa from this link.
It’s very funny
for me as innocent guy (I’m not politician), because I knew these items which is claimed by another when I was a kid.
In this film, you can see some of item which is claimed and recognized by them.
1. Rasa Sayange song (I learn it in Elementary School, >20 years ago)
2. Angklung (In Elementary school too). I heard from my friend in Bandung that his college has very popular group music and had experience brought Angklung to Europe. How could they claimed it?
3. Rendang (This food is original from Padang Sumatra and really delicious, I like it).
In the last week, many people from Ponorogo (East Java) went to Jakarta. They tried to get clarification from Malaysia Embassy about traditional art from East Java which is claimed by Malaysia, Reog Ponorogo. From documentation and pictures, i have seen only minor changes and simple different between Reog Ponorogo and Reog Malaysia except the badge and Malaysia word at the top of the Reog.
I just someone who cares about Indonesia. Sorry if this post makes you uncomfortable 
. Peace
Since last year Juniper releasing 4 books for free to download.
Those books were created by Sybex and now officially out of print. Actually you can still buy this book if you interest using hardcopy rather than softcopy. In my experiences, many people doesn’t like to used softcopy version 
.
Most of engineer used this book when they was starting to become Juniper engineer.
- JNCIA M/T(Download)
- JNCIS M/T (Download)
- JNCIP M/T (Download)
- JNCIE M/T (Download)
For the complete list of JNTCP Study Guides, you can refer to this link.
Courtesy of Juniper.net
In this post i will share VPLS LDP Configuration in Juniper router. The topology similar with previous post (VPLS BGP section).
Requirements:
- In Juniper you have to used Tunnel Service PIC (VT interface). If you don’t have any Tunnel PIC, you have to configure no-tunnel-services in the routing-instance.
- Junos version 8.4.
Topology:
CE3
33.33.33.33
|ge-1/1/0
|11.0.0.3/24
|
|
|ge-2/0/1
PE3
3.3.3.3
|ge-2/0/2
|192.168.101.2
|
|
|ge-3/3/1
|192.168.101.1
11.11.11.11 1.1.1.1 2.2.2.2 22.22.22.22
CE1 ——————PE1———————- PE2————————CE2
11.0.0.1 /24 192.168.100.1 .2 11.0.0.2/24
ge-1/0/0 ge-3/3/0 ge-7/2/0 ge-0/1/0 ge-1/1/0 ge-0/0/0
|
|ge-1/3/0
|192.168.102.1
|
|
|ge-1/1/0
|192.168.102.2
(RR)
4.4.4.4
IP Address:
PE1 Lo0: 1.1.1.1/32
PE2 Lo0: 2.2.2.2/32
PE3 Lo0: 3.3.3.3/32
CE1, CE2 and CE3 has one subnet address.
CE1 interface: 11.0.0.1/24
CE2 interface: 11.0.0.2/24
CE3 interface: 11.0.0.3/24
RR Lo0: 4.4.4.4/32
IGP using OSPF area 0.0.0.0.
VPLS Interface Configurations:
PE1 to CE1 Interface
interfaces {
ge-3/3/0 {
encapsulation ethernet-vpls;
unit 0;
}
PE2 to CE2 Interface
interfaces {
ge-1/1/0 {
encapsulation ethernet-vpls;
unit 0;
}
PE3 to CE3 Interface
interfaces {
ge-2/0/1 {
encapsulation ethernet-vpls;
unit 0;
}
Routing-Instances Configurations:
PE1
routing-instances {
vpls {
instance-type vpls;
interface ge-3/3/0.0;
protocols {
vpls {
vpls-id 50;
neighbor 2.2.2.2;
neighbor 3.3.3.3;
}
}
}
PE2
routing-instances {
vpls {
instance-type vpls;
interface ge-1/1/0.0;
protocols {
vpls {
vpls-id 50;
neighbor 1.1.1.1;
neighbor 3.3.3.3;
}
}
}
PE3
routing-instances {
vpls {
instance-type vpls;
interface ge-2/0/1.0;
protocols {
vpls {
vpls-id 50;
neighbor 1.1.1.1;
neighbor 2.2.2.2;
}
}
}
Since LDP has been used, you haven’t to be connected with BGP. In other words, there are no BGP in PE1, PE2 and PE3.
Sorry, i’m forgot to captured the results of this experiments when i was in Sydney.
You can refer to this link if you have to configuring VPLS in Juniper router using LDP as a signalling.
http://www.juniper.net/techpubs/software/junos/junos84/swconfig84-vpns/id-vpls-ldp-signal.html
In this post i will share VPLS BGP Configuration in Juniper router.
Requirements:
- In Juniper you have to used Tunnel Service PIC (VT interface). If you don’t have any Tunnel PIC, you have to configure no-tunnel-services in the routing-instance.
Below is the configuration topology which is related with my work in VPLS BGP.
CE3
33.33.33.33
|ge-1/1/0
|11.0.0.3/24
|
|
|ge-2/0/1
PE3
3.3.3.3
|ge-2/0/2
|192.168.101.2
|
|
|ge-3/3/1
|192.168.101.1
11.11.11.11 1.1.1.1 2.2.2.2 22.22.22.22
CE1 ——————PE1———————- PE2————————CE2
11.0.0.1 /24 192.168.100.1 .2 11.0.0.2/24
ge-1/0/0 ge-3/3/0 ge-7/2/0 ge-0/1/0 ge-1/1/0 ge-0/0/0
|
|ge-1/3/0
|192.168.102.1
|
|
|ge-1/1/0
|192.168.102.2
(RR)
4.4.4.4
IP Address:
PE1 Lo0: 1.1.1.1/32
PE2 Lo0: 2.2.2.2/32
PE3 Lo0: 3.3.3.3/32
CE1, CE2 and CE3 has one subnet address.
CE1 interface: 11.0.0.1/24
CE2 interface: 11.0.0.2/24
CE3 interface: 11.0.0.3/24
RR Lo0: 4.4.4.4/32
IGP using OSPF area 0.0.0.0.
VPLS Interface Configurations:
PE1 to CE1 Interface
interfaces {
ge-3/3/0 {
encapsulation ethernet-vpls;
unit 0;
}
PE2 to CE2 Interface
interfaces {
ge-1/1/0 {
encapsulation ethernet-vpls;
unit 0;
}
PE3 to CE3 Interface
interfaces {
ge-2/0/1 {
encapsulation ethernet-vpls;
unit 0;
}
BGP Configuration:
RR:
protocols {
bgp {
group rr {
type internal;
local-address 4.4.4.4;
family inet-vpn {
unicast;
}
family l2vpn {
signaling;
}
cluster 1.1.1.1;
neighbor 1.1.1.1;
neighbor 2.2.2.2;
neighbor 3.3.3.3;
}
}
PE1:
protocols {
group rr {
type internal;
local-address 1.1.1.1;
family inet-vpn {
unicast;
}
family l2vpn {
signaling;
}
neighbor 4.4.4.4;
}
}
PE2:
bgp {
group rr {
type internal;
local-address 2.2.2.2;
family inet-vpn {
unicast;
}
family l2vpn {
signaling;
}
neighbor 4.4.4.4;
}
}
PE3:
bgp {
group rr {
type internal;
local-address 3.3.3.3;
family inet-vpn {
unicast;
}
family l2vpn {
signaling;
}
neighbor 4.4.4.4;
}
}
Routing-Instance Configuration:
PE1:
routing-instances {
vpls {
instance-type vpls;
interface ge-3/3/0.0;
route-distinguisher 10:10;
vrf-target target:10:10;
protocols {
vpls {
site-range 50;
site pe1 {
site-identifier 1;
interface ge-3/3/0.0;
}
}
}
}
PE2:
routing-instances {
vpls {
instance-type vpls;
interface ge-1/1/0.0;
route-distinguisher 10:10;
vrf-target target:10:10;
protocols {
vpls {
site-range 50;
site pe2 {
site-identifier 2;
interface ge-1/1/0.0;
}
}
}
}
PE3:
routing-instances {
vpls {
instance-type vpls;
interface ge-2/0/1.0;
route-distinguisher 10:10;
vrf-target target:10:10;
protocols {
vpls {
site-range 50;
tunnel-services {
primary vt-2/3/0;
}
site pe2 {
site-identifier 3;
interface ge-2/0/1.0;
}
}
}
}
Show route from PE1:
CE1_Juniper# run show route
inet.0: 10 destinations, 10 routes (10 active, 0 holddown, 0 hidden)
+ = Active Route, – = Last Active, * = Both
10.1.1.0/24 *[Direct/0] 15:56:05
> via ge-1/0/0.10
10.1.1.2/32 *[Local/0] 15:56:05
Local via ge-1/0/0.10
11.0.0.0/24 *[Direct/0] 14:28:56
> via ge-1/0/0.600
11.0.0.1/32 *[Local/0] 14:28:56
Local via ge-1/0/0.600
11.11.11.11/32 *[Direct/0] 1d 21:31:28
> via lo0.0
——- truncate—————-
Ping Results from CE1:
CE1_Juniper# run ping 11.0.0.3
PING 11.0.0.3 (11.0.0.3): 56 data bytes
64 bytes from 11.0.0.3: icmp_seq=0 ttl=64 time=1.272 ms
64 bytes from 11.0.0.3: icmp_seq=1 ttl=64 time=1.036 ms
64 bytes from 11.0.0.3: icmp_seq=2 ttl=64 time=1.145 ms
C
—- 11.0.0.3 ping statistics—-
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max/stddev = 1.036/1.151/1.272/0.096 ms
CE1_Juniper# run ping 11.0.0.2
PING 11.0.0.2 (11.0.0.2): 56 data bytes
64 bytes from 11.0.0.2: icmp_seq=0 ttl=64 time=1.197 ms
64 bytes from 11.0.0.2: icmp_seq=1 ttl=64 time=1.050 ms
64 bytes from 11.0.0.2: icmp_seq=2 ttl=64 time=1.050 ms
C
—- 11.0.0.2 ping statistics—-
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max/stddev = 1.050/1.099/1.197/0.069 ms
CE1 able to ping CE2 and CE3.
Reference:
Feature guide Junos 8.0 VPLS (PDF)
Juniper support VPLS LDP or RFC 4762 in release 8.4. Juniper has been supporting VPLS BGP since Junos 6.x.
The main different between VPLS BGP and VPLS LDP is: how l2 redistribution carried which is determined by control plane protocols.
- VPLS BGP, BGP used as a control plane protocol. (RFC 4761)
- VPLS LDP, LDP used as a control plane protocol. (RFC 4762)
In order to support Multi protocols BGP, BGP session must be configured to carried VPLS information. VPLS NLRI has AFI 25 and SAFI 65.
+——————————————————+
| Length (2 octets) |
+——————————————————+
| Route Distinguisher (8 octets) |
+——————————————————+
| VE ID (2 octets) |
+——————————————————+
| VE Block Offset (2 octets) |
+——————————————————+
| VE Block Size (2 octets) |
+——————————————————+
| Label Base (3 octets) |
+——————————————————+
All PE must have at least one VE (VPLS Edge Service).
VPLS BGP in Juniper has similar architecture with L3VPN services. The configuration is very simple.
In the next post i will explain the configuration in Juniper to support VPLS. (Both of LDP or BGP).
Suddenly, my blackberry 8707v hangs. There was a message "ERROR 330" in the screen and I couldn’t do anything. Reset has no effect and still stuck in the Error messages.
I decided to wipe all software on it.
Searching from www.google.com make me found software, JLCmder.
With this software I can erase all software in my blackberry. This software is very cool and has simple navigation.
After restart, different error message displayed in the screen “ERROR 507”. I guess this message is to indicate no software loaded in the Blackberry.
I didn’t have any 8707v software in my laptop, so I’m going to my carrier www.vodafone.com to download this file, 8707vMPBr4.2.1rel177PL3.3.0.28A4.2.1.105SmarTone.exe.
Using Blackberry desktop manager, I started to upgrade it with latest version 4.2 (originally my Blackberry have 4.0.2 software version).
The first process is Load JVM and erases all remaining files in the Blackberry. It’s like low level format in Hard disk. It takes me around 10 minutes to wipe all files.
Now, my Blackberry could operate again with software 4.2. But honestly I don’t see what is the different between latest version and 4.0.2. I’m not Blackberry addict and never tried to compare between them.
The next step is enterprise activation. It will load everything from Laptop and Email server. The processes are very simple, just connected Blackberry to laptop and automatically activate the email server.
Usually I used it only for call like a mobile handset. But the important thing is, Blackberry connects me with Juniper email server. So, every time and everywhere I’m able to received emails and read them.
I have M7i router for simulation.
What is M7i?
M7i is the smallest router in the M-series family of Juniper.
M7i has 7G capacity and usually used for medium enterprises networks.
But many customers used it for bigger application such as internet gateway routers.
M7i memory can be upgrade until 2G.
But here, it only have 256Mb…. Uh… very small.
enugadi@M7i# run show version
Here, it only have 256Mb…. Uh… very small. Usually it reach until 95-98%. In the first boot, it has something about 80% CPU processing.
enugadi@M7i# run show route summary
239000 is active routes installed in my M7i.
Full internet prefix
Even M7i is the smallest one, it can handle full internet prefix with high stability.
M7i have builtin ethernet 2 port and tunnel service PIC.
Tunnel service PIC will generate interface for tunneling.
Each tunnel PIC can simultaneously support a number of different
tunnel types facilitating a wide range of applications:
• IP-IP Encapsulation: IP-IP enables the transport of IPv4 and IPv6
over disparate IP infrastructures that may be owned by a third
party or have disjointed capabilities or policies.
• Generic Routing Encapsulation: GRE is an alternative to IP-IP that
supports IPSec and non-IP protocols such as MPLS in addition
to IPv4 and IPv6 over any IP infrastructure. Juniper Networks
implementation of GRE complies with RFC 1701 and RFC 1702.
• PIM Sparse Mode Encapsulation: Supports PIM-SM encapsulation
and de-encapsulation on source designated routers (DR) and
rendezvous points (RPs).
• Logical Tunnels: Logical Tunnels create a virtual interface within
the router that supports the interconnection of VPNs and
communication between logical routers.
• Virtual Tunnels: Virtual Tunnels support Virtual Private LAN
Service (VPLS)
• Multicast Tunnels: Multicast Tunnels are used to create Multicast
Distribution Trees (MDT), which transport VPN multicast packets
across a RFC 2547bis Layer 3 VPN network.
Starting from JUNOS 8.1 Juniper introduce new feature on GE interface, called flexible vlan tagging.
This features are supported by GE IQ2 interfaces.
"flexible" term means that they allow you to configure logical unit on interfaces with vlan combination either dual, single and untag.This technology is widely adapted in Metro Ethernet networks and some used it for Ethernet aggregation router and L2VPN.
Lunch time…
JUNOS supports 15 logical routers. So, using 2 routers you can have 30 logical routers.
Logical router is different with virtual routers.Logical router has separates process between one another including the main router. So, we can treat logical router as different routers than main router.
How about virtual routers?Virtual routers processes are not separates with main router. If you have to do route leaking, you can use virtual router. You can see the complete documentation about logical routers in www.juniper.net.
Fiuh…..
I haven’t seen this blog for a long time. The reason is simple thing, i don’t know what kind of topic to write down in this blog.
Working as part of Professional service team make me learn anything about Juniper and Junos. I should be and it must be.
Doing some labs is my duty and of course to make everything under control and working.
Today I have setup lab in may laptop 
after stuck trying to install "" in vmware.
In previous trial, i used vmware 4.5 and 5 workstation, my " not supported by those vmware.
But i received some files from om Irzan and he told me that his "" working in vmware 6.
And so, it was surprise me "" application running on vmware 6.
Thanks om Irzan. We are team right ??
Virtual Private LAN Service (VPLS), also known as Transparent LAN Service and Virtual Private Switched Network service, is a useful Service Provider offering. The service offers a Layer 2 Virtual Private Network (VPN); however, in the case of VPLS, the customers in the VPN are connected by a multipoint Ethernet LAN, in contrast to the usual Layer 2 VPNs, which are point-to-point in nature.
This document describes the functions required to offer VPLS, a mechanism for signaling a VPLS, and rules for forwarding VPLS frames across a packet switched network.
After installing new OS, i tried to install Yahoo Mesenger from Yahoo.com. But, why version available are only 8.x. Honestly, I hate YM version 8, YM8 only would made my PC getting slow and slowwww. I like to used YM version 7 than 8. I found some link which i can download YM7, here it is http://filehippo.com/download_yahoo_messenger/
I’m sure one of you hate YM 8.
In this experiment, i wanna running EBGP Multihop between PE edge router. VPN IPV4 routes are exchanged directly between each PE. The ASBR maintain EBGP session with labeled unicast. IPV4 routes are exchanged in this ASBR, so PE1 will reach loopback address of the PE2. EBGP Multihop between the PE1 and PE2 require IPv4 connection between them.
(more…)
Option B: EBGP redistribution of labeled VPN-IPv4 routes.
I will put my lab again as i promised in the previous post. I have done with option B.
VPN IPv4 routes are exchanged in the ASBR.
References for labeled unicast can be found in http://www.juniper.net/techpubs/software/junos/junos74/swconfig74-vpns/html/cofc-config.html#1013124
you can find the topology below:
RSVP tunnel configured in the PE1 to PE3, vice versa. Also for connection between PE2 and PE4.
EBGP running between PE2 and PE4.
Objectives:
CE1 can be reached by CE4, CE2 by CE4… vice versa.
(more…)
I will explain what i have done with VRF to VRF connections between 2 providers.
The characteristics of this option is you have to configuring per-VPN on each ASBR or the PE which connected to different AS.
In diagram you will seeing there are two providers which have AS100 and AS200.
Each provider have 2 customer connected, customer Grey and Blue.
The Customers Grey and Blue are connected to the PE1 and PE2. The PE3 of AS100 has directly connected to the PE4 of AS200.
Here you go…
Objective:
CE1 can be reached by CE3 one another, also CE2 to CE4.
(more…)
According to Ina Minei Book, The MPLS Enabled Application, there are 3 option for deploying Multi AS VPN.
Option A: VRF to VRF connections at the ASBR.
This is the simplest method to exchange the VPN routes across AS boundary.
ASBR maintain all vpn connected towards the other AS. ASBR or Edge PE would be directly connected to the other ASBR via logical connection per VRF. Therefore, each VRF will need minumum 1 logical connection to exchange the VPN routes. In fact, this option is only manipulating IPv4 routes. This option is simple but not scalable, because one logical connection should be connected for every VRF. If provider need to add one new VRF, they require to manages logical connection in the ASBR.
Option B: EBGP redistribution of labeled IPv4 routes.
This option would eliminated behaviour in the option A. The ASBR doesn’t have VRF configuration. The option B uses a single EBGP session between ASBR to carry VPN-IPv4 routes. SO the ASBR will maintain state of all VPN routes.
Option C: multihop EBGP redistribution of labeled VPN-IPv4 routes between the source and destination AS, with EBGP redistribution of labeled IPv4 routes from one AS to the neighboring AS.
In this option, the customer uses the Multihop EBGP session between each PE router to carry external prefixes. This option eliminated option B that ASBR should be maintain state of all vpn routes.
In the next post, i will try to present my lab of all option above in detail.
If you have to know the basic of Multi AS in detail, you should have Ina Minei book, and read from this book. Its very good book.
Today is my last day working at Ericsson. I feel so sad when will going out. But the show must go on. I should leaving Ericsson for my career aim. Thanks Ericsson, you made me stronger.
I bought dopod M700 3 month ago. The situation forced me buying the new one. My ipaq broken when i had been using it for GPRS ATP in customer. Well, my boss did not prepared any handset for this ATP activity. I have no other choice except using my own ppc to conduct this. But when it was down, i have to bought it with my own pocket. I chose this ppc because the price is not too expensive compared with the others. My option was only two, the other one was ipaq 6828. But i heard that HP would cutting off and discontinue the ipaq from their business, so i had not interested again.
From my experiences with M700, the cpu speed are slow. Some of my program doesn’t working well. I have to wait for a second while the program loaded. The camera quality just so.. so… its not enough for me (I was graphic designer, maybe my standart too high). I never tried to open the movie files (mov and avi format), but it seems this ppc works good with 3gp format (i tried with 10mb file size).
When I open the mp3 files, i feel the quality is very good. Then i tried to connected to the active speaker, and the result is awesome. The treble and bass is clear for my ears. Also, you can adjust bass and treble intensity from the control panel menu. So, i recommend this ppc if you want the gadges with multifunction and song lover. But if you have many programs, expecially programs which have large cpu consume, i do not recommend it 
.
In this post i will try to explain LDP over RSVP concepts. For Some reason of the networks, sometimes we need to implement LDP and RSVP together. The main reason is existing and current networks doesn’t support RSVP.
All LDP neighbour are up.
LDP session is directly from router 1 to router 6.
04:18:11.951379 Out IP 1.1.1.1.646 > 6.6.6.6.646: LDP, Label-Space-ID: 1.1.1.1:0, pdu-length: 38
04:18:12.001911 In IP 6.6.6.6.4337 > 1.1.1.1.646: P 18:36(18) ack 19 win 16384
04:18:12.071378 Out IP 1.1.1.1.646 > 6.6.6.6.4337: P 19:37(18) ack 36 win 45158
04:18:12.171600 In IP 6.6.6.6.4337 > 1.1.1.1.646: . ack 37 win 16384
enugadi@M20# run show ldp neighbor logical-router pe1
Address Interface Label space ID Hold time
192.168.3.2 lt-0/0/0.13 1.1.1.1:0 11
[edit]
enugadi@M20# run show ldp neighbor logical-router pe2
Address Interface Label space ID Hold time
192.168.1.1 lt-0/0/0.15 6.6.6.6:0 10
[edit]
enugadi@M20# run show ldp neighbor logical-router 1
Address Interface Label space ID Hold time
6.6.6.6 lo0.1 6.6.6.6:0 33
192.168.3.1 lt-0/0/0.12 7.7.7.7:0 14
[edit]
enugadi@M20# run show ldp neighbor logical-router 6
Address Interface Label space ID Hold time
1.1.1.1 lo0.6 1.1.1.1:0 41
192.168.1.2 lt-0/0/0.14 8.8.8.8:0 14
enugadi@M20# run traceroute 10.10.10.10 logical-router ce1
traceroute to 10.10.10.10 (10.10.10.10), 30 hops max, 40 byte packets
1 198.200.1.1 (198.200.1.1) 0.798 ms 0.686 ms 0.592 ms
2 192.168.3.2 (192.168.3.2) 1.104 ms 0.979 ms 0.914 ms
MPLS Label=100048 CoS=0 TTL=1 S=0
MPLS Label=100000 CoS=0 TTL=1 S=1
3 10.1.2.2 (10.1.2.2) 0.935 ms 0.973 ms 0.918 ms
MPLS Label=100016 CoS=0 TTL=1 S=0
MPLS Label=100000 CoS=0 TTL=1 S=0
MPLS Label=100000 CoS=0 TTL=2 S=1
4 10.1.6.2 (10.1.6.2) 0.937 ms 0.975 ms 0.909 ms
MPLS Label=100000 CoS=0 TTL=1 S=0
MPLS Label=100000 CoS=0 TTL=3 S=1
5 192.168.1.2 (192.168.1.2) 0.933 ms 0.949 ms 1.206 ms
MPLS Label=100000 CoS=0 TTL=1 S=1
6 10.10.10.10 (10.10.10.10) 0.866 ms 0.852 ms 0.808 ms
7 10.10.10.10 (10.10.10.10) 0.831 ms 0.867 ms 0.823 ms
PE1 will push label value 1000048 to router 1.
inet.3: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)
+ = Active Route, – = Last Active, * = Both
1.1.1.1/32 *[LDP/9] 01:21:11, metric 1
> to 192.168.3.2 via lt-0/0/0.13
6.6.6.6/32 *[LDP/9] 01:21:11, metric 1
> to 192.168.3.2 via lt-0/0/0.13, Push 100032
8.8.8.8/32 *[LDP/9] 01:21:11, metric 1
> to 192.168.3.2 via lt-0/0/0.13, Push 100048
enugadi@M20# run show ldp database logical-router pe1
Input label database, 7.7.7.7:0—1.1.1.1:0
Label Prefix
3 1.1.1.1/32
100032 6.6.6.6/32
100064 7.7.7.7/32
100048 8.8.8.8/32
Output label database, 7.7.7.7:0—1.1.1.1:0
Label Prefix
100064 1.1.1.1/32
100080 6.6.6.6/32
3 7.7.7.7/32
100096 8.8.8.8/32
Router 1 will advertise label 100016 to router 6 (end of lsp tunell).
enugadi@M20# run show ldp database session 6.6.6.6 logical-router 1
Input label database, 1.1.1.1:0—6.6.6.6:0
Label Prefix
100016 1.1.1.1/32
3 6.6.6.6/32
100032 7.7.7.7/32
100000 8.8.8.8/32
Router 1 will push and swap operation.
enugadi@M20# run show route logical-router 1 table mpls.0 detail | find 100048
100048 (1 entry, 1 announced)
*LDP Preference: 9
Next-hop reference count: 2
Next hop: 10.1.2.2 via lt-0/0/0.2 weight 0×1, selected
Label-switched-path 1-to-6
Label operation: Swap 100000, Push 100016(top)
State:
Age: 1:24:38 Metric: 1
Task: LDP
Announcement bits (1): 0-KRT
AS path: I
Prefixes bound to route: 8.8.8.8/32
The packet received by router 4 has an MPLS label assigned.
Router 6 will perform PHP because next-hop router (PE2) in the egress router and will request router 6 to perform PHP.
Requirement:
1. Traffic flow from ce1 to ce2 is the following:
ce1 – pe1 – router 1 – router 2 – router 4 – router 3 – router 6 – pe 2 – ce2
2. Traffic flow from ce2 to ce1 is the following:
ce2 – pe2 – router 6 – router 5 – router 1 – pe1 – ce1
Results:
enugadi@M20# run show bgp summary logical-router pe1
Groups: 2 Peers: 2 Down peers: 0
Table Tot Paths Act Paths Suppressed History Damp State Pending
bgp.l3vpn.0 2 2 0 0 0 0
Peer AS InPkt OutPkt OutQ Flaps Last Up/Dwn State|#Active/Received/Damped…
198.200.1.2 65000 120 133 0 0 59:08 Establ
vpn1.inet.0: 1/2/0
8.8.8.8 100 221 224 0 0 1:16:07 Establ
bgp.l3vpn.0: 2/2/0
vpn1.inet.0: 2/2/0
enugadi@M20# run show bgp summary logical-router pe2
Groups: 2 Peers: 2 Down peers: 0
Table Tot Paths Act Paths Suppressed History Damp State Pending
bgp.l3vpn.0 2 2 0 0 0 0
Peer AS InPkt OutPkt OutQ Flaps Last Up/Dwn State|#Active/Received/Damped…
172.16.0.2 65000 120 130 0 0 59:22 Establ
vpn1.inet.0: 1/2/0
7.7.7.7 100 223 223 0 0 1:16:21 Establ
bgp.l3vpn.0: 2/2/0
vpn1.inet.0: 2/2/0
enugadi@M20# run ping 10.10.10.10 logical-router ce1
PING 10.10.10.10 (10.10.10.10): 56 data bytes
64 bytes from 10.10.10.10: icmp_seq=0 ttl=58 time=1.009 ms
64 bytes from 10.10.10.10: icmp_seq=1 ttl=58 time=1.002 ms
64 bytes from 10.10.10.10: icmp_seq=2 ttl=58 time=1.015 ms
64 bytes from 10.10.10.10: icmp_seq=3 ttl=58 time=1.034 ms
C
—- 10.10.10.10 ping statistics—-
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max/stddev = 1.002/1.015/1.034/0.012 ms
[edit]
enugadi@M20# run ping 9.9.9.9 logical-router ce2
PING 9.9.9.9 (9.9.9.9): 56 data bytes
64 bytes from 9.9.9.9: icmp_seq=0 ttl=56 time=1.037 ms
64 bytes from 9.9.9.9: icmp_seq=1 ttl=56 time=0.958 ms
64 bytes from 9.9.9.9: icmp_seq=2 ttl=56 time=0.939 ms
64 bytes from 9.9.9.9: icmp_seq=3 ttl=56 time=0.973 ms
C
—- 9.9.9.9 ping statistics—-
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.939/0.977/1.037/0.037 ms
enugadi@M20# run show route logical-router ce1
inet.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden)
+ = Active Route, – = Last Active, * = Both
9.9.9.9/32 *[Direct/0] 02:02:16
> via lo0.9
10.10.10.10/32 *[BGP/170] 00:05:23, localpref 100
AS path: 100 100 I
> to 198.200.1.1 via lt-0/0/0.19
172.16.0.0/24 *[BGP/170] 00:05:23, localpref 100
AS path: 100 I
> to 198.200.1.1 via lt-0/0/0.19
198.200.1.0/24 *[Direct/0] 02:02:44
> via lt-0/0/0.19
198.200.1.2/32 *[Local/0] 02:02:44
Local via lt-0/0/0.19
enugadi@M20# run show route logical-router ce2
inet.0: 5 destinations, 6 routes (5 active, 0 holddown, 0 hidden)
+ = Active Route, – = Last Active, * = Both
9.9.9.9/32 *[BGP/170] 00:07:37, localpref 100
AS path: 100 100 I
> to 172.16.0.1 via lt-0/0/0.21
10.10.10.10/32 *[Direct/0] 01:32:27
> via lo0.10
172.16.0.0/24 *[Direct/0] 01:59:44
> via lt-0/0/0.21
[BGP/170] 00:37:47, localpref 100
AS path: 100 I
> to 172.16.0.1 via lt-0/0/0.21
172.16.0.2/32 *[Local/0] 01:59:44
Local via lt-0/0/0.21
198.200.1.0/24 *[BGP/170] 00:07:37, localpref 100
AS path: 100 I
> to 172.16.0.1 via lt-0/0/0.21
enugadi@M20# run show mpls lsp logical-router pe1
Ingress LSP: 1 sessions
To From State Rt ActivePath P LSPname
8.8.8.8 7.7.7.7 Up 0 primary * pe1-to-pe2
Total 1 displayed, Up 1, Down 0
Egress LSP: 3 sessions
To From State Rt Style Labelin Labelout LSPname
7.7.7.7 8.8.8.8 Up 0 1 FF 3 – pe2-to-pe1
7.7.7.7 8.8.8.8 Up 0 1 FF 3 – pe2-to-pe1
7.7.7.7 8.8.8.8 Up 0 1 FF 3 – pe2-to-pe1
Total 3 displayed, Up 3, Down 0
enugadi@M20# run show mpls lsp logical-router pe2
Ingress LSP: 1 sessions
To From State Rt ActivePath P LSPname
7.7.7.7 8.8.8.8 Up 0 third * pe2-to-pe1
Total 1 displayed, Up 1, Down 0
Egress LSP: 3 sessions
To From State Rt Style Labelin Labelout LSPname
8.8.8.8 7.7.7.7 Up 0 1 FF 3 – pe1-to-pe2
8.8.8.8 7.7.7.7 Up 0 1 FF 3 – pe1-to-pe2
8.8.8.8 7.7.7.7 Up 0 1 FF 3 – pe1-to-pe2
Total 3 displayed, Up 3, Down 0
Transit LSP: 0 sessions
Total 0 displayed, Up 0, Down 0
enugadi@M20# run
