CoA request for the subscriber aggregate-rate-limit change is honored on the LAC and the LNS.
CoA for the rate change of an individual link within the bundle is supported through the same VSA that can be used to initially assign the rate parameter to each member link. This is supported only on LNS. The rate override via CoA is applied to all active link members within the bundle.
Change of the access link parameters via CoA is be supported in the following fashion:
Change of access loop encap: refused (NAK)
Change of access loop rate down:
On L2TP LAC session: refused (NAK). On LAC the access loop rate down is not locally used for any rate limiting function but instead it is just passed to the LNS at the beginning when the session is first established. Mid-session changes on LAC via CoA are not propagated to the LNS.
On L2TP LNS session:
Plain session: ignored. The rate is stored in the MIB table but no rate limiting action is taken. In other words, this parameter is internally excluded from rate calculations and advertisements. However, it is shown in the output of the relevant show commands.
Bundle session: applied on all link sessions. The aggregate rate limit of the bundle is set to the minimum of the:
CoA obtained local loop down rate multiplied by the number of links in the bundle
The aggregate rate limit configured statically or obtained via CoA.
Fragment length is affected by this change. In case that interleaving is enabled on a single link bundle, the interleave interval is affected.
Non-L2TP: ignored. The rate is stored in the MIB table but no rate limiting action is taken. In other words, this parameter is internally excluded from rate calculations and advertisements. However, it is shown in the output of the relevant show commands.
Similar behavior is exhibited if at mid-session, the parameters are changed via LUDB with the exception of the rate-down parameter in LAC. If this parameter is changed on the LAC, all sessions are disconnected.