Paradyne 3700-A2-GB20-10 инструкция обслуживания
- Просмотреть online или скачать инструкцию
- 120 страниц
- 0.4 mb
Идти на страницу of
Похожие руководства по эксплуатации
-
Network Router
Paradyne 8310
136 страниц 1.31 mb -
Network Router
Paradyne 9550 DS3
20 страниц 0.41 mb -
Network Router
Paradyne 9820-2M
166 страниц 1.54 mb -
Network Router
Paradyne 6218-I1
92 страниц 1.5 mb -
Network Router
Paradyne 8312, 8314
136 страниц 1.31 mb -
Network Router
Paradyne 6210
46 страниц 2.62 mb -
Network Router
Paradyne 3700-A2-GB20-10
120 страниц 0.4 mb -
Network Router
Paradyne 8779
182 страниц 0.96 mb
Хорошее руководство по эксплуатации
Законодательство обязывает продавца передать покупателю, вместе с товаром, руководство по эксплуатации Paradyne 3700-A2-GB20-10. Отсутствие инструкции либо неправильная информация, переданная потребителю, составляют основание для рекламации в связи с несоответствием устройства с договором. В законодательстве допускается предоставлении руководства в другой, чем бумажная форме, что, в последнее время, часто используется, предоставляя графическую или электронную форму инструкции Paradyne 3700-A2-GB20-10 или обучающее видео для пользователей. Условием остается четкая и понятная форма.
Что такое руководство?
Слово происходит от латинского "instructio", тоесть привести в порядок. Следовательно в инструкции Paradyne 3700-A2-GB20-10 можно найти описание этапов поведения. Цель инструкции заключается в облегчении запуска, использования оборудования либо выполнения определенной деятельности. Инструкция является набором информации о предмете/услуге, подсказкой.
К сожалению немного пользователей находит время для чтения инструкций Paradyne 3700-A2-GB20-10, и хорошая инструкция позволяет не только узнать ряд дополнительных функций приобретенного устройства, но и позволяет избежать возникновения большинства поломок.
Из чего должно состоять идеальное руководство по эксплуатации?
Прежде всего в инструкции Paradyne 3700-A2-GB20-10 должна находится:
- информация относительно технических данных устройства Paradyne 3700-A2-GB20-10
- название производителя и год производства оборудования Paradyne 3700-A2-GB20-10
- правила обслуживания, настройки и ухода за оборудованием Paradyne 3700-A2-GB20-10
- знаки безопасности и сертификаты, подтверждающие соответствие стандартам
Почему мы не читаем инструкций?
Как правило из-за нехватки времени и уверенности в отдельных функциональностях приобретенных устройств. К сожалению само подсоединение и запуск Paradyne 3700-A2-GB20-10 это слишком мало. Инструкция заключает ряд отдельных указаний, касающихся функциональности, принципов безопасности, способов ухода (даже то, какие средства стоит использовать), возможных поломок Paradyne 3700-A2-GB20-10 и способов решения проблем, возникающих во время использования. И наконец то, в инструкции можно найти адресные данные сайта Paradyne, в случае отсутствия эффективности предлагаемых решений. Сейчас очень большой популярностью пользуются инструкции в форме интересных анимаций или видео материалов, которое лучше, чем брошюра воспринимаются пользователем. Такой вид инструкции позволяет пользователю просмотреть весь фильм, не пропуская спецификацию и сложные технические описания Paradyne 3700-A2-GB20-10, как это часто бывает в случае бумажной версии.
Почему стоит читать инструкции?
Прежде всего здесь мы найдем ответы касательно конструкции, возможностей устройства Paradyne 3700-A2-GB20-10, использования отдельных аксессуаров и ряд информации, позволяющей вполне использовать все функции и упрощения.
После удачной покупки оборудования/устройства стоит посвятить несколько минут для ознакомления с каждой частью инструкции Paradyne 3700-A2-GB20-10. Сейчас их старательно готовят или переводят, чтобы они были не только понятными для пользователя, но и чтобы выполняли свою основную информационно-поддерживающую функцию.
Содержание руководства
-
Страница 1
AREA CODE CHANGE Please note that the area code for Paradyne Corporation in Largo, Florida has changed from 813 to 727. For any Paradyne telephone number that appears in this manual with an 813 area code, dial 727 instead.[...]
-
Страница 2
COMSPHERE 6700 SERIES NETWORK MANAGEMENT SYSTEM SNMP PROXY AGENT FEA TURE USER’S GUIDE Document No. 6700-A2-GB20-10[...]
-
Страница 3
A Issue 2 December 1996 COMSPHERE 6700 Series Network Management System SNMP Proxy Agent Featur e User ’s Guide 6700-A2-GB20-10 Issue 2 (December 1996) Changes and enhancements to the product and to the information herein will be documented and issued as a new release. W arranty , Sales, and Service Information Contact your sales or service repre[...]
-
Страница 4
i Issue 2 December 1996 Preface Related Documents v . . . . . . . . . . . . . . . . . . . . . . . . . . . Ordering Information vi . . . . . . . . . . . . . . . . . . . . . 1 Overview What is SNMP? 1-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . What is the SNMP Proxy Agent Feature? 1-1 . . . . . [...]
-
Страница 5
ii Issue 2 December 1996 3 Management Information Bases MIB-II Support 3-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MIB-II System Group Overview 3-2 . . . . . . . . . . . . MIB-II Interface Group Overview 3-2 . . . . . . . . . . . COMSPHERE 6700 Series NMS Enterprise MIBs 3-3 . . . . . . . . . .[...]
-
Страница 6
iii Issue 2 December 1996 Figures 1 Overview 1-1 Sample SNMP Network T opology 1-3 . . . . . . . . . . 2 Installation 2-1 Welcome Window 2-5 . . . . . . . . . . . . . . . . . . . . . . . . 2-2 Product Information Window 2-6 . . . . . . . . . . . . . . 2-3 Destination Directory Window 2-6 . . . . . . . . . . . . . 2-4 Confirmatio[...]
-
Страница 7
iv Issue 2 December 1996 T ables 2 Installation 2-1 Supported Network Adapter Boards 2-2 . . . . . . . . 3 Management Information Bases 3-1 MIB Browser Output T able 3-2 . . . . . . . . . . . . . . . . 3-2 Primary Alert T raps 3-8 . . . . . . . . . . . . . . . . . . . . . . 3-3 System Security Event T raps 3-9 . . . . . . . . . . . [...]
-
Страница 8
v Issue 2 December 1996 P reface This guide describes how to install and use the COMSPHERE r 6700 Series Network Management System (NMS) SNMP Proxy Agent feature. This manual assumes you have a basic understanding of COMSPHERE modems and data service units (DSUs) and their operation, are knowledgeable about data communications, and are familiar wit[...]
-
Страница 9
Preface vi Issue 2 December 1996 3910-A2-GN32 COMSPHERE 3900 Series Modems, Models 3910 and 391 1, Point–to–Point/Multipoint, Installation and Operation Manual 6700-A2-GB21 COMSPHERE 6700 Series Network Management System Multiuser Feature User ’s Guide 6700-A2-GB22 COMSPHERE 6700 Series Network Management System Network Configuration Guide 67[...]
-
Страница 10
1-1 Issue 2 December 1996 Overview 1 What is SNMP? Simple Network Management Protocol (SNMP) is an Internet standard protocol for managing TCP/IP devices. Using SNMP , a network administrator can address queries and commands to network nodes and devices. Y ou can use SNMP to monitor network performance and status; control operational parameters; an[...]
-
Страница 11
Overview 1-2 Issue 2 December 1996 Software Description The SNMP Proxy Agent feature includes NetManage Enhanced Windows TCP/IP (NEWT t ) software, which supports transmission of SNMP messages across Ethernet r , T oken Ring, FDDI, SLIP , and PPP interfaces. The SNMP Proxy Agent feature is a software package that can be installed on top of the COMS[...]
-
Страница 12
Overview 1-3 Issue 2 December 1996 Integrated TCP/IP , UDP/IP , and SNMP Protocol support Concurrent Ethernet, T oken Ring, FDDI, SLIP , and PPP interface support Sample SNMP Network T opology Figure 1-1 shows a sample SNMP network topology . Figure 1-1. Sample SNMP Network T opology[...]
-
Страница 13
Overview 1-4 Issue 2 December 1996 SNMP Proxy Agent Featur e Package Contents The SNMP Proxy Agent feature package includes the following: SNMP feature software on one 3 1/2 ″ disk COMSPHERE 6700 MIBs 3 1/2 ″ disk One COMSPHERE 6700 Series Network Management System SNMP Proxy Agent Feature User ’s Guide One COMSPHERE 6700 Seri[...]
-
Страница 14
2-1 Issue 2 December 1996 Installation 2 Hardware and Softwar e Requirements The SNMP Proxy Agent feature has the same hardware and software requirements as the basic single-user NMS. Refer to the Hardware Description and Software Description sections of the COMSPHERE 6700 Series Network Management System User ’s Guide for details. Supported Netw[...]
-
Страница 15
Installation 2-2 Issue 2 December 1996 T able 2-1. Supported Network Adapter Boards (1 of 2) Interface V endor Model Ethernet 3COM 3C501 Ether Link 3C503 Ether Link II 3C505 Ether Link Plus 3C507 Ether Link 16 3C509 Ether Link III 3C523 Ether Link/MC TP 3C527 Ether Link/MC 32 Allied T elesis A T -1500 Network Adapter Hewlett Packard r HP27247/HP272[...]
-
Страница 16
Installation 2-3 Issue 2 December 1996 T able 2-1. Supported Network Adapter Boards (2 of 2) Interface Model V endor Ethernet Xircom (Continued) All PE3 Models Other (NDIS Driver Required) T oken Ring IBM r 16/4 T oken Ring Adapter Xircom All PT Models Madge Smart 16/4 RingNode adapter Proteon r p139X p189X p1990 Raycone 16/4 T oken Ring Adapter Ot[...]
-
Страница 17
Installation 2-4 Issue 2 December 1996 SNMP Feature Installation and Configuration Information General Where to install the software (c:pcnms): Network Interface Name (Ethernet0): Network Interface T ype (Ethernet): Workstation Internet Address of Workstation (192.0.2.2): Unique Node Name (Largo Bld. G): SNMP Manager Internet Address of Manager (1[...]
-
Страница 18
Installation 2-5 Issue 2 December 1996 Installing the SNMP Proxy Agent Feature T o install the SNMP Proxy Agent feature software, start from the Program Manager window and perform the following steps: 1. Insert Disk #1 into Drive A. 2. From the Program Manager window , choose File . 3. From the File menu, choose Run . 4. In the Command Line field, [...]
-
Страница 19
Installation 2-6 Issue 2 December 1996 6. Choose Continue . The Product Information window appears, as shown in Figure 2-2. Figure 2-2. Pr oduct Information Window 7. Choose Ye s . The Destination Directory window appears, as shown in Figure 2-3. Figure 2-3. Destination Dir ectory Window The Destination Directory window allows you to place the NMS [...]
-
Страница 20
Installation 2-7 Issue 2 December 1996 9. Choose Continue . The Confirmation window appears, as shown in Figure 2-4. Figure 2-4. Confirmation W indow 10. Choose Install to confirm the installation of the NMS software into the specified directory . The Completion status window appears, as shown in Figure 2-5. Figure 2-5. Completion Status W indow Th[...]
-
Страница 21
Installation 2-8 Issue 2 December 1996 Figure 2-6. Installation Completed! W indow 1 1. Choose OK . Configuring the SNMP Proxy Agent Feature for TCP/IP Networks After installation, use the Network Configuration application to customize your configuration for TCP/IP networks. For details on doing so, refer to the COMSPHERE 6700 Series Network Manage[...]
-
Страница 22
3-1 Issue 2 December 1996 Management Information Bases 3 MIB-II Support The SNMP Proxy Agent feature includes support for the standard Management Information Base (MIB-II) used with network management protocols in TCP/IP-based internets. This support is provided by the NEWT component. The following MIB-II groups are supported as specified in [...]
-
Страница 23
Management Information Bases 3-2 Issue 2 December 1996 MIB-II System Group Overview The MIB-II system group contains system description information. Y ou may customize the sysContact , sysName , and sysLocation text. For further details, refer to the NEWT TCP/IP for Windows Installation and User ’ s Guide. MIB browser output examples for the syst[...]
-
Страница 24
Management Information Bases 3-3 Issue 2 December 1996 COMSPHERE 6700 Series NMS Enterprise MIBs Four new enterprise Management Information Base (MIB) definitions are introduced with SNMP Proxy Agent Release 1.0: COMSPHERE 6700 NMS MIB COMSPHERE 6700 Device MIB Front Panel MIB Call Directory MIB NOTE: For additional installation inf[...]
-
Страница 25
Management Information Bases 3-4 Issue 2 December 1996 Figure 3-1. SMI Defined Object Identifier Pr efix T ree The COMSPHERE 6700 NMS and Device MIBs are defined in the appendices.[...]
-
Страница 26
Management Information Bases 3-5 Issue 2 December 1996 COMSPHERE 6700 NMS MIB Overview The NMS MIB administers the 6700 Series NMS. The following groups are defined in the NMS MIB. NMS Administration Group NMS System Group NMS Device Group NMS Manager Group NMS T est Group Refer to Appendix A for a full description of the COMSPH[...]
-
Страница 27
Management Information Bases 3-6 Issue 2 December 1996 Front Panel MIB Overview The Front Panel MIB provides remote access to the front panel of a device and is accessed using the community procedures used for the 6700 Device MIB. Front panel keypress codes can be sent to the device in Set requests. The current front panel display can be retrieved [...]
-
Страница 28
Management Information Bases 3-7 Issue 2 December 1996 SNMP T raps Overview COMSPHERE 6700 NMS alerts may be exported to authorized SNMP managers as SNMP traps. T raps are forwarded for any event that makes it through the COMSPHERE 6700 Series NMS’s alert filter . All traps are enterprise specific, with an OBJECT IDENTIFIER specifying the COMSPHE[...]
-
Страница 29
Management Information Bases 3-8 Issue 2 December 1996 NOTE: The state of a device’s primary alerts can also be read from devStatusAlert . T able 3-2. Primary Alert T raps (1 of 2) T rap Primary Alert T raps 3600 3800 3900 1 Device Failure D D D 2 Configuration Change Notify D D D 3 T est Mode D D D 4 Disabled D D D 5 Out of Threshold/VF Threshol[...]
-
Страница 30
Management Information Bases 3-9 Issue 2 December 1996 T able 3-2. Primary Alert T raps (2 of 2) 3900 3800 3600 Primary Alert T raps T rap 21 T ributary Timeout D 22 Dial T one D 23 Redundant Power Supply D 32 No Response D D D T able 3-3 identifies which system security event traps apply to the specific devices. T able 3-3. System Security Event T[...]
-
Страница 31
Management Information Bases 3-10 Issue 2 December 1996 T able 3-3. System Security Event T raps (2 of 2) 3900 3800 3600 System Security Event T raps T rap 11 2 Invalid Access Time D D 11 3 User Login Hack - Multiple Sequential Password Retries D D 11 4 Device Security T able Invalid D D 11 6 Security Download Failed D D 11 7 Front Panel Modificati[...]
-
Страница 32
Management Information Bases 3-1 1 Issue 2 December 1996 T able 3-4. Primary Alert Clear Notifications (2 of 2) 3900 3800 3600 Primary Alert T raps T rap 213 Primary Channel Interrupted Cleared D D 214 Firmware Downloading Cleared D D 215 Make Busy Mode Cleared D D 216 Service Line Cleared D D 217 Non-answering Modem Cleared D D 218 Short Holding T[...]
-
Страница 33
Management Information Bases 3-12 Issue 2 December 1996 The community names for the Device MIB are generated by appending the desired device name to the appropriate base name. Consider the following rules when creating community names: Community names should not be the prefix of a device name. Write community names can be used for both read[...]
-
Страница 34
A-1 Issue 2 December 1996 MIB Definition A NMS6700-MIB DEFINITIONS ::= BEGIN –– T itle: COMSPHERE 6700 NMS MIB for Customer Network Management –– Copyright (C) 1996, Paradyne. All rights reserved. –– –– This file may be freely copied and distributed as –– long as no changes are made to it. –– The NMS MIB contains attributes [...]
-
Страница 35
MIB Definition A-2 Issue 2 December 1996 –– –– NMS MIB Groups –– nmsAdmin OBJECT IDENTIFIER ::= { nms 1 }–– administration nmsSystem OBJECT IDENTIFIER ::= { nms 2 }–– system identity nmsDevice OBJECT IDENTIFIER ::= { nms 3 }–– 6700 devices nmsManager OBJECT IDENTIFIER ::= { nms 4 }–– SNMP managers nmsT est OBJECT IDENTIF[...]
-
Страница 36
MIB Definition A-3 Issue 2 December 1996 –– NMS Administration Group (nms 1) –– NMS Information nmsAdminName OBJECT -TYPE SYNT AX DisplayString (SIZE (0..15)) ACCESS read-write ST A TUS mandatory DESCRIPTION ”Name of the 6700 NMS.” ::= { nmsAdmin 1 } nmsAdminLocation OBJECT -TYPE SYNT AX DisplayString (SIZE (0..40)) ACCESS read-write ST[...]
-
Страница 37
MIB Definition A-4 Issue 2 December 1996 access to all objects in the COMSPHERE 6700 NMS MIB. An exception applies with the nmsAdminNmsW riteCommunity object for which the read community provides no access.” ::= { nmsAdmin 5 } nmsAdminNmsW riteCommunity OBJECT -TYPE SYNT AX DisplayString (SIZE (0..32)) ACCESS read-only ST A TUS mandatory DESCRIPT[...]
-
Страница 38
MIB Definition A-5 Issue 2 December 1996 –– NMS System Group (nms 2) –– T ime of Day nmsSystemT ime OBJECT -TYPE SYNT AX DateAndT ime ACCESS read-only ST A TUS mandatory DESCRIPTION ”Specifies the date and time in RFC 1514 DateAndT ime format. The date and time are obtained from the system clock of the workstation running the proxy agent [...]
-
Страница 39
MIB Definition A-6 Issue 2 December 1996 –– Layout of one entry in nmsSystemFeatureT able. NmsSystemFeatureEntry ::= SEQUENCE { nmsSystemFeatureIndex INTEGER, nmsSystemFeatureName DisplayString, nmsSystemFeatureV ersion DisplayString, nmsSystemFeatureSerial DisplayString } –– Index nmsSystemFeatureIndex OBJECT -TYPE SYNT AX INTEGER ACCESS r[...]
-
Страница 40
MIB Definition A-7 Issue 2 December 1996 ::= { nmsSystemFeatureEntry 3 } –– Serial Number nmsSystemFeatureSerial OBJECT -TYPE SYNT AX DisplayString (SIZE (0..25)) ACCESS read-only ST A TUS mandatory DESCRIPTION ”Serial number of system product or feature. If feature has no serial number , this object contains a zero length string.” ::= { nm[...]
-
Страница 41
MIB Definition A-8 Issue 2 December 1996 –– NMS Device Group (nms 3) nmsDevices OBJECT -TYPE SYNT AX INTEGER ACCESS read-only ST A TUS mandatory DESCRIPTION ”The number of devices configured in the 6700 nms network. This is also the number of entries in nmsDeviceT able.” ::= { nmsDevice 1 } nmsDeviceT able OBJECT -TYPE SYNT AX SEQUENCE OF N[...]
-
Страница 42
MIB Definition A-9 Issue 2 December 1996 ”This object is the row index of the nmsDevice table. Note that a device’ s index in the table may change as devices are added or removed from the 6700 nms network, thus this index should not be used as a device ID.” ::= { nmsDeviceEntry 1 } nmsDeviceName OBJECT -TYPE SYNT AX DisplayString (SIZE (0..15[...]
-
Страница 43
MIB Definition A-10 Issue 2 December 1996 DESCRIPTION ”An entry in the manager table. Entries are indexed by IP Address.” INDEX { nmsManagerAddress } ::= { nmsManagerT able 1 } –– Layout of one entry in nmsManagerT able. NmsManagerEntry ::= SEQUENCE { nmsManagerAddress IpAddress, nmsManagerName DisplayString, nmsManagerAccess INTEGER, nmsMa[...]
-
Страница 44
MIB Definition A-1 1 Issue 2 December 1996 ST A TUS mandatory DESCRIPTION ”This object is the NMS manager name. The manager name must be unique in the table. If a set operation is performed for a non-existing instance (i.e., index is a new IP address), a new table entry for the specified IP address will be created. The new entry’ s nmsManagerAc[...]
-
Страница 45
MIB Definition A-12 Issue 2 December 1996 nmsManagerLocation OBJECT -TYPE SYNT AX DisplayString (SIZE (0..40)) ACCESS read-write ST A TUS mandatory DESCRIPTION ”T ext string describing manager location.” ::= { nmsManagerEntry 5 } –– Contact1 nmsManagerContact1 OBJECT -TYPE SYNT AX DisplayString (SIZE (0..40)) ACCESS read-write ST A TUS mand[...]
-
Страница 46
MIB Definition A-13 Issue 2 December 1996 –– NMS T est Group (nms 5) –– T extual Convention for T est Result V alidity Indicator T estResultV alidity ::= INTEGER { valid-final(1), valid-intermediate(2), not-available-yet(3), count-overflow(4), not-used(5) } –– Number of T est T able Entries nmsT estEntries OBJECT -TYPE SYNT AX INTEGER A[...]
-
Страница 47
MIB Definition A-14 Issue 2 December 1996 nmsT estEntry OBJECT -TYPE SYNT AX NmsT estEntry ACCESS not-accessible ST A TUS mandatory DESCRIPTION ”An entry in the nms test table.” INDEX { nmsT estIndex } ::= { nmsT estT able 1 }[...]
-
Страница 48
MIB Definition A-15 Issue 2 December 1996 –– Layout of one entry in nmsT estT able. NmsT estEntry ::= SEQUENCE { nmsT estIndex INTEGER, nmsT estDeviceName DisplayString, nmsT estT ype INTEGER, nmsT estDuration INTEGER, nmsT estPortNumber INTEGER, nmsT estRemoteName DisplayString, nmsT estStatus INTEGER, nmsT estLocalT otalSecondsV alidity T est[...]
-
Страница 49
MIB Definition A-16 Issue 2 December 1996 nmsT estRemoteT otalBlocks INTEGER, nmsT estRemoteErrorBlocksV alidity T estResultV alidity , nmsT estRemoteErrorBlocks INTEGER, nmsT estTimeOutsV alidity T estResultV alidity , nmsT estTimeOuts INTEGER, nmsT estOwner DisplayString, nmsT estEntryStatus INTEGER } –– Index nmsT estIndex OBJECT -TYPE SYNT [...]
-
Страница 50
MIB Definition A-17 Issue 2 December 1996 SYNT AX INTEGER { self-test(1), local-loop(2), rem-digital-loop(3), loc-digital-loop(4), dte-loop(5), bert(6), local-loop-bert(7), rdl-bert(8), digital-test(9), end-to-end-test(10), abort(1 1) } ACCESS read-write ST A TUS mandatory DESCRIPTION ”This object is the test type. T est type self-test(1) perform[...]
-
Страница 51
MIB Definition A-18 Issue 2 December 1996 SYNT AX INTEGER ACCESS read-write ST A TUS mandatory DESCRIPTION ”T est duration in seconds (or blocks). Only applicable for the following test types: bert, local-loop-bert, rdl-bert, digital-test, end-to-end-test.” ::= { nmsT estEntry 4 } –– –– Port Number –– nmsT estPortNumber OBJECT -TYPE[...]
-
Страница 52
MIB Definition A-19 Issue 2 December 1996 ::= { nmsT estEntry 6 } –– –– T est Status –– nmsT estStatus OBJECT -TYPE SYNT AX INTEGER { idle(1), testMode(2), testRunning(3), testAborted(4), testFailed(5) } ACCESS read-only ST A TUS mandatory DESCRIPTION ”T est status. Status of idle(1) indicates that the device is not in test mode (from[...]
-
Страница 53
MIB Definition A-20 Issue 2 December 1996 nmsT estLocalT otalSeconds OBJECT -TYPE SYNT AX INTEGER ACCESS read-only ST A TUS mandatory DESCRIPTION ”T otal seconds for local device. (For 3600 model type devices, this variable is also called elapsed seconds.)” ::= { nmsT estEntry 9 } –– Local Error Seconds nmsT estLocalErrorSecondsV alidity OB[...]
-
Страница 54
MIB Definition A-21 Issue 2 December 1996 –– Local Error Blocks (Bits for 3600 DSU) nmsT estLocalErrorBlocksV alidity OBJECT -TYPE SYNT AX T estResultV alidity ACCESS read-only ST A TUS mandatory DESCRIPTION ”V alidity of the nmsT estLocalErrorBlocks test result object.” ::= { nmsT estEntry 14 } nmsT estLocalErrorBlocks OBJECT -TYPE SYNT AX[...]
-
Страница 55
MIB Definition A-22 Issue 2 December 1996 DESCRIPTION ”V alidity of the nmsT estRemoteErrorSeconds test result object.” ::= { nmsT estEntry 18 } nmsT estRemoteErrorSeconds OBJECT -TYPE SYNT AX INTEGER ACCESS read-only ST A TUS mandatory DESCRIPTION ”Errored seconds elapsed for the remote device. (The value is not used for 3600 model type devi[...]
-
Страница 56
MIB Definition A-23 Issue 2 December 1996 ST A TUS mandatory DESCRIPTION ”Remote Error blocks (actually Bits). Not used for 3800 and 3900 model type devices.)” ::= { nmsT estEntry 23 } –– T ime Outs nmsT estT imeOutsV alidity OBJECT -TYPE SYNT AX T estResultV alidity ACCESS read-only ST A TUS mandatory DESCRIPTION ”V alidity of the nmsT e[...]
-
Страница 57
MIB Definition A-24 Issue 2 December 1996 –– Entry Status nmsT estEntryStatus OBJECT -TYPE SYNT AX INTEGER { valid(1), createRequest(2), underCreation(3), invalid(4) } ACCESS read-write ST A TUS mandatory DESCRIPTION ”The status of this nmsT estT able entry . Setting this object to the value invalid(4) has the effect of invalidating the corre[...]
-
Страница 58
B-1 Issue 2 December 1996 Device Enterprise MIB Definition B NMS6700-DEV -MIB DEFINITIONS ::= BEGIN –– T itle: COMSPHERE 6700 Device MIB for Customer Network Management –– –– Copyright (C) 1996, Paradyne. All rights reserved. –– –– This file may be freely copied and distributed as –– long as no changes are made to it. [...]
-
Страница 59
Device Enterprise MIB Definition B-2 Issue 2 December 1996 –– –– Enterprise Identification for COMSPHERE 6700 Device MIB –– dev OBJECT IDENTIFIER ::= { nms-6700 2 } –– Device MIB –– Device MIB Groups devAdmin OBJECT IDENTIFIER ::= { dev 1 } –– administration devIdentity OBJECT IDENTIFIER ::= { dev 2 } –– device identity [...]
-
Страница 60
Device Enterprise MIB Definition B-3 Issue 2 December 1996 –– Device Administration Group (dev 1) devAdminName OBJECT -TYPE SYNT AX DisplayString (SIZE (0..15)) ACCESS read-only ST A TUS mandatory DESCRIPTION ”Device name. This is the name used by the COMSPHERE 6700 NMS to identify the device.” ::= { devAdmin 1 } devAdminAdpAddress OBJECT -[...]
-
Страница 61
Device Enterprise MIB Definition B-4 Issue 2 December 1996 devAdminCabinet OBJECT -TYPE SYNT AX DisplayString (SIZE (0..15)) ACCESS read-only ST A TUS mandatory DESCRIPTION ”Device cabinet name used by COMSPHERE 6700 NMS.” ::= { devAdmin 5 } devAdminCarrier OBJECT -TYPE SYNT AX DisplayString (SIZE (0..15)) ACCESS read-only ST A TUS mandatory DE[...]
-
Страница 62
Device Enterprise MIB Definition B-5 Issue 2 December 1996 ”Device contact string #2.” ::= { devAdmin 10 } devAdminComment OBJECT -TYPE SYNT AX DisplayString (SIZE (0..40)) ACCESS read-only ST A TUS mandatory DESCRIPTION ”Device comment string.” ::= { devAdmin 1 1 } devAdminDbmOption OBJECT -TYPE SYNT AX INTEGER { dbm-installed(1), dbm-not-[...]
-
Страница 63
Device Enterprise MIB Definition B-6 Issue 2 December 1996 multi point option is installed.” ::= { devAdmin 14 } devAdminTdmOption OBJECT -TYPE SYNT AX INTEGER { tdm-installed(1), tdm-not-installed(2) } ACCESS read-only ST A TUS mandatory DESCRIPTION ”A value of tdm-installed(1) indicates that a time division multiplexer option is installed.”[...]
-
Страница 64
Device Enterprise MIB Definition B-7 Issue 2 December 1996 –– Device Identity Group (dev 2) devIdentityModel OBJECT -TYPE SYNT AX DisplayString (SIZE (0..40)) ACCESS read-only ST A TUS mandatory DESCRIPTION ”Model number .” ::= { devIdentity 1 } devIdentityLineSpeed OBJECT -TYPE SYNT AX DisplayString (SIZE (0..40)) ACCESS read-only ST A TUS[...]
-
Страница 65
Device Enterprise MIB Definition B-8 Issue 2 December 1996 ST A TUS mandatory DESCRIPTION ”Access module (if applicable, otherwise length is zero).” ::= { devIdentity 6 } devIdentityRestoralOption OBJECT -TYPE SYNT AX DisplayString (SIZE (0..40)) ACCESS read-only ST A TUS mandatory DESCRIPTION ”Restoral option (if applicable, otherwise length[...]
-
Страница 66
Device Enterprise MIB Definition B-9 Issue 2 December 1996 devIdentityOption1 OBJECT -TYPE SYNT AX DisplayString (SIZE (0..40)) ACCESS read-only ST A TUS mandatory DESCRIPTION ”Option 1 (if applicable, otherwise length is zero).” ::= { devIdentity 12 } devIdentityOption2 OBJECT -TYPE SYNT AX DisplayString (SIZE (0..40)) ACCESS read-only ST A TU[...]
-
Страница 67
Device Enterprise MIB Definition B-10 Issue 2 December 1996 ”Option 6 (if applicable, otherwise length is zero).” ::= { devIdentity 17 }[...]
-
Страница 68
Device Enterprise MIB Definition B-1 1 Issue 2 December 1996 –– Device Status Group (dev 3) devStatusConnectedDevice OBJECT -TYPE SYNT AX DisplayString (SIZE (0..15)) ACCESS read-only ST A TUS mandatory DESCRIPTION ”The device name of the connected device. A zero length string will be returned if the information is unavailable.” ::= { devSt[...]
-
Страница 69
Device Enterprise MIB Definition B-12 Issue 2 December 1996 service-line(15), non-answering-modem(16), short-holding-time-modem(17), sub-tree-truncation(18), tdm-failure-good-apl(19), trib-timeout(20), dial-tone(21), redundant-power(22), no-response(31)” ::= { devStatus 3 } devStatusAlertDesc OBJECT -TYPE SYNT AX DisplayString (SIZE (0..255)) ACC[...]
-
Страница 70
Device Enterprise MIB Definition B-13 Issue 2 December 1996 devStatusSpeed OBJECT -TYPE SYNT AX INTEGER ACCESS read-only ST A TUS mandatory DESCRIPTION ”The current data rate of the device, in bits per second. A value of zero indicates that the device is training.” ::= { devStatus 6 } devStatusCtrlT rib OBJECT -TYPE SYNT AX INTEGER { local-cont[...]
-
Страница 71
Device Enterprise MIB Definition B-14 Issue 2 December 1996 ”Indicates the polling state of the device in the network.” ::= { devStatus 9 }[...]
-
Страница 72
Device Enterprise MIB Definition B-15 Issue 2 December 1996 –– Circuit Quality Group (dev 4) –– T ype Definition for Circuit Quality V alidity indicators –– V alidity is not-used(6) if not supported by device type. CirQualV alidity ::= INTEGER { valid(1), valid-greater-than(2), valid-less-than(3), not-valid-for-modulation-mode(4), not-v[...]
-
Страница 73
Device Enterprise MIB Definition B-16 Issue 2 December 1996 ”V alidity of the devCirQualMeanSquareError object.” ::= { devCirQual 3 } devCirQualMeanSquareError OBJECT -TYPE SYNT AX INTEGER ACCESS read-only ST A TUS mandatory DESCRIPTION ”Mean squared error .” ::= { devCirQual 4 } –– Receive Level devCirQualReceiveLevelV alidity OBJECT -[...]
-
Страница 74
Device Enterprise MIB Definition B-17 Issue 2 December 1996 ST A TUS mandatory DESCRIPTION ”1004 Hz loss.” ::= { devCirQual 8 } –– Signal to Noise Ratio devCirQualSignalT oNoiseV alidity OBJECT -TYPE SYNT AX CirQualV alidity ACCESS read-only ST A TUS mandatory DESCRIPTION ”V alidity of the devCirQualSignalT oNoise object.” ::= { devCirQ[...]
-
Страница 75
Device Enterprise MIB Definition B-18 Issue 2 December 1996 –– Phase Jitter 20–300 Hz devCirQualPhaseJitter300V alidity OBJECT -TYPE SYNT AX CirQualV alidity ACCESS read-only ST A TUS mandatory DESCRIPTION ”V alidity of the devCirQualPhaseJitter300 object.” ::= { devCirQual 13 } devCirQualPhaseJitter300 OBJECT -TYPE SYNT AX INTEGER ACCESS[...]
-
Страница 76
Device Enterprise MIB Definition B-19 Issue 2 December 1996 ST A TUS mandatory DESCRIPTION ”V alidity of the devCirQualNegativeAttenuation object.” ::= { devCirQual 17 } devCirQualNegativeAttenuation OBJECT -TYPE SYNT AX INTEGER ACCESS read-only ST A TUS mandatory DESCRIPTION ”Negative attenuation.” ::= { devCirQual 18 } –– Envelope Del[...]
-
Страница 77
Device Enterprise MIB Definition B-20 Issue 2 December 1996 SYNT AX INTEGER ACCESS read-only ST A TUS mandatory DESCRIPTION ”Frequency offset. Units are (Hz * 10). Possible range –51.1 to +51.1 Hz.” ::= { devCirQual 22 } –– Non Linear Distortion devCirQualNonLinearDistortionV alidity OBJECT -TYPE SYNT AX CirQualV alidity ACCESS read-only [...]
-
Страница 78
Device Enterprise MIB Definition B-21 Issue 2 December 1996 DESCRIPTION ”Retrains. Integer value represents the number of retrain events during the last 15 minutes. Possible range is 0 to 4095.” ::= { devCirQual 26 } –– Blown Startups devCirQualBlownStartupsV alidity OBJECT -TYPE SYNT AX CirQualV alidity ACCESS read-only ST A TUS mandatory [...]
-
Страница 79
Device Enterprise MIB Definition B-22 Issue 2 December 1996 –– Phase Hits devCirQualPhaseHitsV alidity OBJECT -TYPE SYNT AX CirQualV alidity ACCESS read-only ST A TUS mandatory DESCRIPTION ”V alidity of the devCirQualPhaseHits object.” ::= { devCirQual 31 } devCirQualPhaseHits OBJECT -TYPE SYNT AX INTEGER ACCESS read-only ST A TUS mandatory[...]
-
Страница 80
Device Enterprise MIB Definition B-23 Issue 2 December 1996 ACCESS read-only ST A TUS mandatory DESCRIPTION ”V alidity of the devCirQualDropouts object.” ::= { devCirQual 35 } devCirQualDropouts OBJECT -TYPE SYNT AX INTEGER ACCESS read-only ST A TUS mandatory DESCRIPTION ”Dropouts. Integer value represents the number of dropout events during [...]
-
Страница 81
Device Enterprise MIB Definition B-24 Issue 2 December 1996 SYNT AX CirQualV alidity ACCESS read-only ST A TUS mandatory DESCRIPTION ”V alidity of the devCirQualNearEndEcho object.” ::= { devCirQual 39 } devCirQualNearEndEcho OBJECT -TYPE SYNT AX INTEGER ACCESS read-only ST A TUS mandatory DESCRIPTION ”Near end echo. Units are (dB *10). Possi[...]
-
Страница 82
Device Enterprise MIB Definition B-25 Issue 2 December 1996 ::= { devCirQual 43 } devCirQualFarEndDelay OBJECT -TYPE SYNT AX INTEGER ACCESS read-only ST A TUS mandatory DESCRIPTION ”Far end delay . Units are in milliseconds. Possible range 0 to 4095 ms.” ::= { devCirQual 44 } –– Echo Frequency Offset devCirQualEchoFreqOf fsetV alidity OBJEC[...]
-
Страница 83
Device Enterprise MIB Definition B-26 Issue 2 December 1996 –– EIA Status Group (dev 5) –– T extual Convention for EIA Status Integer EIAStatus ::= INTEGER { off(1), on(2), unsupported-lead(3), lead-changing(4) } –– Number of Ports (Number of Entries in EIA Status T able) devEIAStatusPorts OBJECT -TYPE SYNT AX INTEGER ACCESS read-only S[...]
-
Страница 84
Device Enterprise MIB Definition B-27 Issue 2 December 1996 –– Layout of one entry in devEIAStatusT able. DevEIAStatusEntry ::= SEQUENCE { devEIAStatusIndex INTEGER, devEIAStatusCode OCTET STRING, devEIAStatusDTR EIAStatus, devEIAStatusTD EIAStatus, devEIAStatusRD EIAStatus, devEIAStatusDSR EIAStatus, devEIAStatusR TS EIAStatus, devEIAStatusCTS[...]
-
Страница 85
Device Enterprise MIB Definition B-28 Issue 2 December 1996 devEIAStatusACR EIAStatus, devEIAStatusDSC EIAStatus, devEIAStatusPND EIAStatus } devEIAStatusIndex OBJECT -TYPE SYNT AX INTEGER ACCESS read-only ST A TUS mandatory DESCRIPTION ”The index of the entry in the devEIAStatusT able. Note that the device hardware port number is used as the ind[...]
-
Страница 86
Device Enterprise MIB Definition B-29 Issue 2 December 1996 ST A TUS mandatory DESCRIPTION ”TD.” ::= { devEIAStatusEntry 4 } devEIAStatusRD OBJECT -TYPE SYNT AX EIAStatus ACCESS read-only ST A TUS mandatory DESCRIPTION ”RD.” ::= { devEIAStatusEntry 5 } devEIAStatusDSR OBJECT -TYPE SYNT AX EIAStatus ACCESS read-only ST A TUS mandatory DESCRI[...]
-
Страница 87
Device Enterprise MIB Definition B-30 Issue 2 December 1996 devEIAStatusTM OBJECT -TYPE SYNT AX EIAStatus ACCESS read-only ST A TUS mandatory DESCRIPTION ”TM.” ::= { devEIAStatusEntry 10 } devEIAStatusDRI OBJECT -TYPE SYNT AX EIAStatus ACCESS read-only ST A TUS mandatory DESCRIPTION ”DRI.” ::= { devEIAStatusEntry 1 1 } devEIAStatusPIN13 OBJ[...]
-
Страница 88
Device Enterprise MIB Definition B-31 Issue 2 December 1996 ”LL.” ::= { devEIAStatusEntry 15 } devEIAStatusRL OBJECT -TYPE SYNT AX EIAStatus ACCESS read-only ST A TUS mandatory DESCRIPTION ”RL.” ::= { devEIAStatusEntry 16 } devEIAStatusRI OBJECT -TYPE SYNT AX EIAStatus ACCESS read-only ST A TUS mandatory DESCRIPTION ”RI.” ::= { devEIASt[...]
-
Страница 89
Device Enterprise MIB Definition B-32 Issue 2 December 1996 ACCESS read-only ST A TUS mandatory DESCRIPTION ”ACR.” ::= { devEIAStatusEntry 21 } devEIAStatusDSC OBJECT -TYPE SYNT AX EIAStatus ACCESS read-only ST A TUS mandatory DESCRIPTION ”DSC.” ::= { devEIAStatusEntry 22 } devEIAStatusPND OBJECT -TYPE SYNT AX EIAStatus ACCESS read-only ST [...]
-
Страница 90
Device Enterprise MIB Definition B-33 Issue 2 December 1996 –– External Leads Group (dev 6) –– T extual Convention for External Lead objects ExternalLead ::= INTEGER { lead-off(1), lead-on(2) } devExtLeadsOutPin12 OBJECT -TYPE SYNT AX ExternalLead ACCESS read-write ST A TUS mandatory DESCRIPTION ”RS-232 output pin 12 (port 1).” ::= { de[...]
-
Страница 91
Device Enterprise MIB Definition B-34 Issue 2 December 1996 –– Command Group (dev 7) –– Dial an Entered or Stored Number devCommandDial OBJECT -TYPE SYNT AX DisplayString (SIZE (0..40)) ACCESS read-write ST A TUS mandatory DESCRIPTION ”Setting this attribute will cause the modem to dial the entered number . T o dial a stored number , the [...]
-
Страница 92
Device Enterprise MIB Definition B-35 Issue 2 December 1996 ”Setting this attribute to busy(1) will cause the device to busy out the attached analog phone line. Setting this attribute to clear(2) will cause the device to unbusy the analog phone line. This object will always return a value of unknown(3). T o test the current busy state, refer to t[...]
-
Страница 93
Device Enterprise MIB Definition B-36 Issue 2 December 1996 devCommandReset OBJECT -TYPE SYNT AX INTEGER { software(1), hardware(2), unknown(3) } ACCESS read-write ST A TUS mandatory DESCRIPTION ”Invoke a software(1) or hardware(2) reset of the device. This object always returns a value of unknown(3).” ::= { devCommand 6 } –– Send Message t[...]
-
Страница 94
C-1 Issue 2 December 1996 Enterprise T rap Definitions C NMS6700-TRAP DEFINITIONS ::= BEGIN –– T itle: COMSPHERE 6700 T rap Definitions –– Copyright (C) 1996, Paradyne. All rights reserved. –– –– This file may be freely copied and distributed as –– long as no changes are made to it. IMPOR TS TRAP-TYPE FROM RFC-1215 nms-670[...]
-
Страница 95
Enterprise T rap Definitions C-2 Issue 2 December 1996 –– Primary Alerts (1 – 32) deviceFailure TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”Device failure (major).” ::= 1 configChangeNotify TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”Configuration change notify .” ::= 2 testMode TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”T est mode.” ::= [...]
-
Страница 96
Enterprise T rap Definitions C-3 Issue 2 December 1996 streamingT erminal TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”Streaming terminal (major).” ::= 8 accessSecurity TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”Access security alarm (major).” ::= 9 dialBackup TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”Dial backup active for APL.” ::= 10 dteAla[...]
-
Страница 97
Enterprise T rap Definitions C-4 Issue 2 December 1996 ENTERPRISE devOid DESCRIPTION ”Make busy mode.” ::= 15 serviceLine TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”Service line.” ::= 16 nonAnsweringModem TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”Non-answering modem.” ::= 17 shortHoldingT imeModem TRAP-TYPE ENTERPRISE devOid DESCRIPTION ?[...]
-
Страница 98
Enterprise T rap Definitions C-5 Issue 2 December 1996 DESCRIPTION ”Dial tone.” ::= 22 redundantPowerSupply TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”Redundant power supply .” ::= 23 noResponse TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”No response from the device.” ::= 32[...]
-
Страница 99
Enterprise T rap Definitions C-6 Issue 2 December 1996 –– System Events (101 – 1 17) vfLoginOk TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”VF login OK. The calling party entered a correct VF (DTMF) password.” ::= 101 userLoginOk TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”User Login OK. The calling party entered a correct user password” ::=[...]
-
Страница 100
Enterprise T rap Definitions C-7 Issue 2 December 1996 vfLoginRejected–PasswordT imeout TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”VF Login Rejected – Password T imeout. The calling party failed to enter a VF (DTMF) password within the allotted time.” ::= 107 vfLoginAborted–LineDisconnected TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”VF Logi[...]
-
Страница 101
Enterprise T rap Definitions C-8 Issue 2 December 1996 userLoginHack TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”User Login Hack – Multiple Sequential Password Retries. The password retry pattern indicates a hacker is attempting to defeat login security .” ::= 1 13 securityT ableInvalid TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”Device Security [...]
-
Страница 102
Enterprise T rap Definitions C-9 Issue 2 December 1996 –– Primary Alert Clear Notifications (201 – 232) deviceFailureClear TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”Device failure cleared.” ::= 201 configChangeNotifyClear TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”Configuration change notify cleared.” ::= 202 testModeClear TRAP-TYPE ENTE[...]
-
Страница 103
Enterprise T rap Definitions C-10 Issue 2 December 1996 streamingT erminalClear TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”Streaming terminal cleared.” ::= 208 accessSecurityClear TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”Access security alarm cleared.” ::= 209 dialBackupClear TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”Dial backup active for A[...]
-
Страница 104
Enterprise T rap Definitions C-1 1 Issue 2 December 1996 ”Make busy mode cleared.” ::= 215 serviceLineClear TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”Service line mode cleared.” ::= 216 nonAnsweringModemClear TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”Non-answering modem cleared.” ::= 217 shortHoldingT imeModemClear TRAP-TYPE ENTERPRISE de[...]
-
Страница 105
Enterprise T rap Definitions C-12 Issue 2 December 1996 redundantPowerSupplyClear TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”Redundant power supply cleared.” ::= 223 noResponseClear TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”No response from the device cleared.” ::= 232 END[...]
-
Страница 106
D-1 Issue 2 December 1996 Enterprise Common MIB Definitions D A TTP-ENTERPRISES DEFINITIONS ::= BEGIN IMPOR TS enterprises, IpAddress FROM RFC1 155-SMI OBJECT -TYPE FROM RFC-1212 DisplayString FROM RFC1213-MIB; –– –– Copyright (C) 1996, Paradyne. All rights reserved. –– –– T itle: Paradyne T op Level Enterprise Definitions –[...]
-
Страница 107
Enterprise Common MIB Definitions D-2 Issue 2 December 1996 paradyne-products OBJECT IDENTIFIER ::= { att-products 14 } attp-cellRelay-products OBJECT IDENTIFIER ::= { paradyne-products 1 } attp-31XX-products OBJECT IDENTIFIER ::= { paradyne-products 2 } attp-36XX-products OBJECT IDENTIFIER ::= { paradyne-products 3 } –– –– The NMS mgmt sub[...]
-
Страница 108
Enterprise Common MIB Definitions D-3 Issue 2 December 1996 devIdentityCustAssignedID OBJECT -TYPE SYNT AX DisplayString (SIZE (0..15)) ACCESS read-write ST A TUS mandatory DESCRIPTION ”Device identifier assigned by the customer . Used for display in ASCII interfaces.” ::= { devIdentity 2 } devIdentitySlotID OBJECT -TYPE SYNT AX INTEGER ACCESS [...]
-
Страница 109
Enterprise Common MIB Definitions D-4 Issue 2 December 1996 ::= { devIdentity 6 } devIdentityHWRevEntry OBJECT -TYPE SYNT AX DevIdentityHWRevEntry ACCESS not-accessible ST A TUS mandatory DESCRIPTION ”An entry in the hardware revision table.” INDEX { devIdentityHWRevIndex } ::= { devIdentityHWRevT able 1 } –– –– Layout of one entry in t[...]
-
Страница 110
Enterprise Common MIB Definitions D-5 Issue 2 December 1996 SYNT AX INTEGER ACCESS read-only ST A TUS mandatory DESCRIPTION ”Number of software revision entries in table.” ::= { devIdentity 7 } devIdentitySWRevT able OBJECT -TYPE SYNT AX SEQUENCE OF DevIdentitySWRevEntry ACCESS not-accessible ST A TUS mandatory DESCRIPTION ”The software revis[...]
-
Страница 111
Enterprise Common MIB Definitions D-6 Issue 2 December 1996 DESCRIPTION ”Software Revision table index.” ::= { devIdentitySWRevEntry 1 } devIdentitySWRevNumber OBJECT -TYPE SYNT AX DisplayString (SIZE (1..16)) ACCESS read-only ST A TUS mandatory DESCRIPTION ”Software revision number for the CCA software module.” ::= { devIdentitySWRevEntry [...]
-
Страница 112
Enterprise Common MIB Definitions D-7 Issue 2 December 1996 ”Self-test results. Self-test (or power-up test) results summarizes the test results of each CCA, where each CCA test result is separated by a semi-colon. Refer to device-specific user documentation for a complete description of the self test codes and messages.” ::= { devStatus 2 } ?[...]
-
Страница 113
Enterprise Common MIB Definitions D-8 Issue 2 December 1996 devFrontPanelCursorRow OBJECT -TYPE SYNT AX INTEGER ACCESS read-only ST A TUS mandatory DESCRIPTION ”Front panel cursor row (zero origin).” ::= { devFrontPanel 3 } devFrontPanelCursorColumn OBJECT -TYPE SYNT AX INTEGER ACCESS read-only ST A TUS mandatory DESCRIPTION ”Front panel curs[...]
-
Страница 114
Enterprise Common MIB Definitions D-9 Issue 2 December 1996 ST A TUS mandatory DESCRIPTION ”A row entry in front panel display table.” INDEX { devFrontPanelDisplayRowIndex } ::= { devFrontPanelDisplayT able 1 } DevFrontPanelDisplayEntry ::= SEQUENCE { devFrontPanelDisplayRowIndex INTEGER, devFrontPanelDisplayRow DisplayString } devFrontPanelDis[...]
-
Страница 115
Enterprise Common MIB Definitions D-10 Issue 2 December 1996 ACCESS read-only ST A TUS mandatory DESCRIPTION ”Indicates who owns the front panel at this time. If the status is free, then a keyPress set will successfully update the front panel and the status will change to nms. The agent is allowed to set the status back to free after a specified [...]
-
Страница 116
Enterprise Common MIB Definitions D-1 1 Issue 2 December 1996 The value returned on a GET is undefined.” ::= { adminFrontPanel 4 } –– –– Call Directory –– devCallDir OBJECT IDENTIFIER ::= { attp-callDir 1 } devCallDirEntries OBJECT -TYPE SYNT AX INTEGER ACCESS read-only ST A TUS mandatory DESCRIPTION ”Number of directories in the ca[...]
-
Страница 117
Enterprise Common MIB Definitions D-12 Issue 2 December 1996 devCallDirPurpose INTEGER, devCallDirId DisplayString, devCallDirPhoneNumber DisplayString } devCallDirIndex OBJECT -TYPE SYNT AX INTEGER ACCESS read-only ST A TUS mandatory DESCRIPTION ”A unique value for each call directory . Its value ranges between 1 and the value of devCallDirEntri[...]
-
Страница 118
Enterprise Common MIB Definitions D-13 Issue 2 December 1996 DESCRIPTION ”Call directory phone number .” ::= { devCallDirEntry 4 } END[...]
-
Страница 119
IN-1 Issue 2 December 1996 C Call Directory MIB, 3-6 COMSPHERE 6700 Series NMS Enterprise MIBs, 3-3 D Device MIB, 3-5 device traps, 3-7 DOS MIB, 3-6 F Front Panel MIB, 3-6 H hardware requirements, 2-1 I installation preparation, 2-3 procedure, 2-5 M Management Information Bases Call Directory MIB, 3-6 COMSPHERE 6700 Device MIB, 3-5 [...]
-
Страница 120
Index IN-2 Issue 2 December 1996 S SNMP community views, 3-1 1 overview , 1-1 sample network topology , 1-3 SNMP traps, 3-7 SNMP Proxy Agent feature list, 1-2 overview , 1-1 package contents, 1-4 software description, 1-2 software requirements, 2-1 supported network adapters, 2-2 system event traps, 3-9 T topology , sample, 1-3 traps device, 3-7 pr[...]