Known issues
6100年的开关inAOS-CX10.09.1040
The following are known open issues with this branch of the software. TheSymptomstatement describes what a user might experience if this is seen on the network. TheScenariostatement provides additional environment details and trigger summaries. When available, theWorkaroundstatement provides a workaround to the issue.
Category |
Bug ID |
Description |
RADIUS Port-Access |
227493 |
Symptom: In a Inter VRF route leak(IVRL) setup, port-access authentication fails with server timeout error. Even thought the server is reachable and the tracking indicates the server as reachable. This happens from 10.08 onwards. Scenario: In an IVRL setup, when the radius-server configuration VRF is not the same VRF as that of the actual server is placed, then the client authentication fails with server timeout error. This can happen in cases where a customer is running a software version 10.08 or higher. This can happen in upgrade or normal config instances as well. For example in this config: radius-server host 10.1.1.20 key ciphertext AQBapYuQcBB2A0RVgSPc/7H5lfSBrt8rwbNhTouCxje E4L8SCQAAAGZ3ykq9PEswPA== tracking enable vrf ADMIN radius-server host 10.1.1.21 key ciphertext AQBapYuQcBB2A0RVgSPc/7H5lfSBrt8rwbNhTouCxje E4L8SCQAAAGZ3ykq9PEswPA== tracking enable vrf ADMIN interface 1/3/47 no shutdown routing vrf attach USER ip address 10.10.100.1/30 ip route 10.1.1.0/24 10.10.100.2 vrf USER The radius-server configuration is inVRF ADMINand the IP is reachable onVRF USER. With such configuration the port-access client authentication fails with a server timeout error. Workaround: Have the radius-server configuration in the same VRF as e the server is connected. In the mentioned example the radius-server configuration should be inVRF USER. Another workaround is to leak the connected route to the radius-server configured VRF, in this case VRF ADMINip route 10.10.100.0/30 1/1/1 vrf ADMIN. |
Boot Process |
216818 |
Symptom: The output of theshow boot-historycommand displays an incorrect uptime. Scenario: This issue can occur in a deployment with NTP and Aruba Central enabled, if the switch fails to connect with Aruba Central and continues to retry. Workaround: The customer can disable Aruba Central using the following CLI command. switch (config)# aruba-central switch (config-aruba-central)# disable |
CLI Infra |
211466 |
Symptom: The user session does not timeout. Scenario: When the switch console is left idle, with a CLI command output in progress, waiting for user input to display the next page, the user session does not timeout when the configured timer expires. |
Port Access |
156628 |
Symptom:Theport-accessdaemon crashes. Scenario:When port security is enabled on a port where theport-security client-limitis configured with a value lower than the number of the port-security static clients configured on the port, after a downgrade from 10.07 to 10.05 or 10.06 theport-accessdaemon crashes. 处理:Prior to the downgrade, set the port-security limit configuration to a value equal to or higher than the number of static port-security clients configured on the port. |
