Table of Contents
Advertisement
C900TTL-E | Installation Guide | 5.0
4.6
Enabling Dynamic Host
Configuration Protocol (DHCP)
To use DHCP, you must have v1.10 or later
firmware in the C900TTL-E.
The D6600 can communicate with a C900TTL-E that
has an IP address dynamically assigned by using a
DHCP server on the network. When using DHCP, the
D6600 is set to use the Network Naming Convention
(NNC) to identify the accounts instead of Static IP
addresses. When NNC is used, the devices in the field
have either a static IP address or a dynamic IP address.
The D6600 uses the NNC number instead of the IP
address to identify the account.
When devices in the field have IP addresses assigned
by a DHCP server, the following items are required:
•
DIP Switch 9 on the C900TTL-E must be ON.
•
NNC must be enabled in the D6600. Refer to the
D6600/D6100 Receiver/Gateway Program Entry Guide
(P/N: 4998122702).
•
The Account Database in the Conettix D6200
Programming/Administration Software is in NNC
mode. Refer to the D6200 Programming Software
Operation and Installation Guide (P/N: 4998154991).
•
The eight-digit NNC number printed on the label
of the C900TTL-E's EEPROM must be entered
into the Account Database of the D6600 using the
D6200 Programming Software. Refer to the
D6200 Programming Software Operation and
Installation Guide (P/N: 4998154991).
•
Network connections are configured to
communicate through a DHCP server.
•
The IP address of the C900TTL-E is set to 0.0.0.0.
Bosch Security Systems, Inc. | 5/07 | 4998122718-02
C900TTL-E Implementation of Anti-Substitution Protection
5.0 C900TTL-E Implementation
of Anti-Substitution
Protection
The C900TTL-E must have software
version 1.08 or later.
The C900TTL-E only reads the dip
switches on power up.
1. Power down the C900TTL-E.
2. Set DIP Switch 9 to the ON position (factory
default). Refer to Section 3.1 Setting the DIP Switches
on page 11.
3. Power-up the C900TTL-E.
4. Following a reboot of the C900TTL-E, the field
unit exchanges numeric keys with the D6600, and
they become synchronized. When synchronized,
all subsequent communications sessions are
validated numerically regarding the authenticity of
the sender and the receiver. Each session generates
an entirely new set of "keys", making the replay of
authentic sessions invalid.
.
23
Advertisement
Table of Contents
