CLI

Installing and Configuring MPIO on Windows Server 2008

Posted on Updated on

Multipath I/O (MPIO) is essential for providing redundancy and load balancing for storage connections. Whether you are using Fibre Channel or iSCSI, here is the definitive guide to getting MPIO running on Windows Server 2008.

🛠️ Option 1: Install MPIO via Server Manager (GUI)

  1. Open Server Manager: Click Start > Administrative Tools > Server Manager.
  2. Add Features: In the Features summary area, click Add Features.
  3. Select MPIO: On the Select Features page, check the box for Multipath I/O and click Next.
  4. Confirm: Click Install.
  5. Finish: Once the progress bar completes, click Close.

💻 Option 2: Install MPIO via Command Line (CLI)

If you are working on a Server Core installation or just prefer the speed of the CLI, use ServerManagerCmd.exe.

  1. Open Command Prompt as Administrator.
  2. Install the feature:DOSServerManagerCmd.exe -install Multipath-IO
  3. Verify installation:DOSServerManagerCmd.exe -query Ensure “Multipath I/O” appears in the list of installed packages.

🔗 Claiming iSCSI Devices for MPIO

After installation, Windows doesn’t automatically “claim” iSCSI devices for multipathing. You must enable this manually.

  1. Open the MPIO Control Panel (found in Administrative Tools).
  2. Go to the Discover Multi-Paths tab.
  3. Check the box Add support for iSCSI devices and click Add.
  4. Reboot: You will be prompted to restart the computer. Click Yes.
  5. Verify: After the reboot, check the MPIO Devices tab. You should see hardware ID MSFT2005iSCSIBusType_0x9, indicating the Microsoft DSM has successfully claimed the iSCSI bus.

🗑️ How to Remove MPIO

If you need to decommission MPIO, follow these steps:

  • Via GUI: In Server Manager, click Remove Features, uncheck Multipath I/O, and follow the prompts.
  • Via CLI:DOSServerManagerCmd.exe -remove Multipath-IO

IC347745[1]

#WindowsServer #MPIO #StorageAdmin #SysAdmin #ITPro #DataCenter #iSCSI #Networking #LazyAdmin #LegacyIT

This entry was posted in Windows and tagged , , , , , , , , .

How to Change the Default Snapshot Location in VMware ESXi 5

Posted on Updated on

By default, VMware ESXi stores virtual machine snapshots in the same directory as the parent VM. If your primary datastore is running low on space, taking a new snapshot can fail or, worse, cause the VM to hang.

snapshot

Fortunately, you can redirect these snapshots (and swap files) to a different datastore with more “breathing room.”

Phase 1: vSphere Client Configuration

Before modifying files, we need to tell the VM not to store redo logs with the parent.

  1. Power OFF the Virtual Machine (This is mandatory for the changes to take effect).
  2. Right-click the VM and select Edit Settings.
  3. Go to the Options tab > General > Configuration Parameters.
  4. Click Add Row and enter:
    • Name: snapshot.redoNotWithParent
    • Value: true
  5. Click OK to save and exit.

Phase 2: CLI Configuration (.vmx Modification)

Now we define exactly where those snapshots should go.

  1. Log into the ESXi host via SSH or the local console.
  2. Navigate to your VM’s home directory:Bashcd /vmfs/volumes/[DatastoreName]/[VMName]
  3. Open the .vmx configuration file using the vi editor:Bashvi VMName.vmx
  4. Add the following line to the file, specifying your secondary datastore path:PlaintextworkingDir = "/vmfs/volumes/Secondary-Datastore/snapshots" (Press i to insert text, then Esc followed by :wq to save and exit.)

Phase 3: Reloading the VM

Changes to the .vmx file aren’t picked up until the VM is reloaded in the inventory.

  1. Find your VM’s ID:Bashvim-cmd vmsvc/getallvms | grep [VMName]
  2. Note the ID number (e.g., 13) and run the reload command:Bashvim-cmd vmsvc/reload 13

💡 Pro Tip: Keeping Swap Files in the Original Directory

By default, the workingDir parameter also moves the VM’s .vswp (Swap) file. If you only want to move the snapshots and keep the swap file with the parent VM for performance reasons, add this extra parameter in the Configuration Parameters (Phase 1):

Name: sched.swap.dir

Value: "/vmfs/volumes/Original-Datastore/VM-Directory"

#VMware #ESXi #StorageAdmin #SysAdmin #Virtualization #vSphere #TechTutorial #LazyAdmin #DataCenter #CloudComputing

This entry was posted in VMware and tagged , , , , , , , , .

🏗️ CLI Command Hierarchy & Navigation

Posted on Updated on

The CLI is organized like a file system. You move “down” into specific modes to manage objects and “up” to return to the global level.

  • EXEC Mode (#): The top-level mode. From here, you can access all other sub-modes.
  • Navigation Commands:
    • scope <object>: Moves into a sub-mode for an existing object (e.g., scope chassis 1).
    • enter <object>: Similar to scope, but used to enter or create an object’s mode.
    • exit: Moves up one level in the hierarchy.
    • top: Jumps immediately back to the EXEC mode prompt.

🛠️ Common Management Commands

TargetCommandPurpose
Chassisshow chassis [inventory/status/psu]View physical chassis health and components.
Serversshow server [inventory/cpu/memory/status]Audit blade or rack-mount hardware specs.
Fabricshow fabric-interconnect [a/b] [inventory]Check the state of your Fabric Interconnects.
Faultsshow fault [detail/severity]List active system alarms and errors.
Logsshow sel [chassis-id/blade-id]View the System Event Log for specific hardware.

💾 The Transactional Model (Commit Buffer)

Unlike many traditional CLIs, UCS Manager uses a transactional model. When you make a configuration change (like set or enable), the change is stored in a temporary buffer and is not live until you explicitly save it.

  1. Modify: set addr 192.168.1.50
  2. Verify: show configuration pending (Optional)
  3. Apply: commit-buffer
  4. Discard: discard-buffer (If you made a mistake)

#CiscoUCS #CommandLine #SysAdmin #DataCenter #Networking #Cisco #ITPro #LazyAdmin #TechTutorials #UCSM

This entry was posted in Cisco UCS and tagged , , , , , , , .