MIB Viewer

MALLOC-MIB

95 objects
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.
OIDNameAccessStatusDescription
1.3.6.1.2.1.101IdentitymallocMIBThe 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; …
1.3.6.1.2.1.101.1NodemallocMIBObjects
1.3.6.1.2.1.101.1.1Nodemalloc
1.3.6.1.2.1.101.1.1.1ScalarmallocCapabilitiesread-onlycurrentThis object describes the capabilities which a client or server supports. The startTime bit indicates that allocations with a future start time are supported. …
1.3.6.1.2.1.101.1.1.2TablemallocScopeTablenot-accessiblecurrentThe (conceptual) table containing information on multicast scopes from which addresses may be allocated. Entries in this table may be dynamically discovered vi…
1.3.6.1.2.1.101.1.1.2.1RowmallocScopeEntrynot-accessiblecurrentAn entry (conceptual row) containing the information on a particular multicast scope.
1.3.6.1.2.1.101.1.1.2.1.1ColumnmallocScopeAddressTypenot-accessiblecurrentThe type of the addresses in the multicast scope range. Legal values correspond to the subset of address families for which multicast address allocation is sup…
1.3.6.1.2.1.101.1.1.2.1.2ColumnmallocScopeFirstAddressnot-accessiblecurrentThe first address in the multicast scope range. The type of this address is determined by the value of the mallocScopeAddressType object.
1.3.6.1.2.1.101.1.1.2.1.3ColumnmallocScopeLastAddressread-createcurrentThe last address in the multicast scope range. The type of this address is determined by the value of the mallocScopeAddressType object.
1.3.6.1.2.1.101.1.1.2.1.4ColumnmallocScopeHopLimitread-createcurrentThe default IPv4 TTL or IPv6 hop limit which applications should use for groups within the scope.
1.3.6.1.2.1.101.1.1.2.1.5ColumnmallocScopeStatusread-createcurrentThe 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 i…
1.3.6.1.2.1.101.1.1.2.1.6ColumnmallocScopeSourceread-onlycurrentThe method by which this entry was learned.
1.3.6.1.2.1.101.1.1.2.1.7ColumnmallocScopeDivisibleread-createcurrentIf 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 allo…
1.3.6.1.2.1.101.1.1.2.1.8ColumnmallocScopeServerAddressTyperead-createcurrentThe type of the address of a multicast address allocation server to which a request may be sent.
1.3.6.1.2.1.101.1.1.2.1.9ColumnmallocScopeServerAddressread-createcurrentThe 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…
1.3.6.1.2.1.101.1.1.2.1.10ColumnmallocScopeSSMread-createcurrentIndicates whether the scope is a Source-Specific Multicast (SSM) range.
1.3.6.1.2.1.101.1.1.2.1.11ColumnmallocScopeStorageread-createcurrentThe storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
1.3.6.1.2.1.101.1.1.3TablemallocScopeNameTablenot-accessiblecurrentThe (conceptual) table containing information on multicast scope names. Entries in this table may be dynamically discovered via some other protocol, such as MZ…
1.3.6.1.2.1.101.1.1.3.1RowmallocScopeNameEntrynot-accessiblecurrentAn entry (conceptual row) containing the information on a particular multicast scope name.
1.3.6.1.2.1.101.1.1.3.1.1ColumnmallocScopeNameLangNamenot-accessiblecurrentThe RFC 3066 language tag for the language of the scope name.
1.3.6.1.2.1.101.1.1.3.1.2ColumnmallocScopeNameScopeNameread-createcurrentThe 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 multic…
1.3.6.1.2.1.101.1.1.3.1.3ColumnmallocScopeNameDefaultread-createcurrentIf 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.
1.3.6.1.2.1.101.1.1.3.1.4ColumnmallocScopeNameStatusread-createcurrentThe 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 i…
1.3.6.1.2.1.101.1.1.3.1.5ColumnmallocScopeNameStorageread-createcurrentThe storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
1.3.6.1.2.1.101.1.1.4TablemallocAllocRangeTablenot-accessiblecurrentThe (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 Prefi…
1.3.6.1.2.1.101.1.1.4.1RowmallocAllocRangeEntrynot-accessiblecurrentAn entry (conceptual row) containing the information on a particular allocation range.
1.3.6.1.2.1.101.1.1.4.1.1ColumnmallocAllocRangeFirstAddressnot-accessiblecurrentThe first address in the allocation range. The type of this address is determined by the value of the mallocScopeAddressType object.
1.3.6.1.2.1.101.1.1.4.1.2ColumnmallocAllocRangeLastAddressread-createcurrentThe last address in the allocation range. The type of this address is determined by the value of the mallocScopeAddressType object.
1.3.6.1.2.1.101.1.1.4.1.3ColumnmallocAllocRangeStatusread-createcurrentThe 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 i…
1.3.6.1.2.1.101.1.1.4.1.4ColumnmallocAllocRangeSourceread-onlycurrentThe means by which this entry was learned.
1.3.6.1.2.1.101.1.1.4.1.5ColumnmallocAllocRangeLifetimeread-createcurrentThe 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 subj…
1.3.6.1.2.1.101.1.1.4.1.6ColumnmallocAllocRangeMaxLeaseAddrsread-createcurrentThe 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 enforc…
1.3.6.1.2.1.101.1.1.4.1.7ColumnmallocAllocRangeMaxLeaseTimeread-createcurrentThe 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 mall…
1.3.6.1.2.1.101.1.1.4.1.8ColumnmallocAllocRangeNumAllocatedAddrsread-onlycurrentThe 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 ran…
1.3.6.1.2.1.101.1.1.4.1.9ColumnmallocAllocRangeNumOfferedAddrsread-onlycurrentThe number of addresses in the range which have been offered. This number should match the sum of mallocRequestNumAddrs for all entries in the mallocRequestTab…
1.3.6.1.2.1.101.1.1.4.1.10ColumnmallocAllocRangeNumWaitingAddrsread-onlycurrentThe number of addresses in the range which have been requested, but whose state is waiting, while the server attempts to acquire more address space.
1.3.6.1.2.1.101.1.1.4.1.11ColumnmallocAllocRangeNumTryingAddrsread-onlycurrentThe number of addresses in the scope covered by entries in the mallocRequestTable in the trying state.
1.3.6.1.2.1.101.1.1.4.1.12ColumnmallocAllocRangeAdvertisableread-createcurrentThe 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 t…
1.3.6.1.2.1.101.1.1.4.1.13ColumnmallocAllocRangeTotalAllocatedAddrsread-onlycurrentThe 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…
1.3.6.1.2.1.101.1.1.4.1.14ColumnmallocAllocRangeTotalRequestedAddrsread-onlycurrentThe 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 …
1.3.6.1.2.1.101.1.1.4.1.15ColumnmallocAllocRangeStorageread-createcurrentThe storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
1.3.6.1.2.1.101.1.1.5TablemallocRequestTablenot-accessiblecurrentThe (conceptual) table containing information on allocation requests, whether allocated or in progress. This table may also be used to determine which clients …
1.3.6.1.2.1.101.1.1.5.1RowmallocRequestEntrynot-accessiblecurrentAn entry (conceptual row) containing the information on a particular allocation request.
1.3.6.1.2.1.101.1.1.5.1.1ColumnmallocRequestIdnot-accessiblecurrentAn arbitrary value identifying this row.
1.3.6.1.2.1.101.1.1.5.1.2ColumnmallocRequestScopeAddressTyperead-onlycurrentThe 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 …
1.3.6.1.2.1.101.1.1.5.1.3ColumnmallocRequestScopeFirstAddressread-onlycurrentThe first address of the scope to which the request applies. This must match mallocScopeFirstAddress for some row in the mallocScopeTable. The type of this add…
1.3.6.1.2.1.101.1.1.5.1.4ColumnmallocRequestStartTimeread-onlycurrentThe number of seconds remaining before the start time of the request. A value of 0 means that the allocation is currently in effect.
1.3.6.1.2.1.101.1.1.5.1.5ColumnmallocRequestEndTimeread-onlycurrentThe number of seconds remaining before the end time of the request.
1.3.6.1.2.1.101.1.1.5.1.6ColumnmallocRequestNumAddrsread-onlycurrentThe number of addresses requested. If the addresses have been allocated, this number should match the total number of addresses for this request covered by ent…
1.3.6.1.2.1.101.1.1.5.1.7ColumnmallocRequestStateread-onlycurrentThe 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…
1.3.6.1.2.1.101.1.1.5.1.8ColumnmallocRequestClientAddressTyperead-onlycurrentThe type of the address of the client that (last) requested this allocation.
1.3.6.1.2.1.101.1.1.5.1.9ColumnmallocRequestClientAddressread-onlycurrentThe address of the client that (last) requested this allocation. The type of this address is determined by the value of the mallocRequestClientAddressType obje…
1.3.6.1.2.1.101.1.1.5.1.10ColumnmallocRequestServerAddressTyperead-onlycurrentThe type of the address of the server to which the request was (last) sent.
1.3.6.1.2.1.101.1.1.5.1.11ColumnmallocRequestServerAddressread-onlycurrentThe address of the server to which the request was (last) sent. The type of this address is determined by the value of the mallocRequestServerAddressType objec…
1.3.6.1.2.1.101.1.1.5.1.12ColumnmallocRequestLeaseIdentifierread-onlycurrentThe Lease Identifier of this request. If the allocation mechanism in use does not use Lease Identifiers, then the value is a 0-length string.
1.3.6.1.2.1.101.1.1.6TablemallocAddressTablenot-accessiblecurrentThe (conceptual) table containing information on blocks of allocated addresses. This table may be used to map a given multicast group address to the associated…
1.3.6.1.2.1.101.1.1.6.1RowmallocAddressEntrynot-accessiblecurrentAn entry (conceptual row) containing the information on a particular block of allocated addresses. The block of addresses covered by each entry in this table m…
1.3.6.1.2.1.101.1.1.6.1.1ColumnmallocAddressAddressTypenot-accessiblecurrentThe type of the first address in the allocated block. Legal values correspond to the subset of address families for which multicast address allocation is suppo…
1.3.6.1.2.1.101.1.1.6.1.2ColumnmallocAddressFirstAddressnot-accessiblecurrentThe first address in the allocated block. The type of this address is determined by the value of the mallocAddressAddressType object.
1.3.6.1.2.1.101.1.1.6.1.3ColumnmallocAddressNumAddrsread-onlycurrentThe number of addresses in the allocated block.
1.3.6.1.2.1.101.1.1.6.1.4ColumnmallocAddressRequestIdread-onlycurrentThe 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 mallocR…
1.3.6.1.2.1.101.1.2Nodemadcap
1.3.6.1.2.1.101.1.2.1IdentitymadcapConfigcurrentGroup of objects that count various MADCAP events.
1.3.6.1.2.1.101.1.2.1.1ScalarmadcapConfigExtraAllocationTimeread-writecurrentThe amount of extra time on either side of a lease which the MADCAP server allocates to allow for clock skew among clients.
1.3.6.1.2.1.101.1.2.1.2ScalarmadcapConfigNoResponseDelayread-writecurrentThe amount of time the MADCAP client allows for receiving a response from a MADCAP server.
1.3.6.1.2.1.101.1.2.1.3ScalarmadcapConfigOfferHoldread-writecurrentThe amount of time the MADCAP server will reserve an address for after sending an OFFER message in anticipation of receiving a REQUEST message.
1.3.6.1.2.1.101.1.2.1.4ScalarmadcapConfigResponseCacheIntervalread-writecurrentThe amount of time the MADCAP server uses to detect duplicate messages.
1.3.6.1.2.1.101.1.2.1.5ScalarmadcapConfigClockSkewAllowanceread-writecurrentThe clock skew threshold used by the MADCAP server to generate Excessive Clock Skew errors.
1.3.6.1.2.1.101.1.2.2IdentitymadcapCounterscurrentA group of objects that count various MADCAP events.
1.3.6.1.2.1.101.1.2.2.1ScalarmadcapTotalErrorsread-onlycurrentThe 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 generat…
1.3.6.1.2.1.101.1.2.2.2ScalarmadcapRequestsDeniedread-onlycurrentThe 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 …
1.3.6.1.2.1.101.1.2.2.3ScalarmadcapInvalidRequestsread-onlycurrentThe number of invalid requests received by the MADCAP server, regardless of whether NAKs were sent. This corresponds to the Invalid Request error code in MADCA…
1.3.6.1.2.1.101.1.2.2.4ScalarmadcapExcessiveClockSkewsread-onlycurrentThe number of requests received by the MADCAP server with an excessive clock skew, regardless of whether NAKs were sent. This corresponds to the Excessive Cloc…
1.3.6.1.2.1.101.1.2.2.5ScalarmadcapBadLeaseIdsread-onlycurrentThe number of requests received by the MADCAP server with an unrecognized Lease Identifier, regardless of whether NAKs were sent. This corresponds to the Lease…
1.3.6.1.2.1.101.1.2.2.6ScalarmadcapDiscoversread-onlycurrentThe number of DISCOVER messages received by the MADCAP server.
1.3.6.1.2.1.101.1.2.2.7ScalarmadcapInformsread-onlycurrentThe number of INFORM messages received by the MADCAP server.
1.3.6.1.2.1.101.1.2.2.8ScalarmadcapRequestsread-onlycurrentThe number of REQUEST messages received by the MADCAP server.
1.3.6.1.2.1.101.1.2.2.9ScalarmadcapRenewsread-onlycurrentThe number of RENEW messages received by the MADCAP server.
1.3.6.1.2.1.101.1.2.2.10ScalarmadcapReleasesread-onlycurrentThe number of RELEASE messages received by the MADCAP server.
1.3.6.1.2.1.101.2NodemallocConformance
1.3.6.1.2.1.101.2.1NodemallocCompliances
1.3.6.1.2.1.101.2.1.1CompliancemallocServerReadOnlyComplianceread-onlycurrentThe compliance statement for multicast address allocation servers implementing the MALLOC MIB without support for read-create (i.e., in read-only mode). Such a…
1.3.6.1.2.1.101.2.1.2CompliancemallocClientReadOnlyComplianceread-onlycurrentThe 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…
1.3.6.1.2.1.101.2.1.3CompliancemallocPrefixCoordinatorReadOnlyComplianceread-onlycurrentThe compliance statement for prefix coordinators implementing the MALLOC MIB without support for read-create (i.e., in read-only mode). Such devices can then b…
1.3.6.1.2.1.101.2.1.4CompliancemallocServerFullCompliancecurrentThe compliance statement for multicast address allocation servers implementing the MALLOC MIB with support for read- create. Such servers can then be both moni…
1.3.6.1.2.1.101.2.1.5CompliancemallocClientFullCompliancecurrentThe compliance statement for hosts implementing the MALLOC MIB with support for read-create. Such clients can then be both monitored and configured with this M…
1.3.6.1.2.1.101.2.1.6CompliancemallocPrefixCoordinatorFullCompliancecurrentThe compliance statement for prefix coordinators implementing the MALLOC MIB with support for read-create. Such devices can then be both monitored and configur…
1.3.6.1.2.1.101.2.2NodemallocGroups
1.3.6.1.2.1.101.2.2.1GroupmallocBasicGroupcurrentThe basic collection of objects providing management of IP multicast address allocation.
1.3.6.1.2.1.101.2.2.2GroupmallocServerGroupcurrentA collection of objects providing management of multicast address allocation in servers.
1.3.6.1.2.1.101.2.2.3GroupmallocClientGroupcurrentA collection of objects providing management of multicast address allocation in clients.
1.3.6.1.2.1.101.2.2.4GroupmadcapServerGroupcurrentA collection of objects providing management of MADCAP servers.
1.3.6.1.2.1.101.2.2.5GroupmadcapClientGroupcurrentA collection of objects providing management of MADCAP clients.
1.3.6.1.2.1.101.2.2.6GroupmallocClientScopeGroupcurrentA collection of objects providing management of multicast scope information in clients.
1.3.6.1.2.1.101.2.2.7GroupmallocPrefixCoordinatorGroupcurrentA collection of objects for managing Prefix Coordinators.