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


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

Knowledge Base

Collision of storage initiator alias cause the simplified configuration to create the MN failed

Publication Date:  2012-10-23  |   Views:  219  |   Downloads:  0  |   Document ID:  EKB1000017983


Issue Description

A storage device LUN at a certain test site is distributed to multiple sets of environment, currently the simplified configuration is built, implement the process to the stage of creating the virtual MN node according to the GPI. Execute the operation on MCNA:sh/startCNA/ After the installation go along for about ten minutes, we get the note: Failed: initialize ipsan failed.
Storage device: S3900
Cloud computing version: R2C00SPC200

Alarm Information


Handling Process

1. Ping the 8 storage link ips on the MCNA01, they all can ping through.
2. Run the operation “iscsiadm-m session” on the MCNA01, we examine that the entire storage link are normal.
iscsiadm -m session
tcp: [15],1
tcp: [16],2
tcp: [17],11
tcp: [18],12
3. Collect the VBS logs when the MN node being created: /opt/config/logtmp/bsb.log, we find that the initiator name MCNA01 has been occupied by the script to add the alias of initiator on the IPSAN.
admin:/>addhostport -host 0 -type 5 -info
CNA01 -n MCNA01
Error: The name is identical to an existing one.
Are you sure to exit?(y/n):
Connection to closed.
Jul 03 11:37:51 MCNA01 addhostport -host 0 -type 5 -info -n MCNA01 run successfully
Jul 03 11:37:51 MCNA01 Addport failed: Error: The name is identical to an existing one.
4. Log in the storage to view the initiator’s configuration, we find the alias “MCNA01” is existed in the storage device initiator, which is a duplication of the currently built MCNA.

5. Modify the node information table of MNConfigurationTool, change the name “MCNA01”, such as to add a character “Q” at the back. We still find that there is another alias “CNA01” in the storage device initiator configuration, for the sake of standard and security, we add a character “Q” to the back of the entire node. 

6. According to the GPI, modify the computer name of MCNA01 to MCNA01Q. Execute: sh /startCNA/scripts/gms/ MN master, clear out the configuration, re-lead in the new data, and execute: sh /startCNA/, the MN is created successfully.

Root Cause

1. The link IP between MCNA and storage isn’t ping through.
2. MCNA doesn’t find out the storage LUN.
3. There is collision about the storage configuration. When the MCNA and CNA node are to load, the initiator is added on the storage device automatically by script, the alias of the initiator is the name of the MCNA and CNA node.


When the simplified configuration of R2C00SPC200 is encountering to create the MN node Failed, if the notified false information related with IPSAN, we can analyze and locate the problem via: /opt/config/logtmp/bsb.log. If a storage is relevant with multiple sets of environment, pay attention that the alias of storage initiator is one and only to the device, make sure not be conflicting.