Internet Draft R. Jamp
Document: draft-anda-ops-mib-00.txt Y. Hsiao
Obsoletes: draft-jamp-ops-mib-00.txt ANDA Networks, Inc.
Category: Informational April 13, 2000
Definitions of Managed Objects for
Open Provisioning Standard (OPS) in the
Loop Access Environment
Status of this Memo
This document is an Internet-Draft and is in full conformance with
All provisions of Section 10 of RFC 2026 [1].
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
Abstract
This document specifies an Open Provisioning Standard (OPS) that
addresses the needs of an Integrated Communications Network (ICN)
for remote and automatic service turn-up and for the simplification
of monitoring and fault management across multiple network elements
within the Loop Access environment and within the Customer Premises
Environment (CPE) environment. OPS extends the standard Simple
Network Management Protocol (SNMP) Management Information Base (MIB)
by defining voice/data integration and flow-through provisioning
capabilities for the various devices within the ICN, such as
Integrated Access Devices (IADs).
OPS enables Carriers or Service Providers to control their
Integrated Access Services (IAS) from the network management system
in the Network Operation Center (NOC). Flow-through provisioning
allows administrators to send provisioning commands to multiple
network elements across the ICN. The provisioning commands are used
to define or modify a customer's services and to turn those services
on and off. Similarly, customer-initiated service requests as well
as performance and fault management information for existing
services can flow back to the carrier or service provider.
Jamp, Hsiao Page 1
Definitions of Managed Objects for OPS April 2000
The OPS model addresses interoperability from a management
standpoint across diverse network elements. The OPS model defines
standardized object elements in the OPS MIB that enable end-to-end
provisioning in order to support the variety of devices currently in
use in the Customer Premises Equipment (CPE) environment. This
document explains how the Open Provisioning Standard provides this
new infrastructure support.
Copyright Notice
Copyright (C) The Internet Society (2000). All Rights Reserved.
Table of Contents
1. Introduction ........................................... 2
2. Terminology ............................................ 2
3. The SNMP Management Framework .......................... 3
3.1 Object Definitions ..................................... 3
4. Overview ............................................... 4
4.1 Scope of the OPS MIB ................................... 4
4.2 Flow-Through Provisioning Architecture ................. 5
4.3 Open Provisioning Standard (OPS) ....................... 7
4.4 Voice Service Flow-Through Provisioning ................ 7
4.5 Data Service Flow-Through Provisioning ................. 8
4.6 Dynamic System Image and Configuration File Upgrades ... 8
4.6.1 Configure the File Server............................... 8
4.6.2 Dynamic System Image Upgrade ........................... 8
4.6.3 Dynamic Configuration File Upgrade ..................... 9
4.7 Additional Object Types in the OPS MIB ................. 10
5. OPS MIB Definitions .................................... 10
6. Security Considerations ................................ 37
7. References ............................................. 37
8. Author's Addresses ..................................... 39
9. Expiration Date ........................................ 39
10. Full Copyright Statement ............................... 40
1. Introduction
This document defines a portion of the Management Information Base
(MIB) for use with network management protocols in the Internet
community. In particular, it describes objects used for flow-through
provisioning from a network management system at the Network
Operation Center (NOC) of Carriers or Service Providers.
2. Terminology
This section defines the acronyms used in this document.
ATM Asynchronous Transfer Mode
ATM VCI ATM Virtual Channel identifier
ATM VPI ATM Virtual Path Identifier
CMIP Common Management Information Protocol
CPE Customer Premises Equipment
DACS Digital Cross-Connect
Jamp, Hsiao Informational Page 2
Definitions of Managed Objects for OPS April 2000
DLC Digital Loop Carrier
HTTP HyperText Transfer Protocol
IAD Integrated Access Device, Next Generation CPE device
IAS Integrated Access Services
ICN Integrated Communication Network
MAS Multi-Service Access Concentrator
NG-CPE Next-Generation Customer Premises Equipment
NOC Network Operating Center
OPS Open Provisioning Standard
OPS-CPE OPS-compliant CPE device (such as a DACS or DLC device)
OPS-IAD OPS-compliant NG-CPE IAD device
OPS-MAS OPS-compliant MAS device
PSTN Public Switched Telephone Network
RT Remote Terminal
SNMP Simple Network Management Protocol
TL1 Translation Language 1
UAP 2000 ANDA Network Universal Access Platform 2000
3. The SNMP Management Framework
The SNMP Management Framework presently consists of three major
components:
* SMI for SNMPv2, RFC 1902 [2]
* MIB-II for TCP/IP-based Internets, STD 17 (RFC 1213) [3]
* SNMP extensions, RFC 1157 [4]
* SNMPv2 protocol operations, RFC 1905 [5]
The following SNMP standards are also important to note:
* SNMP textual conventions, RFC 1903 [6]
* SNMP conformance statements, RFC 1904 [7]
The SNMP Management Framework permits new objects to be defined for
the purpose of experimentation and evaluation.
This document specifies the Open Provisioning Standard (OPS) MIB
module which is compliant to the SNMPv2 SMI. A semantically
identical MIB conforming to the SNMPv1 SMI can be produced through
the appropriate translation.
The OPS MIB resides in the experimental branch of the MIB tree under
object-identifier (OID) 1.3.6.1.3.
3.1. Object Definitions
The Management Information Base (MIB) is a virtual information
database. Managed Objects in the MIB are defined using the subset of
Abstract Syntax Notation One (ASN.1) defined in the SMI RFC 1902
[2].
Object definitions are used when describing managed objects. An
ASN.1 macro, OBJECT-TYPE, is used to concisely convey the syntax and
semantics of a Managed Object. Each OBJECT-TYPE is named by an
Jamp, Hsiao Informational Page 3
Definitions of Managed Objects for OPS April 2000
assigned name, the OBJECT IDENTIFIER. An object-instance of an
object-type uniquely identifies a specific instantiation of the
object.
Managed Objects are accessed through the use of the SNMP protocols.
4. Overview
4.1 Scope of the OPS MIB
The Open Provisioning Standard (OPS) MIB defines Managed Objects for
flow-though provisioning and management functions. This document
defines two groups of management objects for next-generation
customer premise equipment (NG-CPE).
The first object group is of a general configuration nature while
the second group contains objects similar to the Analog Line
Termination objects of a GR-303 Remote Terminal (RT) as defined in
the GR-303-Core document [8].
Examples of CPE devices include Digital Cross-Connect (DACS) device
or a Digital Cross-Connect (DACS) device.
An example of a NG-CPE is an Integrated Access Device (IAD). An IAD
that has implemented the OPS MIB is referred to as an OPS-compliant
IAD, abbreviated as OPS-IAD.
The OPS MIB described in this document focuses on OPS-IADs.
The OPS MIB will be will be extended at a later time to handle flow-
through provisioning and management of OPS-CPE devices such as DLC
and DACS devices. For the remainder of this document, the discussion
is focused on an OPS-IAD.
The following additional standard MIBs may be required to complete
the functions of an OPS-IAD to provide integrated voice and data
services:
* Managed Objects for DS0/DS0 bundle, RFC 2494 [9]
* Managed Objects for T1/E1, RFC 2495 [10]
* Managed Objects for T3/E3, RFC 2496 [11]
* Managed Objects for SONET/SDH, RFC 2558 [12]
* Managed Objects for Frame Relay, RFC 1604 [13]
* Managed Objects for PPP (link control protocol), RFC 1471 [14]
* Managed Objects for PPP (security protocols), RFC 1472 [15]
* Managed Objects for PPP (IP control protocol), RFC 1473 [16]
* Managed Objects for PPP (bridge control protocol), RFC 1474 [17]
* Textual conventions and object-identifiers for ATM, RFC 2514 [18]
* Managed Objects for ATM, RFC 2515 [19]
* Managed Objects for Ethernet-like interface types, RFC 2665 [20]
* MIB-II for TCP/IP-based Internets, STD 17 (RFC 1213) [3]
* SNMPv2 MIB for IP using SMIv2, RFC 2011 [21]
* SNMPv2 MIB for TCP using SMIv2, 2012 [22]
* SNMPv2 MIB for UDP using SMIv2, 2013 [23]
Jamp, Hsiao Informational Page 4
Definitions of Managed Objects for OPS April 2000
* Managed Objects for Classical IP and ARP over ATM, RFC 2320 [24]
* Managed Objects for ADSL (RFC 2662) [25]
The network management system at the Network Operation Center (NOC)
performs flow-through provisioning and management of an OPS-IAD
through an OPS-compliant Multi-Service Access Concentrator (MAS),
referred to as an OPS-MAS. The ANDA Networks Universal Access
Platform (UAP) 2000 can function as a MAS device. Flow-through
provisioning and management commands could arrive at an OPS-MAS in a
variety of formats. For example, the commands could be in
Transaction Language 1 (TL1), Common Management Information Protocol
(CMIP), HyperText Transfer Protocol (HTTP), or SNMP.
Typically, a Class 5 Switch uses the CMIP protocol, while an IAD
device uses the SNMP protocol. One of the major functions of an OPS-
MAS is to translate provisioning commands from the incoming format
(such as CMIP) into SNMP format before flowing the commands through
to the OPS-IADs.
4.2 Flow-Through Provisioning Architecture
Figure 1 provides an architectural view of the end-to-end
environment where flow-through provisioning can be implemented.
The OPS-MAS device, for example an ANDA Networks UAP 2000 device,
connects on the network-side to a PSTN Class 5 Switch (using the GR-
303 protocol) for voice traffic, and to other devices, such as a
packet-based ATM/Frame Relay network for data traffic.
On the other side, the OPS-MAS can directly connect to OPS-IAD
devices in the CPE environment, through copper-pair wiring using
technologies such as T1, HDSL or other xDSL. The OPS-MAS can
indirectly connect to OPS-IAD devices that reside within the local
loop access network. The loop access network shown in Figure 1
consists of devices such as DSLAMs and ATM switches.
Jamp, Hsiao Informational Page 5
Definitions of Managed Objects for OPS April 2000
Figure 1: Flow-Through Provisioning Architecture
............................................................
. .
. +-----------+ .
. Circuit Network Lines | Network | .
. to the Switch | Operation | .
. | | +-----| Center | .
. | | | | (NOC) | .
. +---------+ CMIP Messages | +-----------+ .
. | Class 5 |-------------------+ / .
. | Switch | / .
. | (GR-303)| / SNMP Messages .
. +---------+ ................/.......... .
. | . / . .
. | . \ / . .
. CMIP | . \ / . .
. Messages | . +--------+ Data . .
. | . | ATM | Network . .
. | . | Switch | (Backbone) . .
. | . +--------+ . .
. | .../....................... .
. | / .
. | / .
. Network +-------------+ OPS-MAS translates between .
. Side | OPS-MAS | CMIP and SNMP .
..........|.............|...................................
| |
+-------------+
SNMP | |
Messages | |
...........|..... ....|..........................
. | . . | Local Loop Access .
. +---------+ . . +--------+ Environment .
. | OPS-IAD | . . | ATM | (Data traffic) .
. +---------+ . . | Switch | .
. . . +--------+ .
. CPE . . | \ .
. Environment . . | \ .
. . . | \ .
. . . +-------+ +-------+ .
. . . | DSLAM | | DSLAM | .
. . . +-------+ +-------+ .
. . ....|....|.....................
. . | |
. ......|....|.............
. | | .
. +---------+ +---------+ .
. | OPS-IAD | | OPS-IAD | .
. +---------+ +---------+ .
.........................................
Jamp, Hsiao Informational Page 6
Definitions of Managed Objects for OPS April 2000
4.3. Open Provisioning Standard (OPS)
There are two views that the network manager at the NOC sees through
the OPS-MAS and all the attached OPS-IADs.
The first view regards the voice services coming from the Class 5
(GR-303) Switch. In this view, the OPS-IAD implements the Analog
Line Termination objects in the GR-303 managed object definition
(defined in a GR-303 MIB). The messages coming off the Class 5
Switch are CMIP messages. The messages between the OPS-MAS and the
OPS-IADs are SNMP messages. Software residing within the OPS-MAS
functions as a mediation device between the CMIP messages and SNMP
messages and translates between the two message formats.
The second view is an SNMP view, for the management of data and
voice Services. The network manager at the NOC uses either in-band
channel through the ATM network or out-band channel through the
Internet to access an SNMP agent residing in the OPS-MAS. In the
SNMP protocol, the SNMP agent in the OPS-MAS functions as a proxy
for the OPS-IAD SNMP agents.
4.4. Voice Service Flow-Through Provisioning
The network manager at the NOC manages the OPS-MAS and all of the
OPS-IADs through the Class 5 Switch. The Class 5 Switch and the OPS-
MAS communicate through the EOC channel using OSI CMIP messages as
defined in GR-303 Core document [8]. The OPS-MAS can execute
provisioning commands from the Class 5 Switch either directly or
indirectly.
For commands that operate on objects residing on the OPS-MAS, such
as configuring the number of DS1 channels between the Class 5 Switch
and the OPS-MAS, these commands are executed within the OPS-MAS.
For commands that operate on objects residing on the OPS-IAD such as
phone line ringing cadence, the CMIP message sent from the Class 5
Switch is translated by the OPS-MAS into an SNMP message and sends
it to the appropriate OPS-IAD. The OPS-IAD processes the SNMP
message and sends the response back to the OPS-MAS, which translates
the SNMP response into a CMIP response and sends it back to the
Class 5 Switch. The CMIP messages are sent to and from the Class 5
Switch through the EOC channel.
4.5. Data Service Flow-Through Provisioning
The network manager at the NOC uses either the in-band channel
through ATM network or the out-of-band channel through the Internet
to access the SNMP agent in the OPS-MAS. The OPS-MAS SNMP agent
represents all the SNMP Managed Objects residing on the OPS-MAS as
well as the SNMP objects residing in the OPS-IAD. Provisioning
commands such as configuring ATM VPI/VCI cross connections or
configuring traffic parameters at the OPS-MAS are executed within
the MAS.
Jamp, Hsiao Informational Page 7
Definitions of Managed Objects for OPS April 2000
For commands that operate on objects residing on the OPS-IAD such as
the Ethernet interface local to the OPS-IAD, the SNMP messages are
first sent to the OPS-MAS. The OPS-MAS forwards them to the
appropriate OPS-IAD. The OPS-IAD executes the SNMP messages and
sends the responses back to the OPS-MAS. The OPS-MAS then returns
the SNMP responses to the network manager at the NOC.
4.6. Dynamic System Image and Configuration File Upgrades
The OPS MIB provides the capability for the network manager to
initiate a software upgrade of the system image file on the OPS-IAD
and also provides the capability to upload or download the
configuration database file on the OPS-IAD. The file transfers are
accomplished by directing a specified TFTP or FTP server to download
or upload the specified file to the OPS-IAD. Depending on the
capabilities of the specific IAD, multiple versions of the system
image and/or configuration database files can be stored on the OPS-
IAD as well as options about when the IAD is directed to start using
the newly transferred file(s). Section 5, "OPS MIB Definitions,"
contains the definitions of these objects with corresponding
descriptions that explain the usage options/considerations of each
managed object.
The following subsections provide a summary of the procedures for
remotely provisioning and managing the system image and
configuration database files that reside on the OPS-IAD.
4.6.1 Configure the File Server
Before uploading or downloading the system image or configuration
database files, information about the file server must be
configured. For example these objects are defined in the OPS MIB:
* iOpsIADServerIP - indicates the IP address of the file server
* iOpsIADServerType - indicates the type of file transfer protocol
to be used (TFTP, FTP, etc.)
* iOpsIADServerLoginName - indicates the name of the file server
* iOpsIADServerPasswd - is the password used to login to the file
server.
This information could be configured manually, but can be
accomplished remotely by using flow-through provisioning.
4.6.2. Dynamic System Image Upgrade
The following are examples of some of the objects defined in the OPS
MIB to manage the system image file on the OPS-IAD. Note that not
all types of IADs can contain multiple system image files. These
objects are described in more detail in Section 5, "OPS MIB
Definitions."
Jamp, Hsiao Informational Page 8
Definitions of Managed Objects for OPS April 2000
* iOpsIADSoftwareFileName - indicates the system image file the IAD
boots from.
* iOpsIADResetIAD - reboots the OPS-IAD with the system image file
specified in the iOpsIADSoftwareFileName object-type.
* iOpsIADSoftwareUpgradeFileName - indicates the name of a new
system image file name that is to be downloaded to the IAD.
* iOpsIADDownloadSoftware - used to initiate the download of the
new system image file to the OPS-IAD. Is also used to obtain
information about the status of the download (complete, failed,
or in progress).
* iOpsIADSaveSoftware - provides the option to immediately reboot
the OPS-IAD with the newly downloaded system image file, or to
simply save the file for later use.
* softwareDownloadComplete - is a notification (SNMPv2 trap) that
is issued after the attempt to download a new system image file.
4.6.3. Dynamic Configuration File Upgrade
The following are examples of some of the objects defined in the OPS
MIB to manage the configuration file (persistent database) on the
OPS-IAD. Note that not all types of IADs can contain multiple
configuration files. These objects are described in more detail in
Section 5, "OPS MIB Definitions."
* iOpsIADConfigFileName - indicates the configuration file the IAD
will use.
* iOpsIADReConfigIAD - directs the OPS-IAD to start using the
configuration file specified in the iOpsIADConfigFileName
object-type.
* iOpsIADConfigUpgradeFileName - indicates the name of a new
configuration file name that is to be downloaded to the OPS-IAD.
* iOpsIADUpDownloadConfiguration - used to initiate the download of
the new configuration image file to the OPS-IAD. It can also be
used to upload the configuration image, for example, to replicate
the persistent database to another OPS-IAD, It can also used to
obtain information about the status of the download (complete,
failed, or in progress).
* iOpsIADSaveConfiguration - provides the option to immediately
reboot the OPS-IAD with the newly downloaded configuration file,
or to simply save the file for later use.
* configUpDownloadComplete - is a notification (SNMPv2 trap) that
is issued after the attempt to download or upload a configuration
file.
Jamp, Hsiao Informational Page 9
Definitions of Managed Objects for OPS April 2000
4.7. Additional Object Types in the OPS MIB
The OPS MIB defines other object types in addition to the examples
described in the previous sections. All the OPS MIB objects are
included in Section 5, "OPS MIB Definitions." The following are a
few examples of the functionality the OPS MIB provides:
* Obtain alarm information from the OPS-IAD
* Obtain administrative or operational status from the OPS-IAD
* Define the types of data service (Frame Relay, ATM, etc.)
* Define the number of voice lines and their attributes (Robbed bit
mode, CRV, etc.)
* Place lines 'in service' or 'out of service'
* Obtain line information such as line status, line alarms, etc.
* Initiate line loopback tests
* Obtain notifications (SNMPv2 traps) about line status (traps sent
when a status change occurs, the time of the last change in
status, result of loopback testing, etc.)
5. OPS MIB Definitions
This section describes the OPS MIB objects that all OPS compliant
CPE shall implement. All provisioning commands to the OPS-CPE will
be SNMP messages manipulating MIB objects defined in this section.
'iOpsIADConfig' is a group of Managed Objects that support the
configuration of the IAD, including the public IP address settings,
management channel setup, etc.
'iOpsIADVoiceService' is a group of Managed Objects that support the
phone services at the IAD.
OPS-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
IpAddress, experimental, Integer32, Unsigned32, Gauge32
FROM SNMPv2-SMI
DisplayString, RowStatus, DateAndTime, MacAddress,
TEXTUAL-CONVENTION, TruthValue, TimeStamp
FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF
InterfaceIndex
FROM IF-MIB;
opsMIB MODULE-IDENTITY
LAST-UPDATED "9910060000Z"
ORGANIZATION "ANDA Networks, Inc."
CONTACT-INFO
" Ray Jamp
Postal: ANDA Networks, Inc.
2921 Copper Road
Santa Clara, CA 95051
Jamp, Hsiao Informational Page 10
Definitions of Managed Objects for OPS April 2000
Tel: +1 408-990-4900
Fax: +1 408-990-4901
E-mail: rjamp@andanetworks.com
Yu-Jen Hsiao
Postal: ANDA Networks, Inc.
2921 Copper Road
Santa Clara, CA 95051
Tel: +1 408-990-4900
Fax: +1 408-990-4901
E-mail: yjhsiao@andanets.com"
DESCRIPTION
"This is the MIB module for OPS-compliant
CPE for managing configurations of
the CPE system and its voice services."
REVISION "9910060000Z"
DESCRIPTION
"Published as draft-anda-ops-mib-00"
::= { experimental 1 }
-- *****************************************************************
--
-- The Open Provisioning Standard (OPS) MIB defines managed objects
-- for flow-though provisioning and management functions. This
-- document defines two groups of management objects for
-- next-generation customer premise equipment (NG-CPE). The first
-- group of objects are of a general configuration nature.
-- The second group of objects are similar to the Analog Line
-- Termination objects of a GR-303 Remote Terminal as defined in
-- the GR-303-Core document. A NG-CPE that implements the
-- OPS MIB is an OPS compliant NG-CPE (OPS-CPE).
--
-- The network management systems at the Network Operation Center
-- (NOC) perform flow-through provisioning and management of
-- OPS-IADs through an OPS-compliant Multi-Service Access
-- Concentrator (MAS).
--
-- *****************************************************************
opsMIBObjects OBJECT IDENTIFIER ::= { opsMIB 1 }
iadOPS OBJECT IDENTIFIER ::= { opsMIBObjects 1 }
iOpsIADConfig OBJECT IDENTIFIER ::= { iadOPS 1 }
iOpsIADVoiceService OBJECT IDENTIFIER ::= { iadOPS 2 }
dlcOPS OBJECT IDENTIFIER ::= { opsMIBObjects 2 }
dacOPS OBJECT IDENTIFIER ::= { opsMIBObjects 3 }
-- *****************************************************************
--
-- The OPS IAD Configuration Group
--
-- *****************************************************************
Jamp, Hsiao Informational Page 11
Definitions of Managed Objects for OPS April 2000
iOpsIADIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Index of the interface that the IAD uses to
communicate with the Multi-Service Access
Concentrator (MAS)."
::= { iOpsIADConfig 1 }
iOpsIADManufacturerName OBJECT-TYPE
SYNTAX DisplayString (SIZE(0..255))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Name and contact information of the manufacturer
of the IAD."
::= { iOpsIADConfig 2 }
iOpsIADSerialNumber OBJECT-TYPE
SYNTAX DisplayString (SIZE(0..255))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Serial number of the IAD."
::= { iOpsIADConfig 3 }
iOpsIADCLEICode OBJECT-TYPE
SYNTAX DisplayString (SIZE(0..255))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Common Language Equipment Identifier Code of the IAD."
::= { iOpsIADConfig 4 }
iOpsIADAdminStatus OBJECT-TYPE
SYNTAX INTEGER {
up(1),
down(2),
test(3)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Identifies the administrative status of the IAD."
DEFVAL { up }
::= { iOpsIADConfig 5 }
iOpsIADOperStatus OBJECT-TYPE
SYNTAX INTEGER {
up(1),
down(2),
testing(3),
unknown(4)
Jamp, Hsiao Informational Page 12
Definitions of Managed Objects for OPS April 2000
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Identifies the operational status of the IAD."
::= { iOpsIADConfig 6 }
iOpsIADAlarmStatus OBJECT-TYPE
SYNTAX INTEGER {
noAlarm(1),
minorAlarm(2),
majorAlarm(3),
criticalAlarm(4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Identifies the current alarm status of the IAD. If multiple
alarms are present, this object displays the highest
severity alarm value."
::= { iOpsIADConfig 7 }
iOpsIADOperStatusLastChange OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of the SNMPv2 MIBs 'sysUpTime' object-type at the
time the IAD entered its current operating state.
If the IADs current state was entered prior to the last
re-initialization of the SNMP agent, then this object will
contain a zero (0) value."
::= { iOpsIADConfig 8 }
iOpsIADResetIAD OBJECT-TYPE
SYNTAX INTEGER {
none(1),
warmReboot(2),
coldReboot(3)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Reboot the IAD. The IAD will boot up running the system
image file specified in the 'iOpsIADSoftwareFileName'
object-type.
It is highly recommended that the IAD contain bootstrap
code that the IAD can default to, in the unlikely scenario
that the file specified in 'iOpsIADSoftwareFileName'
does not exist on the IAD or is otherwise invalid.
This is an action attribute and it is meaningless to attempt
Jamp, Hsiao Informational Page 13
Definitions of Managed Objects for OPS April 2000
to read this value."
::= { iOpsIADConfig 9 }
iOpsIADSoftwareFileName OBJECT-TYPE
SYNTAX DisplayString (SIZE(0..255))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Contains the name of the system image file that the IAD
will attempt to boot from.
If IAD does not support multiple system image files, then
this object becomes read-only and is only capable of
containing the same file that is uploaded in the
'iOpsIADSoftwareUpgradeFileName' object-type.
This object only specifies the file name of the system image
file residing on the IAD and not a full path name as is
specified in the 'iOpsIADSoftwareUpgradeFileName'
object-type.
The SNMP Agent will reject an SNMP SET PDU message on this
object if the file does not exist on the IAD or if the file
is otherwise invalid (incorrect name, corrupt, etc.)."
::= { iOpsIADConfig 10 }
iOpsIADSoftwareUpgradeFileName OBJECT-TYPE
SYNTAX DisplayString (SIZE(0..255))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Contains the name of the system image file to be
downloaded to the IAD. The full path name of the file must
be specified.
The IP address of the server used to download the file must
first be specified in the 'iOpsIADServerIP' object-type.
The server used to download the file defaults to the
TFTP protocol. This default may be changed to 'FTP' or to
'other'. It is specified in the 'iOpsIADServerType'
object-type.
If an alternate transfer protocol is to be used, it must
be specified before attempting the file download."
::= { iOpsIADConfig 11 }
iOpsIADDownloadSoftware OBJECT-TYPE
SYNTAX INTEGER {
downloadSoftwareFromServer(1),
downloadComplete(2),
downloadFailed(3),
downloadInProgress(4),
none(5)
Jamp, Hsiao Informational Page 14
Definitions of Managed Objects for OPS April 2000
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Is used to download the system image file to the IAD or to
obtain status about the file download:
1) The SNMP SET PDU message is used to initiate a download
of the system image file to the IAD.
2) The SNMP GET, GET-NEXT, OR GET-BULK PDU messages are used
to obtain status of the previously initiated download.
When initiating a download of the system image file, the
attributes of this object and the attributes of the
'iOpsIADSaveSoftware' object-type must be included in the
same SNMP SET PDU message.
'iOpsIADSaveSoftware' is used to specify either:
1) A save of the file on the IAD.
2) A save of the file on the IAD and then perform a reboot
of the IAD.
The IP address of the server used to transfer the file or
the status information is specified in the 'iOpsIADServerIP'
object-type.
The server used to download the system image file defaults
to the TFTP protocol. However, this default may be changed
to 'FTP' or to 'other'. It is specified in the
'iOpsIADServerType' object-type.
If an alternate transfer protocol is used, it must first
be specified before attempting the file download.
If the IAD is unable to complete the file transfer for any
reason, the values of the 'iOpsIADAdminStatus' and
'iOpsIADOperStatus' object-types must remain in the 'up'
status in order for the IAD to be available to accept
subsequent system image file downloads.
SET PDU message:
1: Download the system image file from the server to the
IAD. The system image file name is specified in the
'iOpsIADSoftwareUpgradeFileName' object-type.
GET, GET-NEXT, or GET-BULK PDU message:
2: The download of the system image file is complete.
3: The download of the system image file failed.
4: The download of the system image file is in progress.
5. No status can be returned because no prior SET operation
was performed."
::= { iOpsIADConfig 12 }
iOpsIADSaveSoftware OBJECT-TYPE
Jamp, Hsiao Informational Page 15
Definitions of Managed Objects for OPS April 2000
SYNTAX INTEGER {
save(1),
saveAndReboot(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Save downloaded system image file with the option to
reboot the IAD.
For IADs that can contain multiple system image files,
either option can be used.
For IADs that can only contain one system image file,
only the 'saveAndReboot' option can be used.
1) When the 'save' option is specified, the IAD will not
reboot after the file transfer is completed. the IAD will
continue to use the currently running system image file.
In order for the IAD to come up with the new system image
the next time it is rebooted, the network manager must set
the 'iOpsIADSoftwareFileName' object-type with the
downloaded file name.
2) If the 'saveAndReboot' option is specified, the IAD will
reboot with the new system image if:
- The file transfer successfully completed, AND
- The file is not corrupt
The SNMP Agent must update iOpsIADSoftwareFileName with
the 'iOpsIADSoftwareUpgradeFileName' object-type before
the reboot.
When initiating a download, the attributes of this object
and the attributes of the 'iOpsIADDownloadSoftware'
object-type must be included in the same
SNMP SET PDU message.
This is an action attribute and it is meaningless to attempt
to read this value."
::= { iOpsIADConfig 13 }
iOpsIADSoftwareVersion OBJECT-TYPE
SYNTAX DisplayString (SIZE(0..255))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Version number of the currently running system image."
::= { iOpsIADConfig 14 }
iOpsIADReConfigIAD OBJECT-TYPE
SYNTAX INTEGER {
Jamp, Hsiao Informational Page 16
Definitions of Managed Objects for OPS April 2000
none(1),
reConfig(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Change the current configuration file (persistent database)
running on the IAD to a new configuration file specified in
the 'iOpsIADConfigFileName' object-type."
::= { iOpsIADConfig 15 }
iOpsIADConfigFileName OBJECT-TYPE
SYNTAX DisplayString (SIZE(0..255))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Contains the configuration file name that the IAD will
attempt to load.
If the IAD does not support multiple configuration files,
then this object becomes read-only and is only capable of
containing the same file that is uploaded to the
'iOpsIADConfigUpgradeFileName' object-type.
This object only contains the file name of the
configuration file residing on the IAD and not a full
path name as is specified in the
'iOpsIADConfigUpgradeFileName' object-type.
The SNMP Agent will reject an SNMP SET PDU message on this
object if the file does not exist on the IAD or if the file
is otherwise invalid (incorrect name, corrupt, etc.)."
::= { iOpsIADConfig 16 }
iOpsIADConfigUpgradeFileName OBJECT-TYPE
SYNTAX DisplayString (SIZE(0..255))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Contains the name of the configuration file to be
downloaded to the IAD. The full path name of the file must
be specified.
The IP address of the server used to download the file must
first be specified in the 'iOpsIADServerIP' object-type.
The server used to download the file defaults to the
TFTP protocol. This default may be changed to 'FTP' or to
'other'. It is specified in the 'iOpsIADServerType'
object-type.
If an alternate transfer protocol is to be used, it must
be specified before attempting the file download."
::= { iOpsIADConfig 17 }
Jamp, Hsiao Informational Page 17
Definitions of Managed Objects for OPS April 2000
iOpsIADUpDownloadConfiguration OBJECT-TYPE
SYNTAX INTEGER {
downloadConfigFileFromServer(1),
uploadConfigFileToServer(2),
uploadOrDownloadComplete(3),
uploadOrDownloadFailed(4),
downloadInProgress(5),
uploadInProgress(6),
none(7)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Is used to download the configuration file to the IAD,
or to upload the configuration from the IAD, or to obtain
status about the file download or upload:
1) The SNMP SET PDU message is used to initiate the download
or upload of the configuration file.
2) The SNMP GET, GET-NEXT, or GET-BULK messages are used to
obtain status of the previously initiated download or
upload.
When initiating a download or upload, of the configuration
file, the attributes of this object and the attributes of
the 'iOpsIADSaveConfiguration' object-type must be included
in the same SNMP SET PDU message.
The IP address of the server used to transfer the file or
the status information is specified in iOpsIADServerIP.
The server used to download or upload the configuration
file defaults to the TFTP protocol. However, this default
may be changed to 'FTP' or to 'other'. It is specified in
the 'iOpsIADServerType' object-type.
If an alternate transfer protocol is used, it must first
be specified before attempting the file download.
If the IAD is unable to complete the file transfer for any
reason, the values of the 'iOpsIADAdminStatus' and
'iOpsIADOperStatus' object-types must remain in the 'up'
status in order for the IAD to be available to accept
subsequent requests for configuration file
downloads or uploads.
SET PDU message:
1: Download the configuration file from the server to the
IAD. The configuration file name is specified in the
'iOpsIADConfigUpgradeFileName' object-type.
2: Upload the configuration script from the IAD to the
server. he configuration file name is specified in the
'iOpsIADConfigUpgradeFileName' object-type.
Jamp, Hsiao Informational Page 18
Definitions of Managed Objects for OPS April 2000
GET, GET-NEXT, or GET-BULK PDU message:
3: The upload or download of the configuration file is
complete.
4: The upload or download of the configuration file failed.
5: The download of the configuration file is in progress.
6: The upload of the configuration file is in progress.
7. No status can be returned because no prior SET operation
was performed."
::= { iOpsIADConfig 18 }
iOpsIADSaveConfiguration OBJECT-TYPE
SYNTAX INTEGER {
none(1),
save(2),
saveAndReconfigure(3)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Save the downloaded configuration file, but continue to use
the currently running configuration file or start using the
newly downloaded configuration file.
For IADs that can contain multiple configuration files,
either option can be used.
For IADs that can only contain one configuration file,
only the 'saveAndReconfigure' option can be used.
1) When the 'none' option is specified.
2) When the 'save' option is specified, the IAD will
continue to use the currently running configuration file.
In order for the IAD to use the newly downloaded
configuration file, the network manager should set
the 'iOpsIADConfigFileName' object-type with the newly
downloaded configuration file name, and then set the
'iOpsIADReConfigIAD' object-type to the value
'reConfig(2)'.
3) When 'saveAndReconfigure' is specified, the IAD will
immediately start using the new configuration file if:
- The file transfer successfully completed, AND
- The file is not corrupt
The SNMP Agent must update the 'iOpsIADConfigFileName'
object-type with the 'iOpsIADConfigUpgradeFileName'
object-type before using the newly downloaded
configuration file.
When initiating a download, the attributes of this object
and the attributes of the 'iOpsIADUpDownloadConfiguration'
Jamp, Hsiao Informational Page 19
Definitions of Managed Objects for OPS April 2000
object-type must be included in the same SNMP SET PDU
message.
This is an action attribute and it is meaningless to attempt
to read this value."
::= { iOpsIADConfig 19 }
iOpsIADVersionConfig OBJECT-TYPE
SYNTAX DisplayString (SIZE(0..255))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Version of Configuration."
::= { iOpsIADConfig 20 }
iOpsIADMgmtChType OBJECT-TYPE
SYNTAX INTEGER {
andaFDL(1),
ds0(2),
fr-dlci(3),
atmVPIVCI(4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Specifies the type of management channel to be used, where:
1) 'andaFDL' is the ANDA facility data link channel
2) 'dso' is a DS0 channel
3) 'fr-dlci' is a Frame-Relay circuit
4) 'atmVPIVCI' is an ATM virtual circuit"
::= { iOpsIADConfig 21 }
iOpsIADMgmtChNumber OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This field is set according the value specified in the
'iOpsIADMgmtChType' object-type:
If 'iOpsIADMgmtChType' is 'andaFDL(1)' -
this object is not applicable.
If 'iOpsIADMgmtChType' is 'ds0(2)' -
is the DS0 channel number to use.
If 'iOpsIADMgmtChType' is 'fr-dlci(3)' -
is the DLCI number to use.
If 'iOpsIADMgmtChType' is 'atmVPIVCI(4)' -
is set as follows:
The most significant 16-bit word is the VPI.
The least significant 16-bit word is the VCI."
::= { iOpsIADConfig 22 }
iOpsIADMgmtChBandwidth OBJECT-TYPE
SYNTAX Gauge32
Jamp, Hsiao Informational Page 20
Definitions of Managed Objects for OPS April 2000
UNITS "Kbps"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object is only valid when 'iOpsIADMgmtChType' is
'fr-dlci(3)' or 'atmVPIVCI(4)'.
This object indicates the amount of bandwidth that is
allocated for the management channel."
::= { iOpsIADConfig 23 }
iOpsIADMgmtChInactivityTimer OBJECT-TYPE
SYNTAX INTEGER (1..1000)
UNITS "Seconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Amount of time of inactivity allowed on a management
channel before the link is declared down. The MAS should
poll IAD on a keep-alive timer."
DEFVAL { 60 }
::= { iOpsIADConfig 24 }
iOpsIADDataService OBJECT-TYPE
SYNTAX INTEGER {
frameRelay(1),
atm(2),
ppp(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates the type of data service offered by the IAD:
'1' is Frame Relay
'2' is ATM
'3' is PPP"
::= { iOpsIADConfig 25 }
iOpsIADDateAndTime OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Is the date and time on the IAD."
::= { iOpsIADConfig 26 }
iOpsIADMacAddress OBJECT-TYPE
SYNTAX MacAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Is the MAC address on the IAD."
::= { iOpsIADConfig 27 }
iOpsIADPublicIPAddress OBJECT-TYPE
Jamp, Hsiao Informational Page 21
Definitions of Managed Objects for OPS April 2000
SYNTAX IpAddress
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Is the IP address on the IAD."
::= { iOpsIADConfig 28 }
iOpsIADSubnetMask OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Is the subnet mask on the IAD."
::= { iOpsIADConfig 29 }
iOpsIADGateway OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Is the Gateway IP address."
::= { iOpsIADConfig 30 }
iOpsIADDHCPIP OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"If used, is the IP address of the DHCP server."
::= { iOpsIADConfig 31 }
iOpsIADServerIP OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Is the IP address of the server used for the system image
file downloads, for the downloads and uploads of the
configuration file (persistent database) and for obtaining
status information about the file transfer. "
::= { iOpsIADConfig 32 }
iOpsIADServerType OBJECT-TYPE
SYNTAX INTEGER {
tftpServer(1),
ftpServer(2),
otherServer(3)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Indicates the type of file transfer to be used.
TFTP is the default and will be used unless another
selection is specified."
Jamp, Hsiao Informational Page 22
Definitions of Managed Objects for OPS April 2000
DEFVAL { tftpServer }
::= { iOpsIADConfig 33 }
iOpsIADServerLoginName OBJECT-TYPE
SYNTAX DisplayString (SIZE(0..255))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Is the Login Name of the Server."
::= { iOpsIADConfig 34 }
iOpsIADServerPasswd OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (0..1024))
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"Is the password used to login to the Server. It may be
encrypted.
This value is write only."
::= { iOpsIADConfig 35 }
iOpsIADMasPublicKey OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (0..1024))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Is the public key of the MAS which, when combined with the
private key stored on the IAD, can be used to encrypt and
decrypt the community name in an SNMP PDU."
::= { iOpsIADConfig 36 }
iOpsIADManagementPasswd OBJECT-TYPE
SYNTAX DisplayString (SIZE(0..255))
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"Is the password assigned to an IAD to be used by a directly
connected management station to login to the IAD.
This value is write only."
::= { iOpsIADConfig 37 }
-- *****************************************************************
--
-- The OPS Voice Service Table
--
-- *****************************************************************
iOpsIADVlNumber OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates the number of voice lines on the IAD."
::= { iOpsIADVoiceService 1 }
Jamp, Hsiao Informational Page 23
Definitions of Managed Objects for OPS April 2000
iOpsIADVlTable OBJECT-TYPE
SYNTAX SEQUENCE OF IOpsIADVlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Is a list of the voice line entries. The number of entries
is indicated by the value of the 'iOpsIADVlNumber'
object-type."
::= { iOpsIADVoiceService 2 }
iOpsIADVlEntry OBJECT-TYPE
SYNTAX IOpsIADVlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Is an entry that contains the objects pertaining to a
voice line uniquely identified by the 'iOpsIADVlIndex'
object-type."
INDEX { iOpsIADVlIndex }
::= { iOpsIADVlTable 1 }
IOpsIADVlEntry ::=
SEQUENCE {
iOpsIADVlIndex
INTEGER,
iOpsIADVlDS1IfIndex
InterfaceIndex,
iOpsIADVlDS0Index
INTEGER,
iOpsIADVlOperStatus
INTEGER,
iOpsIADVlSecondaryServiceState
INTEGER,
iOpsIADVlAdminStatus
INTEGER,
iOpsIADVlOperStatusLastChange
TimeStamp,
iOpsIADVlLoopbackTestResult
INTEGER,
iOpsIADVlNumberOfWires
INTEGER,
iOpsIADVlSignalFunctionCode
INTEGER,
iOpsIADVlRobbedBitMode
INTEGER,
iOpsIADVlCallReferenceValue
INTEGER,
iOpsIADVlRingingCadence
INTEGER,
iOpsIADVlVoiceProtocolType
INTEGER,
iOpsIADVlPhoneNumber
DisplayString,
Jamp, Hsiao Informational Page 24
Definitions of Managed Objects for OPS April 2000
iOpsIADVlTransmitImpedance
INTEGER,
iOpsIADVlReceiveImpedance
INTEGER,
iOpsIADVlTransmitLoss
INTEGER,
iOpsIADVlReceiveLoss
INTEGER,
iOpsIADVlPayloadType
INTEGER,
iOpsIADVlEchoCancellation
TruthValue,
iOpsIADVlEchoDelay
INTEGER,
iOpsIADVlSilenceSuppression
TruthValue,
iOpsIADVlGenerateTestTone
TruthValue,
iOpsIADVlRowStatus
RowStatus
}
iOpsIADVlIndex OBJECT-TYPE
SYNTAX INTEGER
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Is the index of the voice line."
::= { iOpsIADVlEntry 1 }
iOpsIADVlDS1IfIndex OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Is the associated DS1 interface index, if the IAD has
one or more DS1s. The value of this object is zero (0),
if there are no DS1s local to the IAD."
::= { iOpsIADVlEntry 2 }
iOpsIADVlDS0Index OBJECT-TYPE
SYNTAX INTEGER
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Is the DS0 index within the DS1, or, the index of the
individual POTS line"
::= { iOpsIADVlEntry 3 }
iOpsIADVlOperStatus OBJECT-TYPE
SYNTAX INTEGER {
up-InService(1),
down-OutOfService(2),
testing(3),
Jamp, Hsiao Informational Page 25
Definitions of Managed Objects for OPS April 2000
unknown(4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates the operating status of the voice line.
Is one of the following:
'up-InService' - The line is in service
'down-OutOfService' - The line is out of service
'testing' - The line is currently undergoing a test
'unknown' - The status of the line cannot be determined"
::= { iOpsIADVlEntry 4 }
iOpsIADVlSecondaryServiceState OBJECT-TYPE
SYNTAX INTEGER {
none(1),
manual-OOS(2),
switch-OOS(3),
los-OOS(4),
oof-OOS(5),
maintenance-OOS(6)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This indicates any current alarm on the voice line."
::= { iOpsIADVlEntry 5 }
iOpsIADVlAdminStatus OBJECT-TYPE
SYNTAX INTEGER {
up-restore(1),
down-remove(2),
test-loopback(3)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This identifies the desired administrative status of the
voice line. It is one of the following values:
'up-restore' - activate or restore the voice service
'down-remove' - deactivate or remove the voice service
'test-loopback' - initiate loopback test on the voice line
The test result can be monitored by polling
the 'iOpsIADVlLoopbackTestResult' object-type.
If this object is set to 'test-loopback(3)' on a voice line
that is still running a previously initiated
'test-loopback(3)', a second (simultaneous) loopback test
will not be invoked. In this case, the status of the
line in test will be indicated by the
'iOpsIADVlLoopbackTestResult' object-type as
'test-inProgress(2)'."
Jamp, Hsiao Informational Page 26
Definitions of Managed Objects for OPS April 2000
DEFVAL { up-restore }
::= { iOpsIADVlEntry 6 }
iOpsIADVlOperStatusLastChange OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of the SNMPv2 MIBs 'sysUpTime' object-type at
the time this voice line entered its current operating
status state.
If the current state of the voice line was entered prior
to the last re-initialization of the SNMP agent, then
this object will contain a zero (0) value."
::= { iOpsIADVlEntry 7 }
iOpsIADVlLoopbackTestResult OBJECT-TYPE
SYNTAX INTEGER {
no-Test(1),
test-inProgress(2),
test-Pass(3),
test-Fail-OffHook(4),
test-Fail-Bell(5),
test-Fail-Others(6)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates the results of the loopback test that was
initiated by the 'iOpsIADVlAdminStatus'
object-type."
::= { iOpsIADVlEntry 8 }
iOpsIADVlNumberOfWires OBJECT-TYPE
SYNTAX INTEGER {
wires2(1),
wires4(2),
wires6(3),
wires8(4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates the number of wires on the line."
::= { iOpsIADVlEntry 9 }
iOpsIADVlSignalFunctionCode OBJECT-TYPE
SYNTAX INTEGER {
fxsLoopStart(1),
fxsGroundStart(2),
fxsWinkStart(3),
fxoLoopStart(4),
fxoGroundStart(5),
Jamp, Hsiao Informational Page 27
Definitions of Managed Objects for OPS April 2000
fxoWinkStart(6),
eAndM2-2(7),
eAndM2-4(8),
eAndM4-2(9),
eAndM4-4(10)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Is the Generic Signal Function code for the voice line.
The default value is 'fxsLoopStart'."
DEFVAL { fxsLoopStart }
::= { iOpsIADVlEntry 10 }
iOpsIADVlRobbedBitMode OBJECT-TYPE
SYNTAX INTEGER {
inactive(1),
clearChannel(2),
abcd(3),
ab(4),
a(5)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Is the Robbed Bit Signal mode for the voice line.
The default value is 'abcd'."
DEFVAL { abcd }
::= { iOpsIADVlEntry 11 }
iOpsIADVlCallReferenceValue OBJECT-TYPE
SYNTAX INTEGER (1..2048)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Indicates the Call Reference Value (CRV)."
::= { iOpsIADVlEntry 12 }
iOpsIADVlRingingCadence OBJECT-TYPE
SYNTAX INTEGER
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Indicates the ring cadence. "
::= { iOpsIADVlEntry 13 }
iOpsIADVlVoiceProtocolType OBJECT-TYPE
SYNTAX INTEGER {
ds0(1),
voATM-AAL1(2),
voATM-AAL2(3),
voIP(4)
}
MAX-ACCESS read-create
Jamp, Hsiao Informational Page 28
Definitions of Managed Objects for OPS April 2000
STATUS current
DESCRIPTION
"Indicates the type of voice protocol that will be used."
::= { iOpsIADVlEntry 14 }
iOpsIADVlPhoneNumber OBJECT-TYPE
SYNTAX DisplayString (SIZE(0..255))
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Indicates the telephone number of the voice line."
::= { iOpsIADVlEntry 15 }
iOpsIADVlTransmitImpedance OBJECT-TYPE
SYNTAX INTEGER {
none(1),
ohm-50(2),
ohm-600(3),
ohm-900(4),
ohm-1200(5)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Indicates the Transmit Impedance."
DEFVAL { none }
::= { iOpsIADVlEntry 16 }
iOpsIADVlReceiveImpedance OBJECT-TYPE
SYNTAX INTEGER {
none(1),
ohm-50(2),
ohm-600(3),
ohm-900(4),
ohm-1200(5)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Indicates the Receive Impedance."
DEFVAL { none }
::= { iOpsIADVlEntry 17 }
iOpsIADVlTransmitLoss OBJECT-TYPE
SYNTAX INTEGER (0..20)
UNITS "db"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Indicates the Transmit Loss."
DEFVAL { 0 }
::= { iOpsIADVlEntry 18 }
iOpsIADVlReceiveLoss OBJECT-TYPE
Jamp, Hsiao Informational Page 29
Definitions of Managed Objects for OPS April 2000
SYNTAX INTEGER (0..20)
UNITS "db"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
" Indicates the Receive Loss"
DEFVAL { 0 }
::= { iOpsIADVlEntry 19 }
iOpsIADVlPayloadType OBJECT-TYPE
SYNTAX INTEGER {
pcm-u-law(1),
pcm-a-law(2),
g711(3),
g726(4),
g728(5),
g723-1-5-6K(6),
g723-1-6-4K(7),
g729(8),
g729-A(9)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
" Indicates the Payload type."
DEFVAL { pcm-u-law }
::= { iOpsIADVlEntry 20 }
iOpsIADVlEchoCancellation OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Indicates if Echo Cancellation is ON or OFF."
DEFVAL { false }
::= { iOpsIADVlEntry 21 }
iOpsIADVlEchoDelay OBJECT-TYPE
SYNTAX INTEGER (0..120)
UNITS "ms"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Indicates the length of the Echo Delay in milliseconds."
DEFVAL { 0 }
::= { iOpsIADVlEntry 22 }
iOpsIADVlSilenceSuppression OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Indicates if Silence Suppression is ON or OFF."
DEFVAL { false }
Jamp, Hsiao Informational Page 30
Definitions of Managed Objects for OPS April 2000
::= { iOpsIADVlEntry 23 }
iOpsIADVlGenerateTestTone OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Indicates if Test Tone Generation is ON or OFF."
DEFVAL { false }
::= { iOpsIADVlEntry 24 }
iOpsIADVlRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Status of this entry in the iOpsIADVlTable. This variable
is used to create a new voice line for the IAD.
To create and activate the voice line, this object should
be set to 'createAndGo'.
To create the voice line in an inactive administrative
state, this object should be set to 'createAndWait'.
The voice line can then be activated later, when desired,
by setting this object to 'active'."
::= { iOpsIADVlEntry 25 }
-- *****************************************************************
--
-- IAD notification
--
-- *****************************************************************
iadNotificationPrefix OBJECT IDENTIFIER ::= { opsMIB 2 }
iadNotifications OBJECT IDENTIFIER ::= { iadNotificationPrefix 1 }
iadOperStatusChange NOTIFICATION-TYPE
OBJECTS {
iOpsIADOperStatus,
iOpsIADOperStatusLastChange
}
STATUS current
DESCRIPTION
"This notification is sent when the IAD status changes.
The following information is returned:
iOpsIADOperStatus - The new operational status of the IAD
iOpsIADOperStatusLastChange - The last time the IAD
operational status changed state"
::= { iadNotifications 1 }
softwareDownloadComplete NOTIFICATION-TYPE
Jamp, Hsiao Informational Page 31
Definitions of Managed Objects for OPS April 2000
OBJECTS {
iOpsIADDownloadSoftware
}
STATUS current
DESCRIPTION
"This notification is sent after an attempt to download the
system image file to the IAD. The status of the download is
returned in the 'iOpsIADDownloadSoftware' object-type.
The value is either:
'download complete(1)' or
'download failed(2)'"
::= { iadNotifications 2 }
configUpDownloadComplete NOTIFICATION-TYPE
OBJECTS {
iOpsIADUpDownloadConfiguration
}
STATUS current
DESCRIPTION
"This notification is sent after an attempt to download
or upload the configuration file to or from the IAD.
The status of the file transfer is returned in the
'iOpsIADUpDownloadConfiguration' object-type.
The value is either:
'up/download complete(1)' or
'up/download failed(2)'"
::= { iadNotifications 3 }
iadVoiceLineOperStatusChange NOTIFICATION-TYPE
OBJECTS {
iOpsIADVlOperStatus,
iOpsIADVlOperStatusLastChange
}
STATUS current
DESCRIPTION
"This notification is sent when the IAD voice line status
changes. The following information is returned:
iOpsIADVlOperStatus - The new operational status of IAD
voice line
iOpsIADVlOperStatusLastChange - The last time the line
status changed state"
::= { iadNotifications 4 }
voiceLineLoopbackTestComplete NOTIFICATION-TYPE
OBJECTS {
iOpsIADVlLoopbackTestResult
}
STATUS current
DESCRIPTION
"This notification is sent after attempting a loopback test
on a voice line. The 'iOpsIADVlLoopbackTestResult'
object-type returns the result of the loopback test."
::= { iadNotifications 5 }
Jamp, Hsiao Informational Page 32
Definitions of Managed Objects for OPS April 2000
-- *****************************************************************
--
-- Conformance Information
--
-- *****************************************************************
opsMIBConformance OBJECT IDENTIFIER ::= { opsMIB 3 }
opsMIBGroups OBJECT IDENTIFIER ::= { opsMIBConformance 1 }
opsMIBCompliances OBJECT IDENTIFIER ::= { opsMIBConformance 2 }
-- *****************************************************************
--
-- Compliance Statements
--
-- *****************************************************************
opsMIBCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMP entities which implement
OPS MIB."
MODULE -- this module
MANDATORY-GROUPS {
iOpsIADConfigGroup,
iOpsIADVoiceServiceGroup
}
GROUP iOpsIADSecurityConfigGroup
DESCRIPTION
"Support for public key encryption or IAD login from
external sites is optional."
OBJECT iOpsIADSoftwareFileName
SYNTAX DisplayString (SIZE(0..255))
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required if the IAD does not support
multiple system image files."
OBJECT iOpsIADSaveSoftware
SYNTAX INTEGER {
saveAndReboot(2)
}
DESCRIPTION
"'saveAndReboot' is the only value supported for IADs that
cannot contain multiple system image files."
OBJECT iOpsIADConfigFileName
SYNTAX DisplayString (SIZE(0..255))
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required if the IAD does not support
multiple configuration files."
Jamp, Hsiao Informational Page 33
Definitions of Managed Objects for OPS April 2000
OBJECT iOpsIADSaveConfiguration
SYNTAX INTEGER {
saveAndReconfigure(3)
}
DESCRIPTION
"'saveAndReconfigure' is the only value supported for IADs
that cannot support multiple configuration files."
OBJECT iOpsIADMgmtChBandwidth
SYNTAX INTEGER
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT iOpsIADMgmtChInactivityTimer
SYNTAX INTEGER (1..1000)
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT iOpsIADDateAndTime
SYNTAX DateAndTime
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT iOpsIADPublicIPAddress
SYNTAX IpAddress
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT iOpsIADSubnetMask
SYNTAX IpAddress
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT iOpsIADGateway
SYNTAX IpAddress
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT iOpsIADDHCPIP
SYNTAX IpAddress
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT iOpsIADServerType
SYNTAX INTEGER {
tftpServer(1)
}
Jamp, Hsiao Informational Page 34
Definitions of Managed Objects for OPS April 2000
DESCRIPTION
"TFTP service from the Server is required. Other kinds
of file transfer protocols are optional."
OBJECT iOpsIADVlRowStatus
SYNTAX INTEGER {
active(1),
createAndGo(4),
destroy(6)
}
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required, and only three of the six
enumerated values for the RowStatus textual convention
are supported."
::= { opsMIBCompliances 1 }
-- *****************************************************************
--
-- Units of Conformance
--
-- *****************************************************************
iOpsIADConfigGroup OBJECT-GROUP
OBJECTS {
iOpsIADIfIndex,
iOpsIADSerialNumber,
iOpsIADCLEICode,
iOpsIADAdminStatus,
iOpsIADOperStatus,
iOpsIADAlarmStatus,
iOpsIADOperStatusLastChange,
iOpsIADResetIAD,
iOpsIADSoftwareFileName,
iOpsIADSoftwareUpgradeFileName,
iOpsIADDownloadSoftware,
iOpsIADSaveSoftware,
iOpsIADSoftwareVersion,
iOpsIADReConfigIAD,
iOpsIADConfigFileName,
iOpsIADConfigUpgradeFileName,
iOpsIADUpDownloadConfiguration,
iOpsIADSaveConfiguration,
iOpsIADVersionConfig,
iOpsIADMgmtChType,
iOpsIADMgmtChNumber,
iOpsIADMgmtChBandwidth,
iOpsIADMgmtChInactivityTimer,
iOpsIADDataService,
iOpsIADMacAddress,
iOpsIADPublicIPAddress,
iOpsIADSubnetMask,
iOpsIADGateway,
iOpsIADDHCPIP,
Jamp, Hsiao Informational Page 35
Definitions of Managed Objects for OPS April 2000
iOpsIADServerIP,
iOpsIADServerType,
iOpsIADServerLoginName,
iOpsIADServerPasswd
}
STATUS current
DESCRIPTION
"A collection of objects that support the configuration
of the IAD."
::= { opsMIBGroups 1 }
iOpsIADSecurityConfigGroup OBJECT-GROUP
OBJECTS {
iOpsIADMasPublicKey,
iOpsIADManagementPasswd
}
STATUS current
DESCRIPTION
"A collection of objects pertaining to security."
::= { opsMIBGroups 2 }
iOpsIADVoiceServiceGroup OBJECT-GROUP
OBJECTS {
iOpsIADVlNumber,
iOpsIADVlDS1IfIndex,
iOpsIADVlDS0Index,
iOpsIADVlOperStatus,
iOpsIADVlSecondaryServiceState,
iOpsIADVlAdminStatus,
iOpsIADVlLoopbackTestResult ,
iOpsIADVlNumberOfWires,
iOpsIADVlSignalFunctionCode,
iOpsIADVlRobbedBitMode,
iOpsIADVlCallReferenceValue,
iOpsIADVlRingingCadence,
iOpsIADVlVoiceProtocolType,
iOpsIADVlPhoneNumber,
iOpsIADVlTransmitImpedance,
iOpsIADVlReceiveImpedance,
iOpsIADVlTransmitLoss,
iOpsIADVlReceiveLoss,
iOpsIADVlPayloadType,
iOpsIADVlEchoCancellation,
iOpsIADVlEchoDelay,
iOpsIADVlSilenceSuppression,
iOpsIADVlGenerateTestTone,
iOpsIADVlRowStatus
}
STATUS current
DESCRIPTION
"A collection of objects that support the phone services
at the IAD."
::= { opsMIBGroups 3 }
Jamp, Hsiao Informational Page 36
Definitions of Managed Objects for OPS April 2000
END
6. Security Considerations
There are a number of management objects defined in this MIB that
have a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on
network operations. There are a number of managed objects in this
MIB that may be service affecting if not SET properly. These are:
* iOpsIADResetIAD
* iOpsIADSoftwareUpgradeFileName
* iOpsIADDownloadSoftware
* iOpsIADSaveSoftware
* iOpsIADReConfigIAD
* iOpsIADConfigUpgradeFileName
* iOpsIADUpDownloadConfiguration
* iOpsIADSaveConfiguration
It is therefore important to control access to these objects. Not
all versions of SNMP provide features for such a secure environment.
SNMPv1 by itself is not a secure environment. Even if the network
itself is secure (for example by using IPSec), even then, there is
no control as to who on the secure network is allowed to access and
can GET/SET (read/change/create/delete) the objects in the OPS MIB.
It is recommended that implementers consider the security features
provided by the SNMPv3 framework. Specifically, the use of the User-
based Security Model, RFC 2274 [26] and the View-based Access
Control Model RFC 2275 [27] are recommended.
It is then a customer/user responsibility to ensure that the SNMP
entity giving access to an instance of this MIB, is configured to
give access to the objects only to those principals (users) that
have legitimate rights to indeed GET or SET (change/create/delete)
them.
7. References
[1] S. Bradner, "The Internet Standards Process -- Revision 3," BCP
9, RFC 2026, October 1996
[2] K. McCloghrie, M. Rose, S. Waldbusser, "Structure of Management
Information for Version 2 of the Simple Network Management Protocol
(SNMPv2)," RFC 1902, January 1996
[3] K. McCloghrie, M. Rose, Editors, "Management Information Base
for Network Management of TCP/IP-based Internets: MIB-II," STD 17,
RFC 1213, March 1991
Jamp, Hsiao Informational Page 37
Definitions of Managed Objects for OPS April 2000
[4] M. Fedor, M. Schoffstall, J. Davin, "A Simple Network Management
Protocol (SNMP)," RFC 1157, May 1990
[5] J. Case, K. McCloghrie, M. Rose, S. Waldbusser, "Protocol
Operations for Version 2 of the Simple Network Management Protocol
(SNMPv2)," RFC 1905, January 1996
[6] J. Case, K. McCloghrie, M. Rose, S. Waldbusser, "Textual
Conventions for Version 2 of the Simple Network Management Protocol
(SNMPv2)," RFC 1903, January 1996
[7} J. Case, K. McCloghrie, M. Rose, S. Waldbusser, "Conformance
Statements for Version 2 of the Simple Network Management Protocol
(SNMPv2)," RFC 1904, January 1996
[8] Bellcore, "Integrated Digital Loop Carrier System Generic
Requirements, Objectives, and Interface (A module of TSGR, FR-440,
GR-303-CORE Issue 2," December 1998
[9] D. Fowler, Editor, "Definitions of Managed Objects for the DS0
and DS0 Bundle Interface Type," RFC 2494, January 1999
[10] D. Fowler, Editor, "Definitions of Managed Objects for the DS1,
E1, DS2 and E2 Interface Types," RFC 2495, January 1999
[11] D. Fowler, Editor, "Definitions of Managed Objects for the
DS3/E3 Interface Type," RFC 2496, January 1999
[12] K. Tesink, "Definitions of Managed Objects for the SONET/SDH
Interface Type," RFC 2558, March 1999
[13] T. Brown, Editor, "Definitions of Managed Objects for Frame
Relay Service," RFC 1604, March 1994
[14] F. Kastenholz, "The Definitions of Managed Objects for the Link
Control Protocol of the Point-to-Point Protocol," RFC 1471, June
1993
[15] F. Kastenholz, "The Definitions of Managed Objects for the
Security Protocols of the Point-to-Point Protocol," RFC 1472, June
1993
[16] F. Kastenholz, "The Definitions of Managed Objects for the IP
Network Control Protocol of the Point-to-Point Protocol," RFC 1473,
June 1993
[17] F. Kastenholz, "The Definitions of Managed Objects for the
Bridge Network Control Protocol of the Point-to-Point Protocol," RFC
1474, June 1993
[18] M. Noto, E. Spiegel, K. Tesink, Editors, "Definitions of
Textual Conventions and OBJECT-IDENTITIES for ATM Management," RFC
2514, February 1999
Jamp, Hsiao Informational Page 38
Definitions of Managed Objects for OPS April 2000
[19] K. Tesink, Editor, "Definitions of Managed Objects for ATM
Management," RFC 2515, February 1999
[20] J. Flick, J. Johnson, "Definitions of Managed Objects for the
Ethernet-like Interface Types," RFC 2665, August 1999
[21] K. McCloghrie, Editor, "SNMPv2 Management Information Base for
the Internet Protocol using SMIv2," RFC 2011, November 1996
[22] K. McCloghrie, Editor, "SNMPv2 Management Information Base for
the Transmission Control Protocol using SMIv2," RFC 2012, November
1996
[23] K. McCloghrie, Editor, "SNMPv2 Management Information Base for
the User Datagram Protocol using SMIv2," RFC 2013, November 1996
[24] M. Greene, J. Luciani, K. White, T. Kuo, "Definitions of
Managed Objects for Classical IP and ARP Over ATM Using SMIv2 (IPOA-
MIB)," RFC 2320, April 1998
[25] G. Bathrick, F. Ly, "Definitions of Managed Objects for the
ADSL Lines," RFC 2662, August 1999
[26] U. Blumenthal, B. Wijnen, "User-based Security Model (USM) for
version 3 of the Simple Network Management Protocol (SNMPv3)," RFC
2274, January 1998
[27] B. Wijnen, R. Presuhn, "View-based Access Control Model (VACM)
for the Simple Network Management Protocol (SNMP)," RFC 2275,
January 1998
8. Author's Addresses
Ray Jamp
ANDA Networks, Inc.
2921 Copper Road
Santa Clara, CA 95051
USA
Phone: +1-408-990-4900
Email: rjamp@andanetworks.com
URL: http://www.andanetworks.com
Yu-Jen Hsiao
ANDA Networks, Inc.
2921 Copper Road
Santa Clara, CA 95051
USA
Phone: +1-408-990-4900
Email: yjhsiao@andanetworks.com
URL: http://www.amnanetworks.com
9. Expiration Date
Expires October 13, 2000
Jamp, Hsiao Informational Page 39
Definitions of Managed Objects for OPS April 2000
10. Full Copyright Statement
Copyright (C) The Internet Society (2000). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph
are included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE."
Jamp, Hsiao Informational Page 40