When NetView became a part of TEC and bundled with it, the TEC architects got a mandate to apply their best practices to the NetView baroc and rules files. These were altered and started shipping with TEC instead of with NetView.
The first thing they did was ditch the old OpenView class structure and adopt the one we use in 7.1.4 and 7.1.5, TEC_ITS_BASE. Then they decided that all incoming events from NetView should be given a default severity and they wrote a rule (or perhaps several I don't know exactly) to increment that severity on a timed basis. The idea was that if a matching Interface Up didn't cancel an Interface Down in 15 minutes, for example, then the Interface Down would be raised to the next higher level of severity on the TEC Console. In order to implement this scheme, NetView was altered to no longer include a severity on the events it sent. The NetView severity scheme is not an exact match for the TEC one anyway, and this was seen as no big deal to give up.
But not all customers were willing to migrate to the new way of doing things. Some of them had written their own TEC rules using the old OpenView classes. Some of them had their own rules for escalating severity. So for them we had to add a switch to tecint.conf so that NetView severity would be included in TEC events. So that's why the doc talks about this in terms of migrating.
You can turn it on if you want to, but this may cause unexpected results at the TEC Console if you are also running the default TEC rules.
Tivoli Network Availability Management Level Three
Network Availability Management
Tivoli Software, IBM Corp
1-919-224-1642 | T/L 687-1642 | ITN 26871642
NV-L mailing list
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to
internal IBM'ers only)