тут, вроде бы, SNMP непричём. Т.е. вы сделали все пункты, как написано в последнем разделе, и не работает? Выделю важные, на мой взгляд, пункты.
RECOMMENDATIONS FOR IMPLEMENTING THE NMC FEATURE (remote system)
The recommended procedure is the following:
- Activate network management (value deactivated by default or after a cold reset)
- Enter the remote system's complete configuration:
• station number for alarm reporting
• validation of the automatic alarm reporting feature
• definition of the various thresholds
• definition of the urgent alarms
• etc.
- Activate the central management feature by checking the Try to use active NMC session
for alarms reporting box in the Centralized Management window
- Perform a warm reset for table resizing
03.02.2012 10:43:53, etc.]]>
Спасибо за инфу,
скорее не работает, т.к. на OXO нет лицензий на SNMP
02.02.2012 16:53:51, Vlad 46.]]>
Выдержка из главы 8.8 доки на ОХО:
Alarms Reporting(Only visible after clicking the Part 2 button)
Alarms reporting enables the remote system to inform the Management Center as soon as an
abnormal event arises with the Alcatel-Lucent OmniPCX Office Communication Server.
- Automatic alarms reporting: check the box to activate automatic alarms reporting. By
default, this feature is inhibited.
- Reaction on erroneous call: for example, the call number does not correspond to that of
the Management Center:
• Time before retry (min): waiting time, in minutes, before trying again (value between
1 and 12 minutes inclusive, by default: 12 minutes)
• Max. number of call attempts: maximum number of call backs (a single callback
authorized)
- Reaction on non-answered call: for example, the Management Center has not answered
because all accesses are busy:
• Time before retry (min): waiting time, in minutes, before trying again (value between
1 and 12 minutes inclusive, by default: 12 minutes)
• Max. number of retries: maximum number of callbacks (value between 1 and 99, by
default: 50)
- Threshold for alarms reporting activation: by default, when the threshold is reached, an
alarm is sent to the Management Center. This one is connected to the remote system
automatically so as to deduct the alarm information:
• History table: by default 80 % (100 % = 400 history messages)
• HW Anomalies table: hardware messages, by default 80 % (100 % = 200 hardware
messages)
• Urgent Alarms table: by default 80 % (100 % = 200 urgent alarm messages)
SELECT URGENT ALARMS SUBMENU
This window makes it possible to define the urgent alarms for hardware anomalies as well as
historic events.
Note 3:
The Urgent Alarm account and password are configured via 2 new fields: URGALARM account and URGALARM
password.
Alarm password: Any alphanumeric character plus @ - _ + . /\\ are allowed. (See default password)
Alarm user: If windows domain/user group must be defined, it must be under the form :”domain\\user”.
Any alphanumeric character plus @ - _ + . /\\ are allowed.
Predefined urgent events in the Hardware Anomalies section
- PRINTING_ATTEMPT_FAULT: Message sent by the output device (printer) after every 5
failed print attempts.
- T2_NO_MULTIFRAME_FOUND: A signal shortage has been detected on a T2 access.
8-81
This alarm occurs after synchonization is lost in multi-frame mode and after timer has
expired. T2 automatically starts double-frame mode.
- T2_REMOTE_ALARM_INDICATION: A remote alarm indication has been received on a
T2 access.
RECOMMENDATIONS FOR IMPLEMENTING THE NMC FEATURE (remote system)
The recommended procedure is the following:
- Activate network management (value deactivated by default or after a cold reset)
- Enter the remote system's complete configuration:
• station number for alarm reporting
• validation of the automatic alarm reporting feature
• definition of the various thresholds
• definition of the urgent alarms
• etc.
- Activate the central management feature by checking the Try to use active NMC session
for alarms reporting box in the Centralized Management window
- Perform a warm reset for table resizing
- Check that the call number has been programmed properly
Remark:
Transmissions of Internet alarms are integrated in the History messages window
02.02.2012 13:18:46, etc.]]>
Что-то настроили, но не работает. Алармы появляются после того, как сделать синхронизацию с OXO,а вот сама OXO не хочет отправлять, сейчас проверяем конфиги
02.02.2012 12:41:11, Vlad 46.]]>
А в ОХО настроили выдачу аварийных сигналов (по документации на ОмниВисту и ОХО)?
01.02.2012 20:54:23, etc.]]>
Завел OXO в OmniVista, синхронизация проходит, учет работает, а алармы не ловит. Алармы появляются только после синхронизации, в чем может быть проблема?
01.02.2012 19:28:27, Vlad 46.]]>