Troubleshooting FiberHome AN5516: Configuration, Compatibility & Error Resolving

Troubleshooting FiberHome AN5516: Configuration, Compatibility & Error Resolving

Overview & Thematic Scope

Welcome to our technical support FAQ for network engineers managing the FiberHome AN5516 OLT series. This guide addresses critical troubleshooting scenarios, focusing on the factory reset process, configuration management, and post-reset recovery for chassis including the AN5516-01, AN5516-04, and AN5516-06. We provide expert answers for pre-sales and post-sales maintenance to help you ensure high availability of your FTTx network.

Troubleshooting FiberHome AN5516: Configuration, Compatibility & Error Resolving details

Frequently Asked Questions

Q1: How do I perform a complete factory reset on a FiberHome AN5516 OLT via CLI?
To factory reset a FiberHome AN5516 OLT, you must clear the startup configuration and reboot the system. The definitive process involves accessing enable mode and executing the reset operation via CLI, not the hardware button. Log in to the device, enter enable mode, and use the command to reset the startup configuration by writing an empty configuration to the startup file. Follow this with a system reboot. Be aware that resetting the main control board (HSWA) will interrupt all ONU services and clear all custom VLANs, ONU authorizations, and uplink port settings.
Q2: What are the risks of using the physical reset button on the EC8B or HSWA boards?
Using the physical reset key on FiberHome service boards like the EC8B or GC4B is strongly discouraged for routine maintenance due to immediate service interruption. The hardware reset button forces a hard reboot of the specific card, bypassing normal shutdown procedures. This can lead to data loss, corrupted configuration files, or a prolonged reboot cycle as the card re-initializes. Official documentation emphasizes that resets should only be conducted via software commands, not direct key presses.
Q3: What are the critical pre-configuration steps after a factory reset, specifically for card authorization?
After a factory reset, the AN5516 system will not recognize any installed service boards until they are explicitly authorized. The essential post-reset task is to re-authorize your service cards via CLI using the `set card_auth` command. You must configure the slot and card type (e.g., EC4B, GC4B, HU1A). For example, to authorize a GC4B board in slot 14, use: `set card_auth slot 14 type gc4b`. Failure to do this will result in the cards remaining in an ‘unauthorized’ state, preventing PON ports from coming online.
Q4: Does the AN5516 support dual control board redundancy to minimize downtime during resets?
Yes, the AN5516 series supports a High-Availability architecture with dual control boards (HSWA) to minimize Mean Time To Repair (MTTR). If you need to reset or upgrade the active control board, the standby board can take over to ensure uninterrupted service. When performing a factory reset or major firmware upgrade, ensure the standby board is active to prevent a full network outage, leveraging the platform’s design for 99.999% uptime.
Q5: How do I configure the uplink ports after a factory reset to restore network connectivity?
Re-configuring uplink ports is mandatory to restore traffic flow to the core network after a reset. You must set the speed, duplex, and auto-negotiation settings using the `set uplink port` command in the device context. For instance, to force a 1Gbps full-duplex connection on port 19:1, use: `set uplink port 19:1 auto_negotiation disable speed 1000m duplex full`. You also need to recreate the management VLAN and IP to re-establish communication with the UNM2000 NMS or AdminOLT.
Q6: What should I do if the ALM (Alarm) LED is red on my GC4B board after a reset?
A red ALM indicator on the GC4B board typically signifies that the card is resetting, has an active alarm, or has failed to establish a communication link with the active control board. This is common after a factory reset. If the red light persists after boot-up, it indicates the board has not been properly authorized or initialized. Check the card status using the `showcard` command and re-authorize the slot if necessary to resolve the alarm state.