Zhone 2000 ユーザーガイド
C o n f i g u r a t i o n
4-45
C
H A P T E R
C
HAPTER
4
C
ONFIGURATION
Introduction
This chapter describes WAN, Router, Bridge, Voice Path, Firewall, DHCP
Server, and NAT Configuration.
Server, and NAT Configuration.
NOTICE:
When the IAD prompts you for input, it displays the default or current
value in parentheses. To conveniently accept this value, just press Enter.
value in parentheses. To conveniently accept this value, just press Enter.
NOTICE:
You must reset the IAD for configuration changes to take effect.
Managing Configuration Files
Each IAD is shipped with a factory default configuration set in the file
default.st. Once you make any changes to your IAD, a new file (config.st) is
default.st. Once you make any changes to your IAD, a new file (config.st) is
created to store the new configuration.
After you have configured the IAD for correct operation in a customer’s
premises, the current system settings in the config.st file may be saved as the
custom default configuration file (refer to Set System Default on page 3-38).
You may also copy this file to a PC or TFTP server for downloading to other
identically configured IADs. Once you have copied over the custom default
file (custdef.st), you cannot retrieve it. You should consider copying the
custdef.st file to a safe location before replacing it.
After you have configured the IAD for correct operation in a customer’s
premises, the current system settings in the config.st file may be saved as the
custom default configuration file (refer to Set System Default on page 3-38).
You may also copy this file to a PC or TFTP server for downloading to other
identically configured IADs. Once you have copied over the custom default
file (custdef.st), you cannot retrieve it. You should consider copying the
custdef.st file to a safe location before replacing it.
WAN Configuration
Basic WAN Setup Tasks
The IAD WAN can be configured for ATM, Frame Relay, or HDLC
protocols, depending on the interface. (Refer to the flowchart in Figure 4.1.)
protocols, depending on the interface. (Refer to the flowchart in Figure 4.1.)