-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No vnics shown after 9 UCSx blades using get-intersightvnicethif #99
Comments
This is still an issue but I found another way to pull the date |
What's the value of Get-IntersightVnicEthIf -Count $true in your environment? If it's over 100 you'll need to specify a -Top parameter or do something like this to filter results on the Intersight side instead of client side:
|
That process shows the vnics for the server that using that my code would not show. |
Here's another way to get the same information without copying the MoId: # One Intersight API call
$results = Get-IntersightVnicEthIf -Top 1000 -Select 'Name,MacAddress,Profile' -Expand 'Profile($select=Name)' | Select-Object -ExpandProperty Results
$results | Select-Object @{n='Profile';e={$_.Profile.ActualInstance.Name}},Name,MacAddress |
THis would be great to put into examples/server . Not at all obvious how to get to the connections data, and this is important for any automated provisioning. |
Describe the bug
When running Get-IntersightVnicEthIf, I get vnics returned for the first 9 UCSx blades but anything after that comes back blank. The vnics are shown in the Connectivity section of the Server Profile in the GUI with no issues.
To Reproduce
$bladename = "servername"
$server = Get-IntersightServerProfile | Where-Object Name -eq $BladeName
$SPMoid = $server.Moid
$vnics = Get-IntersightVnicEthIf | Where {$_.Profile.ActualInstance.Moid -eq $SPMoid} | Select-Object Name, MacAddress
Version used
Expected behavior
Should provide a list of the VNICs witth the Name and MacAddress. It works on 9 blades but anything after 9 it comes back blank even though the vnics can be seen in the GUI for the Server Profile.
Screenshots
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: