Cisco Cisco Evolved Programmable Network Manager 1.2 Developer's Guide
RESTCONF/YANG
Interface Details
Cisco EPNM RESTConf NBI Guide
41
eStateEnum
the management application. It indicates whether the entity is in service,
out of service, under maintenance, and so on.
out of service, under maintenance, and so on.
slotConfig
String
** Deprecated. Will be removed after EquipmentHolder is put back in the
model **\r\nAn indication of which slots in the chassis have modules
inserted. This is an integer value with bits set to indicate configured
modules. It can be interpreted as a sum of f(x) as x goes from 1 to the
number of slots, where f(x) = 0 for no module inserted and f(x) = exp(2, x-
1) for a module inserted. Based on the MIB definition, it can only
represent (the first) 16 slots in a Chassis.
model **\r\nAn indication of which slots in the chassis have modules
inserted. This is an integer value with bits set to indicate configured
modules. It can be interpreted as a sum of f(x) as x goes from 1 to the
number of slots, where f(x) = 0 for no module inserted and f(x) = exp(2, x-
1) for a module inserted. Based on the MIB definition, it can only
represent (the first) 16 slots in a Chassis.
subclassname
String
The name of the object type
udi
String
Universal Device Identifier. The UDI is composed by concatenating the
following values:\r\nPID = Equipment.partNumber\r\nVID =
Equipment.hardwareVersion\r\nSN = Equipment.serialNumber
following values:\r\nPID = Equipment.partNumber\r\nVID =
Equipment.hardwareVersion\r\nSN = Equipment.serialNumber
vendorEquipment
Type
Type
String
An indication of the vendor-specific hardware type of the physical entity.
Represents an independently extensible type identification value. It can,
for example, indicate a particular subtree with further MIB definitions, or
define a particular type of protocol or hardware (for example,
1.3.6.1.4.1.9.12.3.1.9.3.131).\r\nSee CISCO-ENTITY-VENDORTYPE-OID-
MIB.
Represents an independently extensible type identification value. It can,
for example, indicate a particular subtree with further MIB definitions, or
define a particular type of protocol or hardware (for example,
1.3.6.1.4.1.9.12.3.1.9.3.131).\r\nSee CISCO-ENTITY-VENDORTYPE-OID-
MIB.
connectors *
Set<PhysicalCon
nector>
nector>
The set of instances of PhysicalConnectors contained in this piece of
Equipment.
Equipment.
containedEquipm
ent *
ent *
Set<Equipment>
A set of instances of Equipment contained in this instance of Equipment.
occupiedHolders
Set<EquipmentH
older>
older>
The EquipmentHolders occupied by this piece of Equipment.\n Other
pieces of Equipment provide these Holders. For example: A Module can
occupy one or two Slots provided by a Chassis.
pieces of Equipment provide these Holders. For example: A Module can
occupy one or two Slots provided by a Chassis.
providedHolders
Set<EquipmentH
older>
older>
A collection of the EquipmentHolders provided by this Chassis. Other
pieces of Equipment can occupy these Holders. For example: A Chassis
can provide many Slots, and Modules can occupy the Slots.
pieces of Equipment can occupy these Holders. For example: A Chassis
can provide many Slots, and Modules can occupy the Slots.
Operations
The table below lists the operations available to retrieve Chassis data from RESTCONF via
the http protocol.
All URLs require basic authentication and can produce:
the http protocol.
All URLs require basic authentication and can produce:
application/xml
application/yang.data+xml
application/json
application/yang.data+json
The first URL retrieves all the Chassis entities in the database. The next URL returns a
specific Chassis entity by its business key. Enter the values of the attributes shown in the
braces, but do not include the braces. The final URL retrieves a specific Chassis by its
database instance id. Enter the instance id, but do not include the braces.
URL
Description
http://<host>/restconf/v1/data/epnm-restconf-xmp-im-ext-chassis:Chassis
Retrieve all Chassis instances