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 811 to Favourites
    image text
    Enable zoom 
    							 122 
You can enable OSPF FRR to either automatically calculate a backup next hop, or to designate a 
backup next hop by using a routing policy. 
Method I: Enable OSPF FRR to automatically calculate the backup next hop.  
# Configure Switch S.  
 system-view 
[SwitchS] bfd echo-source-ip 1.1.1.1 
[SwitchS] ospf 1 
[SwitchS-ospf-1] fast-reroute auto 
[SwitchS-ospf-1] quit 
# Configure Switch D.  
 system-view 
[SwitchD] bfd echo-source-ip 4.4.4.4 
[SwitchD] ospf 1 
[SwitchD-ospf-1] fast-reroute auto 
[SwitchD-ospf-1] quit 
Method II: Enable OSPF FRR to  designate a backup next hop by using a routing policy. 
# 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] ospf 1 
[SwitchS-ospf-1] fast-reroute route-policy frr 
[SwitchS-ospf-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] ospf 1 
[SwitchD-ospf-1] fast-reroute route-policy frr 
[SwitchD-ospf-1] quit 
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
    Add page 812 to Favourites
    image text
    Enable zoom 
    							 123 
     Protocol: OSPF            Process ID: 1 
   Preference: 10                    Cost: 1 
 IpPrecedence:                    QosLcId: 
      NextHop: 13.13.13.2       Interface: Vlan-interface200 
    BkNextHop: 12.12.12.2     BkInterface: Vlan-interface100 
  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: OSPF            Process ID: 1 
   Preference: 10                    Cost: 1 
 IpPrecedence:                    QosLcId: 
      NextHop: 13.13.13.1       Interface: Vlan-interface200 
    BkNextHop: 24.24.24.2     BkInterface: Vlan-interface101 
  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 OSPF 
Network requirements 
As shown in Figure 48, OSPF is enabled on Switch A, Switch B and Switch C that are reachable to each 
other at the network layer.  
After the link over which Switch A and Switch B co mmunicate through a Layer 2 switch fails, BFD can 
quickly detect the failure and notify OSPF of the fail ure. Switch A and Switch B then communicate through 
Switch C.
    Add page 813 to Favourites
    image text
    Enable zoom 
    							 124 
Figure 48 Network diagram 
 
Device Interface IP address Device Interface IP address 
Switch A  Vlan-int10  10.1.0.102/24  Switch B  Vlan-int10  10.1.0.100/24 
 Vlan-int11 11.1.1.1/24  Vlan-int13 13.1.1.1/24 
Switch C  Vlan-int11  11.1.1.2/24    
 Vlan-int13 13.1.1.2/24     
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.1.0.0 0.0.0.255  
[SwitchA-ospf-1-area-0.0.0.0] network 11.1.1.0 0.0.0.255 
[SwitchA-ospf-1-area-0.0.0.0] network 121.1.1.0 0.0.0.255 
[SwitchA-ospf-1-area-0.0.0.0] quit 
[SwitchA-ospf-1] quit 
[SwitchA] interface vlan 11 
[SwitchA-Vlan-interface11] ospf cost 2 
[SwitchA-Vlan-interface11] quit 
# Configure Switch B. 
 system-view 
[SwitchB] ospf 
[SwitchB-ospf-1] area 0 
[SwitchB-ospf-1-area-0.0.0.0] network 10.1.0.0 0.0.0.255 
[SwitchB-ospf-1-area-0.0.0.0] network 13.1.1.0 0.0.0.255 
[SwitchB-ospf-1-area-0.0.0.0] network 120.1.1.0 0.0.0.255 
[SwitchB-ospf-1-area-0.0.0.0] quit 
[SwitchB-ospf-1] quit 
[SwitchB] interface vlan-interface 13 
[SwitchB-Vlan-interface13] ospf cost 2 
[SwitchB-Vlan-interface13] quit 
# Configure Switch C.  
 system-view
    Add page 814 to Favourites
    image text
    Enable zoom 
    							 125 
[SwitchC] ospf 
[SwitchC-ospf-1] area 0 
[SwitchC-ospf-1-area-0.0.0.0] network 11.1.1.0 0.0.0.255 
[SwitchC-ospf-1-area-0.0.0.0] network 13.1.1.0 0.0.0.255 
[SwitchC-ospf-1-area-0.0.0.0] quit 
[SwitchC-ospf-1] quit 
3. Configure BFD:  
# Enable BFD on Switch A and configure BFD parameters.  
[SwitchA] bfd session init-mode active 
[SwitchA] interface vlan-interface 10 
[SwitchA-Vlan-interface10] ospf bfd enable 
[SwitchA-Vlan-interface10] bfd min-transmit-interval 500 
[SwitchA-Vlan-interface10] bfd min-receive-interval 500 
[SwitchA-Vlan-interface10] bfd detect-multiplier 7 
[SwitchA-Vlan-interface10] quit 
[SwitchA] quit 
# Enable BFD on Switch B and configure BFD parameters. 
[SwitchB] bfd session init-mode active 
[SwitchB] interface vlan-interface 10 
[SwitchB-Vlan-interface10] ospf bfd enable 
[SwitchB-Vlan-interface10] bfd min-transmit-interval 500 
[SwitchB-Vlan-interface10] bfd min-receive-interval 500 
[SwitchB-Vlan-interface10] bfd detect-multiplier 6 
4. Verify the configuration: 
The following operations are performed on Switch  A. The operations on Switch B and Switch C 
are similar. (Details not shown.)  
# Display the BFD 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 \
 3/1           10.1.0.102      10.1.0.100      Up    1700ms   vlan10 
# Display routes to 120.1.1.0/24 on Switch A, an d you can see that Switch A communicates with 
Switch B through the Layer 2 switch.  
 display ip routing-table 120.1.1.0 verbose 
Routing Table : Public 
Summary Count : 2 
  Destination: 120.1.1.0/24 
     Protocol: OSPF            Process ID: 0 
   Preference: 0                     Cost: 2 
 IpPrecedence:                    QosLcId: 
      NextHop: 192.168.0.100    Interface: Vlan-interface10 
    BkNextHop: 0.0.0.0        BkInterface: 
  RelyNextHop: 0.0.0.0          Neighbor : 0.0.0.0 
    Tunnel ID: 0x0                  Label: NULL 
  BKTunnel ID: 0x0                BKLabel: NULL 
        State: Active Adv             Age: 00h58m10s
    Add page 815 to Favourites
    image text
    Enable zoom 
    							 126 
          Tag: 0 
  Destination: 120.1.1.0/24 
     Protocol: OSPF            Process ID: 1 
   Preference: 10                    Cost: 4 
 IpPrecedence:                    QosLcId: 
      NextHop: 10.1.1.100       Interface: Vlan-interface11 
    BkNextHop: 0.0.0.0        BkInterface: 
  RelyNextHop: 0.0.0.0          Neighbor : 0.0.0.0 
    Tunnel ID: 0x0                  Label: NULL 
  BKTunnel ID: 0x0                BKLabel: NULL 
        State: Invalid Adv            Age: 00h58m05s 
          Tag: 0 
# Enable BFD debugging on Switch A.  
 debugging bfd scm 
 debugging bfd event 
 debugging ospf event 
 terminal debugging 
# After the link over which Switch A and Switch B communicates through the Layer 2 switch fails, 
Switch A can quickly detect the changes on Switch B.  
%Nov 12 18:34:48:823 2005 SwitchA BFD/5/LOG: Sess[10.1.0.102/10.1.0.100,\
 vlan10], 
Sta : UP->DOWN, Diag: 1 
%Nov 12 18:34:48:824 2005 SwitchA RM/4/RMLOG:OSPF-NBRCHANGE: Process 1, \
Neighbour 
10.1.0.102 (vlan10) from Full to Down 
*0.50673825 SwitchA BFD/8/SCM:Sess[10.1.0.102/10.1.0.100, vlan10],Oper: \
Reset 
*0.50673825 SwitchA BFD/8/EVENT:Send sess-down Msg, [Src:10.1.0.102, Dst:10.1.0.100, 
vlan10] Protocol: OSPF 
 
*0.50673826 SwitchA RM/7/RMDEBUG:OSPF-BFD: Message Type rcv BFD down, Co\
nnect Type 
direct-connect, Src IP Address 10.1.0.102, Src IFIndex 5, Dst IP Address 10.1.0.100 
 
*0.50673827 SwitchA RM/7/RMDEBUG:OSPF-BFD: Message Type delete session, Connect Type 
direct-connect, Src IP Address 10.1.0.102, Src IFIndex 5, Dst IP Address 10.1.0.100 
OSPF 1: Nbr 10.1.0.100 Rcv KillNbr State Full -> Down. 
*0.50673829 SwitchA BFD/8/EVENT:Receive Delete-sess, [Src:10.1.0.102, 
Dst:10.1.0.100, vlan10], Direct, Proto:OSPF 
*0.50673830 SwitchA BFD/8/SCM:Sess[10.1.0.102/10.1.0.100, vlan10], Oper:\
 Del 
application(OSPF) 
*0.50673831 SwitchA BFD/8/SCM:No application in session, delete 
session[10.1.0.102/10.1.0.100, vlan10] 
*0.50673831 SwitchA BFD/8/SCM:Sess[10.1.0.102/10.1.0.100, vlan10], Oper:\
 Delete 
*0.50673832 SwitchA BFD/8/SCM:Delete send-packet timer 
*0.50673833 SwitchA BFD/8/SCM:Delete session entry 
*0.50673833 SwitchA BFD/8/SCM:Delete session from IP hash table 
*0.50673834 SwitchA BFD/8/SCM:Delete session from bfd interface 
*0.50673834 SwitchA BFD/8/SCM:No session under bfd-int[vlan10] with defa\
ult 
configuration, delete bfd-if 
*0.50673835 SwitchA BFD/8/SCM:Bfd-if[vlan10], Oper: Delete 
*0.50673840 SwitchA BFD/8/SCM:No bfd session exists, stop receiving any \
bfd packets 
# Display the BFD information of Switch A.
    Add page 816 to Favourites
    image text
    Enable zoom 
    							 127 
The BFD session between Switch A and Switch B is deleted and no information is output.  
 display bfd session 
# Display routes to 120.1.1.0/24 on Switch A, an d you can see that Switch A communicates with 
Switch B through Switch C.  
 display ip routing-table 120.1.1.0 verbose 
Routing Table : Public 
Summary Count : 2 
  Destination: 120.1.1.0/24 
     Protocol: OSPF            Process ID: 1 
   Preference: 10                    Cost: 4 
 IpPrecedence:                    QosLcId: 
      NextHop: 10.1.1.100       Interface: Vlan-interface11 
    BkNextHop: 0.0.0.0        BkInterface: 
  RelyNextHop: 0.0.0.0          Neighbor : 0.0.0.0 
    Tunnel ID: 0x0                  Label: NULL 
  BKTunnel ID: 0x0                BKLabel: NULL 
        State: Active Adv             Age: 00h58m10s 
          Tag: 0 
  Destination: 120.1.1.0/24 
     Protocol: OSPF            Process ID: 0 
   Preference: 0                     Cost: 2 
 IpPrecedence:                    QosLcId: 
      NextHop: 192.168.0.100    Interface: Vlan-interface10 
    BkNextHop: 0.0.0.0        BkInterface: 
  RelyNextHop: 0.0.0.0          Neighbor : 0.0.0.0 
    Tunnel ID: 0x0                  Label: NULL 
  BKTunnel ID: 0x0                BKLabel: NULL 
        State: Invalid Adv            Age: 00h58m05s 
          Tag: 0 
Troubleshooting OSPF configuration 
No OSPF neighbor relationship established 
Symptom 
No OSPF neighbor relationship can be established. 
Analysis 
If the physical link and lower layer protocols work  well, check OSPF parameters configured on interfaces. 
Two neighbors must have the same parameters, such as the area ID, network segment, and mask (a P2P 
or virtual link may have different network segments and masks). 
Solution 
1.  Display OSPF neighbor information using the  display ospf peer command. 
2. Display OSPF interface information using the  display ospf interface command. 
3. Ping the neighbor router’s IP  address to check connectivity. 
4. Check OSPF timers. The dead interval on an interface must be at least four times the hello interval.
    Add page 817 to Favourites
    image text
    Enable zoom 
    							 128 
5.
 
On an NBMA network, using the  peer ip-address command to specify the neighbor manually is 
required. 
6.  On an NBMA or a broadcast network, at least one connected interfac e must have a router priority 
higher than 0. 
Incorrect routing information 
Symptom 
OSPF cannot find routes to other areas. 
Analysis 
The backbone area must maintain connectivity to all ot her areas. If a router connects to more than one 
area, at least one area must be connected to the backbone. The backbone cannot be configured as a 
Stub area. 
In a Stub area, all routers cannot receive external ro utes, and all interfaces connected to the Stub area 
must belong to the Stub area. 
Solution 
1.  Use the  display ospf peer  command to display neighbors. 
2. Use the  display ospf interface  command to display OSPF interface information. 
3. Use the  display ospf lsdb  command to display the LSDB to check its integrity.  
4. Display information about area configuration using the  display current-configuration 
configuration ospf  command. If more than two areas ar e configured, at least one area is 
connected to the backbone. 
5.  In a Stub area, all routers attached are configured with the stub command. In an NSSA area, all 
routers attached are configured with the  nssa command. 
6. If a virtual link is configured, use the  display ospf vlink command to check the state of the virtual 
link.
    Add page 818 to Favourites
    image text
    Enable zoom 
    							 129 
Configuring IS-IS 
Hardware compatibility 
The HP 5500 SI Switch Series does not support IS-IS. 
IS-IS overview 
Intermediate System-to-Intermediate System (IS-IS) is a dynamic routing protocol designed by the 
International Organization for Standardization (ISO) to operate on the connectionless network protocol 
(CLNP). 
The IS-IS routing protocol was modified and extended in RFC 1 195 by the International Engineer Task 
Force (IETF) for application in both TCP/IP and OSI reference models, and the new one is named 
Integrated IS-IS or Dual IS-IS. 
I S - I S  i s  a n  I n t e r i o r  G a t e w a y  P ro t o c o l  ( I G P )  u s e d  wi t h i n  a n  A u t o n o m o u s  Sys t e m.  I t  a d o p t s  t h e  S h o r t e s t  Pa t h  
First (SPF) algorithm for route calculation. 
The term router in this chapter refers to both routers and Layer 3 switches. 
Basic concepts 
IS-IS terminology 
•   Intermediate system (IS)—Similar to a router in TCP/IP, it is the basic unit in IS-IS to generate and 
propagate routing information. In the follo wing text, an IS refers to a router. 
•   End system (ES)—Refers to a host system in TCP/IP. ISO defines the ES-IS protocol for 
communication between an ES and an IS. An ES does not participate in the IS-IS processing. 
•   Routing domain (RD) —A group of ISs exchanges routing information with each other using the 
same routing protocol in a routing domain. 
•   Area —A unit in a routing domain. The IS-IS protocol  allows a routing domain to be divided into 
multiple areas. 
•   Link State Database (LSDB) —All link states in the network forms the LSDB. Each IS has at least one 
LSDB. The IS uses the SPF algorithm and LSDB to generate its own routes. 
•   Link State Protocol Data Unit (LSPDU) or Link State Packet (LSP) —Each IS can generate an LSP, 
which contains all the link state information of the IS.  
•   Network Protocol Data Unit (NPDU) —A network layer protocol packet in OSI, which is equivalent 
to an IP packet in TCP/IP. 
•   Designated IS —On a broadcast network, the designated router is also known as the designated 
IS. 
•   Network service access point (NSAP) —An NSAP is an OSI network layer address. It identifies an 
abstract network service access point and describes the network address in the OSI reference 
model.
    Add page 819 to Favourites
    image text
    Enable zoom 
    							 130 
IS-IS address format 
•  NSAP 
As shown in  Figure 49, an NSAP address c
 onsists of the Initial Domain Part (IDP) and the Domain 
Specific Part (DSP). The IDP is equal to the network ID of an IP address, and the DSP is equal to the 
subnet and host ID. 
The IDP includes the Authority and Format Identifier  (AFI) and the Initial Domain Identifier (IDI). 
The DSP includes the High Order Part of DSP (HO-DSP), System ID, and SEL, where the HO-DSP 
identifies the area, the System ID identifies the  host, and the SEL identifies the type of service. 
The IDP and DSP are variable in length. The length  of an NSAP address varies from 8 bytes to 20 
bytes. 
Figure 49  NSAP address format 
 
 
•  Area address 
The area address comprises the IDP and the HO-DSP  of the DSP, which identify the area and the 
routing domain. Different routing domain s cannot have the same area address. 
Typically, a router only needs one area address, and all nodes in the same routing domain must 
share the same area address. However, a router can have a maximum of three area addresses to 
support smooth area merging, partitioning, and switching. 
•   System I D 
A system ID identifies a host or router unique ly. It has a fixed length of 48 bits (6 bytes). 
The system ID of a device can be generated from  the Router ID. For example, a router uses the IP 
address 168.10.1.1 of Loopback 0 as the Router ID. Th e system ID in IS-IS can be obtained in the 
following ways: 
{  Extend each decimal number of the IP address to  3 digits by adding 0s from the left, like 
168.010.001.001; 
{  Divide the extended IP address into 3 sections with  4 digits in each section to get the system ID 
16 8 0 .10 0 0 .10 01.  
If you use other methods for defining a system ID, al ways make sure that it can uniquely identify a 
host or router. 
•   SEL 
The NSAP Selector (SEL), or the N-SEL, is similar to the protocol identifier in IP. Different transport 
layer protocols correspond to differe nt SELs. All SELs in IP are 00. 
•   Routing method 
Because the area information is identified in IS-I S addresses, a Level-1 router can easily identify 
packets destined to other areas.  
{  A Level-1 router makes routing decisions based on  the system ID. If the destination is not in the 
area, the packet is forwarded to the nearest Level-1-2 router. 
{  A Level-2 router routes packets across areas according to the area address.
    Add page 820 to Favourites
    image text
    Enable zoom 
    							 131 
NET 
A network entity title (NET) indicates the network layer information of an IS, and does not include 
transport layer information. It is a special NSAP address with the SEL being 0. The length of the NET is 
equal to the NSAP, and is in the range of 8 bytes to 20 bytes. 
A NET comprises the following parts: 
•  Area ID —Its length is in the range of 1 to 13 bytes. 
•   System ID —A system ID uniquely identifies a host or router in the area and has a fixed 6-byte 
length.  
•   SEL—It has a value of 0 and a fixed 1-byte length.  
For example, a NET is ab.cdef.1234.5678.9abc.00, where, area ID is ab.cdef, system ID is 
1234.5678.9abc, and SEL is 00.  
Typically, a router only needs one NET, but it can have a maximum of three NETs for smooth area 
merging and partitioning. When you configure multiple NETs, ensure their system IDs are the same. 
IS-IS area 
Two-level hierarchy 
IS-IS has a two-level hierarchy to support large scal e networks. A large scale routing domain is divided 
into multiple Areas. Typically, a Level-1 router is de ployed within an area, a Level-2 router is deployed 
between areas, and a Level-1-2 router is deployed between Level-1 and Level-2 routers.  
Level-1 and Level-2 
•   Level-1 router —A Level-1 router establishes neighbor relationships with Level-1 and Level-1-2 routers 
in the same area. The LSDB maintained by the Level-1 router contains the local area routing 
information. It directs the packets destined for an outside area to the nearest Level-1-2 router. 
•   Level-2 router —A Level-2 router establishes neighbor relationships with the Level-2 and Level-1-2 
routers in the same or in different areas. It maintains a Level-2 LSDB containing inter-area routing 
information. All the Level-2 and Level-1-2 routers must be contiguous to form the backbone of a 
routing domain.  
•   Level-1-2 router —A router with both Level-1 and Level-2 router functions is a Level-1-2 router. It can 
establish Level-1 neighbor relationships with the Level-1 and Level-1-2 routers in the same area, or 
establish Level-2 neighbor relationships with the Level-2 and Level-1-2 routers in different areas. A 
Level-1 router must be connected to other areas  through a Level-1-2 router. The Level-1-2 router 
maintains two LSDBs, where the Level-1 LSDB is for routing within the area, and the Level-2 LSDB is 
for routing between areas. 
The Level-1 routers in different areas cannot establish neighbor relationships. 
The neighbor relationship establishment of Level-2 routers has nothing to do with area. 
Figure 50  sho
 ws an IS-IS network topology. Area 1 comprises a set of Level-2 routers and is the backbone. 
The other four areas are non-backbone areas connected to the backbone through Level-1-2 routers.
    All HP manuals Comments (0)

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