- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers - Netservers
- >
- Proliant Microserver N40L: Remote Access Card is b...
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
06-30-2012 11:27 AM
06-30-2012 11:27 AM
Proliant Microserver N40L: Remote Access Card is buggy and lacks GPL source
(Here's a copy and paste, tweaked a bit, of my post on another forum:)
-----------------
...you're not the only one for whom the remote-access card often can't be... remote-accessed.
Mine is a buggy piece of crap. Failure modes I've noticed:
[*]Card entirely off the network -- have to reboot the card via a serial console to the card itself! I've even seen the **bleep** thing spewing errors over that serial console.
[*]Card is visible, but can't be logged into.
Rather, it'll log me directly into... the login page. HTTP requests go: login page -> javascript file -> login page.
My workaround: switch to another browser. Then if login times out there, I have to switch to yet a third browser... or a different computer. Even clearing cookies AND rebooting the RAC sometimes doesn't fix it.
[*]Card is visible, and can be logged into, but any attempt to access the KVM page takes me directly to the login page.
[*]Even when working, the KVM viewer page gives files with textual vomit at the end of the file extension.
viewer.jnlp(192.168.1.11@0@0000000000000)
viewer.jnlp(192.168.1.11@0@0000000000000)
viewer.jnlp(192.168.1.11@0@0000000000000)
viewer.jnlp(192.168.1.11@0@0000000000000)
viewer.jnlp(192.168.1.11@0@0000000000000)
viewer.jnlp(192.168.1.11@0@0000000000000)
viewer.jnlp(192.168.1.11@0@0000000000000)
viewer.jnlp(192.168.1.11@0@0000000000000)
Windows doesn't know how to open a .jnlp(192.168.1.11@0@0000000000000) file... nor does Gnome.
Too bad the microserver entirely lacks a Super IO chip, so there's no way to get a real serial port. (PCIe serial port doesn't work in Grub, and doesn't do console redirection.)
Now, my two questions:
[*] Who do we talk to to get this fixed? The Proliant chat people say they're just for hardware-replacement incidents.
[*] Who do I talk to to get the GPL source for the Remote access Card?
uname -a gives:
Linux microserver-ipmi 2.6.23.1-ASPEED-v.0.11 #26 PREEMPT Thu Aug 26 17:58:31 CST 2010 armv5tejl unknown
If I trigger an oops by trying to cat /dev/nram, I get the following list of loaded modules:
Modules linked in: aess_video g_mass_storage g_kbdmouse g_composite g_ast2050_udc ncsi_protocol bonding aess_pwmdrv aess_fansensordrv aess_cryptodrv aess_pecisensordrv aess_i2cdrv(F) aess_dynairqdrv(F) aess_gpiodrv aess_biospostdrv aess_memdrv aess_kcsdrv(F) vkcs aess_eventhandlerdrv
Log of boot and some other shell commands, on the card itself: http://pastebin.com/67FXc52g
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-31-2012 12:29 PM - edited 07-31-2012 12:39 PM
07-31-2012 12:29 PM - edited 07-31-2012 12:39 PM
Re: Proliant Microserver N40L: Remote Access Card is buggy and lacks GPL source
Have 2 of them in 2 N36L servers.
No matter what I do I can access the card only for few hours, after which IP (DHCP or Static) is no more accessible.
Even reboot of the server itself does not help (I would need to pull the plug)
They are just USELESS!
Seb