DFM: when does the "Alert ID" change for a device?
If an Event occures for device_A a corresponding Alert-ID x is generated. All Events for device_A are grouped together under this Alert-ID x.
Is there a corresponding time window in which all incomming Events for device_A will be grouped under this Alert-ID x or - if generated once this Alert-ID x is bound to device_A for eternity? (or just until the next restart of dmgtd?)
Does anybody know the sense behind these not rememberable Alert-IDs which are also useless for Notification Services?
The only thing I found was this:
Terminology has changed since DFM 1.2.x as follows:
â¢Symptom is replaced by event. Events are rolled up into alerts.
â¢Compound is not used and there is no replacement. A compound differs from an alert; there could be multiple compounds on a single device, whereas an alert is a roll-up of all events for a device.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...