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 871 to Favourites
    image text
    Enable zoom 
    							 182 
[SwitchC-isis-1] network-entity 10.0000.0000.0003.00 
[SwitchC-isis-1] quit 
[SwitchC] interface vlan-interface 200 
[SwitchC-Vlan-interface200] isis enable 1 
[SwitchC-Vlan-interface200] quit 
[SwitchC] interface vlan-interface 300 
[SwitchC-Vlan-interface300] isis enable 1 
[SwitchC-Vlan-interface300] quit 
[SwitchC] interface vlan-interface 300 
[SwitchC-Vlan-interface300] isis enable 1 
[SwitchC-Vlan-interface300] quit 
# Configure Switch D. 
 system-view 
[SwitchD] isis 1 
[SwitchD-isis-1] network-entity 20.0000.0000.0001.00 
[SwitchD-isis-1] quit 
[SwitchD] interface vlan-interface 300 
[SwitchD-Vlan-interface300] isis enable 1 
[SwitchD-Vlan-interface300] quit 
3. Configure neighbor rela tionship authentication between neighbors:  
# Specify the MD5 authenti cation mode and password  eRq on VLAN-interface 100 of Switch A 
and on VLAN-interface 100 of Switch C. 
[SwitchA] interface vlan-interface 100 
[SwitchA-Vlan-interface100] isis authentication-mode md5 eRg 
[SwitchA-Vlan-interface100] quit 
[SwitchC] interface vlan-interface 100 
[SwitchC-Vlan-interface100] isis authentication-mode md5 eRg 
[SwitchC-Vlan-interface100] quit 
# Specify the MD5 authenti cation mode and password  t5Hr on VLAN-interface 200 of Switch B 
and on VLAN-interface 200 of Switch C. 
[SwitchB] interface vlan-interface 200 
[SwitchB-Vlan-interface200] isis authentication-mode md5 t5Hr 
[SwitchB-Vlan-interface200] quit 
[SwitchC] interface vlan-interface 200 
[SwitchC-Vlan-interface200] isis authentication-mode md5 t5Hr 
[SwitchC-Vlan-interface200] quit 
# Specify the MD5 authentication mode and password  hSec on VLAN-interface 300 of Switch D 
and on VLAN-interface 300 of Switch C. 
[SwitchC] interface vlan-interface 300 
[SwitchC-Vlan-interface300] isis authentication-mode md5 hSec 
[SwitchC-Vlan-interface300] quit 
[SwitchD] interface vlan-interface 300 
[SwitchD-Vlan-interface300] isis authentication-mode md5 hSec 
[SwitchD-Vlan-interface300] quit 
4.  Configure area authentication. Specify th e MD5 authentication mode and password  10Sec on 
Switch A, Switch B, and Switch C: 
[SwitchA] isis 1
    Add page 872 to Favourites
    image text
    Enable zoom 
    							 183 
[SwitchA-isis-1] area-authentication-mode md5 10Sec 
[SwitchA-isis-1] quit 
[SwitchB] isis 1 
[SwitchB-isis-1] area-authentication-mode md5 10Sec 
[SwitchB-isis-1] quit 
[SwitchC] isis 1 
[SwitchC-isis-1] area-authentication-mode md5 10Sec 
[SwitchC-isis-1] quit 
5. Configure routing domain authentication. Spec ify the MD5 authentication mode and password 
1020Sec  on Switch C and Switch D: 
[SwitchC] isis 1 
[SwitchC-isis-1] domain-authentication-mode md5 1020Sec 
[SwitchC-isis-1] quit 
[SwitchD] isis 1 
[SwitchD-isis-1] domain-authentication-mode md5 1020Sec 
Configuring BFD for IS-IS 
Network requirements 
•  As shown in Figure 70 , IS-IS 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 communicate through the Layer-2 switch fails, BFD 
can quickly detect the failure and notify IS-IS of th e failure. Switch A and Switch B then communicate 
through Switch C.  
Figure 70  Network diagram for BFD configuration on an IS-IS link 
 
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 interf aces (Details not shown.).  
2. Configure IS-IS basic functions. 
# Configure Switch A.
    Add page 873 to Favourites
    image text
    Enable zoom 
    							 184 
 system-view 
[SwitchA] isis 
[SwitchA-isis-1] network-entity 10.0000.0000.0001.00 
[SwitchA-isis-1] quit 
[SwitchA] interface vlan-interface 10 
[SwitchA-Vlan-interface10] isis enable 
[SwitchA-Vlan-interface10] quit 
[SwitchA] interface vlan-interface 11 
[SwitchA-Vlan-interface11] isis enable 
[SwitchA-Vlan-interface11] quit 
# Configure Switch B. 
 system-view 
[SwitchB] isis 
[SwitchB-isis-1] network-entity 10.0000.0000.0002.00 
[SwitchB-isis-1] quit 
[SwitchB] interface vlan-interface 10 
[SwitchB-Vlan-interface10] isis enable 
[SwitchB-Vlan-interface10] quit 
[SwitchB] interface vlan-interface 13 
[SwitchB-Vlan-interface13] isis enable 
[SwitchB-Vlan-interface13] quit 
# Configure Switch C.  
 system-view 
[SwitchC] isis 
[SwitchC-isis-1] network-entity 10.0000.0000.0003.00 
[SwitchC-isis-1] quit 
[SwitchC] interface vlan-interface 11 
[SwitchC-Vlan-interface11] isis enable 
[SwitchC-Vlan-interface11] quit 
[SwitchC] interface vlan-interface 13 
[SwitchC-Vlan-interface13] isis enable 
[SwitchC-Vlan-interface13] quit 
3. Configure BFD parameters: 
# Enable BFD on Switch A and configure BFD parameters. 
[SwitchA] bfd session init-mode active 
[SwitchA] interface vlan-interface 10 
[SwitchA-Vlan-interface10] isis bfd enable 
[SwitchA-Vlan-interface10] bfd min-receive-interval 500 
[SwitchA-Vlan-interface10] bfd min-transmit-interval 500 
[SwitchA-Vlan-interface10] bfd detect-multiplier 7 
# Enable BFD on Switch B and configure BFD parameters. 
[SwitchB] bfd session init-mode active 
[SwitchB] interface vlan-interface 10 
[SwitchB-Vlan-interface10] isis bfd enable 
[SwitchB-Vlan-interface10] bfd min-receive-interval 500 
[SwitchB-Vlan-interface10] bfd min-transmit-interval 500 
[SwitchB-Vlan-interface10] bfd detect-multiplier 8
    Add page 874 to Favourites
    image text
    Enable zoom 
    							 185 
[SwitchB-Vlan-interface10] return 
4. Verify the configuration: 
The following configurations are made on Switch A. Configurations for Switch B 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 route 120.1.1.0/24 on Switch A, and you can see that Switch A and Switch B 
communicate 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: ISIS            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 
          Tag: 0 
  Destination: 120.1.1.0/24 
     Protocol: ISIS            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 debugging on Switch A.  
 debugging isis bfd-event 
 terminal debugging 
# When the link between Switch B and the Layer-2 sw itch fails, BFD can quickly detect the failure.  
#Aug  8 14:54:05:362 2008 SwitchA IFNET/4/INTERFACE UPDOWN: 
 Trap 1.3.6.1.6.3.1.1.5.3: Interface 983041 is Down, ifAdminStatus is 1, 
ifOperStatus is 2 
#Aug  8 14:54:05:363 2008 SwitchA 
ISIS/4/ADJ_CHANGE:TrapID(1.3.6.1.2.1.138.0.17), I\
SIS Level-2 
Adjencency IN Circuit-983041 State Change.
    Add page 875 to Favourites
    image text
    Enable zoom 
    							 186 
#Aug  8 14:54:05:364 2008 SwitchA 
ISIS/4/ADJ_CHANGE:TrapID(1.3.6.1.2.1.138.0.17), I\
SIS Level-1 
Adjencency IN Circuit-983041 State Change. 
%Aug  8 14:54:05:365 2008 SwitchA IFNET/4/LINK UPDOWN: Vlan-interface10 \
link status 
is DOWN 
%Aug  8 14:54:05:366 2008 SwitchA IFNET/4/UPDOWN: Line protocol on the i\
nterface 
Vlan-interface10 is DOWN 
%Aug  8 14:54:05:367 2008 SwitchA ISIS/4/ADJLOG:ISIS-1-ADJCHANGE: Adjace\
ncy To 
0000.0000.0002 (vlan10) DOWN, Level-2 Circuit Down. 
%Aug  8 14:54:05:367 2008 SwitchA ISIS/4/ADJLOG:ISIS-1-ADJCHANGE: Adjace\
ncy To 
0000.0000.0002 (vlan10) DOWN, Level-2 Adjacency clear. 
%Aug  8 14:54:05:368 2008 SwitchA ISIS/4/ADJLOG:ISIS-1-ADJCHANGE: Adjace\
ncy To 
0000.0000.0002 (vlan10) DOWN, Level-1 Circuit Down. 
%Aug  8 14:54:05:369 2008 SwitchA ISIS/4/ADJLOG:ISIS-1-ADJCHANGE: Adjace\
ncy To 
0000.0000.0002 (vlan10) DOWN, Level-1 Adjacency clear. 
*Aug  8 14:54:05:370 2008 SwitchA ISIS/6/ISIS: 
  ISIS-1-BFD: Success to send msg. Msg type 1 delete session. IfPhyIndex: \
5 ,DstIPAddr: 
10.1.0.100 , SrcIPAddr:10.1.0.102. NeighborType:Level-2. 
 
*Aug  8 14:54:05:370 2008 SwitchA ISIS/6/ISIS: 
  ISIS-1-BFD: Success to send msg. Msg type 1 delete session. IfPhyIndex: \
5 ,DstIPAddr: 
10.1.0.100 , SrcIPAddr:10.1.0.102. NeighborType:Level-1. 
# Display the BFD information of Switch A. Switch A has removed its neighbor relationship with 
Switch B and no information is output.  
 display bfd session 
# Display route 120.1.1.0/24 on Switch A, and you can see that Switch A and Switch B 
communicate 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: ISIS            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
    Add page 876 to Favourites
    image text
    Enable zoom 
    							 187 
Configuring BGP 
Hardware compatibility 
The HP 5500 SI Switch Series does not support BGP. 
BGP overview 
The Border Gateway Protocol (BGP) is a dynamic inter-AS Exterior Gateway Protocol. The three early 
BGP versions are BGP-1 (RFC 1105), BGP-2 (RFC 1163) and BGP-3 (RFC 1267). The current version is 
BGP-4 (RFC 4271), and is the Internet exterior gateway protocol. The term router in this chapter refers 
to both routers and Layer 3 switches, and BGP refers to BGP-4 in this chapter. 
BGP has the following characteristics: 
•   Focuses on the control of route propagation and the selection of optimal routes rather than the route 
discovery and calculation, which makes BGP, an exterior gateway protocol different from interior 
gateway protocols such as OSPF and RIP. 
•   Uses TCP to enhance reliability. 
•   Supports CIDR. 
•   Reduces bandwidth consumption by advertising only incremental updates and is applicable to 
advertising a great amount of routing information on the Internet. 
•   Eliminates routing loops completely by adding AS path information to BGP route advertisements. 
•   Provides abundant policies to implement  flexible route filtering and selection. 
•   Provides good scalability. 
A router advertising BGP messages is called a BGP sp eaker. It establishes peer relationships with other 
BGP speakers to exchange routing information. When a BGP speaker receives a new route or a route 
better than the current one from another AS, it will advertise the route to all the other BGP peers in the 
local AS.  
To simplify configuration, multiple peers using an  identical policy can be organized as a peer group. 
BGP runs on a router in either of the following modes: 
•   IBGP (internal BGP) 
•   EBGP (external BGP) 
BGP is called IBGP when it runs within an AS , and is called EBGP when it runs between ASs. 
BGP messages formats 
Header 
BGP has the following types of messages: 
•  Open 
•   Update 
•   Notification
    Add page 877 to Favourites
    image text
    Enable zoom 
    							 188 
•  Keepalive 
•   Route -refresh 
They have the same header. 
Figure 71  BGP message header 
 
 
•  Marker —The 16-byte field is used to delimit BG P messages. The Marker must be all ones. 
•   Length —The two-byte unsigned integer indicates the total length of the message. 
•   Ty p e —This one-byte unsigned integer indicates the type code of the message. The following type 
codes are defined: 1–Open, 2-Update, 3-Notification, 4–Keepalive, and 5–Route-refresh. The 
former four listed codes are defined in RFC 1771, and the last listed code is defined in RFC 2918. 
Open 
After a TCP connection is established, the first messag e sent by each side is an open message for peer 
relationship establishment.  
Figure 72  BGP open message format 
 
 
Major fields of the BGP open message are as follows: 
•  Version —This one-byte unsigned integer indicates the protocol version number. The current BGP 
version is 4. 
•   My autonomous system —This two-byte unsigned integer indicates the autonomous system number 
of the sender. 
•   Hold time —When establishing a peer relationship, two par ties negotiate an identical hold time. If 
no Keepalive or Update is received from a peer within the hold time, the BGP connection is 
considered down. 
•   BGP identifier —An IP address that identifies the BGP router. 
•   Opt Parm Len (Optional Parameters Length) —Length of optional parameters, which is set to 0 if no 
optional parameter is available.
    Add page 878 to Favourites
    image text
    Enable zoom 
    							 189 
•  Optional parameters —Used for multiprotocol extensions and other functions. 
Update 
The update messages are used to exchange routing information between peers. It can advertise feasible 
routes or remove multiple unfeasible routes.  
Figure 73 BGP update message format 
 
 
Each update message can advertise a group of feasible  routes with identical attributes, and the routes 
are contained in the network layer reachability information (NLRI) field. The path attributes field carries 
the attributes of these routes. Each update message  can also carry multiple withdrawn routes in the 
withdrawn routes field. 
Major fields of the BGP update message are as follows: 
•   Unfeasible routes length —The total length of the withdrawn routes field in bytes. A value of 0 
indicates no route is withdrawn from service, nor is the withdrawn routes field present in this update 
message. 
•   Withdrawn routes —This is a variable length field that co ntains a list of withdrawn IP prefixes. 
•   Total path attribute length —Total length of the path attributes field in bytes. A value of 0 indicates 
that no NLRI field is present in this update message. 
•   Pat h at tribute s —List of path attributes related to NLRI. Each path attribute is a triple  of variable length. BGP uses these attributes to avoid routing loops, 
and perform routing and protocol extensions. 
•   NLRI — Each feasible route is represented as . 
Notification 
A  n o t i f i c a t i o n  m e s s a g e  i s  s e n t  w h e n  a n  e r ro r  i s  d e t e cted. The BGP connection is closed immediately after 
sending it.  
Figure 74  BGP notification message format 
 
 
Major fields of the BGP notification message are as follows: 
•  Error code —Type of notification. 
•   Error subcode —Specific information about the nature of the reported error. 
•   Data —Used to diagnose the reason for the notification . The contents of the data field depend on the 
error code and error subcode. Erroneous data can  be recorded in the data field. The data field 
length is variable. 
07 1 5 31
                                          DataError codeError subCode
    Add page 879 to Favourites
    image text
    Enable zoom 
    							 190 
Keepalive 
Keepalive messages are sent between peers to maintain connectivity. Its format contains only the 
message header. 
Route-refresh 
A route-refresh message is sent to a peer to reques t the specified address family routing information.  
Figure 75  BGP route-refresh message format 
 
 
•  AFI—Address family identifier. 
•   Res—Reserved; set to 0. 
•   SAFI —Subsequent address family identifier. 
BGP path attributes 
Path attributes classification 
BGP path attributes are a group of parameters enc apsulated in the path attributes field of update 
messages. They give detailed route attributes info rmation that can be used for route filtering and 
selection.  
Path attributes fall into the following categories: 
•   Well-known mandatory —Must be recognized by all BGP routers and be included in every Update 
message. Routing information errors occur without this attribute. 
•   Well-known discretionary —Can be recognized by all BGP routers and optionally included in every 
Update message as needed. 
•   Optional transitive —Transitive attribute between ASs. A BGP router not supporting this attribute 
can still receive routes with this attribute and advertise them to other peers. 
•   Optional non-transitive —If a BGP router does not support this attribute, it will not advertise routes 
with this attribute. 
The usage of each BGP path attribute is  described in the following table. 
Table 7  Usage of BGP path attributes 
Name Cate
gory 
ORIGIN Well-known  mandatory 
AS_PATH Well-known mandatory 
NEXT_HOP Well-known  mandatory 
LOCAL_PREF Well-known discretionary 
ATOMIC_AGGREGATE Well-known  discretionary 
AGGREGATOR Optional transitive 
COMMUNITY Optional transitive 
MULTI_EXIT_DISC (MED) Optional non-transitive 
ORIGINATOR_ID Optional  non-transitive
    Add page 880 to Favourites
    image text
    Enable zoom 
    							 191 
Name Category 
CLUSTER_LIST Optional  non-transitive 
 
Usage of BGP path attributes 
•  ORIGIN 
ORIGIN is a well-known mandatory attribute that  defines the origin of routing information (how a 
route became a BGP route). This attribute has the following types: 
{  IGP —Has the highest priority. Routes added to the BGP routing table using the  network 
command have the IGP attribute. 
{  EGP —Has the second highest priority. Routes obtained via EGP have the EGP attribute. 
{ INCOMPLETE —Has the lowest priority. The source of routes with this attribute is unknown, 
which does not mean such routes are unreachabl e. The routes redistributed from other routing 
protocols have the INCOMPLETE attribute. 
•   AS_PATH 
AS_PATH is a well-known mandatory attribute. This  attribute identifies the autonomous systems 
through which routing information carried in this  Update message has passed. When a route is 
advertised from the local AS to another AS, ea ch passed AS number is added into the AS_PATH 
attribute, so the receiver can determine ASs to  route the message back. The number of the AS 
closest to the receiver’s AS  is leftmost, as shown in Figure 76: 
Figure 76  AS_P

ATH attribute 
 
 
Generally, a BGP router does not receive routes co ntaining the local AS number to avoid routing 
loops.  
 
  NOTE: 
The current implementation supports using the  peer allow-as-loop command to receive routes containin
g
the local AS number in order to meet special requirements.  
8.0.0.0
AS 10
D = 8.0.0.0
(10) D = 8.0.0.0
(10)
AS 20 AS 40
D = 8.0.0.0
(20,10)
AS 30
AS 50
D = 8.0.0.0
(30,20,10)D = 8.0.0.0
(40,10)
    All HP manuals Comments (0)

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