- Community Home
- >
- Networking
- >
- Legacy
- >
- Switching and Routing
- >
- ProCurve 2626 (J4900B) - Error Light, then reboots...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-02-2011 03:34 AM - edited 11-02-2011 03:35 AM
11-02-2011 03:34 AM - edited 11-02-2011 03:35 AM
ProCurve 2626 (J4900B) - Error Light, then reboots.
Hello,
I appear to have a problem with a NetGear ProCurve 2626.
When purchased it was tested for a week in our Dev setup without issues (Around 20 Machines are connected to this switch, as well as two NETGEAR unmanaged 5 port switches) we then placed into the live Environment where it was fine for 2 days. Then it appeared to of developed a fault. The switch kept on rebooting randomly with a RED light, It could range from 5 minutes to 4 hours. The only logs were due to a power failure - there was no such issue. We switched over to our backup switch (Which has been running for ~3/4 years no issues, NETGEAR Unmanaged 24 port.)
I called HP and was promptly replaced for a new switch which was tested and worked without fault. It was placed into our live setup and was up for over 140 days until it then randomly rebooted. Now the switch appears to reboot every 20-30 days and revert its date to factory settings - even though I have changed it via the console.
Please review the status /logs...
System Status
System Up-Time: 4 days, 10 hours, 24 minutes, 5 seconds
System CPU Util(%): 6
System Memory: Total - 15973944 Free - 10445760
Product: ProCurve Switch 2626 (J4900B)
Version: H.10.83, ROM H.08.02
Console Log
Keys: W=Warning I=Information
M=Major D=Debug
---- Event Log listing: Events Since Boot ----
M 01/01/90 00:00:04 sys: 'System reboot due to Power Failure'
I 01/01/90 00:00:04 system: --------------------------------------------------
I 01/01/90 00:00:04 system: System went down without saving crash information
I 01/01/90 00:00:14 lacp: Passive Dynamic LACP enabled on all ports
I 01/01/90 00:00:15 udpf: DHCP relay agent feature enabled
I 01/01/90 00:00:15 stack: Stack Protocol enabled
I 01/01/90 00:00:15 tftp: Enable succeeded
I 01/01/90 00:00:15 system: System Booted.
-- MORE --, next page: Space, next line: Enter, quit: Control-C
There are no problems with Power on site, I've got a couple of servers with over 300+ days uptime on all on the same Power strip (Surge Protected) However, no UPS.
Should I call HP for another replacement? The switch operates fine other than these random reboots which is causing some disruption on our network.
Thanks in advance.
Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-02-2011 04:43 AM
11-02-2011 04:43 AM
Re: ProCurve 2626 (J4900B) - Error Light, then reboots.
With a model that old (and out of production for a couple of years) I would consider writing it off.