User manual SMC ES4710BD

[. . . ] ES4700 Series Chassis Core Routing Switch 1 www. smc. com Preface ES4700 Series Chassis Core Routing Switch is a high performance routing switch released by SMC Networks that can be deployed as the core layer device for campus and enterprise networks, or as an aggregation device for IP metropolitan area networks (MAN). ES4700 Series Chassis Core Routing Switch provides 4 and 10 slots, with support for various types of line cards and can seamlessly support a variety of network interfaces from 100Mb, 1000Mb to 10 GB Ethernet. We are providing this manual for your better understanding, use and maintenance of the ES4700 Series Chassis Core Routing Switch. We strongly recommend you to read through this manual carefully before installation and configuration to avoid possible malfunction or damage to the switch. [. . . ] The entry with the highest priority (smallest value) becomes the current best route. The user can configure several routes of different priority to the same destination; layer3 switch will choose one route for IP package forwarding according to the priority order. To avoid too large route table, a default route can be set. Once route table lookup fails, the default route will be chosen for forwarding packages. The table below describes the routing protocols supported by ES4700 series and the default route lookup priority value. Routing Protocols or Direct route OSPF Static route RIP route type Default priority value 0 110 1 120 373 OSPF ASE IBGP EBGP Unknown route 150 200 20 255 14. 2 IP Routing Policy 14. 2. 1 Introduction To Routing Policy Some policies have to be applied when the router publishing and receiving routing messages so to filter routing messages, such as only receiving or publishing routing messages meets the specified conditions. A routing protocol maybe need redistribute other routing messages found by other protocols such as OSPF so to increase its own routing knowledge; when the router redistributing routing messages from other routing protocols there may be only part of the qualified routing messages is needed, and some properties may have to be configured to suit this protocol. To achieve routing policy, first we have to define the characteristics of the routing messages to be applied with routing policies, namely define a group matching rules. We can configure by different properties in the routing messages such as destination address, the router address publishing the routing messages. The matching rules can be previously configured to be applied in the routing publishing, receiving and distributing policies. Five filters are provided in ES4700 series: route-map, acl, as-path, community-list and ip-prefix for use. We will introduce each filter in following sections: 1. route-map For matching certain properties of the specified routing information and setting some routing propertities when the conditions are fulfilled. Route-map is for controlling and changing the routing messages while also controlling the redistribution among routes. A route-map consists of a series of match and set commands in which the match command specifies the conditions required matching, and the set command specifies the actions to be taken when matches. The route-map is also for controlling route publishing among different route process. It can also used on policy routing which select different routes for the messages other than the shortest route. A group matches and set clauses make up a node. A route-map may consist of several nodes each of which is a unit for matching test. We match among nodes with by sequence-number. The matching objects are some 374 properties of routing messages. Different match clause in the same node is "and" relation logically, which means the matching test of a node, will not be passed until conditions in its entire match clause are matched. [. . . ] When the heartbeat packets are received again, the holdtime is reset. If no heartbeat packets are received in the holdtime, the cluster is invalid. 855 Command mode: Global Mode Default: The holdtime of heartbeat is 80 seconds by default. Instructions: In the commander switch, this command is used to set the holdtime of heartbeat. And this information is distributed to all the member switches. [. . . ]