New Fling: PowerCLI Preview for NSX-T

New Fling: PowerCLI Preview for NSX-T

This is the first new fling of 2018. Last three months there were updates on already existing flings but now we have a new fling, PowerCLI Preview for NSX-T

Summary

This Fling provides a community preview of the upcoming PowerCLI commands for NSX-T management. It comes in the form of a single PowerCLI module and integrates with existing PowerCLI modules.

All commands have been automatically generated. They are in an early stage of development, contain known issues, and will change in the future.

List of the most important known issues:

  • Retrieving an object based on its entire parent object does not work. To remedy this issue, specify the ID of the parent instead of the entire parent object. For instance, when calling Get-FirewallRule, use the -SectionId parameter to specify the ID of the parent section, instead of passing the entire parent firewall section to the -FirewallSection parameter.

 

 

Requirements

Requires PowerCLI 10.0.0 (specifically, the VMware.VimAutomation.Nsxt module) and Microsoft Windows.

Instructions

Unzip the contents of the archive directly into one of PowerShell’s module directories. Open a new PowerShell window. Execute ‘Import-Module -Name VMware.VimAutomation.Nsxt.Commands’. At this point, you can call Connect-NsxtServer to connect to a NSX server.

Notes:
1) The PowerShell module directories are listed in the PSModulePath environment variable ($env:PSModulePath).
2) Do not create a subdirectory for the archive’s contents. Unzip directly into the module directory. If the module directory you selected is e.g. ‘C:\Program Files\WindowsPowerShell\Modules’, the resulting path would look like:

C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Nsxt.Commands\EULA.rtf
...and not:
C:\Program Files\WindowsPowerShell\Modules\SomeExtraSubdirectoryYouCreatedForTheArchive\VMware.VimAutomation.Nsxt.Commands\EULA.rtf

For more info you can go here

%d bloggers like this: