This attribute controls which IP stack the Snmp component will use
to send and receive Snmp traffic for Communites and Parties whose
tdomain attribute specifies snmpUdpDomain as the transport
protocol.
If the value of this attribute is vrIp then Snmp Udp traffic will be
sent and received using Ip as provisioned under the VirtualRouter.
This requires provisioning of the ip feature.
If the value of this attribute is ipiFrIpiVc then Snmp Udp traffic
will be sent and received using IpiFr (Ip over Frame Relay) or IpiVc
(Ip over Vc), whichever is provisioned. This requires provisioning
of one of the ipiVc or ipiFr features.
Parsed from file nortelPC-baseSnmpV1.mib.txt
Company: None
Module: Nortel-MsCarrier-MscPassport-BaseSnmpMIB
This attribute controls which IP stack the Snmp component will use
to send and receive Snmp traffic for Communites and Parties whose
tdomain attribute specifies snmpUdpDomain as the transport
protocol.
If the value of this attribute is vrIp then Snmp Udp traffic will be
sent and received using Ip as provisioned under the VirtualRouter.
This requires provisioning of the ip feature.
If the value of this attribute is ipiFrIpiVc then Snmp Udp traffic
will be sent and received using IpiFr (Ip over Frame Relay) or IpiVc
(Ip over Vc), whichever is provisioned. This requires provisioning
of one of the ipiVc or ipiFr features.
Parsed from file Nortel-MsCarrier-MscPassport-BaseSnmpMIB.mib
Module: Nortel-MsCarrier-MscPassport-BaseSnmpMIB
Vendor: Northern Telecom, Ltd.
Module: Nortel-MsCarrier-MscPassport-BaseSnmpMIB
[Automatically extracted from oidview.com]
mscVrSnmpIpStack OBJECT-TYPE SYNTAX INTEGER { vrIp(1), ipiFrIpiVc(2) } ACCESS read-write STATUS mandatory DESCRIPTION "This attribute controls which IP stack the Snmp component will use to send and receive Snmp traffic for Communites and Parties whose tdomain attribute specifies snmpUdpDomain as the transport protocol. If the value of this attribute is vrIp then Snmp Udp traffic will be sent and received using Ip as provisioned under the VirtualRouter. This requires provisioning of the ip feature. If the value of this attribute is ipiFrIpiVc then Snmp Udp traffic will be sent and received using IpiFr (Ip over Frame Relay) or IpiVc (Ip over Vc), whichever is provisioned. This requires provisioning of one of the ipiVc or ipiFr features." DEFVAL { vrIp } ::= { mscVrSnmpProvEntry 4 }
mscVrSnmpIpStack OBJECT-TYPE SYNTAX INTEGER { vrIp(1), ipiFrIpiVc(2) } ACCESS read-write STATUS mandatory DESCRIPTION "This attribute controls which IP stack the Snmp component will use to send and receive Snmp traffic for Communites and Parties whose tdomain attribute specifies snmpUdpDomain as the transport protocol. If the value of this attribute is vrIp then Snmp Udp traffic will be sent and received using Ip as provisioned under the VirtualRouter. This requires provisioning of the ip feature. If the value of this attribute is ipiFrIpiVc then Snmp Udp traffic will be sent and received using IpiFr (Ip over Frame Relay) or IpiVc (Ip over Vc), whichever is provisioned. This requires provisioning of one of the ipiVc or ipiFr features." DEFVAL { vrIp } ::= { mscVrSnmpProvEntry 4 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.562.36.2.1.100.8.20.1.1 | mscVrSnmpV1EnableAuthenTraps | 0 | 0 | This attribute controls whether the Snmp component will generate V1 authentication failure traps or not. The attribute is derive… |
| 1.3.6.1.4.1.562.36.2.1.100.8.20.1.2 | mscVrSnmpV2EnableAuthenTraps | 0 | 0 | This attribute controls whether the Snmp component will generate V2 authentication failure traps or not. The attribute is derive… |
| 1.3.6.1.4.1.562.36.2.1.100.8.20.1.3 | mscVrSnmpAlarmsAsTraps | 0 | 0 | This attribute controls whether the Snmp component will send Alarms as SNMPv1 and SNMPv2 Traps. If enabled, Alarms will be sent a… |
| 1.3.6.1.4.1.562.36.2.1.100.8.20.1.5 | mscVrSnmpCidInEntTraps | 0 | 0 | This attribute controls whether the Customer Identifier (CID) will be included in the SNMP Enterprise Traps. If enabled, the CID… |