Home > HP > Printer > HP 5500 Ei 5500 Si Switch Series Configuration Guide

HP 5500 Ei 5500 Si Switch Series Configuration Guide

Add to Favourites
    Download as PDF Print this page Share this page

    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+.

    View all the pages
    Page
    of 2513
    Add page 741 to Favourites
    image text
    Enable zoom 
    							 52 
[SwitchC-rip-1] quit 
[SwitchC] interface vlan-interface 200 
[SwitchC-Vlan-interface200] rip bfd enable 
[SwitchC-Vlan-interface200] quit 
# Configure Switch D.  
 system-view 
[SwitchD] rip 1 
[SwitchD-rip-1] network 192.168.3.0 
[SwitchD-rip-1] network 192.168.4.0 
3. Configure BFD parameters: 
# Configure Switch A. 
[SwitchA] bfd session init-mode active 
[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 
# Configure Switch C. 
[SwitchC] bfd session init-mode active 
[SwitchC] interface vlan-interface 200 
[SwitchC-Vlan-interface200] bfd min-transmit-interval 500 
[SwitchC-Vlan-interface200] bfd min-receive-interval 500 
[SwitchC-Vlan-interface200] bfd detect-multiplier 7 
[SwitchC-Vlan-interface200] quit 
4. Configure static routes. 
# Configure a static route to Switch C on Switch A. 
[SwitchA] ip route-static 192.168.2.0 24 vlan-interface 100 192.168.1.2 \
[SwitchA] ip route-static 101.1.1.0 24 null 0 
[SwitchA] quit 
# Configure a static route to Switch A on Switch C. 
[SwitchC] ip route-static 192.168.1.0 24 vlan-interface 200 192.168.2.1 \
[SwitchC] ip route-static 100.1.1.0 24 null 0 
 
 IMPORTANT: 
If you specify null 0 interface as the output interface 
for a static route, do not specify the IP address of a 
directly connected network as the destination IP address. 
 
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 Ctrl Mode: 
 LD/RD         SourceAddr      DestAddr        State Holdtime Interface \
 6/3           192.168.1.1     192.168.2.2     Up    1700ms   vlan100 
# 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
    Add page 742 to Favourites
    image text
    Enable zoom 
    							 53 
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.3.2      Interface: vlan-interface 300 
    BkNextHop: 0.0.0.0        BkInterface: 
  RelyNextHop: 0.0.0.0          Neighbor : 192.168.3.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 
# When the link between Switch B and Switch C fails, Switch A quickly detects the link state 
change. 
%Jan 19 10:41:51:203 2008 SwitchA BFD/4/LOG:Sess[192.168.1.1/192.168.2.2\
, 
Vlan-interface 100, Ctrl], Sta: UP->DOWN, Diag: 1 
*Jan 19 10:41:51:203 2008 SwitchA RM/6/RMDEBUG: RIP-BFD: Message Type Disable, Connect 
Type Indirect-connect, Pkt Type Control, Src IP Address 192.168.1.1, Src IFIndex 4, 
Nbr IP Address 192.168.2.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
    Add page 743 to Favourites
    image text
    Enable zoom 
    							 54 
  Destination: 100.1.1.0/24 
     Protocol: RIP             Process ID: 2 
   Preference: 100                   Cost: 2 
 IpPrecedence:                    QosLcId: 
      NextHop: 192.168.3.2      Interface: vlan-interface 300 
    BkNextHop: 0.0.0.0        BkInterface: 
  RelyNextHop: 0.0.0.0          Neighbor : 192.168.3.2 
    Tunnel ID: 0x0                  Label: NULL 
  BKTunnel ID: 0x0                BKLabel: NULL 
        State: Active Adv             Age: 00h18m40s 
          Tag: 0 
Troubleshooting RIP 
No RIP updates received 
Symptom 
No RIP updates are received when the links function.  
Analysis 
After enabling RIP, you must use the network command to enable corresponding interfaces. Ensure no 
interfaces are disabled from handling RIP messages. 
If the peer is configured to send multicast messag es, the same must be configured on the local end. 
Solution 
1. Use the  display current-configuration  command to check RIP configuration. 
2. Use the  display rip  command to check whether an interface is disabled. 
Route oscillation occurred 
Symptom 
When all links function, route oscillation occurs on the RIP network. After displaying the routing table, you 
may find some routes intermittently appe ar and disappear in the routing table. 
Analysis 
In the RIP network, make sure that all the same timers within the entire network are identical and have 
logical relationships between them. For example, the  timeout timer value must be greater than the update 
timer value.  
Solution 
1.  Use the  display rip  command to check the configuration of RIP timers. 
2. Use the  timers command to adjust timers properly.
    Add page 744 to Favourites
    image text
    Enable zoom 
    							 55 
Configuring OSPF 
Hardware compatibility 
The HP 5500 SI Switch Series does not support OSPF. 
Introduction to OSPF 
O p e n  S ho r tes t Pa t h  Fi rs t  ( OS P F)  i s  a  l i n k  s ta te  i nterior gateway protocol developed by the OSPF working 
group of the IETF. Now, OSPF version 2 (RFC 2328) is used. Unless otherwise noted, OSPF refers to 
OSPFv2 throughout this chapter. The term router in this chapter refers to both routers and Layer 3 
switches.  
OSPF has the following features: 
•   Wide scope —Supports various network sizes and up to several hundred routers in an OSPF routing 
domain. 
•   Fast convergence —Transmits routing updates instantly upon network topology changes. 
•   Loop-free —Computes routes with the shortest path firs t (SPF) algorithm to avoid routing loops. 
•   Area-based network partition —Splits an AS into different area s to facilitate management. In 
addition, routing information transmitted between areas is summarized to reduce traffic and routing 
table sizes. 
•   Equal-cost multi-path (ECMP) routing —Supports multiple equal-cost routes to a destination. 
•   Routing hierarchy —Supports a four-level routing hierarchy that prioritizes routes into intra-area, 
inter-area, external Type-1, and external Type-2 routes. 
•   Authentication —Supports interface-based packet authentica tion to ensure the security of packet 
exchange. 
•   Support for multicast —Multicasts protocol packets on some types of links. 
Basic concepts 
Autonomous System 
An Autonomous System (AS) comprises a group of  routers that run the same routing protocol. 
OSPF route computation 
OSPF computes routes in an area as follows: 
•  Based on the network topology around itself, each router generates Link State Advertisements (LSAs) 
and sends them to other routers in update packets. 
•   Each OSPF router collects LSAs from other routers to compose a link state database (LSDB). An LSA 
describes the network topology around a router, and the LSDB describes the entire network 
topology of the AS. 
•   Each router transforms the LSDB in the area to a weighted directed graph, which is the topology of 
the entire network. All the routers of the area have the same graph.
    Add page 745 to Favourites
    image text
    Enable zoom 
    							 56 
•  Each router uses the SPF algorithm to compute a shortest path tree showing the routes to the nodes 
in the AS. The router itself is the root of the tree. 
Router ID 
An OSPF process running on a router must have its own router ID. This ID is a 32-bit unsigned integer that 
uniquely identifies the router in the AS. 
OSPF packets 
OSPF uses the following types of packets: 
•  Hello —Periodically sent to find and maintain neighb ors, containing the values of some timers, 
information about the DR, BDR, and known neighbors. 
•   Database description (DD) —Describes the digest of each LSA in the LSDB, exchanged between two 
routers for data synchronization.  
•   Link state request (LSR) —Requests needed LSAs from the neighbor. After exchanging the DD 
packets, the two routers know which LSAs of the neighbor are missing from their LSDBs. They then 
send an LSR packet to each other, requesting the missing LSAs. The LSA packet contains the digest 
of the missing LSAs. 
•   Link state update (LSU) —Transmits the requested LSAs to the neighbor. 
•   Link state acknowledgment (LSAck) —Acknowledges received LSU packets. It contains the headers 
of received LSAs (an LSAck packet can acknowledge multiple LSAs). 
LSA types 
OSPF sends routing information in LSAs, which—as defined in RFC 2328—have the following types: 
•   Router LSA —Type-1 LSA, originated by all routers, floo ded throughout a single area only. This LSA 
describes the collected states of the routers interfaces to an area.  
•   Network LSA —Type-2 LSA, originated for broadcast and NBMA networks by the designated router, 
flooded throughout a single area only. This LSA contains the list of routers connected to the network. 
•   Network Summary LSA —Type-3 LSA, originated by ABRs (Area Border Routers), and flooded 
throughout the LSAs associated area. Each summary-LSA describes a route to a destination outside 
the area, yet still inside the AS (an inter-area route).  
•   ASBR Summary LSA —Type-4 LSA, originated by ABRs and flooded throughout the LSAs 
associated area. Type 4 summary-LSAs describe routes to ASBR (Autonomous System Boundary 
Router). 
•   AS External LSA —Type-5 LSA, originated by ASBRs, and flooded throughout the AS (except stub 
and NSSA areas). Each AS-external-LSA describes a route to another AS.  
•   NSSA LSA —Type-7 LSA, as defined in RFC 1587, originated by ASBRs in NSSAs (Not-So-Stubby 
Areas) and flooded throughout a single NSSA.  NSSA LSAs describe routes to other ASs. 
•   Opaque LSA —A proposed type of LSA, the format consisting of a standard LSA header and 
application specific information. Opaque LSAs are used by the OSPF protocol or by some 
application to distribute information into the OS PF routing domain. The opaque LSA includes Type 
9, Type 10, and Type 1 1. The Type 9 opaque LSA is flooded in to the local subnet, the Type 10 is 
flooded into the local area, and the Type 1 1 is flooded throughout the AS. 
Neighbor and Adjacency 
In OSPF, neighbor and adjacency are different concepts.
    Add page 746 to Favourites
    image text
    Enable zoom 
    							 57 
•  Neighbor —After startup, OSPF sends a hello packet on ea c h  OS P F  i n t e r f a c e.  A  ro u t e r  t h a t  re c e ive s  
the hello packet checks parameters in the packe t. If the parameters match its own, the router 
considers the sending router an OSPF neighbor. 
•   Adjacency —Two OSPF neighbors establish an adjacency relationship to synchronize their LSDBs. 
Therefore, any two neighbors without exchanging ro ute information do not establish an adjacency.   
Area based OSPF network partition 
Network partition 
In a large OSPF routing domain, the LSDB becomes very huge and SPF computation consumes many 
storage and CPU resources. 
In addition, because topology changes can easily oc cur, OSPF packets generated for route information 
synchronization are enormous, occupying excessive bandwidth.  
To  s o l ve  t h e s e  p ro b l e m s ,  OS P F  s p l i t s  a n  AS  i n t o  m u l t i p l e  a re a s ,  e a c h  o f  wh i c h  i s  i d e n t i fi e d  by  a n  a re a  I D.  
The boundaries between areas are routers rather than  links. A network segment (or a link) can only 
reside in one area. An OSPF interface must be sp ecified to belong to its attached area, as shown 
in  Figure 17 . 
Figure 17  Area based OSPF network 

partition 
 
 
After network partition, ABRs perform route summarization to reduce the number of LSAs advertised to 
other areas and minimize the effect of topology changes. 
Backbone area and virtual links 
Each AS has a backbone area that distributes routing information between none-backbone areas. 
Routing information between non-backbone areas must be forwarded by the backbone area. OSPF 
requires the following: 
•  All non-backbone areas must maintain connectivity to the backbone area. 
•   The backbone area itself must maintain connectivity.
    Add page 747 to Favourites
    image text
    Enable zoom 
    							 58 
In practice, the requirements may not be satisfied due to lack of physical links. OSPF virtual links can 
solve this problem. 
A virtual link is established between two ABRs through a non-backbone area and is configured on both 
ABRs to take effect. The non-backbone area is called a transit area. 
In the following figure, Area 2 has no direct physical link to the backbone area 0. You can configure a 
virtual link between the two ABRs to connect Area 2 to the backbone area. 
Figure 18  Virtual link application 1 
 
 
Virtual links can also be used to provide redundant links. If the backbone area cannot maintain internal 
connectivity due to the failure of a physical link, you can configure a virtual link to replace the failed 
physical link, as shown in  Figure 19. 
Figure 19  Virtual link application 2 
 
 
The virtual link between the two ABRs acts as a point-to-point connection. You can configure interface 
parameters such as hello interval on the virtual link  as they are configured on a physical interface. 
The two ABRs on the virtual link unicast OSPF packets to each other, and the OSPF routers in between 
convey these OSPF packets as normal IP packets. 
Stub area 
A stub area does not distribute Type-5 LSAs, so the routing table size and amount of routing information 
in this area are reduced significantly. The  ABR generates a default route into the area. 
You can configure the stub area as a totally stub area, where the ABR advertises neither inter-area routes 
nor external routes. 
Stub area configuration is optional, and not every area is eligible to be a stub area. In general, a stub 
area resides on the border of the AS. 
When you configure a totally stub area, follow these guidelines: 
•   The backbone area cannot be a totally stub area. 
•   To configure an area as a stub area, the  stub command must be configured on routers in the area. 
Area 0
Area 1
Virtual link
R2
R1
    Add page 748 to Favourites
    image text
    Enable zoom 
    							 59 
•  To configure an area as a totally stub area, the  stub c o m m a n d  mus t  b e  c o n fig u re d  o n  ro u te rs  i n  t he  
area, and the ABR of the area must be configured with the  stub [ no-summary  ] command. 
•   A totally stub area cannot have an ASBR because AS  external routes cannot be distributed into the 
stub area. 
•   Virtual links cannot transit totally stub areas. 
NSSA area 
Similar to a stub area, an NSSA area does not impo rt AS external LSAs (Type-5 LSAs), but can import 
Type-7 LSAs generated by the NSSA ASBR. The NSSA ABR translates Type-7 LSAs into Type-5 LSAs and 
advertises the Type-5 LSAs to other areas. 
In the following figure, the OSPF AS contains Area 1, Area 2, and Area 0. The other two ASs run RIP. 
Area 1 is an NSSA area. The ASBR redistributes RIP ro utes in Type-7 LSAs into Area 1. Upon receiving 
these Type-7 LSAs, the NSSA ABR translates them to Type-5 LSAs, and then advertises the Type-5 LSAs to 
Area 0. 
T h e  AS B R  o f  A re a  2  re d i s t ri b u t e s  R I P  ro u t e s  i n  Typ e - 5  L SA s  i n t o  t h e  OS P F  ro u t i n g  d o m a i n.  H oweve r,  A re a  
1 does not receive these Type-5 LSAs because it is an NSSA area. 
Virtual links cannot transit NSSA areas. 
Figure 20  NSSA area 
 
 
Comparison between the areas 
Figure 21 Comparison between the areas 
 
 
Figure 21 shows the comparison of the areas: 
•   In a totally stub area, the ABR distributes a Type 3 default route, rather than external routes and 
inter-area routes.  
•   A stub area can import inter-area routes, but a stub area cannot.  
Totally Stub 
area
Stub area
NSSA area
Totally NSSA  area
Permits 
Type 3 LSAs
Permits 
Type 7 LSAs 
within the area
Does not 
permit Type 3  LSAs
A Type 3 default route 
can be distributed in the  area, while Type 3 and 
Type 5 LSAs cannot be  distributed in the area
    Add page 749 to Favourites
    image text
    Enable zoom 
    							 60 
•  An NSSA area can import external routes in Type 7 LSAs through the ASBR, but a stub area cannot.   
•   A totally NSSA area cannot import inter-area routes but an NSSA area can.  
Router types 
Router classification 
The following are OSPF router types and their positions in the AS: 
•  Internal router —All interfaces on an internal router belong to one OSPF area. 
•   Area Border Router (ABR) —An ABR belongs to more than two areas, one of which must be the 
backbone area. It connects the backbone area to a non-backbone area. The connection between 
an ABR and the backbone area can be physical or logical. 
•   Backbone router —At least one interface of a backbone router must reside in the backbone area. 
All ABRs and internal routers in  area 0 are backbone routers. 
•   Autonomous System Boundary Router (ASBR) —A router exchanging routing information with 
another AS is an ASBR, which may not reside on the  border of the AS. It can be an internal router 
or an ABR. 
Figure 22  OSPF router types 
 
 
Route types 
OSPF prioritize routes into the following levels: 
•  Intra-area route 
•   Inter-area route 
•   Type-1 external route 
•   Type-2 external route
    Add page 750 to Favourites
    image text
    Enable zoom 
    							 61 
The intra-area and inter-area routes describe the network topology of the AS. The external routes describe 
routes to external ASs.  
OSPF classifies external routes as Type -1 or Type -2.  A Type-1 external route has high credibility. The cost 
from a router to the destination of the Type-1 external route = the cost from the router to the corresponding 
ASBR + the cost from the ASBR to the destination of the external route. 
A Type-2 external route has low credibility, so OSPF considers the cost from the ASBR to the destination 
of the Type -2 external route is much greater than the cost from the ASBR to an OSPF internal router. The 
cost from the internal router to the destination of the Type-2 external route = the cost from the ASBR to the 
destination of the Type-2 external route. If two rout es to the same destination have the same cost, OSPF 
takes the cost from the router to the ASBR into consideration to determine the best route. 
OSPF network classification 
OSPF network types 
OSPF classifies networks into the following type s depending on different link layer protocols: 
•   Broadcast —When the link layer protocol is Ethernet or FDDI, OSPF considers the network type as 
broadcast by default. On a broadcast network, hello, LSU, and LSAck packets are multicast to 
224.0.0.5 that identifies all OSPF routers or 224.0.0.6 that identifies the DR, and DD packets and 
LSR packets are unicast. 
•   NBMA (Non-Broadcast Multi-Access)—When the link layer protocol is Frame Relay, ATM, or X.25, 
OSPF considers the network type as NBMA by default. OSPF packets are unicast on a NBMA 
network. 
•   P2MP (point-to-multipoint) — By defau l t, OSP F  c onsiders  no  l i nk  l ayer  proto c ol  as  P 2 M P, which i s  a 
conversion from other network types such as NBMA. On a P2MP network, OSPF packets are 
multicast to 224.0.0.5. 
•   P2P (point-to-point) —When the link layer protocol is PPP or HDLC, OSPF considers the network 
type as P2P. On a P2P network, OSPF packets are multicast to 224.0.0.5. 
NBMA network configuration guidelines 
Typical NBMA networks include ATM and Frame Relay networks. 
Because NBMA interfaces cannot broadcast hello  packets, you must specify neighbors manually and 
configure router priorities for the neighbors. 
An NBMA network is fully meshed, which means any two routers in the NBMA network have a direct 
virtual circuit for communication. If direct connect ions are not available between some routers, the 
network type of associated interfaces must be conf igured as P2MP. If such an interface has only one 
neighbor, configure its network type as P2P. 
The differences between NBMA and P2MP networks are as follows: 
•   NBMA networks are fully meshed, non-broadcast, and multi access. P2MP networks are not 
required to be fully meshed. 
On an NBMA network, you must elect the DR and  BDR, while on a P2MP network, DR and BDR are 
not available. 
•   NBMA is the default network type, but P2MP is a conversion from another network type, such as 
NBMA. 
•   On a NBMA network, OSPF packets are unicast, and neighbors are manually configured on routers. 
On a P2MP network, OSPF packets are multicast.
    All HP manuals Comments (0)

    Related Manuals for HP 5500 Ei 5500 Si Switch Series Configuration Guide