Lucent Technologies 6000 - Manual (Page 195)

Configuring Individual WAN Connections
Configuring bidirectional CHAP support
MAX 6000/3000 Network Configuration Guide 4-63
Stack Options
UDP Checksum=No
When you press Enter, the Ethernet
> Mod Config > Stack Options subprofile appears. For
example:
Ethernet
Mod Config
Stack Options
Stacking Enabled=Yes
Stack Name=maxstack-1
UDP Port=6000
Multicast Addr=
2 Set the Stacking Enabled parameter to Yes.
3 Set the Stack Name parameter to a unique name for the stack.
A stack name has 16 characters or less. This is the name members of a stack use to identify
other members of the same stack. The stack name must be unique among all MAX units
that communicate with each other, even if they are not on the same LAN.
If a MAX unit receives calls from two units on different LANs, and the two units are
members of different stacks with the same stack name, the unit receiving the calls assumes
the two MAX units with the same stack name are in the same bundle.
Note: Multiple stacks can exist on the same physical Ethernet LAN if the stacks have
different names.
4 Specify the UDP port parameter.
This is a reserved UDP port for intrastack communications. The UDP port must be
identical for all members of a stack, but is not required to be unique among all stacks.
5 Exit the profile and, at the exit prompt, select the exit and accept option.
Disabling a MAX stack
To disable a stack, specify Stacking Enabled=No for each of the MAX units in the stack.
Adding and removing a MAX
You can add a MAX unit to an existing stack at any time without rebooting the unit or affecting
stack operation. Because a stack is a collection of peers, none keeps a list of the stack
membership. The units in a stack communicate when they need a service from the stack.
Removing a unit from a stack requires care, because any calls using a channel between the unit
to be removed and another unit in the stack could be dropped. There is no need to reboot a unit
removed from a stack.
Configuring bidirectional CHAP support
You can set up bidirectional CHAP authentication between the calling PPP device and the
called PPP device. The bidirectional CHAP feature increases compliance with the RFC 1994
standard for PPP CHAP authentication. Note that the feature is not implemented for
PAP-based authentication (PAP, PAP-TOKEN, or PAP-TOKEN-CHAP).