Can't do a firmware selection in Netsight
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎01-30-2017 11:14 AM
When I use the Firmware Upgrade Wizard in Netsight, I can't do a Frimware Selection.
So I cann't map af device type to an image an upgrade the switch.
I tested a couple devices (X440, X460)
Version Netsight 7.0.9.4
So I cann't map af device type to an image an upgrade the switch.
I tested a couple devices (X440, X460)
Version Netsight 7.0.9.4
Johan Hendrik
System Architect
Audax
6 REPLIES 6
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎02-06-2017 05:44 AM
Do you mean this view?
On my side there is no firmware shown automaticaly, but if i check the "Show All Images", there i can choose the firmware i want. And the Update works for Summit Switches.
On my side there is no firmware shown automaticaly, but if i check the "Show All Images", there i can choose the firmware i want. And the Update works for Summit Switches.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎02-06-2017 05:44 AM
No, I see the firmware but I cann't assign the firmware to the device or family
Johan Hendrik
System Architect
Audax
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎01-31-2017 01:13 PM
I have found most issues having a question mark are fixed by correcting SNMP credentials on either the switch or in Profile/Device Mapping in Netsight.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎01-30-2017 12:39 PM
I have had this same issue. I deleted the device and then re-added it back to Netsight. And then I was able to upgrade the firmware without any problems. It seems like there have been a few other people with this same problem and deleting/re-adding the device fixed it.
I am thinking there might be a bug hidden away in there somewhere?
I am thinking there might be a bug hidden away in there somewhere?
