MIB
Click on the red underlined text to get to the source
...
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community ...
... accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol ...
... the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP ...
... Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI ...
... Structure of Management Information (SMI). This memo specifies a set
of MIB modules that are compliant to the SMIv2, which is described in
STD ...
... multimedia distribution, and multimedia conferences.
This MIB provides some managed objects for SIP entities defined in
...
... used in all the SIP entities. SIP-SERVER-MIB contains objects
specific to Proxy, Redirect, and Registrar servers. SIP ...
... Proxy, Redirect, and Registrar servers. SIP-UA-MIB
includes objects specific to User Agents. SIP ...
... includes objects specific to User Agents. SIP-TC-MIB defines the
textual conventions used throughout the MIB modules ...
... SNMP agent MUST implement the
SIP-TC-MIB module, plus the SIP-COMMON-MIB module and one of the SIP
entity ...
... SIP-TC-MIB module, plus the SIP-COMMON-MIB module and one of the SIP
entity-type-specific MIB modules (SIP ...
... SIP-COMMON-MIB module and one of the SIP
entity-type-specific MIB modules (SIP-SERVER-MIB or SIP ...
... SipTCOptionTagHeaders, and SipTCMethodName are defined in the SIP-
TC-MIB module and used as Textual Conventions in this document.
...
... Relationship to the Network Services MIB ...
... requirement: the SIP MIB must allow a single system with a single
SNMP agent to support multiple instances of various SIP ...
... SNMP agent to support multiple instances of various SIP MIB modules.
This requirement is met by using the framework ...
... NETWORK-SERVICES-
MIB and, at a minimum, MUST support the index and name objects
(applIndex and applName) in the application table (applTable). In
order to allow each instance of a SIP entity ...
... UAs that need to be managed as 2 separate SIP
entities, by convention, the application names used in the Network
Services Monitoring MIB application table should be "sip_ua1" and
"sip_ua2". This convention allows each instance to have its own row
...
... o applUptime: the value of applUptime MUST be identical to the value
of sipCommonCfgServiceStartTime defined in the SIP-COMMON-MIB
module.
o applOperStatus: the value of applOperStatus SHOULD reflect the
...
... Registrar server might be configured to maintain separate SIP-
COMMON-MIB instances.
The NETWORK ...
... The NETWORK-SERVICES-MIB applTable might be populated as follows:
+-----------+-------------------+----------------------+
...
...
The SIP-COMMON-MIB sipCommonCfgTable would have two rows: one for the
proxy (applIndex=1) and one for the registrar (applIndex=2). The
...
... proxy (applIndex=1) and one for the registrar (applIndex=2). The
SIP-SERVER-MIB tables would, however, only be populated with one row
indexed by applIndex=1 and applIndex=2, respectively, if the server
...
...
The SIP-COMMON-MIB sipCommonCfgTable might be populated as:
+---------+------------------------+--------------------------+-----+
...
... Proxy and Registrar server, where the two entities share a single
instance of SIP-COMMON-MIB.
The NETWORK ...
... The NETWORK-SERVICES-MIB applTable might be populated as follows:
+-----------+------------------------+------------------------------+
...
...
The SIP-COMMON-MIB sipCommonCfgTable might be populated as:
+----------+---------------------------+-----------------------------+
...
... IMPORTed MIB Modules and REFERENCE Clauses ...
...
The SIP MIB modules defined in this document IMPORT definitions
normatively from the following MIB modules, beyond [RFC2578 ...
... SIP MIB modules defined in this document IMPORT definitions
normatively from the following MIB modules, beyond [RFC2578],
[RFC2579 ...
... RFC3411].
This MIB module also includes REFERENCE clauses that normatively
refer to SIP [RFC3261 ...
... RFC4001].
Finally, this MIB module makes informative references to several RFCs
in some of the examples described in the DESCRIPTION clauses,
including Reliability ...
...
For example, in the sipCommonMethodSupportedTable of SIP-COMMON-MIB,
the sipCommonMethodSupportedName values can be represented as
follows:
...
...
SIP-TC-MIB DEFINITIONS ::= BEGIN
IMPORTS
...
... "Session Initiation Protocol (SIP) MIB TEXTUAL-CONVENTION
module used by other SIP-related MIB Modules ...
... Trust (2007). This version of
this MIB module is part of RFC 4780prop; see the RFC itself for
...
... SIP Common MIB Module ...
...
SIP-COMMON-MIB DEFINITIONS ::= BEGIN
IMPORTS
...
... "Session Initiation Protocol (SIP) Common MIB module. This
module defines objects that may be common to all SIP entities.
...
... 3261prop (June 2002).
This MIB is defined for managing objects that are common to
SIP User Agents (UAs ...
... Objects specific to each of these entities MAY be managed using
entity specific MIBs defined in other modules.
Copyright (C) The IETF ...
... Trust (2007). This version of
this MIB module is part of RFC 4780prop; see the RFC itself for
full legal notices."
...
...
-- Top-Level Components of this MIB.
sipCommonMIBNotifications OBJECT IDENTIFIER ::= { sipCommonMIB 0 }
...
...
--
-- This MIB contains objects that are common to all SIP entities.
--
...
... framework of the NETWORK-SERVICES-MIB (RFC 2788prop)."
INDEX { applIndex, sipCommonOptionTagIndex }
...
... table without any requirement to update this MIB module.
The table is informational in nature and conveys capabilities
...
... framework of the NETWORK-SERVICES-MIB (RFC 2788prop)."
INDEX { applIndex, sipCommonMethodSupportedIndex }
...
... identifier is suitable for referencing the associated
method throughout this and other MIBs supported by this managed
system."
::= { sipCommonMethodSupportedEntry 1 }
...
... framework of the NETWORK-SERVICES-MIB (RFC 2788prop).
The objects in this table entry SHOULD be non-volatile and
...
... framework of the NETWORK-SERVICES-MIB (RFC 2788prop)."
INDEX { applIndex, sipCommonMethodStatsName }
...
... framework of the NETWORK-SERVICES-MIB (RFC 2788prop)."
INDEX { applIndex, sipCommonStatusCodeMethod,
...
... "A collection of accessible-for-notify objects related to the
notification defined in this MIB module."
::= { sipCommonMIBGroups 8 }
...
... SIP User Agent MIB Module ...
... Trust (2007). This version of
this MIB module is part of RFC 4780prop; see the RFC itself for
full legal notices."
...
...
--
-- This MIB contains objects related to SIP User Agents.
--
...
... framework of the NETWORK-SERVICES-MIB
(RFC 2788prop). The same value of applIndex used in the
...
... 2788prop). The same value of applIndex used in the
corresponding SIP-COMMON-MIB is used here."
INDEX { applIndex, sipUACfgServerIndex }
::= { sipUACfgServerTable 1 }
...
... sipUACfgServerAddressType object."
REFERENCE "INET-ADDRESS-MIB (RFC 4001prop)"
::= { sipUACfgServerEntry 3 }
...
... SIP-SERVER-MIB DEFINITIONS ::= BEGIN ...
... Trust (2007). This version of
this MIB module is part of RFC 4780prop; see the RFC itself for
full legal notices."
...
... framework of the NETWORK-SERVICES-MIB (RFC 2788prop).
The same value of applIndex used in the corresponding
...
... The same value of applIndex used in the corresponding
SIP-COMMON-MIB is used here."
INDEX { applIndex }
::= { sipServerCfgTable 1 }
...
... framework of the NETWORK-SERVICES-MIB (RFC 2788prop). The
same value of applIndex used in the corresponding
...
... same value of applIndex used in the corresponding
SIP-COMMON-MIB is used here."
INDEX { applIndex }
::= { sipServerProxyCfgTable 1 }
...
... framework of the NETWORK-SERVICES-MIB (RFC 2788prop). The
same value of applIndex used in the corresponding
...
... same value of applIndex used in the corresponding
SIP-COMMON-MIB is used here."
INDEX { applIndex }
::= { sipServerProxyStatsTable 1 }
...
... framework of the NETWORK-SERVICES-MIB (RFC 2788prop). The
same value of applIndex used in the corresponding
...
... same value of applIndex used in the corresponding
SIP-COMMON-MIB is used here."
INDEX { applIndex }
::= { sipServerRegCfgTable 1 }
...
... framework of the NETWORK-SERVICES-MIB (RFC 2788prop). The
same value of applIndex used in the corresponding
...
... same value of applIndex used in the corresponding
SIP-COMMON-MIB is used here."
INDEX { applIndex, sipServerRegUserIndex }
::= { sipServerRegUserTable 1 }
...
... framework of the NETWORK-SERVICES-MIB (RFC 2788prop). The
same value of applIndex used in the corresponding
...
... same value of applIndex used in the corresponding
SIP-COMMON-MIB is used here."
INDEX { applIndex,
...
... framework of the NETWORK-SERVICES-MIB (RFC 2788prop). The
same value of applIndex used in the corresponding
...
... same value of applIndex used in the corresponding
SIP-COMMON-MIB is used here."
INDEX { applIndex }
::= { sipServerRegStatsTable 1 }
...
... management objects defined in the SIP-COMMON-
MIB MIB module with a MAX-ACCESS clause of read-write ...
... The following read-create object in SIP-COMMON-MIB is used to
configure the status code statistics that will be monitored by the
...
... The following read-write objects in SIP-COMMON-MIB are used to
configure the behavior of certain SNMP notifications ...
... notifications.
Some of the readable objects in the MIB modules (i.e., objects with a
MAX-ACCESS other than not-accessible) may be considered sensitive or
...
... and the sipCommonMethodSupportedTable table contains in the SIP-
COMMON-MIB MIB module list of SIP methods ...
...
In the SIP-SERVER-MIB MIB module, the sipServerCfgProxyAuthMethod
object defines the authentication methods ...
... In the SIP-SERVER-MIB MIB module, the sipServerCfgProxyAuthMethod
object defines the authentication methods supported by the server ...
... SNMP entity giving access to
an instance of this MIB module is properly configured to give access
to the objects only to those principals (users) that have legitimate
...
... SIPPING working
groups, and the SIP-MIB Design team for their comments and
suggestions. Detailed comments were provided by Tom Taylor, Kavitha
Patchayappan, Dan Romascanu, Cullen Jennings, Orit Levin, AC ...
... Dean Willis. Special thanks to Bert Wijnen for his expert reviews,
which have greatly improved the SIP MIB modules.
...