This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Extreme Networks
- Community List
- Switching & Routing
- ExtremeSwitching (EXOS/Switch Engine)
- System Type: EXOS or SwitchEngine ?
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
System Type: EXOS or SwitchEngine ?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
a month ago
We noticed the show switch command on 2 different 5420s gave another System Type:
System Type: 5420F-48P-4XE-EXOS
System Type: 5420F-48P-4XE-SwitchEngine
A few of the Switchengine ones give us a headache doing tftp image upload ( 31 -> 32 ) as tftp times out.
download image 10.10.10.10 summit_arm-32.6.1.5-patch1-2.xos vr vr-def
Note: The inactive partition (secondary) will be used for installation.
Do you want to install image after downloading? (y - yes, n - no, <cr> - cancel) Yes
Downloading to Switch
Error: Failed to download image - tftp: timeout
1) what is the difference?
2) do we need to look for a exos 32 for the SwitchEngine type?
Solved! Go to Solution.
1 ACCEPTED SOLUTION
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
a month ago
Hello!
As of 32.1, EXOS was rebranded to SwitchEngine when running on universal platforms (5XXX and 7XXX) series switches. They are exactly the same software, just a different name.
Regarding the TFTP timeout, that seems unrelated. I would try using a larger block-size to reduce the potential for TFTP timeouts (specify 'block-size 65000' at the end of the 'download image' command). Otherwise, it could be an issue with TFTP being blocked somewhere in the network, or some server issue, that is causing the timeout.
Hope that helps!
5 REPLIES 5
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
a month ago
cli help said default block size is 1400,
but going big 65000 timed out as well.
So I tried small 500 and hoorai,
image get tftp'ed just fine!
Many thanks for te hints.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
a month ago
The misbehaving 5420 mentioned memory problems:
03/29/2024 16:09:39.79 <Noti:EPM.install_status> User admin: Image installation finished with status success.
03/29/2024 16:09:39.56 <Warn:EPM.Upgrade.State> Upgrade status Installation time may be greater than expected due to a lack of memory resources
03/29/2024 16:07:07.75 <Noti:EPM.Upgrade.Strt> User admin: Image upgrade has started.
System Memory Information
-------------------------
Total DRAM (KB): 1048576
System (KB): 45916
User (KB): 450288
Free (KB): 552372
While another 5420 in the same rack has a lot more DRAM and this more free space:
System Memory Information
-------------------------
Total DRAM (KB): 2097152
System (KB): 71684
User (KB): 451316
Free (KB): 1574152
Different memory sizes on the same type of switch?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
a month ago
I'm pretty sure the 48 port 5420s have 2GB of RAM, the 24 port 5420s have 1GB of RAM.
Regarding the logs, those are informational, but installation will complete regardless in a similar amount of time.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
3 weeks ago
DRAM is not linked to the number of ports :
5420F-48P-4XE-SwitchEngine - Total DRAM (KB): 2097152
5420F-48P-4XE-EXOS - Total DRAM (KB): 1048576
