Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
When the "set-navfileraddress" cmdlet is used to add an IP address to an existing vfiler in completely overwrites the vfiler's exports file, resetting it back to default values.
This is likely because this cmdlet is using the "vfiler-setup" API. (This is a known behavior with vfiler setup) Why is the cmdlet using "vfiler-setup" and not just "vfiler-add-ipaddress"?
When the same operation is done from the console (via the "vfiler add") command it works fine so there must be some way of the cmdlet to do this without invoking vfiler setup api.
Solved! See The Solution
1 ACCEPTED SOLUTION
migration has accepted the solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
My colleague just answered this question - it's using the vfiler-setup API to ensure that the new IP address gets added as an alias line in the RC file. So the real issue is fixing the vfiler-setup API not to regenerate the exports file every time it is run.
1 REPLY 1
migration has accepted the solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
My colleague just answered this question - it's using the vfiler-setup API to ensure that the new IP address gets added as an alias line in the RC file. So the real issue is fixing the vfiler-setup API not to regenerate the exports file every time it is run.
