New-NetworkControllerDiscoveredTopologyNode

New-NetworkControllerDiscoveredTopologyNode

Adds or changes a topology node in the discovered topology.

Syntax

Parameter Set: Default
New-NetworkControllerDiscoveredTopologyNode [-ResourceId] <String> [-Properties] <DiscoveredTopologyNodeProperties> [[-ResourceMetadata] <ResourceMetadata> ] [[-VersionId] <String> ] [[-Force]] -ConnectionUri <String> [-CertificateThumbprint <String> ] [-Credential <PSCredential> ] [-Confirm] [-WhatIf] [ <CommonParameters>]

Detailed Description

The New-NetworkControllerDiscoveredTopologyNode cmdlet adds or changes a topology node in the discovered topology. To discover the topology of a network, run the Invoke-NetworkControllerTopologyDiscovery cmdlet.

For information about discovered network topology, see the Get-NetworkControllerDiscoveredTopology cmdlet.

If the discovered topology does not identify certain nodes, you can add them by using this cmdlet. If you develop a script or tool that compares the discovered topology to the expected topology, the comparison logic can show nodes that are present in the network, but that are not discoverable by the discovery logic. Adding those nodes to the discovered topology lets your script ignore these elements when it displays the differences between the discovered and the actual topology.

This cmdlet can modify a topology node to hide it by specifying the IsHidden property. If the discovery logic displays an element that is not present in the actual topology, you can hide it so that a script or tool that compares the discovered and the actual topologies does not display that anomaly.

Parameters

-CertificateThumbprint<String>

Specifies the certificate thumbprint of a digital public key X.509 certificate of a user account that has permission to perform this action. In order for Network Controller to authorize the account, specify this thumbprint by using the ClientCertificateThumbprint parameter of the Install-NetworkController or Set-NetworkController cmdlet.

Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-ConnectionUri<String>

Specifies the Uniform Resource Identifier (URI) of the network controller that all Representational State Transfer (REST) clients use to connect to that controller.

Aliases

none

Required?

true

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-Credential<PSCredential>

Specifies a user credential that has permission to perform this action. The default value is the current user.

This user must be a member of in the security group specified by the ClientSecurityGroup parameter of the Install-NetworkController cmdlet.

Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-Force

Forces the command to run without asking for user confirmation.

Aliases

none

Required?

false

Position?

9

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-Properties<DiscoveredTopologyNodeProperties>

Specifies the properties of the topology node this cmdlet adds or modifies. For discovered topology nodes, you can modify the following property:

-- IsHidden. Whether to hide the node. If you run the Get-NetworkControllerDiscoveredTopology cmdlet, a hidden node does not appear.

For a node that you add manually, you can specify the following properties:

-- Name. The name of the node.
-- Model. The model of the node.
-- OS. The operating system of the node.
-- Serial. The serial number of the node.
-- Type. The type of node. Acceptable values for this property are Server and Switch.
-- Vendor. The vendor of the node.
-- TerminationPoints. Use this property to add termination points manually to the manually added topology node.

Aliases

none

Required?

true

Position?

4

Default Value

none

Accept Pipeline Input?

true (ByPropertyName)

Accept Wildcard Characters?

false

-ResourceId<String>

Specifies the resource ID of the topology node that this cmdlet adds.

Aliases

none

Required?

true

Position?

1

Default Value

none

Accept Pipeline Input?

true (ByPropertyName)

Accept Wildcard Characters?

false

-ResourceMetadata<ResourceMetadata>

Specifies metadata information for the client, such as tenant ID, group ID, and resource name.

Aliases

none

Required?

false

Position?

7

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-VersionId<String>

Specifies the entity tag (ETag) parameter of the resource. An ETag is an HTTP response header returned by an HTTP-compliant web server. An ETag is used to determine change in the content of a resource at a given URL. The value of the header is an opaque string representing the state of the resource at the time the response was generated.

Aliases

none

Required?

false

Position?

8

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-Confirm

Prompts you for confirmation before running the cmdlet.

Required?

false

Position?

named

Default Value

false

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-WhatIf

Shows what would happen if the cmdlet runs. The cmdlet is not run.

Required?

false

Position?

named

Default Value

false

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

<CommonParameters>

This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see    about_CommonParameters.

Inputs

The input type is the type of the objects that you can pipe to the cmdlet.

Outputs

The output type is the type of the objects that the cmdlet emits.

Examples

Example 1: Create and add a node

The first command creates a DiscoveredTopologyNodeProperties object by using the New-Object cmdlet. The command stores the node in the $Node variable.

The next three command assign values to some of the properties of the node.

The final command adds a node to the discovered topology that has the resource ID Node11. The command specifies a connection URI and the properties stored in $Node.

PS C:\> $Node = New-Object Microsoft.Windows.NetworkController.DiscoveredTopologyNodeProperties
PS C:\> $Node.Name = "Host_01"
PS C:\> $Node.Type = "Server" 
PS C:\> $Node.Vendor = "HP"
PS C:\> New-NetworkControllerDiscoveredTopologyNode -ConnectionUri "https://restserver" -ResourceId "Node11" -Properties $Node

Example 2: Hide a topology node

The first command gets an existing topology node by using the Get-NetworkControllerDiscoveredTopologyNode cmdlet, and then stores it in the $Node variable.

The second command assigns a value of true to the IsHidden property of $Node.

The final command updates the properties of the node to match the current value of $Node.

PS C:\> $Node = Get-NetworkControllerDiscoveredTopologyNode -ConnectionUri "https://networkcontroller" -ResourceId "Node12"
PS C:\> $Node.IsHidden = "true"
PS C:\> New-NetworkControllerDiscoveredTopologyNode -ConnectionUri "https://networkcontroller" -ResourceId "Node12" -Properties $Node

Get-NetworkControllerDiscoveredTopology

Get-NetworkControllerDiscoveredTopologyNode

Install-NetworkController

Invoke-NetworkControllerTopologyDiscovery

New-Object

Remove-NetworkControllerDiscoveredTopologyNode

Set-NetworkController