MALLOC-MIB
AI MIB Summary
The MALLOC-MIB monitors multicast address allocation states and conflicts within network devices to ensure the integrity of IP multicast group assignments. It tracks specific metrics including allocated multicast addresses, allocation status, and conflict detection events to prevent address collisions during dynamic group management.
The MIB module for management of multicast address allocation. Copyright (C) The Internet Society (2003). This version of this MIB module is part of RFC 3559; see the RFC itself for full legal notices.
Main OID:
mallocMIB.1.3.6.1.2.1.101
95
Objects
Active
Status
7
Dependencies
Imported Objects
Objects
95 total| Object Name |
|---|
mallocMIBThe MIB module for management of multicast address allocation. Copyright (C) The Internet Society (2003). This version of this MIB module is part of RFC 3559; see the RFC itself for full legal notices. MODULE-IDENTITY .1.3.6.1.2.1.101 |
mallocMIBObjects OBJECT IDENTIFIER .1.3.6.1.2.1.101.1 |
malloc OBJECT IDENTIFIER .1.3.6.1.2.1.101.1.1 |
mallocCapabilitiesThis object describes the capabilities which a client or server supports. The startTime bit indicates that allocations with a future start time are supported. The serverMobility bit indicates that allocations can be renewed or released from a server other than the one granting the original allocation. The retryAfter bit indicates support for a waiting state where the client may check back at a later time to get the status of its request.ro Bits .1.3.6.1.2.1.101.1.1.1 |
mallocScopeTableThe (conceptual) table containing information on multicast scopes from which addresses may be allocated. Entries in this table may be dynamically discovered via some other protocol, such as MZAP, or may be statically configured, such as in an isolated network environment. Each scope is associated with a range of multicast addresses, and ranges for different rows must be disjoint. SEQUENCE OF MallocScopeEntry .1.3.6.1.2.1.101.1.1.2 |
mallocScopeEntryAn entry (conceptual row) containing the information on a particular multicast scope. MallocScopeEntry .1.3.6.1.2.1.101.1.1.2.1 |
mallocScopeAddressTypeThe type of the addresses in the multicast scope range. Legal values correspond to the subset of address families for which multicast address allocation is supported. InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.2.1.101.1.1.2.1.1 |
mallocScopeFirstAddressThe first address in the multicast scope range. The type of this address is determined by the value of the mallocScopeAddressType object. InetAddress .1.3.6.1.2.1.101.1.1.2.1.2 |
mallocScopeLastAddressThe last address in the multicast scope range. The type of this address is determined by the value of the mallocScopeAddressType object.rw InetAddress .1.3.6.1.2.1.101.1.1.2.1.3 |
mallocScopeHopLimitThe default IPv4 TTL or IPv6 hop limit which applications should use for groups within the scope.rw Unsigned32 .1.3.6.1.2.1.101.1.1.2.1.4 |
mallocScopeStatusThe status of this row, by which new entries may be created, or old entries deleted from this table. If write access is supported, the other writable objects in this table may be modified even while the status is `active'.rw RowStatus (SNMPv2-TC) .1.3.6.1.2.1.101.1.1.2.1.5 |
mallocScopeSourceThe method by which this entry was learned.ro IANAscopeSource (IANA-MALLOC-MIB) .1.3.6.1.2.1.101.1.1.2.1.6 |
mallocScopeDivisibleIf false, the server may allocate addresses out of the entire range. If true, the server must not allocate addresses out of the entire range, but may only allocate addresses out of a subrange learned via another method. Creating or deleting a scope which is not divisible has the side effect of creating or deleting the corresponding entry in the mallocAllocRangeTable. Deleting a scope which is divisible has the side effect of deleting any corresponding entries in the mallocAllocRangeTable, and the mallocRequestTable.rw TruthValue (SNMPv2-TC) .1.3.6.1.2.1.101.1.1.2.1.7 |
mallocScopeServerAddressTypeThe type of the address of a multicast address allocation server to which a request may be sent.rw InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.2.1.101.1.1.2.1.8 |
mallocScopeServerAddressThe address of a multicast address allocation server to which a request may be sent. The default value is an zero- length address, indicating that no server is known. The type of this address is determined by the value of the mallocScopeServerAddressType object.rw InetAddress (INET-ADDRESS-MIB) .1.3.6.1.2.1.101.1.1.2.1.9 |
mallocScopeSSMIndicates whether the scope is a Source-Specific Multicast (SSM) range.rw TruthValue (SNMPv2-TC) .1.3.6.1.2.1.101.1.1.2.1.10 |
mallocScopeStorageThe storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.rw StorageType (SNMPv2-TC) .1.3.6.1.2.1.101.1.1.2.1.11 |
mallocScopeNameTableThe (conceptual) table containing information on multicast scope names. Entries in this table may be dynamically discovered via some other protocol, such as MZAP, or may be statically configured, such as in an isolated network environment. SEQUENCE OF MallocScopeNameEntry .1.3.6.1.2.1.101.1.1.3 |
mallocScopeNameEntryAn entry (conceptual row) containing the information on a particular multicast scope name. MallocScopeNameEntry .1.3.6.1.2.1.101.1.1.3.1 |
mallocScopeNameLangNameThe RFC 3066 language tag for the language of the scope name. LanguageTag .1.3.6.1.2.1.101.1.1.3.1.1 |
mallocScopeNameScopeNameThe textual name associated with the multicast scope. The value of this object should be suitable for displaying to end-users, such as when allocating a multicast address in this scope. If the scope is an IPv4 scope, and no name is specified, the default value of this object should be the string 239.x.x.x/y with x and y replaced appropriately to describe the address and mask length associated with the scope. If the scope is an IPv6 scope, and no name is specified, the default value of this object should generically describe the scope level (e.g., site).rw SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.2.1.101.1.1.3.1.2 |
mallocScopeNameDefaultIf true, indicates a preference that the name in the associated language should be used by applications if no name is available in a desired language.rw TruthValue (SNMPv2-TC) .1.3.6.1.2.1.101.1.1.3.1.3 |
mallocScopeNameStatusThe status of this row, by which new entries may be created, or old entries deleted from this table. If write access is supported, the other writable objects in this table may be modified even while the status is `active'.rw RowStatus (SNMPv2-TC) .1.3.6.1.2.1.101.1.1.3.1.4 |
mallocScopeNameStorageThe storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.rw StorageType (SNMPv2-TC) .1.3.6.1.2.1.101.1.1.3.1.5 |
mallocAllocRangeTableThe (conceptual) table containing information on subranges of addresses from which the device may allocate addresses, if it is a MAAS. If the device is a Prefix Coordinator, any ranges which the device is advertising to MAAS's will be in this table. Note that the device may be both a MAAS and a Prefix Coordinator. Address ranges for different rows must be disjoint, and must be contained with the address range of the corresponding row of the mallocScopeTable. Deleting an allocation range has the side effect of deleting any entries within that range from the mallocAddressTable. SEQUENCE OF MallocAllocRangeEntry .1.3.6.1.2.1.101.1.1.4 |
mallocAllocRangeEntryAn entry (conceptual row) containing the information on a particular allocation range. MallocAllocRangeEntry .1.3.6.1.2.1.101.1.1.4.1 |
mallocAllocRangeFirstAddressThe first address in the allocation range. The type of this address is determined by the value of the mallocScopeAddressType object. InetAddress .1.3.6.1.2.1.101.1.1.4.1.1 |
mallocAllocRangeLastAddressThe last address in the allocation range. The type of this address is determined by the value of the mallocScopeAddressType object.rw InetAddress .1.3.6.1.2.1.101.1.1.4.1.2 |
mallocAllocRangeStatusThe status of this row, by which new entries may be created, or old entries deleted from this table. If write access is supported, the other writable objects in this table may be modified even while the status is `active'.rw RowStatus (SNMPv2-TC) .1.3.6.1.2.1.101.1.1.4.1.3 |
mallocAllocRangeSourceThe means by which this entry was learned.ro IANAmallocRangeSource (IANA-MALLOC-MIB) .1.3.6.1.2.1.101.1.1.4.1.4 |
mallocAllocRangeLifetimeThe number of seconds remaining in the lifetime of the (sub)range out of which addresses are being allocated. A value of 0 indicates that the range is not subject to aging.rw Unsigned32 UNITS "seconds" .1.3.6.1.2.1.101.1.1.4.1.5 |
mallocAllocRangeMaxLeaseAddrsThe maximum number of addresses which the server is willing to grant for each future request in this range. A value of 0 means that no specific limit is enforced, as long as the server has valid addresses to allocate.rw Unsigned32 .1.3.6.1.2.1.101.1.1.4.1.6 |
mallocAllocRangeMaxLeaseTimeThe maximum lifetime which the server will grant for future requests in this range. A value of 0 means that no additional limit is enforced beyond that of mallocAllocRangeLifetime.rw Unsigned32 UNITS "seconds" .1.3.6.1.2.1.101.1.1.4.1.7 |
mallocAllocRangeNumAllocatedAddrsThe number of addresses in the range which have been allocated. This value can be used to determine the current address space utilization within the scoped range. This should match the total number of addresses for this scope covered by entries in the mallocAddressTable.ro Gauge32 .1.3.6.1.2.1.101.1.1.4.1.8 |
mallocAllocRangeNumOfferedAddrsThe number of addresses in the range which have been offered. This number should match the sum of mallocRequestNumAddrs for all entries in the mallocRequestTable in the offered state. Together with mallocAllocRangeNumAllocatedAddrs and mallocAllocRangeNumTryingAddrs, this can be used to determine the address space utilization within the scoped range in the immediate future.ro Gauge32 .1.3.6.1.2.1.101.1.1.4.1.9 |
mallocAllocRangeNumWaitingAddrsThe number of addresses in the range which have been requested, but whose state is waiting, while the server attempts to acquire more address space.ro Gauge32 .1.3.6.1.2.1.101.1.1.4.1.10 |
mallocAllocRangeNumTryingAddrsThe number of addresses in the scope covered by entries in the mallocRequestTable in the trying state.ro Gauge32 .1.3.6.1.2.1.101.1.1.4.1.11 |
mallocAllocRangeAdvertisableThe value of this object is true if the range is eligible to be advertised to other MAASs. When the row is first created, the default value of this object is true if the scope is divisible, and is false otherwise.rw TruthValue (SNMPv2-TC) .1.3.6.1.2.1.101.1.1.4.1.12 |
mallocAllocRangeTotalAllocatedAddrsThe approximate number of addresses in the range which have been allocated by any MAAS, as determined by a Prefix Coordinator. This object need only be present if mallocAllocRangeAdvertisable is true. If the number is unknown, a value of 0 may be reported.ro Gauge32 .1.3.6.1.2.1.101.1.1.4.1.13 |
mallocAllocRangeTotalRequestedAddrsThe approximate number of addresses in the range for which there is potential demand among MAASs, as determined by a Prefix Coordinator. This object need only be present if mallocAllocRangeAdvertisable is true. If the number is unknown, a value of 0 may be reported.ro Gauge32 .1.3.6.1.2.1.101.1.1.4.1.14 |
mallocAllocRangeStorageThe storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.rw StorageType (SNMPv2-TC) .1.3.6.1.2.1.101.1.1.4.1.15 |
mallocRequestTableThe (conceptual) table containing information on allocation requests, whether allocated or in progress. This table may also be used to determine which clients are responsible for high address space utilization within a given scope. Entries in this table reflect requests dynamically received by an address allocation protocol. SEQUENCE OF MallocRequestEntry .1.3.6.1.2.1.101.1.1.5 |
mallocRequestEntryAn entry (conceptual row) containing the information on a particular allocation request. MallocRequestEntry .1.3.6.1.2.1.101.1.1.5.1 |
mallocRequestIdAn arbitrary value identifying this row. Unsigned32 .1.3.6.1.2.1.101.1.1.5.1.1 |
mallocRequestScopeAddressTypeThe type of the first address of the scope to which the request applies. Legal values correspond to the subset of address families for which multicast address allocation is supported.ro InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.2.1.101.1.1.5.1.2 |
mallocRequestScopeFirstAddressThe first address of the scope to which the request applies. This must match mallocScopeFirstAddress for some row in the mallocScopeTable. The type of this address is determined by the value of the mallocRequestScopeAddressType object.ro InetAddress (INET-ADDRESS-MIB) .1.3.6.1.2.1.101.1.1.5.1.3 |
mallocRequestStartTimeThe number of seconds remaining before the start time of the request. A value of 0 means that the allocation is currently in effect.ro Unsigned32 UNITS "seconds" .1.3.6.1.2.1.101.1.1.5.1.4 |
mallocRequestEndTimeThe number of seconds remaining before the end time of the request.ro Unsigned32 UNITS "seconds" .1.3.6.1.2.1.101.1.1.5.1.5 |
mallocRequestNumAddrsThe number of addresses requested. If the addresses have been allocated, this number should match the total number of addresses for this request covered by entries in the mallocAddressTable.ro Unsigned32 .1.3.6.1.2.1.101.1.1.5.1.6 |
mallocRequestStateThe state of the request. A value of allocated(1) indicates that one or more entries for this request are present in the mallocAddressTable. A value of offered(2) indicates that addresses have been offered to the client (e.g. via a MADCAP OFFER message), but the allocation has not been committed. A value of waiting(3) indicates that the allocation is blocked while the server attempts to acquire more space from which it can allocate addresses. A value of trying(4) means that no addresses have been offered to the client, but that an attempt to allocate is in progress.ro Enumeration .1.3.6.1.2.1.101.1.1.5.1.7 |
mallocRequestClientAddressTypeThe type of the address of the client that (last) requested this allocation.ro InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.2.1.101.1.1.5.1.8 |
mallocRequestClientAddressThe address of the client that (last) requested this allocation. The type of this address is determined by the value of the mallocRequestClientAddressType object.ro InetAddress (INET-ADDRESS-MIB) .1.3.6.1.2.1.101.1.1.5.1.9 |
mallocRequestServerAddressTypeThe type of the address of the server to which the request was (last) sent.ro InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.2.1.101.1.1.5.1.10 |
mallocRequestServerAddressThe address of the server to which the request was (last) sent. The type of this address is determined by the value of the mallocRequestServerAddressType object.ro InetAddress (INET-ADDRESS-MIB) .1.3.6.1.2.1.101.1.1.5.1.11 |
mallocRequestLeaseIdentifierThe Lease Identifier of this request. If the allocation mechanism in use does not use Lease Identifiers, then the value is a 0-length string.ro OCTET STRING .1.3.6.1.2.1.101.1.1.5.1.12 |
mallocAddressTableThe (conceptual) table containing information on blocks of allocated addresses. This table may be used to map a given multicast group address to the associated request. SEQUENCE OF MallocAddressEntry .1.3.6.1.2.1.101.1.1.6 |
mallocAddressEntryAn entry (conceptual row) containing the information on a particular block of allocated addresses. The block of addresses covered by each entry in this table must fall within a range corresponding to an entry in the mallocAllocRangeTable. MallocAddressEntry .1.3.6.1.2.1.101.1.1.6.1 |
mallocAddressAddressTypeThe type of the first address in the allocated block. Legal values correspond to the subset of address families for which multicast address allocation is supported. InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.2.1.101.1.1.6.1.1 |
mallocAddressFirstAddressThe first address in the allocated block. The type of this address is determined by the value of the mallocAddressAddressType object. InetAddress .1.3.6.1.2.1.101.1.1.6.1.2 |
mallocAddressNumAddrsThe number of addresses in the allocated block.ro Unsigned32 .1.3.6.1.2.1.101.1.1.6.1.3 |
mallocAddressRequestIdThe index of the request which caused this block of addresses to be allocated. This value must match the value of mallocRequestId for some entry in the mallocRequestTable.ro Unsigned32 .1.3.6.1.2.1.101.1.1.6.1.4 |
madcap OBJECT IDENTIFIER .1.3.6.1.2.1.101.1.2 |
madcapConfigGroup of objects that count various MADCAP events. OBJECT IDENTIFIER .1.3.6.1.2.1.101.1.2.1 |
madcapConfigExtraAllocationTimeThe amount of extra time on either side of a lease which the MADCAP server allocates to allow for clock skew among clients.rw Unsigned32 UNITS "seconds" .1.3.6.1.2.1.101.1.2.1.1 |
madcapConfigNoResponseDelayThe amount of time the MADCAP client allows for receiving a response from a MADCAP server.rw Unsigned32 UNITS "seconds" .1.3.6.1.2.1.101.1.2.1.2 |
madcapConfigOfferHoldThe amount of time the MADCAP server will reserve an address for after sending an OFFER message in anticipation of receiving a REQUEST message.rw Unsigned32 UNITS "seconds" .1.3.6.1.2.1.101.1.2.1.3 |
madcapConfigResponseCacheIntervalThe amount of time the MADCAP server uses to detect duplicate messages.rw Unsigned32 .1.3.6.1.2.1.101.1.2.1.4 |
madcapConfigClockSkewAllowanceThe clock skew threshold used by the MADCAP server to generate Excessive Clock Skew errors.rw Unsigned32 UNITS "seconds" .1.3.6.1.2.1.101.1.2.1.5 |
madcapCountersA group of objects that count various MADCAP events. OBJECT IDENTIFIER .1.3.6.1.2.1.101.1.2.2 |
madcapTotalErrorsThe total number of transactions for which the MADCAP server has detected an error of any type, regardless of whether the server ignored the request or generated a NAK.ro Counter32 .1.3.6.1.2.1.101.1.2.2.1 |
madcapRequestsDeniedThe number of valid requests for which the MADCAP server could not complete an allocation, regardless of whether NAKs were sent. This corresponds to the Valid Request Could Not Be Completed error code in MADCAP.ro Counter32 .1.3.6.1.2.1.101.1.2.2.2 |
madcapInvalidRequestsThe number of invalid requests received by the MADCAP server, regardless of whether NAKs were sent. This corresponds to the Invalid Request error code in MADCAP.ro Counter32 .1.3.6.1.2.1.101.1.2.2.3 |
madcapExcessiveClockSkewsThe number of requests received by the MADCAP server with an excessive clock skew, regardless of whether NAKs were sent. This corresponds to the Excessive Clock Skew error code in MADCAP.ro Counter32 .1.3.6.1.2.1.101.1.2.2.4 |
madcapBadLeaseIdsThe number of requests received by the MADCAP server with an unrecognized Lease Identifier, regardless of whether NAKs were sent. This corresponds to the Lease Identifier Not Recognized error code in MADCAP.ro Counter32 .1.3.6.1.2.1.101.1.2.2.5 |
madcapDiscoversThe number of DISCOVER messages received by the MADCAP server.ro Counter32 .1.3.6.1.2.1.101.1.2.2.6 |
madcapInformsThe number of INFORM messages received by the MADCAP server.ro Counter32 .1.3.6.1.2.1.101.1.2.2.7 |
madcapRequestsThe number of REQUEST messages received by the MADCAP server.ro Counter32 .1.3.6.1.2.1.101.1.2.2.8 |
madcapRenewsThe number of RENEW messages received by the MADCAP server.ro Counter32 .1.3.6.1.2.1.101.1.2.2.9 |
madcapReleasesThe number of RELEASE messages received by the MADCAP server.ro Counter32 .1.3.6.1.2.1.101.1.2.2.10 |
mallocConformance OBJECT IDENTIFIER .1.3.6.1.2.1.101.2 |
mallocCompliances OBJECT IDENTIFIER .1.3.6.1.2.1.101.2.1 |
mallocServerReadOnlyComplianceThe compliance statement for multicast address allocation servers implementing the MALLOC MIB without support for read-create (i.e., in read-only mode). Such a server can then be monitored but can not be configured with this MIB. Unknown .1.3.6.1.2.1.101.2.1.1 |
mallocClientReadOnlyComplianceThe compliance statement for clients implementing the MALLOC MIB without support for read-create (i.e., in read- only mode). Such clients can then be monitored but can not be configured with this MIB. Unknown .1.3.6.1.2.1.101.2.1.2 |
mallocPrefixCoordinatorReadOnlyComplianceThe compliance statement for prefix coordinators implementing the MALLOC MIB without support for read-create (i.e., in read-only mode). Such devices can then be monitored but can not be configured with this MIB. Unknown .1.3.6.1.2.1.101.2.1.3 |
mallocServerFullComplianceThe compliance statement for multicast address allocation servers implementing the MALLOC MIB with support for read- create. Such servers can then be both monitored and configured with this MIB. Unknown .1.3.6.1.2.1.101.2.1.4 |
mallocClientFullComplianceThe compliance statement for hosts implementing the MALLOC MIB with support for read-create. Such clients can then be both monitored and configured with this MIB. Unknown .1.3.6.1.2.1.101.2.1.5 |
mallocPrefixCoordinatorFullComplianceThe compliance statement for prefix coordinators implementing the MALLOC MIB with support for read-create. Such devices can then be both monitored and configured with this MIB. Unknown .1.3.6.1.2.1.101.2.1.6 |
mallocGroups OBJECT IDENTIFIER .1.3.6.1.2.1.101.2.2 |
mallocBasicGroupThe basic collection of objects providing management of IP multicast address allocation. Unknown .1.3.6.1.2.1.101.2.2.1 |
mallocServerGroupA collection of objects providing management of multicast address allocation in servers. Unknown .1.3.6.1.2.1.101.2.2.2 |
mallocClientGroupA collection of objects providing management of multicast address allocation in clients. Unknown .1.3.6.1.2.1.101.2.2.3 |
madcapServerGroupA collection of objects providing management of MADCAP servers. Unknown .1.3.6.1.2.1.101.2.2.4 |
madcapClientGroupA collection of objects providing management of MADCAP clients. Unknown .1.3.6.1.2.1.101.2.2.5 |
mallocClientScopeGroupA collection of objects providing management of multicast scope information in clients. Unknown .1.3.6.1.2.1.101.2.2.6 |
mallocPrefixCoordinatorGroupA collection of objects for managing Prefix Coordinators. Unknown .1.3.6.1.2.1.101.2.2.7 |