User guide

ExtremeWare EPICenter Software Installation and User Guide 8-35
Importing Resources
<resource_type>:<resource_uniqueID> <tab> <resource_type>:<resource_uniqueID>
<resource_type>:<resource_uniqueID>
<tab> <resource_type>:<resource_uniqueID>
• resource_type can be user, host, group, device,orport. A group that exists in the
EPICenter database (and is not defined in the import file) can be specified as a child of
an imported group, but the reverse is not supported.
•
resource_uniqueID is the unique ID defined in the first part of the file (or known to
exist already in the EPICenter database).
For creating group membership relationships, the first type:ID pair defines the parent, the
second one defines the child. Thus, the first pair must always be a group. The second pair
canbeagrouporanindividualresource.
For defining peer-to-peer relationships, (user-host, user-port, and host-port relationships)
either member of the relationship can be specified first.
Example
The following is an example of an import file.
#SYNTAX VERSION:1.0
Resource_UniqueName Resource_Type Resource_Name IP Address DLCS OSType Dept
(IP/Subnet)(DLCS ID)(Generic)(Generic)
wendy user Wendy Lee NMS
heidi user Heidi Smith NMS
pam user Pam Johnson SQA
eric user Eric Wilson SQA
mary user Mary Baker NMS
win2k host win2k 10.20.30.2 wlee windows NMS
host1 host host1 10.20.30.4 HPUX NMS
host2 host host2 10.20.30.5 Solaris NMS
host3 host host3 10.20.30.6 windows SQA
host4 host host4 10.20.30.7 Solaris SQA
ugr1 group SQA
ugr2 group dev
hgr1 group hostgr1
dgr1 group eng1
switch group switch
portgr group portgr
#GROUPS#
group:ugr1 user:wendy