"Fossies" - the Fresh Open Source Software Archive

Member "opensaf-5.21.09/00-README.debug" (31 May 2021, 5667 Bytes) of package /linux/misc/opensaf-5.21.09.tar.gz:


As a special service "Fossies" has tried to format the requested text file into HTML format (style: standard) with prefixed line numbers. Alternatively you can here view or download the uninterpreted source code file.

    1 Troubleshooting OpenSAF
    2 ======================
    3 
    4 System Controller Checklist
    5 ===========================
    6 
    7 1.  If TIPC is chosen as the mds transport , did TIPC installation fail?
    8     The following error "FATAL: Error inserting
    9     tipc (<kernel_modules_dir>/tipc.ko): Invalid module format" indicates that 
   10     user had not compiled TIPC with proper kernel files. Compile TIPC with 
   11     appropriate kernel header files (e.g. They are different for an smp kernel 
   12     type, etc.)
   13 
   14 2.  If TIPC is chosen as the mds transport , have you checked the TIPC configuration?
   15     The following TIPC configuration parameters should be set appropriately in nodeinit.conf:
   16  
   17      a. TIPC network_id should be the same as ACTIVE system controller's 
   18         network_id.
   19      b. The interface information is set with default values. This has 
   20         to be set correctly to ensure connectivity between the system 
   21         controller and payload nodes.
   22         Also, the TIPC zone_id and cluster_id values are currently hard-coded.
   23         These have to be checked for correctness as below if zone_id and 
   24         cluster_id are changed:
   25      c. zone_id should be the same as ACTIVE system controller's zone_id.
   26      d. cluster_id should be the same as ACTIVE system controller's cluster_id.
   27 
   28 3.  If TCP is chosen as the mds transport with IPv6, have you checked the system configuration?
   29  
   30      a. The kernel should be ipv6 compiled.
   31       The following commands should succeed : 
   32       - ls /proc/net/if_inet6
   33       - modprobe ipv6
   34       - lsmod |grep -w 'ipv6' && echo "IPv6 module successfully loaded"
   35      b. For communication between ipv6 m/c's, firewall should be disabled.
   36      c. If there is any router in between the m/c's, the router should be ipv6 enabled.
   37      d. kernel should assign ipv6 link-local ip address automatically for the interface available.
   38 
   39 4.  If TCP is  chosen as the mds transport , have you checked the TCP configuration?
   40     The following TCP configuration  parameters should be set appropriately in dtmd.conf:
   41  
   42      a. DTM_NODE_IP should be configured same as system IP address.
   43 
   44 5.  Have you checked the slot_id?
   45     The slot_id should be unique and different from any other node. The system 
   46     controllers.
   47 
   48 6.  Have you checked the open source packages installation?
   49     Ensure that the following open source packages are installed
   50     (make install or the rpm packages are installed):
   51 
   52     The configure process should have detected the presence or absence of
   53     those packages at runtime.
   54 
   55     a. The libxml2 libraries are available and libxml2 include files are 
   56        available. In cases of rpm installation, make sure the devel package 
   57        is installed.
   58 
   59 7.  Have you checked the chassis_id? The chassis_id should be the same as 
   60     ACTIVE system controller.
   61 
   62 8.  Have you checked the node_name. It should contain the same name as the
   63     value specified in the nodes.cfg file while generating the imm.xml.
   64     "Unconfigured CLM nodes are not allowed to join the cluster if the node_names
   65      dont match and CLMNA will not allowed to be initialized".
   66 
   67 NOTE: Also check for /var/log/messages for any errors during the startup.
   68 
   69 Payload Node Checklist
   70 ======================
   71 
   72 1.  If TIPC is chosen as the mds transport ,did TIPC installation fail? The following error "FATAL: Error inserting 
   73     tipc (<kernel_modules_dir>/tipc.ko): Invalid module format" indicates that 
   74     user had not compiled TIPC with proper kernel files. Compile TIPC with 
   75     appropriate kernel header files (e.g. They are different for an smp kernel 
   76     type, etc.)
   77 
   78 2.  If TIPC is chosen as the mds transport , have you checked the TIPC configuration?
   79     The following TIPC configuration parameters should be set appropriately 
   80     in nodeinit.conf.payload:
   81 
   82     a. TIPC Network id should be the same as system controllers's network ID.
   83     b. The interface information is set with default values. This has to be 
   84        set correctly to ensure connectivity between the payload and system 
   85        controller nodes.
   86        Also, the TIPC zone_id and cluster_id values are currently hardcoded. 
   87        These have to be checked for correctness as below if zone_id and 
   88        cluster_id are changed:
   89     c. zone_id should be the same as the system controllers's zone_id.
   90     d. cluster_id should be the same as the system controllers's cluster_id.
   91 
   92 3.  If TCP is chosen as the mds transport with IPv6, have you checked the system configuration?
   93  
   94      a. The kernel should be ipv6 compiled.
   95       The following commands should succeed :
   96       - ls /proc/net/if_inet6
   97       - modprobe ipv6
   98       - lsmod |grep -w 'ipv6' && echo "IPv6 module successfully loaded"
   99      b. For communication between ipv6 m/c's, firewall should be disabled.
  100      c. If there is any router in between the m/c's, the router should be ipv6 enabled.
  101      d. kernel should assign ipv6 link-local ip address automatically for the interface available.
  102 
  103 4.  If TCP is chosen as the mds transport , have you checked the TCP configuration?
  104     The following TCP configuration  parameters should be set appropriately in dtmd.conf:
  105  
  106      a. DTM_NODE_IP should be configured same as system IP address.
  107 
  108 5.  Have you checked the chassis_id? The chassis_id should be the same as 
  109     ACTIVE & STANDBY system controllers.
  110 
  111 6.  Have you checked the node_name. It should contain the same name as the
  112     value specified in the nodes.cfg file while generating the imm.xml.
  113     "Unconfigured CLM nodes are not allowed to join the cluster if the node_names
  114      dont match and CLMNA will not allowed to be initialized".
  115 
  116 
  117 NOTE: Also check for /var/log/messages for any errors during the startup.
  118