How to Resolve The Problem Where Failed to configure the in-band environment and some functions are unavailable Is Displayed During The Deployment Start Phase

13

The causes are as follow.

Cause 1: The optical fibers between the clustered NAS engine and the controller enclosure of the storage unit may be loosely connected or not connected.
Connect optical fibers correctly. Then, start deployment again.

Cause 2: The management IP address assigned to the N8500 and that assigned to the controller enclosure of the storage unit do not belong to the same network segment.
Assign IP addresses that reside in the same network segment to the N8500 and the controller enclosure of the storage unit as management IP addresses. Then, start deployment again.

Other related questions:
How to Resolve The Problem Where Executing the command has timed out Is Displayed During The Deployment Start Phase
Restart all clustered nodes of the N8500. Then, start deployment again.

Problem and solution when a firewall cannot be added to the NMS
To solve the problem that a firewall cannot be added to the NMS (NMS workstation), perform the following steps: 1. Check whether the SNMP settings on the firewall are correct. For example, check whether the SNMP version matches the NMS. 2. Check whether the NMS is reachable to the firewall. 3. Check whether access management in SNMP mode is enabled on the interface connecting the firewall to the NMS. That is, you need to run the service-manage snmp enable command on the interface to allow the peer device to access the firewall in SNMP mode. By default, the SNMP permission of the interface is disabled. In this case, even if the security policy for the interzone between the zone where the interface resides and the Local zone is enabled, you cannot access the device through the interface. This is because that the service-manage function has a higher priority than the security policy. For details, see USG6350 can't add to the NMS server.

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

Problem and solution when the URL category query server fails to be connected
To locate and rectify the fault that the URL category query server fails to be connected, perform the following steps: 1. Check whether there is a URL remote query license. Check whether the URL remote query license is enabled and valid on the CLI or web UI. 2.Check whether the networking and the configuration is correct. a.Run the display url-filter global-configuration command to check whether the server state is Connected. If the state is another value, the server is not connected. b. Check whether the DNS server is correctly configured and test the connectivity between the device and the website sec.huawei.com. This website is Huawei security upgrade and authentication center. To connect to a URL remote query server, the device must pass authentication on this website. If the device cannot access the website, it cannot connect to the URL remote query server. c. Check the URL filtering profile.Run the display url-filter global-configuration command to check whether a country name is configured. If no country name is configured for the firewall, it cannot connect to the URL remote query server. d. Check related configurations on the device.View IPsec and tunnel configurations and check whether connection request packets enter IPsec tunnels. If so, analyze the networking and configuration and ensure that the packets can be correctly sent to the authentication center, scheduling server, and query server. e. View security policies and check whether security policies have blocked connection request packets.Several special IP addresses and port numbers are involved for URL server connections. Ensure that the packets sent to the URL servers can pass the check of security policies. f. Check whether the update host source command is configured.This command has an influence on the source address used to connect to the URL remote query server. If this command is configured, the specified interface address serves as the source address of query packets sent to the URL remote query server.If this command is configured, ensure that the packets in response to the packets sent from the specified address to the URL server can be properly forwarded to the device.

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