BGP Peers Settings
|
Setting |
Description |
|
Destination (Peer) Address |
IP address of the peer router. |
|
Source (Local) Address |
IP address of the PortMaster (source router) to be placed in outgoing packets. |
|
ASN |
Autonomous system number of the peer. If this autonomous system is the same as that of the PortMaster, the peer is an internal peer. If it is different, the peer is an external peer. The autonomous system number is a 16-bit number ranging from 1 to 65535. |
|
Easy Multihome |
If enabled for this peer, applies to a routing method for handling multihome paths from the PortMaster. It restricts the BGP routing table to accept only paths through the remote autonomous system, and optionally through one additional autonomous system. Otherwise, the PortMaster uses Assume Default. Use this feature as an alternative to Accept Policy, Inject Policy, and Advertise Policy. |
|
Assume Default |
If enabled for this peer, which must be an external peer, a default route is created to the peer when it is up. To specify a preferred peer, assign a Hop Count value to each peer with a default route. |
|
Hop Count |
If Assume Default is enabled for multiple external peers, this value, between 1 and 15, assigns a preference to this peer for default route forwarding. The peer with the lowest hop count is preferred. |
|
State |
The status of this peer: up or down. |
|
Confederation Member |
If enabled for this peer, identifies it a member of the same confederation as the active PortMaster. (Disabled by default) |
|
Route Reflector Client |
If enabled for this peer, which must be an internal peer, it is one of a cluster of internal peers that share a common set of route reflectors. The PortMaster forwards internal routes to these clients. (Disabled by default) |
|
Always Next Hop |
If enabled for this peer, the active PortMaster is identified as the next hop in any update packet sent to it from the peer. (Disabled by default) CAUTION! Standard BGP speaker behavior is to forward next hop information to internal peers without modification. The Always Next Hop feature enables this behavior to be changed. Therefore, when using Always Next Hop, take care to ensure that inconsistent routing information is not propagated from the autonomous system. |
|
Accept Policy |
The name of a BGP acceptance policy. The acceptance policy criteria must be met before the PortMaster can accept any IP prefix from this peer as a variable BGP route. You must use the command line interface to create BGP policies. See the PortMaster Command Line Reference for information. |
|
Inject Policy |
The name of a BGP injection policy. The injection policy criteria must be met before the PortMaster places any IP prefex from this peer in the routing table. You must use the command line interface to create BGP policies. See the PortMaster Command Line Reference for information. |
|
Advertise Policy |
The name of a BGP adversisement policy. The advertisement policy criteria must be met before the PortMaster advertises any IP address prefix to this peer. You must use the command lline interface to create BGP policies. See the PortMaster Command Line Reference for information. |