Status in source: current.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"hiscomIpmcMvrConfigVlanPortRole",
"OBJECT-TYPE",
"SYNTAX",
"HISCOMIpmcMvrVlanInterfacePortRole",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"Configure a MVR port of the designated MVR VLAN as one of the following roles: Inactive, Source or Receiver. An inactive port does not participate MVR operations. Configure uplink ports that receive and send multicast data as a source port, and multicast subscribers cannot be directly connected to source ports. Configure a port as a receiver port if it is a subscriber port and should only receive multicast data, and a receiver port does not receive data unless it becomes a member of the multicast group by issuing IGMP/MLD control messages. Be Caution: MVR source ports are not recommended to be overlapped with management VLAN ports.\"",
"::=",
"{",
"hiscomIpmcMvrConfigVlanPortEntry",
"3",
"}"
],
"syntax_tree": [
[
"row",
"HISCOMIpmcMvrVlanInterfacePortRole"
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Configure a MVR port of the designated MVR VLAN as one of the following roles: Inactive, Source or Receiver. An inactive port does not participate MVR operations. Configure uplink ports that receive and send multicast data as a source port, and multicast subscribers cannot be directly connected to source ports. Configure a port as a receiver port if it is a subscriber port and should only receive multicast data, and a receiver port does not receive data unless it becomes a member of the multicast group by issuing IGMP/MLD control messages. Be Caution: MVR source ports are not recommended to be overlapped with management VLAN ports."
],
null,
null,
null,
null
]
}