Problem and solution when the USG6000 virtual system cannot be configured

63

Check the permission of the administrator account used for login.
If you use the root system administrator account to configure the virtual system, the level of the root system administrator shall be the system administrator. If you use the virtual system administrator account to configure the virtual system, the level of the virtual system administrator shall be the system administrator or the configuration administrator with the read and write permissions.
Choose System > Admin > Administrator Role and configure the administrator account.

Other related questions:
Problem and solution when an error is reported during NAT IP address configuration on a virtual system
Only public IP addresses assigned to the virtual system can be used as the public IP addresses for NAT, NAT server, and interfaces.

Problem and solution when the firewall cannot ping the virtual IP address of the VRRP group
Possible causes are as follows: A VRID conflict occurs. The virtual IP address ping function is disabled. According to RFC3768, the ping command cannot be used to detect the virtual IP address connectivity. Huawei provides the virtual IP address ping function for the convenience of monitoring. This function is enabled by default. If it is disabled, you can run the vrrp virtual-ip ping enable command to enable it.

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.

Problem and solution when a host of an OceanStor V3 storage system cannot deliver services
Cause: The disk enclosure that encounters a power failure is a sub-group of RAID 10. Data can also be written into other sub-groups. However, if a disk enclosure encounters a power failure, the metadata logs of more than three disks are recorded. Currently, the RAID 1 group has only four disks. Therefore, the logs of a maximum of four disks are recorded. If the logs of extra three logs must be recorded, the logs fail to be recorded and an I/O failure is returned to the host. Solution: Power on the disk enclosure to solve the problem.

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