BladeSystem Virtual Connect
cancel
Showing results for 
Search instead for 
Did you mean: 

Save off/print Configs? Specifically Virtual Connect Manager Ethernet Networks details

lokiju
Occasional Visitor

Save off/print Configs? Specifically Virtual Connect Manager Ethernet Networks details

Trying to see if there's a easy way to save off or print off the configs for specifically the Ethernet Networks section but any section for that matter.

 

Would be handy to have for reference and when adding new blades.

3 REPLIES
HEM_2
Honored Contributor

Re: Save off/print Configs? Specifically Virtual Connect Manager Ethernet Networks details

I think your best bet would be to connect to the VCM CLI (via SSH) and issue a "show all *"

 

or you may find some more specific show commands from the show all (its a macro that runs several show commands) that fit what you need. 

The Brit
Honored Contributor

Re: Save off/print Configs? Specifically Virtual Connect Manager Ethernet Networks details

The VC configurations can be "saved off"using the "Backup/Restore" option in the Navigation window on left.

 

The file however, is a non-printable file, suitable only for restoring back to a VC Module.

 

HEM's idea of using the "show all" command at the CLI prompt is probably your best option if you want to be able to read it.    Actually, you should probably use the "Show All *" command, to get all of the detail.

 

You can probably write a script to log in and get this information on a periodic basis.

 

Dave.

 

 

Casper42
Trusted Contributor

Re: Save off/print Configs? Specifically Virtual Connect Manager Ethernet Networks details

VC 3.30 was released today and adds the feature you are looking for.

You can SSH to VC and type: show config
That will dump out a script that would allow you to build another VC Domain with very similar properties.

The Metadata and any Virtual WWN/MAC/Serial settings are not retained during this type of dump (you wouldnt want to push the config to another chassis and immediately have WWN conflicts), so you still need to use the Backup process for traditional DR style backups.

But for cloning configs, you can use the GUI on chassis #1, shwo config to grab the script, tweak a few settings as needed (including Virtual WWN/MAC/Serial Pools) and then quickly build chassis 2-64 with almost identical configs.