3Com 3C13636 Configuration Manual page 673

3Com Router 3000 Ethernet Family
Configuration Guide
Table 6-13 Configure to take the local address as the next-hop in advertising a route
Configure itself as the next hop in
advertising a route
Disable itself from being the next hop in
advertising a route
By default, the local router does not take its address as the next-hop, when it advertises
route to a peer group.
Note: If BGP load balancing is configured, no matter the peer next-hop-local
command is configured or not, the local router will take its address as the next-hop
when it advertises a route to an IBGP peer group.
XII. Configuring not to carry private AS numbers inforwarding BGP updates
Generally speaking, BGP carries AS numbers (either public or private) when it forwards
BGP updates. In order for some egress routers to ignore private AS numbers while
sending updates, you can configure to make them carry no private AS numbers when
forwarding BGP updates.
Table 6-14 Configure not to carry private AS numbers in forwarding BGP updates
Configure not to carry private AS
numbers in forwarding BGP updates
Configure to carry private AS number in
forwarding BGP updates
By default, AS numbers are carried when BGP updates are forwarded.
XIII. Specifying the source interface for route updates
For updates to be forwarded in case the interface for them experiences a failure, you
can configure to enable the internal BGP session to use any interface on which a TCP
connection can be established with the peer. The Loopback interface is usually used for
the purpose.
Table 6-15 Specify the source interface for route updates
Specify the source interface for route
updates
Operation
Operation
Operation
3Com Corporation
6-8
Chapter 6 BGP Configuration
Command
peer group-name next-hop-local
undo peer group-name next-hop-local
Command
peer group-name public-as-only
undo peer group-name public-as-only
Command
peer { group-name | peer-address }
connect-interface
interface-number
interface-type