12-17-2009
You may want to double check that nothing in /etc/default/snmpd is over-riding your configuration. I think by default, the local loopback address (127.0.0.1) is passed in the SNMPDOPTS directive.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
I am doing this perl script
print (@line(1..15));
the lines 1 to 15 get printed...
how can i redirect this to file?
thanks and regards
vivek.s (4 Replies)
Discussion started by: vivekshankar
4 Replies
2. Solaris
Hi
I am getting the uptime output as follows
12:40am up 4 day(s), 18:29, 2 users, load average: 38.97, 36.54, 34.89
The load average is too high .
I have checked the processes , but no process is taking too much cpu time
Please help (3 Replies)
Discussion started by: guy009
3 Replies
3. Solaris
i am using this way to create zone1 and zone2
bash-2.05b# zonecfg -z zone1
zone1: No such zone configured
Use 'create' to begin configuring a new zone.
zonecfg:zone1> create
zonecfg:zone1> set zonepath=/zone/1
zonecfg:zone1> set autoboot=true
zonecfg:zone1> add net
zonecfg:zone1:net>... (6 Replies)
Discussion started by: coxmanchester
6 Replies
4. Shell Programming and Scripting
can u plz tell me where is the error
echo enter the filename to be searched
read fname
if #-d $fname
then
echo file exists
if
then
echo itsa directory
elif
then
echo its readable
cat $fname
else
echo its not readable
fi
else
... (1 Reply)
Discussion started by: gotam
1 Replies
5. Infrastructure Monitoring
I am trying to enabling SNMP access and trap forwarding for Linux(RHEL5) using following official url from IBM.
http://publib.boulder.ibm.com/infocenter/eserver/v1r2/index.jsp?topic=/diricinfo/fqm0_t_enabling_snmp_access_and_trap_forwarding_for_linux.html
In my system, snmp and snmplibs are... (1 Reply)
Discussion started by: SiddhV
1 Replies
6. Shell Programming and Scripting
Hi,
I have a logrotate configuration which rotates a log every night 1 min before midnight, but somehow its not working and unfortunately not showing any error message as well. Sharing the code for the cron job as well as the conf file, I am using, if some one coule help me..whats wrong with... (2 Replies)
Discussion started by: Neeryan
2 Replies
7. AIX
Hi,
I am able to login using su - or su directly ,
# prompt is coming, it doesnt ask for password.
any normal user on aix system is login using su - or su .
Please suggest where to change the configuration
direct root login is disabled in /etc/ssh/sshd_config file. (0 Replies)
Discussion started by: manoj.solaris
0 Replies
8. IP Networking
I am having a problem with an SNMP event, and I am not sure where I should be looking to solve this problem.
Description:
There is an SNMP event in our system that for one reason or another is not getting sent out as an email because it is never getting to our SNMP agent.
I see where the... (0 Replies)
Discussion started by: broberts
0 Replies
9. Solaris
I am trying to configure central syslog server
On hostA, in /etc/syslog.conf file,I am adding below line*.err;kern.debug;daemon.notice;mail.crit @hostB
then I am restarting syslog servicesvcadm restart /system/system-log
In hostA, I have already added hostB entry in /etc/hosts... (5 Replies)
Discussion started by: amity
5 Replies
10. SuSE
Please let me know how to configure network in suse Linux, I have configured the network using ifup and network manager, it is not giving any error but not working,
using suse Linux 11.0 sp3
I have checked network connectivity is working. (0 Replies)
Discussion started by: manoj.solaris
0 Replies
LO(4) BSD Kernel Interfaces Manual LO(4)
NAME
lo -- software loopback network interface
SYNOPSIS
pseudo-device
loop
DESCRIPTION
The loop interface is a software loopback mechanism which may be used for performance analysis, software testing, and/or local communication.
As with other network interfaces, the loopback interface must have network addresses assigned for each address family with which it is to be
used. These addresses may be set or changed with the SIOCSIFADDR ioctl(2). The loopback interface should be the last interface configured,
as protocols may use the order of configuration as an indication of priority. The loopback should never be configured first unless no hard-
ware interfaces exist.
DIAGNOSTICS
lo%d: can't handle af%d. The interface was handed a message with addresses formatted in an unsuitable address family; the packet was
dropped.
SEE ALSO
inet(4), intro(4), ns(4)
HISTORY
The lo device appeared in 4.2BSD.
BUGS
Previous versions of the system enabled the loopback interface automatically, using a nonstandard Internet address (127.1). Use of that
address is now discouraged; a reserved host address for the local network should be used instead.
4.2 Berkeley Distribution June 5, 1993 4.2 Berkeley Distribution