- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- Problems with Proliant Support Pack 6.40a
ProLiant Servers (ML,DL,SL)
1753773
Members
5524
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
07-10-2003 02:58 PM
07-10-2003 02:58 PM
Problems with Proliant Support Pack 6.40a
Hi, I was wondering if anyone has been experiencing similar problems with the latest Proliant Support Pack, ver 6.40a.
After installing the support pack, I reboot as required. After the reboot, the server doesn't come back online. If I look at the server ipconfig /all, I see that my enet address is 00:00:00:00:00:00, and obviously the server hasn't been able to DHCP. This comes right after rebooting the server.
Anyone else experienced this? The same has occured on five out of five servers I have installed the support pack on so far. Four DL380 G3s, one DL320. This is obviously a major problem if installing the support pack on remote servers that don't have ILOs (or anyone handy to reboot the server the second time)!.
The second problem is with the 'Version control Repository Manager' - I can't seem to get it to recognise Support Pack 6.40a. I have manually copied it into the repository directory, rescanned, but it never picks it up. If I try a single component from support pack 6.30a, the repository manager picks it up straight away, but it won't pick up a single component from version 6.40a.
Any thoughts/comments?
After installing the support pack, I reboot as required. After the reboot, the server doesn't come back online. If I look at the server ipconfig /all, I see that my enet address is 00:00:00:00:00:00, and obviously the server hasn't been able to DHCP. This comes right after rebooting the server.
Anyone else experienced this? The same has occured on five out of five servers I have installed the support pack on so far. Four DL380 G3s, one DL320. This is obviously a major problem if installing the support pack on remote servers that don't have ILOs (or anyone handy to reboot the server the second time)!.
The second problem is with the 'Version control Repository Manager' - I can't seem to get it to recognise Support Pack 6.40a. I have manually copied it into the repository directory, rescanned, but it never picks it up. If I try a single component from support pack 6.30a, the repository manager picks it up straight away, but it won't pick up a single component from version 6.40a.
Any thoughts/comments?
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-10-2003 03:15 PM
07-10-2003 03:15 PM
Re: Problems with Proliant Support Pack 6.40a
Sorry to reply to my own post, but I figured out the answer to my second problem. I was running ver 1 of the VCRM, didn't realise there was a newer version until I read about it in another post!
Updating to the new version fixed my problem - Support Pack 6.40a is now recognised. Another bonus - the new VCRM supports automatic updating... no more need to worry about using ActiveUpdate!
Updating to the new version fixed my problem - Support Pack 6.40a is now recognised. Another bonus - the new VCRM supports automatic updating... no more need to worry about using ActiveUpdate!
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