01-08-2010
Quote:
Originally Posted by
pupp
just a thought here, what about downgrading the fw?
downgrading firmware esp on SUN x-series is a wrong move to make. The newer the better.
Issue solved. Power cycled the system a few times.
Created IP,netmask , reset SP <all IP config will disappear again bcos the commitpending failed)
Again created IP,netmask and gateway, followed by commitpending and enabled state as the last command before reset SP.
ILOM got configured!
T-series, X-Series, though the iLOM technology are the same, the concept or method of configuring them always differs by some way, depending on the h/w arch model.. Really crazy SUN....!
10 More Discussions You Might Find Interesting
1. Solaris
Hi,
I ;ve a SUN x4600 running solaris 10. I want to connect to the system remotely form console like we can connect to sparc sc or alom .. (9 Replies)
Discussion started by: fugitive
9 Replies
2. 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
3. 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
4. Solaris
One of my X4600 server had a power loss and rebooted and now its giving me a strange problem servers internal disk controller naming has changed by itself ... the after failsafe boot md.conf file shows following c3txdx but shows internal disk at c4txdx ... what could be the reason for this and... (1 Reply)
Discussion started by: fugitive
1 Replies
5. 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
6. Solaris
Hi Folks,
Has anyone seen these errors on bootup.
Mar 15 12:22:30 svc.startd: svc:/system/device/local:default: Method "/lib/svc/method/devices-local" failed due to signal SEGV.ht (c) 1983, 2010,
Oracle and/or its affiliates. All rights reserved.
Configuring devices. ... (1 Reply)
Discussion started by: ESSTEAM
1 Replies
7. Hardware
Hi
I have a new SUN X4270 server. I am trying to login to the server's ILOM using it's serial management port from a Windows machine but am not getting any login prompt from the server.
I am using a RJ-45/DB-9 adaptor. After connecting the adaptor, I am opening the serial connection using... (3 Replies)
Discussion started by: mystition
3 Replies
8. Hardware
Booting and checking BIOS there is no option to enable-disable hyperthreading.
I have 8 Dual-Core AMD Opteron(tm) Processor 8220 and I see 16 cores.
Enable hyperthreading I should have 32 cores.
I have red hat 5.4 installed.
Anyone know how can enable hypethreading ? I have last BIOS/Firmware... (2 Replies)
Discussion started by: laxtnog
2 Replies
9. Hardware
Hi All,
I am having an Sun fire X4600 M2 server where one of the interfaces is down.
I had requested for the replacement but had a bit problem in identifying the port.
As per the server service module, there are 4 NIC ports and one port is not flashing (e1000g0) but as per server, the port... (8 Replies)
Discussion started by: Rockyc3400
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 DEBIAN
if_iwn
IWN(4) BSD Kernel Interfaces Manual IWN(4)
NAME
iwn -- Intel Wireless WiFi Link 4965/1000/5000/5150/5300/6000/6050 IEEE 802.11n driver
SYNOPSIS
To compile this driver into the kernel, include the following lines in your kernel configuration file:
device iwn
device pci
device wlan
device firmware
You also need to select a firmware for your device. Choose one from:
device iwn4965fw
device iwn1000fw
device iwn5000fw
device iwn5150fw
device iwn6000fw
device iwn6050fw
Or you can use
device iwnfw
to include them all.
Alternatively, to load the driver as a module at boot time, place the following lines in loader.conf(5):
if_iwn_load="YES"
iwn4965fw_load="YES"
iwn1000fw_load="YES"
iwn5000fw_load="YES"
iwn5150fw_load="YES"
iwn6000fw_load="YES"
iwn6050fw_load="YES"
DESCRIPTION
The iwn driver provides support for Intel Wireless WiFi Link 4965, 1000, 5000 and 6000 series of PCI-Express network adapters. iwn supports
station, adhoc, and monitor mode operation. Only one virtual interface may be configured at any time. For more information on configuring
this device, see ifconfig(8).
This driver requires the firmware built with the iwnfw module to work.
EXAMPLES
Join an existing BSS network (i.e., connect to an access point):
ifconfig wlan create wlandev iwn0 inet 192.168.0.20
netmask 0xffffff00
Join a specific BSS network with network name ``my_net'':
ifconfig wlan create wlandev iwn0 ssid my_net up
Join a specific BSS network with 64-bit WEP encryption:
ifconfig wlan create wlandev iwn0 ssid my_net
wepmode on wepkey 0x1234567890 weptxkey 1 up
Join a specific BSS network with 128-bit WEP encryption:
ifconfig wlan create wlandev iwn0 wlanmode adhoc ssid my_net
wepmode on wepkey 0x01020304050607080910111213 weptxkey 1
DIAGNOSTICS
iwn%d: device timeout The driver will reset the hardware. This should not happen.
iwn%d: firmware error The onboard microcontroller crashed for some reason. The driver will reset the hardware. This should not happen.
iwn%d: timeout waiting for firmware initialization to complete The onboard microcontroller failed to initialize in time. This should not
happen.
iwn%d: could not load firmware image '%s' The driver failed to load the firmware image using the firmware(9) subsystem. Verify the iwnfw(4)
firmware module is present.
iwn%d: could not load boot firmware An attempt to upload the boot firmware image to the onboard microcontroller failed. This should not
happen.
iwn%d: could not load microcode An attempt to upload the microcode image to the onboard microcontroller failed. This should not happen.
iwn%d: could not load main firmware An attempt to upload the main firmware image to the onboard microcontroller failed. This should not
happen.
SEE ALSO
iwnfw(4), pci(4), wlan(4), wlan_ccmp(4), wlan_tkip(4), wlan_wep(4), ifconfig(8), wpa_supplicant(8)
AUTHORS
The original iwn driver was written by Damien Bergamini <damien.bergamini@free.fr>
BSD
July 20, 2010 BSD