722CHAPTER 51: CONFIGURING DCC

Configuring MP binding in resource-shared DCC

If an interface is a serial, asynchronous interface or an AUX interface, then the resource-shared DCC will enable another physical interface in the dialer bundle of the dialer interface whenever the percentage of traffic on the physical interface to the bandwidth exceeds the traffic threshold. At the same time, it implements MP binding on these links. If the physical interface is an ISDN BRI or PRI interface, the resource-shared DCC will first select the available B channels on the interface, and then the B channels on other ISDN interfaces to implement MP binding.

Use the link-protocol ppp or ppp mp command to configure PPP encapsulation and MP binding in dial interface (physical or dialer interface) view, and use the dialer threshold command to configure a traffic-percentage threshold for MP binding in dialer interface view.

Table 756 Configure MP Binding in Resource-Shared DCC

Operation

Command

 

 

Set a traffic-percentage threshold for MP

dialer threshold traffic-percentage

binding

[ in-out in out ]

 

 

Restore the default traffic-percentage

undo dialer threshold

threshold of MP binding (that is, no flow

 

control will be implemented).

 

 

 

Enable PPP encapsulation

link-protocol ppp

 

 

Configure MP binding on interfaces

ppp mp [ interface virtual-template

 

number ]

 

 

By default, neither MP binding, nor traffic-percentage threshold is configured.

That is, MP binding is not supported.

Configuring PPP When configuring PPP callback, one endpoint of a connection should be Callback configured as client, and the other endpoint as server. The calling party is the

callback client and the called party is the callback server. The client first originates a call, and the server determines whether to originate a return call. If it determines to do that, the callback server disconnects and then originates a return call according to the information such as user name or callback number.

Configure PPP callback after completing the basic configuration of Circular DCC or

Resource-Shared DCC.

PPPcallback implementation requires authentication. The users are recommended to configure PAP or CHAP authentication on both the physical and dialer interfaces on both the callback client and server.

Configuring PPP callback in the circular DCC implementation

1Configure PPP callback client in the circular DCC implementation

As a callback client, a router can originate calls to the remote end (which can be a router or Windows NT server having the PPP callback server function), and receive the return calls from the remote end.

Use the local-user password command to configure the user name in system view, and perform the other configurations in dial interface (physical or dialer interface) view.

Page 726
Image 726
3Com 10014299 Configuring MP binding in resource-shared DCC, Configuring PPP callback in the circular DCC implementation