- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Procurve 2650 J4899B running H.10.29 crashed
Switches, Hubs, and Modems
1753774
Members
6993
Online
108799
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
03-19-2007 01:52 AM
03-19-2007 01:52 AM
Procurve 2650 J4899B running H.10.29 crashed
Switch J4899B 2650 running H.10.29 froze. Link lights still on, no access via ping, snmp or
telnet. No access to clients on switch. No
response from Port LED view button. Came back
up after power cycle. We have several hundred
Procurve switches at our site. Nothing in logs
to indicate cause of crash. 1 hour before
crash, this was syslogged " radius: Can't reach
RADIUS server ...". Switch is 1 month old.
It is the only switch where we have been
testing webauth with RADIUS, and one of a few
running H.10.29 so far. A support case has
been openned.
Config is below.
hostname "xxx"
snmp-server location "xxxx"
max-vlans 64
time timezone -300
no cdp run
no web-management
interface 13
speed-duplex 10-half
exit
interface 47
no lacp
exit
interface 49
name "xxx"
exit
ip default-gateway 172.17.1.1
sntp server 129.97.x.y
timesync sntp
sntp unicast
logging facility local3
logging 129.97.x.y
vlan 1
name "DEFAULT_VLAN"
ip address dhcp-bootp
no untagged 1-50
exit
vlan 3010
name "b1prinet"
ip address 172.17.1.30 255.255.255.192
tagged 3,9,33,49-50
exit
vlan 65
name "scicompnet"
no ip address
tagged 49
ip igmp
exit
vlan 24
name "b2net"
untagged 5-10
no ip address
tagged 49
ip igmp
exit
vlan 18
name "sci-naanet"
no ip address
tagged 3,9,33,49
ip igmp
exit
vlan 53
name "VLAN53"
no ip address
tagged 49
ip igmp
exit
vlan 62
name "b1net"
untagged 1-2,4,11-32,34-48
no ip address
tagged 49
ip igmp
exit
ip authorized-managers 129.97.x.0 255.255.255.0
ip authorized-managers 129.97.y.0 255.255.255.0
aaa authentication port-access eap-radius
radius-server host 129.97.x.y
aaa port-access supplicant 45
aaa port-access web-based 47
aaa port-access web-based 47 redirect-url "http://www.google.ca"
spanning-tree
no spanning-tree 49 edge-port
no spanning-tree 50 edge-port
Bruce Campbell
Director, Network Services
Information Systems and Technology
MC 1018
(519)888-4567 x38323
University of Waterloo, Waterloo, ON
Director, Network Services
Information Systems and Technology
MC 1018
(519)888-4567 x38323
University of Waterloo, Waterloo, ON
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-19-2007 03:34 AM
03-19-2007 03:34 AM
Re: Procurve 2650 J4899B running H.10.29 crashed
crashed again. Power cycle fixed it again.
This was syslogged 1 hour before the crash:
Can't reach RADIUS server 129.97.x.y
We had one client on the webauth port and
I have turned off webauth now. (it wasn't
working anyway)
Bruce Campbell
Director, Network Services
Information Systems and Technology
MC 1018
(519)888-4567 x38323
University of Waterloo, Waterloo, ON
Director, Network Services
Information Systems and Technology
MC 1018
(519)888-4567 x38323
University of Waterloo, Waterloo, ON
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP