08-13-2014
10 More Discussions You Might Find Interesting
1. Solaris
Hi
I received a Sun server and want to know whether the ILOM will allow me to install Solaris on the server.
I was able to access the ILOM (ssh and serial and web). But will it allow me to install Solaris on it?
thx (11 Replies)
Discussion started by: melanie_pfefer
11 Replies
2. Solaris
HI,
Is it possible to set up ILOM from the ethernet terminal. I 'm at remote location from server so would like to know if i can configure it remotely
I'm able to access my server via ssh terminal. (3 Replies)
Discussion started by: fugitive
3 Replies
3. Solaris
I 've 2 different T5220 and both are showing different prompts when i ssh to the console.
1. Shows sc> ALOM
2. Shows -> ILOM
as far as i know the T5220 comes with ILOM , so why i 'm seeing 2 different type of console for same tyep of hardware ?
and i found that we... (6 Replies)
Discussion started by: fugitive
6 Replies
4. Solaris
I bought a new Netra X4450 and this is my first time experience with intel based Sun server. I powered on the machine and went through the Sun wizard to complete OS configuration. Now I am on the root prompt and trying to get to the ILOM. On Sparc based servers I used to be able to go to the ILOM... (4 Replies)
Discussion started by: StarSol
4 Replies
5. Solaris
hi guys
How to know ILOM and ALOM ip address.
how to find the ilom alerts and alom alerts can one help out pls
thanks,
deepu.
---------- Post updated at 04:39 AM ---------- Previous update was at 04:38 AM ---------- (2 Replies)
Discussion started by: pradeepaasuri
2 Replies
6. Solaris
Hi,
I am just confused with iLOM. Is iLOM is applicable for SPARC as well as X86 servers?? which are having CMM. Hope ALOM will be applicable for rest of the servers like v240 kind of series.
Can any one pls clarify this??
Thanks in Advance
Vaisakh K S (3 Replies)
Discussion started by: vks47
3 Replies
7. Solaris
Hi,
Can you pls. provide me detailed procedure on how to update system BIOS and ILOM Firmware for x4100 M2 servers.
Thanks. :) (1 Reply)
Discussion started by: chozie
1 Replies
8. Hardware
Hello,
I have an x86 server with an ILOM connection that produces strange characters when I perform a start /SP/console, see below:
Oracle(R) Integrated Lights Out Manager
Version 3.0.16.10.a r68533
Copyright (c) 2011, Oracle and/or its affiliates. All rights reserved.
-> start... (9 Replies)
Discussion started by: kerrygold
9 Replies
9. Solaris
While trying to perform a firmware upgrade on this ilom, the system refused to allow uploading of more than ~900k or so... We tried multiple approaches using FTP and all failed. I decided to start this morning by firing up Apache on another box and trying the same process via HTTP but when I went... (8 Replies)
Discussion started by: DustinT
8 Replies
10. Solaris
Dear all
would you tell me the command in ILOM to :
- Check for error logged in ILOM ouput
- Check for system uptime (DAYS)
- Check for system reboot logged (Last system reboot)
Thank you (1 Reply)
Discussion started by: gema.utama
1 Replies
LEARN ABOUT NETBSD
firmware_get_size
FIRMLOAD(9) BSD Kernel Developer's Manual FIRMLOAD(9)
NAME
firmload -- Firmware loader API for device drivers
SYNOPSIS
#include <dev/firmload.h>
int
firmware_open(const char *drvname, const char *imgname, firmware_handle_t *fhp);
int
firmware_close(firmware_handle_t fh);
off_t
firmware_get_size(firmware_handle_t fh);
int
firmware_read(firmware_handle_t fh, off_t offset, void *buf, size_t size);
void *
firmware_malloc(size_t size);
void
firmware_free(void *buf, size_t size);
DESCRIPTION
firmload provides a simple and convenient API for device drivers to load firmware images from files residing in the file system that are nec-
essary for the devices that they control. Firmware images reside in sub-directories, one for each driver, of a series of colon-separated
path prefixes specified by the sysctl variable hw.firmware.path.
FUNCTIONS
The following functions are provided by the firmload API:
firmware_open(drvname, imgname, fhp)
Open then firmware image imgname for the driver drvname. The path to the firmware image file is constructed by appending the string
``/drvname/imgname'' to each configured path prefix until opening the firmware image file succeeds. Upon success, firmware_open()
returns 0 and stores a firmware image handle in the location pointed to by fhp. Otherwise, an error code is returned to indicate the
reason for failure.
firmware_close(fh)
Close the firmware image file associated with the firmware handle fh. Returns 0 upon success or an error code to indicate the reason
for failure.
firmware_get_size(fh)
Returns the size of the image file associated with the firmware handle fh.
firmware_read(fh, offset, buf, size)
Reads from the image file associated with the firmware handle fh beginning at offset offset for length size. The firmware image data
is placed into the buffer specified by buf. Returns 0 upon success or an error code to indicate the reason for failure.
firmware_malloc(size)
Allocates a region of wired kernel memory of size size. Note: firmware_malloc() may block.
firmware_free(buf, size)
Frees a region of memory previously allocated by firmware_malloc().
SEE ALSO
autoconf(9), malloc(9), vnsubr(9)
HISTORY
The firmload framework first appeared in NetBSD 4.0.
AUTHORS
Jason Thorpe <thorpej@NetBSD.org>
BSD
January 17, 2006 BSD