BAS-ALIAS-SNMP-MIB
The BAS-ALIAS-SNMP-MIB module provides SNMP objects for managing and monitoring alias configurations within Broadband Access System clusters, enabling the mapping of logical interface identifiers to physical hardware resources for accurate traffic analysis and device inventory tracking.
Imported Objects
Objects
41 total| Object Name |
|---|
basAliasSnmpMibThis MIB module defines the Alias SNMP MIB objects for a Broadband Access System Cluster. MODULE-IDENTITY .1.3.6.1.4.1.3493.2.7.1.1 |
basSnmp OBJECT IDENTIFIER .1.3.6.1.4.1.3493.2.7.1.1.1 |
basSnmpTablePer Chassis Stack MIB-II system objects. SEQUENCE OF BasSnmpEntry .1.3.6.1.4.1.3493.2.7.1.1.1.1 |
basSnmpEntryMIB-II system objects for a Chassis Stack. BasSnmpEntry .1.3.6.1.4.1.3493.2.7.1.1.1.1.1 |
basSnmpInPktsThe total number of messages delivered to the SNMP entity from the transport service.ro Counter32 .1.3.6.1.4.1.3493.2.7.1.1.1.1.1.1 |
basSnmpInBadVersionsThe total number of SNMP messages which were delivered to the SNMP entity and were for an unsupported SNMP version.ro Counter32 .1.3.6.1.4.1.3493.2.7.1.1.1.1.1.3 |
basSnmpInBadCommunityNamesThe total number of SNMP messages delivered to the SNMP entity which used a SNMP community name not known to said entity.ro Counter32 .1.3.6.1.4.1.3493.2.7.1.1.1.1.1.4 |
basSnmpInBadCommunityUsesThe total number of SNMP messages delivered to the SNMP entity which represented an SNMP operation which was not allowed by the SNMP community named in the message.ro Counter32 .1.3.6.1.4.1.3493.2.7.1.1.1.1.1.5 |
basSnmpInASNParseErrsThe total number of ASN.1 or BER errors encountered by the SNMP entity when decoding received SNMP messages.ro Counter32 .1.3.6.1.4.1.3493.2.7.1.1.1.1.1.6 |
basSnmpEnableAuthenTrapsIndicates whether the SNMP entity is permitted to generate authenticationFailure traps. The value of this object overrides any configuration information; as such, it provides a means whereby all authenticationFailure traps may be disabled. Note that it is strongly recommended that this object be stored in non-volatile memory so that it remains constant across re-initializations of the network management system.rw Enumeration .1.3.6.1.4.1.3493.2.7.1.1.1.1.1.30 |
basSnmpSilentDropsThe total number of GetRequest-PDUs, GetNextRequest-PDUs, GetBulkRequest-PDUs, SetRequest-PDUs, and InformRequest-PDUs delivered to the SNMP entity which were silently dropped because the size of a reply containing an alternate Response-PDU with an empty variable-bindings field was greater than either a local constraint or the maximum message size associated with the originator of the request.ro Counter32 .1.3.6.1.4.1.3493.2.7.1.1.1.1.1.31 |
basSnmpProxyDropsThe total number of GetRequest-PDUs, GetNextRequest-PDUs, GetBulkRequest-PDUs, SetRequest-PDUs, and InformRequest-PDUs delivered to the SNMP entity which were silently dropped because the transmission of the (possibly translated) message to a proxy target failed in a manner (other than a time-out) such that no Response-PDU could be returned.ro Counter32 .1.3.6.1.4.1.3493.2.7.1.1.1.1.1.32 |
basSnmpChassisThe BAS Chassis ID of this card. BasChassisId (BAS-MIB) .1.3.6.1.4.1.3493.2.7.1.1.1.1.1.33 |
basSnmpSlotThe BAS Slot ID of this card. BasSlotId (BAS-MIB) .1.3.6.1.4.1.3493.2.7.1.1.1.1.1.34 |
basSnmpIfThe BAS interface ID of this card. BasInterfaceId (BAS-MIB) .1.3.6.1.4.1.3493.2.7.1.1.1.1.1.35 |
basSnmpLPortThe BAS logical port ID of this card. BasLogicalPortId (BAS-MIB) .1.3.6.1.4.1.3493.2.7.1.1.1.1.1.36 |
basSystem OBJECT IDENTIFIER .1.3.6.1.4.1.3493.2.7.1.1.2 |
basSysTablePer Chassis Stack MIB-II system objects. SEQUENCE OF BasSysEntry .1.3.6.1.4.1.3493.2.7.1.1.2.1 |
basSysEntryMIB-II system objects for a Chassis Stack. BasSysEntry .1.3.6.1.4.1.3493.2.7.1.1.2.1.1 |
basSysDescrA textual description of the entity. This value should include the full name and version identification of the system's hardware type, software operating-system, and networking software.ro DisplayString .1.3.6.1.4.1.3493.2.7.1.1.2.1.1.1 |
basSysObjectIDThe vendor's authoritative identification of the network management subsystem contained in the entity. This value is allocated within the SMI enterprises subtree (1.3.6.1.4.1) and provides an easy and unambiguous means for determining `what kind of box' is being managed. For example, if vendor `Flintstones, Inc.' was assigned the subtree 1.3.6.1.4.1.4242, it could assign the identifier 1.3.6.1.4.1.4242.1.1 to its `Fred Router'.ro OBJECT IDENTIFIER .1.3.6.1.4.1.3493.2.7.1.1.2.1.1.2 |
basSysUpTimeThe time (in hundredths of a second) since the network management portion of the system was last re-initialized.ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.3493.2.7.1.1.2.1.1.3 |
basSysContactThe textual identification of the contact person for this managed node, together with information on how to contact this person. If no contact information is known, the value is the zero-length string.rw DisplayString .1.3.6.1.4.1.3493.2.7.1.1.2.1.1.4 |
basSysNameAn administratively-assigned name for this managed node. By convention, this is the node's fully-qualified domain name. If the name is unknown, the value is the zero-length string.rw DisplayString .1.3.6.1.4.1.3493.2.7.1.1.2.1.1.5 |
basSysLocationThe physical location of this node (e.g., `telephone closet, 3rd floor'). If the location is unknown, the value is the zero-length string.rw DisplayString .1.3.6.1.4.1.3493.2.7.1.1.2.1.1.6 |
basSysServicesA value which indicates the set of services that this entity may potentially offers. The value is a sum. This sum initially takes the value zero, Then, for each layer, L, in the range 1 through 7, that this node performs transactions for, 2 raised to (L - 1) is added to the sum. For example, a node which performs only routing functions would have a value of 4 (2^(3-1)). In contrast, a node which is a host offering application services would have a value of 72 (2^(4-1) + 2^(7-1)). Note that in the context of the Internet suite of protocols, values should be calculated accordingly: layer functionality 1 physical (e.g., repeaters) 2 datalink/subnetwork (e.g., bridges) 3 internet (e.g., supports the IP) 4 end-to-end (e.g., supports the TCP) 7 applications (e.g., supports the SMTP) For systems including OSI protocols, layers 5 and 6 may also be counted.ro INTEGER .1.3.6.1.4.1.3493.2.7.1.1.2.1.1.7 |
basSysORLastChangeThe value of sysUpTime at the time of the most recent change in state or value of any instance of sysORID.ro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.3493.2.7.1.1.2.1.1.8 |
basSysChassisThe BAS Chassis ID of this card. BasChassisId (BAS-MIB) .1.3.6.1.4.1.3493.2.7.1.1.2.1.1.9 |
basSysSlotThe BAS Slot ID of this card. BasSlotId (BAS-MIB) .1.3.6.1.4.1.3493.2.7.1.1.2.1.1.10 |
basSysIfThe BAS interface ID of this card. BasInterfaceId (BAS-MIB) .1.3.6.1.4.1.3493.2.7.1.1.2.1.1.11 |
basSysLPortThe BAS logical port ID of this card. BasLogicalPortId (BAS-MIB) .1.3.6.1.4.1.3493.2.7.1.1.2.1.1.12 |
basSysORTableThe (conceptual) table listing the capabilities of the local SNMPv2 entity acting in an agent role with respect to various MIB modules. SNMPv2 entities having dynamically- configurable support of MIB modules will have a dynamically-varying number of conceptual rows. SEQUENCE OF BasSysOREntry .1.3.6.1.4.1.3493.2.7.1.1.2.2 |
basSysOREntryAn entry (conceptual row) in the basSysORTable. BasSysOREntry .1.3.6.1.4.1.3493.2.7.1.1.2.2.1 |
basSysORIndexThe auxiliary variable used for identifying instances of the columnar objects in the basSysORTable. INTEGER .1.3.6.1.4.1.3493.2.7.1.1.2.2.1.1 |
basSysORIDAn authoritative identification of a capabilities statement with respect to various MIB modules supported by the local SNMPv2 entity acting in an agent role.ro OBJECT IDENTIFIER .1.3.6.1.4.1.3493.2.7.1.1.2.2.1.2 |
basSysORDescrA textual description of the capabilities identified by the corresponding instance of basSysORID.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.3493.2.7.1.1.2.2.1.3 |
basSysORUpTimeThe value of basSysUpTime at the time this conceptual row was last instanciated.ro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.3493.2.7.1.1.2.2.1.4 |
basSysORChassisThe BAS Chassis ID of this card. BasChassisId (BAS-MIB) .1.3.6.1.4.1.3493.2.7.1.1.2.2.1.5 |
basSysORSlotThe BAS Slot ID of this card. BasSlotId (BAS-MIB) .1.3.6.1.4.1.3493.2.7.1.1.2.2.1.6 |
basSysORIfThe BAS interface ID of this card. BasInterfaceId (BAS-MIB) .1.3.6.1.4.1.3493.2.7.1.1.2.2.1.7 |
basSysORLPortThe BAS logical port ID of this card. BasLogicalPortId (BAS-MIB) .1.3.6.1.4.1.3493.2.7.1.1.2.2.1.8 |
More MIBs from Broadband Access
Browse all Broadband AccessMIBs →The BAS-CMTS-CONFIG-MIB provides SNMP-manageable configuration parameters for Cable Modem Termination Systems (CMTS) within DOCSIS-based broadband access networks, enabling the remote administration of interface settings, channel profiles, and MAC-layer operational states. This module facilitates the centralized provisioning and modification of CMTS subsystems to ensure consistent service delivery and network topology alignment across the cable infrastructure.
The BAS-OSPF-MIB module provides management objects for monitoring and configuring Open Shortest Path First (OSPF) routing instances within the IP forwarding subsystem of Broadband Access Systems. It enables the tracking of OSPF neighbor adjacencies, interface states, and routing table metrics to ensure reliable Layer 3 connectivity across broadband aggregation networks.
The AATS-MIB provides SNMP management capabilities for the BATS (Business Application Traffic System) software suite, enabling monitoring of application session states, traffic throughput, and protocol-specific performance counters. This module facilitates the collection of operational metrics required for troubleshooting BATS service availability and analyzing data flow patterns within the managed network environment.
The BAS-ALIAS-CABLE-DEVICE-MIB provides standard OID definitions for mapping and managing alias attributes of Cable Modem Termination System (CMTS) and Docsis Cable Device interfaces within a Broadband Access System cluster. It enables network management systems to correlate logical device identifiers with physical hardware components for precise fault isolation and configuration tracking in DOCSIS-based cable networks.
The BAS-PBRF-RIP-MIB module enables management of Broadband Access Systems, Inc. routers to configure and monitor Route Information Protocol (RIP) export policies and associated route filtering rules. It provides access to configuration parameters governing how routing updates are selectively advertised to neighboring RIP peers based on defined filter criteria.
The BAS-PBRF-OSPF-MIB module manages OSPF-based policy-based routing (PBR) filters on Broadband Access Systems, Inc. hardware, enabling the configuration and monitoring of route selection policies that override standard OSPF forwarding decisions.