12-26-2002
Quote:
Originally posted by shibz
-- The link status gives correct information provided the interface is plumbed and up.---
Is this correct ?.. Or is there any other way to get the correct link_status.
I can't believe that the interface needs to be plumbed for the link status to be correct. "Plumbed" means tcp/ip stack installed. The ethernet driver does not require tcp/ip. Your veritas heartbeat should work fine without the etherface being plumbed.
Are you setting the instance?
ndd -set /dev/hme instance 1
ndd -get /dev/hme link_status
is needed to get the link status of hme1.
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. Solaris
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: IP address not found: xxx.xxx.xxx.xxx"
...where xxx.xxx.xxx.xxx is DHCP IP addresses of Windows 2000 workstations in the organisation. ... (2 Replies)
Discussion started by: soliberus
2 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
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
6. 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
7. 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
8. 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
9. Solaris
Hi,
Is the contents in /var/log/syslog and /var/adm/messages are same??
Regards (3 Replies)
Discussion started by: vks47
3 Replies
10. UNIX for Advanced & Expert Users
The /var/log/messages folder grows exponentially - in 3 hours it went up from 70 K to 6GB.
I have an application and it keeps writing such logs at very high speed.
Which of the following feature has to be disabled?
The entry in syslog.config is shown below
... (1 Reply)
Discussion started by: nathan_nathan
1 Replies
ndd(1M) System Administration Commands ndd(1M)
NAME
ndd - get and set driver configuration parameters
SYNOPSIS
ndd [-set] driver parameter [value]
DESCRIPTION
ndd gets and sets selected configuration parameters in some kernel drivers. Currently, ndd only supports the drivers that implement the
TCP/IP Internet protocol family. Each driver chooses which parameters to make visible using ndd. Since these parameters are usually
tightly coupled to the implementation, they are likely to change from release to release. Some parameters may be read-only.
If the -set option is omitted, ndd queries the named driver, retrieves the value associated with the specified parameter, and prints it. If
the -set option is given, ndd passes value, which must be specified, down to the named driver which assigns it to the named parameter.
By convention, drivers that support ndd also support a special read-only parameter named ``?'' which can be used to list the parameters
supported by the driver.
EXAMPLES
Example 1: Getting Parameters Supported By The TCP Driver
To see which parameters are supported by the TCP driver, use the following command:
example% ndd /dev/tcp ?
The parameter name ``?'' may need to be escaped with a backslash to prevent its being interpreted as a shell meta character.
The following command sets the value of the parameter ip_forwarding in the dual stack IP driver to zero. This disables IPv4 packet forward-
ing.
example% ndd -set /dev/ip ip_forwarding 0
Similarly, in order to disable IPv6 packet forwarding, the value of parameter ip6_forwarding
example% ndd -set /dev/ip ip6_forwarding 0
To view the current IPv4 forwarding table, use the following command:
example% ndd /dev/ip ipv4_ire_status
To view the current IPv6 forwarding table, use the following command:
example% ndd /dev/ip ipv6_ire_status
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO
nca(1), ioctl(2), attributes(5), arp(7P), ip(7P), ip6(7P), tcp(7P), udp(7P)
NOTES
The parameters supported by each driver may change from release to release. Like programs that read /dev/kmem, user programs or shell
scripts that execute ndd should be prepared for parameter names to change.
The ioctl() command that ndd uses to communicate with drivers is likely to change in a future release. User programs should avoid making
dependencies on it.
The meanings of many ndd parameters make sense only if you understand how the driver is implemented.
SunOS 5.10 8 Nov 1999 ndd(1M)