| chassis-id-subtype-type |
enumeration |
The source of a chassis identifier. |
| chassis-id-subtype-type |
enumeration |
The source of a chassis identifier. |
| chassis-id-subtype-type |
enumeration |
The source of a chassis identifier. |
| chassis-id-subtype-type |
enumeration |
The source of a chassis identifier. |
| chassis-id-subtype-type |
enumeration |
The source of a chassis identifier. |
| chassis-id-type |
string |
The format of a chassis identifier string. Objects of this type are
always used with an associated lldp-chassis-is-subtype object, which
identifies the format of the particular lldp-chassis-id object
instance.
If the associated lldp-chassis-id-subtype object has a value of
chassis-component, then the octet string identifies a particular
instance of the entPhysicalAlias object (defined in IETF RFC 2737) for
a chassis component (i.e., an entPhysicalClass value of chassis(3)).
If the associated lldp-chassis-id-subtype object has a value of
interface-alias, then the octet string identifies a particular
instance of the ifAlias object (defined in IETF RFC 2863) for an
interface on the containing chassis. If the particular ifAlias object
does not contain any values, another chassis identifier type should be
used.
If the associated lldp-chassis-id-subtype object has a value of
port-component, then the octet string identifies a particular instance
of the entPhysicalAlias object (defined in IETF RFC 2737) for a port
or backplane component within the containing chassis.
If the associated lldp-chassis-id-subtype object has a value of
mac-address, then this string identifies a particular unicast source
address (encoded in network byte order and IEEE 802.3 canonical bit
order), of a port on the containing chassis as defined in IEEE Std
802-2001.
If the associated lldp-chassis-id-subtype object has a value of
network-address, then this string identifies a particular network
address, encoded in network byte order, associated with one or more
ports on the containing chassis. The first octet contains the IANA
Address Family Numbers enumeration value for the specific address
type, and octets 2 through N contain the network address value in
network byte order.
If the associated lldp-chassis-id-subtype object has a value of
interface-name, then the octet string identifies a particular instance
of the ifName object (defined in IETF RFC 2863) for an interface on
the containing chassis. If the particular ifName object does not
contain any values, another chassis identifier type should be used.
If the associated lldp-chassis-id-subtype object has a value of local,
then this string identifies a locally assigned Chassis ID. |
| chassis-id-type |
string |
The format of a chassis identifier string. Objects of this type
are always used with an associated lldp-chassis-is-subtype object,
which identifies the format of the particular lldp-chassis-id
object instance.
If the associated lldp-chassis-id-subtype object has a value of
chassis-component, then the octet string identifies a particular
instance of the entPhysicalAlias object (defined in IETF RFC 2737)
for a chassis component (i.e., an entPhysicalClass value of
chassis(3)).
If the associated lldp-chassis-id-subtype object has a value of
interface-alias, then the octet string identifies a particular
instance of the ifAlias object (defined in IETF RFC 2863) for an
interface on the containing chassis. If the particular ifAlias
object does not contain any values, another chassis identifier
type should be used.
If the associated lldp-chassis-id-subtype object has a value of
port-component, then the octet string identifies a particular
instance of the entPhysicalAlias object (defined in IETF RFC 2737)
for a port or backplane component within the containing chassis.
If the associated lldp-chassis-id-subtype object has a value of
mac-address, then this string identifies a particular unicast
source address (encoded in network byte order and IEEE 802.3
canonical bit order), of a port on the containing chassis as
defined in IEEE Std 802-2001.
If the associated lldp-chassis-id-subtype object has a value of
network-address, then this string identifies a particular network
address, encoded in network byte order, associated with one or
more ports on the containing chassis. The first octet contains the
IANA Address Family Numbers enumeration value for the specific
address type, and octets 2 through N contain the network address
value in network byte order.
If the associated lldp-chassis-id-subtype object has a value of
interface-name, then the octet string identifies a particular
instance of the ifName object (defined in IETF RFC 2863) for an
interface on the containing chassis. If the particular ifName
object does not contain any values, another chassis identifier
type should be used.
If the associated lldp-chassis-id-subtype object has a value of
local, then this string identifies a locally assigned Chassis ID. |
| chassis-id-type |
string |
The format of a chassis identifier string. Objects of this type are
always used with an associated chassis-id-subtype object, which
identifies the format of the particular chassis-id object
instance.
If the associated chassis-id-subtype object has a value of
chassis-component, then the octet string identifies a particular
instance of the entPhysicalAlias object (defined in IETF RFC 2737) for
a chassis component (i.e., an entPhysicalClass value of chassis(3)).
If the associated chassis-id-subtype object has a value of
interface-alias, then the octet string identifies a particular
instance of the ifAlias object (defined in IETF RFC 2863) for an
interface on the containing chassis. If the particular ifAlias object
does not contain any values, another chassis identifier type should be
used.
If the associated chassis-id-subtype object has a value of
port-component, then the octet string identifies a particular instance
of the entPhysicalAlias object (defined in IETF RFC 2737) for a port
or backplane component within the containing chassis.
If the associated chassis-id-subtype object has a value of
mac-address, then this string identifies a particular unicast source
address (encoded in network byte order and IEEE 802.3 bit
significance), of a port on the containing chassis as defined in
IEEE Std 802.
If the associated chassis-id-subtype object has a value of
network-address, then this string identifies a particular network
address, encoded in network byte order, associated with one or more
ports on the containing chassis. The first octet contains the IANA
Address Family Numbers enumeration value for the specific address
type, and octets 2 through N contain the network address value in
network byte order.
If the associated chassis-id-subtype object has a value of
interface-name, then the octet string identifies a particular instance
of the ifName object (defined in IETF RFC 2863) for an interface on
the containing chassis. If the particular ifName object does not
contain any values, another chassis identifier type should be used.
If the associated chassis-id-subtype object has a value of local,
then this string identifies a locally assigned Chassis ID. |
| chassis-id-type |
string |
The format of a chassis identifier string. Objects of this type
are always used with an associated lldp-chassis-is-subtype
object, which identifies the format of the particular
lldp-chassis-id object instance.
If the associated lldp-chassis-id-subtype object has a value of
chassis-component, then the octet string identifies
a particular instance of the entPhysicalAlias object
(defined in IETF RFC 2737) for a chassis component (i.e.,
an entPhysicalClass value of chassis(3)).
If the associated lldp-chassis-id-subtype object has a value
of interface-alias, then the octet string identifies
a particular instance of the ifAlias object (defined in
IETF RFC 2863) for an interface on the containing chassis.
If the particular ifAlias object does not contain any values,
another chassis identifier type should be used.
If the associated lldp-chassis-id-subtype object has a value
of port-component, then the octet string identifies a
particular instance of the entPhysicalAlias object (defined
in IETF RFC 2737) for a port or backplane component within
the containing chassis.
If the associated lldp-chassis-id-subtype object has a value of
mac-address, then this string identifies a particular
unicast source address (encoded in network byte order and
IEEE 802.3 canonical bit order), of a port on the containing
chassis as defined in IEEE Std 802-2001.
If the associated lldp-chassis-id-subtype object has a value of
network-address, then this string identifies a particular
network address, encoded in network byte order, associated
with one or more ports on the containing chassis. The first
octet contains the IANA Address Family Numbers enumeration
value for the specific address type, and octets 2 through
N contain the network address value in network byte order.
If the associated lldp-chassis-id-subtype object has a value
of interface-name, then the octet string identifies
a particular instance of the ifName object (defined in
IETF RFC 2863) for an interface on the containing chassis.
If the particular ifName object does not contain any values,
another chassis identifier type should be used.
If the associated lldp-chassis-id-subtype object has a value of
local, then this string identifies a locally assigned
Chassis ID. |
| chassis-id-type |
string |
The format of a chassis identifier string. Objects of this type are
always used with an associated chassis-id-subtype object, which
identifies the format of the particular chassis-id object instance.
If the associated chassis-id-subtype object has a value of
chassis-component, then the octet string identifies a particular
instance of the entPhysicalAlias object (defined in IETF RFC 2737) for
a chassis component (i.e., an entPhysicalClass value of chassis(3)).
If the associated chassis-id-subtype object has a value of
interface-alias, then the octet string identifies a particular instance
of the ifAlias object (defined in IETF RFC 2863) for an interface on
the containing chassis. If the particular ifAlias object does not
contain any values, another chassis identifier type should be used.
If the associated chassis-id-subtype object has a value of
port-component, then the octet string identifies a particular instance
of the entPhysicalAlias object (defined in IETF RFC 2737) for a port or
backplane component within the containing chassis.
If the associated chassis-id-subtype object has a value of mac-address,
then this string identifies a particular unicast source address
(encoded in network byte order and IEEE 802.3 canonical bit order), of
a port on the containing chassis as defined in IEEE Std 802-2014.
If the associated chassis-id-subtype object has a value of
network-address, then this string identifies a particular network
address, encoded in network byte order, associated with one or more
ports on the containing chassis. The first octet contains the IANA
Address Family Numbers enumeration value for the specific address type,
and octets 2 through N contain the network address value in network
byte order.
If the associated chassis-id-subtype object has a value of
interface-name, then the octet string identifies a particular instance
of the ifName object (defined in IETF RFC 2863) for an interface on the
containing chassis. If the particular ifName object does not contain
any values, another chassis identifier type should be used.
If the associated chassis-id-subtype object has a value of local, then
this string identifies a locally assigned Chassis ID. |
| mac-address |
string |
The mac-address type represents a MAC address in the canonical
format and hexadecimal format specified by IEEE Std 802. The
hexidecimal representation uses uppercase characters. |
| mac-address |
string |
The mac-address type represents a MAC address in the canonical
format and hexadecimal format specified by IEEE Std 802. The
hexidecimal representation uses uppercase characters. |
| mac-address |
string |
The mac-address type represents a MAC address in the canonical format
and hexadecimal format specified by IEEE Std 802. The hexidecimal
representation uses uppercase characters. |
| mac-address |
string |
The mac-address type represents a MAC address in the canonical
format and hexadecimal format specified by IEEE Std 802. The
hexidecimal representation uses uppercase characters. |
| mac-address |
string |
The mac-address type represents a MAC address in the canonical format
and hexadecimal format specified by IEEE Std 802. The hexidecimal
representation uses uppercase characters. |
| mac-address |
string |
The mac-address type represents a MAC address in the canonical format
and hexadecimal format specified by IEEE Std 802. The hexadecimal
representation uses uppercase characters. |
| port-id-subtype-type |
enumeration |
The source of a particular type of port identifier used in the
LLDP YANG module. |
| port-id-subtype-type |
enumeration |
The source of a particular type of port identifier. |
| port-id-subtype-type |
enumeration |
The source of a particular type of port identifier used in the LLDP
YANG module. |
| port-id-subtype-type |
enumeration |
The source of a particular type of port identifier used
in the LLDP YANG module. |
| port-id-subtype-type |
enumeration |
The source of a particular type of port identifier. |
| port-id-type |
string |
The format of a port identifier string. Objects of this type
are always used with an associated lldp-port-id-subtype object,
which identifies the format of the particular lldp-port-id
object instance.
If the associated lldp-port-id-subtype object has a value of
interface-alias, then the octet string identifies a
particular instance of the ifAlias object (defined in IETF
RFC 2863). If the particular ifAlias object does not contain
any values, another port identifier type should be used.
If the associated lldp-port-id-subtype object has a value of
port-component, then the octet string identifies a
particular instance of the entPhysicalAlias object (defined
in IETF RFC 2737) for a port or backplane component.
If the associated lldp-port-id-subtype object has a value of
mac-address, then this string identifies a particular
unicast source address (encoded in network byte order
and IEEE 802.3 canonical bit order) associated with the port
(IEEE Std 802-2001).
If the associated lldp-port-id-subtype object has a value of
network-address, then this string identifies a network
address associated with the port. The first octet contains
the IANA AddressFamilyNumbers enumeration value for the
specific address type, and octets 2 through N contain the
networkAddress address value in network byte order.
If the associated lldp-port-id-subtype object has a value of
interface-name, then the octet string identifies a
particular instance of the ifName object (defined in IETF
RFC 2863). If the particular ifName object does not contain
any values, another port identifier type should be used.
If the associated lldp-port-id-subtype object has a value of
agent-circuit-id, then this string identifies a agent-local
identifier of the circuit (defined in RFC 3046).
If the associated lldp-port-id-subtype object has a value of
local, then this string identifies a locally assigned port ID. |
| port-id-type |
string |
The format of a port identifier string. Objects of this type are
always used with an associated lldp-port-id-subtype object, which
identifies the format of the particular lldp-port-id object instance.
If the associated lldp-port-id-subtype object has a value of
interface-alias, then the octet string identifies a particular
instance of the ifAlias object (defined in IETF RFC 2863). If the
particular ifAlias object does not contain any values, another port
identifier type should be used.
If the associated lldp-port-id-subtype object has a value of
port-component, then the octet string identifies a particular instance
of the entPhysicalAlias object (defined in IETF RFC 2737) for a port
or backplane component.
If the associated lldp-port-id-subtype object has a value of
mac-address, then this string identifies a particular unicast source
address (encoded in network byte order and IEEE 802.3 canonical bit
order) associated with the port (IEEE Std 802-2001).
If the associated lldp-port-id-subtype object has a value of
network-address, then this string identifies a network address
associated with the port. The first octet contains the IANA
AddressFamilyNumbers enumeration value for the specific address type,
and octets 2 through N contain the networkAddress address value in
network byte order.
If the associated lldp-port-id-subtype object has a value of
interface-name, then the octet string identifies a particular instance
of the ifName object (defined in IETF RFC 2863). If the particular
ifName object does not contain any values, another port identifier
type should be used.
If the associated lldp-port-id-subtype object has a value of
agent-circuit-id, then this string identifies a agent-local identifier
of the circuit (defined in RFC 3046).
If the associated lldp-port-id-subtype object has a value of local,
then this string identifies a locally assigned port ID. |
| port-id-type |
string |
The format of a port identifier string. Objects of this type are
always used with an associated lldp-port-id-subtype object, which
identifies the format of the particular lldp-port-id object
instance.
If the associated lldp-port-id-subtype object has a value of
interface-alias, then the octet string identifies a particular
instance of the ifAlias object (defined in IETF RFC 2863). If the
particular ifAlias object does not contain any values, another
port identifier type should be used.
If the associated lldp-port-id-subtype object has a value of
port-component, then the octet string identifies a particular
instance of the entPhysicalAlias object (defined in IETF RFC 2737)
for a port or backplane component.
If the associated lldp-port-id-subtype object has a value of
mac-address, then this string identifies a particular unicast
source address (encoded in network byte order and IEEE 802.3
canonical bit order) associated with the port (IEEE Std 802-2001).
If the associated lldp-port-id-subtype object has a value of
network-address, then this string identifies a network address
associated with the port. The first octet contains the IANA
AddressFamilyNumbers enumeration value for the specific address
type, and octets 2 through N contain the networkAddress address
value in network byte order.
If the associated lldp-port-id-subtype object has a value of
interface-name, then the octet string identifies a particular
instance of the ifName object (defined in IETF RFC 2863). If the
particular ifName object does not contain any values, another port
identifier type should be used.
If the associated lldp-port-id-subtype object has a value of
agent-circuit-id, then this string identifies a agent-local
identifier of the circuit (defined in RFC 3046).
If the associated lldp-port-id-subtype object has a value of
local, then this string identifies a locally assigned port ID. |
| port-id-type |
string |
The format of a port identifier string. Objects of this type are
always used with an associated port-id-subtype object, which identifies
the format of the particular port-id object instance.
If the associated port-id-subtype object has a value of
interface-alias, then the octet string identifies a particular instance
of the ifAlias object (defined in IETF RFC 2863). If the particular
ifAlias object does not contain any values, another port identifier
type should be used.
If the associated port-id-subtype object has a value of port-component,
then the octet string identifies a particular instance of the
entPhysicalAlias object (defined in IETF RFC 2737) for a port or
backplane component.
If the associated port-id-subtype object has a value of mac-address,
then this string identifies a particular unicast source address
(encoded in network byte order and IEEE 802.3 canonical bit order)
associated with the port (IEEE Std 802-2014).
If the associated port-id-subtype object has a value of
network-address, then this string identifies a network address
associated with the port. The first octet contains the IANA
AddressFamilyNumbers enumeration value for the specific address type,
and octets 2 through N contain the networkAddress address value in
network byte order.
If the associated port-id-subtype object has a value of interface-name,
then the octet string identifies a particular instance of the ifName
object (defined in IETF RFC 2863). If the particular ifName object does
not contain any values, another port identifier type should be used.
If the associated port-id-subtype object has a value of
agent-circuit-id, then this string identifies a agent-local identifier
of the circuit (defined in RFC 3046).
If the associated port-id-subtype object has a value of local, then
this string identifies a locally assigned port ID. |
| port-id-type |
string |
The format of a port identifier string. Objects of this type are
always used with an associated port-id-subtype object, which
identifies the format of the particular port-id object instance.
If the associated port-id-subtype object has a value of
interface-alias, then the octet string identifies a particular
instance of the ifAlias object (defined in IETF RFC 2863). If the
particular ifAlias object does not contain any values, another port
identifier type should be used.
If the associated port-id-subtype object has a value of
port-component, then the octet string identifies a particular instance
of the entPhysicalAlias object (defined in IETF RFC 2737) for a port
or backplane component.
If the associated port-id-subtype object has a value of
mac-address, then this string identifies a particular unicast source
address (encoded in network byte order and IEEE 802.3 bit
significance) associated with the port (IEEE Std 802).
If the associated port-id-subtype object has a value of
network-address, then this string identifies a network address
associated with the port. The first octet contains the IANA
AddressFamilyNumbers enumeration value for the specific address type,
and octets 2 through N contain the networkAddress address value in
network byte order.
If the associated port-id-subtype object has a value of
interface-name, then the octet string identifies a particular instance
of the ifName object (defined in IETF RFC 2863). If the particular
ifName object does not contain any values, another port identifier
type should be used.
If the associated port-id-subtype object has a value of
agent-circuit-id, then this string identifies a agent-local identifier
of the circuit (defined in RFC 3046).
If the associated port-id-subtype object has a value of local,
then this string identifies a locally assigned port ID. |