To be willing is only half the task

adisubrata — Thu, 03 Jan 2008 22:02:56 +0000

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.

IQ2 PIC’s Traffic Shapping going easy

adisubrata — Wed, 05 Dec 2007 20:27:56 +0000

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
forwarding-classes {
    queue 1 be;
    queue 0 af;
    queue 2 ef;
    queue 3 nc;
}
traffic-control-profiles {
    customer100k {
        scheduler-map m1; //Optional if you have to do Hierarchical shapping.
        shaping-rate 100k;
        guaranteed-rate 50k;
        delay-buffer-rate 100k;
    }
    upstream {
        shaping-rate 300m;
    }
}
interfaces {
    ge-0/0/0 {
        shaping-rate 10m; <- maximum traffic set to this interface (Due oversubscribe 1:4 in Ge-IQ2 PIC)
        unit 0 {
            input-traffic-control-profile customer100k;
            output-traffic-control-profile customer100k;
        }
        unit 1 {
            output-traffic-control-profile customer100k;
        }
    }
    ge-0/0/3 {
        shaping-rate 500m;
    }
}
scheduler-maps {
    m1 {
        forwarding-class be scheduler be;
        forwarding-class ef scheduler ef;
        forwarding-class af scheduler af;
        forwarding-class nc scheduler nc;
    }
}
schedulers {
    be1 {
        transmit-rate percent 30;
    }
    ef1 {
        transmit-rate percent 35;
    }
    af1 {
        transmit-rate percent 25;
    }
    nc1 {
        transmit-rate percent 5;
    }
}

From configuration above, you can see there is shaping parameter and guaranteed rate parameter configured in the traffic-control-profiles.
Shaping parameter is called with PIR and guaranteed rate is called with CIR.
You can define specific PIC and CIR for each customer, respectively.
Another approach to do traffic shaping is used rate limit policy which is called with “Policer” in Junos. Both of them has similar function to do rate limit, but the process are really different, IQ PIC doing it in hardware level J, the PIC itself. Another benefit is Hierarchical CoS/QoS supported in the IQ PIC.

Just to give you a clue how to check IQ PIC ASIC components:

iq2(uart)#——- hidden———
Output ifd resources
===============
ifd       speed   bwremain   bwlatent defaultifls latentifls totalshapedbw
—-      ——-  ————-  ————-———————————-———————-
128    10000000     7800000           0            0           0          2200000
129 1000000000 1000000000           0            0           0                0
130 1000000000 1000000000           0            0           0                0
131   500000000   500000000           0            0           0                0
ifd        guarbwremain   guarlatentifls guarbwifls      delaybwremain delaylatentifls
—-        ———————  ——————————————     ———————- ————————-
128               8900000                  0           2               8000000                  0
129            1000000000                  0           0            1000000000                  0
130            1000000000                  0           0            1000000000                  0
131             500000000                  0           0             500000000                  0

Indonesian assets has to be claimed and has recognized by another

adisubrata — Sat, 01 Dec 2007 21:44:37 +0000

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.

My concern is Indonesia should keep all traditional assets before the others claim and steal it.
I’m not politician and I don’t have any purpose to be sarcastic.

I just someone who cares about Indonesia. Sorry if this post makes you uncomfortable . Peace

Juniper Books (Legal) - Free Download

adisubrata — Sat, 01 Dec 2007 17:59:15 +0000

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

VPLS LDP Configuration

adisubrata — Sun, 18 Nov 2007 11:03:53 +0000

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

VPLS BGP Configuration

adisubrata — Fri, 09 Nov 2007 03:20:43 +0000

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)

VPLS

adisubrata — Fri, 09 Nov 2007 02:36:56 +0000

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

My BlackBerry 8707v Hang

adisubrata — Thu, 08 Nov 2007 21:47:13 +0000

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.

The Power of M7i

adisubrata — Wed, 31 Oct 2007 01:31:07 +0000

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
Hostname: M7i
Model: m7i
JUNOS Base OS boot [7.6R3.6]
JUNOS Base OS Software Suite [7.6R3.6]
JUNOS Kernel Software Suite [7.6R3.6]
JUNOS Packet Forwarding Engine Support (M7i/M10i) [7.6R3.6]
JUNOS Routing Software Suite [7.6R3.6]
JUNOS Online Documentation [7.6R3.6]
JUNOS Crypto Software Suite [7.6R3.6]
[edit]
enugadi@M7i# run show chassis routing-engine
Routing Engine status:
    Temperature                 21 degrees C / 69 degrees F
    CPU temperature             19 degrees C / 66 degrees F
    DRAM                       256 MB
    Memory utilization          87 percent
    CPU utilization:
      User                       0 percent
      Background                 0 percent
      Kernel                     2 percent
      Interrupt                  0 percent
      Idle                      97 percent
    Model                          RE-5.0
    Serial ID                      xxxxxxx
    Start time                     2007-10-31 03:10:55 UTC
    Uptime                        5 hours, 2 minutes, 29 seconds
    Load averages:                 1 minute   5 minute 15 minute
                                       0.01       0.02       0.00

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
Autonomous system number: xxxx
Router ID: x.x.x.x
inet.0: 239007 destinations, 239007 routes (239007 active, 0 holddown, 0 hidden)
              Direct:      3 routes,      3 active
               Local:      3 routes,      3 active
                 BGP: 239000 routes, 239000 active
           Aggregate:      1 routes,      1 active
__juniper_private1__.inet.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
              Direct:      1 routes,      1 active
               Local:      1 routes,      1 active
__juniper_private1__.inet6.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden)
              Direct:      3 routes,      3 active
               Local:      2 routes,      2 active

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.

Flexible vlan tagging

adisubrata — Wed, 19 Sep 2007 19:22:31 +0000

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.
Ethernet frame can be configured as untagged, single tagged or dual tagged (stacked vlan).
In previous version of JUNOS, we cannot configure logical interface with mix configuration between single tagged and dual tagged. So, if you have 2 logical interface in the same physical port, you cannot configure one logical interface with single tag and another logical interface with dual tag.
The configuration is very simple. Just put flexible-vlan-tagging syntax under GE IQ2 physical interface.
Under logical interface, we can configure vlan inner and outer simultaneously.
Look at this example:
vlan-tags outer 0×8100.100 inner 0×8100.101;
This logical interface will have vlan outer 100 and vlan inner 101.
Each vlan has 4bytes overhead. So, stacked vlan need additional header 4 bytes than single tag.
What is 0×8100?
0×8100 is TPID (Tag protocol identifier).
Juniper used 0×8100 for TPID, but another vendor like Extreme Networks using TPID 0×9100.
Juniper called dual tagged vlan with Stacked Vlan, another vendor call it with QinQ.
Just different term, but have the same concept. J

This technology is widely adapted in Metro Ethernet networks and some used it for Ethernet aggregation router and L2VPN.

lunch time with logical routers

adisubrata — Wed, 19 Sep 2007 18:58:53 +0000

Lunch time…

Usually I used logical-routers for testing purposes.

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.

Running “^^”

adisubrata — Wed, 29 Aug 2007 17:33:23 +0000

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 ??

RFC 4761 on Virtual Private LAN Service (VPLS) Using BGP for Auto Discouvery

adisubrata — Mon, 11 Jun 2007 18:34:41 +0000

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.

See complete of RFC VPLS Using BGP

Yahoo Mesenger Version 7.x

adisubrata — Sun, 03 Jun 2007 13:08:13 +0000

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.

Multi AS backbone: Option C // EBGP Multihop

adisubrata — Sat, 02 Jun 2007 15:16:07 +0000

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.

BGP Status:

Note: No VPN routes exchanged in th PE3 and PE4.

enugadi@enugadi# run show bgp summary logical-router all

—————————-output truncate——————————

logical-router: pe1
Groups: 2 Peers: 2 Down peers: 0
Table          Tot Paths Act Paths Suppressed    History Damp State    Pending
inet.0                 1          0          0          0          0          0
bgp.l3vpn.0           16         16          0          0          0          0
Peer               AS      InPkt     OutPkt    OutQ   Flaps Last Up/Dwn State|#Active/Received/Damped…
2.2.2.2           200         32         32       0       0       12:34 Establ
bgp.l3vpn.0: 16/16/0
blue.inet.0: 14/14/0
grey.inet.0: 2/2/0
3.3.3.3           100         18         19       0       0        8:22 Establ
inet.0: 0/1/0
——-

logical-router: pe2
Groups: 2 Peers: 2 Down peers: 0
Table          Tot Paths Act Paths Suppressed    History Damp State    Pending
inet.0                 1          0          0          0          0          0
bgp.l3vpn.0            4          4          0          0          0          0
Peer               AS      InPkt     OutPkt    OutQ   Flaps Last Up/Dwn State|#Active/Received/Damped…
1.1.1.1           100         31         34       0       0       12:34 Establ
bgp.l3vpn.0: 4/4/0
blue.inet.0: 2/2/0
grey.inet.0: 2/2/0
4.4.4.4           200         28         28       0       0       12:38 Establ
inet.0: 0/1/0
——-

logical-router: pe3
Groups: 2 Peers: 2 Down peers: 0
Table          Tot Paths Act Paths Suppressed    History Damp State    Pending
inet.0                 1          1          0          0          0          0
Peer               AS      InPkt     OutPkt    OutQ   Flaps Last Up/Dwn State|#Active/Received/Damped…
1.1.1.1           100         18         20       0       0        8:22 Establ
inet.0: 0/0/0
11.0.0.10         200         28         30       0       0       13:17 Establ
inet.0: 1/1/0
——-

logical-router: pe4
Groups: 2 Peers: 2 Down peers: 0
Table          Tot Paths Act Paths Suppressed    History Damp State    Pending
inet.0                 1          1          0          0          0          0
Peer               AS      InPkt     OutPkt    OutQ   Flaps Last Up/Dwn State|#Active/Received/Damped…
2.2.2.2           200         26         29       0       0       12:38 Establ
inet.0: 0/0/0
11.0.0.9          100         29         30       0       0       13:17 Establ
inet.0: 1/1/0
——-

Testing connectivity:

enugadi@enugadi# run ping 30.30.30.30 logical-router ce1 rapid count 100
PING 30.30.30.30 (30.30.30.30): 56 data bytes
!
—- 30.30.30.30 ping statistics—-
100 packets transmitted, 100 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.438/0.450/0.513/0.010 ms

[edit]
enugadi@enugadi# run traceroute 30.30.30.30 logical-router ce1
traceroute to 30.30.30.30 (30.30.30.30), 30 hops max, 40 byte packets
1 10.0.0.2 (10.0.0.2) 0.149 ms 0.134 ms 0.107 ms
2 11.0.0.2 (11.0.0.2) 0.440 ms 0.418 ms 0.421 ms
     MPLS Label=100032 CoS=0 TTL=1 S=0
     MPLS Label=1024 CoS=0 TTL=1 S=1
3 11.0.0.10 (11.0.0.10) 0.414 ms 0.408 ms 0.412 ms
     MPLS Label=100000 CoS=0 TTL=1 S=0
     MPLS Label=1024 CoS=0 TTL=2 S=1
4 30.30.30.30 (30.30.30.30) 0.431 ms 0.425 ms 0.435 ms

[edit]
enugadi@enugadi# run ping 40.40.40.40 logical-router ce2 rapid count 100
PING 40.40.40.40 (40.40.40.40): 56 data bytes
!
—- 40.40.40.40 ping statistics—-
100 packets transmitted, 100 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.438/0.450/0.510/0.011 ms

[edit]
enugadi@enugadi# run traceroute 40.40.40.40 logical-router ce2
traceroute to 40.40.40.40 (40.40.40.40), 30 hops max, 40 byte packets
1 10.0.0.10 (10.0.0.10) 0.145 ms 0.109 ms 0.107 ms
2 11.0.0.2 (11.0.0.2) 0.436 ms 0.411 ms 0.419 ms
     MPLS Label=100032 CoS=0 TTL=1 S=0
     MPLS Label=1025 CoS=0 TTL=1 S=1
3 11.0.0.10 (11.0.0.10) 0.418 ms 0.408 ms 0.412 ms
     MPLS Label=100000 CoS=0 TTL=1 S=0
     MPLS Label=1025 CoS=0 TTL=2 S=1
4 40.40.40.40 (40.40.40.40) 0.442 ms 0.425 ms 0.424 ms

Multi AS backbone: Option B // EBGP redistribution of labeled VPN-IPv4 routes

adisubrata — Fri, 01 Jun 2007 20:14:39 +0000

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.

All Status

LSP Status

enugadi@enugadi# run show mpls lsp logical-router all

——————— output truncate————————

logical-router: pe1
Ingress LSP: 1 sessions
To From State Rt ActivePath P LSPname
3.3.3.3 1.1.1.1 Up 0 * 1-to-3
Total 1 displayed, Up 1, Down 0

Egress LSP: 1 sessions
To From State Rt Style Labelin Labelout LSPname
1.1.1.1 3.3.3.3 Up 0 1 FF 3 – 3-to-1
Total 1 displayed, Up 1, Down 0

Transit LSP: 0 sessions
Total 0 displayed, Up 0, Down 0
——-

logical-router: pe4

Ingress LSP: 1 sessions
To From State Rt ActivePath P LSPname
2.2.2.2 4.4.4.4 Up 0 * 4-to-2
Total 1 displayed, Up 1, Down 0

Egress LSP: 1 sessions
To From State Rt Style Labelin Labelout LSPname
4.4.4.4 2.2.2.2 Up 0 1 FF 3 – 2-to-4
Total 1 displayed, Up 1, Down 0

Transit LSP: 0 sessions
Total 0 displayed, Up 0, Down 0
——-

logical-router: pe2

Ingress LSP: 1 sessions
To From State Rt ActivePath P LSPname
4.4.4.4 2.2.2.2 Up 0 * 2-to-4
Total 1 displayed, Up 1, Down 0

Egress LSP: 1 sessions
To From State Rt Style Labelin Labelout LSPname
2.2.2.2 4.4.4.4 Up 0 1 FF 3 – 4-to-2
Total 1 displayed, Up 1, Down 0

Transit LSP: 0 sessions
Total 0 displayed, Up 0, Down 0
——-

logical-router: pe3

Ingress LSP: 1 sessions
To From State Rt ActivePath P LSPname
1.1.1.1 3.3.3.3 Up 0 * 3-to-1
Total 1 displayed, Up 1, Down 0

Egress LSP: 1 sessions
To From State Rt Style Labelin Labelout LSPname
3.3.3.3 1.1.1.1 Up 0 1 FF 3 – 1-to-3
Total 1 displayed, Up 1, Down 0

Transit LSP: 0 sessions
Total 0 displayed, Up 0, Down 0
——-

BGP Status

enugadi@enugadi# run show bgp summary logical-router all

———output truncate————

logical-router: pe1
Groups: 1 Peers: 1 Down peers: 0
Table          Tot Paths Act Paths Suppressed    History Damp State    Pending
bgp.l3vpn.0           16         16          0          0          0          0
inet.0                 0          0          0          0          0          0
Peer               AS      InPkt     OutPkt    OutQ   Flaps Last Up/Dwn State|#Active/Received/Damped…
3.3.3.3           100        140         80       0       2       31:34 Establ
bgp.l3vpn.0: 16/16/0
blue.inet.0: 14/14/0
grey.inet.0: 2/2/0
——-

logical-router: pe4
Groups: 2 Peers: 2 Down peers: 0
Table          Tot Paths Act Paths Suppressed    History Damp State    Pending
bgp.l3vpn.0           20         20          0          0          0          0
inet.0                 0          0          0          0          0          0
Peer               AS      InPkt     OutPkt    OutQ   Flaps Last Up/Dwn State|#Active/Received/Damped…
2.2.2.2           200        100        153       0       0       39:26 Establ
bgp.l3vpn.0: 16/16/0
11.0.0.9          100         72         77       0       0       29:13 Establ
bgp.l3vpn.0: 4/4/0
——-

logical-router: pe2
Groups: 1 Peers: 1 Down peers: 0
Table          Tot Paths Act Paths Suppressed    History Damp State    Pending
bgp.l3vpn.0            4          4          0          0          0          0
inet.0                 0          0          0          0          0          0
Peer               AS      InPkt     OutPkt    OutQ   Flaps Last Up/Dwn State|#Active/Received/Damped…
4.4.4.4           200        152        102       0       0       39:26 Establ
bgp.l3vpn.0: 4/4/0
blue.inet.0: 2/2/0
grey.inet.0: 2/2/0
——-

logical-router: pe3
Groups: 2 Peers: 2 Down peers: 0
Table          Tot Paths Act Paths Suppressed    History Damp State    Pending
bgp.l3vpn.0           20         20          0          0          0          0
inet.0                 0          0          0          0          0          0
Peer               AS      InPkt     OutPkt    OutQ   Flaps Last Up/Dwn State|#Active/Received/Damped…
1.1.1.1           100        108        187       0       2       31:34 Establ
bgp.l3vpn.0: 4/4/0
11.0.0.10         200         76         74       0       1       29:13 Establ
bgp.l3vpn.0: 16/16/0
——-

Routing tables

enugadi@enugadi# run show route logical-router ce3

inet.0: 19 destinations, 19 routes (19 active, 0 holddown, 0 hidden)
+ = Active Route, – = Last Active, * = Both

10.0.0.0/30        *[OSPF/150] 00:22:12, metric 0, tag 3489661128
                    > to 10.0.0.6 via fxp2.3
10.0.0.4/30        *[Direct/0] 05:38:29
                    > via fxp2.3
10.0.0.5/32        *[Local/0] 05:38:30
                      Local via fxp2.3
10.10.10.10/32     *[OSPF/10] 00:22:12, metric 1
                    > to 10.0.0.6 via fxp2.3
30.30.30.30/32     *[Direct/0] 05:38:30
                    > via lo0.30
192.168.1.0/24     *[Direct/0] 05:21:21
                    > via fxp2.9
192.168.1.1/32     *[Local/0] 05:21:21
                      Local via fxp2.9
192.168.100.0/24   *[Static/5] 03:45:24
                      Reject
192.168.101.0/24   *[Static/5] 03:45:24
                      Reject
192.168.102.0/24   *[Static/5] 03:45:24
                      Reject
192.168.103.0/24   *[Static/5] 03:45:24
                      Reject
192.168.104.0/24   *[Static/5] 03:45:24
                      Reject
192.168.105.0/24   *[Static/5] 03:45:24
                      Reject
192.168.106.0/24   *[Static/5] 03:45:24
                      Reject
192.168.107.0/24   *[Static/5] 03:45:24
                      Reject
192.168.108.0/24   *[Static/5] 03:45:24
                      Reject
192.168.109.0/24   *[Static/5] 03:45:24
                      Reject
192.168.110.0/24   *[Static/5] 03:45:24
                      Reject
224.0.0.5/32       *[OSPF/10] 05:38:31, metric 1
                      MultiRecv

[edit logical-routers pe2]
enugadi@enugadi# run show route logical-router ce2

inet.0: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden)
+ = Active Route, – = Last Active, * = Both

10.0.0.8/30        *[Direct/0] 05:38:34
                    > via fxp1.2
10.0.0.9/32        *[Local/0] 05:38:35
                      Local via fxp1.2
10.0.0.12/30       *[OSPF/150] 00:22:17, metric 0, tag 3489661028
                    > to 10.0.0.10 via fxp1.2
20.20.20.20/32     *[Direct/0] 05:38:35
                    > via lo0.20
40.40.40.40/32     *[OSPF/10] 00:22:17, metric 1
                    > to 10.0.0.10 via fxp1.2
224.0.0.5/32       *[OSPF/10] 05:38:35, metric 1
                      MultiRecv

[edit logical-routers pe2]
enugadi@enugadi# run show route logical-router ce4

inet.0: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden)
+ = Active Route, – = Last Active, * = Both

10.0.0.8/30        *[OSPF/150] 00:22:20, metric 0, tag 3489661128
                    > to 10.0.0.14 via fxp2.4
10.0.0.12/30       *[Direct/0] 05:38:37
                    > via fxp2.4
10.0.0.13/32       *[Local/0] 05:38:38
                      Local via fxp2.4
20.20.20.20/32     *[OSPF/10] 00:22:20, metric 1
                    > to 10.0.0.14 via fxp2.4
40.40.40.40/32     *[Direct/0] 05:38:38
                    > via lo0.40
224.0.0.5/32       *[OSPF/10] 05:38:38, metric 1
                      MultiRecv

Result:

enugadi@enugadi# …ping 30.30.30.30 logical-router ce1 rapid count 100
PING 30.30.30.30 (30.30.30.30): 56 data bytes
!
—- 30.30.30.30 ping statistics—-
100 packets transmitted, 100 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.437/0.457/0.922/0.048 ms

[edit logical-routers pe2]
enugadi@enugadi# run traceroute 30.30.30.30 logical-router ce1
traceroute to 30.30.30.30 (30.30.30.30), 30 hops max, 40 byte packets
1 10.0.0.2 (10.0.0.2) 0.151 ms 0.108 ms 0.107 ms
2 11.0.0.2 (11.0.0.2) 0.438 ms 0.417 ms 0.418 ms
     MPLS Label=100512 CoS=0 TTL=1 S=1
3 11.0.0.10 (11.0.0.10) 0.413 ms 0.407 ms 0.411 ms
     MPLS Label=100480 CoS=0 TTL=1 S=1
4 30.30.30.30 (30.30.30.30) 0.432 ms 0.425 ms 0.434 ms

[edit logical-routers pe2]
enugadi@enugadi# run ping 40.40.40.40 logical-router ce2 rapid count 100
PING 40.40.40.40 (40.40.40.40): 56 data bytes
!
—- 40.40.40.40 ping statistics—-
100 packets transmitted, 100 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.437/0.451/0.514/0.010 ms

[edit logical-routers pe2]
enugadi@enugadi# run traceroute 40.40.40.40 logical-router ce2
traceroute to 40.40.40.40 (40.40.40.40), 30 hops max, 40 byte packets
1 10.0.0.10 (10.0.0.10) 0.149 ms 0.111 ms 0.107 ms
2 11.0.0.2 (11.0.0.2) 0.432 ms 0.417 ms 0.418 ms
     MPLS Label=100528 CoS=0 TTL=1 S=1
3 11.0.0.10 (11.0.0.10) 0.413 ms 0.406 ms 0.413 ms
     MPLS Label=100496 CoS=0 TTL=1 S=1
4 40.40.40.40 (40.40.40.40) 0.459 ms 0.425 ms 0.425 ms

Cheersss…………..