No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

HUAWEI CLOUD Stack 6.5.0 Alarm and Event Reference 04

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
ALM-104 Failed to Import the iptables Rules into a Node

ALM-104 Failed to Import the iptables Rules into a Node

Description

This alarm is reported when the iptables rules fail to be imported into a node.

Attribute

Alarm ID

Alarm Severity

Alarm Type

104

Major

Environment alarm

Parameters

Parameter Name

Parameter Description

kind

Resource type.

namespace

Name of the project to which the resource belongs.

name

Resource name.

OriginalEventTime

Event generation time.

EventSource

Name of the component that reports an event.

EventMessage

Supplementary information about an event.

Impact on the System

The container network of the node is inaccessible.

System Actions

The system keeps importing the iptables rules to the node.

Possible Causes

There is no soft link iptables-restore on the node.

Procedure

  1. Obtain the name and namespace of the node based on the location information in the alarm information.

    1. Use a browser to log in to the FusionStage OM zone console.
      1. Log in to ManageOne Maintenance Portal.
        • Login address: https://Address for accessing the homepage of ManageOne Maintenance Portal:31943, for example, https://oc.type.com:31943.
        • The default username is admin, and the default password is Huawei12#$.
      2. On the O&M Maps page, click the FusionStage link under Quick Links to go to the FusionStage OM zone console.
    2. Choose Application Operations > Application Operations > Alarm Center > Alarm List to view alarm details.
    3. Choose Location Info > name to obtain the name of the pod that fails to be created.
    4. Obtain the namespace (used in the following contents) where the application that fails to be created resides by viewing the value of namespace in the Location Info field in the alarm details area.

  2. Use PuTTY to log in to the manage_lb1_ip node.

    The default username is paas, and the default password is QAZ2wsx@123!.

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

    su - root

    Default password: QAZ2wsx@123!

  4. Run the following command to query the IP address of the node reporting the alarm:

    kubectl get no {nodename} -oyaml | grep addr

    {nodename} indicates the node name obtained in 1.

    If the following information is displayed, the IP address of the node reporting the alarm is 10.107.225.8.

      address: 10.107.225.8
      addresses:
      - address: 10.107.225.8
      - address: 10.107.225.8-67abfa09
      - address: 10.107.225.8
      - address: 10.107.225.8

  5. Use PuTTY to log in to the node obtained in Step 3 as the root user to check whether there is the soft link iptables-restore on the node. If security hardening has been performed on the node, log in to the node as the paas user and then switch to the root user.

    1. Run the following command to go to the sbin directory:

      cd /usr/sbin

    2. Run the following command to check whether there is the soft link iptables-restore on the node:

      ls -l |grep xtables-multi

      If the following information is displayed, there is the soft link iptables-restore on the node.
      lrwxrwxrwx. 1 root root      13 Feb 25 09:49 ip6tables -> xtables-multi
      lrwxrwxrwx. 1 root root      13 Feb 25 09:49 ip6tables-restore -> xtables-multi
      lrwxrwxrwx. 1 root root      13 Feb 25 09:49 ip6tables-save -> xtables-multi
      lrwxrwxrwx. 1 root root      13 Feb 25 09:49 iptables -> xtables-multi
      lrwxrwxrwx. 1 root root      13 Feb 25 09:49 iptables-restore -> xtables-multi
      lrwxrwxrwx. 1 root root      13 Feb 25 09:49 iptables-save -> xtables-multi
      -rwxr-xr-x. 1 root root   96768 Feb 12 08:00 xtables-multi
      • If there is the soft link iptables-restore on the node, go to 6.
      • If there is no soft link iptables-restore on the node, go to 5.c.
    3. Run the following command to add the soft link iptables-restore on the node:

      ln -s xtables-multi iptables-restore

  6. Check whether the alarm is cleared.

    • If the alarm is cleared, no further action is required.
    • If the alarm is not cleared, go to 7.

  7. Contact technical support for assistance.

Alarm Clearing

This alarm will be automatically cleared after the fault is rectified.

Related Information

None

Translation
Download
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 35901

Downloads: 31

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Share
Previous Next