![]() |
SYSTEM ADMINISTRATOR GUIDE 62/1543-CRA 119 1170/1-V1 Uen B | ![]() |
Copyright
© Ericsson AB 2009–2010. All rights reserved. No part of this document may be reproduced in any form without the written permission of the copyright owner.
Disclaimer
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 LM Ericsson. | |
NetOp | is a trademark of Telefonaktiebolaget LM Ericsson. |
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.
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:
Follow these guidelines to determine whether the port, channel,, PVC, child circuit, link group, or GRE tunnel circuit is to be bound:
This section provides binding options for each type of port, channel and circuit.
The following types of ports and channels are not bound; the channels and circuits configured on them are bound instead:
Table 1 lists the binding options for POS ports on OC-3c/STM-1c, OC-12c/STM-4c, and OC-48c/STM-16c cards.
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 |
Table 2 lists the binding options for the following types of channels and ports:
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 |
Table 3 lists the 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.
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 |
Table 5 lists the binding options for static and on-demand ATM PVCs configured on ATM OC or ATM DS-3 ports.
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 |
The following guidelines apply to the encapsulations in Table 5
The following guidelines apply to the subscriber and auto-subscriber commands in Table 5
The following guidelines apply to binding CLIPS PVCs:
Table 6 lists the binding options for Ethernet ports with static CLIPS PVCs configured on them.
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.
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.
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
Table 9 lists the binding options for the child circuits on ATM PVCs and 802.1Q PVCs with multiprotocol encapsulation.
Type of Binding |
Bind Command |
Encapsulation IPv6oE |
Encapsulation PPPoE |
---|---|---|---|
Dynamic |
authentication |
No |
Yes |
Static |
interface |
No |
No |
subscriber |
No |
No | |
auto-subscriber |
No |
No |
Other documents with related commands include:
To configure a binding, perform the tasks described in one of the following sections:
To create a static binding, perform one of the task options described in Table 10.
Task(1) |
Root Command |
Notes |
---|---|---|
Statically bind a circuit to allow it to be cross-connected. |
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. |
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. |
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. |
Enter this command in ATM or CLIPS PVC configuration mode. |
(1) Select only one of the task options.
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.
Task(1) |
Root Command |
Notes |
---|---|---|
Dynamically bind a port or circuit through a subscriber record or remotely through a RADIUS record without restrictions. |
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. |
(1) Select only one of the following task options
To display bindings status use the show bindings command listed in Table 12; enter the command in any mode.
Task |
Root Command |
---|---|
Display configured bindings for one or more subscribers, ports, , channel or permanent virtual circuits (PVCs) on the system. |
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.
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
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
The following example shows how to create 20 Dot1Q PVCs and bind them to the interface named california in the local context:
[local]Redback(config)#port ethernet 5/1 [local]Redback(config-port)#encap dot1q [local]Redback(config-port)#dot1q pvc explicit 20 through 40 [local]Redback(config-dot1q-pvc)#bind interface california local
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