Format for hosts file when specifying multiple TL1 devices on a single host
The hosts file specifies how the
probe connects
to the network elements on the target host. The probe is designed
to have a dedicated thread for each <hostname>
<port>
entry
in the hosts file, where each thread creates a socket connection towards
the host.
The TL1 Probe supports two different formats for the host files.
File format 1
File format 1 uses the following syntax:
<host> <port>:
"<tid1>","ci1" "co1",,,:
"<tid2>","ci2" "co2",,,:
"<tid3>","ci3" "co3",,,;
host1 10033:
"NYCM1759","login1 user1\r password pass1\r" "tl1stop\r",,,:
"NYCM5500","login user2\r password pass2\r" "tl1stop\r",,"\r" "HB" 10 15,:
"NYCM1630",,,,;
In
this example there are three network elements (TIDs) under a single
socket connection. After opening a telnet session the probe sends wakeup
, login
and resync
commands
which are defined in each TID entry.
File format 2
File format 2 is the recommended format for the hosts file. It contains separate connection entries for each TID element being managed. This maximizes the performance of the probe by making full use of its multi-threaded capabilities.
File format 2 uses the following syntax:
<host1> <port1>:
"<tid1>","ci1" "co1",,,;
<host1> <port1>:
"<tid2>","ci2" "co2",,,;
<host1> <port1>:
"<tid3>","ci3" "co3",,,;
host1 10033:
"NYCM1759","login user1\r password pass1\r" "tl1stop\r",,,;
host1 10033:
"NYCM5500","login user2\r password pass2\r" "tl1stop\r",,"\r" "HB" 10 15,;
host1 10033:
"NYCM1630",,,,;
In
this example there are three separate socket elements for each of
the network elements. After opening the telnet session, the probe
only sends wakeup
, login
and resync
commands
for a single TID. This maximizes probe performance. The problem, however,
is that some element management systems have a limit on the maximum
number of connections it can manage at one time. If this is the case
with your EMS, use hosts File format 1.