< Back
New-vRNIDataSource
Post
NAME New-vRNIDataSource
SYNOPSIS
Create new datasources within vRealize Network Insight to retrieve data from.
SYNTAX
New-vRNIDataSource [-Username <String>] [-Password <String>] [-IP <String>] [-FDQN <String>] -CollectorVMId
<String> -Nickname <String> [-Enabled <Boolean>] [-Notes <String>] [-Connection <PSObject>] [<CommonParameters>]
New-vRNIDataSource [-Username <String>] [-Password <String>] [-IP <String>] [-FDQN <String>] -CollectorVMId
<String> -Nickname <String> [-Enabled <Boolean>] [-Notes <String>] [-NSXEnableCentralCLI <Boolean>]
[-NSXEnableIPFIX <Boolean>] [-NSXEnableLatency <Boolean>] [-NSXvCenterID <String>] [-Connection <PSObject>]
[<CommonParameters>]
New-vRNIDataSource [-Username <String>] [-Password <String>] [-IP <String>] [-FDQN <String>] -CollectorVMId
<String> -Nickname <String> [-Enabled <Boolean>] [-Notes <String>] -CiscoSwitchType <String> [-Connection
<PSObject>] [<CommonParameters>]
New-vRNIDataSource [-Username <String>] [-Password <String>] [-IP <String>] [-FDQN <String>] -CollectorVMId
<String> -Nickname <String> [-Enabled <Boolean>] [-Notes <String>] -DellSwitchType <String> [-Connection
<PSObject>] [<CommonParameters>]
New-vRNIDataSource [-Username <String>] [-Password <String>] [-IP <String>] [-FDQN <String>] -CollectorVMId
<String> -Nickname <String> [-Enabled <Boolean>] [-Notes <String>] -TenantID <String> -ApplicationID <String>
-SecretKey <String> -SubscriptionID <String> [-FlowsEnabled <Boolean>] [-Connection <PSObject>]
[<CommonParameters>]
New-vRNIDataSource [-Username <String>] [-Password <String>] [-IP <String>] [-FDQN <String>] -CollectorVMId
<String> -Nickname <String> [-Enabled <Boolean>] [-Notes <String>] [-KubeConfig <String>] -NSXTManagerID <String>
[-Connection <PSObject>] [<CommonParameters>]
DESCRIPTION
Datasources within vRealize Network Insight provide the data shown in
the UI. The vRNI Collectors periodically polls the datasources as the
source of truth. Typically you have a vCenter, NSX Manager and physical
switches as the datasource.
This cmdlet adds new datasources to vRNI, so it can retrieve data from it and
correlate and display this data in the interfce.
PARAMETERS
-Username <String>
Username to use to login to the datasource
Required? false
Position? named
Default value
Accept pipeline input? false
Accept wildcard characters? false
-Password <String>
Password to use to login to the datasource
Required? false
Position? named
Default value
Accept pipeline input? false
Accept wildcard characters? false
-IP <String>
The IP address of the datasource
Required? false
Position? named
Default value
Accept pipeline input? false
Accept wildcard characters? false
-FDQN <String>
The FDQN address of the datasource
Required? false
Position? named
Default value
Accept pipeline input? false
Accept wildcard characters? false
-CollectorVMId <String>
Collector (Proxy) Node ID
Required? true
Position? named
Default value
Accept pipeline input? false
Accept wildcard characters? false
-Nickname <String>
Nickname for the datasource
Required? true
Position? named
Default value
Accept pipeline input? false
Accept wildcard characters? false
-Enabled <Boolean>
Whether we want to enable the datasource
Required? false
Position? named
Default value True
Accept pipeline input? false
Accept wildcard characters? false
-Notes <String>
Optional notes for the datasource
Required? false
Position? named
Default value
Accept pipeline input? false
Accept wildcard characters? false
-NSXEnableCentralCLI <Boolean>
These params are only required when adding a NSX Manager as datasource
Enable the central CLI collection
Required? false
Position? named
Default value True
Accept pipeline input? false
Accept wildcard characters? false
-NSXEnableIPFIX <Boolean>
Enable NSX IPFIX as a source
Required? false
Position? named
Default value True
Accept pipeline input? false
Accept wildcard characters? false
-NSXEnableLatency <Boolean>
Enable Virtual Latency (VTEP, VNIC, & PNIC) streaming from NSX to vRNI
Required? false
Position? named
Default value False
Accept pipeline input? false
Accept wildcard characters? false
-NSXvCenterID <String>
vCenter ID that this NSX Manager will be linked too
Required? false
Position? named
Default value
Accept pipeline input? false
Accept wildcard characters? false
-CiscoSwitchType <String>
This params is only required when adding a cisco switch
Set the switch type
Required? true
Position? named
Default value
Accept pipeline input? false
Accept wildcard characters? false
-DellSwitchType <String>
This params is only required when adding a dell switch
Set the switch type
Required? true
Position? named
Default value
Accept pipeline input? false
Accept wildcard characters? false
-TenantID <String>
These params are only required when adding an Azure subscription as datasource
Azure Tenant ID
Required? true
Position? named
Default value
Accept pipeline input? false
Accept wildcard characters? false
-ApplicationID <String>
Azure Application ID
Required? true
Position? named
Default value
Accept pipeline input? false
Accept wildcard characters? false
-SecretKey <String>
Azure Secret Key
Required? true
Position? named
Default value
Accept pipeline input? false
Accept wildcard characters? false
-SubscriptionID <String>
Azure Subscription ID
Required? true
Position? named
Default value
Accept pipeline input? false
Accept wildcard characters? false
-FlowsEnabled <Boolean>
Retrieve Flows?
Required? false
Position? named
Default value True
Accept pipeline input? false
Accept wildcard characters? false
-KubeConfig <String>
KubeConfig as a string
Required? false
Position? named
Default value
Accept pipeline input? false
Accept wildcard characters? false
-NSXTManagerID <String>
NSX-T Manager entity ID
Required? true
Position? named
Default value
Accept pipeline input? false
Accept wildcard characters? false
-Connection <PSObject>
vRNI Connection object
Required? false
Position? named
Default value $defaultvRNIConnection
Accept pipeline input? false
Accept wildcard characters? false
<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (https:/go.microsoft.com/fwlink/?LinkID=113216).
INPUTS
OUTPUTS
-------------------------- EXAMPLE 1 --------------------------
PS C:\\>$collectorId = (Get-vRNINodes | Where {$_.node_type -eq "PROXY_VM"} | Select -ExpandProperty id)
PS C:\\> New-vRNIDataSource -DataSourceType vcenter -FDQN vc.nsx.local -Username administrator@vsphere.local
-Password secret -CollectorVMId $collectorId -Nickname vc.nsx.local
First, get the node ID of the collector VM (assuming there's only one), then add a vCenter located at vc.nsx.local
to vRNI.
-------------------------- EXAMPLE 2 --------------------------
PS C:\\>$collectorId = (Get-vRNINodes | Where {$_.node_type -eq "PROXY_VM"} | Select -ExpandProperty id)
PS C:\\> $vcId = (Get-vRNIDataSource | Where {$_.nickname -eq "vc.nsx.local"} | Select -ExpandProperty entity_id)
PS C:\\> New-vRNIDataSource -DataSourceType nsxv -FDQN mgr.nsx.local -Username admin -Password secret -Nickname
mgr.nsx.local -CollectorVMId $collectorId -Enabled $True -NSXEnableCentralCLI $True -NSXEnableIPFIX $True
-NSXvCenterID $vcId
Adds a new NSX Manager as a data source, auto select the collector ID (if you only have one), enable the NSX
Central CLI for collecting data, also enable NSX IPFIX for network datastream insight from the point of view of
NSX.
-------------------------- EXAMPLE 3 --------------------------
PS C:\\>$collectorId = (Get-vRNINodes | Where {$_.ip_address -eq "10.0.0.11"} | Select -ExpandProperty id)
PS C:\\> New-vRNIDataSource -DataSourceType azure -CollectorVMId $collectorId -Nickname Azure-1 -TenantID
xxx-xxx-xxx-xxx-xxx -ApplicationID xxx-xxx-xxx-xxx-xxx -SecretKey secret -SubscriptionID xxx-xxx-xxx-xxx-xxx
Adds a new Azure subscription; first gets a specific collector appliance based on IP, and continues to add the
Azure subscription based on the application registration information.
More info on requirements can be found here: https://docs.vmware.com/en/VMware-vReal ... .0/com.vmw
are.vrni.using.doc/GUID-12272E1A-055F-47E9-9EA6-8693FE86AA02.html
-------------------------- EXAMPLE 4 --------------------------
PS C:\\>$nsxtId = (Get-vRNIDataSource -DatasourceType nsxt | Where {$_.nickname -eq "my-nsxt-manager"} |
Select -ExpandProperty id)
PS C:\\> $collectorId = (Get-vRNINodes | Where {$_.ip_address -eq "10.0.0.11"} | Select -ExpandProperty id)
PS C:\\> $kubeconfig = (Get-Content ~/.kube/config | Out-String)
PS C:\\> New-vRNIDataSource -DataSourceType kubernetes -Nickname k8s-cluster-1 -CollectorVMId $collectorId
-NSXTManagerID $nsxtId -KubeConfig $kubeconfig
Add a Kubernetes cluster as a data source. First gets the entity ID of the NSX-T Manager supporting the container
network, then vRNI Collector ID, then puts the kubeconfig file into a string, and finally adds the Kubernetes
cluster to vRNI.
RELATED LINKS
SYNOPSIS
Create new datasources within vRealize Network Insight to retrieve data from.
SYNTAX
New-vRNIDataSource [-Username <String>] [-Password <String>] [-IP <String>] [-FDQN <String>] -CollectorVMId
<String> -Nickname <String> [-Enabled <Boolean>] [-Notes <String>] [-Connection <PSObject>] [<CommonParameters>]
New-vRNIDataSource [-Username <String>] [-Password <String>] [-IP <String>] [-FDQN <String>] -CollectorVMId
<String> -Nickname <String> [-Enabled <Boolean>] [-Notes <String>] [-NSXEnableCentralCLI <Boolean>]
[-NSXEnableIPFIX <Boolean>] [-NSXEnableLatency <Boolean>] [-NSXvCenterID <String>] [-Connection <PSObject>]
[<CommonParameters>]
New-vRNIDataSource [-Username <String>] [-Password <String>] [-IP <String>] [-FDQN <String>] -CollectorVMId
<String> -Nickname <String> [-Enabled <Boolean>] [-Notes <String>] -CiscoSwitchType <String> [-Connection
<PSObject>] [<CommonParameters>]
New-vRNIDataSource [-Username <String>] [-Password <String>] [-IP <String>] [-FDQN <String>] -CollectorVMId
<String> -Nickname <String> [-Enabled <Boolean>] [-Notes <String>] -DellSwitchType <String> [-Connection
<PSObject>] [<CommonParameters>]
New-vRNIDataSource [-Username <String>] [-Password <String>] [-IP <String>] [-FDQN <String>] -CollectorVMId
<String> -Nickname <String> [-Enabled <Boolean>] [-Notes <String>] -TenantID <String> -ApplicationID <String>
-SecretKey <String> -SubscriptionID <String> [-FlowsEnabled <Boolean>] [-Connection <PSObject>]
[<CommonParameters>]
New-vRNIDataSource [-Username <String>] [-Password <String>] [-IP <String>] [-FDQN <String>] -CollectorVMId
<String> -Nickname <String> [-Enabled <Boolean>] [-Notes <String>] [-KubeConfig <String>] -NSXTManagerID <String>
[-Connection <PSObject>] [<CommonParameters>]
DESCRIPTION
Datasources within vRealize Network Insight provide the data shown in
the UI. The vRNI Collectors periodically polls the datasources as the
source of truth. Typically you have a vCenter, NSX Manager and physical
switches as the datasource.
This cmdlet adds new datasources to vRNI, so it can retrieve data from it and
correlate and display this data in the interfce.
PARAMETERS
-Username <String>
Username to use to login to the datasource
Required? false
Position? named
Default value
Accept pipeline input? false
Accept wildcard characters? false
-Password <String>
Password to use to login to the datasource
Required? false
Position? named
Default value
Accept pipeline input? false
Accept wildcard characters? false
-IP <String>
The IP address of the datasource
Required? false
Position? named
Default value
Accept pipeline input? false
Accept wildcard characters? false
-FDQN <String>
The FDQN address of the datasource
Required? false
Position? named
Default value
Accept pipeline input? false
Accept wildcard characters? false
-CollectorVMId <String>
Collector (Proxy) Node ID
Required? true
Position? named
Default value
Accept pipeline input? false
Accept wildcard characters? false
-Nickname <String>
Nickname for the datasource
Required? true
Position? named
Default value
Accept pipeline input? false
Accept wildcard characters? false
-Enabled <Boolean>
Whether we want to enable the datasource
Required? false
Position? named
Default value True
Accept pipeline input? false
Accept wildcard characters? false
-Notes <String>
Optional notes for the datasource
Required? false
Position? named
Default value
Accept pipeline input? false
Accept wildcard characters? false
-NSXEnableCentralCLI <Boolean>
These params are only required when adding a NSX Manager as datasource
Enable the central CLI collection
Required? false
Position? named
Default value True
Accept pipeline input? false
Accept wildcard characters? false
-NSXEnableIPFIX <Boolean>
Enable NSX IPFIX as a source
Required? false
Position? named
Default value True
Accept pipeline input? false
Accept wildcard characters? false
-NSXEnableLatency <Boolean>
Enable Virtual Latency (VTEP, VNIC, & PNIC) streaming from NSX to vRNI
Required? false
Position? named
Default value False
Accept pipeline input? false
Accept wildcard characters? false
-NSXvCenterID <String>
vCenter ID that this NSX Manager will be linked too
Required? false
Position? named
Default value
Accept pipeline input? false
Accept wildcard characters? false
-CiscoSwitchType <String>
This params is only required when adding a cisco switch
Set the switch type
Required? true
Position? named
Default value
Accept pipeline input? false
Accept wildcard characters? false
-DellSwitchType <String>
This params is only required when adding a dell switch
Set the switch type
Required? true
Position? named
Default value
Accept pipeline input? false
Accept wildcard characters? false
-TenantID <String>
These params are only required when adding an Azure subscription as datasource
Azure Tenant ID
Required? true
Position? named
Default value
Accept pipeline input? false
Accept wildcard characters? false
-ApplicationID <String>
Azure Application ID
Required? true
Position? named
Default value
Accept pipeline input? false
Accept wildcard characters? false
-SecretKey <String>
Azure Secret Key
Required? true
Position? named
Default value
Accept pipeline input? false
Accept wildcard characters? false
-SubscriptionID <String>
Azure Subscription ID
Required? true
Position? named
Default value
Accept pipeline input? false
Accept wildcard characters? false
-FlowsEnabled <Boolean>
Retrieve Flows?
Required? false
Position? named
Default value True
Accept pipeline input? false
Accept wildcard characters? false
-KubeConfig <String>
KubeConfig as a string
Required? false
Position? named
Default value
Accept pipeline input? false
Accept wildcard characters? false
-NSXTManagerID <String>
NSX-T Manager entity ID
Required? true
Position? named
Default value
Accept pipeline input? false
Accept wildcard characters? false
-Connection <PSObject>
vRNI Connection object
Required? false
Position? named
Default value $defaultvRNIConnection
Accept pipeline input? false
Accept wildcard characters? false
<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (https:/go.microsoft.com/fwlink/?LinkID=113216).
INPUTS
OUTPUTS
-------------------------- EXAMPLE 1 --------------------------
PS C:\\>$collectorId = (Get-vRNINodes | Where {$_.node_type -eq "PROXY_VM"} | Select -ExpandProperty id)
PS C:\\> New-vRNIDataSource -DataSourceType vcenter -FDQN vc.nsx.local -Username administrator@vsphere.local
-Password secret -CollectorVMId $collectorId -Nickname vc.nsx.local
First, get the node ID of the collector VM (assuming there's only one), then add a vCenter located at vc.nsx.local
to vRNI.
-------------------------- EXAMPLE 2 --------------------------
PS C:\\>$collectorId = (Get-vRNINodes | Where {$_.node_type -eq "PROXY_VM"} | Select -ExpandProperty id)
PS C:\\> $vcId = (Get-vRNIDataSource | Where {$_.nickname -eq "vc.nsx.local"} | Select -ExpandProperty entity_id)
PS C:\\> New-vRNIDataSource -DataSourceType nsxv -FDQN mgr.nsx.local -Username admin -Password secret -Nickname
mgr.nsx.local -CollectorVMId $collectorId -Enabled $True -NSXEnableCentralCLI $True -NSXEnableIPFIX $True
-NSXvCenterID $vcId
Adds a new NSX Manager as a data source, auto select the collector ID (if you only have one), enable the NSX
Central CLI for collecting data, also enable NSX IPFIX for network datastream insight from the point of view of
NSX.
-------------------------- EXAMPLE 3 --------------------------
PS C:\\>$collectorId = (Get-vRNINodes | Where {$_.ip_address -eq "10.0.0.11"} | Select -ExpandProperty id)
PS C:\\> New-vRNIDataSource -DataSourceType azure -CollectorVMId $collectorId -Nickname Azure-1 -TenantID
xxx-xxx-xxx-xxx-xxx -ApplicationID xxx-xxx-xxx-xxx-xxx -SecretKey secret -SubscriptionID xxx-xxx-xxx-xxx-xxx
Adds a new Azure subscription; first gets a specific collector appliance based on IP, and continues to add the
Azure subscription based on the application registration information.
More info on requirements can be found here: https://docs.vmware.com/en/VMware-vReal ... .0/com.vmw
are.vrni.using.doc/GUID-12272E1A-055F-47E9-9EA6-8693FE86AA02.html
-------------------------- EXAMPLE 4 --------------------------
PS C:\\>$nsxtId = (Get-vRNIDataSource -DatasourceType nsxt | Where {$_.nickname -eq "my-nsxt-manager"} |
Select -ExpandProperty id)
PS C:\\> $collectorId = (Get-vRNINodes | Where {$_.ip_address -eq "10.0.0.11"} | Select -ExpandProperty id)
PS C:\\> $kubeconfig = (Get-Content ~/.kube/config | Out-String)
PS C:\\> New-vRNIDataSource -DataSourceType kubernetes -Nickname k8s-cluster-1 -CollectorVMId $collectorId
-NSXTManagerID $nsxtId -KubeConfig $kubeconfig
Add a Kubernetes cluster as a data source. First gets the entity ID of the NSX-T Manager supporting the container
network, then vRNI Collector ID, then puts the kubeconfig file into a string, and finally adds the Kubernetes
cluster to vRNI.
RELATED LINKS