Specifying an aggregate interface as the outbound interface when configuring a static route does not work

If a static route is registered per interface (RAGG10.530), then the route does not work.

  Example:

  ip route-static vpn-instance L3VPN_XXX_VPN 10.8.xxx.0 24 Route-Aggregation10.530

If you specify a specific p2p ip address when configuring a static route, then the static route is processed.

  Example:

  ip route-static vpn-instance L3VPN_XXX_VPN 10.8.xxx.0 24 10.xx.1xx.2

When configuring static routes, you can specify the outbound interface or next-hop address as needed. Note that:

· For point-to-point interfaces, you can specify only the outbound interface without specifying the next-hop address during configuration. In this way, there is no need to change the configuration even if the peer address changes.

· For interfaces such as NBMA and P2MP, it is necessary to map the IP address to the link layer address. It is recommended to configure both the outbound interface and the next-hop IP address.

· For broadcast interfaces such as Ethernet interfaces and VLAN interfaces, because there may be multiple next-hops, both the outbound interface and the next-hop must be specified during configuration.

RAGG10.530 is not a point-to-point interface, so you need to specify both the interface and the IP address when specifying a static route.