Importing Device Aliases

If you do not use aliases (nicknames for port WWNs), or if you do not use them in a consistent and coherent manner, then you might want to create them or to modify them, and then import them into VirtualWisdom. Without aliases, you only see FCIDs in the VirtualWisdom UI. Useful alias names are recommended to getting the most benefit out of using the Entity Creation Utility.

Alias import is done using the fcport type in a JSON import file. You can only perform alias mapping on the port level entities HBA Port and Storage Port. You cannot map aliases to switch ports.

Tip: The examples that follow use a singleton array with JSONIMPORTED as the only entry. This is simply a best practice. Tags can be any valid string.

The port WWN displays with the assigned entity name rather than the WWN in all parts of the user interface.

Structure of an alias import file:

Note that description and tags are optional elements, and edit_type defaults to add, so they are not explicitly required.

The fcport type is only used for mapping aliases to existing port level entities (HBA Port and Storage Port).

{

"entities": [

{

"description": "description text",

"edit_type": "add",

"name": "name text",

"tags": ["JSONIMPORTED"],

"type": "fcport",

"wwn": "WWN hash"

}

],

"version": 2

}

Example of an alias import file:

{

"entities": [

{

"description": "248d00059b2b78c0,corp1server_hba1 from user.csv",

"name": "corp1server_hba1",//The name to be mapped to “wwn”:"248d00059b2b78c0"

"tags": [//Optional; help with search and identification

"JSONIMPORTED"

],

"type": "fcport",//”fcport” is only used for alias import

"wwn": "248d00059b2b78c0"//The WWN to be mapped to “name”:"corp1server_hba1"

},

{

"description": "5001438002b0dbb4,corp2server_hba1 from user.csv",

"name": "corp2server_hba1",//The name to be mapped to “wwn”:"5001438002b0dbb4"

"tags": [

"JSONIMPORTED"

],

"type": "fcport",

"wwn": "5001438002b0dbb4"

}

],

"version": 2//The JSON file format used

}

When importing aliases, consider the following:

  • You can only import aliases for the discovered, port-level entities HBA Port and Storage Port. Switch port aliases are not supported.

  • You can override discovered aliases by providing an alternative name for a Port WWN in an import file.

  • You can revert to a discovered name using an import where the name strings for a Port WWN is the empty string "".