RAD Data comm ASMI-450 Manual de usuario Pagina 34

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 166
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 33
Chapter 2 Installation RADview-HPOV/ATM User’s Manual
2-18 Frequently Asked Questions
2.6 Frequently Asked Questions
This section lists all RADview-HPOV for ATM FAQs relevant to installation
FAQ 1419
Question: Cannot zoom into agent, due to shared memory overflow.
Answer: This is a shared memory problem. It can be solved by running
/opt/MNG/MNGVIEWHP/bin/mng164_clear_shm
FAQ 1391
Question: Device is connected (ping from Terminal OK), but not reachable from
HPOV map.
Answer: While using host names as selection names, the /etc/hosts file is used
to correlate Host_name to IP, in order to enable communicating with
an SNMP agent. HPOV NNM is using a cache file, and does not
request the IP of the node from the host file on each polling, or
communication request. Thus, in case of modifications to the host file
(change of host's IP), they will not be reflected immediately in NNM.
To manually refresh HPOV's Host cashing, perform (as root)
/opt/OV/bin/xnmsnmpconf -optCache noIpAddr".
FAQ 1070
Question: Does RADview-HPOV include a built in Debug tool?
Answer: RADview HPOV includes a built in debug tool.
By setting the MNG164_DEBUG_LEVEL environment variable before
initiating HPOV, the user will get a report on the operations
performed by RADview-HPOV during the runtime.
The environment variable should be set in the same X-terminal
window from which RADview-HPOV is launched.
Example
:
While running csh:
1. Type: setenv MNG164_DEBUG_LEVEL 5
2. Type: script debug_data
The following message is displayed: "Script started, file is
debug_data".
3. Type: ovw &
The debug information is stored into the debug_data file,
and can be sent to RAD technical support for investigation.
Vista de pagina 33
1 2 ... 29 30 31 32 33 34 35 36 37 38 39 ... 165 166

Comentarios a estos manuales

Sin comentarios