The ipv4 adjacency command configures a static adjacency segment ID (SID) for the segment routing connection to be established between the local and remote interfaces.
The undo ipv4 adjacency command deletes the static adjacency SID configured for the segment routing connection to be established between the local and remote interfaces.
By default, no static adjacency SID is configured for the segment routing connection to be established between the local and remote interfaces.
| Parameter | Description | Value |
|---|---|---|
| remote-ip-addr remote-ip-address |
Specifies the IP address of the remote interface. |
The value is in dotted decimal notation. |
| sid sid-value |
Specifies a static adjacency SID. |
The value is an integer that ranges from 284688 to 294927. |
| local-ip-addr local-ip-address |
Specifies the IP address of the local interface. |
The value is in dotted decimal notation. |
Usage Scenario
After Segment Routing is enabled, an adjacency SID needs to be configured for the segment routing link to be established between the local and remote interfaces.
Configuration Impact
Running the command may cause the tunnel to go Down.
Precautions
If no direct route corresponding to local-ip-addr local-ip-address exists on the device, no entry is generated after this command is run.
SIDs can be repeatedly used. If multiple adjacencies are configured with the same static SID, the SIDs are called parallel adjacency SIDs, which can be flooded through IS-IS, advertised to BGP LS, and then reported to the controller through BGP LS. Currently, a maximum of six static SIDs can be configured for an adjacency.In VS mode, this command is supported only by the admin VS.