Got it

How to solve ALM-70251

Created: Feb 21, 2022 06:33:42Latest reply: Feb 21, 2022 06:51:59 275 4 0 0 0
  Rewarded HiCoins: 0 (problem resolved)

Hello, everyone!

Does anyone know what to do with ALM-70251?

Can you solve this annoying issue for me, please?

Product: HUAWEI CLOUD Stack

  • x
  • convention:

Featured Answers
olive.zhao
Admin Created Feb 21, 2022 06:51:59

Hello, friend!

1. Use PuTTY to log in to the FusionSphere OpenStack controller node through the IP address of the External OM plane.

The default user name is fsp. The default password is Huawei@CLOUD8.

2. Run the following command and enter the password of user root to switch to user root:

su - root

The default password of user root is Huawei@CLOUD8!.

3. Run the following command to disable user logout upon system timeout:

TMOUT=0

4. Run the following command to import environment variables:

source set_env

Information similar to the following is displayed:

source set_env

5. Enter to enable Keystone V3 authentication and enter the password of OS_USERNAME as prompted.

The default password is FusionSphere123.

6. Perform the required operation based on the alarm information.

  • If only one subordinate network port is available and it is not in the unknown state, go to step 7.

  • If more than one subordinate network port is available and one network port is in the unknown state, go to Step 8.

  • If more than one subordinate network port is available and one network port is in the unknown state, go to Step 12.

7. If a bond has only one subordinate network port, add subordinate network ports to the bond in either of the following ways:

  • If no service is running on the host, log in to the FusionSphere OpenStack web client, choose Configuration > Network > Configure NIC Mapping, and locate the host group to which the host belongs based on host_id in Fault Location Info. Delete the bond, select an available idle NIC network port, and create a bond again.

  • If services are running on the host, switch to PuTTY and run the following commands to update the subordinate network port of the bond:

    cps hostcfg-item-update --item bond --bond-name trunk_name --slaves nic_name_1,nic_name_2,... --type network group_name

    cps commit

    The value of trunk_name is obtained from the alarm information. The value of nic_name can be obtained by running the cat /usr/bin/ports_info |python -mjson.tool|grep eth command and the value of group_name can be obtained by running the cps hostcfg-list --type network command.

    For example, run the following commands:

    cps-hostcfg-item-update --item bond --bond-name trunk1 --slaves nic3,nic4 --type network group1

    cps commit

    If the commands are successfully executed, Wait for 5 minutes and check whether the alarm is cleared. 

8. Log in to the FusionSphere OpenStack web client, choose Configuration Network Configure NIC Mapping, and locate the host group to which the host belongs based on host_id in Fault Location Info. Switch to PuTTY and run the following command using the command-line interface (CLI) to check whether the option attribute of the subordinate network ports is AUTO_PXE.

cps hostcfg-show --type network host group

  • If the unknown subordinate port is of the AUTO_PXE type, go to Step 9.

  • If the unknown subordinate port is not of the AUTO_PXE type, go to Step 10.

9. Perform the required operation to replace the unknown subordinate network port with a planned physical network port on the host.

a. Switch to PuTTY and run the cat /usr/bin/ports_info |python -mjson.tool|grep eth command to check whether the eth port is registered as the NIC port.

  • If yes, the physical NIC has been registered with the network group to which the host belongs. In this case, go to 9.b.

  • If no, the physical NIC is not registered with the network group to which the host belongs. In this case, go to Step 11.

b. Run the following commands to deregister the physical NIC from the network group:

cps hostcfg-item-delete --item nic --nic-name nic_name --type network group_name

cps commit

The group_name value can be queried using the cps hostcfg-list --type network command, and the nic_name value can be queried using the cat /usr/bin/ports_info |python -mjson.tool|grep eth command.

For example, run the following commands:

cps hostcfg-item-delete --item nic --nic-name nic3 --type network group1

cps commit

After this step is complete, go to Step 11.

10. Replace the unknown subordinate network port in the bonded port as follows:

  • If no service is running on the host, log in to the FusionSphere OpenStack web client, choose Configuration > Network > Configure NIC Mapping, and locate the host group to which the host belongs based on host_id in Fault Location Info. Delete the bond and create a bond of the same name. In the new bond, replace the faulty network port with a normal one.

  • If services are running on the host, switch to PuTTY and run the following commands to update the subordinate network port of the bond:

    cps hostcfg-item-update --item bond --bond-name trunk_name --slaves nic1,nic2,... --type network group_name

    cps commit

    The value of trunk_name is obtained from the alarm information. The value of nic_name can be obtained by running the cat /usr/bin/ports_info |python -mjson.tool|grep eth command and the value of group_name can be obtained by running the cps hostcfg-list --type network command.

    For example, run the following commands:

    cps hostcfg-item-update --item bond --bond-name trunk1 --slaves nic3,nic4 --type network group1

    cps commit

    If the commands are successfully executed, wait for 5 minutes and check whether the alarm is cleared. 

11. Configure the switch to enable the planned physical NIC to communicate with the preboot execution environment (PXE) network port at layer 2.

After successful operation, wait for 5 minutes and check whether the alarm is cleared. 

12. View the additional information in the alarm.

  • If "status is down" is displayed, go to Step 13.

  • If "aggregator id mismatch" is displayed, go to Step 14.

13. Check abnormal and normal NICs in the additional information and rectify the fault one if any by referring to ALM-6021 Host Network Port Fault.

After successful operation, wait for 5 minutes and check whether the alarm is cleared.

14. Log in to the peer host or switch of the aggregation network port and check whether the trunk configuration is correct.

If the configuration is incorrect, correct the configuration and wait for 5 minutes and check whether the alarm is cleared.

Hope this helps!

View more
  • x
  • convention:

piaopiaoran
piaopiaoran Created Feb 21, 2022 07:39:43 (0) (0)
Thanks very much!  
All Answers
stephen.xu
stephen.xu Admin Created Feb 21, 2022 06:35:11

Hello, dear.

What is your product? and what is the version?
View more
  • x
  • convention:

piaopiaoran
piaopiaoran Created Feb 21, 2022 06:52:34 (0) (0)
Hello,
HUAWEI CLOUD Stack 8.0.2.  
olive.zhao
olive.zhao Admin Created Feb 21, 2022 06:51:59

Hello, friend!

1. Use PuTTY to log in to the FusionSphere OpenStack controller node through the IP address of the External OM plane.

The default user name is fsp. The default password is Huawei@CLOUD8.

2. Run the following command and enter the password of user root to switch to user root:

su - root

The default password of user root is Huawei@CLOUD8!.

3. Run the following command to disable user logout upon system timeout:

TMOUT=0

4. Run the following command to import environment variables:

source set_env

Information similar to the following is displayed:

source set_env

5. Enter to enable Keystone V3 authentication and enter the password of OS_USERNAME as prompted.

The default password is FusionSphere123.

6. Perform the required operation based on the alarm information.

  • If only one subordinate network port is available and it is not in the unknown state, go to step 7.

  • If more than one subordinate network port is available and one network port is in the unknown state, go to Step 8.

  • If more than one subordinate network port is available and one network port is in the unknown state, go to Step 12.

7. If a bond has only one subordinate network port, add subordinate network ports to the bond in either of the following ways:

  • If no service is running on the host, log in to the FusionSphere OpenStack web client, choose Configuration > Network > Configure NIC Mapping, and locate the host group to which the host belongs based on host_id in Fault Location Info. Delete the bond, select an available idle NIC network port, and create a bond again.

  • If services are running on the host, switch to PuTTY and run the following commands to update the subordinate network port of the bond:

    cps hostcfg-item-update --item bond --bond-name trunk_name --slaves nic_name_1,nic_name_2,... --type network group_name

    cps commit

    The value of trunk_name is obtained from the alarm information. The value of nic_name can be obtained by running the cat /usr/bin/ports_info |python -mjson.tool|grep eth command and the value of group_name can be obtained by running the cps hostcfg-list --type network command.

    For example, run the following commands:

    cps-hostcfg-item-update --item bond --bond-name trunk1 --slaves nic3,nic4 --type network group1

    cps commit

    If the commands are successfully executed, Wait for 5 minutes and check whether the alarm is cleared. 

8. Log in to the FusionSphere OpenStack web client, choose Configuration Network Configure NIC Mapping, and locate the host group to which the host belongs based on host_id in Fault Location Info. Switch to PuTTY and run the following command using the command-line interface (CLI) to check whether the option attribute of the subordinate network ports is AUTO_PXE.

cps hostcfg-show --type network host group

  • If the unknown subordinate port is of the AUTO_PXE type, go to Step 9.

  • If the unknown subordinate port is not of the AUTO_PXE type, go to Step 10.

9. Perform the required operation to replace the unknown subordinate network port with a planned physical network port on the host.

a. Switch to PuTTY and run the cat /usr/bin/ports_info |python -mjson.tool|grep eth command to check whether the eth port is registered as the NIC port.

  • If yes, the physical NIC has been registered with the network group to which the host belongs. In this case, go to 9.b.

  • If no, the physical NIC is not registered with the network group to which the host belongs. In this case, go to Step 11.

b. Run the following commands to deregister the physical NIC from the network group:

cps hostcfg-item-delete --item nic --nic-name nic_name --type network group_name

cps commit

The group_name value can be queried using the cps hostcfg-list --type network command, and the nic_name value can be queried using the cat /usr/bin/ports_info |python -mjson.tool|grep eth command.

For example, run the following commands:

cps hostcfg-item-delete --item nic --nic-name nic3 --type network group1

cps commit

After this step is complete, go to Step 11.

10. Replace the unknown subordinate network port in the bonded port as follows:

  • If no service is running on the host, log in to the FusionSphere OpenStack web client, choose Configuration > Network > Configure NIC Mapping, and locate the host group to which the host belongs based on host_id in Fault Location Info. Delete the bond and create a bond of the same name. In the new bond, replace the faulty network port with a normal one.

  • If services are running on the host, switch to PuTTY and run the following commands to update the subordinate network port of the bond:

    cps hostcfg-item-update --item bond --bond-name trunk_name --slaves nic1,nic2,... --type network group_name

    cps commit

    The value of trunk_name is obtained from the alarm information. The value of nic_name can be obtained by running the cat /usr/bin/ports_info |python -mjson.tool|grep eth command and the value of group_name can be obtained by running the cps hostcfg-list --type network command.

    For example, run the following commands:

    cps hostcfg-item-update --item bond --bond-name trunk1 --slaves nic3,nic4 --type network group1

    cps commit

    If the commands are successfully executed, wait for 5 minutes and check whether the alarm is cleared. 

11. Configure the switch to enable the planned physical NIC to communicate with the preboot execution environment (PXE) network port at layer 2.

After successful operation, wait for 5 minutes and check whether the alarm is cleared. 

12. View the additional information in the alarm.

  • If "status is down" is displayed, go to Step 13.

  • If "aggregator id mismatch" is displayed, go to Step 14.

13. Check abnormal and normal NICs in the additional information and rectify the fault one if any by referring to ALM-6021 Host Network Port Fault.

After successful operation, wait for 5 minutes and check whether the alarm is cleared.

14. Log in to the peer host or switch of the aggregation network port and check whether the trunk configuration is correct.

If the configuration is incorrect, correct the configuration and wait for 5 minutes and check whether the alarm is cleared.

Hope this helps!

View more
  • x
  • convention:

piaopiaoran
piaopiaoran Created Feb 21, 2022 07:39:43 (0) (0)
Thanks very much!  

Comment

You need to log in to comment to the post Login | Register
Comment

Notice: To protect the legitimate rights and interests of you, the community, and third parties, do not release content that may bring legal risks to all parties, including but are not limited to the following:
  • Politically sensitive content
  • Content concerning pornography, gambling, and drug abuse
  • Content that may disclose or infringe upon others ' commercial secrets, intellectual properties, including trade marks, copyrights, and patents, and personal privacy
Do not share your account and password with others. All operations performed using your account will be regarded as your own actions and all consequences arising therefrom will be borne by you. For details, see " User Agreement."

My Followers

Login and enjoy all the member benefits

Login

Block
Are you sure to block this user?
Users on your blacklist cannot comment on your post,cannot mention you, cannot send you private messages.
Reminder
Please bind your phone number to obtain invitation bonus.
Information Protection Guide
Thanks for using Huawei Enterprise Support Community! We will help you learn how we collect, use, store and share your personal information and the rights you have in accordance with Privacy Policy and User Agreement.