- Community Home
- >
- Storage
- >
- HPE Nimble Storage
- >
- Application Integration
- >
- Powershell - New-NSVolume does not work
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-26-2015 12:27 PM
05-26-2015 12:27 PM
Re: Powershell - New-NSVolume does not work
I just downloaded V2 again from the site. Was not blocked. Extracted, cleared out my powershell directory, copied these in, did not run install.ps1:
PS C:\Users\terry> $snap = Get-NSSnapShot | where {($_.name -match "test")}
Get-NSSnapShot : Unable to find type [snap]. Make sure that the assembly that contains this type is loaded.
At line:1 char:9
+ $snap = Get-NSSnapShot | where {($_.name -match "test")}
+ ~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (snap:TypeName) [], RuntimeException
+ FullyQualifiedErrorId : TypeNotFound
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-26-2015 12:34 PM
05-26-2015 12:34 PM
Re: Powershell - New-NSVolume does not work
Interesting, im fairly certain it should be
give me a little bit, i'll review and push an update.
On Tue, May 26, 2015 at 12:27 PM, terryzolinski <connect@nimblestorage.com>
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-26-2015 02:37 PM
05-26-2015 02:37 PM
Re: Powershell - New-NSVolume does not work
So i just pushed a new snap.ps1 file that updates the namespace. The old dll didnt have a namespace so references were jsut like new-object vol.. which, could be a problem.. so i added namespace to the new dll, so its more like, new-object nimble.vol
I thought all of those had been fixed and pushed, but apparently not.
also i find it odd that the DLL commit/date make it seem like thats the old DLL.. clearly not the case if its requiring the Nimble namespace addition
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-26-2015 03:07 PM
05-26-2015 03:07 PM
Re: Powershell - New-NSVolume does not work
Downloaded the new zip, it wasn't blocked. Still erroring on assembly
PS C:\Users\terry> Get-NSSnapShot
Get-NSSnapShot : Unable to find type [snap]. Make sure that the assembly that contains this type is loaded.
At line:1 char:1
+ Get-NSSnapShot
+ ~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (snap:TypeName) [], RuntimeException
+ FullyQualifiedErrorId : TypeNotFound
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-23-2015 02:13 PM
07-23-2015 02:13 PM
Re: Powershell - New-NSVolume does not work
So, I've determined that my issues were related to the specific build of the Nimble OS we were running. At the time this did not work we were running 2.2.5.0-197583-opt. Now we are on 2.2.8-252438-opt and this works as expected, no errors on assembly.
- « Previous
-
- 1
- 2
- Next »