Possible Bug when changing sysName through NMS
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎03-17-2017 02:38 PM
I recently found that when changing the sysName through Netsight it configures the old sysName as a display string on all ports that did not previously have a display string configured.
X460G2-48p-10G4 running 15.7.3.1-patch1-6.xos
NMS 7.0.6.27
X460G2-48p-10G4 running 15.7.3.1-patch1-6.xos
NMS 7.0.6.27
9 REPLIES 9
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎03-23-2017 04:54 PM
Hi All,
Please upgrade to version 7.1.1.9 of Extreme Management. I was able to replicate this in 7.0.9.4, but not in 7.1.1.9.
Please upgrade to version 7.1.1.9 of Extreme Management. I was able to replicate this in 7.0.9.4, but not in 7.1.1.9.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎03-23-2017 04:54 PM
Thanks for the follow up.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎03-23-2017 04:54 PM
Hi Bob,
I used 7.1.1.9 in the tests above...
I used 7.1.1.9 in the tests above...
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎03-20-2017 03:12 PM
Hi,
How is the sysname being edited from the NMS side?
How is the sysname being edited from the NMS side?
