- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- server access failure on a ProCurve Switch 4108GL
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
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
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
05-18-2012 10:12 AM
05-18-2012 10:12 AM
server access failure on a ProCurve Switch 4108GL
Dear All
i'm using a ProCurve Switch 4108GL for internal network of my cluster. Recently i try to update my version of OS (Rocks 6.0) and face a problem with the node instalation:
The node could get this IP with PXe protocol, but at the moment to download the kickstart from the server, i detect an access failure as the link with the server can not be established.
The advise me the problem is because of the time to the spanning tree to be established. I read in the documentation that if it occurs, i should put the port as "fast" (Ref: Spanning Tree Options: RSTP (802.1w) and STP (802.1d)). The problem is that the switch is configured with RSTP, that suppose to be fast.
Can someone help me in the issue?
Best regards