[Contents] [Prev] [Next] [Index] [Report an Error]

Step 2: Verify the Operation of Uneven Bandwidth Load Balancing

Purpose

When a router is performing unequal-cost load balancing between LSPs paths, the show route detail command displays a balance field associated with each next hop being used.

Action

To verify that an RSVP LSP is unevenly load-balanced, use the following JUNOS CLI operational mode commands:

user@host> show route protocol rsvp detail

user@host> show mpls lsp statistics

Sample Output

user@R1> show route protocol rsvp detail 



inet.0: 25 destinations, 25 routes (25 active, 0 holddown, 0 hidden)

10.0.90.14/32 (1 entry, 1 announced)

        State: <FlashAll>

        *RSVP   Preference: 7

                Next-hop reference count: 7

                Next hop: 10.0.12.14 via fe-0/1/0.0 weight 0x1 balance 10%

                Label-switched-path lsp1

                Label operation: Push 100768

                Next hop: 10.0.12.14 via fe-0/1/0.0 weight 0x1 balance 20%

                Label-switched-path lsp2

                Label operation: Push 100736

                Next hop: 10.0.12.14 via fe-0/1/0.0 weight 0x1 balance 30% ,selected

                Label-switched-path lsp3

                Label operation: Push 100752

                Next hop: 10.0.12.14 via fe-0/1/0.0 weight 0x1 balance 40%

                Label-switched-path lsp4

                Label operation: Push 100784

                State: <Active Int>

                Local AS: 65432 

                Age: 8:03       Metric: 4 

                Task: RSVP

                Announcement bits (2): 0-KRT 4-Resolve tree 1 

                AS path: I



inet.3: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)



192.168.0.1/32 (1 entry, 1 announced)

        State: <FlashAll>

        *RSVP   Preference: 7

                Next-hop reference count: 7

                Next hop: 10.0.12.14 via fe-0/1/0.0 weight 0x1 balance 10%

                Label-switched-path lsp1

                Label operation: Push 100768

                Next hop: 10.0.12.14 via fe-0/1/0.0 weight 0x1 balance 20%

                Label-switched-path lsp2

                Label operation: Push 100736

                Next hop: 10.0.12.14 via fe-0/1/0.0 weight 0x1 balance 30%

                Label-switched-path lsp3

                Label operation: Push 100752

                Next hop: 10.0.12.14 via fe-0/1/0.0 weight 0x1 balance 40%, selected

                Label-switched-path lsp4

                Label operation: Push 100784

                State: <Active Int>

                Local AS: 65432 

                Age: 8:03       Metric: 4 

                Task: RSVP

                Announcement bits (1): 1-Resolve tree 1 

                AS path: I



user@R1> show mpls lsp statistics 

Ingress LSP: 4 sessions

To              From            State     Packets            Bytes LSPname

192.168.0.1     192.168.1.1     Up          10067           845628 lsp1

192.168.0.1     192.168.1.1     Up          20026          1682184 lsp2

192.168.0.1     192.168.1.1     Up          29796          2502864 lsp3

192.168.0.1     192.168.1.1     Up          40111          3369324 lsp4

Total 4 displayed, Up 4, Down 0



Egress LSP: 1 sessions

To              From            State     Packets            Bytes LSPname

192.168.1.1     192.168.0.1     Up             NA               NA r0-r1

Total 1 displayed, Up 1, Down 0



Transit LSP: 0 sessions

Total 0 displayed, Up 0, Down 0

What It Means

The sample output from ingress router R1 shows that traffic is distributed according to the LSP bandwidth configuration, as indicated by the Balance: xx% field. For example, lsp1 has 10 Mbps of bandwidth configured, as reflected in the Balance: 10% field.

Router Configurations for Bandwidth Load Balancing

Purpose

The configuration in this section is for ingress router R1 in the example network illustrated in Figure 13. The configuration for the other five routers in the network are the same as those found in Router Configurations for the Load-Balanced MPLS Network.

Action

To display a router configuration, use the following JUNOS CLI operational mode command:

user@host> show configuration | no-more

Sample Output

user@R1> show configuration | no-more 

[....Output truncated...]

interfaces {

    fe-0/1/0 {

        unit 0 {

            family inet {

                address 10.0.12.13/30;

            }

            family mpls;

        }

    }

    fe-0/1/2 {

        unit 0 {

            family inet {

                address 10.0.16.13/30;

            }

            family mpls;

        }

    }

    fxp0 {

        unit 0 {

            family inet {

                address 192.168.70.143/21;

            }

        }

    }

    lo0 {

        unit 0 {

            family inet {

                address 192.168.1.1/32;

            }

        }

    }

}

routing-options {

    static {

        [...Output truncated...]

        }

        route 100.100.1.0/24 reject;

    }

    router-id 192.168.1.1;

    autonomous-system 65432;

    forwarding-table {

        export lbpp;

    }

}

protocols {

    rsvp {

        load-balance bandwidth; #RSVP bandwidth load balancing

        interface fe-0/1/0.0;

        interface fe-0/1/2.0;

        interface fxp0.0 {

            disable;

        }

    }

    mpls {

        label-switched-path lsp1 {

            to 192.168.0.1;

            install 10.0.90.14/32 active;

            bandwidth 10m; #Bandwidth configured for each LSP

            primary via-r4;

        }

        label-switched-path lsp2 {

            to 192.168.0.1;

            install 10.0.90.14/32 active;

            bandwidth 20m; #Bandwidth configured for each LSP

            primary via-r2;

        }

        label-switched-path lsp3 {

            to 192.168.0.1;

            install 10.0.90.14/32 active;

            bandwidth 30m; #Bandwidth configured for each LSP

            primary via-r2;

        }

        label-switched-path lsp4 {

            to 192.168.0.1;

            install 10.0.90.14/32 active;

            bandwidth 40m; #Bandwidth configured for each LSP

            primary via-r4;

        }

        path via-r2 {

            10.0.29.2 loose;

        }

        path via-r4 {

            10.0.24.2 loose;

        }

        interface fe-0/1/0.0;

        interface fe-0/1/2.0;

        interface fxp0.0 {

            disable;

        }

    }

    bgp {

        export send-statics;

        group internal {

            type internal;

            local-address 192.168.1.1;

            neighbor 192.168.2.1;

            neighbor 192.168.4.1;

            neighbor 192.168.9.1;

            neighbor 192.168.6.1;

            neighbor 192.168.0.1;

        }

    }

    ospf {

        traffic-engineering;

        area 0.0.0.0 {

            interface fe-0/1/0.0;

            interface fe-0/1/2.0;

            interface lo0.0 {

                passive;

            }

        }

    }

}

policy-options {

    policy-statement lbpp { Load balancing policy

        then {

            load-balance per-packet;

        }

    }

    policy-statement send-statics {

        term statics {

            from {

                route-filter 100.100.1.0/24 exact;

            }

            then accept;

        }

    }

}

What It Means

The sample output shows the configuration for the ingress router R1 in the example network illustrated in Figure 13. The configuration for the other five routers in the network is the same as those found in Router Configurations for the Load-Balanced MPLS Network.

[Contents] [Prev] [Next] [Index] [Report an Error]