3Com 4210, 5500G, 4200G Configuration Procedure Configure the switches, Configure the hosts

94CHAPTER 15: ROUTING CONFIGURATION GUIDE

Product series	Software version	Hardware version
Switch 4500	Release V03.03.00	All versions

Configuration Procedure Configure the switches:

■Configure static routes on Switch A.

<SwitchA> system-view

[SwitchA] ip route-static 1.1.3.0 255.255.255.0 1.1.2.2

[SwitchA] ip route-static 1.1.4.0 255.255.255.0 1.1.2.2

[SwitchA] ip route-static 1.1.5.0 255.255.255.0 1.1.2.2

■Configure static routes on Switch B.

<SwitchB> system-view

[SwitchB] ip route-static 1.1.2.0 255.255.255.0 1.1.3.1

[SwitchB] ip route-static 1.1.5.0 255.255.255.0 1.1.3.1

[SwitchB] ip route-static 1.1.1.0 255.255.255.0 1.1.3.1

■Configure static routes on Switch C.

<SwitchC> system-view

[SwitchC] ip route-static 1.1.1.0 255.255.255.0 1.1.2.1

[SwitchC] ip route-static 1.1.4.0 255.255.255.0 1.1.3.2

Configure the hosts:

#Configure the default gateway of Host A as 1.1.5.1. Detailed configuration procedure is omitted.

#Configure the default gateway of Host B as 1.1.4.1. Detailed configuration procedure is omitted.

#Configure the default gateway of Host C as 1.1.1.1. Detailed configuration procedure is omitted.

Complete Configuration ■ Perform the following configuration on Switch A.

#

ip route-static 1.1.3.0 255.255.255.0 1.1.2.2 preference 60 ip route-static 1.1.4.0 255.255.255.0 1.1.2.2 preference 60 ip route-static 1.1.5.0 255.255.255.0 1.1.2.2 preference 60

■Perform the following configuration on Switch B.

#

ip route-static 1.1.2.0 255.255.255.0 1.1.3.1 preference 60 ip route-static 1.1.5.0 255.255.255.0 1.1.3.1 preference 60 ip route-static 1.1.1.0 255.255.255.0 1.1.3.1 preference 60

■Perform the following configuration on Switch C.

#

ip route-static 1.1.1.0 255.255.255.0 1.1.2.1 preference 60 ip route-static 1.1.4.0 255.255.255.0 1.1.3.2 preference 60

Precautions Note the following when configuring a static route:

■If the nexthop of a static route is indirectly connected, the static route takes effect (that is, it is installed into the routing table) only if a route to the nexthop exists in the routing table.