Life is a Roller Coaster

November 18, 2007

VPLS LDP Configuration

Filed under: Technical section — adisubrata @ 8:34 PM

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:

vpls.gifIP 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

November 9, 2007

VPLS BGP Configuration

Filed under: Technical section — adisubrata @ 10:34 AM

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. No-tunnel-services has limitation in several PIC in Junos 8.0

NOTE: The following interface types do not support the use of LSI interfaces with VPLS:

  • Aggregated SONET/SDH (cannot be used as the core-facing interface)
  • 1-port Gigabit Ethernet
  • 2-port Gigabit Ethernet
  • 4-port Fast Ethernet

However, I cannot see the documentation of this limitation in Junos 8.3

NOTE: The following interface types do not support the use of LSI interfaces with VPLS:

  • Aggregated SONET/SDH interfaces (cannot be used as the core-facing interface)
  • Channelized interfaces (cannot be used as the core-facing interface)
  • ATM1 interfaces

Below is the configuration topology which is related with my work in VPLS BGP.

vpls.gif

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)

VPLS

Filed under: Technical section — adisubrata @ 7:35 AM

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).

List of AFI Proposed:

Number Description
0 Reserved
1 IPv4
2 IPv6
3 NSAP
4 HDLC (8-bit multidrop)
5 BBN 1822
6 802 (includes all 802 media plus Ethernet “canonical format”)
7 E.163
8 E.164 (SMDS, Frame Relay, ATM)
9 F.69 (Telex)
10 X.121 (X.25, Frame Relay)
11 IPX
12 AppleTalk
13 DECnet IV
14 Banyan Vines
65535 Reserved

November 8, 2007

My BlackBerry 8707v Hang

Filed under: General — adisubrata @ 8:36 PM

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.

Blog at WordPress.com.