BladeSystem - General
cancel
Showing results for 
Search instead for 
Did you mean: 

Resetting C7000 to default settings

 
chuckk281
Trusted Contributor

Resetting C7000 to default settings

David had a question:

 

********************

 

Could anybody advise how to reset a C7000 Blade chassis to defaults?

The Blade chassis was previously used by another group and nobody has any contact details for them. Don’t ask why.

 

We can login into the chassis but we are unable to delete the Virtual Connect domain as it was previously managed by VCEM. We will be using the chassis standalone with no VCEM management.

 

We’ve tried clearing the VC mode from the Onboard Administrator but it still says enabled even though it gives a message ‘completed successfully’. After this we’ve tried resetting to factory defaults but  it gives a message about an error communicating with the Onboard Administrator module (we’ll get this reseated)

 

So the question is ‘how can we reset this chassis (Onboard Administrator\Virtualconnect settings) to default settings as we’d expect to have with a new chassis?’

 

******************

 

Nick replied:

 

********************

 

Are you trying to reset the whole chassis and blades, or just the VC modules? As long as they are lower than VC v3.30 you can wipe the VC modules by physically moving them to a bay other than 1 or 2 and powering them on.

 

*******************

 

Any other suggestions or comments for David?

1 REPLY
chuckk281
Trusted Contributor

Re: Resetting C7000 to default settings

Had a number of people reply to this question:

 

From Jim:

If that does not work try:

 

The recommended password recovery procedure is as follows:

1. Remove the Virtual Connect Ethernet module from interconnect bay 1.

2. Remove the access panel from the Virtual Connect Ethernet module.

3. Set switch 1 to the ON position. Ensure that all other switches remain in the OFF position.(these are very small)

4. Install the access panel.

5. Insert the Virtual Connect Ethernet module into bay 1 and allow the module to power up and reach a fully booted and operational state (approximately 1 minute).

6. Remove the Virtual Connect Ethernet module from interconnect bay 2.
This causes interconnect bay 1 to become the module running the active VC Manager. Because switch 1 is set, the Administrator password remains at the factory default for interconnect bay 1 (not overwritten by the change of state because of the failover).

7. Wait to ensure that the VC Manager has had time to become active on interconnect bay 1. Log into the VC Manager to confirm it is up and functional on interconnect bay 1.

8. Insert the Virtual Connect Ethernet module into interconnect bay 2 and allow the module to power on and reach a fully booted and operational state (approximately 1 minute).

9. Remove the Virtual Connect Ethernet module from interconnect bay 1.

10. Remove the access panel from the Virtual Connect Ethernet module.

11. Set switch 1 to the OFF position. Ensure that all other switches remain in the OFF position.

12. Install the access panel.

13. Insert the Virtual Connect Ethernet module into interconnect bay 1 and allow the module to power up and reach a fully booted and operation state (approximately 1 minute).

14. Log into the VC Manager using the factory default user name and password to log in to the module (regardless of whether it is running on the module

 

************

 

From Mike:

I have seen a few cases just working in the lab where the “clear vcmode” has to be entered more than once and you need to wait a minute before then issuing a reset factory after issuing clear vcmode.  If you only tried once I would try it a few more times. If this woks I would be interested in hearing about it. I figured it was just a fluke when I saw this, but perhaps there is corner case where there is a timing issue.

 

**************

 

From Rajesh:

Virtual connect modules that part of a VC domain can be returned to the factory default settings when placed into a new enclosure by applying power, and then pressing and holding the reset button on the front panel for at least 10 seconds.

 

************

 

And from Lee:

You can use the following command in the VCM cli to clear the VCEM Manager setting.  Clearing the vcmode in the OA does not tell the VCM that it is no longer being managed by VCEM.

 

show external-manager               (outputs username)

set external-manager Username=<username> Enabled=false   (removes lock)

remove external-manager username=<username>        (removes domain)

 

**************

 

Any others?