
Configuring TMS and Security for erpcd Networks
303509-A Rev 00 5-3
The syntax of the command that creates a TMS entry is:
tms_dbm add
<domain> <dnis>
te=
<ip_addr_of_the_gateway>
\
maxu=
<maximum_count_of_users>
[hwtype=
<fr_or_ppp>
\
[hwaddr=
<hardware_link_address_from_home_agent_to_CPE>
\
hwalen=
<length_of_hardware_link_address>
]]\
[srvloc=servers_location] [tutype=tunnel_type]\
pauth=
<ip_addr_of_primary_authentication_server>
\
sauth=
<ip_addr_of_secondary_authentication_server>
\
[pacct=
<ip_addr_of_primary_accounting_server>
\
[sacct=
<ip_addr_of_secondary_accounting_server>
]]\
[paddr=
<ip_addr_of_primary_dynamic_address_server>
\
[saddr=
<ip_addr_of_secondary_dynamic_address_server>
]]\
authp=
<radius_or_acp>
[acctp=accounting protocol] \
[addrp=dynamic address allocation protocol]\
[spi=
<security_protocol_index>
] [passw=
<password>
] [tatype=kmd5-128\
tamode=pref-suff takey=
<authentication_key_value(hex, 256_bits)>
]
The dialed number parameter
dnis
is available only for the Model 8000/5399
products. By default,
dnis
is set to 0 for all Remote Access Concentrators.
The
hwalen
parameter is set to 0 for PPP and optional for frame relay. If you do
specify the
hwalen
parameter, use the actual length in bytes of the hexadecimal
value of the DLCI number (the hardware address). For example, if the DLCI is
101 (that is, 0x65), the hardware address length is 1 byte. For a hardware address
of 400 (0x190), the hardware address length is 2 bytes.
If you omit the
hwalen
parameter, tms_dbm derives the length from the value of
the
hwaddr
parameter. If, for the
hwaddr
parameter, you specify a decimal value
that is smaller than 4 bytes (that is, from 0 through 2
31
), TMS converts that value
to hexadecimal. To specify a hexadecimal value, prefix the number with the
characters 0x; for example, to express 64 (decimal), specify 0x40. For PPP, set the
hwaddr
parameter to 0.
Note:
In this syntax description, square brackets [ ] indicate optional
parameters.
Note:
The
ha
(home agent) parameter used in previous versions is still
recognized, but the
te
(tunnel end point) parameter required in the current
version has taken over its function.
Komentarze do niniejszej Instrukcji