Status in source: current.
Names: prvtLsrId
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"prvtLsrId",
"OBJECT-TYPE",
"SYNTAX",
"InetAddressIPv4",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"This object allows LSR Id value to be set. It is needed for unique identification of LSR instance, from which the packets are sent through created LDP session. Although every 32 bit value is valid, it is recommended the device's loopback ip address to be used. A value of zero indicates that no LSR ID has been configured. In this case, the signaling protocol stack should construct a unique LSR ID from the other information that is available to it (such as IP addresses). For example, PRVT-CR-LDP and PRVT-RSVP derive the LSR ID by taking the 32 low bits of the following _transport_address_ field, left padding with zeros if necessary.\"",
"::=",
"{",
"prvtLmgrObjects",
"1",
"}"
],
"syntax_tree": [
[
"row",
"InetAddressIPv4"
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"This object allows LSR Id value to be set. It is needed for unique identification of LSR instance, from which the packets are sent through created LDP session. Although every 32 bit value is valid, it is recommended the device's loopback ip address to be used. A value of zero indicates that no LSR ID has been configured. In this case, the signaling protocol stack should construct a unique LSR ID from the other information that is available to it (such as IP addresses). For example, PRVT-CR-LDP and PRVT-RSVP derive the LSR ID by taking the 32 low bits of the following _transport_address_ field, left padding with zeros if necessary."
],
null,
null,
null,
null
]
}