### JunosE 12.2.0 Release Notes

> ### Errata

> This section identifies errors found in the JunosE documentation. These errors are corrected in subsequent releases of the affected documentation.

> - The following additional information regarding the processing of tunneled subscriber sessions on Agent Circuit Identifier-based (ACI) VLAN subinterfaces with ICR partitions configured applies to the following guides in the JunosE documentation set:
> - JunosE Service Availability Configuration Guide—Grouping ICR Subscribers Based on S-VLAN IDs section in Chapter 7, Managing Interchassis Redundancy
> - JunosE Broadband Access Configuration Guide—Monitoring Subscriber Information section in Chapter 3, Monitoring and Troubleshooting Remote Access

> If you attempt to bring up tunneled subscribers on ACI-based VLAN subinterfaces on LAC devices with subscriber groups that are based on S-VLAN IDs (using the ip vrrp vrid icr-partition group svlan command on S-VLAN subinterfaces), the VLAN subinterface does not come up and a log message to denote its down state is not generated. If you attempt to bring up tunneled subscribers on ACI-based VLAN subinterfaces on LAC devices with subscriber groups that are based on VLAN IDs (using the ip vrrp vrid icr-partition group vlan command on VLAN subinterfaces), the subscribers over tunnels are brought up. However, on the LAC device, the subscribers are logged in outside of the ICR partition.

> This behavior is expected when attempts are made to log in tunneled subscribers over ACI-based VLAN subinterfaces configured with ICR partitions with VLAN-based grouping or S-VLAN based grouping.

> - The [26-1] Virtual-Router section in JunosE Broadband Access Configuration Guide, Chapter 4, Configuring RADIUS Attributes fails to state the following additional information regarding the usage of the IPv4 virtual router context configured in the AAA domain map and the RADIUS server on an authentication virtual router:

> If you configure the default virtual router as the authentication virtual router for the domain map using the ip-router-name command in Domain Map Configuration Mode and the Virtual-Router RADIUS VSA attribute [26-1] is returned from the RADIUS server in the Access-Accept message, the IPv4 virtual router context returned from the RADIUS server overrides the IPv4 virtual router context configured in the AAA domain map. If you configure a nondefault virtual router as the authentication virtual router for the AAA domain map and the Virtual-Router RADIUS VSA attribute [26-1] is returned from the RADIUS server in the Access-Accept message, the IPv4 virtual router context in the AAA domain map takes precedence over the IPv4 virtual router context returned from the RADIUS server.

> - The [26-45] Ipv6-Virtual-Router section in JunosE Broadband Access Configuration Guide, Chapter 4, Configuring RADIUS Attributes fails to state the following additional information regarding the usage of the IPv6 virtual router context configured in the AAA domain map and the RADIUS server on an authentication virtual router:

> If you configure the default virtual router as the authentication virtual router for the domain map using the ipv6-router-name command in Domain Map Configuration Mode and the IPv6-Virtual-Router RADIUS VSA attribute [26-45] is returned from the RADIUS server in the Access-Accept message, the IPv6 virtual router context returned from the RADIUS server overrides the IPv6 virtual router context configured in the AAA domain map. If you configure a nondefault virtual router as the authentication virtual router for the AAA domain map and the IPv6-Virtual-Router RADIUS VSA attribute [26-45] is returned from the RADIUS server in the Access-Accept message, the IPv6 virtual router context in the AAA domain map takes precedence over the IPv6 virtual router context returned from the RADIUS server.

Copyright © 2011, Juniper Networks, Inc. Report An Error