This is the frequency at which an HMTS transmits its FSK signal on the HFC network, and only applies to RF ports. Other port types should return noSuchName upon SNMP get or set commands. When changing from one downstream frequency to another, an HMTS should first transmit several CHNLDESC packets with the new frequency as payload and modulated on the old frequency. This will tell transponders to switch from the old to new frequency. Next the HMTS must change its modulator from the old to the new frequency. In combination with the hmtsFwdXpndrFrequency variable, two applications are possible: - Tuning all transponders to a new frequency by first changing hmtsFwdXpndrFrequency and next setting hmtsFwdHmtsFrequency to the same frequency. - Recovering transponders that missed a frequency transition, e.g. because they were disconnected at the time the CHNLDESC PDU's were transmitted. Recovery can be performed by setting hmtsFwdHmtsFrequency for a short time to the frequency at which the non-communicating transponders are listening. Frequency transitions can be implemented in an HMTS e.g. in one of the following ways: 1. Manual frequency transition: hmtsFwdHmtsFrequency and hmtsFwdXpndrFrequency can be set independently by an operator. Hence, both frequency transitions and recovering transponders is supported. 2. Automatic frequency transition: when hmtsFwdXpndrFrequency is set, and after the transition CHNLDESC PDU's have been sent, the HMTS also sets hmtsFwdHmtsFrequency to the new frequency. SNMP sets on hmtsFwdHmtsFrequency will result in a bad value error. RESOLUTION: <=100 Hz This object is non-volatile.