Difference between revisions of "AlphaNet Link (Event Type)"
From Zenitel Wiki
(→Additional information) |
|||
Line 22: | Line 22: | ||
* In case of Alternative Routing: | * In case of Alternative Routing: | ||
** If there are two routes to the destination node, this event will be triggered every time one of the links to the destination node goes up or down. | ** If there are two 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 'transit node', it is the link to the 'transit node' which is reported. | + | ** 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== | ==Application== |
Revision as of 00:10, 18 February 2009
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: | N/A |
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 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
- AlphaNet surveillance and reporting