Sponsored Content
Full Discussion: Network lost after reboot
Operating Systems SCO Network lost after reboot Post 302128186 by DickTutton on Monday 23rd of July 2007 09:25:06 AM
Old 07-23-2007
yes .. the NIC is always picked up by the CMOS.

The NIC is being seen by the OS as if I unplug it from the switch I get the eeE Lost Link message on the console .. I just cannot get it to talk to the network.

As I say the worrying thing to me is that running netcfg

a) takes a long time to pick up settings
b) when it does come back I cannot see all the options (greyed out) in particular, modify the settings
c) once in netcfg, I cannot then exit .. it justs stays within the menu system.

Again very strange that I can restore the system from a known working date but still cannot get the network running!!!
 

7 More Discussions You Might Find Interesting

1. Solaris

Network Connectivity lost after reboot

I have 4 V440 servers running Solaris 9. I have their interfaces configured (ce0) and have connectivity to our network. However, after reboot,...the connectivity is lost although the interface shows that its still up after an ifconfig -a. Only after I reconfigure the interface do I restore... (19 Replies)
Discussion started by: StorageGuy
19 Replies

2. Solaris

[help]network error after reboot server v890 sparc

hi expert, i had reinstall the sun v890 server solaris 8 and also do mirroring, i had configure the network for the server (hostname.eri0,hosts,netmasks,nodename,etc) after i reboot get and error messages below : Setting default IPv4 interface for multicast: add net 224.0/4: gateway... (5 Replies)
Discussion started by: bucci
5 Replies

3. AIX

tuning network parameters : parameters not persist after reboot

Hello, On Aix 5.2, we changed the parameters tcp_keepinit, tcp_keepintvl and tcp_keepidle with the no command. tunrestore -R is present in inittab in the directory /etc/tunables we can clearly see the inclusion of parameters during reboot, including the file lastboot.log ... (0 Replies)
Discussion started by: dantares
0 Replies

4. SuSE

reboot and boot from network

Hello, Does any one know any command which reboot the system and select as boot device the network. I give bootnet to many servers at once and i want to avoid opening ILOM and select as boot device the network. Can i do it by just executing a command? Thanks in advance (2 Replies)
Discussion started by: @dagio
2 Replies

5. UNIX for Dummies Questions & Answers

Will authconfig make permanent change or lost after reboot?

Hi, I made following configuration to create user directory: # authconfig --enablemkhomedir --update But the directory is created as permission 755, I'd like to modify the script to change directory access permission to 700, where is the script which copies /etc/skel to /home... (0 Replies)
Discussion started by: hce
0 Replies

6. IP Networking

Finding lost machine on network trouble

Couldn't find my PC on network. Root of evil the was in bad patch-cable. (0 Replies)
Discussion started by: useretail
0 Replies

7. Solaris

Changing "rx_queue_number" in "ixgbe.conf". Reboot or Network Restart?

Hi all, First post here. Working on Solaris 10, on a Sun t4-4, need to change RX queue depth(ethernet, not HBA) and was wondering if i could get by with just restarting the network or if i should just bounce the whole shebang. Apologies if i missed a similar thread. if there is one, please... (2 Replies)
Discussion started by: caspnx
2 Replies
AN(4)							   BSD Kernel Interfaces Manual 						     AN(4)

NAME
an -- Aironet Communications 4500/4800 wireless network adapter driver SYNOPSIS
To compile this driver into the kernel, place the following lines in your kernel configuration file: device an device wlan Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): if_an_load="YES" DESCRIPTION
The an driver provides support for Aironet Communications 4500 and 4800 wireless network adapters and variants, including the following: o Aironet Communications 4500 and 4800 series o Cisco Aironet 340 and 350 series o Xircom Wireless Ethernet Adapter Support for these devices include the ISA, PCI and PCMCIA varieties. The Aironet 4500 series adapters operate at 1 and 2Mbps while the Aironet 4800 series and Cisco adapters can operate at 1, 2, 5.5 and 11Mbps. The ISA, PCI and PCMCIA devices are all based on the same core PCMCIA modules and all have the same programming interface, however unlike the Lucent WaveLAN/IEEE cards, the ISA and PCI cards appear to the host as normal ISA and PCI devices and do not require any PCCARD support. The PCMCIA Aironet cards require PC Card support, including the kernel pccard(4) driver. ISA cards can either be configured to use ISA Plug and Play or to use a particular I/O address and IRQ by properly setting the DIP switches on the board. (The default switch setting is for Plug and Play.) The an driver has Plug and Play support and will work in either configuration, however when using a hard-wired I/O address and IRQ, the driver configuration and the NIC's switch settings must agree. PCI cards require no switch settings of any kind and will be automatically probed and attached. All host/device interaction with the Aironet cards is via programmed I/O. The Aironet devices support 802.11 and 802.3 frames, power manage- ment, BSS (infrastructure) and IBSS (ad-hoc) operation modes. The an driver encapsulates all IP and ARP traffic as 802.11 frames, however it can receive either 802.11 or 802.3 frames. Transmit speed is selectable between 1Mbps, 2Mbps, 5.5Mbps, 11Mbps or "auto" (the NIC automati- cally chooses the best speed). By default, the an driver configures the Aironet card for infrastructure operation. For more information on configuring this device, see ifconfig(8). DIAGNOSTICS
an%d: init failed The Aironet card failed to become ready after an initialization command was issued. an%d: failed to allocate %d bytes on NIC The driver was unable to allocate memory for transmit frames in the NIC's on-board RAM. an%d: device timeout The Aironet card failed to generate an interrupt to acknowledge a transmit command. SEE ALSO
altq(4), arp(4), miibus(4), netintro(4), wlan(4), ancontrol(8), ifconfig(8) HISTORY
The an device driver first appeared in FreeBSD 4.0. AUTHORS
The an driver was written by Bill Paul <wpaul@ee.columbia.edu>. BSD
July 16, 2005 BSD
All times are GMT -4. The time now is 04:51 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy