Cisco Cisco Evolved Programmable Network Manager 2.0 Developer's Guide
RESTCONF/YANG Interface Details
Cisco Evolved Programmable Network Manager 2.0 RESTCONF NBI Guide
64
64
PhysicalConnector Retrieval
4.6
This interface provides the operations to retrieve PhysicalConnector entities. Represents a
connector that can transmit signals or power when in a connection.
connector that can transmit signals or power when in a connection.
PhysicalConnector Data
Associated objects are represented by a collection, for one-to-many associations, or an
attribute of the object type for one-to-one or many-to-one associates. The role of the
object(s) in the association provides the name for association attributes. The API traverses
selected associations, usually of one-to-many cardinality, to allow retrieval of a hierarchy
of objects in a single request. Attribute names of such associations are followed by an
asterisk (*).
To prevent cycles in the retrieval or divide the hierarchy into manageable pieces, other
associations are summarized as a string with an entry giving the object type, name, and
business key for each object in the collection. Some attributes may not be displayed since
null values and empty associations are not included in the response.
The following table lists the attributes in the PhysicalConnector object:
attribute of the object type for one-to-one or many-to-one associates. The role of the
object(s) in the association provides the name for association attributes. The API traverses
selected associations, usually of one-to-many cardinality, to allow retrieval of a hierarchy
of objects in a single request. Attribute names of such associations are followed by an
asterisk (*).
To prevent cycles in the retrieval or divide the hierarchy into manageable pieces, other
associations are summarized as a string with an entry giving the object type, name, and
business key for each object in the collection. Some attributes may not be displayed since
null values and empty associations are not included in the response.
The following table lists the attributes in the PhysicalConnector object:
PhysicalConne
ctor Data
ctor Data
Data Type
Description
instanceId
int
Instance identifier of entity in the database.
businessKey
String
String representation of attribute value(s) that uniquely identify the entity
or instanceId if no business key defined
or instanceId if no business key defined
description
String
an optional description of the entity
entAliasLogical
IndexOrZero
IndexOrZero
String
## Internal use only ##
entPhysicalCo
ntainedIn
ntainedIn
String
## Internal use only ##
entPhysicalInd
ex
ex
String
## Internal use only ##
name
String
the name of the entity
owningEntityI
d
d
String
## Internal use only ##
subclassname
String
The name of the object type.
vendorEquipm
entType
entType
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.
Operations
All URLs require basic authentication and can produce:
application/xml
application/yang.data+xml
application/json