 |
Note: You must define the interface in the directory before you can assign it to a residential subscriber (see Configuring Network Interfaces in the Directory for the Edge Network). |
The tasks to configure SRC-ACP to manage the edge network are:
You must add network interfaces to the directory. For the edge network, you do so by specifying the network interfaces of the routers and the switches in the access network between subscribers and the SRC network.
Use the following configuration statements to configure a network interface:
- shared admission-control device name {
- description description;
- }
- shared admission-control device name interface name {
- description description;
- upstream-provisioned-rate upstream-provisioned-rate;
- downstream-provisioned-rate downstream-provisioned-rate;
- upstream-background-bandwidth upstream-background-bandwidth;
- downstream-background-bandwidth downstream-background-bandwidth;
- detect-link-rate;
- }
To configure the network interfaces of the routers and the switches in the access network:
Enter the name of the network device.
Enter the name of the virtual router.
- [edit shared admission-control device name interface name]
- user@host# set upstream-background-bandwidth upstream-background-bandwidth
- user@host# set downstream-background-bandwidth downstream-background-bandwidth
For information about background bandwidths, see Allocating Bandwidth to Applications Not Controlled by SRC-ACP.
If you set this option, specify portId as an index key when configuring SRC-ACP operations so that updated sync rates are provided from interface tracking events. If the sync rate is not available, then the provisioned bandwidth configured in the subscriber profile is used.
[edit shared admission-control device name interface name] user@host# show
You must configure bandwidths for subscribers that SRC-ACP manages in the edge region of the network.
If the access network between the subscriber and the router uses ATM, and all the traffic coming from one DSLAM travels on a single virtual path, you do not need to provision bandwidths for each subscriber. In this case, SRC-ACP can derive the congestion points from the router (see Deriving Congestion Points Automatically).
However, if the access network uses a protocol other than ATM, you must provide the following information for each subscriber.
To configure bandwidths for subscribers:
- user@host# edit subscribers retailer name subscriber-folder folder-name subscriber name admission-control
For more information about configuring residential subscribers, see Adding Residential Subscribers (SRC CLI).
You must assign to the subscriber object interfaces (including the router interfaces) for all congestion points between the subscriber and the router.
|
Note: You must define the interface in the directory before you can assign it to a residential subscriber (see Configuring Network Interfaces in the Directory for the Edge Network). |
To assign an interface:
- user@host# edit subscribers retailer name subscriber-folder folder-name subscriber name admission-control
For more information about configuring residential subscribers, see Adding Residential Subscribers (SRC CLI).
Upstream and downstream bandwidths must be specified for services that SRC-ACP manages. You can obtain bandwidths for services in two ways:
For example, a business partner may need to specify the required values for a particular piece of content through the SAE core API.
To configure values for services:
For more information about configuring services, see Overview of Services for the SRC Software.
 | Copyright © 2008, Juniper Networks, Inc. All Rights Reserved. Trademark Notice. | |