After a device's sub-interfaces or VLANIF interfaces have static ARP entries configured or dynamically learn ARP entries, the device generates a type of 32-bit host route according to ARP entries if the arp direct-route enable command is executed to configure the ARP module of the device to report IPv4 ARP Vlink direct routes to the RM module. This type of 32-bit host route is called IPv4 ARP Vlink direct route.
By default, IPv4 ARP Vlink direct routes are only used to guide local traffic forwarding. To control the routing table size and ensure routing table stability, devices are prohibited from redistributing these direct routes into dynamic routing protocols. In some situations, however, devices need to perform operations based on specific routes. For example, a device needs to direct remote traffic for different users using different export policies. Subsequently, the device needs to redistribute IPv4 ARP Vlink direct routes into dynamic routing protocols and advertises them to the remote end.
Only the S5720-EI, S5720-HI, S5730-HI, S5731-H, S5731-S, S5731S-H, S5731S-S, S5732-H, S6720-EI, S6720-HI, S6720S-EI, S6730-H, S6730S-H, S6730-S, and S6730S-S support the configuration of the advertisement of IPv4 ARP Vlink direct routes.
Before configuring the advertisement of IPv4 ARP Vlink direct routes, set link layer protocol parameters and assign IP addresses to interfaces to ensure that the status of the link layer protocol of the interfaces is Up.
The system view is displayed.
The advertisement of IPv4 ARP Vlink direct routes is configured.
By default, a device does not advertise IPv4 ARP Vlink direct routes.
Currently, apply clauses cannot be used to set route attributes for the routes that match the specified route-policy.
IPv4 ARP Vlink direct routes need to be redistributed into the routing tables of dynamic routing protocols on the device running dynamic routing protocols before these routes are advertised by dynamic routing protocols.