[Contents]
[Prev]
[Next]
[Index]
[Report an Error]
Modifying Congestion Points
By default, SRC-ACP does not register changes in
congestion points until you stop and restart SRC-ACP. To modify the
congestion point associated with a service without stopping and starting
SRC-ACP:
- Make sure that no subscribers have subscriptions to services
that use the congestion point you want to modify.
- From configuration mode, access the configuration statement
that configures SRC-ACP connections to the services’ directory.
- user@host# edit shared acp configuration ldap
service-data
- Specify whether SRC-ACP detects changes in the backbone
congestion point for a service while SRC-ACP is operative.
- [edit shared acp configuration ldap service-data]
- user@host# set reload-congestion-points
- Wait for 30 seconds before you proceed to the next step.
Depending on the value of the polling interval
for directory eventing, SRC-ACP may take up to 30 seconds to register
the change to the reload-congestion-points option. If you
modify the congestion point before SRC-ACP registers the new setting
for the reload-congestion-points option, SRC-ACP will not
register the change for the congestion point.
- Modify the congestion point in the service definition.
SRC-ACP immediately registers the change.
- From configuration mode, access the configuration statement
that configures SRC-ACP connections to the services’ directory.
- user@host# edit shared acp configuration ldap
service-data
- Specify whether SRC-ACP detects changes in the backbone
congestion point for a service while SRC-ACP is operative.
- [edit shared acp configuration ldap service-data]
- user@host# set reload-congestion-points
[Contents]
[Prev]
[Next]
[Index]
[Report an Error]
