Backtrack:  
 
showing posts tagged with 'cli'
 
edited by on August 24th 2018, at 15:14
In case of disaster, it is usually a very good idea to periodically back up the configuration of your network switches. This article lists syntax for backing up configuration to a TFTP server for different vendors.

In the syntax examples below, the IP for the TFTP is 1.2.3.4, and we're writing to the file switch.cfg.

Note that this article is definitely not complete. If you have additions to this article, please post them in the comments.

The syntax for Dell and Cisco switches is mostly the same. For N-series and PowerConnect, a summary is displayed which needs to be confirmed, which is not the case for Cisco and Dell S-series.

For Cisco Small Business (SF- and SG-series), the CLI ne  ...
edited by on August 21st 2018, at 14:44

Cisco's SF/SG 300/500 series managed switches have CLI access via Telnet and SSH but this is turned off by default, leaving only the web interface to manage the switch. You can enable Telnet and/or SSH via the web interface, enabling management via CLI.

  1. Log on to the web interface, then navigate to Security → TCP/UDP Services.
  2. Check the Enable boxes for Telnet Service and/or SSH Service. You can check both if you wish to enable both protocols. Click Apply, which will immediately start the selected services:
  3. Don't forget to save the configuration change to flash. Otherwise, the change will be lost after a reboot:
edited by on August 21st 2015, at 10:23

If your vCenter server has a self-signed certificate, you will get a warning about this when connecting to it from vSphere PowerCLI. You can disable this warning through PowerCLI with the Set-PowerCLIConfiguration cmdlet.

  1. Start an elevated vSphere PowerCLI (right-click, Run as Administrator).
  2. Enter the following cmdlet:
    Set-PowerCLIConfiguration -InvalidCertificateAction Ignore
    Press Enter again to confirm the change.

After making the change, new connections to the vCenter server will no longer produce a warning about the certificate.

edited by on April 29th 2015, at 16:39
Below is a list of most common CLI commands for VMWare ESXi. Type these in directly in an ESXi or SSH shell.

vim-cmd vmsvc/getallvmsList all VMs running on the host. Also provides vmid, required for commands below.vim-cmd vmsvc/power.off vmidPower off specified VM.vim-cmd vmsvc/power.on vmidPower off specified VM.vim-cmd vmsvc/power.reboot vmidReboot specified VM.vim-cmd solo/registervm /vmfs/volume/datastore/subdir/vm-file.vmxRegister the VM stored at location on the ESX host inventory.vim-cmd vmsvc/unregister vmidUnregister VM from the host. Does not remove the VM's files from the datastore.vim-cmd vmsvc/destroy vmidDelete the specified VM. The VMDK and VMX files will be deleted from stor  ...
 
showing posts tagged with 'cli'
 
 
« March 2024»
SunMonTueWedThuFriSat
     12
3456789
10111213141516
17181920212223
24252627282930
31      
 
Links
 
Quote
« You only find out who is swimming naked when the tide goes out. »
Warren Buffett