hartman323
Technical User
I set CM to send traps about trunks, but I got strange behavior.
My filter: Severity: all, category: trunks, MO-type: all.
After that, I physically unplug E1 cable => trunk goes out-of-service => on the snmp traps destination I see nothing.
Now I plug in E1 cable back => trunk goes in-service => now on the snmp destination I got 2 type of traps (OIDs) .1.3.6.1.4.1.6889.1.8.1.0.4 (corresponds to down event) and .1.3.6.1.4.1.6889.1.8.1.0.12 (corresponds to up event).
If I try the same experiment with another filter: severity - all, category - trkbd, MO-type: all.
If I disconnect E1 cable => trunk out-of-service => I got .1.3.6.1.4.1.6889.1.8.1.0.4
If I connect E1 cable back > trunk in-service => I got .1.3.6.1.4.1.6889.1.8.1.0.12.
I wonder why with 'trunks' filter I got no traps on down event, and got down and up traps on up event? Bug??
Thanks!
My filter: Severity: all, category: trunks, MO-type: all.
After that, I physically unplug E1 cable => trunk goes out-of-service => on the snmp traps destination I see nothing.
Now I plug in E1 cable back => trunk goes in-service => now on the snmp destination I got 2 type of traps (OIDs) .1.3.6.1.4.1.6889.1.8.1.0.4 (corresponds to down event) and .1.3.6.1.4.1.6889.1.8.1.0.12 (corresponds to up event).
If I try the same experiment with another filter: severity - all, category - trkbd, MO-type: all.
If I disconnect E1 cable => trunk out-of-service => I got .1.3.6.1.4.1.6889.1.8.1.0.4
If I connect E1 cable back > trunk in-service => I got .1.3.6.1.4.1.6889.1.8.1.0.12.
I wonder why with 'trunks' filter I got no traps on down event, and got down and up traps on up event? Bug??
Thanks!