APPIAN-SERVICES-MIB
AI MIB Summary
The APPIAN-SERVICES-MIB provides SNMP definitions for monitoring and managing Appian Communications OSAP hardware, specifically tracking the operational status and configuration parameters of Internet Access (IAS) and Transparent LAN (TLS) services.
Appian Communications OSAP Services MIB contain the definitions for Internet Access (IAS) and Transparent LAN (TLS) services.
Main OID:
acServicesCommon.1.3.6.1.4.1.2785.2.8.1
81
Objects
Active
Status
4
Dependencies
Imported Objects
Objects
81 total| Object Name |
|---|
acServiceTraps OBJECT IDENTIFIER .1.3.6.1.4.1.2785.2.8.0 |
acServiceUpTrapThis trap indicates a service has become active. NOTIFICATION-TYPE .1.3.6.1.4.1.2785.2.8.0.1 |
acServiceDownTrapThis trap indicates a service has become deactivated. The detailed code indicates the reason why NOTIFICATION-TYPE .1.3.6.1.4.1.2785.2.8.0.2 |
acServicesCommonAppian Communications OSAP Services MIB contain the definitions for Internet Access (IAS) and Transparent LAN (TLS) services. MODULE-IDENTITY .1.3.6.1.4.1.2785.2.8.1 |
acServiceTableThis table is the common thread of all services, regardless of service types, in other words, every service would have an entry in this table. A service is identified by a tuple of {node, slot, port, channel}. The {slot, port} pair identies the access port of a subscriber. The port can support multiple services, and each such service is identified by a 'service channel'. To create a service, a row should be created in this table. When the service type is set, a row is automatically 'created' in the appropriate service type specific table. For example, to create an IAS service, one first creates a row in this common table, and then set acServiceType to IAS (which triggers the automatic creation of an entry in the IAS service table), and then set the all necessary parameters. To remove a service, remove the row in this common table only. SEQUENCE OF AcServiceEntry .1.3.6.1.4.1.2785.2.8.1.1 |
acServiceEntryA row equates to a service defined on a particular port and channel. AcServiceEntry .1.3.6.1.4.1.2785.2.8.1.1.1 |
acServiceNodeIdA unique node identification number assigned by the EMS to uniquely identify a node within an Appian Ring.ro AcNodeId (APPIAN-SMI-MIB) .1.3.6.1.4.1.2785.2.8.1.1.1.1 |
acServiceSlotThe slot number within the chassis where the physical i/o port can be found for customer access.ro AcSlotNumber (APPIAN-SMI-MIB) .1.3.6.1.4.1.2785.2.8.1.1.1.2 |
acServicePortThe port number ranging from (1..8) where the physical i/o connection for this customer service can be found.ro AcPortNumber (APPIAN-SMI-MIB) .1.3.6.1.4.1.2785.2.8.1.1.1.3 |
acServiceChannelThe service channel amongst the potentially multiple service channels on a data access port. If only one service channel is provisioned, this channel number should be a value of 1. If multiple service channels are provisioned, the channel number should follow the ranges described below. If multiple service channels are provisioned,each channel maps to a unique 802.1q VLAN tag used to effectively channalize the Ethernet. 4 service channels (1..4) are supported on the 100baseX Ethernet access board. 255 service channels (1..255) are supported on the Gigabit, 1000baseX, Ethernet access board.ro INTEGER .1.3.6.1.4.1.2785.2.8.1.1.1.4 |
acServiceAdminStatusThe administrative or desired status.rw AcAdminStatus (APPIAN-SMI-MIB) .1.3.6.1.4.1.2785.2.8.1.1.1.5 |
acServiceOpStatusThe operational or actual status.ro AcOpStatus (APPIAN-SMI-MIB) .1.3.6.1.4.1.2785.2.8.1.1.1.6 |
acServiceTypeSpecifies the service type. Each row in this table has an associated row in one of the service type specific tables. This object indicates which table, IAS or TLS, has a row at the same index containing additional parameters associated with this service.rw Enumeration .1.3.6.1.4.1.2785.2.8.1.1.1.7 |
acServiceVlanIdThe VLAN ID attribute is only used when the enetEnableMultiService flag has been set to true. The VLAN ID is a 12-bit VLAN ID and is used when the OSAP is processing packets to differentiate between the four service channels. This object must set if an access port supports multiple services. VLAN ID is a 12-bit value and therefore the value range is 0 to 4095. However value 0 is not a VLAN ID per se, but rather a value indicating VLAN tagging is not used.rw INTEGER .1.3.6.1.4.1.2785.2.8.1.1.1.8 |
acServiceTrunkNumberIdentifies the trunk over which this access service is to be carried onto the network. Maps to a row in the trunk table.rw INTEGER .1.3.6.1.4.1.2785.2.8.1.1.1.9 |
acServiceQosTemplateThis object specifies the QOS template to use. A QOS template dictates the QOS model assigned to this subscriber service. If zero(0), no differentiation is done and packets flow through a single queue.rw INTEGER .1.3.6.1.4.1.2785.2.8.1.1.1.10 |
acServiceGBRThe guaranteed bit rate in 1-kpbs increments. On the access side of the service, It should not exceed the maximum bandwidth of the access port. On the network side, the sum of GBR's of all the services carried by a trunk should not exceed the trunk capacity. **NOADMINDOWN**rw INTEGER .1.3.6.1.4.1.2785.2.8.1.1.1.11 |
acServiceMBRThe maximum bit rate in 1-kbps increments. A service may burst up to this rate, but there is no guarantee to the data transmitted above the GBR. The MBR should not exceed the access port capacity nor the trunk capacity. **NOADMINDOWN**rw INTEGER .1.3.6.1.4.1.2785.2.8.1.1.1.12 |
acServiceResetStatsSetting this varible to TRUE causes all service statistics counters to reset. This variable always return FALSE as its value.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.2785.2.8.1.1.1.13 |
acServiceUpstreamBuffCapWeightThe weight associated with the upstream traffic on this service relating to buffering capacity. Upstream traffic is defined as traffic that enters the system from an access port and exits the system on a trunk. A value of 1 provides the least amount of buffering capacity while a value of 10 provides the most buffering capacity. This value is relative in that the number of buffers actually assigned to the upstream traffic depends on how many services share the buffer pool associated with this service.rw Unsigned32 .1.3.6.1.4.1.2785.2.8.1.1.1.14 |
acServiceDownstreamBuffCapWeightThe weight associated with the downstream traffic on this service relating to buffering capacity. Downstream traffic is defined as traffic that enters the system from a trunk and exits the system on an access port. A value of 1 provides the least amount of buffering capacity while a value of 10 provides the most buffering capacity. This value is relative in that the number of buffers actually assigned to the downstream traffic depends on how many services share the buffer pool associated with this service.rw Unsigned32 .1.3.6.1.4.1.2785.2.8.1.1.1.15 |
acServiceLocalBuffCapWeightThe weight associated with local traffic on this service relating to buffering capacity. Local traffic is defined as traffic which enters the system on an access port and exits the system on an access port. This value is therefore only relevant for transparent LAN services with multiple local access ports. This value is relative in that the number of buffers actually assigned to the local traffic depends on how many services share the buffer pool associated with this service.rw Unsigned32 .1.3.6.1.4.1.2785.2.8.1.1.1.16 |
acServiceBufferPoolThe buffer pool associated with this service. The default is 1 which indicates the default buffer pool will be used. The value 0 is not allowed and values greater than 1 are user defined buffer pools.rw Unsigned32 .1.3.6.1.4.1.2785.2.8.1.1.1.17 |
acQosTableTable of QOS templates. SEQUENCE OF AcQosEntry .1.3.6.1.4.1.2785.2.8.1.2 |
acQosEntryA row in the QOS template table. AcQosEntry .1.3.6.1.4.1.2785.2.8.1.2.1 |
acQosNodeIdA unique node identification number assigned by the EMS to uniquely identify a node within an Appian Ring.ro AcNodeId (APPIAN-SMI-MIB) .1.3.6.1.4.1.2785.2.8.1.2.1.1 |
acQosTemplateNumberA number identifies a QOS template. Also used as the index into the QOS template table.ro INTEGER .1.3.6.1.4.1.2785.2.8.1.2.1.2 |
acQosAdminStatusThe administrative status.rw AcAdminStatus (APPIAN-SMI-MIB) .1.3.6.1.4.1.2785.2.8.1.2.1.3 |
acQosTemplateNameA textual string solely for easy identification of a template.rw DisplayString .1.3.6.1.4.1.2785.2.8.1.2.1.4 |
acQosQueueWeightsThe weighted values control relative bandwidth for each queue of the four queues. Each byte represents the proportional weight out of 100 for a queue. The sum of these bytes must equal to 100. For example, if 2 queues are used, and the relative weights (or priorities) are 90 and 10, then acQosQueueWeights should be set to '\0x5A\0x0A\0x00\0x00'.rw AcQueueWeights .1.3.6.1.4.1.2785.2.8.1.2.1.5 |
acQosClassMappingThe object identifies a row in the classification mapping table.rw INTEGER .1.3.6.1.4.1.2785.2.8.1.2.1.6 |
acQosQueueBuffCapsThese values control the relative buffering capacities of the four queues. Each byte represents the proportional buffering capacity out of 100 for a queue. The sum of these bytes must equal to 100. For example, if 2 queues are used, and the buffering capacities are 90 and 10, then acQosQueueBuffCaps should be set to '\0x5A\0x0A\0x00\0x00'.rw AcQueueBufferingCapacity .1.3.6.1.4.1.2785.2.8.1.2.1.7 |
acClassMapTableClassification Map table. SEQUENCE OF AcClassMapEntry .1.3.6.1.4.1.2785.2.8.1.3 |
acClassMapEntryA row in the class map provisioning table. AcClassMapEntry .1.3.6.1.4.1.2785.2.8.1.3.1 |
acClassMapNumberA number to identify a classification mapping. There can be at most four(4) rows for IP TOS based classification, four(4) additional rows for MPLS experimental bits based classfication, and four(4) additional rows for IEEE 802.1p based calssification. This table can have at most 12 rows for this version of the Ethernet access board.ro INTEGER .1.3.6.1.4.1.2785.2.8.1.3.1.1 |
acClassMapAdminStatusThe administrative status.rw AcAdminStatus (APPIAN-SMI-MIB) .1.3.6.1.4.1.2785.2.8.1.3.1.2 |
acClassMapNameA textual string for easy naming of the classification mapping.rw DisplayString .1.3.6.1.4.1.2785.2.8.1.3.1.3 |
acClassMapTypeThe type of classification used. This parameter specifies what fields in the packets are to be used for classification. This in turn dictates the width of the mapping used in acClassMapMapping.rw Enumeration .1.3.6.1.4.1.2785.2.8.1.3.1.4 |
acClassMapMappingThis octet string defines a mapping between a field within a packet payload and a 2-bit internal queue number. The octet string is a list of queue numbers. Each octet contains a single 2-bit queue number. In this product, 6-bits are wasted in each octet. In the future we may support more queues per service in which case we will extend the bit field in each octet. When this map is used for 802.1p and MPLS, it must be exactly 8-octets in length. For IP TOS, it must be 64-octets in length.rw AcClassMapping .1.3.6.1.4.1.2785.2.8.1.3.1.5 |
acServiceStatTableThe service statistics table. Statistics is provided for each queue priority of a service. Consequently, the table is composed of node, slot, port, channel, queue. SEQUENCE OF AcServiceStatEntry .1.3.6.1.4.1.2785.2.8.1.4 |
acServiceStatEntryA set of counters collected for a service queue priority. AcServiceStatEntry .1.3.6.1.4.1.2785.2.8.1.4.1 |
acServiceStatNodeIdA unique node identification number assigned by the EMS to uniquely identify a node within an Appian Ring.ro AcNodeId (APPIAN-SMI-MIB) .1.3.6.1.4.1.2785.2.8.1.4.1.1 |
acServiceStatSlotThe slot number within the chassis where the physical i/o port can be found for customer access.ro AcSlotNumber (APPIAN-SMI-MIB) .1.3.6.1.4.1.2785.2.8.1.4.1.2 |
acServiceStatPortThe port number ranging from (1..8) where the physical i/o connection for this customer service can be found.ro AcPortNumber (APPIAN-SMI-MIB) .1.3.6.1.4.1.2785.2.8.1.4.1.3 |
acServiceStatChannelThe service queue is one of 4 queues where a service is provisioned. Currently each (data) access port supports 4 service queues, each of which can support a service. The first release of our Ethernet access card supports a max of 4 services/port. In the future this range may increase but will always be dependent upon the access card being provisioned .ro INTEGER .1.3.6.1.4.1.2785.2.8.1.4.1.4 |
acServiceStatQueueThe service queuing priority. Service statistics is collected for each service queuing priority. Current OSAP supports up to 4 priorities. If a service doesn't use a priority, the corresponding entry has 0s for all counters.ro INTEGER .1.3.6.1.4.1.2785.2.8.1.4.1.5 |
acServiceStatUpstreamFramesThe number frames transported from the access port to the network.ro Counter64 .1.3.6.1.4.1.2785.2.8.1.4.1.6 |
acServiceStatUpstreamBytesThe number bytes transported from the access port to the network.ro Counter64 .1.3.6.1.4.1.2785.2.8.1.4.1.7 |
acServiceStatUpstreamDroppedFramesThe number frames dropped in the direction of the access port to the network.ro Counter64 .1.3.6.1.4.1.2785.2.8.1.4.1.8 |
acServiceStatUpstreamDroppedBytesThe number bytes dropped in the direction of the access port to the network.ro Counter64 .1.3.6.1.4.1.2785.2.8.1.4.1.9 |
acServiceStatUpstreamUnexpectedFramesThe number of frames that are unexpected. An example would a frame of wrong protocol type. Such frames are silently dropped but not counted in the dropped frames counter.ro Counter64 .1.3.6.1.4.1.2785.2.8.1.4.1.10 |
acServiceStatDownstreamFramesThe number frames transported from the network to access port.ro Counter64 .1.3.6.1.4.1.2785.2.8.1.4.1.11 |
acServiceStatDownstreamBytesThe number bytes transported from the network to the access port.ro Counter64 .1.3.6.1.4.1.2785.2.8.1.4.1.12 |
acServiceStatDownstreamDroppedFramesThe number frames dropped in the direction of the network to the access port.ro Counter64 .1.3.6.1.4.1.2785.2.8.1.4.1.13 |
acServiceStatDownstreamDroppedBytesThe number bytes dropped in the direction of the network to the access port.ro Counter64 .1.3.6.1.4.1.2785.2.8.1.4.1.14 |
acServiceStatDownstreamUnexpectedFramesThe number of frames that are unexpected. An example would a frame of wrong protocol type. Such frames are silently dropped but not counted in the dropped frames counter.ro Counter64 .1.3.6.1.4.1.2785.2.8.1.4.1.15 |
acIas OBJECT IDENTIFIER .1.3.6.1.4.1.2785.2.8.2 |
acIasTableThe Internet Access Service table. SEQUENCE OF AcIasEntry .1.3.6.1.4.1.2785.2.8.2.1 |
acIasEntryA row within the IAS provisioning table. AcIasEntry .1.3.6.1.4.1.2785.2.8.2.1.1 |
acIasNodeIdThe unique node identification number assigned by the EMS which identifies the node where the IAS service is being configured.ro AcNodeId (APPIAN-SMI-MIB) .1.3.6.1.4.1.2785.2.8.2.1.1.1 |
acIasSlotThe slot number where the physical data i/o port is located in the OSAP chassis, which will have the IAS service configured.ro AcSlotNumber (APPIAN-SMI-MIB) .1.3.6.1.4.1.2785.2.8.2.1.1.2 |
acIasPortThe physical port number on the i/o slot where this customers data interface will reside.ro AcPortNumber (APPIAN-SMI-MIB) .1.3.6.1.4.1.2785.2.8.2.1.1.3 |
acIasChannelThe service channel.ro INTEGER .1.3.6.1.4.1.2785.2.8.2.1.1.4 |
acIasDlciWhen an IAS service is carried over a FrameRelay trunk, this attribute dictates the frame relay circuit (DLCI) to be used for the service. When other types of trunks are used, this object has not meaning and has the value of 0.rw INTEGER .1.3.6.1.4.1.2785.2.8.2.1.1.5 |
acIasRespondToArpFlag to indicate we should respond to ARP requests.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.2785.2.8.2.1.1.6 |
acIasRemoteIpAddressThe IP address of at the network side. The object is optional. If set, ARP requests from the user are responded if the target IP address matchs this object. If this is object is not set, all ARP requests from the user are responded. If this object is not set, it may be learned from the inverse ARP if the service is carried on a frame relay circuit.rw IpAddress .1.3.6.1.4.1.2785.2.8.2.1.1.7 |
acIasCpeIpAddressThe IP address of the CPE device. This object is optional and if not set, it will be learned by looking into traffic from the CPE device.rw IpAddress .1.3.6.1.4.1.2785.2.8.2.1.1.8 |
acIasCpeMacAddressThe MAC Address of the CPE router.ro MacAddress (SNMPv2-TC) .1.3.6.1.4.1.2785.2.8.2.1.1.9 |
acIasCpeEncapsModeThe type of encapsulation used for packets destined for the CPE. unknown(0) - encapsulation mode is not set and is same as learning(1) mode. learning(1) - learn the encapsulation mode from the packets generated by the CPE. enet(2) - ethernet encapsulation. snap(3) - SNAP encaspualtion mode.rw Enumeration .1.3.6.1.4.1.2785.2.8.2.1.1.10 |
acIasPerformInverseArpFlag to indicate whether to perform Inverse ARP request to learn the remote IP address. This is applicable if the service is carried on a frame relay circuit. **-DInitiate Inverse Arp**rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.2785.2.8.2.1.1.11 |
acTls OBJECT IDENTIFIER .1.3.6.1.4.1.2785.2.8.3 |
acTlsTableThe Transparent LAN Services table. SEQUENCE OF AcTlsEntry .1.3.6.1.4.1.2785.2.8.3.1 |
acTlsEntryA row in the TLS table. AcTlsEntry .1.3.6.1.4.1.2785.2.8.3.1.1 |
acTlsNodeIdThe unique node number assigned by the EMS to uniquely identify this node within an Appian Ring of OSAP's which is configured for TLS service.ro AcNodeId (APPIAN-SMI-MIB) .1.3.6.1.4.1.2785.2.8.3.1.1.1 |
acTlsSlotThe slot upon which the TLS service is being provisioned.ro AcSlotNumber (APPIAN-SMI-MIB) .1.3.6.1.4.1.2785.2.8.3.1.1.2 |
acTlsPortThe physical port number on the slot on which the TLS service is provisioned.ro AcPortNumber (APPIAN-SMI-MIB) .1.3.6.1.4.1.2785.2.8.3.1.1.3 |
acTlsChannelThe service channel on which this TLS service is provisioned.ro INTEGER .1.3.6.1.4.1.2785.2.8.3.1.1.4 |
acTlsTlanIdIdentifies the Transparent LAN on which this virtual port, subscriber port and channel, is participating. This is a 12-bit value and is assigned by the EMS to ensure it is global to all TLS services and TLS trunks which share any common OSAPs or L2 switches. Note: It is prudent to keep the TlanId unique within the carriers entire TLS service offering until the carrier starts another 'TLS service domain'. WARNING: TLAN ID of zero(0) is invalid. TlanId's 1..15 are reserved for managment access. TlanId's 16..4095 are legal values.rw INTEGER .1.3.6.1.4.1.2785.2.8.3.1.1.5 |
acTlsServiceIdAn ID which is used within a TLS service to identify which service packets are associated with as they traverse the TLS trunks. Each Tls service, virtual port, configured needs an Id assigned to it. Each packet received on this virtual port, subscriber port and channel, is stamped with this value for its trip around a TLS trunk. These tags are assigned by the EMS and must be unique on a given TLS trunk. This value is a 10-bit number providing a range of 1k. Values 1..15 are reserved. Value 0 is used for TLS services that are not provisioned over a TLS trunk. These trunkless TLS services perform only local switching.rw INTEGER .1.3.6.1.4.1.2785.2.8.3.1.1.6 |
acTlsPointToPointEnableFlag to indicate whether or not the TLAN over which this Tls service is provisioned is a point to point TLAN. A point to point TLAN is a TLAN with two and only two Tls services, virtual ports.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.2785.2.8.3.1.1.7 |
acTlsServiceIdSharingEnableFlag to indicate whether or not the Tls Servive Id is shared between this service and other Tls Services provisioned on the same TLS trunk either on this OSAP or different OSAPs.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.2785.2.8.3.1.1.8 |