ifconfig: bad address

Cause

System fails to boot with this error message: ifconfig: bad address. When
coming up to multi-user ifconfig -a, it indicates the following:

le0: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500
inet 0.0.0.0 netmask 0

Once up, if this command succeeds, then all is well:

# ifconfig le0 inet hostname

Action

Check /etc/hostname.* for a possible bad entry.
/etc/hosts was linked to /var/named/hosts and /var was a separate file
system. Until system comes up in multi-user to mount /var, host name could not be
resolved to proper IP address.

ifconfig bad address le0

Cause

The user installed the recommended 2.5.1 patches. When booting, rootuser.sh
presented the following errors:

ifconfig bad address le0
le0 arp - revarp failed no rarp replies
bad address hme0
hme0 auto-revarp failed: no rarp replies received.

The IP address of interface is set to 0.0.0.0.

System fails to resolve host IP address from /etc/host and no other RARP servers
responded to the system’s request for its IP address.

Action

If dns [NOTFOUND=return] appears before files in /etc/nsswitch.conf,
ifconfig complains at boot-time about bad address. In some cases this can cause
the boot to fail.

ifconfig: host name bad space address

Cause

When the system is booted, this error message is displayed. The
/etc/nsswitch.conf file had the following entries for the hosts line:

hosts: dns nis [NOTFOUND=return] files

Action

Move files to the first entry in the list. Now, when the system boots, it resolves the
interface names from the /etc/hosts file.

ifconfig: SIOCGIFFLAGS: hme0: no such interface

Cause

If you just installed hme interface and are now manually configuring it, you could
receive this error message when running the following:

ifconfig hme0 inet ipaddr netmask + broadcast + -trailers up

Action

If there is no hostname.hme0 file, then the startup scripts do not execute the
ifconfig hme0 plumb command. The user can either create the hostname.hme0 file
or issue the ifconfig hme0 plumb command manually before attempting to
configure the interface.

Comments

Post a Comment

Popular posts from this blog

Understanding How ZFS Calculates Used Space

This document explains how ZFS calculates the amount of used space within a zpool and provides examples of how various ZFS features affect that calculation. DETAILS A ZFS storage pool is a logical collection of devices that provide space for datasets such as filesystems, snapshots and volumes. A zfs pool can be used as a filesystem, i.e. such as mounting/unmounting; to take snapshots that provides read-only (clones are writable copies of snapshots) copies of the filesystem taken in the past; to create volumes that can be accessed as a raw and a block device and for setting properties on datasets. Interaction of all these datasets and associated properties such as quotas, reservations, compression and deduplication (Solaris 11 only) play a role in how ZFS calculates space usage. Neither the du nor df command have been updated to account for ZFS file system space usage. When calculating zfs space usage, always use the following command. # zfs list -r -o space <pool_name...
Read more

How To Verify Remote System Controller (RSC) is Configured and Current on Sun Fire[TM] 280R/V480/V490/V880/V890 servers

Steps to Follow: How To Verify Remote System Controller(RSC) is Configured and Current 1.Check to see if the RSC software is already installed. # /usr/bin/pkginfo | grep SUNWrsc 2.If the software is installed the command should output the package name and info.   The version of the package installed in Solaris should match the version of firmware installed on the card.   `rscadm version` in Solaris will display the firmware version. 3.If the software is not installed the packages can be found on the supplemental CD that came with the Solaris Operating Environment. If you do not have the CD the software can be downloaded from MOS: RSC 2.2.2 is supported with Solaris 10, but you need to get this from a supplemental CD (for Solaris 9, since there is no supplemental CD for S10). The packages for Solaris 8 and 9 (and later) are both in the zip file. There are two options of the zip file, 32bit, and 64bit, but they both have the same checksums, so there are...
Read more

Restart autosys agent

#/etc/init.d/uajm_agent stop CA-UAJM Agent stopped. #/etc/init.d/uajm_agent start CA-UAJM Agent started. Follow the below workaround if the autosys agent does not start. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1.Run the command to check the status of both process, auto_remote and csampmuxf # ps -ef|grep 'auto'     root 14712     1  0   Aug 27 ?        2:42 auto_remote     root 27652     1  0 13:00:22 ?        0:00 auto_remote     root 27782     1  0 13:00:40 ?        0:00 auto_remote     root 29066 24480  0 13:01:07 pts/7    0:00 grep auto 2.There should be two entries for /opt/CA/SharedComponents/Csam/SockAdapter/bin/csampmux status . If you see one entry then stop agent and check the autore...
Read more