Cisco Cisco IOS Software Release 12.2

The removal of NetFlow Feature Acceleration does not affect any other aspects of Netflow 
operation, for example Access-list processing. The features are separate and distinct. 

Cisco Express Forwarding (CEF) supersedes the deprecated NetFlow Feature Acceleration.

Additionally, the following MIB objects and OIDs have been deprecated and removed from the 
netflow mib (CISCO-NETFLOW-MIB): 

cnfFeatureAcceleration 1.3.6.1.4.1.9.9.99999.1.3
cnfFeatureAccelerationEnable 1.3.6.1.4.1.9.9.99999.1.3.1 
cnfFeatureAvailableSlot 1.3.6.1.4.1.9.9.99999.1.3.2
cnfFeatureActiveSlot 1.3.6.1.4.1.9.9.99999.1.3.3 
cnfFeatureTable 1.3.6.1.4.1.9.9.99999.1.3.4 
cnfFeatureEntry 1.3.6.1.4.1.9.9.99999.1.3.4.1 
cnfFeatureType 1.3.6.1.4.1.9.9.99999.1.3.4.1.1 
cnfFeatureSlot 1.3.6.1.4.1.9.9.99999.1.3.4.1.2 
cnfFeatureActive 1.3.6.1.4.1.9.9.99999.1.3.4.1.3 
cnfFeatureAttaches 1.3.6.1.4.1.9.9.99999.1.3.4.1.4 
cnfFeatureDetaches 1.3.6.1.4.1.9.9.99999.1.3.4.1.5 
cnfFeatureConfigChanges 1.3.6.1.4.1.9.9.99999.1.3.4.1.6 

This section describes possibly unexpected behavior by Cisco IOS Release 12.2(28). All the caveats 
listed in this section are resolved in Cisco IOS Release 12.2(28). This section describes severity 1 and 2 
caveats and select severity 3 caveats.

The following information is provided for each caveat:

Symptoms: A description of what is observed when the caveat occurs. 

Conditions: The conditions under which the caveat has been known to occur. 

Workaround: Solutions, if available, to counteract the caveat.

CSCee20816

Symptoms: A system used for reverse connections, such as a console server or other “milking 
machine” applications, may unexpectedly restart due to a bus error.

Conditions: The conditions under which this occurs are not well understood, but it is likely that 
frequent, short-lived connections are more likely to cause the problem than environments where 
connections are either long-lived or rarely opened and closed.

Workaround: There is no workaround. 

CSCee84611

Symptoms: An NTP broadcast client may fail to synchronize with an NTP broadcast server if the 
server cannot be reached from the client.

Conditions: This symptom is observed in Cisco IOS interim Release 12.2(12.11)T or a later release, 
including Release 12.3. However, the symptom may also occur in other releases.

Workaround: Ensure that the server can be reached from the client.