Cisco Cisco Evolved Programmable Network Manager 1.2 Developer's Guide
RESTCONF/YANG Interface Details
Cisco EPN Manager RESTConf NBI Guide
68
68
on.
serialNumber
String
The vendor-specific serial number string for the physical entity. The preferred
value is the serial number string actually printed on the component itself (if
present). If a serial number is unknown or nonexistent, the SerialNumber will be
left null. Note that not every physical component has (or needs) a serial
number. Physical entities, which are not FRU (field replaceable) do not need
their own unique serial number. This item is used for composing the UDI SID
(see attribute 'udi').
value is the serial number string actually printed on the component itself (if
present). If a serial number is unknown or nonexistent, the SerialNumber will be
left null. Note that not every physical component has (or needs) a serial
number. Physical entities, which are not FRU (field replaceable) do not need
their own unique serial number. This item is used for composing the UDI SID
(see attribute 'udi').
serviceState
Equipme
ntService
StateEnu
m
ntService
StateEnu
m
Denotes the service state of a physical entity from the point of view of the
management application. It indicates whether the entity is in service, out of
service, under maintenance, and so on.
management application. It indicates whether the entity is in service, out of
service, under maintenance, and so on.
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
values:\r\nPID = Equipment.partNumber\r\nVID =
Equipment.hardwareVersion\r\nSN = Equipment.serialNumber
vendorEquipmentT
ype
ype
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<Phys
icalConn
ector>
icalConn
ector>
The set of instances of PhysicalConnectors contained in this piece of Equipment.
containedEquipme
nt *
nt *
Set<Equi
pment>
pment>
A set of instances of Equipment contained in this instance of Equipment.
occupiedHolders
Set<Equi
pmentHo
lder>
pmentHo
lder>
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.
Equipment provide these Holders. For example: A Module can occupy one or
two Slots provided by a Chassis.
Operations
The table below lists the operations available to retrieve Module 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 Module entities in the database. The next URL returns a
specific Module 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 Module 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-module:Module
Retrieve all Module instances
http://<host>/restconf/v1/data/epnm-restconf-xmp-im-ext-
Retrieve Module instance by