Status in source: current.
Names: pwEntry
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"pwEntry",
"OBJECT-TYPE",
"SYNTAX",
"PwEntry",
"MAX-ACCESS",
"not-accessible",
"STATUS",
"current",
"DESCRIPTION",
"\"A row in this table represents a pseudo-wire (PW) virtual connection across a packet network. It is indexed by pwIndex, which uniquely identifies a singular connection. A row can be created by an operator command from a management plan of a PE, by signaling or due to autodiscovery process. Operator's command can be issued via non SNMP application; in such case a row will be created implicitly by the agent. The read-create objects in this tables are divided into three categories: 1) Objects that MUST NOT be changed after row activation. These are objects that define basic properties of the PW (for example type, destination, etc.). 2) Objects that MAY be changed when the PW is defined as not active. A change of these objects involves re-signaling of the PW or it might be traffic affecting. PW not active is defined as one of the following conditions: a) The pwRowStatus is notInService(2). b) The pwRowStatus is notReady(3). c) The pwAdminStatus is down(2). If the operator needs to change one of the values for an active row, the operator can either set the pwRowStatus to notInService(2) or set pwAdminStatus to down(2). Signaling (or traffic) is initiated again upon setting the pwRowStatus to active(1) or setting the pwAdminStatus to up(1) or testing(3) respectively. 3) Objects that MAY be changed at any time. By default, all the read-create objects MUST NOT be changed after row activation, unless specifically indicated in the individual object description. Manual entries in this table SHOULD be preserved after a re-boot, the agent MUST ensure the integrity of those entries. If the set of entires of a specific row are found to be non consistent after reboot, the PW pwOperStatus MUST be declared as notPresent(5). \"",
"INDEX",
"{",
"pwIndex",
"}",
"::=",
"{",
"pwTable",
"1",
"}"
],
"syntax_tree": [
[
"row",
"PwEntry"
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"A row in this table represents a pseudo-wire (PW) virtual connection across a packet network. It is indexed by pwIndex, which uniquely identifies a singular connection. A row can be created by an operator command from a management plan of a PE, by signaling or due to autodiscovery process. Operator's command can be issued via non SNMP application; in such case a row will be created implicitly by the agent. The read-create objects in this tables are divided into three categories: 1) Objects that MUST NOT be changed after row activation. These are objects that define basic properties of the PW (for example type, destination, etc.). 2) Objects that MAY be changed when the PW is defined as not active. A change of these objects involves re-signaling of the PW or it might be traffic affecting. PW not active is defined as one of the following conditions: a) The pwRowStatus is notInService(2). b) The pwRowStatus is notReady(3). c) The pwAdminStatus is down(2). If the operator needs to change one of the values for an active row, the operator can either set the pwRowStatus to notInService(2) or set pwAdminStatus to down(2). Signaling (or traffic) is initiated again upon setting the pwRowStatus to active(1) or setting the pwAdminStatus to up(1) or testing(3) respectively. 3) Objects that MAY be changed at any time. By default, all the read-create objects MUST NOT be changed after row activation, unless specifically indicated in the individual object description. Manual entries in this table SHOULD be preserved after a re-boot, the agent MUST ensure the integrity of those entries. If the set of entires of a specific row are found to be non consistent after reboot, the PW pwOperStatus MUST be declared as notPresent(5)."
],
null,
null,
[
"INDEX",
[
[
0,
"pwIndex"
]
]
],
null
]
}
- Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)
· Publisher's source file: Source package: observium-community-latest.tar.gz
Vendor MIB copy from the Observium Community archive.
Module: FOUNDRY-PW-STD-MIB
See published definition above
Module imports
{'IF-MIB': ['InterfaceIndexOrZero'], 'SNMPv2-TC': ['TruthValue', 'RowStatus', 'StorageType', 'TimeStamp', 'TEXTUAL-CONVENTION'], 'SNMPv2-SMI': ['NOTIFICATION-TYPE', 'MODULE-IDENTITY', 'OBJECT-TYPE', 'Integer32', 'Unsigned32', 'Counter32', 'Counter64', 'TimeTicks'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'PerfHist-TC-MIB': ['PerfCurrentCount', 'PerfIntervalCount'], 'INET-ADDRESS-MIB': ['InetAddressType', 'InetAddress'], 'HC-PerfHist-TC-MIB': ['HCPerfCurrentCount', 'HCPerfIntervalCount', 'HCPerfTimeElapsed', 'HCPerfValidIntervals'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString'], 'FOUNDRY-SN-ROOT-MIB': ['pwe3'], 'FOUNDRY-SN-AGENT-MIB': ['snAgGblTrapMessage'], 'FOUNDRY-IANA-PWE3-MIB': ['IANAPwTypeTC', 'IANAPwPsnTypeTC', 'IANAPwCapabilities'], 'FOUNDRY-PW-TC-STD-MIB': ['PwIndexType', 'PwIndexOrZeroType', 'PwGroupID', 'PwIDType', 'PwOperStatusTC', 'PwAttachmentIdentifierType', 'PwCwStatusTC', 'PwStatus', 'PwFragSize', 'PwFragStatus']}
Related source files and packages: