Filter
Top Products
Advanced Configuration and Management Guide
USING THE WEB MANAGEMENT INTERFACE
1. Log on to the device using a valid user name and password for read-write access. The System configuration
panel is displayed.
2. Click on the plus sign next to Configure in the tree view to expand the list of configuration options.
3. Click on the plus sign next to BGP in the tree view to expand the list of BGP option links.
4. Click on the General
link to display the BGP configuration panel, shown in Figure 10.2 on page 10-8.
5. If route reflection is not already enabled, select Enable next to Client To Client Reflection.
6. If the autonomous system (AS) the routing switch is in will contain more than one route reflector (a route
reflector in addition to the routing switch), enter a cluster ID in the Cluster ID field. The cluster ID is required
to avoid loops in an AS that contains more than one route reflector.
7. Click the Apply button to apply the changes to the device’s running-config file.
8. Click on the Neighbor link at the bottom of the BGP configuration panel or under BGP in the Configure section
of the tree view.
9. If you have already configured neighbors, a table listing the neighbors is displayed. Click Modify next to the
neighbor you want to identify as a route reflector client or select the Add Neighbor
link. The BGP
configuration panel is displayed.
10. Configure or change other parameters if needed, then identify this neighbor as a route reflector client by
selecting Enable next to Client To Client Reflection. See “Adding BGP4 Neighbors” on page 10-14 for
information about the other neighbor parameters.
11. Click the Add button to apply the changes to the device’s running-config file.
12. Select the Save
link at the bottom of the dialog. Select Yes when prompted to save the configuration change
to the startup-config file on the device’s flash memory.
Configuring Confederations
A confederation is a BGP4 Autonomous System (AS) that has been subdivided into multiple, smaller ASs.
Subdividing an AS into smaller ASs simplifies administration and reduces BGP-related traffic, thus reducing the
complexity of the Interior Border Gateway Protocol (IBGP) mesh among the BGP routers in the AS.
The HP implementation of this feature is based on RFC 1965.
Normally, all BGP routers within an AS must be fully meshed, so that each BGP router has interfaces to all the
other BGP routers within the AS. This is feasible in smaller ASs but becomes unmanageable in ASs containing
many BGP routers.
When you configure BGP routers into a confederation, all the routers within a sub-AS (a subdivision of the AS) use
IBGP and must be fully meshed. However, routers use EBGP to communicate between different sub-ASs.
NOTE: Another method for reducing the complexity of an IBGP mesh is to use route reflection. However, if you
want to run different Interior Gateway Protocols (IGPs) within an AS, configure a confederation. You can run a
separate IGP within each sub-AS.
To configure a confederation, configure groups of BGP routers into sub-ASs. A sub-AS is simply an AS. The term
“sub-AS” distinguishes ASs within a confederation from ASs that are not in a confederation. For the viewpoint of
remote ASs, the confederation ID is the AS ID. Remote ASs do not know that the AS represents multiple sub-ASs
with unique AS IDs.
NOTE: You can use any valid AS numbers for the sub-ASs. If your AS is connected to the Internet, HP
recommends that you use numbers from within the private AS range (64512 – 65535). These are private ASs
numbers and BGP4 routers do not propagate these AS numbers to the Internet.
10 - 36