Vip cpu utilization at 99% and acceptor buffer (1)

This type of interface is the most widely used virtual interface, which is used on almost every vro. It is commonly used for the following purposes.
1 As the management address of a vro
After the system administrator completes the network planning, a loopback interface is created for each vro for convenient management, and an IP address is separately specified as the management address on the interface, the Administrator will use this address to remotely log on to the vrotelnet for telnet). This address actually provides a feature similar to a device name.

But there are usually many interfaces and addresses on each vro. Why don't you choose one of them?

The reason is as follows: Because the telnet command uses TCP packets, the following situation may occur: A router interface is down due to a fault, but other interfaces can still be telnet, that is, the TCP connection to this vro still exists. Therefore, the selected telnet address must never be down, and the virtual interface meets this requirement. Because this type of interface does not require interconnection with the peer end, the address of the loopback interface is usually specified as a 32-bit mask to save address resources.
2. Use this interface address as the router id of the Dynamic Routing Protocol OSPF and BGP. During the operation of the Dynamic Routing Protocol OSPF and BGP, you must specify a Router id for the Protocol, it is the unique identifier of the vro and must be unique within the autonomous system. The router id is a 32-bit unsigned integer, which is very similar to the IP address. In addition, the IP address is not repeated, so the router id is usually specified as the address of an interface on the device. Because the IP address of the loopback interface is generally regarded as the router id, it becomes the best choice for the router id.
3. Use this interface address as the source address of the bgp tcp connection. In the BGP protocol, the two routers running BGP establish a neighbor relationship through TCP.

When configuring a neighbor, the loopback interface is often specified as the source address for establishing a TCP connection, which is only used for IBGP. The reason is the same as 2.1, which is to enhance the robustness of the TCP connection)
The configuration command is as follows:
Router id 61.235.66.1
Interface loopback 0
Ip address 61.235.66.1 255.255.255.255
Router bgp 100
Neighbor 61.235.66.7 remote as 200
Neighbor 61.235.66.7 update-source LoopBack0
The value 2 indicates that only two buffers are left. When txacc is lower than "4", Rx. buffering does not queue data packets in MEMD.