Why cannot the router ID of the system be changed by using the router id command take effect in BGP

0

The changed router ID of the system can take effect in BGP only when the reset bgp all command is executed. Then, BGP takes the changed router ID as the new router ID.

Other related questions:
On S series switches, why does the Router ID of the system not take effect after it is changed through the router id command
For S series switches that support BGP, after the system router ID is modified, you need to run the reset bgp all command to make the modification take effect on BGP. BGP then uses the router ID as the new router ID.

WPA/WPA2 has been configured on the AR router successfully but does not take effect
The troubleshooting procedure is as follows: 1. Check whether you have run the dot1x enable command to enable 802.1x authentication globally. 2. Check whether the configuration of WPA/WPA2 is complete. 3. Check whether the user name and password are correct.

Proxy ARP configuration on S series switch
An S series switch, except S1700, supports the following proxy ARP: routed proxy ARP, intra-VLAN proxy ARP, and inter-VLAN proxy ARP, which are configured using the arp-proxy enable, arp-proxy inner-sub-vlan-proxy enable, and arp-proxy inter-sub-vlan-proxy enable commands respectively. Routed proxy ARP (available on all models in V2R5 and later versions, but unavailable on S275x and S5700LI in the versions earlier than V2R5) The destination IP address in the received ARP request packet and the IP address of the inbound interface are in different subnets, but there is a route to the destination IP address and the outbound/inbound interfaces of the route are different. Routed proxy ARP takes effect in this situation. The switch uses its MAC address as the source MAC address to return ARP reply packets. Intra-VLAN proxy ARP (available on all models in V2R5 and later versions, but unavailable on S275x and S5700LI in the versions earlier than V2R5) If the destination IP address of the received ARP request packet and the IP address of the inbound interface are in the same subnet, intra-VLAN proxy ARP takes effect. Inter-VLAN proxy ARP (unavailable on S1720, S2720, S275x, S5700LI and E series switches) It is similar to intra-VLAN proxy ARP. Inter-VLAN proxy ARP takes effect only on super VLAN. If the destination IP address of the received ARP request packet and the IP address of the inbound interface are in the same subnet, inter-VLAN proxy ARP takes effect. If the source and destination are in the same VLAN, inter-VLAN proxy ARP is not required. Regardless of which type of proxy ARP is used, the destination IP address of the received ARP request packet and the IP address of the inbound interface must be in the same subnet.

What should I do when the System Time change does not take effect
Question: Under System > System Settings > Basic Settings > System Time on the RSE6500, change the local system time, save the change, and re-log in to the RSE6500. The system time that is displayed is still the system time before the change. Possible Cause: At the time the system time change is saved, a user runs the shell command to log in to the operating system after having connected to the RSE6500 using Telnet or SSH. Solution: Ask the user to log out of the operating system by running the exit command. Then change the system time and save the change again.

What are the rules for an S series switches to select and refresh router IDs
On an S series switches, the rules for selecting and refreshing router IDs are as follows: If the router id command is executed, the configured router ID is used. If the router id command is not executed and the loopback interfaces with IP addresses configured already exist, the switch selects the largest IP address from the loopback interface addresses as the router ID. If the router id command is not executed and the loopback interfaces with IP addresses configured do not exist, the switch selects the largest IP address from the IP addresses of other interfaces as the router ID. In this case, the Up or Down state of interfaces is not considered. The router ID is reelected only when the interface IP address that is elected as the router ID is deleted or modified. Interface status changes do not result in reelection of the router ID. If the IP address of a non-loopback interface is originally selected as the router ID and currently the IP address of a loopback interface is configured, the router ID will not be reelected. If a larger interface IP address is set, the router ID will not reelected. If the master and slave MPUs are installed on the switch, the system backs up the configured router ID and the router ID selected among interface IP addresses. During system startup, when the protocol attempts to obtain the router ID, the RM may not obtain the information about all interface IP addresses. In this case, a smaller interface IP address may be selected as the router ID to return to the protocol. This is not considered as a problem. When the router ID is changed, you need to manually reset the protocol to obtain a new router ID. The router ID cannot be 0.0.0.0 or 255.255.255.255.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top