Status in source: current.
Names: chmgrODescrDestinationTable
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"chmgrODescrDestinationTable",
"OBJECT-TYPE",
"SYNTAX",
"SEQUENCE",
"OF",
"ChmgrODescrDestinationEntry",
"MAX-ACCESS",
"not-accessible",
"STATUS",
"current",
"DESCRIPTION",
"\"The table describes destinations for a connection. A unicast connection can normally only have one destination, while a multicast connection may have several destinations. If a unicast connection allows alternative destinations, as defined by the allowAlternative(10) bit in chmgrODescrCapabilities, it is allowed to define multiple destinations. At channel establishment, the destinations will be tried in succession until a channel is successfully established. It is possible to add, change and delete destinations while the connection is active. For a unicast connection, a changed destination is torn down as soon as it is changed, and established as soon as the changed information contains valid data. For a multicast connection, it is possible to add and delete destinations to an already established connection without affecting the connection to the other destinations. An added destination will be established as soon as it includes valid information, and will be re-established as soon as the information is changed. Note that a destination address with an empty string can be used to disable the destination. For a multicast connection a single destination can also be enabled and disabled using its administrative status. The bits allowAlternative(10), destination(1) and allowMulticast(3) in chmgrODescCapabilities describes if and how it is allowed to add a destination to a connection.\"",
"::=",
"{",
"chmgrODescriptionGroup",
"3",
"}"
],
"syntax_tree": [
[
"conceptualTable",
[
"row",
"ChmgrODescrDestinationEntry"
]
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The table describes destinations for a connection. A unicast connection can normally only have one destination, while a multicast connection may have several destinations. If a unicast connection allows alternative destinations, as defined by the allowAlternative(10) bit in chmgrODescrCapabilities, it is allowed to define multiple destinations. At channel establishment, the destinations will be tried in succession until a channel is successfully established. It is possible to add, change and delete destinations while the connection is active. For a unicast connection, a changed destination is torn down as soon as it is changed, and established as soon as the changed information contains valid data. For a multicast connection, it is possible to add and delete destinations to an already established connection without affecting the connection to the other destinations. An added destination will be established as soon as it includes valid information, and will be re-established as soon as the information is changed. Note that a destination address with an empty string can be used to disable the destination. For a multicast connection a single destination can also be enabled and disabled using its administrative status. The bits allowAlternative(10), destination(1) and allowMulticast(3) in chmgrODescCapabilities describes if and how it is allowed to add a destination to a connection."
],
null,
null,
null,
null
]
}