ltm-mkprotodb(1)ltm-mkprotodb(1)NAMEltm-mkprotodb - Creates a compiled protocols database file
SYNTAXltm-mkprotodb-i {input file} -o {output file}
DESCRIPTION
The ltm-client program requires a compiled version of the protocols.cfg
file. This is done using ltm-mkprotodb.
eg.
cd /usr/local/etc &&
ltm-mkprotodb-i protocols.cfg -o protocols.db
OPTIONS-i input file (eg. /usr/local/etc/protocols.cfg)
-o output file (eg. /usr/local/etc/protocols.db)
FILES
The format of the /usr/local/etc/protocols.cfg file is as follows:
Field 1: State 0=off 1=on
Field 2: Modify 0=non editable 1=editable
Field 3: Protocol id (eg. icmp=1, tcp=6, udp=17, ospf=89)
Field 4: Protocol name (eg. icmp, tcp, udp, ospf)
Field 5: SubProtocol id (eg. echorequest=0, telnet=23,
Field 6: SubProtocol name (eg. echorequest, telnet, domain)
Field 7: IP address (0.0.0.0 match all IP addresses)
Field 8: Netmask (currently unused)
The Statseeker network performance monitoring product contains a web
tool for modifying this configuration file, but you'll just have to
edit it with a text editor. Field number 2 is only meaningful to the
web tool. Field 8 is unused, but must exist.
A 'Protocol name' and 'SubProtocol name' can consist of alpha numeric,
underscore and dash characters. A dot '.' can not be used.
LTM IP protocols are defined by:
1. IP Protocol type (eg. ICMP, TCP, UDP, OSPF, EGP)
2. Sub Type (eg. TCP/UDP port numbers, ICMP code, etc)
3. IP Address of a specific host.
The IP address field allows you to redefine the protocol type for a
specific host. For example, port 80 can be redefined from "http" to
"my_intranet". All other port 80 traffic will be displayed as "http". A
value of 0.0.0.0 for the IP address is a wild card, meaning "any IP
address".
AUTHORS
Statseeker. 300 Adelaide Street, Brisbane, Queensland, Australia.
SUPPORT
Refer to ltm(1).
SEE ALSOltm(1), ltm-client, http://www.statseeker.com
Statseeker 3.0.0.608281003 ltm-mkprotodb(1)
