About the CSV object files in Veritas Operations Manager Enterprise Server 5.0

Article:HOWTO77584  |  Created: 2012-08-10  |  Updated: 2012-09-05  |  Article URL http://www.symantec.com/docs/HOWTO77584
Article Type
How To

Product(s)

Environment

Subject


About the CSV object files in Veritas Operations Manager Enterprise Server 5.0

You must know about the Veritas Operations Manager Enterprise Server CSV object files if you update business views using the command line interface.

Each .csv file represents one of the object types that are defined in the .view file for this business view. These files, collectively, are called the business view assignment CSV files.

Each file should have the same base name as the name of the .view file. Business view .csv files use the following naming convention. All files that make up an individual view must use the same prefix. While the business view definition file has a '.view' extension, the CSV files have the extensions that map directly to their associated object type. For example, a "foo_Host.csv" extension defines the business view assignment for hosts.

If you used "GEOGRAPHY" as a base name, the .view and CSV files would be named as follows:

  • GEOGRAPHY.view

  • GEOGRAPHY_Array.csv

  • GEOGRAPHY_Cluster.csv

  • GEOGRAPHY_Filesystem.csv

  • GEOGRAPHY_Host.csv

  • GEOGRAPHY_NAS_Filesystem.csv

  • GEOGRAPHY_NAS_Share.csv

  • GEOGRAPHY_Servicegroup.csv

  • GEOGRAPHY_Volume.csv

Each object type has a set of columns that uniquely identify the object. These columns are required in each object .csv assignment file. They are in addition to the required hierarchy level columns that are defined in the .view file. Records that do not have the required number of columns are rejected.

Each object type requires the following columns.

Table: Object types and their required columns

Object type

Required object identifier columns

Array

Define one or more of the following:

  • Name: The name of the array

  • IP: The SNMP IP address for the array. If the array has multiple IPs, you can specify the IPs by enclosing this column in double quotes and separating addresses with a comma. For example, "127.0.0.1,192.168.1.1".

  • unique_id

Filesystem

Either define both the host and file system name, or specify the unique ID, as follows:

  • Host name: The name of the host to which the file system belongs

  • File system name: The name of the file system

  • object_unique_id: A unique identifier that Veritas Operations Manager generates

Host

Define one or more of the following:

  • Name: The name of the host

  • IP: The IP address for the host. If the host has multiple IPs, you can specify the IPs by enclosing this column in double quotes and separating addresses with a comma. For example, "127.0.0.1,192.168.1.1".

  • object_unique_id: A unique identifier that Veritas Operations Manager generates

Volume

Either define both the host and volume name, or specify the unique ID, as follows:

  • Host name: The name of host to which the file system belongs

  • Volume name: The name of the volume

  • object_unique_id: A unique identifier that Veritas Operations Manager generates

NAS_Filesystem

Either define both the filer and NAS file system name, or specify the unique ID, as follows:

  • Filer name: The name of the filer

  • File system name: The name of the NAS file system

  • object_unique_id: A unique identifier that Veritas Operations Manager generates

NAS_Share

Either define both the filer and path of the share, or specify the unique ID, as follows:

  • Filer name: The name of the filer

  • Path: The complete path of the share on the NAS volume

  • object_unique_id: A unique identifier that Veritas Operations Manager generates

Cluster

Define one or more of the following:

  • Name: The name of the cluster

  • object_unique_id: A unique identifier that Veritas Operations Manager generates

Service Group

Either define both the cluster and service group name, or specify the unique ID, as follows:

  • Cluster name: The name of the cluster

  • Service group name: The name of the service group

  • object_unique_id: A unique identifier that Veritas Operations Manager generates

The columns in the CSV file start with all of the levels in the branch, in order, separated by commas. There must be a column for each of the levels that are defined in the business view definition file. In addition to the level columns, you must define all the columns required for the object type. The unique identifier columns for the object type follow the levels.

Each non-comment, non-blank line defines a node or object in the business view. If the view defines a tree branch but no object assignment, use empty commas as placeholders for the object columns. If a leaf node misses its parent nodes, use empty commas as place holders.

Example:

#Continent, Country, State or Province, City, Data Center, name, IP, unique id

Europe,France,Paris,,,,10.68.8.15,

Comment lines start with "#". Comments and blank lines are ignored. Do not place any characters before the #. For example, if you include double quotes (") before the #, then the business view import process fails because the comment lines are considered assignment rows.

See About the .view structure file in Veritas Operations Manager Enterprise Server 5.0

See About the business view files in Veritas Operations Manager Enterprise Server 5.0


Legacy ID



v73877941_v71621782


Article URL http://www.symantec.com/docs/HOWTO77584


Terms of use for this information are found in Legal Notices