Reason for unavailability of the secondary gateway

9

Question:
Question: When NEs A and B are forcibly switched to secondary GNE C, the NEs become unreachable, namely the secondary gateway is not available.
Analysis:
1. When the primary GNE is used, the NEs are reachable. This means that the system control boards and software are normal, as well as the communication parameters. 2. The maximum number of route hops is 20, which is smaller than the actual value, resulting in the failure in backup route search. 3. The maximum number of route hops should be set to the default value 64, and the issue will be resolved.
Root cause:
The maximum number of route hops was set to 20 for NEs A and B. The actual number of hops between NEs and the GNE is greater than 20, resulting in the failure in locating the backup route and communication.
Answer:
The maximum number of route hops should be set to the default value 64, and the issue will be resolved.
Suggestion and conclusion:
Common causes for unreachable NEs are: incorrect communication parameters (NEID, subnet mask, or ECC modes), constant reset of the system control boards resulting in communication failures, and excessively large scale of the automatically extended ECC resulting in network instability.

Other related questions:
Intra-band control channels unavailable
Question: What are the reasons for the intra-band control channels being unavailable? Root cause: None Answer: Answer: 1. The physical board is offline, and the board reports the BD_STATUS alarm. 2. The number of optical ports in the config_snd state is beyond the limit. 3. The AdminStatus of the control channel is set to AdminDown manually, meaning that the control channel is closed. 4. The peer end NE is not an ASON NE or the ASON function is not enabled. 5. No optical port is designated to the DCC. 6. Optical-port-level alarms on the fiber cause the AdminStatus state to be AdminDown. 7. Bit errors on the optical port make the ECC unavailable. 8. The NE Node ID configuration is incorrect. Suggestion and conclusion: None

Can the secondary analysis be performed on prefixes of the U1900 voice gateway?
The secondary analysis cannot be performed on prefixes. We can realize this by configuring number change for prefixes. Assume the following scenario: All intra-office numbers of the U1900 begin with 4. Intra-office numbers used for making intra-office calls must be sent to the peer end. Then the peer end sends the numbers to the U1900 which forwards the calls to corresponding intra-office extensions. Method: Set the outgoing prefix to 4 and associate it with the number change rule of adding prefix 111 to the called number. Set the intra-office prefix to 1114 and associate it with the called number change rule of deleting the first three digits.

Unavailability of the KVM
The browser or Java version does not meet requirements. For details about version requirements, see the iBMC user guide or iMana user guide of your server model.

Why ISDN phone is unavailable
The causes are as follows: - The ISDN phone has no power supply. ISDN phones can obtain power by themselves or through the remote PBX. By default, the 2BST (BRA) card does not provide power when the AR router is connected to an ISDN telephone. If power supply is required, run the remote-power enable command. system-view [Huawei] voice [Huawei-voice] port bra 3/0/0 [Huawei-voice-bra3/0/0] remote-power enable - The phone pin assignment is incorrect. The pin assignment of the ISDN phone differs from that of a common network cable. The ISDN crossover cable is often used to connect the AR router to the ISDN phone. If the ISDN phone obtains power supply and the pin assignment is correct but the fault persists, contact Huawei technical support personnel.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top