Search results for query: *

The general answer to "why" dou you need to reboot is that it gets the system back to a known "state". This is true of any computer-based system. Every piece of software has bugs. We hope that the worst and the the most common are found and fixed, but there are always bugs lurking in the...

There are lots of trap receiver systems that run on lots of OSs. Some trap receivers can only handle a restricted set of traps, others can be configured to accept traps from any old system. While one could set up a trap receiver on an 8730, you should not - it might overload the system. My...

1. I'd log in with your "best" login and repeat the entire process, just in case it was a transient problem 2. If that does not work, see if you can rename the "conf" file and then create a new one with better permissions: mv /etc/snmp/snmpd.cnf /etc/snmp/snmpd.cnf.old cp...

As I remember, email is not on the CM system. (All for the best, email is ugly to set up). There are various ways to cause email to be sent, but you always need another system to actually send the email. Personally, I'd set up SNMP on the CM and see if I could use net-snmp (on either a windows...

You don't need to mess with "IP Addresses for IP access" unless you are going to query (or update) the server. I assume you just want to receive traps. I'd guess that you forgot to bring the "Master Agent" down and back up. Go to "Agent Status" on the Web page and cycle the Master Agent down...

I'd bet one of the new routers is dropping the NTP packets. NTP is a UDP protocol. Ping uses ICMP, so pinging does not prove that the "new" router(s) will pass NTP packets. Go to shell on the CM and type this: nmap -sU -p123 "IP_address_or_name_of_NTP_server" (I think nmap is on the CM...

1. As I remember, ssh has the ability to cache passwords. I believe it can be set up to go password-less or to require a LOCAL passphrase instead of the remote password. 2. The Expect system allows one to automate logging in - but that blows all security steve

Try using tcpdump or tethereal on the s8730 to check out the packets to see if they are reaching the system. Also look in /var/log for ntp-related messages. steve

I would note that it is a function of how those phones will be used (call center?), the geographic distribution, networking, etc. If this is a school project, then S87xx is a good answer. If your continued employment rests on the answer, I'd suggest you talk to Avaya. steve

Several folks have lamented that jaymzworld is now password protected. If you want copies of any of the documents that were on jaymzworld, just look in the Internet Archive http://www.archive.org/index.php. It takes a bit of fiddling around, but the entire site has been archived. steve

look here: http://www.tek-tips.com/viewthread.cfm?qid=1456215

type "stty echo" steve

Try this: cd /var/tmp chmod 777 conf_queue # make file usable by all now retry the config if it still fails, try this: mv conf_queue conf_queue.old # rename the file Now retry the configure - if it works, be happy - if it does not work, do this: mv conf_queue.old conf_queue # move the...

/var/tmp is a directory where temporary files go. So conf_queue should be a temporary file. If you can get to "shell" (bash) commandline, try these: cd /var/tmp # did this work? date > junkfile # did this work? rm junkfile # remove the test file ls -ld /var/tmp # permissions should...

If it has an IP address, it can be pinged & "seen" via many tcp/ip functions (like umap or SNMP - if it is administered). If it does not have an IP address, I think MAC addresses are only useful within the same sub-net. steve

I think you need to add more specifics. What hardware & software are you running, how heavy a load is on the system (one way to get the load is this bash-level command: top -n1). Also what are your plans, needs & concerns? - Are you going to do this overnight or during the work day? - How many...

Sounds like a SAT bug to me. Maybe someone should report it to Avaya. OK, here are some alternative ways to try to solve the problem: 1. do not "go shell". Use a login that starts at bash and then you can start SAT manually, if necessary. This will almost undoubtedly solve the buffering...

1. try "stty sane" #(I don't expect it to help, but it is easy) 2. It sounds like you are in "line buffered" mode. Are you logging in directly to the Bash shell, are you doing a "go shell" in ASA, or are you starting bash (shell) in some other way? steve

OK, Note the "-echo" in the "stty -g" output. This is your problem. Just type "stty echo" and you will be happy - at least until you login next time. If the problem returns next time you login, you might look at your ".bashrc" and/or ".bash_profile" files to see if there is a "stty -echo" in...

Whoops, my blunder. use stty -a not stty -g steve