White Papers

Version Description
9.14(0.0) Introduced on the C9010, MXL, FN IOM, S3100 series, S3048–ON, S4048–ON,
S4048T-ON, S5048F-ON, S6000, S6010–ON, S6100–ON, Z9100–ON, and S6000–
ON.
Usage
Information
The peer remains in idle state based on the configured idle holdtime. The less the idle holdtime,
less the peer in idle state.
For the new idle holdtime to take effect, you need to shutdown the respective peer manually using
neighbor shutdown command and enable the peer again.
neighbor update-source
Enable the E-Series software to use Loopback interfaces for TCP connections for BGP sessions.
Syntax
neighbor {ip-address | peer-group-name} update-source interface
To use the closest interface, use the no neighbor {ip-address | peer-group-name}
update-source interface command.
Parameters
ip-address Enter the IP address of the peer router in dotted decimal format.
peer-group-name Enter the name of the peer group to disable all routers within the peer group.
interface Enter the keyword loopback then a number of the Loopback interface. The range
is from 0 to 16383.
Defaults Not configured.
Command Modes ROUTER BGP
Command
History
This guide is platform-specific. For command information about other platforms, see the relevant Dell
EMC Networking OS Command Line Reference Guide.
Version Description
9.10(0.1) Introduced on the S6010-ON and S4048T-ON.
9.10(0.0) Introduced on the S3148.
9.10(0.0) Introduced on the S6100-ON.
9.8(2.0) Introduced on the S3100 series.
9.8(1.0) Introduced on the Z9100–ON.
9.8(0.0P5) Introduced on the S4048-ON.
9.8(0.0P2) Introduced on the S3048-ON.
9.7(0.0) Introduced on the S6000–ON.
9.2(1.0) Introduced on the Z9500.
9.0.2.0 Introduced on the S6000.
8.3.19.0 Introduced on the S4820T.
8.3.11.1 Introduced on the Z9000.
8.3.7.0 Introduced on the S4810.
7.8.1.0 Introduced on the S-Series.
7.7.1.0 Introduced on the C-Series.
Usage
Information
Loopback interfaces are up constantly and the BGP session may need one interface constantly up
to stabilize the session. The neighbor update-source command is not necessary for directly
connected internal BGP sessions.
400 Border Gateway Protocol