Docstoc

CSV Import Template - Raritan

Document Sample
CSV Import Template - Raritan Powered By Docstoc
					# pdu_ip      PX User Name          PX Password SNMP Write Community String
192.168.60.50 admin                 raritan     private

#Notes:
#Remove these notes before import
#Remove row one before import
#Data in red is an example and should be modified with your data. You can add additional rows for each PDU
#This file should be imported as a stand alone csv file into the "Import PDUs" page under the "Import PDUs from CSV file" pag
for each PDU
 port PDUs from CSV file" page under the PDU tab
# object_type external_key name     contact_name    contact_phone contact_email
DATA_CENTER Somerset NJ Somerset NJ James Cerwinski 732 764 8886 jamesc@raritan.com




#Notes:
#Remove these notes before import
#Data in red is an example and should be modified with your data. You can add additional rows for each Data_Center
#Each "external_key" needs to be unique. If your data center names are unique, then the "external_key" can be the same as th
#Don't use dashes in the contact_phone field
#This file should be imported as a stand alone csv file into the "CSV Data Mapping Actions" section under the "Enterprise Relat
             company_name city     state             country     peak_kwh_rate off_peak_kwh_rate peak_begin
             Raritan      Somerset NJ                US                     0.2              0.1          7




each Data_Center
key" can be the same as the "name"

under the "Enterprise Relationships page" page under the Settings tab
peak_end co2_factor cooling_factor
      22        0.4              2
# object_type external_key name       parent_object_type parent_external_key
RACK          Rack1Floor1 Rack1Floor1 DATA_CENTER        Somerset NJ


#Notes:
#Remove these notes before import
#Data in red is an example and should be modified with your data. You can add additional rows for each RACK
#Each "external_key" needs to be unique. If your rack names are unique, then the "external_key" can be the same as the "nam
#This example associates a RACK with a parent of DATA_CENTER. See the user guide if you want to use FLOOR, ROOM, o
#This file should be imported as a stand alone csv file into the "CSV Data Mapping Actions" section under the "Enterprise Relat
or each RACK
 can be the same as the "name"
ant to use FLOOR, ROOM, or ROW as the parent of a rack
 n under the "Enterprise Relationships page" page under the Settings tab
# object_type external_key                              name
DEVICE        Exchange                                  Exchange


#Notes:
#Remove these notes before import
#Data in red is an example and should be modified with your data. You can add additional rows for each DEVICE
#Each "external_key" needs to be unique. If your devcie names are unique, then the "external_key" can be the same as the "n
#This file should be imported as a stand alone csv file into the "CSV Data Mapping Actions" section under the "Enterprise Relat
             parent_object_type parent_external_key customer device_type                 power_rating decommissioned
             RACK               Rack1Floor1         Raritan  Server                                       FALSE




ditional rows for each DEVICE
e "external_key" can be the same as the "name"
Actions" section under the "Enterprise Relationships page" page under the Settings tab
custom_field_1 custom_field_2
default        default
# object_type pdu_ip        parent_object_type parent_external_key
PDU           192.168.60.50 RACK               Rack1Floor1


#Notes:
#Remove these notes before import
#Data in red is an example and should be modified with your data. You can add additional rows for each PDU
#This file should be imported as a stand alone csv file into the "CSV Data Mapping Actions" section under the "Enterprise Relat
 for each PDU
ion under the "Enterprise Relationships page" page under the Settings tab
# object_type pdu_ip        outlet_number parent_object_type parent_external_key
OUTLET        192.168.58.50             1 DEVICE             Exchange


#Notes:
#Remove these notes before import
#Data in red is an example and should be modified with your data. You can add additional rows for each OUTLET
#This file should be imported as a stand alone csv file into the "CSV Data Mapping Actions" section under the "Enterprise Relat
 for each OUTLET
ion under the "Enterprise Relationships page" page under the Settings tab
#PX IP Address PX Contact PX Name        PX Location   Outlet 1              Outlet 2   Outlet 3   Outlet 4
192.168.60.50 James       Phase_A_Ckt_14 Rack1Floor1 R Name 1                Name 2     Name 3     Name 4



#Notes:
#Remove these notes before import
#Remove row one before import
#Data in red is an example and should be modified with your data. You can add additional rows for each PX PDU
#This file should be imported as a stand alone csv file into the "Import PDU Outlet Names" page under the "Outlet Naming" pag
             Outlet 5   Outlet 6   Outlet 7   Outlet 8
             Name 5     Name 6     Name 7     Name 8




each PX PDU
der the "Outlet Naming" page under the Dashboard tab

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:6
posted:11/6/2011
language:English
pages:16