Known issues
for 8400 SwitchesinAOS-CX10.10.0002
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 |
Multicast |
227159 |
Symptom: The switch may unexpectedly reboot when configuring more than 128 LAG interfaces. Scenario: When configuring more than 128 LAG interfaces in a multicast topology, if a line card (LC) is rebooted or interfaces are toggled using theshutdown/no shutdowncommands, the switch will unexpectedly reboot and a coredump file is generated for theswitchddaemon. Workaround: Reduce the number of LAG interfaces to fewer than 128. |
BGP |
226220 |
Symptom: A mismatch between uptime shown byshow bgpcommands and the BGP state is reflected in the event log. Scenario: This issue occurs if no BGP show commands were run for 49 days Workaround: Run any BGP show command once every 48 days or fewer. |
L3 Routes |
189422 |
Symptom: A BGP default route is flapping between iBGP and eBGP. Scenario: A default route is learned from eBGP and iBGP both. and eBGP default route is selected as best route in FIB. Once the uplink connecting to eBPG peer is down, the default route starts flapping between iBGP and eBGP. Workaround: Configure BGP fast-external fallover for eBGP. |
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. Workaround: The session idle timeout counts when CLI command is completed and the switch is idle at the switch prompt. |
