- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 11-10-2015 01:08 PM
This script allows a bulk load of VLANs via a CSV file into a single or multiple UCS domains. The ZIP file contains a sample file. Script can run interactively or silently via command line parameters.
v0.1.01 - Initial version
v0.1.02 - Updated to validate the VLAN CSV file
v0.1.03 - Updated to check for overlaps of VLAN names and numbers against existing UCS domain(s)
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Joe, thank you so much for this script, it is a life saver!
I made some modifications to it and the CSV, so now after it creates the VLANs they are then added to the appropriate port-channels on the FI's as well!
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
That's fantastic to hear. Glad it helped you and you were able to customize it for your specific requirements. Take care!
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Hi Joe!
Thanks a lot for the script! It also helped me a lot!
I do not know if it is related to the last version of PowerTool Suite but I had to modify the PowerShell Module that the script is looking for.
From :
Import-Module ciscoUcsPs
To
Import-Module Cisco.Ucs.Core
- I also update the search condition ($Modules -like "Cisco.Ucs.Core") -
The script worked like a charm with this minor correction. Let me know if it is right or not (I see that there is a Cisco.UCSManager module also loaded).
Best,
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Hi Maxence
The UCS PowerTool module names are changed in UCS PowerTool Suite 2.0.1 release. You need to update the script to use the new module names. You need to change the module name to Cisco.UCSManager
The following table lists the module name changes in this release:
Previous Module Name | |
---|---|
Thanks,
Sumanth.
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Hi Sumanth!
Thanks for the table! That was exactly my interrogation when I changed the verification to the Ucs.Core module. So now I know that I should check for the UCSManager instead (or maybe both?)
Maybe a new release of the script can be uploaded? > joemar ?
Thanks again!
EDIT: Ok, the Module Names change was described in the Release Notes, sorry to have missed that!
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Hello Team,
This is a great script - what would i do - to just list the VLANs in the domains?
No central/Director in the Customer ecosystem.
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Hi Vishwajeeth,
You can use the below cmdlet to get the VLANs available in the UCS Domain.
Get-UcsVlan- To get all the fabric level VLANs
Get-UcsAdaptorVlan - To get the VLANs configured on a particular Ethernet interface
Thanks,
Sumanth
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
is there a way i can get that what ever VLANs are in above script i want to test that all VLANS able to respond to ping or so some testing kind of??
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
great script it's helped a lot :)