Download Print this page

Extreme Networks EPICenter Reference Manual page 247

Hide thumbs Also See for EPICenter:

Advertisement

The combination of
uniqueID
definitions generate a warning.
For example, assume the following format definition at the beginning of the import file:
Resource_UniqueName Resource_Type Resource_Name
To create a user resource named Judy Jones, with three attributes:
Location, whose value is Denver
Department, whose value is Sales
RoomNo whose value is 3050
Enter a resource definition as follows:
judy user
Judy Jones
You cannot use the Import function to create new device or port resources. You can import attributes for
device and port resources, and define relationships for them. The device and port resources must
already exist in the EPICenter database, and the names you specify must match their names in the
database.
See
"Resource
Details,"
on page 226
Group and Relationship Definitions. The second part of the file defines the relationships between the
resources—both group membership and relationships between the resources themselves (see
Relationships to a
Resource,"
The
specification is required, even if you do not define any groups.
#GROUPS#
#GROUPS#
Each line in this section has the following form:
<resource_type>:<resource_uniqueID>
<resource_type>:<resource_uniqueID>
can be
resource_type
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.
is the unique ID defined in the first part of the file (or known to exist already in
resource_uniqueID
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 can be a group or an
individual resource.
For defining peer-to-peer relationships, (user-host, user-port, and host-port relationships) either member
of the relationship can be specified first.
EPICenter Reference Guide
and
must be unique within this section. Duplicate
resource_type
Denver
Sales
for more information on the components of a resource.
on page 233
for more information about relationships).
<tab>
<resource_type>:<resource_uniqueID>
<tab>
<resource_type>:<resource_uniqueID>
,
,
,
user
host
group
device
Location Department
3050
, or
. A group that exists in the EPICenter
port
Importing Resources
RoomNo
"Adding
247

Advertisement

loading

This manual is also suitable for:

Epicenter 6.0