Cisco Cisco FastHub 412M 10 100 Repeater

Refer to the online FastHub 400 10/100 Series Command Reference for information about accessing 
the CLI. See the 

 section of this document for information about 

locating this document through Cisco.com.

Use the CLI delete nvram command to reset either or both management hubs to their default values. 

Refer to the online reference FastHub 400 10/100 Series Command Reference for more information 
about this command.

The management hub that is powered on first becomes the new M1 hub in the stack because the hub 
with the longest up time is by default the M1 hub. 

If you delete the NVRAM configuration settings for one management hub and not the other, be sure to 
power on the management hub with the deleted configuration first. This prevents the redundant 
management hub from copying its saved configuration to the hub whose configuration you just deleted.

This section describes resolved caveats in the FastHub 400.

This configuration caveat was resolved in v.1.00.08:

CSCdw69907

The Cisco FastHub 400 is susceptible to Simple Network Management Protocol (SNMP) 
vulnerabilities. These vulnerabilities can be easily and repeatedly demonstrated with the use of the 
University of Oulu Secure Programming Group (OUSPG) “PROTOS” Test Suite for SNMPv1. The 
test suite is generally used to analyze a protocol and produce messages that probe various design 
limits within an implementation of a protocol. Test packets containing overly-long or malformed 
object identifiers and other combinations of exceptional values in various fields can be 
programmatically generated and then transmitted to a network device under test. The PROTOS test 
suite for SNMPv1, as distributed, contains approximately 53,000 individual test cases.

Further details are described in the advisory at this link:

http://www.cisco.com/warp/public/707/cisco-malformed-snmp-msgs-non-ios-pub.shtml

This problem was resolved in release v.1.00.06:

CSCdv15665

You no longer lose connectivity across the uplink module when moving to a new port on the same 
FastHub 400 or to a port on a different FastHub 400.

This problem was resolved in release v.1.00.04: