neighbor transport

wangguan

neighbor transport
To enable a TCP transport session option for a Border Gateway Protocol (BGP) session, use the neighbor transport command in address family or router configuration mode. To disable a TCP transport session option for a BGP session, use the no form of this command.
neighbor {ip-address | peer-group-name} transport {connection-mode {active | passive} | path-mtu-discovery | multi-session | single-session}
no neighbor {ip-address | peer-group-name} transport {connection-mode | path-mtu-discovery | multi-session | single-session}
Syntax Description
ip-address
IP address of the BGP neighbor.
peer-group-name
Name of a BGP peer group.
connection-mode
Specifies the type of connection.
active
Specifies an active connection.
passive
Specifies a passive connection.
path-mtu-discovery
Enables TCP transport path maximum transmission unit (MTU) discovery. TCP path MTU discovery is enabled by default.
multi-session
Enables a separate TCP transport session for each address family.
single-session
Enables all address families to use a single TCP transport session.
Command Default
If this command is not configured, TCP path MTU discovery is enabled by default, but no other TCP transport session options are enabled.
Command Modes
Address family configuration
Router configuration
Command History
Release
Modification
12.4
This command was introduced.
12.2(33)SRA
The path-mtu-discovery keyword was added.
12.2(33)SRB
The multi-session and single-session keywords were added.
Usage Guidelines
This command is used to specify various transport options. An active or passive transport connection can be specified for a BGP session. TCP transport path MTU discovery can be enabled to allow a BGP session to take advantage of larger MTU links. Use the show ip bgp neighbors command to determine whether TCP path MTU discovery is enabled.
In Cisco IOS Release 12.2(33)SRB and later releases, options can be specified for the transport of address family traffic using a single TCP session or to enable a separate TCP session for each address family. Multiple TCP sessions are used to support Multi-Topology Routing (MTR), and the single session option is available for backwards compatibility for non-MTR configurations and for scalability purposes.
Examples
The following example shows how to configure the TCP transport connection to be active for a single internal BGP (iBGP) neighbor:
router bgp 45000
neighbor 172.16.1.2 remote-as 45000
neighbor 172.16.1.2 activate
neighbor 172.16.1.2 transport connection-mode active
end
The following example shows how to configure the TCP transport connection to be passive for a single external BGP (eBGP) neighbor:
router bgp 45000
neighbor 192.168.1.2 remote-as 40000
neighbor 192.168.1.2 activate
neighbor 192.168.1.2 transport connection-mode passive
end
The following example shows how to disable TCP path MTU discovery for a single BGP neighbor:
router bgp 45000
neighbor 172.16.1.2 remote-as 45000
neighbor 172.16.1.2 activate
no neighbor 172.16.1.2 transport path-mtu-discovery
end
The following example shows how to reenable TCP path MTU discovery for a single BGP neighbor, if TCP path MTU discovery is disabled:
router bgp 45000
neighbor 172.16.1.2 remote-as 45000
neighbor 172.16.1.2 activate
neighbor 172.16.1.2 transport path-mtu-discovery
end
The following example shows how to enable a separate TCP session for each address family for an MTR topology configuration:
router bgp 45000
scope global
  neighbor 172.16.1.2 remote-as 45000
  neighbor 172.16.1.2 transport multi-session
  address-family ipv4
   topology VIDEO
   bgp tid 100
   neighbor 172.16.1.2 activate
   end


本文来自ChinaUnix博客，如果查看原文请点：http://blog.chinaunix.net/u2/88305/showart_1998994.html