Route Configuration

Context

Campus routes include internal routes and campus egress routes. Internal routes must meet communication requirements of network devices and user hosts on the campus network and enable communication with the external network. It is recommended that you design internal routes based on the gateway location.

• If gateways are deployed at the core layer, you only need to configure routes at the core layer. It is recommended that static routes be used preferentially.
• If gateways are deployed at the aggregation layer, routes need to be deployed at the core and aggregation layers. Routing tables can be dynamically updated along with network topology changes, so an Interior Gateway Protocol (IGP), such as Open Shortest Path First (OSPF), is recommended.

Egress routes must meet requirements of internal terminals for accessing the Internet and WAN. A large- or medium-sized campus network usually has a large number of branches. The egress needs to support multiple links for Internet access and mutual communication between enterprise branches. For this purpose, a large number of routes need to be imported to the campus network. Therefore, you are advised to plan a dynamic routing protocol such as OSPF.

Configuration Tasks