HP 5500 Ei 5500 Si Switch Series Configuration Guide
Have a look at the manual HP 5500 Ei 5500 Si Switch Series Configuration Guide online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 1114 HP manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.
42 Configuring an additional metric for a RIP interface Network requirements I n t h e fo l l owi n g fi g u re, R I P i s e n a b l e d o n a l l t h e i n t e r fa c e s o f Swi tch A , Swi t ch B, Swi tch C , Swi tch D, a n d Switch E. The switches are interconnected through RIPv2. Swi t c h A h a s t w o l i n k s t o Swi t c h D. T h e l i n k f ro m Swi t c h B t o Swi t c h D i s m o re s t a b l e t h a n t h a t f ro m Swi t c h C to Switch D. Configure an additional metric for RIP routes received through VLAN-interface 200 on Switch A so that Switch A prefers the 1.1.5.0/24 network learned from Switch B. Figure 12 Network diagram Configuration procedure 1. Configure IP addresses for the in terfaces. (Details not shown.) 2. Configure RIP basic functions: # Configure Switch A. system-view [SwitchA] rip 1 [SwitchA-rip-1] network 1.0.0.0 [SwitchA-rip-1] version 2 [SwitchA-rip-1] undo summary [SwitchA-rip-1] quit # Configure Switch B. system-view [SwitchB] rip 1 [SwitchB-rip-1] network 1.0.0.0 [SwitchB-rip-1] version 2 [SwitchB-rip-1] undo summary # Configure Switch C. system-view [SwitchB] rip 1 [SwitchC-rip-1] network 1.0.0.0 [SwitchC-rip-1] version 2 [SwitchC-rip-1] undo summary # Configure Switch D. system-view [SwitchD] rip 1 [SwitchD-rip-1] network 1.0.0.0 [SwitchD-rip-1] version 2
43 [SwitchD-rip-1] undo summary # Configure Switch E. system-view [SwitchE] rip 1 [SwitchE-rip-1] network 1.0.0.0 [SwitchE-rip-1] version 2 [SwitchE-rip-1] undo summary # Display the IP routing table of Switch A. [SwitchA] display rip 1 database 1.0.0.0/8, cost 0, ClassfulSumm 1.1.1.0/24, cost 0, nexthop 1.1.1.1, Rip-interface 1.1.2.0/24, cost 0, nexthop 1.1.2.1, Rip-interface 1.1.3.0/24, cost 1, nexthop 1.1.1.2 1.1.4.0/24, cost 1, nexthop 1.1.2.2 1.1.5.0/24, cost 2, nexthop 1.1.1.2 1.1.5.0/24, cost 2, nexthop 1.1.2.2 The output shows that two RIP routes can reach network 1.1.5.0/24. Their next hops are Switch B (1.1.1.2) and Switch C (1.1.2.2) respectively, with the same cost of 2. Switch C is the next hop router to reach network 1.1.4.0/24, with a cost of 1. 3. Configure an additional metric for the RIP interface: # Configure an additional metric of 3 for VLAN-interface 200 on Switch A. [SwitchA] interface vlan-interface 200 [SwitchA-Vlan-interface200] rip metricin 3 [SwitchA-Vlan-interface200] display rip 1 database 1.0.0.0/8, cost 0, ClassfulSumm 1.1.1.0/24, cost 0, nexthop 1.1.1.1, Rip-interface 1.1.2.0/24, cost 0, nexthop 1.1.2.1, Rip-interface 1.1.3.0/24, cost 1, nexthop 1.1.1.2 1.1.4.0/24, cost 2, nexthop 1.1.1.2 1.1.5.0/24, cost 2, nexthop 1.1.1.2 The output shows that only one RIP route reaches network 1.1.5.0/24, with the next hop as Switch B (1.1.1.2) and a cost of 2. Configuring RIP to advertise a summary route Network requirements In the following figure, Switch A and Switch B run OSPF, Switch D runs RIP, and Switch C runs OSPF and RIP. Configure RIP to redistribute OSPF routes on Switch C so that Switch D has routes destined for networks 1 0 .1.1. 0 / 2 4 , 1 0 . 2 .1. 0 / 2 4 , 1 0 . 5 .1. 0 / 2 4 , a n d 1 0 . 6 .1. 0 / 2 4 . Configure route summarization on Switch C and advertise only the summary route 10.0.0.0/8, reducing the routing table size of Switch D.
44 Figure 13 Network diagram Configuration procedure 1. Configure IP addresses for inte rfaces. (Details not shown.) 2. Configure OSPF basic functions: # Configure Switch A. system-view [SwitchA] ospf [SwitchA-ospf-1] area 0 [SwitchA-ospf-1-area-0.0.0.0] network 10.5.1.0 0.0.0.255 [SwitchA-ospf-1-area-0.0.0.0] network 10.2.1.0 0.0.0.255 [SwitchA-ospf-1-area-0.0.0.0] quit # Configure Switch B. system-view [SwitchB] ospf [SwitchB-ospf-1] area 0 [SwitchB-ospf-1-area-0.0.0.0] network 10.1.1.0 0.0.0.255 [SwitchB-ospf-1-area-0.0.0.0] network 10.6.1.0 0.0.0.255 [SwitchB-ospf-1-area-0.0.0.0] quit # Configure Switch C. system-view [SwitchC] ospf [SwitchC-ospf-1] area 0 [SwitchC-ospf-1-area-0.0.0.0] network 10.1.1.0 0.0.0.255 [SwitchC-ospf-1-area-0.0.0.0] network 10.2.1.0 0.0.0.255 [SwitchC-ospf-1-area-0.0.0.0] quit 3. Configure RIP basic functions: # Configure Switch C. system-view [SwitchC] rip 1 [SwitchC-rip-1] network 11.3.1.0 [SwitchC-rip-1] version 2 [SwitchC-rip-1] undo summary # Configure Switch D. system-view
45 [SwitchD] rip 1 [SwitchD-rip-1] network 11.0.0.0 [SwitchD-rip-1] version 2 [SwitchD-rip-1] undo summary [SwitchD-rip-1] quit # Configure RIP to redistribute the routes from OSPF process 1 and direct routes on Switch C. [SwitchC-rip-1] import-route direct [SwitchC-rip-1] import-route ospf 1 # Display the routing table information of Switch D. [SwitchD] display ip routing-table Routing Tables: Public Destinations : 10 Routes : 10 Destination/Mask Proto Pre Cost NextHop Interface 10.1.1.0/24 RIP 100 1 11.3.1.1 Vlan300 10.2.1.0/24 RIP 100 1 11.3.1.1 Vlan300 10.5.1.0/24 RIP 100 1 11.3.1.1 Vlan300 10.6.1.0/24 RIP 100 1 11.3.1.1 Vlan300 11.3.1.0/24 Direct 0 0 11.3.1.2 Vlan300 11.3.1.2/32 Direct 0 0 127.0.0.1 InLoop0 11.4.1.0/24 Direct 0 0 11.4.1.2 Vlan400 11.4.1.2/32 Direct 0 0 127.0.0.1 InLoop0 127.0.0.0/8 Direct 0 0 127.0.0.1 InLoop0 127.0.0.1/32 Direct 0 0 127.0.0.1 InLoop0 4. Configure route summarization on Switch C and advertise only the summary route 10.0.0.0/8: [SwitchC] interface vlan-interface 300 [SwitchC-Vlan-interface300] rip summary-address 10.0.0.0 8 # Display the routing table information of Switch D. [SwitchD] display ip routing-table Routing Tables: Public Destinations : 7 Routes : 7 Destination/Mask Proto Pre Cost NextHop Interface 10.0.0.0/8 RIP 100 1 11.3.1.1 Vlan300 11.3.1.0/24 Direct 0 0 11.3.1.2 Vlan300 11.3.1.2/32 Direct 0 0 127.0.0.1 InLoop0 11.4.1.0/24 Direct 0 0 11.4.1.2 Vlan400 11.4.1.2/32 Direct 0 0 127.0.0.1 InLoop0 127.0.0.0/8 Direct 0 0 127.0.0.1 InLoop0 127.0.0.1/32 Direct 0 0 127.0.0.1 InLoop0
46 RIP FRR configuration example Network requirements Switch S, Switch A, and Switch D are interconnected through RIPv2, as illustrated in Figure 14. C onfigure RIP FRR so that when Link A between Switch S and Switch D fails, services can be switched to Link B immediately. Figure 14 Network diagram Configuration procedure 1. Configure IP addresses for the interfaces on each switch and configure RIPv2: Follow Figure 14 to c onfigure the IP address and subnet mask of each interface on the switches. (Details not shown.) Configure RIPv2 on the switches, ensuring that Switch A, Switch D, and Switch S can communicate with each other at Layer 3. (Details not shown.) 2. Configure RIP FRR: # Configure Switch S. system-view [SwitchS] bfd echo-source-ip 1.1.1.1 [SwitchS] ip ip-prefix abc index 10 permit 4.4.4.4 32 [SwitchS] route-policy frr permit node 10 [SwitchS-route-policy] if-match ip-prefix abc [SwitchS-route-policy] apply fast-reroute backup-interface vlan-interfac\ e 100 backup-nexthop 12.12.12.2 [SwitchS-route-policy] quit [SwitchS] rip 1 [SwitchS-rip-1] fast-reroute route-policy frr [SwitchS-rip-1] quit # Configure Switch D. system-view [SwitchD] bfd echo-source-ip 4.4.4.4 [SwitchD] ip ip-prefix abc index 10 permit 1.1.1.1 32 [SwitchD] route-policy frr permit node 10 [SwitchD-route-policy] if-match ip-prefix abc [SwitchD-route-policy] apply fast-reroute backup-interface vlan-interfac\ e 101 backup-nexthop 24.24.24.2 [SwitchD-route-policy] quit [SwitchD] rip 1 [SwitchD-rip-1] fast-reroute route-policy frr Switch S Switch D Switch A Loop 0 1.1.1.1/32 V l a n-i n t1 0 0 1 2 . 1 2 . 1 2. 1 /2 4 Vlan-int200 13.13.13.1/24 Vlan-int200 13.13.13.2/24 V la n - in t 1 0 0 1 2.1 2.1 2.2 /2 4 V la n- in t 1 01 2 4 .2 4 .2 4 .2 / 2 4 V la n -in t1 0 1 2 4 .2 4 .2 4 .4 / 2 4 Loop 0 4.4.4.4/32 Link A Link B
47 [SwitchD-rip-1] quit47 3. Verify the configuration: # Display route 4.4.4.4/32 on Switch S and you can view the backup next hop information. [SwitchS] display ip routing-table 4.4.4.4 verbose Routing Table : Public Summary Count : 1 Destination: 4.4.4.4/32 Protocol: RIP Process ID: 1 Preference: 100 Cost: 1 IpPrecedence: QosLcId: NextHop: 13.13.13.2 Interface: vlan200 BkNextHop: 12.12.12.2 BkInterface: vlan100 RelyNextHop: 0.0.0.0 Neighbor : 0.0.0.0 Tunnel ID: 0x0 Label: NULL BKTunnel ID: 0x0 BKLabel: NULL State: Active Adv Age: 00h01m27s Tag: 0 # Display route 1.1.1.1/32 on Switch D. You can find the backup next hop information. [SwitchD] display ip routing-table 1.1.1.1 verbose Routing Table : Public Summary Count : 1 Destination: 1.1.1.1/32 Protocol: RIP Process ID: 1 Preference: 100 Cost: 1 IpPrecedence: QosLcId: NextHop: 13.13.13.1 Interface: vlan200 BkNextHop: 24.24.24.2 BkInterface: vlan101 RelyNextHop: 0.0.0.0 Neighbor : 0.0.0.0 Tunnel ID: 0x0 Label: NULL BKTunnel ID: 0x0 BKLabel: NULL State: Active Adv Age: 00h01m27s Tag: 0 Configuring BFD for RIP (single-hop detection in BFD echo packet mode) Network requirements In the following figure, Switch A and Switch C are interconnected through a Layer 2 switch. VLAN-interface 100 of the two switches runs RIP process 1, BFD is enabled on VLAN-interface 100 of Switch A. Switch A is connected to Switch C through Switch B. VLAN-interface 200 on Switch A runs RIP process 2; VLAN-interface 300 on Switch C, and VLAN-interface 200 and VLAN-interface 300 on Switch B run RIP process 1.
48 Configure a static route and enable static route redistribution into RIP on Switch C. Switch A learns the static route sent by Switch C, the outbound interface of the route is the interface connected to the Layer 2 switch. Configure BFD so that when the link between Switch C and the Layer 2 switch fails, BFD can quickly detect the link failure and notify it to RIP, and the BFD session goes down. In response, RIP deletes the neighbor relationship with Switch C and the route information received from Switch C. Then, Switch A learns the static route sent by Switch C with the outbound interface being the interface connected to Switch B. Figure 15 Network diagram Configuration procedure 1. Configure IP addresses for inte rfaces. (Details not shown.) 2. Configure RIP basic functions: # Configure Switch A. [SwitchA] rip 1 [SwitchA-rip-1] network 192.168.1.0 [SwitchA-rip-1] quit [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] rip bfd enable [SwitchA-Vlan-interface100] quit [SwitchA] rip 2 [SwitchA-rip-2] network 192.168.2.0 # Configure Switch B. [SwitchB] rip 1 [SwitchB-rip-1] network 192.168.2.0 [SwitchB-rip-1] network 192.168.3.0 [SwitchB-rip-1] quit # Configure Switch C. [SwitchC] rip 1 [SwitchC-rip-1] network 192.168.1.0 [SwitchC-rip-1] network 192.168.3.0 [SwitchC-rip-1] import-route static [SwitchC-rip-1] quit 3. Configure BFD parameters:
49 # Configure Switch A. [SwitchA] bfd session init-mode active [SwitchA] bfd echo-source-ip 11.11.11.11 [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] bfd min-transmit-interval 500 [SwitchA-Vlan-interface100] bfd min-receive-interval 500 [SwitchA-Vlan-interface100] bfd detect-multiplier 7 [SwitchA-Vlan-interface100] quit [SwitchA] quit 4. Configure a static route on Switch C: [SwitchC] ip route-static 100.1.1.1 24 null 0 5. Verify the configuration: # Display the BFD session information of Switch A. display bfd session Total Session Num: 1 Init Mode: Active Session Working Under Echo Mode: LD SourceAddr DestAddr State Holdtime Interfa\ ce 5 192.168.1.1 192.168.1.2 Up 2000ms Vlan100\ # Display the RIP route 100.1.1.0/24 learned by Switch A. display ip routing-table 100.1.1.0 24 verbose Routing Table : Public Summary Count : 2 Destination: 100.1.1.0/24 Protocol: RIP Process ID: 1 Preference: 100 Cost: 1 IpPrecedence: QosLcId: NextHop: 192.168.1.2 Interface: vlan-interface 100 BkNextHop: 0.0.0.0 BkInterface: RelyNextHop: 0.0.0.0 Neighbor : 192.168.1.2 Tunnel ID: 0x0 Label: NULL BKTunnel ID: 0x0 BKLabel: NULL State: Active Adv Age: 00h00m47s Tag: 0 Destination: 100.1.1.0/24 Protocol: RIP Process ID: 2 Preference: 100 Cost: 2 IpPrecedence: QosLcId: NextHop: 192.168.2.2 Interface: vlan-interface 200 BkNextHop: 0.0.0.0 BkInterface: RelyNextHop: 0.0.0.0 Neighbor : 192.168.2.2 Tunnel ID: 0x0 Label: NULL BKTunnel ID: 0x0 BKLabel: NULL State: Inactive Adv Age: 00h12m50s Tag: 0 # Enable RIP event debugging on Switch A. debugging rip 1 event terminal debugging
50 # When the link between Switch C and the Layer 2 switch fails, Switch A can quickly detect the change. %Jan 19 10:41:51:203 2008 SwitchA BFD/4/LOG:Sess[192.168.1.1/192.168.1.2\ , Vlan-interface 100,Ctrl], Sta: UP->DOWN, Diag: 1 *Jan 19 10:33:12:813 2008 SwitchA RM/6/RMDEBUG: RIP-BFD: Message Type Disable, Connect Type Direct-connect, Pkt Type Echo, Src IP Address 192.168.1.1, Src IFIndex4, Nbr IP Address 192.168.1.2. # Display the BFD information of Switch A. Switch A has deleted the neighbor relationship with Switch C and no output is displayed. display bfd session # Display the RIP routes of RIP process 1 on Switch A. The RIP route learned from Switch C is no longer existent. display rip 1 route Route Flags: R - RIP, T - TRIP P - Permanent, A - Aging, S - Suppressed, G - Garbage-coll\ ect -----------------------------------------------------------------------\ ----- # Display the RIP route 100.1.1.0/24 learned on Switch A. display ip routing-table 100.1.1.0 24 verbose Routing Table : Public Summary Count : 1 Destination: 100.1.1.0/24 Protocol: RIP Process ID: 2 Preference: 100 Cost: 2 IpPrecedence: QosLcId: NextHop: 192.168.2.2 Interface: vlan-interface 200 BkNextHop: 0.0.0.0 BkInterface: RelyNextHop: 0.0.0.0 Neighbor : 192.168.2.2 Tunnel ID: 0x0 Label: NULL BKTunnel ID: 0x0 BKLabel: NULL State: Active Adv Age: 00h18m40s Tag: 0 Configuring BFD for RIP (bidirectional detection in BFD control packet mode) Network requirements In the following figure, Switch A is connected to Switch C through Switch B. VLAN-interface 100 on Switch A, VLAN-interface 200 on Switch C, and VLAN-interface 200 and VLAN-interface 100 on Switch B run RIP process 1. Configure a static route to Switch C on Switch A, an d configure a static route to Switch A on Switch C. Enable BFD on VLAN-interface 100 of Switch A and VLAN-interface 200 of Switch C. Switch A is connected to Switch C through Switch D. VLAN-interface 300 on Switch A runs RIP process 2; VLAN-interface 400 on Switch C, and VLAN-interface 300 and VLAN-interface 400 on Switch D run RIP process 1.
51 Enable static route redistribution into RIP on Switch A and Switch C so that Switch A and Switch C have routes to send to each other. Switch A learns the static route sent by Switch C, the outbound interface is the interface connected to Switch B. Configure BFD so that when the link between Switch B and Switch C fails, BFD can quickly detect the link failure and notify it to RIP, and the BFD session goes down. In response, RIP deletes the neighbor relationship with Switch C and the route information received from Switch C. Then, Switch A learns the static route sent by Switch C, the outbound interface of the route is the interface connected to Switch D. Figure 16 Network diagram Configuration procedure 1. Configure IP addresses for inte rfaces. (Details not shown.) 2. Configure RIP basic functions and enable static rout e redistribution into RIP so that Switch A and Switch C have routes to send to each other: # Configure Switch A. [SwitchA] rip 1 [SwitchA-rip-1] network 192.168.1.0 [SwitchA-rip-1] peer 192.168.2.2 [SwitchA-rip-1] undo validate-source-address [SwitchA-rip-1] import-route static [SwitchA-rip-1] quit [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] rip bfd enable [SwitchA-Vlan-interface100] quit [SwitchA] rip 2 [SwitchA-rip-2] network 192.168.3.0 [SwitchA-rip-2] quit # Configure Switch C. [SwitchC] rip 1 [SwitchC-rip-1] network 192.168.2.0 [SwitchC-rip-1] network 192.168.4.0 [SwitchC-rip-1] peer 192.168.1.1 [SwitchC-rip-1] undo validate-source-address [SwitchC-rip-1] import-route static