Nokia Network Voyager for IPSO 4.0 Reference Guide 433
5. In the Nexthop field, click on next to EBGP Multihop to enable the multihop option; then
click Apply.
6. (Optional) Enter a value in the TTL text box to set the number of hops over which the EBGP
multihop session is established. The default value is 64 and the range is 1 to 255. Click
Apply.
Configuring an EBGP Peer on Platform B
1. Configure an EBGP peer on Nokia Platform B as in “Ethernet Interfaces.”
2. Enter
5.6.7.8 as the local address on the main BGP configuration page.
3. Configure the inbound and route redistribution policies.
4. Click the link for specific peer you configured in Step 1. This action takes you the page that
lets you configure options for that peer.
5. In the Nexthop field, click on next to EBGP Multihop to enable the multihop option, and
then click Apply.
6. (Optional) Enter a value in the TTL text box to set the number of hops over which the EBGP
multihop session is established.
The default value is 64 and the range is 1 to 255.
7. Click Apply.
Verification
To verify that you have configured load balancing correctly, run the following commands in
iclid:
show bgp neighbor
show route bgp
For more information on these commands, see “Viewing Routing Protocol Information.”.
Adjusting BGP Timers Example
1. Configure a BGP neighbor as in the “BGP Neighbors Example.”
2. Click the link for the peer IP address to configure peer-specific parameters.
3. Enter a value in seconds in the Holdtime text box.
Holdtime indicates the maximum number of seconds that can elapse between the receipt of
successive keepalive or update messages by the sender before the peer is declared dead. It
must be either zero (0) or at least 3 seconds.
The default value is 180 seconds.
4. Enter a value in seconds in the Keepalive text box; then click Apply.
BGP does not use any transport-protocol-based keepalive mechanism to determine whether
peers are reachable. Instead, keepalive messages are exchanged between peers to determine
whether the peer is still reachable.