Network configuration, Dns configuration – Guralp Systems CMG-DCM User Manual
Page 53

Operator's guide
3 open (never) Wed Jul 7 16:04:48 2004
4 open (never) Wed Jul 7 16:04:48 2004
5 closed Wed Jul 7 16:04:48 2004 (never)
6 open (never) Wed Jul 7 16:04:48 2004
7 closed Wed Jul 7 16:04:48 2004 (never)
8 closed Wed Jul 7 16:04:48 2004 (never)
9 closed (never) (never)
10 closed (never) (never)
11 closed (never) (never)
12 closed (never) (never)
13 closed (never) (never)
14 closed (never) (never)
15 closed (never) (never)
The columns in the table give, in turn, the current state of each switch
and when it was last observed to be in each state. The above example
shows a typical reading for a set of 9 tamper switches that have not
triggered: the normally-closed switches show the current time under
“Last Closed”, and the normally-open switches under “Last Open”. All
other fields show (never), indicating that no switches have been
observed in the “wrong” state since the DCM was last booted.
Network configuration
This section displays basic information about the DCM's network
setup. It is identical to the output from the Linux ifconfig program.
A typical reading might look like this:
eth0 Link encap:Ethernet HWaddr 00:D0:1F:34:EB:08
inet addr:192.168.0.46 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3619 errors:0 dropped:0 overruns:0 frame:0
TX packets:2453 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:290005 (283.2 kb) TX bytes:417231 (407.4 kb)
Interrupt:42 Base address:0x8300
For further information, see the Linux manual page for ifconfig.
DNS configuration
This section reports the current status of the DCM's domain name
resolution service. This is done by presenting the contents of the
standard Linux /etc/resolv.conf file.
# eth0 begin
domain guralp.local
nameserver 192.168.0.1
nameserver 192.168.0.2
# eth0 end
For further information, see the Linux manual page for resolv.conf.
December 2006
53