06-29-2005
/var/adm/messages
I'm running a Solaris 9 box with Oracle databases on it.
I'm getting the following messages in my /var/adm/messages log
"Jun 24 12:30:32 sundb01 bootpd[3260]: [ID 872878 daemon.notice] IP address not found: xxx.xxx.xxx.xxx"
...where xxx.xxx.xxx.xxx is DHCP IP addresses of Windows 2000 workstations in the organisation. The workstations are getting the addresses from a Novell DHCP server.
Does anyone know why I'm getting these messages?
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Just want to check with all of you out there what does the following warning means in my "messages" file in /var/adm
the warning is Prevous Time Adjustment Incomplete , does it mean my hard ware is faulty if so which piece of hardware it is ? (1 Reply)
Discussion started by: owls
1 Replies
2. Solaris
Solaris 8/ sun 420R
Checked /var/adm/messages file and got the following message:
Dec 4 16:40:05 serverXYZ ConfigProvider: get_pkg_instdate: getdate failed for the standard C locale (7)
Does anyone know what this means? Looked up getdate but do not understand....
Thanks. (1 Reply)
Discussion started by: finster
1 Replies
3. UNIX for Dummies Questions & Answers
Hi,
No log entry is found in messages files. The file size is 0. We are using Solaris 9. Anyone knows what could be wrong. (3 Replies)
Discussion started by: FrankC
3 Replies
4. Solaris
Hello Friends,
I am geting the folowing error in /var/adm/message is it disl related problem?
if yes.. how to check all the disk are perfect or not?
Sep 15 06:01:12 scsi: WARNING: /pci@1f,700000/scsi@2/sd@2,0 (sd7):
Sep 15 06:01:12 Error for Command: write(10) Error Level:... (5 Replies)
Discussion started by: bullz26
5 Replies
5. Solaris
Hi all,
where I can find a list and meaning of the ID number (for example ID 353554 kern.warning)?
Thanks in advance
Pierluigi (1 Reply)
Discussion started by: Petrucci
1 Replies
6. Solaris
Check message file and result posted below.
Can anyone tell me what this is a sign of, what does it mean?
server1% more messages.0
Dec 02 09:35:06 server1 bsd-gw: Inval
id protocol request (65): AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA^\\2... (6 Replies)
Discussion started by: finster
6 Replies
7. Solaris
hi sirs
can u tell the difference between /var/log/syslogs and /var/adm/messages
in my working place i am having two servers.
in one servers messages file is empty and syslog file is going on increasing..
and in another servers message file is going on increasing but syslog file is... (2 Replies)
Discussion started by: tv.praveenkumar
2 Replies
8. UNIX for Advanced & Expert Users
The /var/adm/messages in Solaris seem to log more system messages/errors compared to /var/log/messages in Linux.
I checked the log level in Linux and they seem OK.
Is there any other log file that contains the messages or is it just that Linux doesn't log great many things? (2 Replies)
Discussion started by: gomes1333
2 Replies
9. Shell Programming and Scripting
grep \"^`date "+%b %d %T"`\" /var/adm/messages | egrep \"emerg|alert|crit|err|warning\
but get an output like this
ksh: alert: not found
ksh: crit: not found
ksh: err: not found
ksh: warning": not found
grep: can't open "19"
grep: can't open "16:27:16"" (1 Reply)
Discussion started by: arch12
1 Replies
10. Solaris
Hi,
Is the contents in /var/log/syslog and /var/adm/messages are same??
Regards (3 Replies)
Discussion started by: vks47
3 Replies
AGR(4) BSD Kernel Interfaces Manual AGR(4)
NAME
agr -- link aggregation pseudo network interface driver
SYNOPSIS
pseudo-device agr
DESCRIPTION
The agr driver provides link aggregation functionality (a.k.a. L2 trunking or bonding).
It supports the IEEE 802.3ad Link Aggregation Control Protocol (LACP) and the Marker Protocol.
The agr driver supports the following link specific flags for ifconfig(8):
link0 Use the round-robin distribution algorithm. Don't use it unless you're really sure, because it violates the frame ordering rule.
-link0 Use the default distribution algorithm, which is based on the hash of DA/SA, TCI, and, if available, some upper layer protocol infor-
mation like ip(4) DA/SA.
link1 Disable LACP. Prevents any LACP or Marker messaging which leaves the ports in the default static configuration. Set this prior to
adding ports.
EXAMPLES
Create an agr interface, agr0, and attach re0 and re1 to it. In other words, aggregate re0 and re1 so that they can be used as a single
interface, agr0. The physical interfaces which are attached to the agr interface must not have any IP addresses, neither IPv4 nor IPv6.
ifconfig re0 inet xxx.xxx.xxx.xxx delete
ifconfig re0 inet6 fe80::xxxx:xxxx:xxxx:xxxx delete
ifconfig re1 inet xxx.xxx.xxx.xxx delete
ifconfig re1 inet6 fe80::xxxx:xxxx:xxxx:xxxx delete
ifconfig agr0 create
ifconfig agr0 agrport re0
ifconfig agr0 agrport re1
Destroy an interface created in the above example.
ifconfig agr0 -agrport re0
ifconfig agr0 -agrport re1
ifconfig agr0 destroy
SEE ALSO
ifconfig(8)
STANDARDS
IEEE 802.3ad Aggregation of Multiple Link Segments
HISTORY
The agr driver first appeared in NetBSD 4.0.
AUTHORS
The agr driver was written by YAMAMOTO Takashi.
BUGS
There is no way to configure LACP administrative variables, including system and port priorities. The current implementation of the agr
driver always performs active-mode LACP and uses 0x8000 as system and port priorities.
The agr driver uses the MAC address of the first-added physical interface as the MAC address of the agr interface itself. Thus, removing the
physical interface and using it for another purpose can result in non-unique MAC addresses.
The current implementation of the agr driver doesn't prevent unsafe operations like some ioctls against underlying physical interfaces. Such
operations can result in unexpected behaviors, and are strongly discouraged.
There is no way to configure agr interfaces without attaching physical interfaces.
Physical interfaces being added to the agr interface shouldn't have any addresses except for link level address. Otherwise, the attempt will
fail with EBUSY. Note that it includes an automatically assigned IPv6 link-local address.
BSD
February 23, 2010 BSD