This document contains information relating to the safe
installation, maintenance, and use of the Oki BV1250. Carefully
note all safety precautions and procedures contained in this
document before installing and using the product.
Rev. 1.0Page i
BV1250 Technical Reference
The BV1250 Internet Voice Gateway and the Maintenance Console
Software are products of Oki Electric Industry Co. Ltd.
Right to reproduce this manual and/or the Maintenance Console
Software is restricted by the Copyright Act.
No part of this document may be reproduced, stored on a retrieval
system, or transmitted in any form or by any means, electronic,
mechanical, photocopying, recording, or otherwise, without the
written permission of Oki Electric Industry Co. Ltd.
Information in this document is subject to change without notice.
The contents of this document and the Maintenance Console
Software have been prepared with the utmost care. However, if you
notice an ambiguous point or omission, please contact an authorized
agent.
No responsibility will be taken by our company with respect to
consequences resulting from the use of the Maintenance Console
Software and/or the content and interpretation of the information
contained in this manual.
2000, Oki Electric Industry Co. Ltd.
Ethernet is a registered trademark of Xerox Corporation.
MS-DOS and Windows are registered trademarks of Microsoft
Corporation.
Other companies and product names mentioned in this manual are
the registered trademarks or services marks of their respective
companies.
Revision 1.0
Printed in the USA
Page iiRev. 1.0
BV1250 Technical Reference
Limited Warranty
Oki Electric Industry Co., Ltd. warrants that these products (BV1250 and
Maintenance Console Software) are free of manufacturing defects during the
warranty period and while operating under normal conditions. In the event of
failure, a replacement unit and/or software will be provided free of charge.
This warranty covers this product only and is subject to the following conditions:
1.Oki Electric warrants the media upon which the Maintenance Console
Software is recorded to be free from defects in materials and workmanship
under normal use for a period of ninety (90) days from the date of purchase.
In the event any media prove to be defective during the warranty period,
user’s remedy shall be to return media to Oki Electric for replacement.
2.Oki Electric does not accept liability for loss or damage caused by the user's
mishandling, misoperation, or damages occurring as a consequence of
unusual events such as fire, earthquake, or flood.
3.Regarding the quality and functionality of the Maintenance Console Software
and this Installation Guide, Oki Electric holds no liability for the conformity of
the equipment to the purpose of use by the user and the marketability. Oki
Electric does not accept liability for any loss or damage occurring directly or
indirectly thereof.
4.No responsibility will be taken regarding the results obtained by the use of the
BV1250 and/or the Maintenance Console Software and/or this Installation
Guide.
5.Media such as this Installation Guide, floppy disks, CDs, etc., are supplied
with the Maintenance Console Software as a package and shall be used for
the Maintenance Console Software only. It is strictly forbidden to make a
copy of the Maintenance Console Software other than a back-up copy. Oki
Electric holds no liability for consequences incurred by the use of the copied
media.
Others
1. It is strictly forbidden to offer the MCS program to a third party as such or
after adding modifications. If this program is used by a third party, that use
infringes upon the copyright of the author and it becomes the author's right to
demand compensation.
2. Customer services are available at our company's head office and at our
service locations.
The Oki BV1250 Internet Voice Gateway (IVG) is a self-contained device that
allows organizations to route both voice and fax communications over any IP
compatible network. Oki’s IVG seamlessly bridges existing PBX, key telephone,
analog, and PSTN telephone systems with digital data networks. This technology
allows organizations to more fully utilize existing intranet and Internet facilities.
Most importantly, since communications take place over digital data networks, the
high cost of long distance communications over conventional public telephone
networks is eliminated.
Salient features of the BV1250 include:
•
Analog terminal, PBX, PSTN, and G3 Fax communications achieved
over IP network.
•
High-quality voice compression encoding that can be configured on a
priority basis to automatically select between 64kbps PCM stream as
either G.729A (8kbps), G.723.1 (5.3kbps) or G.723.1 (6.3kbps)
compression, packet priority control, and bandwidth management.
•
Oki’s proprietary dynamic jitter buffer and Dynamic Echo
Cancellation assure uninterrupted and natural speech communications.
•
All four BV1250 unit ports are capable of real-time fax transmission
using IP transmission, taking full advantage of the data network’s
flow and data control (TCP transmission).
•
Compliant with H.323 Version 2 network protocols and interoperable
with all H.323 compliant devices.
•
In non-H.323 networks, provides unified telephone numbering
management using both internal (within the unit) and external DNS
(Domain Name System) functions.
•
Network management control through SNMP (Simple Network
Management Protocol – MIBI and MIBII).
Connection ConfirmationImmediate, Delay-dial, or Wink-start
Selection signalDP 10/20 PPS or DTMF
ConnectorSimple solderless / RJ45
ComplianceITU-T Rec. Q.517
Model Name :EMIF FIC :TL11E, TL12E, TL31E, TL32E
Registrant :OKI INDUSTRY CO LTD , Reg. No.:1XLUSA-33761-CN-E, Grant Date :04/27/1999
Canadian Approval CS03, Model Name :EMIF E&M Certification No. :187 9837 A
ComponentPCB board
TerminalAnalog Telephone or Key Telephone System
Lines4 maximum
Channels4 simultaneous
Resistance400 ohms
Start-up methodLoop start
Selection signalDP 10/20 PPS or DTMF
ConnectorSimple solderless / RJ11
Ringer freq.20Hz/25Hz/50Hz
ComplianceITU-T Rec. Q.517
A functional BV1250 unit must have a Line Interface card installed. The interface may be FXS
(analog), FXO (analog), E&M (Types 1 and 2), or E&M–OD (Type 5). The G3 facsimile interface is
available with all of the above.
US
= Type 1 or Type 2
JPN
= Type 5 EU = Type 1, Type 2, Type 5 (OD)
(Including terminal resistance)
FXO(option):
Fax
ComponentPCB board
TerminalAnalog CO Lines, Key Telephone System, PBX
Lines4 maximum
Channels4 simultaneous
Resistance288 ohms
Start-up methodLoop start
Selection signalDP 10/20 PPS or DTMF
ConnectorSimple solderless / RJ 11
ComplianceITU-T Rec. Q.517
Model Name :FXO FIC :O2LS2
Registrant :OKI INDUSTRY CO LTD, Reg. No:1XLJPN-33760-CN-E Grant Date :04/27/1999
Canadian Approval CS03, Model Name: FXO, Certification No:187 9903 X
Lines 4 max
Data transfer9600 bps/4800bps
Transmission ControlG3
(Including terminal resistance)
Page 4Rev. 1.0
BV1250 Technical ReferenceDescription
2. BV1250 External Views
The external characteristics of a BV1250 unit are shown below.
2.1 Base Unit Configuration
Figure 2-1 illustrates the basic configuration of all versions BV1250 units.
The only difference between unit configurations is that the line interface
connector ports appearing on the front panel vary between FXS, FXO,
E&M, and E&M-OD equipped units. These differences are noted in Figure
2-2.
Figure 2-1: BV1250 External View (FXS shown)
Height =
53mm (3")
Depth = 400mm (14")
Rear
Front
Width = 420mm (17")
:
NOTE
Appearance of Line
Interface varies
based on type of
interface installed.
(See description in
following section,
External Features.)
2.2
Rev. 1.0Page 5
DescriptionBV1250 Technical Reference
BV1250 External Features
The BV1250 base unit front and rear panels have various physical elements
associated with supplying power to the unit and providing operational status
information. Figure 2-2 illustrates these features. These features are
described in greater detail in Table 2-1 on the following page.
Figure 2-2: BV1250 External Features
Page 6Rev. 1.0
BV1250 Technical ReferenceDescription
Table 2-1: Description of BV1250 External Feature
ItemDescription
1Power lampIndicates power ON when lamp litGreen lamp
2Busy lampWhen port is in use, lit lamp indicates line is busyOrange lamp
3Alarm lampIndicates alarmed condition detected in unit when lamp lit or blinkingRed lamp
5Serial portConnector for serial cable connection of maintenance console terminalDB9-F
6Link lampIndicates LAN link is operating normally when litGreen lamp
7Uplink connector10BaseT connector for LANRJ45
9Collision lampIndicates frame collisions are occurring when lit.Yellow lamp
8Data lampIndicates that data is being sent/received when lamp is lit or blinkingGreen lamp
10.Line interface
a. FXS
b. FXO
c. E&M
d. E&M-OD
11Fan assemblyServiceable fan assembly for cooling of unit
12FG terminalTerminal strip for frame ground
Line interface board connectors
Four TEL connectors of FXS board equipped units
Four FXO connectors of FXO board equipped units
Eight E&M connectors for E&M board equipped units
Four E&M-OD connectors for E&M-OD board equipped units
Green lamp
Connectors
supplied with
board
13Power connectorConnector for AC power cord
14Fuse holderHousing for fuse
15Power switchTurns power to the base unit ON and OFFToggle switch
Rev. 1.0Page 7
DescriptionBV1250 Technical Reference
3. BV1250 Parts
Below is a listing of BV1250 parts along with the part and product numbers.
Product NameOki Networks Part NumberOki-J Product No.
Basic Parts
BV1250 Base Unit1001014YA1158-1121G002
BV1250 Accessories
BV1250 Accessories, Europe
BV1250 FXS Interface kit
BV1250 FXO Interface kit
BV1250 E&M Interface kit
BV1250 AP interface retrofit kit
BV1250 FXO interface retrofit kit
BV1250 EM interface retrofit kit
BV1250 OD Interface retrofit kit (Japan)
BV1250 FXO Interface kit, Japan
BV1250 Rack Mount Kit1001064YA1158-1122G001
Maintenance Console Software103012
BV1250 Installation Guide
BV1250 Technical reference
Ancillary Parts and Spares
BV1250 General Description103115
BV1250 User's Guide1010043PP1158-5120P101
BV1250 Indicator Label for FXS unit1011013PP1158-5220P001
BV1250 Indicator Label for FXO unit1011023PP1158-5220P002
BV1250 Indicator Label for E&M unit1011033PP1158-5220P004
DDK Connectors for AP unit Installation101006224A3223P0020
DDK Connectors for E&M unit Installation101008224A3231P0040
DDK Connectors for OD unit Installation101010224A3231P0060
Screws for Base unit Type M4101011P(SW+W)4-10-FRC
Screws for Interface card Type M3101012P(SW+W)3-8-FRC
BV1250 Cooling Fan unit101105
BV1250 Fuse, Rating 250V, 3.15A101106
PC Serial cable for Maintenance Console101013--
100102
100114
100103
100104
100105
100107
100108
100109
100113
100112
103111
103112
4YA1158-1123G002
4YA1158-1123G003
4YA1158-1124G001
4YA1158-1125G002
4YA1158-1146G001
4YA1158-1144G001
4YA1158-1142G001
4YA1158-1143G001
4YA1158-1145G001
4YA1158-1125G001
Page 8Rev. 1.0
BV1250 Technical ReferenceMaintenance and Troubleshooting
BV1250 Maintenance
and Troubleshooting
The BV1250 unit is a low maintenance electronic device that, once installed and properly
configured, should need only infrequent attention.
Other than an occasional external cleaning, all maintenance activities should be performed
by qualified personnel. General maintenance activities include routine checks of data logs
maintained in the unit’s log files, system file updates, and should it becomes necessary, the
replacement of the unit’s fuse and fan assembly.
In the event that a unit’s performance fails or becomes unstable, it may be necessary to
troubleshoot the unit to diagnose and correct the problem.
In this section, the following topics are discussed:
•
Routine Maintenance
•
Troubleshooting and Corrective Action
•
Fault Messages and Reports
•
Error Traps
•
Fuse Replacement
•
Fan Unit Replacement
Rev. 1.0Page 1
Maintenance and TroubleshootingBV1250 Technical Reference
Page 2Rev. 1.0
BV1250 Technical ReferenceMaintenance and Troubleshooting
1. Routine Maintenance
Routine maintenance involves tasks to be performed on a regular basis even when the
unit gives no evidence of problems or malfunction. These activities are generally
preventative in nature.
1.1 External Cleaning
Depending on the environment in which it is installed, a BV1250 unit may
need occasional cleaning. Cleaning will help to remove accumulated dust and
dirt which can interfere with the proper cooling of the unit and can affect the
operation of the unit’s external switches and buttons.
External cleaning is performed using a cloth dampened with a mild soapy
solution. Simply wipe down the unit to remove dirt and dust taking care that no
excess moisture penetrates the unit.
!
Do not allow moisture to penetrate the unit. Moisture in the
unit can cause serious damage and may produce an electrical
hazard.
When cleaning the external base unit, it is also useful to check the unit fan for
dust build-up. If an excessive amount of dust is present, the fan unit should be
cleaned. See Section 6 for a description of the fan assembly.
Rev. 1.0Page 3
Maintenance and TroubleshootingBV1250 Technical Reference
1.2 Periodic inspection
Periodic inspection activities should be organized using a maintenance
schedule that specifies regular inspection intervals. Inspection need not occur
frequently but is best when conducted on a routine basis.
With the exception of external inspection, all inspection activities can be
conducted remotely using the Maintenance Console Software or with On-line
commands on a terminal.
Recommended inspection and maintenance activities are shown in Table 1-1
below.
Table 1-1: Periodic Inspection Procedure
StepActionNominal ConditionIf trouble. . .
1. Check general
operation.
2. Check Trouble
Log.
3. Restart unit.Power cycle the unit being careful to
4. Check voice
communication.
5. Check fax
communication
Check the Alarm lamp on the front
panel of the unit.
Use the MCS to view the equipment
status.
Use the MCS Fault Log display or
enter the on-line
retrieve the unit’s fault log.
use the Shutdown procedure
described in the BV1250 Installation
Guide.
OR
Reboot the equipment using the
MCS Reboot item or the on-line
REBOOT command.
After restart repeat Step 1 this table.
Place test calls to and from
extensions associated with the unit.
Send test faxes to and from
extensions associated with the unit.
ELOG
command to
Red ALARM lamp not lit.
All lamps are operating,
(e.g. PWR, CONT, PP.
FAX, and FAN)
No fault conditions are
displayed in the log.
Red ALARM lamp not lit.
All lamps are operating,
(e.g. PWR, CONT, PP.
FAX, and FAN)
The ring-back tone (RBT)
can be heard.
Speech quality is normal
and there is little or no
ambient background
noise.
Fax transmitted
successfully.
Use the MCS Fault Log display or enter the on-line
command to retrieve the unit’s fault log,
ELOG
record listed trouble code(s), and refer to the Fault
Messages table for corrective action.
Record listed trouble code(s) and refer to the Fault
Messages table for corrective action.
Use the MCS Fault Log display or enter the on-line
command to retrieve the unit’s fault log,
ELOG
record listed trouble code(s), and refer to the Fault
Messages table for corrective action.
Verify that the access code and destination number
dialed are correct.
Use the MCS or other facility to send a Ping test to
the remote IVG to verify communication.
Use the MCS Fault Log display or enter the on-line
command to retrieve the unit’s fault log,
ELOG
record listed trouble code(s), and refer to the Fault
Messages table for corrective action.
Verify that the access code and destination
numbers dialed are correct.
Use the MCS or other facility to send a Ping test to
the remote IVG to verify communication.
Use the MCS Fault Log display or enter the on-line
command to retrieve the unit’s fault log,
ELOG
record listed trouble code(s), and refer to the Fault
Messages table for corrective action.
The ELOG must be cleared following the correction of a
problem listed in the log. If this is not done, a previously
resolved item will be erroneously displayed in subsequent
reports. After resolving a problem always clear the trouble
log using the MCS or the on-line ELOG-CLR command.
Page 4Rev. 1.0
NOTE:
BV1250 Technical ReferenceMaintenance and Troubleshooting
1.3 File Management
On occasion it may be necessary to update or restore a BV1250 unit’s system
files. The updating or restoration of unit’s system files is performed using the
Maintenance Console Software or with the On-line commands. The procedures
for this are discussed in the BV1250 Installation Guide and in the On-line
Command Reference section in this document.
Table 1-2 shows the files installed in a BV1250 unit.
Each BV1250 has an office data file, OFDD.VHO, which resides in the
directory
This file contains unit specific configuration information such as network data,
numbering plan data, line data, and operational data.
When a BV1250 unit is replaced or should a unit’s OFDD.VHO file become
lost or corrupted, this file must be restored to the unit using the procedures
described in the BV1250 Installation Guide. Maintaining backup copies of all
BV1250 unit OFDD.VHO files is strongly recommended. See the Maintenance
Console Software Operations Manual for the recommended procedure.
The Maintenance Console Software (MCS) stores backup versions of all units
configured using the MCS.
By default, the MCS stores OFDD backup files in the directory
Files\Cons50\DATA\(Group_Name)\(Unit_Name)\
with the extension .OLD.
C:\Program
Rev. 1.0Page 5
Maintenance and TroubleshootingBV1250 Technical Reference
Page 6Rev. 1.0
BV1250 Technical ReferenceMaintenance and Troubleshooting
2. Trouble Diagnosis and Corrective
Action
When a BV1250 unit problem is detected/reported, a systematic methodology
will assist in the diagnosis and correction of the problem.
The recommended procedure involves the following steps.
1. Retrieve the unit’s trouble log.
2. Analyze the fault information.
3. Identify the fault location.
4. Correct the problem.
5. Clear the fault log.
!
Before opening the cover of a BV1250 unit be certain to read
and understand all safety precautions listed at the beginning
of the BV1250 Installation Guide.
Rev. 1.0Page 7
Maintenance and TroubleshootingBV1250 Technical Reference
2.1 Fault Processing
On occasion, a fault condition may arise which causes a unit to behave
erratically or fail altogether. Should this occur, it is important to take timely
action to obtain a trouble report, diagnose, and resolve the problem. In addition,
it is recommended that some form of trouble ticket be maintained in order to
track actions taken to resolve the problem and to preserve a maintenance record
for the affected unit(s).
The first steps in dealing with a trouble report can be handled remotely. If
remote activities are not sufficient to resolve the problem, it may be necessary
to perform on-site tasks to resolve the difficulty.
1. Check the situation by telephone
When a problem occurs, it should be reported by the user or network manager and
a record of the problem should be made. Important elements of the report include
the unit identification/location information, time of the event, symptoms of the
event, and conditions/use under which the event occurred.
In addition, it may be necessary to provide the reporting person with instructions
regarding action to be taken immediately to prevent broader network problems.
2. Confirm the fault situation using a remote connection with the unit
If communications with the problem unit are intact, use the MCS Fault Log
display or the on-line
related trouble code(s).
Once any fault codes have been retrieved, refer to the Table 2-2 Fault Conditions
in this document to diagnose the problem. If the trouble is due to a software or data
error, it will usually be possible to correct the problem remotely, using the
Maintenance Console Software.
3. Troubleshoot on-site
If a fault condition is due to hardware, such as a blown fuse for example, it will
be necessary to make a service call to the site where the unit is located.
ELOG
command, to retrieve the unit’s fault log and to record
Page 8Rev. 1.0
BV1250 Technical ReferenceMaintenance and Troubleshooting
2.2 Guide to Trouble Indications
Table 2-1 provides a general troubleshooting guide. In many cases this
information will be sufficient to diagnose and correct a problem.
If an error not mentioned in the table has occurred, check the unit’s Fault Log
and refer to the Fault Conditions table (Table 2-1) in this document. In
addition, the unit automatically sends SNMP traps for a Network Management
System (NMS) giving notification of the fault. See Section 3 for details
regarding Trap Information.
Table 2-1: Trouble Indications and Corrective Action
SymptomCauseCorrective Action
POWER lamp not on when POWER is
on.
ALARM lamp is lit.
LINK lamp does not turn on when LAN
cable connected to UPLINK socket.
Can not set office data using
Maintenance Console Software.
No dial tone even if when phone is offhook.
Dial tone continues after dialing.
Voice/fax transmission disconnects while
receiving or sending a fax.
Connect tone (CON) status continues
when dialing from a telephone and then
changes to Restricted Outward Tone
(ROT).
Calls can be made from a telephone but
calls cannot be received.
Power cord not connected or damaged.
•
Fuse blown.
•
Defective/damaged part(s).
•
Unit configuration error.
•
Cable is not correctly installed or is
•
defective.
Equipment failure has occurred.
•
Power to the destination equipment
•
(router, hub, etc.) not turned on.
IP address, gateway address, or subnet
•
address wrong.
Incorrect cable connection.
•
Cable between telephone and the BV1250
unit not connected or is damaged.
Dial type (DP/DTMF) of telephone set
•
does not match BV1250 unit office data
configuration.
Network is congested or a trouble has
•
occurred on the network.
Registered DNS server information is
•
incorrect.
DNS numbering information for BV1250
•
unit has not been set.
Registered Gatekeeper information is
•
incorrect.
Gatekeeper not operated.
•
Router Address Resolution Protocol
•
(ARP) information (IP address Ethernet address correspondence
information) does not match with the
BV1250 information.
Inspect and connect power cord.
•
(Replace cord if required.)
Replace fuse.
•
Check for defective part(s) and correct
•
condition.
Correct configuration error.
•
Inspect and reconnect LAN cable.
•
(Replace cable if required.)
Determine if there is an equipment
•
fault and correct condition.
Turn destination equipment power on.
•
Correct address(es).
•
Inspect cable for damage and type and
•
reconnect. (Replace cable if required.)
Inspect and connect cable.
•
(Replace cable if required.)
Correct office data configuration for
•
BV1250 unit.
Try again later.
•
Check the registered DNS information.
•
Verify that the DNS numbering plan
•
information for the BV1250 unit is
properly configured.
Check the registered Gatekeeper
•
information.
Check the Gatekeeper status.
•
Clear the router’s ARP information.
•
(To clear the ARP information, refer to
the router’s manual.)
: This symptom may occur even if
Note
the BV1250 has been replaced.
Rev. 1.0Page 9
Maintenance and TroubleshootingBV1250 Technical Reference
2.3 Fault Log Codes and Corrective Action
The BV1250 maintains a fault log in which fault conditions are recorded as
they occur. The fault log is useful in diagnosing problems with a unit and in
determining appropriate corrective action.
NOTE:
Not all conditions recorded in the fault log represent faults
with the equipment. In some cases, the log records events
such as powering the unit up and down or rebooting the unit.
The Maintenance Console Software or the on-line command
ELOG
can be used
to retrieve a unit’s fault log. See the Maintenance Console Software
Operations Guide and the BV1250 On-line Command Reference section in this
document, for retrieval procedures.
Below is an example of a fault log report.
# ELOG
There are 003 Messages
10(Remove) 20(Voice) 00(DSP-Fault) SEQ=01 TUE Jan 06 12:29:30 1998
4EF9400015784E71 009029D0 009029D0 N.@..xNq..)...).
00(Fault) 20(Voice) 00(DSP-Fault) SEQ=01 TUE Jan 06 12:29:00 1998
0008F75C4FEF000C 300748CO 00000000 ...\0...0.H.r...
01(Report) 00(System) 00(Power-ON) SEQ=00 TUE Jan 06 12:28:52 1998
The information shown in the sample log output reveals that:
•
The equipment restarted at 12:28:52 PM on the 6th of January 1998 by
being powered ON (PowerON).
•
DSP trouble occurred in voice processing DSP of line no. 1 at 12:29:00
PM on the 6th of January 1998.
•
Voice processing DSP for line no. 1 was restored at 12:29:30 PM on the
6th of January 1998.
Table 2-2 on the following page provides definitions of the fields in a fault log
report. In addition, the table provides explanations and suggested corrective
actions associated with the various fault conditions.
Page 10Rev. 1.0
BV1250 Technical ReferenceMaintenance and Troubleshooting
Rev. 1.0Page 11
Table 2-2: Fault Conditions
CodeCode
Detail
EquipmentMessage TypeFault
Abbreviation
SEQFault ExplanationAlarm LampComments and Corrective Action
On eventOn restore
0000SYSTEMReportPowerON00Power ONOff--No trouble.
01ReportResetKey00Reboot by reset keyOff--No trouble.
BV1250 Technical ReferenceMaintenance and Troubleshooting
Rev. 1.0Page 13
CodeCode
Detail
EquipmentMessage TypeFault
Abbreviation
SEQFault ExplanationAlarm LampComments and Corrective Action
On eventOn restore
1501
02
2002VOICEReportRFIFO_OVF00-03Receive FIFO
disconnected
Status hold--Excessive traffic on network. Try call
later.
03ReportNonPacket00-03Receive packet
disconnected
Status hold--Excessive traffic on network. Try call
later.
04ReportVCL_ERROR00-03Voice communications
error
Status hold--Excessive traffic on network. Try call
later.
3001FAXReportFaxError00
Fax communication
error
Status hold--
Excessive traffic on network. Try call
later.
4000CCLReportSockError
00-03
or FF
Communication errorStatus hold--Voice communications interrupted.
5000DNSReportSockError00Communication errorStatus hold--DNS communication interrupted.
01Report
RrqRrj
00
GK Communication
error
Status holdCheck Office data
02ReportXrsRcv00GK Communication
error
Status hold--Contact dealer or customer service.
Maintenance and TroubleshootingBV1250 Technical Reference
3. Trap Information Sent to NMS
A Trap is one of the signals included in the Simple Network Management Protocol
(SNMP). In the case of the BV1250, a trap signal is sent to a Network
Management System (NMS) when a fault is detected in the unit. The trap
information is recorded in an NMS trouble log which, when retrieved by
maintenance personnel, can be useful in diagnosing and correcting problems with
the BV1250 unit.
The trap signal is sent to an NMS when an abnormality in the equipment or a
change in status is detected by the BV1250 unit’s software. If the fault is of a
critical nature, the equipment reboot processing is automatically started before
sending the trap. When this occurs, the unit sends the trap message to the NMS
during the system reboot.
A trap message is output using the fields shown in Table 3-1:
Table 3-1: Trap messages
FieldTypeValue
VersionINTEGERO(SNMP-Version1)
communityOCTET STRING“public”
enterpriseOBJECT INDENTIFIERObject ID of BV1250
agent-addrNETWORK ADDRESSIP address of BV1250
generic-trapINTEGER0(coldStart)
specific-trapINTERGERFault number
time-stampTimeTicksTime elapsed
variable-bindingsVarBindListNULL
6(enterpriseSpecific)
community:The community name value is configured in the BV1250
unit’s office data file (OFDD.VHO). The default value
in the OFDD.VHO file is “public”.
enterprise value:The enterprise value shows the object ID for a BV1250
unit, e.g. 1.3.6.1.4.1.666.90.3.3.1).
generic-trap:The cold start (coldStart) after the system startup causes
the trap value to be output as a generic-trap which is
displayed as 0. Messages other than this generic output,
such as fault, recovery, and report messages, are output
as the enterprise Specific trap value which is displayed as
a generic trap equal to 6.
Page 14Revision 1.0
Loading...
+ 168 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.