Difference between revisions of "AlphaNet Link (Event Type)"
From Zenitel Wiki
(→Application) |
|||
| Line 26: | Line 26: | ||
==Application== | ==Application== | ||
| − | [[Image: System Events_29AlphaNet Link.jpg| | + | [[Image: System Events_29AlphaNet Link.jpg|left|250px|thumb|Example: [[LOG - Send text to exchange’s log port (including date/time)|Log]] all AlphaNet links connected to this exchange]] |
* AlphaNet surveillance and reporting | * AlphaNet surveillance and reporting | ||
| + | |||
| + | [[File:AlphaNet monitoring.PNG|left|250px|thumb|Example: LOG - Send text to exchange’s log port (including date/time)]] | ||
| + | |||
[[Category:Event Handler]] | [[Category:Event Handler]] | ||
[[Category:Event types]] | [[Category:Event types]] | ||
Revision as of 11:32, 21 December 2012
Event description
| Event Owner: | Station number 1 (fixed) |
| Event type: | 29 - AlphaNet Link |
| Subevent: | The remote node number |
| When change to ON: | When the AlphaNet link is reported UP |
| When change to OFF: | When the AlphaNet link is reported DOWN |
| When related to: | (Not used) |
Available from AMC software version 10.01.
Additional information
- Sub-event = 255 means "wildcard", and the node number can be read by the parameter %sev
- In case of Alternative Routing:
- If there are two direct routes to the destination node, this event will be triggered every time one of the links to the destination node goes up or down.
- Only links to the neighbouring node is reported. If there is an alternative route via a 'transit node', it is the link to the 'transit node' which is reported.
Application
Example: Log all AlphaNet links connected to this exchange
- AlphaNet surveillance and reporting
