- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
M4300 firmware with differing models in stack - is firmware file same for all M4300 models
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The M4300 Admin guide highlights that when stacking switches together you can use different models from the M4300
range which is great, but that they must all have the same firmware version.
When I navigate to the firmware download for a specific switch, the download file looks to be model specific.
Is this indeed the case ? or is it one firmare file for all models in the range ?
If they are different firmware files per model, presumably this means dont use the central stack firmware update
where it pushes the same file to all switches in the stack
Solved! Go to Solution.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi
While there is a download page per model for each member of the M4300 line of switches, you'll see that the download URL is the same for all models. I remember this started around the timeline of the M4100 series where they (thankfully) started to make 1 firmware image for an entire line of switches. (Which made testing and updating much easier!)
Thus, since it is the same image, it gets copied first to the stack master (image1 or image2) and afterwards the stack master takes care of copying the image onto the other stack members.
All Replies
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi
While there is a download page per model for each member of the M4300 line of switches, you'll see that the download URL is the same for all models. I remember this started around the timeline of the M4100 series where they (thankfully) started to make 1 firmware image for an entire line of switches. (Which made testing and updating much easier!)
Thus, since it is the same image, it gets copied first to the stack master (image1 or image2) and afterwards the stack master takes care of copying the image onto the other stack members.