Cisco Cisco WT2750 Multipoint Broadband Wireless System Guia De Informação
Note: You can configure the HE to play the part of the DHCP/TFTP server. If the HE is not
configured to be the DHCP/TFTP server, make sure that there is a radio helper−address
command configured under the HE radio interface. This ensures that DHCP broadcasts are
forwarded to the correct server. If you use an external DHCP/TFTP server, the server must
also contain a route or default gateway that instructs how to send packets back to the SU
network.
configured to be the DHCP/TFTP server, make sure that there is a radio helper−address
command configured under the HE radio interface. This ensures that DHCP broadcasts are
forwarded to the correct server. If you use an external DHCP/TFTP server, the server must
also contain a route or default gateway that instructs how to send packets back to the SU
network.
These error messages point to the absence of optional parameters in the DHCP response:
DHCP_ERROR_ACQUIRING_SEC_SVR_ADDR
DHCP_ERROR_ACQUIRING_LOG_ADDRESS
Configure the secondary server and log server address on the DHCP server to eliminate these
errors.
errors.
Q. What if the SU gets to the establish_tod_state but never gets to
TOD_REPLY_RECEIVED?
TOD_REPLY_RECEIVED?
A. A common reason for failure at this state is that a TOD server is not present either
externally or on the HE. You can configure the HE to act as the TOD server. Issue the radio
time−server command from the global configuration mode. Once again, to use an external
TOD server, a route must be present for the TOD server to send the response back to the SU.
externally or on the HE. You can configure the HE to act as the TOD server. Issue the radio
time−server command from the global configuration mode. Once again, to use an external
TOD server, a route must be present for the TOD server to send the response back to the SU.
Q. What if the SU fails on the configuration_file_state?
A. The configuration_file_state is the main configuration and administration interface to the
SU DOCSIS subsystem. The name of this file and the TFTP server address in which this can
be downloaded were originally provided in the DHCP state. This configuration file contains:
SU DOCSIS subsystem. The name of this file and the TFTP server address in which this can
be downloaded were originally provided in the DHCP state. This configuration file contains:
Downstream channel and upstream channel identification
♦
Characteristics
♦
Class of Service settings
♦
Baseline Privacy settings
♦
General operational settings
♦
Common reasons for failure at this state are missing files, wrong file permissions, an
unreachable TFTP server, files in the wrong format, files with missing required options,
incorrectly configured required options, or incorrect options (unknown or invalid
Type−Length−Values (TLVs)).
unreachable TFTP server, files in the wrong format, files with missing required options,
incorrectly configured required options, or incorrect options (unknown or invalid
Type−Length−Values (TLVs)).
Q. What if the SU fails at the registration_state?
A. Problems with the registration state almost always point to a configuration file error. Make
sure the SU and the HE both support the settings in the configuration file. Make sure the HE
allows the creation of class of service profiles or use a profile that the HE creates. Check the
authentication strings in the HE radio interface configuration and in the DOCSIS
configuration file.
sure the SU and the HE both support the settings in the configuration file. Make sure the HE
allows the creation of class of service profiles or use a profile that the HE creates. Check the
authentication strings in the HE radio interface configuration and in the DOCSIS
configuration file.
Q. What if the SU fails at the establish_privacy_state?
A. This situation probably means that the HE or the SU tries to establish Baseline Privacy
(BPI) and the other one is not. Verify whether the DOCSIS config file has BPI turned on. On
the HE, verify whether the QoS profile also shows BPI turned on. Use the show radio qos
profile command. Also, make sure both the HE and SU use K images.
(BPI) and the other one is not. Verify whether the DOCSIS config file has BPI turned on. On
the HE, verify whether the QoS profile also shows BPI turned on. Use the show radio qos
profile command. Also, make sure both the HE and SU use K images.