[ Contents] [ Prev] [ Next] [ Index] [ Report an Error]

Example: Configuring Client-to-Client Reflection (OSPF)

Building on the topology shown in Example: Configuring the JCS 1200 Platform as a Route Reflector, this example shows how to configure routers for OSPF client-to-client route reflection.

Requirements

This example requires the following hardware and software components:

Overview and Topology

Figure 16: Example: Configuring Client-to-Client Reflection (OSPF)

Image g017297.gif

The example configuration shown in contains one router reflector (RR) and three client routers (R1, R2, and R3). The three routers (R1 through R3) and the route reflector (RR) are configured as PSDs that include Routing Engines on the JCS chassis.

The routers have the following loopback addresses:

With this configuration example, a route added to client router R1 is propagated to the route reflector (RR) and to the other client routers (R2, R3). This example uses OSPF as the IGP and enables BFD for the connections from the route reflector.

Configuration

First, configure protocols for the route reflector (RR), then configure protocols for the routers (R1, R2, and R3).

PSD15 Configuration (Route Reflector)

Step-by-Step Procedure

To configure the route reflector (PSD15):

  1. At the [edit routing-options] hierarchy level, include the autonomous-system 2 statement to configure the router’s AS number.
  2. At the [edit protocols] hierarchy level, include the bgp statement to enable BGP on the router.
  3. At the [edit protocols bgp] hierarchy level, include the group int statement to define the routing group.

    A BGP system must know which routers are its peers (neighbors). You define the peer relationship explicitly by configuring the neighboring routers that are the peers of the local BGP system. After peer relationships have been established, the BGP peers exchange update messages to advertise network reachability information.

  4. At the [edit protocols bgp group int] hierarchy level:
    1. Include the type internal statement to configure an internal BGP group.
    2. Include the local-address 10.12.1.1 statement to specify the address of the local end of a BGP session. This address is used to accept incoming connections to the peer and to establish connections to the remote peer.
    3. Include the cluster 1.2.3.4 statement to specify the cluster identifier (IPV4 address) to be used by the route reflector cluster in the internal BGP group.
    4. Include the neighbor 10.12.1.2, neighbor 10.12.1.2, and neighbor 10.12.1.4 statements to specify which routers (Router 1, Router 2, and Router 3) are peers (neighbors) of the route reflector.
  5. At the [edit protocols] hierarchy level, include the ospf statement to enable OSPF on the router.
  6. At the [edit protocols ospf] hierarchy level, include the overload statement to prevent other routers from attempting to route data traffic through the route reflector. This option is set in the route reflector (RR), but not in Router 1, 2, and 3.
  7. At the [edit protocols ospf] hierarchy level, include the area 0.0.0.0 statement to specify the area identifier for this router to use when participating in OSPF routing. All routers in the area must use the same area identifier to establish adjacencies.
  8. At the [edit protocols ospf area 0.0.0.0] hierarchy level, include the interface fxp1.1 statement to configure the internal Ethernet interface in the backbone area.
  9. At the [edit protocols ospf area 0.0.0.0 fxp1.1] hierarchy level, include the bfd-liveness-detection statement to specify bidirectional failure detection timers.
  10. At the [edit protocols ospf area 0.0.0.0 fxp1.1 bfd-liveness-detection] hierarchy level, include the minimum-interval 333 statement to specify 333 milliseconds as the minimum interval at which the local router transmits a hello packet and then expects to receive a reply from its BFD neighbor.
  11. Repeat steps 7 through 9 for the fxp1.0 internal Ethernet interface:
    1. At the [edit protocols ospf area 0.0.0.0] hierarchy level, include the interface fxp1.0 statement to configure the internal Ethernet interface in the backbone area.
    2. At the [edit protocols ospf area 0.0.0.0 fxp1.0] hierarchy level, include the bfd-liveness-detection statement to specify bidirectional failure detection timers.
    3. At the [edit protocols ospf area 0.0.0.0 fxp1.0 bfd-liveness-detection] hierarchy level, include the minimum-interval 333 statement to specify 333 milliseconds as the minimum interval at which the local router transmits a hello packet and then expects to receive a reply from its BFD neighbor.

Results

Display the results of the configuration:

routing-options {
autonomous-system 2;
}
protocols {
bgp {
group int {
type internal;
local-address 10.12.1.1;
cluster 1.2.3.4;
neighbor 10.12.1.2;
neighbor 10.12.1.3;
neighbor 10.12.1.4;
}
}
ospf {
overload;
area 0.0.0.0 {
interface fxp1.1 {
bfd-liveness-detection {
minimum-interval 333;
}
}
interface fxp0.1 {
bfd-liveness-detection {
minimum-interval 333;
}
}
}
}
}

PSD11 Configuration (Router 1)

Step-by-Step Procedure

To configure the route reflector (PSD11):

  1. At the [edit routing-options] hierarchy level, include the autonomous-system 2 statement to configure the router’s AS number.
  2. At the [edit protocols] hierarchy level, include the bgp statement to enable BGP on the router.
  3. At the [edit protocols bgp] hierarchy level, include the group int statement to define the routing group.
  4. At the [edit protocols bgp group int] hierarchy level:
    1. Include the type internal statement to configure an internal BGP group.
    2. Include the local-address 10.12.1.2 statement to specify the address of the local end of a BGP session. This address is used to accept incoming connections to the peer and to establish connections to the remote peer.
    3. Include the export nh-self statement to apply the nh-self policy to routes being exported from the routing table into BGP.
    4. Include the neighbor 10.12.1.1 statement to specify the route reflector (RR) as peer (neighbor) of Router 1. You do not need to include neighbor statements for Router 2 or Router 3.
  5. At the [edit protocols] hierarchy level, include the ospf statement to enable OSPF on the router.
  6. At the [edit protocols ospf] hierarchy level, include the area 0.0.0.0 statement to specify the area identifier for this router to use when participating in OSPF routing. All routers in the area must use the same area identifier to establish adjacencies.
  7. At the [edit protocols ospf area 0.0.0.0] hierarchy level, include the interface ge-1/1/1.0 statement to configure the Gigabit Ethernet interface in the backbone area.
  8. At the [edit protocols ospf area 0.0.0.0] hierarchy level, include the interface ge-1/1/0.0 statement to configure the Gigabit Ethernet interface in the backbone area.
  9. At the [edit policy-options] hierarchy level, include the policy-statement nh-self statement to define the nh-self policy.

    A routing policy contains one or more terms. The nh-self policy you are defining includes three terms (term a, term b, and term c). This policy is applied to routes exported from the routing table into BGP.

  10. At the [edit policy-options nh-self] hierarchy level, include the term a statement to define the first term for the nh-self policy.
  11. At the [edit policy-options nh-self term a] hierarchy level, include the following statements to specify that any static route with destination prefix 0.0.0.0/0 is rejected:
    from {
    protocol static;
    route-filter 0.0.0.0/0 exact;
    }
    then reject;
  12. At the [edit policy-options nh-self] hierarchy level, include the term b statement to define the next term for the nh-self policy.
  13. At the [edit policy-options nh-self term b] hierarchy level, include the following statements:
    from protocol static;
    then {
    next-hop self;
    accept;
    }

    These statements specify that for all remaining static routes, the next-hop address is replaced by the local IP address used for the BGP adjacency. The router is then accepted with the new, next-hop value.

  14. At the [edit policy-options nh-self] hierarchy level, include the term c statement to define the next term for the nh-self policy.
  15. At the [edit policy-options nh-self term c] hierarchy level, include the then reject statement to reject all other routes.

Results

Display the results of the configuration:

routing-options {
autonomous-system 2;
}
protocols {
bgp {
group int {
type internal;
local-address 10.12.1.2;
export nh-self;
neighbor 10.12.1.1;
}
}
ospf {
area 0.0.0.0 {
interface ge-1/1/1.0;
interface ge-1/1/0.0;
}
}
}
policy-options {
policy-statement nh-self {
term a {
from {
protocol static;
route-filter 0.0.0.0/0 exact;
}
then reject;
}
term b {
from protocol static;
then {
next-hop self;
accept;
}
}
term c {
then reject;
}
}
}

PSD12 Configuration (Router 2)

Step-by-Step Procedure

To configure the route reflector (PSD12):

  1. At the [edit routing-options] hierarchy level, include the autonomous-system 2 statement to configure the router’s AS number.
  2. At the [edit protocols] hierarchy level, include the bgp statement to enable BGP on the router.
  3. At the [edit protocols bgp] hierarchy level, include the group int statement to define the routing group.
  4. At the [edit protocols bgp group int] hierarchy level:
    1. Include the type internal statement to configure an internal BGP group.
    2. Include the local-address 10.12.1.3 statement to specify the address of the local end of a BGP session. This address is used to accept incoming connections to the peer and to establish connections to the remote peer.
    3. Include the export nh-self statement to apply the nh-self policy to routes being exported from the routing table into BGP.
    4. Include the neighbor 10.12.1.1 statement to specify the route reflector (RR) as peer (neighbor) of Router 2. You do not need to include neighbor statements for Router 1 or Router 3.
  5. At the [edit protocols] hierarchy level, include the ospf statement to enable OSPF on the router.
  6. At the [edit protocols ospf] hierarchy level, include the area 0.0.0.0 statement to specify the area identifier for this router to use when participating in OSPF routing. All routers in the area must use the same area identifier to establish adjacencies.
  7. At the [edit protocols ospf area 0.0.0.0] hierarchy level, include the interface ge-2/0/2.0 statement to configure the Gigabit Ethernet interface in the backbone area.
  8. At the [edit protocols ospf area 0.0.0.0] hierarchy level, include the interface ge-2/0/3.0 statement to configure the Gigabit Ethernet interface in the backbone area.
  9. At the [edit protocols ospf area 0.0.0.0] hierarchy level, include the interface ge-2/0/1.0 statement to configure the Gigabit Ethernet interface in the backbone area.
  10. At the [edit protocols ospf area 0.0.0.0 interface ge-2/0/1.0] hierarchy level, include the bfd-liveness-detection statement to specify bidirectional failure detection timers.
  11. At the [edit protocols ospf area 0.0.0.0 interface ge-2/0/1.0 bfd-liveness-detection] hierarchy level, include the minimum-interval 333 statement to specify 333 milliseconds as the minimum interval at which the local router transmits a hello packet and then expects to receive a reply from its BFD neighbor.
  12. At the [edit policy-options] hierarchy level, include the policy-statement nh-self statement to define the nh-self policy.

    A routing policy contains one or more terms. The nh-self policy you are defining includes three terms (term a, term b, and term c). This policy is applied to routes exported from the routing table into BGP.

  13. At the [edit policy-options nh-self] hierarchy level, include the term a statement to define the first term for the nh-self policy.
  14. At the [edit policy-options nh-self term a] hierarchy level, include the following statements to specify that any static route with destination prefix 0.0.0.0/0 or destination prefix 10.12.1.1/32 is rejected:
    from {
    protocol static;
    route-filter 0.0.0.0/0 exact;
    route-filter 10.12.1.1/32 exact;
    }
    then reject;
  15. At the [edit policy-options nh-self] hierarchy level, include the term b statement to define the next term for the nh-self policy.
  16. At the [edit policy-options nh-self term b] hierarchy level, include the following statements:
    from protocol static;
    then {
    next-hop self;
    accept;
    }

    These statements specify that for all remaining static routes, the next-hop address is replaced by the local IP address used for the BGP adjacency. The router is then accepted with the new, next-hop value.

  17. At the [edit policy-options nh-self] hierarchy level, include the term c statement to define the next term for the nh-self policy.
  18. At the [edit policy-options nh-self term c] hierarchy level, include the then reject statement to reject all other routes.

Results

Display the results of the configuration:

routing-options {
autonomous-system 2;
}
protocols {
bgp {
group int {
type internal;
local-address 10.12.1.3;
export nh-self;
neighbor 10.12.1.1;
}
}
ospf {
area 0.0.0.0 {
interface ge-2/0/2.0;
interface ge-2/0/3.0;
interface ge-2/0/1.0 {
bfd-liveness-detection {
minimum-interval 333;
}
}
}
}
}
policy-options {
policy-statement nh-self {
term a {
from {
protocol static;
route-filter 0.0.0.0/0 exact;
route-filter 10.12.1.1/32 exact;
}
then reject;
}
term b {
from protocol static;
then {
next-hop self;
accept;
}
}
term c {
then reject;
}
}
}

PSD13 Configuration (Router 3)

Step-by-Step Procedure

To configure the route reflector (PSD13):

  1. At the [edit routing-options] hierarchy level, include the autonomous-system 2 statement to configure the router’s AS number.
  2. At the [edit protocols] hierarchy level, include the bgp statement to enable BGP on the router.
  3. At the [edit protocols bgp] hierarchy level, include the group int statement to define the routing group.
  4. At the [edit protocols bgp group int] hierarchy level:
    1. Include the type internal statement to configure an internal BGP group.
    2. Include the local-address 10.12.1.4 statement to specify the address of the local end of a BGP session. This address is used to accept incoming connections to the peer and to establish connections to the remote peer.
    3. Include the export nh-self statement to apply the nh-self policy to routes being exported from the routing table into BGP.
    4. Include the neighbor 10.12.1.1 statement to specify the route reflector (RR) as peer (neighbor) of Router 3. You do not need to include neighbor statements for Router 1 or Router 2.
  5. At the [edit protocols] hierarchy level, include the ospf statement to enable OSPF on the router.
  6. At the [edit protocols ospf] hierarchy level, include the area 0.0.0.0 statement to specify thearea identifier for this router to use when participating in OSPF routing. All routers in the area must use the same area identifier to establish adjacencies.
  7. At the [edit protocols ospf area 0.0.0.0] hierarchy level, include the interface ge-0/2/3.0 statement to configure the Gigabit Ethernet interface in the backbone area.
  8. At the [edit protocols ospf area 0.0.0.0] hierarchy level, include the interface ge-0/1/7.0 statement to configure the Gigabit Ethernet interface in the backbone area.
  9. At the [edit protocols ospf area 0.0.0.0] hierarchy level, include the interface ge-0/1/0.0 statement to configure the Gigabit Ethernet interface in the backbone area.
  10. At the [edit protocols ospf area 0.0.0.0 interface ge-0/1/0.0] hierarchy level, include the bfd-liveness-detection statement to specify bidirectional failure detection timers.
  11. At the [edit protocols ospf area 0.0.0.0 interface ge-0/1/0.0 bfd-liveness-detection] hierarchy level, include the minimum-interval 333 statement to specify 333 milliseconds as the minimum interval at which the local router transmits a hello packet and then expects to receive a reply from its BFD neighbor.
  12. At the [edit policy-options] hierarchy level, include the policy-statement nh-self statement to define the nh-self policy.

    A routing policy contains one or more terms. The nh-self policy you are defining includes three terms (term a, term b, and term c). This policy is applied to routes exported from the routing table into BGP.

  13. At the [edit policy-options nh-self] hierarchy level, include the term a statement to define the first term for the nh-self policy.
  14. At the [edit policy-options nh-self term a] hierarchy level, include the following statements to specify that any static route with destination prefix 0.0.0.0/0 is rejected:
    from {
    protocol static;
    route-filter 0.0.0.0/0 exact;
    }
    then reject;
  15. At the [edit policy-options nh-self] hierarchy level, include the term b statement to define the next term for the nh-self policy.
  16. At the [edit policy-options nh-self term b] hierarchy level, include the following statements:
    from protocol static;
    then {
    next-hop self;
    accept;
    }

    These statements specify that for all remaining static routes, the next-hop address is replaced by the local IP address used for the BGP adjacency. The router is then accepted with the new, next-hop value.

  17. At the [edit policy-options nh-self] hierarchy level, include the term c statement to define the next term for the nh-self policy.
  18. At the [edit policy-options nh-self term c] hierarchy level, include the then reject statement to reject all other routes.

Results

Display the results of the configuration:

routing-options {
autonomous-system 2;
}
protocols {
bgp {
group int {
type internal;
local-address 10.12.1.4;
export nh-self;
neighbor 10.12.1.1;
}
}
ospf {
area 0.0.0.0 {
interface ge-0/2/3.0;
interface ge-0/1/7.0;
interface ge-0/1/0.0 {
bfd-liveness-detection {
minimum-interval 333;
}
}
}
}
}
policy-options {
policy-statement nh-self {
term a {
from {
protocol static;
route-filter 0.0.0.0/0 exact;
}
then reject;
}
term b {
from protocol static;
then {
next-hop self;
accept;
}
}
term c {
then reject;
}
}
}

Related Topics

[ Contents] [ Prev] [ Next] [ Index] [ Report an Error]

[an error occurred while processing this directive]