When the check-lease-limit-with-sae option is set to true, you must configure the NIC proxy so that the pseudo-RADIUS authorization server can find the SAE managing the interface and determine the number of subscriber sessions already established on the interface (that is, the number of leases on the interface). The NIC proxy must be configured for a NIC scenario that maps VRs to SAEs.
Tasks to configure the NIC proxy are:
Use the following configuration statements to configure the NIC proxy:
- slot number external-subscriber-monitor
nic-proxy-configuration radius-authorization-nic resolution {
- resolver-name resolver-name;
- constraints constraints;
- }
To configure resolution information for a NIC proxy:
- [edit slot 0 external-subscriber-monitor nic-proxy-configuration
radius-authorization-nic resolution]
- user@host# set ?
For more information about configuring resolution information for a NIC proxy, see Configuring Resolution Information for a NIC Proxy (SRC CLI).
You can modify cache properties for the NIC proxy to optimize the resolution performance for your network configuration and system resources. Typically, you can use the default settings for the cache properties. The configuration statements are available at the Advanced editing level.
Use the following configuration statements to change values for the NIC proxy cache:
- slot number external-subscriber-monitor
nic-proxy-configuration radius-authorization-nic cache {
- cache-size cache-size;
- cache-cleanup-interval cache-cleanup-interval;
- cache-entry-age cache-entry-age;
- }
To configure the cache for a NIC proxy:
- [edit slot 0 external-subscriber-monitor nic-proxy-configuration
radius-authorization-nic cache]
- user@host# set ?
For more information about configuring the cache for a NIC proxy, see Changing the Configuration for the NIC Proxy Cache (SRC CLI).
[edit slot 0 external-subscriber-monitor nic-proxy-configuration radius-authorization-nic cache] user@host# show cache-size 10000; cache-cleanup-interval 15;
Typically, you configure NIC replication to keep the NIC highly available. You configure NIC host selection to specify the groups of NIC hosts to be contacted to resolve a request, and to define how the NIC proxy handles NIC hosts that the proxy is unable to contact. The configuration statements are available at the Advanced editing level.
Use the following configuration statements to configure NIC host selection for a NIC proxy:
- slot number external-subscriber-monitor
nic-proxy-configuration radius-authorization-nic nic-host-selection
{
- groups groups;
- selection-criteria (roundRobin | randomPick | priorityList);
- }
- slot number external-subscriber-monitor
nic-proxy-configuration radius-authorization-nic nic-host-selection
blacklisting {
- try-next-system-on-error;
- number-of-retries-before-blacklisting number-of-retries-before-blacklisting;
- blacklist-retry-interval blacklist-retry-interval;
- }
To configure a NIC proxy to use NIC replication:
- [edit slot 0 external-subscriber-monitor nic-proxy-configuration
radius-authorization-nic nic-host-selection]
- user@host# set ?
For more information about configuring NIC host selection for a NIC proxy, see Configuring a NIC Proxy for NIC Replication (SRC CLI).
[edit slot 0 external-subscriber-monitor nic-proxy-configuration radius-authorization-nic nic-host-selection] user@host# show groups ; selection-criteria roundRobin;
- [edit slot 0 external-subscriber-monitor nic-proxy-configuration
radius-authorization-nic nic-host-selection blacklisting]
- user@host# set ?
For more information about configuring NIC host selection for a NIC proxy, see Configuring a NIC Proxy for NIC Replication (SRC CLI).
[edit slot 0 external-subscriber-monitor nic-proxy-configuration
radius-authorization-nic nic-host-selection blacklisting]user@host# show[edit slot 0 external-subscriber-monitor nic-proxy-configuration radius-authorization-nic nic-host-selection blacklisting] user@host# show try-next-system-on-error; number-of-retries-before-blacklisting 3; blacklist-retry-interval 15;