NetGuardian 832A/864A G5
NetGuardian 832A & 864A G5
USER MANUAL
Visit our website at www.dpstelecom.com for the latest PDF manual and FAQs.
February 26, 2010
D-OC-UM102.26100
Firmware Version 5.2D
Revision History
February 26, 2010
Added info for NetGuardian G5 with GigE Fiber top board option.
December 2, 2009
Added info on Command Line Mode in TTY.
July 13, 2009
Revisions to Analog and LAN sections
February 5, 2009
Added RADIUS information on G5 platform and NetGuardian E16
expansion option. Updates graphics and instructions for installing
the hinged pluggable back panel.
December 18,
2008
Added sections for installing the hinged pluggable back panel and
tuning the 202 modem.
November 26,
2008
Edited directions for analog dipswitches.
Updated blue LCDs to yellow
March 28, 2008
Added Section for GPRS/CDMA Wireless option
March 3, 2008
Added NetGuardian 864A Tables and 10/100Mbps Switch
February 6, 2008
Added pictures of sealed hardware kits
This document contains proprietary information which is protected by copyright. All rights are reserved. No part of this
document may be photocopied without prior written consent of DPS Telecom.
All software and manuals are copyrighted by DPS Telecom. Said software and manuals may not be reproduced, copied,
transmitted or used to make a derivative work, by either mechanical, electronic or any other means in whole or in part,
without prior written consent from DPS Telecom, except as required by United States copyright laws.
© 2010 DPS Telecom
Notice
The material in this manual is for information purposes and is subject to change without notice. DPS Telecom shall not be
liable for errors contained herein or consequential damages in connection with the furnishing, performance, or use of this
manual.
Contents
Visit our website at www.dpstelecom.com for the latest PDF manual and FAQs
1 NetGuardian G5 Overview
1
2 About This Manual
2
3 Shipping List
2
3.1 Port Allocation
4
4 Optional Accessories
4
5 Specifications
7
6 Hardware Installation
8
6.1 Tools Needed
8
6.2 Mounting
8
6.3 Power Connection
9
6.4 LAN Connection
12
6.5 Telco Connection
13
6.6 Alarm and Control Relay Connections
13
6.6.1
Alarm and Control Relay Connector Pinout Table (832A)
14
6.6.2
Alarm and Control Relay Connector Pinout Table (864A)
15
6.6.3
Discretes 1–24 Connector Pinout Diagram (832A)
16
6.6.4
Analogs1–6/Discretes 25–32/Relays 1–8 Connector Pinout Diagram (832A)
17
6.6.5
Discretes 1- 48 Connector Pinout Diagram (864A)
18
6.6.6
Analogs 1-6/Discretes 49-64/Relays 1-8 Connector Pinout Diagram (864A)
19
6.6.7
Analog Dipswitches
20
6.6.8
Integrated Temperature and Battery Sensor (Optional)
21
6.7 Data Ports
21
6.7.1
Connecting NetGuardian Accessories
23
6.7.2
GLD/ECU Expansion Port (RS-485)
23
6.8 Integrated 10/100BaseT Ethernet Switch (Optional)
23
6.9 GSM/GPRS or CDMA Wireless Modem Top Board (Optional)
25
6.10 +12 or +24 VDC Sensor Power Supply
26
6.11 Optional 66 Block Connector (832A)
27
6.12 Optional 66 Block Connector (864A)
29
6.13 Optional Hinged Wire-Wrap Back Panel
31
6.13.1 Lexan Wire-Wrap Cover
32
6.14 Optional Hinged Pluggable Back Panel
33
6.15 Controls
35
7 LCD Display
36
7.1 Alarm and Control Status Messages
37
7.2 LCD Command Menu
37
7.2.1
Sound off
38
7.2.2
Reboot
38
7.2.3
Run Config
39
7.2.4
Contrast
39
8 Alarm Speaker
39
9 Front Panel LEDs
40
10 Back Panel LEDs
41
11 Configuring the NetGuardian
41
11.1 RADIUS Authentication (Available as of Firmware 5.0I)
12 Connecting to the NetGuardian
42
42
12.1 ... via Craft Port
42
12.2 ... via LAN
43
13 TTY Interface
13.1 Unit Configuration
44
44
13.1.1 Ethernet Port Setup
44
13.1.2 SFP Fiber Connection (For Fiber Build Option)
46
13.1.3 Edit PPP Port
47
13.1.4 Tune 202 Modem
48
13.1.5 RADIUS Configuration
49
13.1.6 New! - TTY Command Mode
50
13.2 Monitoring
13.2.1 Monitoring the NetGuardian
53
53
13.2.1.1 Monitoring Base Alarms
13.2.1.2 Monitoring Ping Targets
13.2.1.3 Monitoring and Operating Relays (Controls)
13.2.1.4 Monitoring Analogs
53
13.2.1.5 Monitoring System Alarms
13.2.1.6 Monitoring Data Port Activity
13.2.1.7 Monitoring the Accumulation Timer
56
54
55
55
56
56
13.2.2 Viewing Live Target Pings
57
13.2.3 Proxy Menu
57
13.2.4 Event Logging
58
13.2.5 Backing Up NetGuardian Configuration Data via FTP
59
13.2.5.1 Reloading NetGuardian Configuration Data
13.2.6 Debug Input and Filter Options
14 Reference Section
14.1 Display Mapping
14.1.1 System Alarms Display Map
59
60
61
61
63
14.2 SNMP Manager Functions
66
14.3 SNMP Granular Trap Packets
68
14.4 Trap SNMP Logic
70
14.5 ASCII Conversion
70
14.6 RADIUS Disctionary File (Available on Resource Disk)
71
15 Frequently Asked Questions
72
15.1 General FAQs
72
15.2 SNMP FAQs
75
15.3 Pager FAQs
76
16 Technical Support
77
1
1 NetGuardian G5 Overview
Fig. 1.1. The NetGuardian has all the tools you need to manage your remote site.
The NetGuardian G5 — The Intelligent RTU for Complete Site Management
The NetGuardian G5 is a RoHS 5/6-compliant, LAN-based, SNMP/DCPx remote telemetry unit. The
NetGuardian has all the tools you need to manage your remote sites, including built-in alarm monitoring, paging
and email capabilities that can eliminate the need for an alarm master.
With the NetGuardian, you can:
· Monitor 32 discrete alarms, 32 ping alarms, and 8 analog alarms
· Control remote site equipment via 8 terminal server ports and 8 control relays
· Monitor your remote site from anywhere using the NetGuardian's built-in Web Browser Interface.
· Report alarms to multiple SNMP managers or the T/Mon NOC Alarm Monitoring System.
· Report alarms via LAN or dial-up connection.
· Automatically send pager and email alarm notifications 24/7.
· Connect multiple concurrent users via Telnet over LAN to telecom switches, servers, radios, PBXs and
other equipment.
· Monitor discrete and analog threshold alarms.
· Ping IP network devices and verify that they're online and operating.
New: The NetGuardian G5 supports serial baud rates up to 115,200, additional RS485 for GLD/ECU expansion
polling port, triple CPU speed for faster processing, optional built-in 4-port switch (tied to NET2), optional
external temperature sensor, analog readings accurate to within +/- 1%, dual 10/100 NICs (isolated) replacing
the 10BaseT NICs, SNMPv2c, SNMPv2c Inform trap, and SNMPv3.
TIP: This is the basic installation and hardware manual. For software and web configuration manuals, please
refer to appropriate manual on the Resource CD included with your shipment or visit the DPS website at www.
dpstele.com/pdfs/op_guides
Stand-alone local visibility
You don't need an alarm master unit to monitor your site with the NetGuardian. With the NetGuardian's built-in
Web Browser Interface, you can access the NetGuardian, view alarms and control remote site devices from any
computer anywhere in your network.
24/7 pager and email alerts - no master needed
Out of the box, the NetGuardian supports 24/7 pager and email reporting. Send alarms directly to maintenance
technicians in the field, even when no one's in the office.
Connect via LAN to telecom switches, servers, radios and more
Each of the NetGuardian's eight serial ports can be individually configured to serve as a craft port, a channel port
or a TCP or UDP reach-through port, giving you LAN-based terminal server access to up to eight serial devices.
NEW - RADIUS Authentication (As of firmware v5.0I)
Take the security of your alarm remotes to the next level with RADIUS authentication. Now the NetGuardian
G5 can interact with your RADIUS server, integrating it as part of your enterprise management.
2
Reports to multiple SNMP managers and T/Mon NOC simultaneously
The NetGuardian reports to both the T/Mon NOC Alarm Monitoring System and any SNMP manager. You can
simultaneously forward alarms from the NetGuardian to T/Mon NOC and multiple SNMP managers at multiple
IP addresses. Alarms can also be configured to dispatch to one, some, or all SNMP managers.
2 About This Manual
There are three separate user manuals for the NetGuardian G5: the Hardware Manual (which you're reading
now), the NGEditG5 User Manual, and the NetGuardian G5 Web Interface User Manual.
This Hardware Manual provides instructions for hardware installation and using the TTY interface. The
NGEditG5 and Web Interface User Manuals, included on the NetGuardian Resource CD, provide instructions for
configuring the NetGuardian using the Windows-based NGEditG5 utility software or the Web Interface.
3 Shipping List
While unpacking the NetGuardian, please make sure that all of the following items are included. If some parts
are missing, or if you ever need to order new parts, please refer to the part numbers listed and call DPS Telecom
at (800) 622-3314.
NetGuardian 832A G5: D-PK-NETG5-12001
NetGuardian 864A G5: D-PK-NG864-12001
NetGuardian G5 Hardware
Manual D-OC-UM102.26100
NetGuardian G5 Resource CD
(includes manuals, MIBs, and software)
DB9M-DB9F Download Cable 6 ft.
D-PR-045-10-A-04
Two Ethernet Cables 14 ft.
D-PR-923-10A-14
Telephone Cable 6 ft.
D-PR-045-10A-01
23" Rack Ears
19" Rack Ears
3
Eight 3/8" Ear Screws
Four Standard Rack Screws
Four Metric Rack Screws
Three 3/4-Amp GMT Main Power Fuses
Two Large Power Connector Plugs for Main Power
Four Cable Ties
(Sixteen with hinged panel)
4 Pin Analog Connector
Pads
Screws and connectors are packaged in a sealed hardware kit, shown above
(Hardware kit containing a WAGO connector)
Optional Items
Two 1/4-Amp GMT Accessory Fuses
External Temperature Sensor
D-PR-984-10A-10
One Small Power Connector Plug for Sensor Output
4
3.1 Port Allocation
Located on the top of the unit in the back left corner is the Port Allocation Sticker. This sticker includes your
part number (D-PK-NETG5-#####.#####), which specifies your build option. The table below it lists your port
allocation.
4 Optional Accessories
You can extend the capabilities of the NetGuardian through accessory units that provide greater discrete alarm
capacity, remote audiovisual alarm notification, visual surveillance of remote sites, and other options. If you
would like to order any of these accessories, or if you would like more information about them, call DPS
Telecom at (800) 622-3314.
NetGuardian Expansion (NetGuardian DX G4)
D-PK-NETDX-12022.00001
The NetGuardian Expansion G4 provides an additional 48 discrete and 8 relay controls. Up to three NetGuardian
Expansions can be daisy-chained off one NetGuardian, providing a total of 176 discrete and 32 analog alarm
points.
NetGuardian Expansion
The NetGuardian 480 (NG480) Expansion provides an additional 80 alarms and 4 relays. With 80 discrete alarm
inputs, you can easily forward all the alarms of a small to medium-sized site.
5
NetGuardian E16
D-PK-DXE16
Adding the NetGuardian E16 provides an additional 16 alarm points and 16 controls. One NetGuardian E16 unit
may be used per NetGuardian 832A/864A G5 remote. In this configuration, the E16 must be the last unit in the
chain. Having only 1 serial port, it cannot forward traffic to a subsequent RTU.
General LCD Display (GLD)
D-PC-820-10A-04
The General LCD Display (GLD) is a small wall-mounted remote terminal for the NetGuardian. The LCD
display shows system status and alarm messages, and the built-in speaker gives an audible notice of alarms. Up
to 12 GLDs can be daisy-chained off the NetGuardian.
NetGuardian SiteCAM
D-PK-CAMRA-12001.00001
The NetGuardian SiteCAM provides streaming video security surveillance of remote sites. The SiteCAM
connects to either the NetGuardian's integrated 10/100BaseT switch or a separate 10/100/1000 switch. SiteCAM
video can be accessed directly from the NetGuardian's Web Browser Interface. Up to four cameras can be
supported.
Hinged Wire-Wrap Back Panel
For 19" rack: D-PK-NGPAN-12002
For 23" rack: D-PK-NGPAN-12006
The hinged wire-wrap back panel provides wire-wrap connections for the NetGuardian's alarms and control
relays.
6
Pluggable Barrier Panel
For 19" rack: D-PK-NGPAN-12003
For 23" rack: D-PK-NGPAN-12007
The pluggable barrier panel provides screw-lug barrier plug connections for the NetGuardian's alarms and
control relays.
NetGuardian 3288 Test Fixture
D-PK-TSTBX-12005.00001
Every DPS product is rigorously tested before shipping, and the NetGuardian Test Box allows technicians to
verify every discrete alarm input, control relay, and voltage-based analog alarm input on a NetGuardian G5. This
time-tested tool is now available to you as the NetGuardian 3288 Test Fixture (known casually as the
"NetGuardian Test Box"). With 32 discrete alarm toggles, 8 analog knobs, and 8 control relay LEDs, you can
verify every alarm input and control output on your NetGuardians in a controlled way.
7
5 Specifications
Discrete Alarm Inputs:
Analog Alarms:
Control Relays:
Ping Alarms:
Protocols:
Interfaces:
Dimensions:
Weight:
Mounting:
Power Input:
`
Power Output:
Current Draw:
Fuse:
Modem:
Visual Interface:
Audible Notification:
Operating Temperature:
Operating Humidity:
*RoHS 5 Approved
32 (expandable to 80, 128, or 176 in G5 model)
64 (expandable to 112, 160, or 208 in 864A model)
8
Analog Input Range: (–94 to 94 VDC or 4 to 20 mA)
8 Form C (expandable to 16, 24, 32)
Maximum Voltage: 60 VDC/120 VAC
Maximum Current: 1 Amp, AC/DC
32
SNMPv1, SNMPv2c, SNMPv3, DCPx, DCPf, TRIP, SNPP
SMTP, TAP, HTTP, FTP, TELNET, ICMP, RADIUS
9 RJ45 Yost serial ports
2 RJ45 10/100 Ethernet ports (1 port tied internally to switch- if switch option is
purchased)
1 RJ11 telco jack
2 50-pin amphenol connectors (discretes, controls, and analogs)
1 4-pin screw connector (analogs)
With Fiber top-board build option: 4 10/100/1000 copper Ethernet ports AND
2- 1000 Base-X SFP Fiber ports
1.75"H x 17"W x 12"D (4.5 cm x 43.2 cm x 30.5 cm)
4 lbs. 3 oz. (1.9 kg)
19" or 23" rack
–48VDC (–40 to –70 VDC)
(Optional) –24 VDC (–18 to –36 VDC)
(Optional) Wide Range –24/–48 VDC ( –18 to –72 VDC)
(Optional) +24VDC (+20 to +34VDC)
(Optional)12 VDC or 24 VDC power output for external sensor
200 mA
3/4 amp GMT for power inputs
1/4 amp GMT for external sensor power output and integrated Ethernet switch
33.6 K internal
LCD display
16 bicolor LEDs
5 unicolor LEDs (10 with Switch Option)
Alarm speaker
32°–140° F (0°–60° C)
0%–95% noncondensing
8
6 Hardware Installation
6.1 Tools Needed
To install the NetGuardian, you'll need the following tools:
Phillips No. 2 Screwdriver
Small Standard No. 2 Screwdriver
Wire Strippers/Cutter
Wire Wrap Gun (if hinged wire wrap panel is used)
Punch Down Tool (if 66 blocks are used)
PC with NGEditG5 software
6.2 Mounting
Fig. 6.2.1. The NetGuardian can be flush or rear-mounted
The NetGuardian mounts in a 19" rack or a 23" rack using the provided rack ears for each size. Two rack ear
locations are provided. Attach the appropriate rack ears in the flush-mount or rear-mount locations shown in
Figure 6.2.1.
Note: Rack ears can be rotated 90° for wall mounting or 180º for other mounting options (not shown).
9
6.3 Power Connection
Fig. 6.3.1. Power connectors and fuse.
The NetGuardian has two screw terminal barrier plug power connectors, located on the left side of the back
panel. (See Figure 6.3.1.)
WARNING!
The Grounding Lug on the back of the unit provides a permanent connection to earth
ground when connected. The Grounding Lug must be used in order to comply with
standards.
Grounding Lug and Symbol
Before you connect a power supply to the NetGuardian, test the voltage of your power supply:
·
Connect the black common lead of a voltmeter to the ground terminal of the battery, and connect the red
lead of the voltmeter to the battery's –48 VDC terminal. The voltmeter should read between –43 and –
53 VDC. If the reading is outside this range, test the power supply.
To connect the NetGuardian to a power supply, follow these steps:
1. Remove the fuse from the back panel of the NetGuardian. Do not reinsert the fuse until all
connections to the unit have been made.
2. Remove the power connector plug from Power Connector A. Note that the plug can be inserted into the
power connector only one way — this ensures that the barrier plug can only be reinserted with the
correct polarity. Note that the –48V terminal is on the left and the GND terminal is on the right.
3. Use the grounding lug to connect the unit to earth ground. The grounding lug is next to the
symbol.
Insert the eyelet of the earth ground cable between the two bolts on the grounding lug (Ground cable not
included).
4. Insert a battery ground into the power connector plug's right terminal and tighten the screw; then
insert a –48 VDC line to the plug's left terminal and tighten its screw.
5. Push the power connector plug firmly back into the power connector. If the power feed is connected
10
correctly, the LED by the connector will light GREEN. If the polarity of the power feed is reversed, the
LED will not illuminate.
6. Repeat Steps 2–4 for Power Connector B.
7. Reinsert the fuse to power the NetGuardian. The front panel LEDs will flash RED and GREEN.
To connect the NetGuardian to a power supply using a WAGO connector, follow these steps:
WARNING!
The Grounding Lug on the back of the unit provides a permanent connection to earth
ground when connected. The Grounding Lug must be used in order to comply with
standards.
Grounding Lug and Symbol
1. Remove the 2 fuses (A& B) from the back panel of the NetGuardian. Do not reinsert the fuses until all
connections to the unit have been made.
2. Remove the WAGO power connector. Note that the plug can be inserted into the power connector only one
way — this ensures that the barrier plug can only be reinserted with the correct polarity. Note that the –48V
terminal is on Slots 1 and 3 and the GND terminal is on Slots 2 and 4.
3. Use the grounding lug to connect the unit to earth ground. The grounding lug is next to the
symbol.Insert
the eyelet of the earth ground cable between the two bolts on the grounding lug (Ground cable not included).
4. Insert a battery ground into the power connector plug's slots 2 and 4 by pushing down on top of the
appropriate slot of the WAGO connector with a screwdriver and inserting the wire into the slot, then releasing
the screwdriver. Insert a –48 VDC line to the plug's slots 1 and 3 using the same method as before.
11
Inserting a -48 VDC Line into Slot 1 of WAGO
Connector
5. Push the power connector plug firmly back into the power connector. If the power feed is connected correctly,
the LED by the connector will light GREEN. If the polarity of the power feed is reversed, the LED will not
illuminate.
6. Reinsert the fuses to power the NetGuardian. The front panel LEDs will flash RED and GREEN.
12
6.4 LAN Connection
RJ45 Ethernet Connection
8
7
6
5
4
3
2
1
Fig. 6.4.1. Two 10/100 Ethernet ports (With Switch)
Receive In– (RI–)
Receive In + (RI+)
Transmit Out– (TO–)
Transmit Out + (TO+)
Fig. 6.4.3 Ethernet port pinout
Fig. 6.4.2. Two 10/100 Ethernet ports (Without Switch)
For enhanced security, the NetGuardian G5 has two 10/100 Ethernet ports. Each port has its own separate IP
address and subnet, so you can safely connect one port to your private company LAN and the other to the public
Internet.
There is no routing between Net 1 and Net 2, this ensures that both connections are independent of each other.
By default, outbound data traffic from the NetGuardian 832A will be sent over Net 2. Only outbound data that is
specifically directed to Net 1, usually the Company's LAN, will be sent to Net 1. To use both network interfaces,
be sure Net1 and Net2 are on separate Subnet Masks.
To use only one of the network interfaces, set either Net1 or Net2 to IP address being used and set the unused
network IP subnet and gateway to 255.255.255.0. If your NetGuardian has the 4-port hub build option, use Net2,
which is connected to the Hub. Both ports are standard RJ45 ports that take standard RJ45 Ethernet cables. If the
IP connection is OK, the LNK LED will light SOLID GREEN when the cable is connected.
The NetGuardian G5 unit with the integrated switch comes with two physical 10/100 Ethernet ports. The
standard G5 unit without the switch comes equipped with two physical Ethernet ports. The switch is internally
tied to NET2 and any one of its four ports can be used for uplink.
Build Option: NetGuardian G5 with GigE Fiber Top Board
If your NetGuardian G5 was ordered with the GigE Fiber top board, 1000Base SFP interface must be used. The
SFP ports are internally connected to the 4 port switch and NET 2.
Fig. 6.4.4. Back panel of NetGuardian G5 with fiber
13
6.5 Telco Connection
Fig. 6.5.1. Telco jack
The rear panel telco jack (see Figure 6.5.1) connects the NetGuardian internal modem to a standard phone line
for dial-up access and pager alarm notification.
RJ11 Phone Line Connection
4
3 Ring
2 Tip
1
Fig. 6.5.2 Telco jack pinout
The pinout for the Telco jack is shown in Figure 6.5.2, above.
6.6 Alarm and Control Relay Connections
Fig. 6.6.1. Alarm and control relay connectors
The NetGuardian G5's discrete alarm inputs, control relay outputs, and first six analog alarm inputs are
connected through the two 50-pin connectors labeled "Discretes 1–24" and "Analogs 1–6/Discretes 25–32/Relays
1–8" on the back panel. Analog alarm inputs 7 and 8 are connected through the four-pin connector labeled
"Analogs 7–8." (See Figure 6.6.1.)
Note: The NetGuardian's 864A's discrete alarm inputs, control relay outputs, and first six analog alarm inputs are
connected through the two 50-pin connectors labeled "Discretes 1–48" and "Analogs 1–6/Discretes 49–64/Relays
1–8" on the back panel. Analog alarm inputs 7 and 8 are connected through the four-pin connector labeled
"Analogs 7–8."
14
6.6.1 Alarm and Control Relay Connector Pinout Table (832A)
Discretes 1–25
ALM 1
1
26
ALM 13
13
38
Discretes 25–32
RTN ALM
1
26
ALM 25
ALM 2
2
27
ALM 14
14
39
ALM 26
2
27
CTRL 2
10
35
ALM 3
3
28
ALM 15
15
40
ALM 27
3
28
CTRL 3
11
36
ALM 4
4
29
ALM 16
16
41
ALM 28
4
29
CTRL 4
12
37
ALM 5
5
30
ALM 17
17
42
ALM 29
5
30
CTRL 5
13
38
ALM 6
6
31
ALM 18
18
43
ALM 30
6
31
CTRL 6
14
39
32
CTRL 7
15
40
33
CTRL 8
16
41
FUSE
17
42
RTN ALM
RTN
ALM
ALM 7
7
32
ALM 19
19
44
ALM 31
7
ALM 8
8
33
ALM 20
20
45
ALM 32
8
ALM 9
9
34
ALM 21
21
46
ALM 10
10
35
ALM 22
22
47
ALM 11
11
36
ALM 23
23
48
ALM 12
12
37
ALM 24
24
49
GND
25
50
Analogs 1–6
+
Analogs 7–8
ADC
–
+
ADC 1
19 44
7
7–
7+
ADC 2
20 45
8
8–
8+
ADC 3
21 46
ADC 4**
22 47
ADC 5**
23 48
ADC 6**
24 49
GND
25 50
ADC
Control Relays 1–8
NO/NC CO
9
34
CTRL 1
–
ANA 7 –
ANA 8 +
ANA 7 +
ANA 8 –
Analogs 7–8
Table 6.6.1.A. Alarm and control relay connector pinout for G5
Table 6.6.1.A shows the pinouts for the 50-pin connectors "Discretes 1–24" and "Analogs 1–6/Discretes 25–
32/Relays 1–8," and the pinout for the four-pin connector "Analogs 7–8."
Note that the NetGuardian's control relays can be set for either Normally Open or Normally Closed operation. By
factory default, all control relays are set to Normally Open. You can reset all relays for Normally Closed
operation at the hardware level by resetting a jumper on the NetGuardian circuit board. You can also configure
the control relays individually, using either the Web interface or the NGEditG5 software utility.
For instructions on resetting control relays for Normally Closed operation, see Section 6.12, "Jumper Options."
ADC** channels 4, 5, and 6 may be unavailable for external use. These analog channels are
sometimes configured in hardware for monitoring A and B power feeds, and internal temperature. For
details regarding your unit's hardware, please reference the product description appendix.
15
6.6.2 Alarm and Control Relay Connector Pinout Table (864A)
Discretes 1–48
Discretes 49-64, Relays 1-8, Analogs 1-6
ALM
PIN
ALM
PIN
ALM
PIN
Relays 1-8
1
26
26
13
49
26
RLY 1
9
34
2
1
27
39
50
1
RLY 2
10
35
3
27
28
14
51
27
RLY 3
11
36
4
2
29
40
52
2
RLY 4
12
37
5
28
30
15
53
28
RLY 5
13
38
6
3
31
41
54
3
RLY 6
14
39
7
29
32
16
55
29
RLY 7
15
40
8
4
33
42
56
4
RLY 8
16
41
9
30
34
17
57
30
FUSE
17
42
10
5
35
43
58
5
ADC
+
-
11
31
36
18
59
31
ADC 1
19
44
12
6
37
44
60
6
ADC 2
20
45
13
32
38
19
61
32
ADC 3
21
46
14
7
39
45
62
7
ADC 4**
22
47
15
33
40
20
63
33
ADC 5**
23
48
16
8
41
46
64
8
ADC 6**
24
49
17
34
42
21
GND
25
18
9
43
47
GND/RTN*
50
19
35
44
22
20
10
45
48
21
36
46
23
22
11
47
49
23
37
48
24
24
12
GND
25
25
38
GND/RTN*
50
Analogs 7-8
ADC +
7
B A
8
B A
Table 7.B. Alarm and relay connection pinouts for NetGuardian G5 864
RTN* is the alarm return pin. Alarms on standard units are dry closure or ground closure. Most units
will have RTN internally tied to GND. However, special hardware assemblies may have RTN isolated
from GND. For details regarding your unit's hardware, please reference the product description
appendix.
ADC** channels 4, 5, and 6 may be unavailable for external use. These analog channels are
sometimes configured in hardware for monitoring A and B power feeds, and internal temperature. For
details regarding your unit's hardware, please reference the product description appendix.
16
6.6.3 Discretes 1–24 Connector Pinout Diagram (832A)
RTN 1
RTN 2
RTN 3
RTN 4
RTN 5
RTN 6
RTN 7
RTN 8
RTN 9
RTN 10
RTN 11
RTN 12
RTN 13
RTN 14
RTN 15
RTN 16
RTN 17
RTN 18
RTN 19
RTN 20
RTN 21
RTN 22
RTN 23
RTN 24
GND
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
ALM 1
ALM 2
ALM 3
ALM 4
ALM 5
ALM 6
ALM 7
ALM 8
ALM 9
ALM 10
ALM 11
ALM 12
ALM 13
ALM 14
ALM 15
ALM 16
ALM 17
ALM 18
ALM 19
ALM 20
ALM 21
ALM 22
ALM 23
ALM 24
GND
Fig. 6.6.2.1. Pinout Diagram for Discretes 1–24 connector
17
6.6.4 Analogs1–6/Discretes 25–32/Relays 1–8 Connector Pinout Diagram
(832A)
RTN 25
RTN 26
RTN 27
RTN 28
RTN 29
RTN 30
RTN 31
RTN 32
CTRL 1 NO
CTRL 2 NO
CTRL 3 NO
CTRL 4 NO
CTRL 5 NO
CTRL 6 NO
CTRL 7 NO
CTRL 8 NO
FUSE NO
Unused
ANA 1 +
ANA 2 +
ANA 3 +
ANA 4 +
ANA 5 +
ANA 6 +
GND
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
ALM 25
ALM 26
ALM 27
ALM 28
ALM 29
ALM 30
ALM 31
ALM 32
CTRL 1 CO
CTRL 2 CO
CTRL 3 CO
CTRL 4 CO
CTRL 5 CO
CTRL 6 CO
CTRL 7 CO
CTRL 8 CO
FUSE CO
Unused
ANA 1 –
ANA 2 –
ANA 3 –
ANA 4 –
ANA 5 –
ANA 6 –
GND
Fig. 6.6.3.1. Pinout Diagram for Discretes 25–32/Relays 1–8 connector
18
6.6.5 Discretes 1- 48 Connector Pinout Diagram (864A)
Fig. 6.6.5.1- Pinout Diagram for Discretes 1-48 Connector
RTN* is the alarm return pin. Standard configurations have this pin tied to GND. While it is possible to
change this configuration to utilize different types of alarms (i.e. TTL, Open Collector, Battery Closure),
the hardware must be ordered in that configuration. It is NOT field-adjustable.
.
19
6.6.6 Analogs 1-6/Discretes 49-64/Relays 1-8 Connector Pinout Diagram
(864A)
Fig. 6.6.5.2- Pinout Diagram for Analogs 1-6/Discretes 49-64/Relays 1-8 Connector
RTN* is the alarm return pin. Standard configurations have this pin tied to GND. While it is possible to
change this configuration to utilize different types of alarms (i.e. TTL, Open Collector, Battery Closure),
the hardware must be ordered in that configuration. It is NOT field-adjustable.
20
6.6.7 Analog Dipswitches
The analogs are controlled by the dipswitches accessible via the top sliding panel. For milliamp sensor operation
(current loop), turn the dipswitch on by placing it in the up (ON) position. For voltage operation, place the
dipswitch in the down (OFF) position.
You can access the analog dipswitches via the sliding hatch panel on top of the unit
WARNING: Do not put the dipswitches in the upward, ON position (current loop mode) unless
you are sure of the analog setting. Having the dipswitch on puts a 250 ohm resistor across the
input lines. Any voltage beyond 5V or 20 mA will damage components.
21
6.6.8 Integrated Temperature and Battery Sensor (Optional)
Fig. 6.6.6.1. The external temperature sensor
The optional integrated temperature and battery sensor monitors the ambient temperature and the NetGuardian's
power inputs. This option is available only if it was ordered with your NetGuardian. The integrated temperature
sensor measures a range of 32° F to 140° F (0° C to 60° C) within an accuracy of ± 1°.
Sensor Function
Temperature
Power Feed A
Power Feed B
Temperature
Analog Input Options
Can be used on analog input 4 (Internal)
Can be used on analog input 5
Can be used on analog input 6
Can be used on analog input 8 (External)
Table 6.6.6.A. Integrated sensor connection options
Each integrated sensor takes the place of an analog input, and does not need any external connections. No other
analog input can be connected to the input point used for the integrated sensors. Table 6.6.6.A lists the
connection options for the integrated temperature sensor. Note that these options are set at the factory, based on
the option ordered, and cannot be adjusted by the user.
6.7 Data Ports
Fig. 6.7.1. Data ports 1–8
The NetGuardian's eight data ports provide reach-through terminal server functionality for connecting multiple
simultaneous users to external equipment via Telnet over LAN. Each port can function as a proxy connection to
an external device, a craft port, a channel port, a TCP or UDP reach-through port. The NetGuardian can support
simultaneous proxy connections for up to eight users.
22
Yost RS-232 RJ45 Connector
Yost RS-485 RJ45 Connector
8 RTS (Request to Send)
7 DTR (Data Terminal Ready)
6 TXD (Transmit Data)
5 GND (Ground)
4 GND (Ground)
3 RXD (Receive Data)
2 DSR (Data Set Ready)
1 CTS (Clear to Send)
8 TX- (Transmit -)
7 N/C (Not Connected)
6 RX- (Receive -)
5 GND (Ground)
4 GND (Ground)
3 RX+ (Receive +)
2 N/C (Not Connected)
1 TX+ (Transmit +)
Yost 4-Wire 202 Connector
8 TX+ (Transmit +)
7 N/C (Not Connected)
6 RX- (Receive -)
5 GND (Ground)
4 GND (Ground)
3 RX+ (Receive +)
2 N/C (Not Connected)
1 TX- (Transmit -)
Fig. 6.7.2 Data port pinouts
Location of Pin 1 on RJ-45
Connector
NetGuardian data ports can be configured for Yost RS-232, RS-485, and 4-wire 202 RJ45 connects. These data
ports are available as optional builds on NetGuardian hardware units (Call DPS Sales for more information @
1-800-693-0351). The pinouts for Data Ports 1–8 are shown in Figure 6.7.2, above.
DB9 RS-232
RX
GND
TX
5 4 321
98 7 6
RTS
CTS
Pin # Signal
Description
1
2
3
4
5
6
7
8
9
Not connected
Transmit data
Recieve Data
Not connected
Ground
Not connected
Clear to send
Request to send
Not connected
TX
RX
GND
CTS
RTS
Fig. 6.7.2 DB9 RS-232 Pinouts (Craft Port Only)
23
6.7.1 Connecting NetGuardian Accessories
Some NetGuardian accessories must be connected to particular data ports. However, if you don't use these
accessories, the data ports are available for other uses.
If you are using a NetGuardian Expansion, connect it to Port 7.
6.7.2 GLD/ECU Expansion Port (RS-485)
If you are using a General LCD Display (GLD) unit, connect it to the GLD/ECU port.
GLD/ECU Port
Data Port Pinout
6.8 Integrated 10/100BaseT Ethernet Switch (Optional)
Fig. 6.8.1. NetGuardian integrated Ethernet Switch
You can order your NetGuardian G5 with an optional integrated Ethernet switch, which provides four regular
Ethernet ports. (See Figure 6.8.1.). The integrated Ethernet switch is powered by the same –48 VDC power as
the NetGuardian, which provides more secure, more robust operation than switches that run off commercial
power. The integrated switch also frees valuable rack space by eliminating an unnecessary extra unit.
To power and activate the integrated Ethernet switch, insert the provided 1/4 amp fuse in the switches fuse
socket. (See Figure 6.8.1.) If you ever want to turn off power to the integrated switch, just remove the fuse.
24
RJ45 Ethernet Connection
8
7
6
5
4
3
2
1
Trasmit Out – (TO–)
Transmit Out + (TO+)
Receive In – (RI–)
Receive In + (RI+)
Fig. 6.8.2. Regular Ethernet port pinout
The four Ethernet ports of the switch are regular straight-through Ethernet ports. (See Figure 6.8.1.) The pinout
for the regular Ethernet ports is shown in Figure 6.8.2, above.
25
6.9 GSM/GPRS or CDMA Wireless Modem Top Board (Optional)
Fig. 6.9.1. NetGuardian G5 wireless modem option.
You can order your NetGuardian G5 with an optional GSM/GPRS or CDMA wireless modem, which provides
wireless network connection. (See Figure 6.9.1.). The wireless modem is powered by the same –48 VDC power
as the NetGuardian, which provides more secure, more robust operation than modems that run off commercial
power.
To power and activate the wireless modem top board, insert the provided 1/4 amp fuse in the wireless
modems fuse socket. (See Figure 6.9.1.) If you ever want to turn off power to the wireless modem, just remove
the fuse.
You may use any service provider you choose for your wireless connectivity.
DPS Telecom has tested and recommends using CrossBridge Solutions.
www.crossbridgesolutions.com
Phone: (800) 668-4368
Email: info@crossbridgesolutions.com
Below is a diagram of a connection scenario using CrossBridge.
Simplified diagram of CrossBridge Connection
26
6.10 +12 or +24 VDC Sensor Power Supply
Fig. 6.10.1. +12 VDC sensor power supply
You can order your NetGuardian G5 with an optional +12 VDC or +24 VDC sensor power supply. (See Figure
6.10.1.) This provides a convenient way to connect an auxiliary sensor to a robust battery power supply.
The two-pin connector for the sensor power supply is a barrier plug connector similar to the main power
connector.
To power an external sensor, follow these steps:
1. Remove the 1/4 amp fuse from the sensor power supply on the back panel of the NetGuardian. (See
Figure 6.10.1.) Do not reinsert the fuse until all power connections to the external sensor have been
made.
2. Remove the power connector plug from the sensor power supply. Note that the plug can be inserted into
the power connector only one way — this ensures that the barrier plug can only be reinserted with the
correct polarity. Note that the positive terminal is on the left and the negative terminal is on the right.
3. Connect the appropriate leads to each of the plug's screw terminals and tighten the screws.
4. Push the power connector plug firmly back into the sensor power supply connector.
5. Reinsert the fuse to power the external sensor.
27
6.11 Optional 66 Block Connector (832A)
Both of the 50-pin connectors on the back panel of the NetGuardian can be connected to the optional 25-pair 66
Block Connector (part number D-PR-966-10A-00). For 66 block pinout and color code information, see Figure
6.11.1 for Discretes 1–24 and Figure 6.11.2. for Analogs 1–6/Discretes 25–32/Relays 1–8.
Note: If connecting to a 50-pair split block, all connections should be made on the two pin columns closest to the
right-hand side of the block or bridge clips should be installed.
Fig 6.11.1. Optional 66 block pinout for Discretes 1–24
28
Fig. 6.11.2. Optional 66 block pinout for Analogs 1–8/Discretes 25–32/Relays 1–8
29
6.12 Optional 66 Block Connector (864A)
Both of the 50-pin connectors on the back panel of the NetGuardian can be connected to the optional 66 block,
25 pair block (part number D-PR-966-10A-00). See Figure 6.12.1 for pinout and color code information for
Discretes 1–48 and Figure 6.12.2 for pinouts and color code information for Discretes 49–64, Relays 1–8, and
Analogs 1–6.
Note: If connecting to a 50-pair split block, all connections should be made on the two pin columns closest to the
right-hand side of the block.
Fig. 6.12.1 66 Block connections for Discretes 1–48
RTN* is the alarm return pin. Alarms on standard units are dry closure or ground closure. Most units
will have RTN internally tied to GND. However, special hardware assemblies may have RTN isolated
from GND. For details regarding your unit's hardware, please reference the product description
appendix.
30
Fig. 6.12.2. 66 Block connections for Discretes 49–64, Relays 1–8, and Analogs 1–6
RTN* is the alarm return pin. Alarms on standard units are dry closure or ground closure. Most units
will have RTN internally tied to GND. However, special hardware assemblies may have RTN isolated
from GND. For details regarding your unit's hardware, please reference the product description
appendix.
31
6.13 Optional Hinged Wire-Wrap Back Panel
Turn the plastic swivel
to the vertical position
to lock in place
Fig. 6.13.1. The hinged wire-wrap back panel is mounted on the mounting rack of the NetGuardian
Alarm Pinout for NG864 is different than the NG832 and is not compatible with NG832
hinged panel termination units
WARNING
The optional hinged wire-wrap back panel provides wire-wrap connections for the NetGuardian's alarms and
control relays. To connect alarms and control relays to the wire-wrap panel, follow these steps:
1. Mount the hinged wire-wrap back panel on the mounting rack of the NetGuardian. (See Figure 6.13.1.)
2. Close the hinged back panel and lock in place by turning the black plastic locking swivel to the vertical
position.
3. Connect discrete alarms, analog alarms, and control relays to the two pin blocks. Figures 6.13.2 and
Figure 6.13.3 show the pinouts for the wire-wrap back panel.
(Shown with point 5 wired)
+0
Discretes 1 - 10
(Return 1 - 10)
Discretes 11 - 20
+2
+4
+6
+8
10
1
RET
RET
11
20
RET
(Return 11 - 20) RET
Discretes 21 - 30
21
30
(Return 21 - 30)
RET
RET
+0
+2
+4
+6
+8
Fig. 6.13.2. Wire-wrap pinouts for Discretes 1–30
32
Analogs 1 - 8
+0
+2
+4
+6
+8
+0
+2
+4
+6
+8
+
_
Discretes 31 - 32
(Return 31 - 32)
Controls 1 - 8
N/O
COM
Fig. 6.13.3. Wire-wrap pinouts for Discretes 31–32, Analogs 1–8, and Controls 1–8
6.13.1 Lexan Wire-Wrap Cover
Spacer
Lexan panel
Lexan panel bracket
Securing screw
Fig. 6.13.1.1. Lexan panel assembly
To attach the Lexan cover to the hinged wire-wrap panel, follow these steps:
1. Attach communication lines to the wire-wrap pins before connecting the Lexan cover
2. Attach the Lexan cover to the mounting clips and connect to the hinged panel. (See Figure 6.13.1.1.)
33
6.14 Optional Hinged Pluggable Back Panel
Fig.6.14.1 - Silk screen on the Hinged Pluggable Back Panel indicates
which way to turn the black swivel to lock and unlock the gate.
Instructions for installing the Hinged Pluggable Back Panel:
Rear View
1. To begin installing the hinged pluggable back panel,
the NetGuardian G5 should be rack mounted.
Suggestion: Mount the unit in the flush, rack-mount
position. This means the front of the NetGuardian is
flush with the front of the rack post.
2. Facing the back of the NetGuardian, install the
right side of the hinged pluggable back panel.
Used the screws provided to secure the right
mounting arm to the rack.
3. The rack should appear as shown above.
4. Close the back panel gate and lock it in place by
turning the black swivel to the vertical, locked
position as indicated on the silk screen (See
Figure 6.14.1).
34
5. Attached the left side of the hinged panel to the rack
with the screws provided.
6. Unlock the back panel by turning the black
swivel to the horizontal position. (See Figure
6.14.1) Plug the amphenol cables in to the
hinged back panel and secure them with the
Velcro straps. Make sure the NetGuardian's silk
screen matches the hinged panel where the
amphenols are connected.
7. Tighten the 2 screws located to the right of the
amphenol cables. Use the plastic zip ties provided to
secure both cables to the NetGuardian where shown
(bottom image). Note: A zip tie will be used on the
NetGuardian's small metal tab to secure the left
amphenol cable. If your remote is equipped with the
4-pin analog connector, connect it to the
NetGuardian and to the DB9 on the hinged panel.
8. Use the remaining zip ties to keep the amphenol
cords tied together. Trim the excess plastic off
the zip ties with scissors.
9. Close the back panel and lock it by turning the black swivel to the vertical position. (See Figure 6.14.1)
35
6.15 Controls
Fig. 6.14.1. Adjustable jumpers on the NetGuardian circuit board
The following options are adjusted by resetting jumpers on the NetGuardian's circuit board:
· Control relays can be switched from normally open (N/O) to normally closed (N/C)
To simply configure the jumpers, use the hatch panel access on the top of the NetGuardian chassis. This allows
for easy access and configuration of jumpers without having to open the entire case. Remove top screw on hatch
panel and rotate hatch cover until you can easily reach the jumpers. Figure 6.14.1 shows the circuit board and the
location of the adjustable jumpers.
Hatch Panel Access on Top of NetGuardian G5 Chassis
WARNING: Always observe anti-static precautions whenever opening the unit.
36
Fig. 6.14.2. Jumper settings for analog alarm inputs and control relays
For control relay jumpers, the open position corresponds to normally open operation, and the closed position
corresponds to normally closed operation. See Figure 6.14.2.
Note: Default settings may be different if you ordered a special configuration NetGuardian.
7 LCD Display
Fig. 7.1. NetGuardian Front Panel LCD
The front panel LCD displays the current alarm and control status and provides a command menu for controlling
the NetGuardian's basic functions.
Using the LCD command menu
The four buttons surrounding the front panel LCD are used to access the LCD Command Menu. To access the
menu, press the Menu button. To scroll the menu, use the q and p buttons. To select a menu command, press
the Sel (Select) button.
Standard Prompt
When no Command Menu item is selected and no alarms or relays are active, the LCD displays the firmware
version and the standard prompt, Press MENU for front panel options.
Controlling Display Speed
The scroll speed can be temporarily increased by pressing and holding the p button while the message is active.
37
7.1 Alarm and Control Status Messages
If an alarm or control relay is active, the LCD will display the following messages to indicate alarm and control
status:
The LCD panel will display the following messages to indicate alarm and control status:
Discrete Alarms:
If there are any standing discrete alarms, the display will read "Discrete
Alarms:", followed by the user-defined descriptions of the standing alarm points.
Relays:
If there are any latched relays, the display will read "Relays:", followed by the
user-defined descriptions of the latched relays.
Ping Alarms:
If any ping targets have failed to respond within the specified time, the display
will read "Ping Alarms:", followed by the user-defined descriptions of the ping
targets.
Analogs:
If any analog channels have crossed a threshold value, the display will read
"Analogs", followed by the user-defined description of the analog channel, the
channel's last voltage reading, and a letter indicating which threshold the
channel has crossed.
Analog thresholds are represented by the following characters:
Major Over:
Minor Over:
Minor Under:
Major Under:
a capital O
a lower-case o
a lower-case u
a capital U
7.2 LCD Command Menu
Fig. 7.3.1. LCD display
The LCD Command Menu provides commands for controlling some of the NetGuardian's basic functions:
temporarily silencing the alarm speaker, rebooting the unit, and running the TTY configuration utility.
When no Command Menu item is selected and no alarms or relays are active, the LCD displays the firmware
version and the Standard Prompt, Press MENU for front panel options. (See Figure 7.3.1,
above.)
To access the Command Menu, press the Menu button.
38
7.2.1 Sound off
Fig. 7.3.1.1. Sound Off command
Sound off
The Sound off command suppresses sounds from the alarm speaker for a user-defined period of 10, 20, or 30
minutes.
To scroll to the next menu command, press the q button.
To change the Sound off setting, press Sel to select the command. The arrow cursor (>) will move to the right
of the colon (:) in Sound off: to indicate that the command submenu is selected. Press the q and p buttons
to scroll through the Sound off time period options. Select 0 minutes to allow all sounds. When the time period
you want is displayed, press Sel to make your selection.
To exit the Command Menu without changing the Sound off setting, press Menu.
7.2.2 Reboot
Fig. 7.3.2.1. Reboot command
Reboot
The Reboot command reboots the NetGuardian.
To scroll to the next menu command, press the q button.
To reboot the NetGuardian, press Sel. The LCD will briefly display the message Rebooting ..., and the
normal boot sequence will begin.
To exit the Command Menu without rebooting, press Menu.
39
7.2.3 Run Config
Fig. 7.3.3.1. Run Config command
Run Config
The Run Config command forces the TTY configuration interface to run over the craft port at the user defined
baud rate (default is 9600 baud).
To scroll to the next menu command, press the q button.
To run the TTY configuration utility, press Sel.
To exit the Command Menu without running the TTY interface, press Menu.
7.2.4 Contrast
Fig. 7.3.4.1. Contrast command
Contrast
The Contrast command provides controls for adjusting the contrast of the LCD.
To scroll to the next menu command, press the – button.
To adjust the contrast, press Sel to select the command. The arrow cursor (>) will move to the right of the
colon (:) in Contrast: to indicate that the command submenu is selected. Press the q or p button until
you're satisfied with the contrast setting, then press Sel to make your selection.
To exit the Command Menu and revert to the default contrast setting, press Menu.
8 Alarm Speaker
The NetGuardian's alarm speaker emits distinctive tones under two conditions
1.
If there is an Ethernet connection failure, the speaker will emit a high-low warbling tone. Press any
front panel button to silence the speaker.
2. If an alarm occurs, the speaker will emit an intermittent beep. Press any front panel button to silence
the speaker. If you do not silence the speaker, the beep will continue for the user defined duration
(default is a 6 second duration). Silencing the speaker will allow the next alarm, if any, to sound.
40
9 Front Panel LEDs
Fig. 9.1. Front panel LEDs
The NetGuardian's front panel LEDs indicate communication and alarm reporting status. LED status messages
are described below in Table 9.A.
LED
Config
Alarm
Expansion
Net 1
Net 2
LNK Alarm
Craft
Modem
Data Ports1-8
Status
Blink Green
Blink Red
Blink Red
Solid Red
Blink Green
Blink Red
Blink Green
Blink Red
Blink Green
Blink Red
Solid Red
Blink Green
Blink Red
Blink Green
Blink Red
Blink Green
Blink Red
Description
Valid Configuration
Invalid Configuration
New COS alarm*
One or more standing alarms*
Transmit over expansion port
Receive over expansion port
Transmit over Ethernet port 1
Receive over Ethernet port 1
Transmit over Ethernet port 2
Receive over Ethernet port 2
No Ethernet link detected (for configured Net1 or Net2)
Transmit over craft port
Receive over craft port
Transmit over Modem port
Receive over Modem port
Transmit over indicated data port
Receive over indicated data port
*NOTE: Alarm must be configured for notification to be reflected in LED
Table 9.A. Front panel LED Status message descriptions
41
10 Back Panel LEDs
Fig. 10.1. Back panel LEDs for Power (left) and Ethernet connections
The back panel LEDs indicate the status of power and Ethernet connections. LED status messages are described
below in Table 10.A.
LED
Power
10/100 Net
10/100 BaseT
Switch
SFP Fiber 1000Base-X
(Fiber build option
only)
10/100/1000 BaseT
Switch
(Fiber build option
only)
Power A
and/or B
FA
Net1
Net2
Col
1-4
Status
Solid Green
Off
Solid Red
Blink Green
Solid Green
Blink Green
Blink Green
Solid Green
Solid Red
Description
Polarity is correct on power feed A
No Power or Polarity Reverse
Fuse failure
Activity over indicated integrated Ethernet port
Link detected
One or more of the Ethernet Switch ports are active.
Activity over indicated integrated Ethernet Switch port
Link detected
SFP detected, no link.
1-2
Solid Green SFP detected, link is up.
1-4
Flashing
Green
Activity on port detected.
Solid Greenok Link detected.
Table 10.A. Back panel LED Status message descriptions
11 Configuring the NetGuardian
The NetGuardian must be provisioned with log-on passwords, alarm descriptions, port parameters, ping targets,
control descriptions, and other system information. You can provision the NetGuardian using either the
NGEditG5 software or the Web interface. The NetGuardian also supports a limited TTY interface for
configuring some basic options. (For full instructions on configuring the NetGuardian, see the software
configuration guides on the NetGuardian Resource CD.)
You can provision the NetGuardian either locally through the craft port or remotely through a LAN connection.
However, to access the NetGuardian via LAN you must first make a temporary connection to the NetGuardian
and assign it an IP address on your network. For more information, see Section 12, "Connecting to the
NetGuardian."
42
11.1 RADIUS Authentication (Available as of Firmware 5.0I)
RADIUS authentication is now supported by any NetGuardian G5 platform (832A or 864A, with or without
hardware acceleration).
RADIUS (Remote Authentication Dial In User Service) is an industry-standard way to manage logins to many
different types of equipment in one central location. The NetGuardian 832A / 864A G5 connects to your central
RADIUS server. Every time a device receives a login attempt (usually a username & password), it requests an
authentication from the RADIUS server. If the username & password combination is found in the server's
database, an affirmative "access granted" reply is sent back to the unit device, allowing the user to connect.
Also included in the reply are the user's individual access rights, so different users can be granted different
privilege levels. If the user's login attempt is not found, a rejection is returned instead. RADIUS configuration for
the NetGuardian will be achieved via the web browser interface, NGEditG5 software utility, and/or TTY
interface. For details, see the separate user manuals for the NetGuardian G5 web browser and NGEditG5.
12 Connecting to the NetGuardian
12.1 ... via Craft Port
Fig. 12.1.1. NetGuardian Craft Port
The simplest way to connect to the NetGuardian is over a physical cable connection between your PC's COM
port and the NetGuardian's craft port.
Note: You must be connected via craft port to use the TTY interface, but you don't have to be connected to a
NetGuardian unit to use NGEditG5. You only need a connection to the unit to read or write configuration files to
its NVRAM. You can use NGEditG5 on an unconnected PC to create and store NetGuardian configuration files.
Use the DB9M-DB9F download cable provided with your NetGuardian to make a craft port connection.
Select the following COM port options:
• Bits per second: 9600
• Data bits: 8
• Parity: None
• Stop bits: 1
• Flow control: None
When a connection is established (sometimes accompanied by receipt of a hex byte), type DPSCFG, press
Enter to activate the configuration menu. The default password is 'dpstelecom' RADIUS: As of firmware 5.0I,
typing <CR> will prompt for a username and password.
You can perform basic configuration via the craft port — but if you like, you can connect via the craft port just to
configure the NetGuardian's Private LAN IP address, and then do the rest of your configuration via a LAN
connection.
43
12.2 ... via LAN
Fig. 3.2.1. Ethernet port 1
You can also connect to the NetGuardian over a LAN connection. This is a very convenient way to provision
multiple NetGuardian units at multiple locations. Note: You don't have to be connected to a NetGuardian unit to
use NGEditG5. You only need a connection to the unit to read or write configuration files to its NVRAM. You
can use NGEditG5 on an unconnected PC to create and store NetGuardian configuration files.
To connect to the NetGuardian via LAN, all you need is the unit's IP address (Default IP address is
192.168.1.100).
Note: NET1 is defaulted to 192.168.1.100
If you have physical access to the NetGuardian, the easiest thing to do is connect to the unit through the craft
port and then assign it an IP address. Then you can complete the rest of the unit configuration over a remote
LAN connection, if you want. For instructions, see Section 12.1, "Connecting to the NetGuardian via Craft Port."
If you DON'T have physical access to the NetGuardian, you can make a LAN connection to the unit by
temporarily changing your PC's IP address and subnet mask to match the NetGuardian's factory default IP
settings. Follow these steps:
1. Look up your PC's current IP address and subnet mask, and write this information down.
2. Reset your PC's IP address to 192.168.1.200.
3. Reset your PC's subnet mask to 255.255.0.0. You may have to reboot your PC to apply your changes.
4. Once the IP address and subnet mask of your computer coincide with the NetGuardian's, you can access
the NetGuardian via a Telnet session or via Web browser by using the NetGuardian's default IP address
of 192.168.1.100.
5. Provision the NetGuardian with the appropriate information, then change your computer's IP address and
subnet mask back to their original settings.
44
13 TTY Interface
Fig. 13.1. The TTY interface initial configuration screen
The TTY interface is the NetGuardian's built-in provision controls for basic configuration of the NetGuardian.
Configure the NetGuardian's ethernet port settings, monitor the status of base and system alarms, operate control
relays, view live ping targets , view debug or create proxy connections to other ports. For more advanced
configuration tools, please use the Web Browser Interface or the NGEditG5 utility.
To use the TTY interface with the NetGuardian, all you need is any PC with terminal emulation software (i.e.
Hyperterminal) and a connection to the NetGuardian. This connection can be a direct connection to the
NetGuardian's front panel craft port or a remote connection via Telnet or dial-up
Some initial software configuration must be performed before you can use a remote connection to the
NetGuardian. For Telnet, connect to the Net Guardian's IP address at port 2002 to access the configuration
menus after initial LAN/WAN setup. Telnet sessions are established at port 2002, not the standard Telnet
port as an added security measure.
The TTY interface is primarily used for configuring and provisioning the NetGuardian, but you can also use it to
ping IP targets, view system statistics, and data port activity.
NOTE: The TTY default password is "dpstelecom".
Menu Shortcut Keys
The letters before or enclosed in parentheses ( ) are menu shortcut keys. Press the shortcut key to access that
option. Pressing the ESC key will always bring you back to the previous level. Entries are not case sensitive.
13.1 Unit Configuration
13.1.1 Ethernet Port Setup
The NetGuardian must be assigned an IP address before you will be able to connect via LAN/WAN using a
Telnet client or a Web browser. To connect via LAN, the minimum configuration requires setup of the IP address
and subnet mask. Minimum WAN configuration requires that the default gateway be set as well. Follow the
instructions below to configure the NetGuardian's IP address, subnet mask, default gateway, trap address, SNMP
port number, proxy base, and DCHP option.
45
Fig. 13.1.1. Configure the Ethernet port parameters
1. Connect using Hyperterminal @ 9600, 8, N, 1.
2. Type "dpscfg" and hit enter (you won't be able to see this text), the NetGuardian will respond with
"Password."
Note: If you receive no password prompt then check the port you are using on your PC and make sure
you are using a straight thru cable.
46
3. Type the default password, "dpstelecom," then press Enter.
Note: DPS strongly recommends changing the default password.
4. The NetGuardian's main menu will appear.
5. Type C for the C)onfig menu.
6. Type E for E)dit menu.
7. Type E for port settings, 1 for Net 1 and 2 for Net 2.
8. Configure the unit address, subnet mask, and default gateway.
9. ESC to the main menu.
10. When asked if you would like to save changes, type Y (yes).
11. Reboot to save the new configuration to the NetGuardian.
12. Now you can connect to the NetGuardian via LAN and use either NGEdit software over LAN or the
Web Browser to complete the configuration.
RADIUS logons are case-sensitive. If the RADIUS server is unavailable or access is denied, the
master password will work for craft port access only. Also, the "dictionary.dps" files (included on the Resource
Disk) needs to be loaded on the RADIUS server for access-right definition. If RADIUS is enabled on the
NetGuardian, local authentication will not be valid.
13.1.2 SFP Fiber Connection (For Fiber Build Option)
For NetGuardian G5 units with GigE Fiber top board, you also can view and edit switch and SFP fiber
connections in the TTY interface. After logging in, select M)onitor > sW)itch to view details for the
10/100/1000BaseT switch and Fiber interface.
Fig. 13.1.2 SFP fiber connection detail in the TTY interface
47
13.1.3 Edit PPP Port
Choose P)PP to edit your PPP port in TTY Interface. You can choose a baud rate, depending on what device has
been chose for the PPP port.
Fig. 13.1.3 Edit your PPP port
If you are using a modem for the PPP port, then choose mo(D)em for the modem option to define the modem
initialization strings.
Choose B)aud to define the baud rate for that port.
Fig. 13.1.4. Select the baud rate for your PPP port
48
13.1.4 Tune 202 Modem
Tuning the 202 modem on a NetGuardian G5 can only be done from the TTY interface (using either
HyperTerminal through the front craft port or by telnet to the unit over LAN on port 2002).
Fig. 13.1.4. Press 'T' to tune the 202 Modem with the TTY interface
Though no menu options will appear, use the following commands to tune the 202 modem. Each menu option,
when chosen, will output the character "A" on screen:
1) Minor Adjust DB+
2) Minor Adjust DB3) High Frequency
4) Low Frequency
5) Off
6) Major Adjust DB7) Major Adjust DB+
8) Median Frequency (Average of high and low frequency)
After selecting an option (like #1 in this example) for Minor Adjust the DB+ level, the NetGuardian will return a
'+' command to inform you task is completed. Each time you hit a number key (1-8), the NetGuardian will a '+'
on your screen.
49
13.1.5 RADIUS Configuration
The TTY interface can also be used to configure RADIUS settings. After entering the IPA for the RADIUS
server, users will be prompted for both a username and password to logon to the unit. This username and
password combination will be verified against the RADIUS database, and not the local database. The local
password database will only be used for front panel craft port access in the event the RADIUS configuration is
making the unit otherwise inaccessible.
Fig. 13.1.5. The RADIUS configuration menu using the TTY interface.
Retry
Time-out
IPA
Port
Interface
Secret
Global Settings
How many times the RADIUS server will retry a logon
attempt
Enter in the number of seconds before a logon request is
timed out
Servers 1 / 2
Enter the IP address of the RADIUS server
Port 1812 is an industry-standard port for using RADIUS
Use the drop-down menu to choose between NET1 and
NET2
Enter the RADIUS secret in this field
Fig. 13.1.5.2 RADIUS logon screen prompts for a Username and Password.
50
13.1.6 New! - TTY Command Mode
This command line mode offers an alternate way of configuring the NetGuardian G5. This interface is scriptable,
and is recommended for advanced users. Entries are NOT case sensitive.
Fig. 13.1.6 To enter Command Line mode, login to the TTY, then press Ctrl+C.
Tips for using TTY Command Mode
· To enter command mode, login to the TTY interface and press Ctrl + C.
· To view all acceptable operations, type get help, then press Enter.
· Invalid commands will return "Error" as the response.
· A CRLF is sent by the RTU following all responses from the RTU.
· Limited data validation is in place using this method. Use caution when setting variable values.
· In some cases, you need to reboot the NetGuardian for new variable values to take effect.
· Changing REF1, REF2, DISP1, or DISP2 affects the MAJOR, MINOR, OVER, and UNDER alarm
thresholds. Changing any of these settings should be checked and re-established as required.
· In the table below, variables (params) are noted in brackets.
Operation
Help
Initialize NVRAM
Write NVRAM
Read NVRAM
View System Up Time
View Firmware Version
Data Port Description
Command
get help
init nvram {g2}
set nvram
get nvram
get sysuptime
get prodid
{get,set} dataport {1...9} desc
Data Port Baud
{get,set} dataport {1...9} baud
Data Port Format
{get,set} dataport {1...9} wfmt
Data Port RTS Head
(msec)
Data Port RTS Tail
(msec)
Data Port Type
Params
None
None
None
None
None
None
string {0...15} chars
{1200,300,600,1200,2400,4800,
9600,19200,38400,57600,11520
0}
{8n1,8n2,7n1,7e1,7o1,8
o2,8o1}
{get,set} dataport {1...9} rtshead
{0..255}
{get,set} dataport {1...9} rtstail
{0..255}
{get,set} dataport {1...9} type
{off,tcp,ptcp,htcp,rtcp,udp,chan
51
, crft,cap,ecu,sps8}
# of NetGuardian
Expanders
# of GLD or BSU
Timed Tick Period
System Name
System Location
System Contact
System Phone
Reboot
DCP Unit ID
DCP Port Number
DCP Port Type
DCP Protocol
DCP Autonomous Time
Network Time IPA
Username
Password
{get,set} gld
{get,set} timed tick
{get,set} name
{get,set} location
{get,set} contact
{get,set} phone
set reboot
{get,set} dcpaddr
{get,set} dcpport
{get,set} dcptype
{get,set} dcpprot
{get,set} dcpautotm
{get,set} ntpipa
{get,set} username {1...16}
set password {master, 1...16}
Access Rights
{get,set} access {1...16}
Network IPA
Subnet Mask
Gateway IPA
Proxy Base
Analog Description
Analog Display Unit
Analog Major Under
Threshold
Analog Minor Under
Threshold
Analog Minor Over
Threshold
Analog Major Over
Threshold
{get,set} net {1,2} ipa
{get,set} net {1,2} subnet
{get,set} net {1,2} gateway
{get,set} proxybase
{get,set} alg {1...8} desc
{get,set} alg {1...8} unit
Analog Trap
Analog Primary
Notification
Analog Secondary
Location
{get,set} ngddx
{0...3}
{0...16}
{0...60} {min}
string {0..31} chars
string {0..31} chars
string {0..31} chars
string {0..20} chars
None
{0...255}
{1..32767}
{udp,tcp,serial}
{dcpx,dcpf,dcpe}
{0..120} {sec,min}
IP Address
string {0...18} chars
string {0..15} chars
{0000..01ff} where
Bit.0 – 1=admin
Bit.1 – 1=database
Bit.2 – 1=monitor
Bit.3 – 1=rly control
Bit.4 – 1=reachthru
Bit.5 – 1=modem
Bit.6 – 1=telnet
Bit.7 – 1=sd_monitor
Bit.8 – 1=ppp
IP Address
Subnet
Gateway
{1..32767}
string {0..48} chars
string {0..3} chars
{get,set} alg {1...8} thres mju
{-94.0000...94.0000}
{get,set} alg {1...8} thres mnu
{-94.0000...94.0000}
{get,set} alg {1...8} thres mno
{-94.0000...94.0000}
{get,set} alg {1...8} thres mjo
{-94.0000...94.0000}
{get,set} alg {1...8} trap
0=trap disabled
1=trap enabled
{get,set} alg {1...8} pri
{0...8}
{get,set} alg {1...8} sec
{0...8}
52
Analog Polarity
{get,set} alg {1...8} polarity
Analog Group Number {get,set} alg {1...8} group {mju,mnu, mno,mjo}
{get,set} alg {1...8} ref1
Analog Reference 1 VDC
Analog Reference 1
{get,set} alg {1...8} disp1
Display
{get,set} alg {1...8} ref2
Analog Reference 2 VDC
Analog Reference 2
{get,set} alg {1...8} disp2
Display
{get,set} alg {1...8} deadband
Analog Deadband
{get,set} alm {base,exp1,exp2,exp3} {1...64} desc
Alarm Description
{get,set} alm {base,exp1,exp2,exp3} {1...64}
Alarm Polarity
polarity
Alarm Trap
Alarm Primary
Notification
Alarm Secondary
Notification
Alarm Group
Global Trap IP Address
Global Trap Format
{get,set} alm {base,exp1,exp2,exp3} {1...64} trap
0=Normal
1=Reversed
{1...8}
Number
Number
Number
Number
{0.1...9.9}
string {0...48} chars
0=Normal
1=Reversed
0=trap disabled
1=trap enabled
{get,set} alm {base,exp1,exp2,exp3} {1...64} pri
{0...8}
{get,set} alm {base,exp1,exp2,exp3} {1...64} sec
{0...8}
{get,set} alm {base,exp1,exp2,exp3} {1...64}
group
{get,set} trap {1,2} ipa
{get,set} trap {1,2} format
{1...8}
IP Address
{v1, v2c, v2cinf,v3}
Examples
· You want to find out how long this NetGuardian has been running (since last rebooted.) To find system
uptime, you would type get sysuptime, then press Enter.
· You want to see the alarm description for Base Alarm 1. To see the description, type get alm base 1 desc
· You want to set the Global Trap IP Address to 126.10.230.133. To enter this, type set trap 1 ipa =
126.10.230.133
53
13.2 Monitoring
13.2.1 Monitoring the NetGuardian
Connect a PC running VT100 terminal emulation software to the craft port or connect via LAN using a Telnet
client with VT100 emulation to port 2002 to reach the monitor menu selection. This section allows you to do full
system monitoring of the NetGuardian including: all alarms, ping information, relays, analogs, and system status.
Fig. 13.3.1.1. The monitor menu allows status checking on all elements
13.2.1.1 Monitoring Base Alarms
View the status of the device connected to the discrete alarms from the M)onitor menu > A)larms option. Under
Status, the word Alarm will appear if an alarm has been activated and Clear will appear if an alarm condition
is not present. If groups are used the user defined status will be displayed.
54
Fig. 13.3.1.1.1. This example shows page two of the discrete alarms
13.2.1.2 Monitoring Ping Targets
View the status of all your ping targets from the M)onitor menu > P)ing targets option. This screen displays the
ping target ID, description, and IP address. Under Status the word Alarm will appear if an alarm has been
activated and Clear will appear if an alarm condition is not present.
Fig. 13.3.1.2.1. The Ping info submenu allows you to change ping targets
55
13.2.1.3 Monitoring and Operating Relays (Controls)
The NetGuardian comes equipped with 8 relays that can be used to control external devices. Monitor the status
of your relays from the M)onitor menu > R)elays option.
Relays are set to normally open (N/O) as the factory default, but each or all of them can be changed to normally
closed (N/C) by changing their respective jumper (see Section 6.12, "Jumper Options").
Fig. 13.3.1.3.1 The eight relays can be operated from this screen
13.2.1.4 Monitoring Analogs
View the current reading and the alarm status of your analog devices from the M)onitor menu > a(N)logs option.
The value shown is a snapshot of the channels measurement, not a real-time reading. Refresh the readings by
re-selecting the analogs option. Alarm status indicates that a preset threshold has been crossed and is designated
by an x.
The eight analog measuring inputs are set to measure voltage as the factory default. If your sensors output is
current, change the appropriate analog dip switch, to the current measuring position. The scaling worksheet in
the provisioning section converts all readings shown here into native units, such as degrees Celsius or percent
relative humidity.
Fig. 13.3.1.4.1. This display allows you to monitor your eight analog inputs
56
13.2.1.5 Monitoring System Alarms
View the status of the NetGuardian's system alarms from the M)onitor menu > S)ystem option. Under Status,
the word Alarm will appear if an alarm has been activated and Clear will appear if an alarm condition is not
present. See Appendix, "System Alarm Descriptions," for more information. If groups are used the user defined
status will be displayed.
Fig. 13.3.1.5.1. System Alarms can be viewed from the M)onitor menu > S)ystem option
13.2.1.6 Monitoring Data Port Activity
View the status of the NetGuardian's 8 data ports from the M)onitor menu > p(O)rts option. Enter the number of
the port you wish to view and press Enter.
The NetGuardian provides an ASCII description under Transmit and Receive. Choose a) Transmit to view data
transmitted to another device. Choose b) Receive to view data received from another device. See Appendix,
"ASCII Conversion," for specific ASCII symbol conversion.
Fig. 13.3.1.6.1. Data port activity can be viewed from the M)onitor menu > p(O)rts option
13.2.1.7 Monitoring the Accumulation Timer
The Accumulation Timer keeps a running total of the amount of time a point is in an alarm state. An alarm point
that exceeds a user defined threshold will trigger a Accumulation Event system alarm. Refer to Figure
13.3.1.7.1. and Table 13.3.1.7.A to define the accumulation timer.
57
Fig. 13.3.1.7.1. Monitor and reset the Accumulator Timer
Field
Description
Display and Point
Reference
Indicates which alarm point is to be monitored.
Point Description
The user-defined description of the monitored alarm point.
Point Status
The current status of the monitored point.
Event Threshold
Amount of time allowed to accumulate before the system alarm,
“Accumulation Event” is triggered. Note: Maximum is 45 days.
Accumulated Time
The total time the monitored point has been in an ALARM state.
Accumulated Since
Indicates the last time the accumulation timer was reset.
Reset Accumulation
Timer
Selecting this option will reset the timer.
Table 13.3.1.7.A. Field descriptions in the Accumulator Timer Settings
13.2.2 Viewing Live Target Pings
Choose P)ing to ping any of the NetGuardian's user defined IP addresses. Then enter the ID number (1-32) of the
IP address or enter any IP address to ping.
Fig. 13.3.2.1. Continuously ping an IP address that has been defined in the NetGuardian's ping table
13.2.3 Proxy Menu
You can create proxy connections to reach-through to the craft port, modem port or any of the other eight serial
ports from the P)roxy menu. You'll be able to monitor and control additional devices via proxy connection to the
NetGuardian. Data presented and handshaking will be specified by the connected device.
To cancel the proxy connection wait a half second, then quickly type @@@ and press ENTER.
58
Fig. 13.3.3.1. Access devices connected to the eight data ports on the back panel through M)onitor menu >
P)roxy option
13.2.4 Event Logging
Choose E)vent log to view the up to 100 events posted to the NetGuardian; including power up, base and system
alarms, ping alarms, analog alarms, and controls. Posted events for the various alarms include both alarm and
clear status. Refer to Table 13.3.4.A for event log field descriptions.
Note: All information in the event log will be erased upon reboot or a power failure.
Fig. 13.3.4.1. Monitor the last 100 events recorded by the NetGuardian from the M)onitor menu > E)vent log
option
59
Event Log Field
Evt
Date
Time
Grp
State
PRef
Description
Description
Event number (1–100)
Date the event occurred
Time the event occurred
Alarm Group
State of the event (A=alarm, C=clear)
Point reference (See Appendix A for display descriptions).
User defined description of the event as entered in the alarm point
and relay description fields.
Table 13.3.4.A. Event Log field descriptions
13.2.5 Backing Up NetGuardian Configuration Data via FTP
1. From the Start menu on your PC, select RUN.
2. Type "ftp" followed by the IP address of the NetGuardian you are backing up (e.g. ftp 126.10.120.199).
3. After the connection is made press Enter.
4. Enter the password of the NetGuardian (default password is dpstelecom), then press Enter.
5. Type "binary" and press Enter (necessary for NetGuardian file transfer).
6. Type "lcd" and press Enter (this allows you to change the directory of your local machine).
7. Type "get" followed by the name you wish to define for the NetGuardian backup file. Add the extension
".bin" to the file name (e.g. get ngdbkup.bin) and press Enter.
8. After reloading, type "bye" and press Enter to exit.
Note: The backup file name can have a maximum of eight characters before the file extension.
13.2.5.1 Reloading NetGuardian Configuration Data
1. From the Start menu on your PC, select RUN.
2. Type "ftp" followed by the IP address of the NetGuardian you are backing up (e.g. ftp 126.10.120.199).
3. After the connection is made press Enter.
4. Enter the password of the NetGuardian (default password is dpstelecom), then press ENTER.
5. Type "binary" and press Enter (necessary for NetGuardian file transfer).
6. Type "lcd" and press Enter (this allows you to change the directory of your local machine).
7. Type "put" followed by the name you defined for the NetGuardian backup file and press Enter (e.g. put
ngdbkup.bin).
8. Type "literal REBT" to reboot the NetGuardian.
9. After reloading, type "bye" and press Enter to exit.
60
13.2.6 Debug Input and Filter Options
Debug Input Options
ESC
Exit Debug
B
Show BAC status points
T
Show task status
U
Show DUART information
R
Show network routing table
X
Clear debug enable bitmap. Turn all debug filters OFF
?
Display Options
a
(1) Alarm toggle switch. Shows posting of alarm data
A
(2) Analog toggle switch. Shows TTY interface debug
c
(3) Config toggle switch. Shows TTY interface debug
C
(4) Control relay toggle switch. Shows relay operation
d
(5) DCP responder toggle switch. Shows DCP protocol
D
(6) Device toggle switch. Shows telnet and proxy information and NGEditG5 serial
communication.
e
(7) Expansion poller toggle switch. Shows NGDdx polling
E
(8) ECU Interrogator toggle switch. Shows BAC processing
f
(9) FTP Command toggle switch. Shows command string parsing
Debug Filter Options:
F
(10) FTP Data toggle switch. Shows FTP Read / Write
G
(11) GLD poller toggle switch. Shows GLD polling
h
(12) HTML debug switch. Shows Web Browser processing
H
(13) HWACS debug switch. Shows hardware access operation
i
(14) PING toggle switch
k
(15) Socket toggle switch. Shows current dcu resources
l
(16) LED toggle switch. Shows current LED state
L
(17) LCD display toggle switch. Shows LCD control and text
m
(18) Modem toggle switch. Shows modem vectored initialization
M
(19) Undefined
o
(20) Osstart toggle switch. Miscellaneous application debug, including NVRAM read
and write operation, and event posting
O
(21) Undefined
p
(22) SPORT toggle switch. Port init debug and channeled port debug
P
(23) PPP toggle switch. Shows PPP functioning
q
(24) QAccess toggle switch. Reserved for future use
Q
(25) Undefined
r
(26) Report toggle switch. Shows reporting event activity, including SNMP, pagers,
email, etc. Also shows PPP negotiation for NG client PPP mode.
s
(27) SNMP toggle switch. Reserved for future use
S
(28) STAK toggle switch. Shows network processing and IPA of arp requests. Also
shows packets discarded by Filter IPA.
t
(29) TERM toggle switch. Shows UDP/TCP port handling. The camera and network time
(NTP) jobs also use the TERM toggle switch
V
(30) Undefined
w
(31) HTTP toggle switch. Shows handling of web browser packets
W
(32) WEB toggle switch 2. Dump HTML text from web browser
Table. 13.3.A. Debug Input and Filter Options
61
14 Reference Section
14.1 Display Mapping
Port
99
Address Display
1
1
99
99
99
99
99
99
99
99
99
99
99
99
99
1
1
1
1
1
1
1
1
1
1
1
1
1
2
3
4
5
6
7
8
9
10
11
12
12
13
99
99
99
99
99
1
1
1
1
1
13
14
15
16
17
Description
Discrete Alarms 1-32
For NG 864 Alarms 1-64
Set
8001-8032
8001-8064
Clear
9001-9032
9001-9064
Ping Table
Analog Channel 1**
Analog Channel 2**
Analog Channel 3**
Analog Channel 4**
Analog Channel 5**
Analog Channel 6**
Analog Channel 7**
Analog Channel 8**
Relays/System Alarms (See table below)
NetGuardian Expansion 1 Alarms 1-48
NetGuardian 480 (as DX) Alarms 1-64
NetGuardian Expansion 1 Relays 1-8 or
NetGuardian 480 (as DX) Relays 1-4
NetGuardian 480 (as DX) Alarms 65-80
NetGuardian Expansion 2 Alarms 1-48
NetGuardian Expansion 2 Relays 1-8
NetGuardian Expansion 3 Alarms 1-48
NetGuardian Expansion 3 Relays 1-8
8065-8096
8129-8132
8193-8196
8257-8260
8321-8324
8385-8388
8449-8452
8513-8516
8577-8580
8641-8674
6001-6064
6001-6064
6065-6072
9065-9096
9129-9132
9193-9196
9257-9260
9321-9324
9385-9388
9449-9452
9513-9516
9577-9580
9641-9674
7001-7064
7001-7064
7065-7072
6081-6096
6129-6177
6193-6200
6257-6305
6321-6328
7081-7096
7129-7177
7193-7200
7257-7305
7321-7328
Table 14.1.A. Display descriptions and SNMP Trap numbers for the NetGuardian
* The TRAP number ranges shown correspond to the point range of each display. For example, the SNMP Trap
"Set" number for alarm 1 (in Display 1) is 8001, "Set" for alarm 2 is 8002, "Set" for alarm 3 is 8003, etc.
** The TRAP number descriptions for the Analog channels (1-8) are in the following order: minor under, minor
over, major under, and major over. For example, for Analog channel 1, the "Set" number for minor under is
8129, minor over is 8130, major under is 8131, and major over is 8132.
62
SNMP Trap #s
Points
Description
Set
Clear
1
Relays
8641
9641
2
Relays
8642
9642
3
Relays
8643
9643
4
Relays
8644
9644
5
Relays
8645
9645
6
Relays
8646
9646
7
Relays
8647
9647
8
Relays
8648
9648
17
Timed Tick
8657
9657
18
Exp. Module Callout
8658
9658
19
Network Time Server
8659
9659
20
Accumulation Event
8660
9660
21
Duplicate IP Address
8661
9661
33
Unit Reset
8673
9673
36
Lost Provisioning
8676
9676
37
DCP Poller Inactive
8677
9677
38
NET1 not active
8678
9678
39
NET2 not active
8679
9679
40
NET Link Down
8680
9680
41
Modem not responding
8681
9681
42
No Dial Tone
8682
9682
43
SNMP Trap not Sent
8683
9683
44
Pager Que Overflow
8684
9684
45
Notification failed
8685
9685
46
Craft RcvQ full
8686
9686
47
Modem RcvQ full
8687
9687
48
Data 1 RcvQ full
8688
9688
49
Data 2 RcvQ full
8689
9689
50
Data 3 RcvQ full
8690
9690
51
Data 4 RcvQ full
8691
9691
52
Data 5 RcvQ full
8692
9692
53
Data 6 RcvQ full
8693
9693
54
Data 7 RcvQ full
8694
9694
55
Data 8 RcvQ full
8695
9695
56
NetGuardian DX 1 fail
8696
9696
57
NetGuardian DX 2 fail
8697
9697
58
NetGuardian DX 3 fail
8698
9698
59
GLD/BSU 1 fail
8699
9699
60
GLD/BSU 2 fail
8700
9700
61
GLD/BSU 3+ fail
8701
9701
62
Chan. Port Timeout
8702
9702
63
Craft Timeout
8703
9703
64
Event Que Full
8704
9704
Table 14.1.B Display 11 System Alarms point descriptions
63
Note: See Section 14.1.1, "System Alarms Display Map," for detailed descriptions of the NetGuardian's system
alarms.
14.1.1 System Alarms Display Map
Display Points
17
18
19
11
20
21
33
36
Alarm Point
Timed Tick
Exp. Module
Callout
Description
Toggles state at constant rate as
configured by the Timed Tick timer
variable. Useful in testing integrity of
SNMP trap alarm reporting.
Alarm is triggered whenever an alarm
point from an Entry Control Unit (ECU)
is collected. A notification event may
be associated with the alarm to force a
call out or trap.
Network Time Communication with Network Time
Server
Server has failed.
Solution
To turn the feature off, set the Timed
Tick timer to 0.
Disable Building Access Control
(BAC) by setting the BAC Unit ID to 0.
If Building Access is being used, then
investigate the ECU alarm source or
don’t associate notification with the
alarm event.
Try pinging the Network Time Server’s
IP Address as it is configured. If the
ping test is successful, then check the
port setting and verify the port is not
being blocked on your network.
An alarm has been standing for the
time configured under Accum. Timer.
The Accumulation timer enables you To turn off the feature, under
Accumulation
Accum.Timer, set the display and
to monitor how long an alarm has
Event
been standing despite system reboots. point reference to 0.
Only the user may reset the
accumulated time, a reboot will not.
Unplug the LAN cable and contact
your network administrator. Your
Duplicate IP The unit has detected another node
network and the unit will most likely
Address
with the same IP Address.
behave incorrectly. After assigning a
correct IP Address, reboot the unit to
clear the System alarm.
The unit has just come-online. The
Seeing this alarm is normal if the unit
set alarm condition is followed
Power Up
is powering up.
immediately by a clear alarm
condition.
Use Web or latest version of
The internal NVRAM may be
Lost
NGEditG5 to configure unit. Power
damaged. The unit is using default
Provisioning
cycle to see if alarm goes away. May
configuration settings.
require RMA.
Table 14.1.1.A. System Alarms Descriptions
Note: Table 14.1.1.A. continues on following pages.
64
Display Points
37
38
39
40
Alarm Point
DCP Poller
Inactive
NET1 not
active
NET2 not
active
LNK Alarm
41
Modem not
responding
42
No Dial Tone
43
SNMP Trap
not Sent
44
11
Description
The unit has not seen a poll from the
Master for the time specified by the
DCP Timer setting.
The Net1 LAN port is down.
The Net2 LAN port is down.
No network connection detected
An error has been detected during
modem initialization. The modem did
not respond to the initialization string.
During dial-out attempt, the unit did
not detect a dial tone.
SNMP trap address is not defined and
an SNMP trap event occurred.
Over 250 events are currently queued
Pager Queue
in the pager queued and are still trying
Overflow
to report.
45
Notification
failed
A notification event, like a page or
email, was unsuccessful.
46
Craft RcvQ full
The Craft port received more data
than it was able to process.
47
Modem RcvQ The modem port received more data
full
than it was able to process.
48
49
50
51
52
53
54
55
Solution
If DCP responder is not being used,
then set the DCP Unit ID to 0.
Otherwise, try increasing the DCP
timer setting under timers, or check
how long it takes to cycle through the
current polling chain on the Master
system.
Check LAN cable. Ping to and from
the unit. (If not using Net1 or Net2, set
IP, Subnet and Gateway to 255's)
Remove configured modem
initialization string, then power cycle
the unit. If alarm persists, try resetting
the Modem port from the TTY
interface, or contact DPS for possible
RMA.
Check the integrity of the phone line
and cable.
Define the IP Address where you
would like to send SNMP trap events,
or configure the event not to trap.
Check for failed notification events
that may be filling up the pager queue.
There may be a configuration or
communication problem with the
notification events.
Use RPT filter debug to help diagnose
notification problems.
Disconnect whatever device is
connected to the craft serial port. This
alarm should not occur.
Check what is connecting to the
NetGuardian. This alarm should not
occur.
Serial 1 RcvQ
full
Serial 2 RcvQ
full
Serial 3 RcvQ
full
Serial 4 RcvQ
Serial port 1 (or appropriate serial port Check proxy connection. The serial
full
number) receiver filled with 8 K of data port data may not be getting collected
Serial 5 RcvQ (4 K if BAC active).
as expected.
full
Serial 6 RcvQ
full
Serial 7 RcvQ
full
Serial 8 RcvQ
full
Table 14.1.1.A System Alarms Descriptions (continued)
65
Display Points
Alarm Point
Description
56
NetGuardian NGDdx 1 Fail (Expansion shelf 1
DX 1 fail
communication link failure)
57
NetGuardian NGDdx 2 Fail (Expansion shelf 2
DX 2 fail
communication link failure)
58
NetGuardian NGDdx 3 Fail (Expansion shelf 3
DX 3 fail
communication link failure)
59
GLD 1 fail
GLD address 1 is failed.
60
GLD 2 fail
GLD address 2 is failed.
61
GLD 3+ fail
One or more GLD units addressed 3
through 12 may be failed.
11
62
63
64
Chan. Port has not forwarded any
traffic in the time specified by the
Channel Timeout Timer. The channel
Chan. Port
feature forwards data between two
Timeout
ports so the NG may be used to
analyze serial traffic using CHAN filter
debug.
The Craft Timeout Timer has not been
reset in the specified time. This
feature is designed so other machines
Craft Timeout may keep the TTY link active. If the
TTY interface becomes unavailable to
the machine, then the Craft Timeout
alarm is set.
Event Que Full
Solution
Under Ports > Options, verify the
number of configured NGDdx units.
Use EXP filter debug and port LEDs to
help diagnose the problem. Use
DB9M to DB9M with null crossover for
cabling. Verify the DIP addressing on
the back of the NGDdx unit.
Connect just GLD unit 1 and attempt
to poll. Verify GLD is connected to
data port 8 and the hardware is
RS485, not RS232.
Verify the GLD unit addressing, and
test GLD units individually on the GLD
communication bus.
Reduce the number of connected
GLD units to determine which unit
may be causing the link to fail.
Change the data port type to OFF, or
set the Channel Timer to a different
setting.
Change the Craft Timeout Timer to 0
to disable the feature.
Enable DCP timestamp polling on the
The Event Que is filled with more than
master so events are collected, or
500 uncollected events.
reboot the system to clear the alarm.
Table 14.1.1.A System Alarms Descriptions (continued)
66
14.2 SNMP Manager Functions
The SNMP Manager allows the user to view alarm status, set date/time, issue controls, and perform a resync. The
display and tables below outline the MIB object identifiers. Table B.1 begins with dpsRTU; however, the MIB
object identifier tree has several levels above it. The full English name is as follows:
root.iso.org.dod.internet.private.enterprises.dps-Inc.dpsAlarmControl.dpsRTU. Therefore, dpsRTU's full object
identifier is 1.3.6.1.4.1.2682.1.4. Each level beyond dpsRTU adds another object identifying number. For
example, the object identifier of the Display portion of the Control Grid is 1.3.6.1.4.1.2682.1.4.3.3 because the
object identifier of dpsRTU is 1.3.6.1.4.1.2682.1.4 + the Control Grid (.3) + the Display (.3).
Tbl. B1 (O.)_OV_Traps
points
_OV_vTraps
(1.3.6.1.4.1.2682.1.4.0)
Tbl. B2 (.1) Identity points
Tbl. B3 (.2) DisplayGrid points
Ident
(1.3.6.1.4.1.2682.1.4.1)
DisplayEntry
(1.3.6.1.4.1.2682.1.4.2.1)
Manufacturer (.1)
Port (.1)
PointSet (.20)
Model (.2)
Address (.2)
PointClr (.21)
Firmware Version (.3)
Display (.3)
SumPSet (.101)
DateTime (.4)
DispDesc (.4)*
ResyncReq (.5)*
PntMap (.5)*
SumPClr (.102)
ComFailed (.103)
ComRestored (.014)
P0001Set (.10001) through
P0064Set (.10064)
* Must be set to "1" to perform the resync
request which will resend TRAPs for any
standing alarm.
P0001Clr (.20001) through
P0064Clr (.20064)
Tbl. B3 (.3) ControlGrid
points
ControlGrid
(1.3.6.1.4.1.2682.1.4.3)
Tbl. B5 (.5) AlarmEntry points
AlarmEntry
(1.3.6.4.1.2682.1.4.5.1)
Aport (.1)
Port (.1)
AAddress (.2)
Address (.2)
ADisplay (.3)
Display (.3)
APoint (.4)
Point (.4)
APntDesc (.5)*
Action (.5)
AState (.6)
* For specific alarm points, see
Table B6
!
Hot
The NetGuardian G5 OID has changed from 1.3.6.1.4.1.2682.1.2 to 1.3.6.1.4.1.2682.1.4
Tip!Updated MIB files are available on the Resource CD or upon request.
67
Disp 1
Disp 2
Disp 3
Disp 4
Disp 5
Disp 6
Disp 7
Disp 8
Disp 9
Disp 10
Disp 11
Description
Discrete Alarms
Undefined**
Ping Targets
Undefined**
Analog 1
Undefined**
Analog 2
Undefined**
Analog 3
Undefined**
Analog 4
Undefined**
Analog 5
Undefined**
Analog 6
Undefined**
Analog 7
Undefined**
Analog 8
Undefined**
Relays 1-8
Undefined**
Timed Tick
Exp. Module Callout
Network Time
Server
Accumulation Event
Duplicate IP Address
Undefined**
Unit Reset
Undefined**
Lost
DCP poll inactive
NET 1 not active
NET 2 not active
NET link down
Modem not
No dial-tone
SNMP trap not
Pager Que
Notification
Craft RCVQ full
Modem RCVQ
Data 1-8 RCVQ
Port
99
99
99
99
99
99
99
99
99
99
99
99
99
99
99
99
99
99
99
99
99
99
99
99
Address Display
1
1
1
1
1
2
1
2
1
3
1
3
1
4
1
4
1
5
1
5
1
6
1
6
1
7
1
7
1
8
1
8
1
9
1
9
1
10
1
10
1
11
1
11
1
11
1
11
Points
1-32
33-64
1-32
33-64
1-4
5-64
1-4
5-64
1-4
5-64
1-4
5-64
1-4
5-64
1-4
5-64
1-4
5-64
1-4
5-64
1-8
9-16
17
18
99
1
11
19
99
99
99
99
99
99
99
99
99
99
99
99
99
99
99
99
99
99
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
20
21
22-32
33
34-35
36
37
38
39
40
41
42
43
44
45
46
47
48-55
68
NGDdx 1-3 fail
GLD/BSU 1-3 fail
CHAN timeout
CRFT timeout
99
99
99
99
1
1
1
1
11
11
11
11
56-58
59-61
62
63
Table 14.2.A. Alarm Point Descriptions
* "No data" indicates that the alarm point is defined but there is no description entered.
** "Undefined" indicates that the alarm point is not used.
14.3 SNMP Granular Trap Packets
Tables 14.3.A and 14.3.B provide a list of the information contained in the SNMP Trap packets sent by the
NetGuardian.
SNMP Trap managers can use one of two methods to get alarm information:
1. Granular traps (not necessary to define point descriptions for the NetGuardian)
or
2. The SNMP manager reads the description from the Trap.
UDP Header
Description
1238
Source port
162
Destination port
303
Length
0xBAB0
Checksum
Table 14.3.A UDP Headers and descriptions
69
SNMP Header
Description
0
Version
Public
Request
Trap
Request
1.3.6.1.4.1.2682.1.4
Enterprise
126.10.230.181
Agent address
Enterprise Specific
Generic Trap
8001
Specific Trap
617077
Time stamp
1.3.7.1.2.1.1.1.0
Object
NetGuardian 216 v1.0K
Value
1.3.6.1.2.1.1.6.0
Object
1-800-622-3314
Value
1.3.6.1.4.1.2682.1.4.4.1.0
Object
01-02-1995 05:08:27.760
Value
1.3.6.1.4.1.2682.1.4.5.1.1.99.1.1.1
Object
99
Value
1.3.6.1.4.1.2682.1.4.5.1.2.99.1.1.1
Object
1
Value
1.3.6.1.4.1.2682.1.4.5.1.3.99.1.1.1
Object
1
Value
1.3.6.1.4.1.2682.1.4.5.1.4.99.1.1.1
Object
1
Value
1.3.6.1.4.1.2682.1.4.5.1.5.99.1.1.1
Object
Rectifier Failure
Value
1.3.6.1.4.1.2682.1.4.5.1.6.99.1.1.1
Object
Alarm
Value
Table 14.3.B. SNMP Headers and descriptions
70
14.4 Trap SNMP Logic
NET1
Subnet 1 & Gateway
NET2
Not Defined
Trap Dest.
Subnet 3
Subnet 1 & Gateway
Subnet 2, No Gateway
Subnet 3
Subnet 1 & Gateway
Subnet 2 & Gateway
Subnet 3
Subnet 1 & Gateway
Subnet 1 & Gateway
Subnet 1, No Gateway
Subnet 1, No Gateway
Subnet 1, No Gateway
Subnet 2 & Gateway
Subnet 2
Subnet 2 & Gateway
Subnet 1
Subnet 2 & Gateway
Subnet 1
Subnet 2 & Gateway
Subnet 2
Subnet 2 & Gateway
Subnet 3
Table 14.3.C. Trap SNMP Logic
Result
Trap goes out NET1's
Gateway
Trap goes out NET1's
Gateway
Trap goes out NET2's
Gateway
Trap goes out NET2
Trap goes out NET1
Trap goes out NET1
Trap goes out NET2
Trap goes out NET2
14.5 ASCII Conversion
The information contained in Table D.1 is a list of ASCII symbols and their meanings. Refer to the bulleted list
below to interpret the ASCII data transmitted or received through the data ports. Port transmit and receive
activity can be viewed from the Web Browser Interface.
• Printable ASCII characters will appear as ASCII.
• Non-printable ASCII characters will appear as labels surrounded by { } brackets (e.g. {NUL}).
• Non-ASCII characters will appear as hexadecimal surrounded by [ ] brackets (e.g. [IF]).
• A received BREAK will appear as <BRK>.
Abbreviation
Description
Abbreviation
Description
NUL
Null
DLE
Data Link Escape
SOH
Start of Heading
DC
Device Control
STX
Start of Text
NAK
Negative Acknowledge
ETX
End of Text
SYN
Synchronous Idle
EOT
End of Transmission
ETB
End of Transmission Block
ENQ
Enquiry
CAN
Cancel
ACK
Acknowledge
EM
End of Medium
BEL
Bell
SUB
Substitute
BS
Backspace
ESC
Escape
HT
Horizontal Tabulation
FS
File Separator
LF
Line Feed
GS
Group Separator
VT
Vertical Tabulation
RS
Record Separator
FF
Form Feed
US
Unit Separator
CR
Carriage Return
SP
Space (blank)
SO
Shift Out
DEL
Delete
SI
Shift In
BRK
Break Received
Table 14.4.A. ASCII symbols
71
14.6 RADIUS Disctionary File (Available on Resource Disk)
# -*- text -*#
# dictionary.dps
#
#
DPS Telecom, Inc
#
For assistance or support, please contact support@dpstele.com
#
v1.0 Released - 1/23/09 (CBH/DPS)
VENDOR
DPS
2682
#
# Standard attribute for NetGuardian RTU.
# All values are integer with 1 = True, 0 = False.
# If attribure does not exist in Access-Accept packet, default value will be 0.
#
BEGIN-VENDOR
DPS
ATTRIBUTE dps-admin
ATTRIBUTE dps-edit
ATTRIBUTE dps-monitor
ATTRIBUTE dps-SD-monitor
#To allow monitor of data port buffer/activity
ATTRIBUTE dps-reach-through
#To allow proxy to serial ports via TTY interface
ATTRIBUTE dps-telnet
#To allow telnet in and out of NetGuardian
ATTRIBUTE dps-control
#To allow manipulation of dry contact relay outputs
ATTRIBUTE dps-modem
#To allow dial in and out of NetGuardian
ATTRIBUTE dps-ppp
#To allow this user PPP (inbound) access to the NetGuardian
END-VENDORDPS
1
2
3
4
integer
integer
integer
integer
5
integer
6
integer
7
integer
8
integer
9
integer
72
15 Frequently Asked Questions
Here are answers to some common questions from NetGuardian users. The latest FAQs can be found on the
NetGuardian support web page, http://www.dpstelecom.com.
If you have a question about the NetGuardian, please call us at (559) 454-1600 or e-mail us at
support@dpstele.com
15.1 General FAQs
Q. How do I telnet to the NetGuardian?
A. You must use Port 2002 to connect to the NetGuardian. Configure your Telnet client to connect using
TCP/IP (not "Telnet," or any other port options). For connection information, enter the IP address of the
NetGuardian and Port 2002. For example, to connect to the NetGuardian using the standard Windows Telnet
client, click Start, click Run, and type "telnet <NetGuardian IP address> 2002."
Q. How do I connect my NetGuardian to the LAN?
A. To connect your NetGuardian to your LAN, you need to configure the unit IP address, the subnet mask and
the default gateway. A sample configuration could look like this:
Unit Address: 192.168.1.100
subnet mask: 255.255.255.0
Default Gateway: 192.168.1.1
Save your changes by writing to NVRAM and reboot. Any change to the NetGuardian's IP configuration
requires a reboot.
Q. When I connect to the NetGuardian through the craft port on the front panel it either doesn't work
right or it doesn't work at all. What's going on?
A. Make sure your using the right COM port settings. Your COM port settings should read:
Bits per second: 9600 (9600 baud)
Data bits: 8
Parity: None
Stop bits: 1
Flow control: None
Important! Flow control must be set to none. Flow control normally defaults to hardware in most terminal
programs, and this will not work correctly with the NetGuardian.
Q. I can't change the craft port baud rate.
A. If you select a higher baud rate, you must set your terminal emulator program to the new baud rate and then
type DPSCFG and press Enter. If your terminal emulator is set to a slower baud rate than the craft port,
normal keys can appear as a break key — and the craft port interprets a break key as an override that resets
the baud rate to the standard 9600 baud.
Q. How do I use the NetGuardian to access TTY interfaces on remote site equipment?
A. If your remote site device supports RS-232, you can connect it to one of the eight data ports located on the
NetGuardian back panel. To make the data port accessible via LAN, configure the port for TCP/IP operation.
You now have a LAN-based proxy port connection that lets you access your device's TTY interface through
a Telnet session.
Q. I just changed the port settings for one of my data ports, but the changes did not seem to take effect
even after I wrote the NVRAM.
A. In order for data port and craft port changes (including changes to the baud rate and word format) to take
effect, the NetGuardian must be rebooted. Whenever you make changes, remember to write them to the
73
NetGuardian's NVRAM so they will be saved when the unit is rebooted.
Q. The LAN link LED is green on my NetGuardian, but I can't poll it from my T/Mon.
A. Some routers will not forward packets to an IP address until the MAC address of the destination device has
been registered on the router's Address Resolution Protocol (ARP) table. Enter the IP address of your
gateway and your T/Mon system to the ARP table.
Q. What do the terms "port," "address," "display" and "alarm point" mean?
A. These terms refer to numbers that designate the location of a network alarm, from the most general (a port to
which several devices are connected) to the most specific (an individual alarm sensor).
Port: A number designating a serial port through which a monitoring device collects data.
Address: A number designating a device connected to a port.
Display: A number designating a logical group of 64 alarm points.
Alarm Point: A number designating a contact closure that is activated when an alarm condition occurs. For
example, an alarm point might represent a low oil sensor in a generator or an open/close sensor in a door.
These terms originally referred only to physical things: actual ports, devices, and contact closures. For the
sake of consistency, port-address-display-alarm point terminology has been extended to include purely
logical elements: for example, the NetGuardian reports internal alarms on Port 99, Address 1.
Q. What characteristics of an alarm point can be configured through software? For instance, can point 4
be used to sense an active-low signal, or point 5 to sense a level or a edge?
A. The NetGuardian's standard configuration is for all alarm points to be level-sensed. You cannot use
configuration software to convert alarm points to TTL (edge-sensed) operation. TTL alarm points are a
hardware option that must be specified when you order your NetGuardian. Ordering TTL points for your
NetGuardian does not add to the cost of the unit What you can do with the configuration software is change
any alarm point from "Normal" to "Reversed" operation. Switching to Reversed operation has different
effects, depending on the kind of input connected to the alarm point:
· If the alarm input generates an active-high signal, switching to Reversed operation means the
NetGuardian will declare an alarm in the absence of the active-high signal, creating the practical equivalent
of an active-low alarm.
· If the alarm input generates an active-low signal, switching to Reversed operation means the
NetGuardian will declare an alarm in the absence of the active-low signal, creating the practical equivalent of
an active-high alarm.
· If the alarm input is normally open, switching to Reversed operation converts it to a normally closed
alarm point.
· If the alarm input is normally closed, switching to Reversed operation converts it to a normally open
alarm point.
Q. Every time my NetGuardian starts up, I have to reenter the date and time. How can I get the
NetGuardian to automatically maintain the date and time setting?
A. You have three options for keeping the correct time on your NetGuardian:
Real Time Clock Option: You can order your NetGuardian with the Real Time Clock hardware option.
Once it's set, the Real Time Clock will keep the correct date and time, regardless of reboots.
Network Time Protocol Synchronization: If your NetGuardian has Firmware Version 2.9F or later, you
can configure the unit to automatically synchronize to a Network Time Protocol (NTP) server.
· To get the latest NetGuardian firmware, sign in to MyDPS at www.dpstelecom.com/mydps.
· For instructions on configuring your NetGuardian to use NTP synchronization, see your NGEditG5 or
NetGuardian Web Browser Interface user manual.
T/Mon RTU Time Sync Signal: You can configure your T/Mon NOC to send an RTU Time Sync signal at
a regular interval, which you can set to any time period between 10 and 10,080 minutes. The Time Sync will
automatically synchronize the NetGuardian's clock to the T/Mon's clock. And if you set your T/Mon to NTP
synchronization, you'll make sure you have consistent, accurate time stamps throughout your monitoring
network.
74
Q. How do I back up my NetGuardian configuration?
A. There are two ways to back up NetGuardian configuration files:
Use NGEditG5
NGEditG5 can read the configuration of a NetGuardian unit connected to your PC via LAN, modem or COM
port. You can then use NGEditG5 to save a NetGuardian configuration file on your PC's hard disk or on a
floppy disk. With NGEditG5 you can also make changes to the configuration file and write the changed
configuration to the NetGuardian's NVRAM.
Use FTP
You can use File Transfer Protocol (FTP) to read and write configuration files to the NetGuardian's
NVRAM, but you can't use FTP to edit configuration files.
75
15.2 SNMP FAQs
Q. How do I configure the NetGuardian to send traps to an SNMP manager? Is there a separate MIB for
the NetGuardian? How many SNMP managers can the agent send traps to? And how do I set the IP
address of the SNMP manager and the community string to be used when sending traps?
A. The NetGuardian begins sending traps as soon as the SNMP managers are defined. The NetGuardian MIB is
included on the NetGuardian Resource CD. The MIB should be compiled on your SNMP manager. (Note:
MIB versions may change in the future.) The unit supports 2 SNMP managers, which are configured by
entering its IP address in the Trap Address field of Ethernet Port Setup. You can also configure up to eight
secondary SNMP managers, which is configured by selecting the secondary SNMP managers as pager
recipients. Community strings are configured globally for all SNMP managers. To configure the community
strings, choose System from the Edit menu, and enter appropriate values in the Get, Set, and Trap fields.
Q. Does the NetGuardian support MIB-2 and/or any other standard MIBs?
A. The NetGuardian supports the bulk of MIB-2.
Q. Does the NetGuardian SNMP agent support both NetGuardian and T/MonXM variables?
A. The NetGuardian SNMP agent manages an embedded MIB that supports only the NetGuardian's RTU
variables. The T/MonXM variables are included in the distributed MIB only to provide SNMP managers
with a single MIB for all DPS Telecom products.
Q. How many traps are triggered when a single point is set or cleared? The MIB defines traps like
"major alarm set/cleared," "RTU point set," and a lot of granular traps, which could imply that more
than one trap is sent when a change of state occurs on one point.
A. Generally, a single change of state generates a single trap, but there are two exception to this rule. Exception
1: the first alarm in an "all clear" condition generates an additional "summary point set" trap. Exception 2:
the final clear alarm that triggers an "all clear" condition generates an additional "summary point clear" trap.
Q. What does "point map" mean?
A. A point map is a single MIB leaf that presents the current status of a 64-alarm-point display in an
ASCII-readable form, where a "." represents a clear and an "x" represents an alarm.
Q. The NetGuardian manual talks about eight control relay outputs. How do I control these from my
SNMP manager?
A. The control relays are operated by issuing the appropriate set commands, which are contained in the DPS
control grid. For more information about the set commands, see Appendix, "Display Mapping," in any of the
NetGuardian software configuration guides.
Q. How can I associate descriptive information with a point for the RTU granular traps?
A. The NetGuardian alarm point descriptions are individually defined using the Web Browser, TTY, or
NGEditG5 configuration interfaces.
Q. My SNMP traps aren't getting through. What should I try?
A. Try these three steps:
1. Make sure that the Trap Address (IP address of the SNMP manager) is defined. (If you changed the
Trap Address, make sure you saved the change to NVRAM and rebooted.)
2. Make sure all alarm points are configured to send SNMP traps.
3. Make sure the NetGuardian and the SNMP manager are both on the network. Use the NetGuardian's
ping command to ping the SNMP manager.
76
15.3 Pager FAQs
Q. Why won't my alpha pager work?
A. To configure the NetGuardian to send alarm notifications to an alpha pager, enter the data phone number for
your pager in the Phone Number field. This phone number should connect to your pager service's modem.
Then enter the PIN for your pager in the PIN/Rcpt/Port field. You don't need to enter anything in any of the
other fields. If you still don't receive pages, try setting the Dial Modem Init string to ATS37=9. This will
limit the NetGuardian's connection speed. Be sure to use the rpt debug feature, if needed.
Q. Numeric pages don't come in or are cut off in the middle of the message. What's wrong?
A. You need to set a delay between the time the NetGuardian dials your pager number and the time the
NetGuardian begins sending the page message. You can set the delay in the Pager Number field, where you
enter your pager number. First enter the pager number, then enter some commas directly after the number.
Each comma represents a two-second delay. So, for example, if you wanted an eight-second delay, you
would enter "555-1212,,,," in the Pager Number field.
Q. What do I need to do to set up e-mail notifications?
A. You need to assign the NetGuardian an e-mail address and list the addresses of e-mail recipients. Let's
explain some terminology. An e-mail address consists of two parts, the user name (everything before the "@"
sign) and the domain (everything after the "@" sign). To assign the NetGuardian an e-mail address, choose
System from the Edit menu. Enter the NetGuardian's user name in the Name field (it can't include any
spaces) and the domain in the Location field. For example, if the system configuration reads:
Name: netguardian
Location: proactive.com
Then e-mail notifications from the NetGuardian will be sent from the address "netguardian@proactive.com."
The next step is to list the e-mail recipients. Choose Pagers from the Edit menu. For each e-mail recipient,
enter his or her e-mail domain in the Phone/Domain field and his or her user name in the PIN/Rcpt/Port field.
You must also enter the IP address of an SMTP server in the IPA field and configure the alarm point to use
the pager you setup as email.
77
16 Technical Support
DPS Telecom products are backed by our courteous, friendly Technical Support representatives, who will give
you the best in fast and accurate customer service. To help us help you better, please take the following steps
before calling Technical Support:
1. Check the DPS Telecom website.
You will find answers to many common questions on the DPS Telecom website, at
http://www.dpstelecom.com/support/. Look here first for a fast solution to your problem.
2. Prepare relevant information.
Having important information about your DPS Telecom product in hand when you call will greatly reduce the
time it takes to answer your questions. If you do not have all of the information when you call, our Technical
Support representatives can assist you in gathering it. Please write the information down for easy access.
Please have your user manual and hardware serial number ready.
3. Have access to troubled equipment.
Please be at or near your equipment when you call DPS Telecom Technical Support. This will help us solve
your problem more efficiently.
4. Call during Customer Support hours.
Customer support hours are Monday through Friday, from 7 A.M. to 6 P.M., Pacific time. The DPS Telecom
Technical Support phone number is (559) 454-1600.
Emergency Assistance: Emergency assistance is available 24 hours a day, 7 days a week. For emergency
assistance after hours, allow the phone to ring until it is answered with a paging message. You will be asked to
enter your phone number. An on-call technical support representative will return your call as soon as possible.
“Dependable, Powerful Solutions
that allow users to monitor larger,
more complicated networks with a
smaller, less trained staff”
“Your Partners in Network Alarm Management”
www.dpstelecom.com
4955 E Yale • Fresno, CA 93727
559-454-1600 • 800-622-3314 • 559-454-1688 fax
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising