Verifying the operation of the hash key configuration of port data on the ingress and transit routers in your network.
On the ingress router, to verify the operation of the hash key, enter the following JUNOS CLI operational mode commands:
On the transit router, to verify the operation of the hash key, enter the following JUNOS CLI operational mode commands:
The following sample output is for ingress router R1:
user@R1> show configuration forwarding-options
hash-key {
family inet { #Port data configuration
layer-3;
layer-4;
}
}
user@R1> show configuration routing-options
static {
[...Output truncated...]
autonomous-system 65432;
forwarding-table {
export lbpp; #Load balancing policy applied
}
user@R1> show configuration policy-options
policy-statement lbpp { #Load balancing policy defined
then {
load-balance per-packet;
}
}
[...Output truncated...]
The sample output from ingress router R1 for the three show configuration commands (forwarding-options, routing-options, and policy-options) shows that load balancing is correctly configured for the INET hash key and the load-balancing policy (lbpp).
Sample Output
The following sample output is for ingress router R1:
user@R1> show route forwarding-table destination 10.0.90.14
Routing table: inet
Internet:
Destination Type RtRef Next hop Type Index NhRef Netif
10.0.90.14/32 user 0 ulst 262144 2
10.0.12.14 Push 100688 fe-0/1/0.0
10.0.12.14 Push 100656 fe-0/1/0.0
10.0.12.14 Push 100672 fe-0/1/0.0
10.0.12.14 Push 100704 fe-0/1/0.0
Meaning
The sample output from ingress router R1 for the show route forwarding-table destination command shows unilist (ulst) in the Type field, indicating that load balancing is working. In this case, the Type field shows the operation performed on packets. The push operation adds a new label to the top of the packet before the packets are pushed out of interface fe-0/1/0.0.
Sample Output
The following sample output is for transit router R2:
user@R2> show route 10.0.90.14
inet.0: 25 destinations, 27 routes (25 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
10.0.90.12/30 *[OSPF/10] 03:06:04, metric 3
via so-0/0/1.0
> via so-0/0/2.0
Meaning
The sample output from transit router R2 for the show route command shows two OSPF routes to the destination interface on egress router R0. Even though the route with the greater than sign (>) is the selected route, traffic will be balanced across both interfaces, as shown in the output for the following show route forwarding-table and monitor traffic commands.
Sample Output
The following sample output is for transit router R2:
user@R2> show route forwarding-table destination 10.0.90.14
Routing table: inet
Internet:
Destination Type RtRef Next hop Type Index NhRef Netif
10.0.90.12/30 user 0 ulst 262144 6
ucst 345 5 so-0/0/1.0
ucst 339 2 so-0/0/2.0
Meaning
The sample output from transit router R2 for the show route forwarding-table destination command shows unilist (ulst) in the Type field, indicating that load balancing is working. A packet sent to this next hop (R2) goes to any next hop in the unicast (ucst) list, so-0/0/1.0 and so-0/0/2.0.
Sample Output
The following sample output is for transit router R2:
user@R2> monitor interface traffic R2 Seconds: 123 Time: 21:28:29 Interface Link Input packets (pps) Output packets (pps) so-0/0/0 Up 0 (0) 0 (0) so-0/0/1 Up 95 (0) 50012 (1) so-0/0/2 Up 100132 (19) 50217 (0) so-0/0/3 Up 0 (0) 0 (0) fe-0/1/0 Up 100127 (17) 100128 (1) fe-0/1/1 Up 0 (0) 0 (0) fe-0/1/2 Up 0 (0) 0 (0) fe-0/1/3 Up 0 (0) 0 (0) [...Output truncated...]
Meaning
The sample output from transit router R2 for the monitor interface traffic command shows that traffic is balanced across interfaces so-0/0/1.0 and so-0/0/2.0.
Sample Output
The following sample output is for transit router R2:
user@R2> show mpls lsp statistics Ingress LSP: 0 sessions Total 0 displayed, Up 0, Down 0 Egress LSP: 0 sessions Total 0 displayed, Up 0, Down 0 Transit LSP: 5 sessions To From State Packets Bytes LSPname 192.168.0.1 192.168.1.1 Up 24874 2188912 lsp1 192.168.0.1 192.168.1.1 Up 24471 2153448 lsp2 192.168.0.1 192.168.1.1 Up 25613 2253944 lsp3 192.168.0.1 192.168.1.1 Up 25042 2203696 lsp4 192.168.1.1 192.168.0.1 Up 0 0 r0-r1 Total 5 displayed, Up 5, Down 0
Meaning
The sample output from transit router R2 for the show mpls lsp statistics command shows that traffic is balanced across the four LSPs (lsp1, lsp2, lsp3, and lsp4) transiting R2.
