SYSTEM ADMINISTRATOR GUIDE     62/1543-CRA 119 1170/1-V1 Uen A    

Configuring Bindings

© Copyright Ericsson AB 2009. All rights reserved.

Disclaimer

No part of this document may be reproduced in any form without the written permission of the copyright owner. The contents of this document are subject to revision without notice due to continued progress in methodology, design and manufacturing. Ericsson shall have no liability for any error or damage of any kind resulting from the use of this document.

Trademark List

SmartEdge is a registered trademark of Telefonaktiebolaget L M Ericsson.
NetOp is a trademark of Telefonaktiebolaget L M Ericsson.

Contents

1Overview
1.1Types of Bindings
1.2Binding Guidelines
1.3Binding Summary Tables
1.4Related Information

2

Configuration and Operations Tasks
2.1Create a Static Binding
2.2Create a Dynamic Binding
2.3Display Bindings Status

3

Configuration Examples
3.1Static Binding for a Single Circuit to an Interface
3.2Static Binding for Multiple Circuits
3.3Restricted Dynamic Binding for a Circuit


1   Overview

This document describes how to bind a SmartEdge interface to a port, channel, or circuit. Static bindings to circuits include permanent virtual circuits (PVCs), child circuits, link groups, clientless IP service selection (CLIPS) PVCs, and Generic Routing Encapsulation (GRE) tunnel circuits. Dynamic bindings attach to dynamically created subscribers circuits. The administration and monitoring of bindings is also described.

A binding forms the association in the SmartEdge router between a port, channel, or circuit and the higher-layer interface over which routing protocols are configured for a given context. No subscriber data can flow on a port, channel, or circuit until some higher-layer service is configured and associated with it. After you bind a port, channel, or circuit to an interface, traffic flows through the port, channel, or circuit as it would through any IP router.

Note:  
Unless otherwise noted, the SmartEdge 100 router supports all commands described in this document.

Note:  
Throughout this document, the term circuit refers to Asynchronous Transfer Mode (ATM), Frame Relay, 802.1Q, and CLIPS PVCs, and Point-to-Point Protocol over Ethernet (PPPoE)-encapsulated child circuits on ATM and 802.1Q PVCs.

Note:  
When IP Version 6 (IPv6) addresses are not referenced or explicitly specified, the term IP address can refer generally to IP Version 4 (IPv4) addresses, IPv6 addresses, or IP addressing. In instances where IPv6 addresses are referenced or explicitly specified, the term IP address refers only to IPv4 addresses. For a description of IPv6 addressing and the types of IPv6 addresses, see RFC 3513, Internet Protocol Version 6 (IPv6) Addressing Architecture.

1.1   Types of Bindings

Bindings are either static, to a fixed interface, or dynamic, based on subscriber characteristics as defined in the local database or on a Remote Authentication Dial-In User Service (RADIUS) server.

Static binding occurs when you bind the port, channel, or circuit directly to an interface. In this case, the port, channel, or circuit is hard-wired to the higher-layer protocols defined for the interface. This is the simplest form of binding available in the SmartEdge router , and provides functions similar to those provided by traditional network devices, such as routers. You can create a static binding for any port, channel, or circuit with any encapsulation type.

Dynamic binding occurs when you bind a port, channel, or circuit to the higher-layer protocols based on session information. Dynamic binding enables SmartEdge router advanced features, such as dynamic service and provider selection. Dynamic bindings can be restricted or unrestricted:

Note:  
You do not bind Layer 2 Tunneling Protocol (L2TP) peers or groups.

1.2   Binding Guidelines

Follow these guidelines to determine whether the port, channel, PVC, child circuit, link group, or GRE tunnel circuit is to be bound:

1.3   Binding Summary Tables

This section provides binding options for each type of port, channel and circuit.

Note:  

The following types of ports and channels are not bound; the channels and circuits configured on them are bound instead:


1.3.1   Bindings for POS Ports with and without Frame Relay PVCs

Table 1 lists the binding options for POS ports on OC-3c/STM-1c, OC-12c/STM-4c, and OC-48c/STM-16c cards.

Note:  
POS ports configured with Frame Relay encapsulation are not bound; the Frame Relay PVCs are bound instead. Entering the bind command in port configuration mode displays an error message.

Table 1    Binding Options for POS Ports with and Without Frame Relay PVCs

Type of Binding

Bind Command

Port Encapsulation

PPP

Port Encapsulation

Cisco HDLC

Port Encapsulation

Frame Relay

PVC Encapsulation

Frame Relay

Dynamic

authentication

No

No

No

No

Static

interface

Yes

Yes

No

Yes

 

subscriber

No

No

No

No

 

auto-subscriber

No

No

No

No

Note:  
A POS port in an APS group is bound only if it is a working port; you do not bind the protect port.

1.3.2   Bindings for PDH Channels and Ports With and Without Frame Relay PVCs

Table 2 lists the binding options for the following types of channels and ports:

Table 2    Binding Options for Channels and Ports With and Without Frame Relay PVCs

Type of Binding

Bind Command

Channel or Port Encapsulation

PPP

Channel or Port Encapsulation

Cisco HDLC

Channel or Port Encapsulation

Frame Relay

PVC Encapsulation

Frame Relay

Dynamic

authentication

No

No

No

No

Static

interface

Yes

Yes

No

Yes

subscriber

No

No

No

No

auto-subscriber

No

No

No

No

Note:  
Channels and ports configured with Frame Relay encapsulation are not bound; the Frame Relay PVCs are bound instead. Entering the bind command for the channel or port in the appropriate configuration mode displays an error message.

1.3.3   Bindings for FE and GE Ports and 802.1Q PVCs

Table 3 lists the binding options for FE and GE ports.

Table 3    Binding Options for FE and GE Ports

Type of Binding

Bind Command

Port Encapsulation

IPoE

Port Encapsulation

PPPoE

Port Encapsulation

802.1Q (dot1q)

Dynamic

authentication

No

Yes

No

Static

interface

Yes

No

Yes

 

subscriber

No

No

No

 

auto-subscriber

No

No

No

Table 4 lists the binding options for static and on-demand 802.1Q PVCs.

Table 4    Binding Options for Static and On-Demand 802.1Q PVCs

Type of Binding

Bind Command

Type of PVC

802.1Q PVC Encapsulation

IPoE

Multi

PPPoE

Dynamic

authentication

Static or on-demand

No

No

Yes

Static

interface

Static only

Yes

Yes

No

 

subscriber

Static or on-demand

Yes

Yes

No

 

auto-subscriber

On-demand only

No

No

No

Note:  
When an 802.1Q PVC is configured with encapsulation, the parent circuit is encapsulated with IP over Ethernet (IPoE) encapsulation. Table 9 lists binding options for the child circuits.

1.3.4   Bindings for ATM PVCs

Table 5 lists the binding options for static and on-demand ATM PVCs configured on ATM OC or ATM DS-3 ports.

Table 5    Binding Options for Static and On-Demand ATM PVCs

Type of Binding

Bind Command

Type of ATM PVC

Encapsulation

Bridge1483

Multi

Route1483

Raw

PPP

PPPoE

Dynamic

authentication

 

No

No

No

No

Yes

Yes

Static

interface

Static only

Yes

Yes

Yes

No

No

No

 

subscriber

See Note

Yes

Yes

Yes

No

Yes

No

 

auto-subscriber

Static or on-demand

Yes

Yes

Yes

No

Yes

No

Note:  
You can use the bind subscriber command in ATM PVC configuration mode for a single on-demand ATM PVC if you have configured the PVC with the aaa keyword to use the Remote Authentication Dial-In User Service (RADIUS) to supply the binding, or for a single static ATM PVC.

The following guidelines apply to the encapsulations in Table 5

The following guidelines apply to the subscriber and auto-subscriber commands in Table 5

1.3.5   Bindings for CLIPS PVCs

The following guidelines apply to binding CLIPS PVCs:

Table 6 lists the binding options for Ethernet ports with static CLIPS PVCs configured on them.

Table 6    Binding Options for Static CLIPs PVCs on Ethernet Ports

Type of Binding

Bind Command

Port Encapsulation

IPoE

Port Encapsulation

PPPoE

Port Encapsulation

802.1Q (dot1q)

Static CLIPS PVC Encapsulation

IPoE

Dynamic

authentication

No

Yes

No

No

Static

interface

Yes

No

Yes

No

 

subscriber

No

No

No

Yes

 

auto-subscriber

No

No

No

Yes

Table 7 lists the binding options for static 802.1Q PVCs with static CLIPS PVCs configured on them.

Table 7    Binding Options for Static CLIPS PVCs on Static 802.1Q PVCs

Type of Binding

Bind Command

802.1Q PVC Encapsulation

IPoE

802.1Q PVC Encapsulation

Multi

802.1Q PVC Encapsulation

PPPoE

Static CLIPS PVC Encapsulation

IPoE

Dynamic

authentication

No

No

Yes

No

Static

interface

Yes

Yes

No

No

 

subscriber

Yes

Yes

No

Yes

 

auto-subscriber

No

No

No

Yes

Table 8 lists the binding options for static ATM PVCs with static CLIPS PVCs configured on them.

Table 8    Binding Options for Static ATM PVCs with Static CLIPS PVCs

Type of Binding

Bind Command

ATM PVC Encapsulation

Bridge1483

Static CLIPS PVC Encapsulation

IPoE

Dynamic

authentication

No

No

Static

interface

Yes

No

 

subscriber

Yes

Yes

 

auto-subscriber

Yes

Yes

The following guidelines apply to the subscriber and auto-subscriber commands in Table 8

1.3.6   Bindings for Child Circuits

Table 9 lists the binding options for the child circuits on ATM PVCs and 802.1Q PVCs with multiprotocol encapsulation.

Table 9    Binding Options for Child Circuits

Type of Binding

Bind Command

Encapsulation

IPv6oE

Encapsulation

PPPoE

Dynamic

authentication

No

Yes

Static

interface

No

No

 

subscriber

No

No

 

auto-subscriber

No

No

Note:  
Child circuits configured with IP Version 6 over Ethernet (IPv6oE) encapsulation are not bound, but are cross-connected instead.

1.4   Related Information

Other documents with related commands include:

2   Configuration and Operations Tasks

To configure a binding, perform the tasks described in one of the following sections:

2.1   Create a Static Binding

To create a static binding, perform one of the task options described in Table 10.

Table 10    Create a Static Binding

Task(1)

Root Command

Notes

Statically bind a circuit to allow it to be cross-connected.

bind bypass

Enter this command in ATM child circuit, ATM PVC, dot1q child circuit, or dot1q PVC configuration mode.

Statically bind a port, channel, or circuit to a previously created interface in the specified context.

bind interface

Enter this command in ATM PVC, dot1q PVC, DS-0, DS-1, DS-3, E1, Frame Relay PVC, GRE tunnel, IPv6 tunnel, link group, link PVC, or port configuration mode.

Statically bind a circuit to an interface using the IP address in a subscriber record.

bind subscriber

Enter this command in ATM PVC, CLIPS PVC, or dot1q PVC configuration mode.

Statically bind multiple circuits to an interface and automatically generate subscriber names and optional passwords.

bind auto-subscriber

Enter this command in ATM or CLIPS PVC configuration mode.

(1)  Select only one of the task options.

2.2   Create a Dynamic Binding

To create a dynamic binding, perform one of the task options described in Table 11; enter this command in ATM PVC, dot1q PVC, port, ATM child protocol, or dot1q child protocol configuration mode.

Table 11    Create a Dynamic Binding

Task(1)

Root Command

Notes

Dynamically bind a port or circuit through a subscriber record or remotely through a RADIUS record without restrictions.

bind authentication

You must specify the context to restrict the binding.

Dynamically bind a circuit to an interface using the IP address in a subscriber record and restrict the binding to a specific context.

bind authentication

 

(1)  Select only one of the following task options

2.3   Display Bindings Status

To display bindings status use the show bindings command listed in Table 12; enter the command in any mode.

Table 12    Display Bindings Status

Task

Root Command

Display configured bindings for one or more subscribers, ports, , channel or permanent virtual circuits (PVCs) on the system.

show bindings

3   Configuration Examples

This section provides examples of configuring static binding for a single circuit in an interface, static binding for multiple circuits, and restricted dynamic binding for a circuit.

3.1   Static Binding for a Single Circuit to an Interface

The following example shows how to create a static binding between the Ethernet management port and an interface configured in the local context:

[local]Redback#configure
[local]Redback(config)#context local
[local]Redback(config-ctx)#interface mgmt
[local]Redback(config-if)#ip address 1.2.3.4/24
[local]Redback(config-if)#exit
[local]Redback(config-ctx)#exit
[local]Redback(config)#port ethernet 7/1
[local]Redback(config-port)#bind interface mgmt local

3.2   Static Binding for Multiple Circuits

The following example shows how to create 10 ATM PVCs with a virtual path identifier (VPI) value of 100, and virtual circuit identifier (VCI) values ranging from 100 to 109, then use the bind auto-subscriber command to statically bind each PVC to an automatically generated subscriber record beginning with the string DSL:

[local]Redback(config)#port atm 3/1
[local]Redback(config-port)#atm pvc explicit 100:100 through 100:109 profile encapsulation route1483
[local]Redback(config-pvc)#bind auto-subscriber DSL local

3.3   Restricted Dynamic Binding for a Circuit

The following example shows how to limit subscriber sessions on the PPP-encapsulated ATM PVC to the isp.net context:

[local]Redback(config)#port atm 3/1
[local]Redback(config-port)#atm pvc 100 101 profile ubr encapsulation ppp
[local]Redback(config-pvc)#bind authentication pap context isp.net