Providing Connectivity Using ATM Routed Bridge Encapsulation over PVCs

ATM RBE is used to route IP over bridged RFC 1483 Ethernet traffic from a stub-bridged LAN.

The figure below shows an ATM subinterface on a headend router that is configured to function in ATM routed-bridge encapsulation mode. This configuration is useful when a remote bridged Ethernet network device needs connectivity to a routed network via a device bridging from an Ethernet LAN to an ATM RFC 1483 bridged encapsulation.

Figure 1

ATM Routed Bridge Encapsulation

Because PVCs are statically configured along the entire path between the end systems, it would not be suitable to route bridged encapsulated traffic over them when the user wants to configure the virtual circuits (VCs) dynamically and tear down the VCs when there is no traffic.

You can configure ATM routed bridge encapsulation using an ATM PVC range rather than individual PVCs. When you configure a PVC range for routed bridge encapsulation, a point-to-point subinterface is created for each PVC in the range. The number of PVCs in a range can be calculated using the following formula:

number of PVCs = (end-vpi - start-vpi + 1) x (end-vci - start-vci +1)

Subinterface numbering begins with the subinterface on which the PVC range is configured and increases sequentially through the range.

Note	You cannot explicitly configure the individual point-to-point subinterfaces created by the PVC range on a point-to-point subinterface. All the point-to-point subinterfaces in the range share the same configuration as the subinterface on which the PVC range is configured.

The DHCP relay agent information option (option 82) enables a Dynamic Host Configuration Protocol (DHCP) relay agent to include information about itself when forwarding client-originated DHCP packets to a DHCP server. The DHCP server can use this information to implement IP address or other parameter-assignment policies.

The DHCP Option 82 Support for RBE feature provides support for the DHCP relay agent information option when ATM RBE is used. The figure below shows a typical network topology in which ATM RBE and DHCP are used. The aggregation router that is using ATM RBE is also serving as the DHCP relay agent.

Figure 2

Network Topology Using ATM RBE and DHCP

This feature communicates information to the DHCP server using a suboption of the DHCP relay agent information option called agent remote ID. The information sent in the agent remote ID includes an IP address identifying the relay agent and information about the ATM interface and the PVC over which the DHCP request came in. The DHCP server can use this information to make IP address assignments and security policy decisions.

The figure below shows the format of the agent remote ID suboption.

Figure 3

Format of the Agent Remote ID Suboption

The table below describes the agent remote ID suboption fields displayed in the figure above.

The figure below shows the format of the network access server (NAS) port field in the agent remote ID suboption.

Figure 4

Format of the NAS Port Field

The figure below shows the format of the interface field. If there is no module, the value of the module bit is 0.

Figure 5

Format of the Interface Field

The DHCP lease limit per ATM RBE Unnumbered Interface feature is enabled on a Cisco IOS DHCP relay agent connected to clients through unnumbered interfaces. The relay agent keeps information about the DHCP leases offered to the clients per subinterface. When a DHCPACK message is forwarded to the client, the relay agent increments the number of leases offered to clients on that subinterface. If a new DHCP client tries to obtain an IP address and the number of leases has already reached the configured lease limit, DHCP messages from the client will be dropped and will not be forwarded to the DHCP server.

If this feature is enabled on the Cisco IOS DHCP server directly connected to clients through unnumbered interfaces, the server allocates addresses and increments the number of leases per subinterface. If a new client tries to obtain an IP address, the server will not offer an IP address if the number of leases on the subinterface has already reached the configured lease limit.

Cisco IOS High Availability (HA) functionality for broadband protocols and applications allows for stateful switchover (SSO) and In-Service Software Upgrade (ISSU) that minimize planned and unplanned downtime and failures. HA uses the cluster control manager (CCM) to synchronize the subscriber sessions on the standby processor of a redundant processor system. Use the show ccm clients command to display information about the CCM clients. Use the show ccm sessions command to display information about CCM sessions on active and standby processors. Use the show subscriber policy command to display information about subscriber redundancy policies.

In Cisco IOS Release 15.1(1)S and later releases, all ATM RBE features are supported with SSO and ISSU.

Bridged IP packets received on an ATM interface configured in routed-bridge mode are routed via the IP header. Such interfaces take advantage of the characteristics of a stub LAN topology commonly used for digital subscriber line (DSL) access and offer increased performance and flexibility over integrated routing and bridging (IRB).

Another benefit of ATM RBE is that it reduces the security risk associated with normal bridging or IRB by reducing the size of the nonsecured network. By using a single VC allocated to a subnet (which could be as small as a single IP address), ATM RBE uses an IP address in the subnet to limit the "trust environment" to the premises of a single customer.

ATM RBE supports Cisco Express Forwarding (CEF), fast switching, and process switching.

The DHCP Option 82 Support for RBE feature enables those service providers to use DHCP to assign IP addresses and DHCP option 82 to implement security and IP address assignment policies.

The DHCP Lease Limit per ATM RBE Unnumbered Interface feature allows an Internet service provider (ISP) to globally limit the number of leases available to clients per household or connection.

1.    enable

2.    configure terminal

3.    interface atm slot / 0 . subinterface-number point-to-point

4.   Do one of the following:

5.    exit

6.    ip address ip-address mask [secondary]

7.    end

8.   Do one of the following:

Router# show arp
 
Protocol  Address          Age (min)  Hardware Addr   Type   Interface
Internet 	209.165.201.51          6   0001.c9f2.a81d  ARPA   Ethernet3/1
Internet 	209.165.201.49          -   0060.0939.bb55  ARPA   Ethernet3/1
Internet 209.165.202.128         30   0010.0ba6.2020  ARPA   Ethernet3/0
Internet 209.165.201.52           6   00e0.1e8d.3f90  ARPA   ATM1/0.4
Internet 209.165.201.53           5   0007.144f.5d20  ARPA   ATM1/0.2
Internet 209.165.202.129          -   0060.0939.bb54  ARPA   Ethernet3/0
Internet 209.165.201.125         30   00b0.c2e9.bc55  ARPA   Ethernet3/1#
Router# show ip cache verbose
IP routing cache 3 entries, 572 bytes
   9 adds, 6 invalidates, 0 refcounts
Minimum invalidation interval 2 seconds, maximum interval 5 seconds,
   quiet interval 3 seconds, threshold 0 requests
Invalidation rate 0 in last second, 0 in last 3 seconds
Last full cache invalidation occurred 00:30:34 ago
Prefix/Length       Age       Interface 	Next Hop
209.165.201.51/32-24 00:30:10  Ethernet3/1 10.1.0.51 14  0001C9F2A81D00600939 BB550800
209.165.202.129/32-24 00:00:04 ATM1/0.2 	10.8.100.50 28  00010000AAAA030080C2000700000007144F5D2000600939 BB1C0800
209.165.201.125/32-24 00:06:09 ATM1/0.4 	10.8.101.35 28  00020000AAAA030080C20007000000E01E8D3F9000600939 BB1C0800

1.    enable

2.    configure terminal

3.    ip dhcp relay information option

4.    rbe nasip source-interface

5.    end

1.    enable

2.    configure terminal

3.    ip dhcp limit lease per interface lease-limit

4.    end

1.    enable

2.    debug ip dhcp server packet

3.    debug ip dhcp server events