NMServer for Stratus VOS Frequently Asked Questions (FAQ)
@1. When I try to bring up
snmpd.pm, it fails and the .out file says that
there is an error of "host
unknown".
@2. When I try to start snmpd.pm, it fails with the error "bind: Not enough
access to perform operation".
@3. How do I change the NMServer License Key?
@4.
The NMServer agent is up and running but doesn't respond to my SNMP manager.
@5. My SNMP manager isn't getting any traps.
@6. The monitor_log process won't run and reports "You have a bad
license key."
@1. When I try to bring up snmpd.pm, it fails and the .out file says that
there is an error of "host unknown".
You do not have the Stratus configured for tcp_os correctly. Display
>system>tcp_os>hosts to see what names and IP addresses you have defined;
you should see entries such as:
166.37.27.103 abc1 # (development)
166.34.100.237 abc2 # (production)
Next, type in the following command line (you must be privileged):
sethost -form
The response is:
-device: %abc1#tcp_m1
-hostname: xyz
-hostid: 0
You will see what your host name is on the -hostname line; in this
example, no name in the hosts table matches xyz. If it is blank or there is no name that matches in >system>tcp_os>hosts, you must assign a name
that is in the hosts file. After you change the name with the sethost command or edit the hosts table to match the current -hostname value,
restart snmpd. The Agent should not fail with this error again.
@2. When
I try to start snmpd.pm, it fails with the error "bind: Not enough access
to perform operation".
The snmpd process uses UDP port 161, the
well-known port for SNMP agents. On recent versions of VOS, a process must
be started as privileged to have access to one of the well-known ports (ports
numbered 1024 or less). In order to start snmpd, you must do one of the
following:
- Start the snmpd process with the command
"start_process snmpd -privileged"
- Disable the requirement for privileged access
to all well-known ports by using analyze_system to set the External variable
allow_unpriv_bind$. Consult VOS documentation for further information.
@3.
How do I change the NMServer License Key?
Two changes are necessary to update the NMServer
for VOS license key.
- COMTEK will provide you with a new mib.conf
file, replace the existing mib.conf file with the new file.
- COMTEK will also provide you with a new
license key; the license key is a required parameter when starting the
monitor_log utility. Generally, command macros (.cm files) are used to
launch monitor_log so you should update all .cm files that you have created
for monitor_log so that they include the new license key.
@4.
The NMServer agent is up and running but doesn't respond to my SNMP manager.
- Examine the snmpd.communities
file. Verify that the IP address listed in
this file is the correct IP address for your SNMP manager.
- Make sure that the
community string that you have placed in the snmpd.communities
file
is the community string that your SNMP manager is using for
gets/sets. If you want to allow your manager to do SNMP gets and
SNMP sets, you may need to make 2 entries in the snmpd.communities
file, one entry for the get community string with the access of read
and another entry for the set community string with the access of
write.
- If you have made any
changes to the snmpd.communities
file, you must stop and restart the agent for the change to take effect.
- Verify that your SNMP
manager is configured to send SNMP requests to this system on the
correct port. The agent listens for requests on UDP
port 161; by default, SNMP managers send their requests to
port 161.
- Use the VOS PING command to make sure that you have connectivity
between the VOS system and the SNMP manager system.
- Use the VOS packet_monitor command to verify that SNMP requests are being
received on the correct port. Note: packet_monitor incurs
substantial system overhead and isn't guaranteed to catch all
packets, use this command with care.
- Use a TCP trace
facility on your SNMP manager system to verify that SNMP responses
are received by your SNMP manager's system.
- Verify that UDP ports
161 and 162 are not being blocked by a router of firewall within
your network.
- Make sure that you are
not getting Authentication Failure traps from NMServer every time
you make an SNMP request. Authentication Failures indicate
that the community information for the SNMP manager is not valid.
@5. My SNMP manager isn't getting any traps.
- Examine the snmpd.trap_comm
file. Verify that the IP address listed in
this file is the correct IP address for your SNMP
manager.
- Make sure that the
community string that you have placed in the snmpd.trap_comm
file
is valid for the SNMP manager (most SNMP managers do not validate
the community string that is put in a trap message).
- Verify that your SNMP
manager is listening for traps on the port you specified on the snmpd.trap_comm
file. UDP port 162 is the standard port for
the SNMP manager to use to receive traps.
- If you have made any
changes to the snmpd.trap_comm file, you must stop and restart
NMServer for the change to take effect.
- Use the VOS PING command to make sure that you have connectivity
between the VOS system and the SNMP manager system.
- Use the VOS packet_monitor command to verify that traps are being sent out
on the correct port. Note: packet_monitor incurs substantial
system overhead and isn't guaranteed to catch all packets, use this
command with care.
- Use a TCP trace
facility on your SNMP manager system to verify that traps are being
received on the correct port.
- Verify that UDP ports
161 and 162 are not being blocked by a router of firewall within
your network.
- Make sure that your
SNMP manager is listening for traps on the specified port (usually
port 162). Another trap receiving process may be enabled that
is locking port 162 preventing your SNMP manager from receiving
traps.
@6.
The monitor_log process won't run and reports "You have a bad
license key."
Use the VOS command validate_hub to verify
that the Site_id has been set. Monitor_log uses the Site_id as the
system name. Report this name when requesting a permanent license
key.
|
