Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Help for understanding Alert & Activities in DFM

Is there any help for the table fields in Alert and activities ??

for example in the commponent table there is IF-192.168.100.1/92 [Tu1011213001] [MPLS-**]  I dont understand what IF means and what is the number 92 after the IP ??

Thank you

2 ACCEPTED SOLUTIONS

Accepted Solutions

Re: Help for understanding Alert & Activities in DFM

It is not that mysterius as it seems to be in first place;

The first part is how Fault Managment classifies the entity (component) for which the event is reported:

In you case it is as follows:

an interface of the device with mgmt IP 192.168.100.2, and the interface has the snmp ifIndex 92;

    IF     InterFace

    IPAddress   Mgmt IP address of the device known by DFM

   92      snmp ifIndex of the interface (for which the event is active)

in square brakets is following detailed information retrieved from SNMP:

    ifName  [1.3.6.1.2.1.31.1.1.1.1]

    ifAlias [1.3.6.1.2.1.31.1.1.1.18]

Help for understanding Alert & Activities in DFM

on modular devices there is an IOS command to enable the ifIndex persistant feature:

    snmp-server ifindex persist

if confiugured, the command shows up in the config of the device. Also, the ifIndex-table is written into nvram :

   dir nvram:

here are some links for detailed information:

http://www.cisco.com/en/US/tech/tk648/tk362/technologies_tech_note09186a0080134eec.shtml

http://www.cisco.com/en/US/docs/ios/12_1t/12_1t5/feature/guide/dt5ifidx.html#20001

and here on the CSC forum in the "Documents" section for "Network Management":

https://supportforums.cisco.com/docs/DOC-4568

[there are other helpful docs:

https://supportforums.cisco.com/community/netpro/network-infrastructure/network-management?view=documents]

per default DFM rediscovers the devices once a week and will recognize changes through this process - I would say in most cases this is enough - for non modular devices new ifIndexes are generated when logical interfaces are configured and usually that is not very often, for modular device generally a change is known to the administrator and a manual rediscover of the device can be started in DFM.

DFM needs to know a device and its interfaces to correctly report on an error, but (in my opinion!) in most cases the one week rediscover is ok to start with for DFM (even with no ifIndex persistance). But HUM - (now, the "Monitor" part of LMS 4.x) works with ifIndexes and a change of ifIndexes could lead to graph showing data from different pyhiscal interfaces or suddenly showing no data any more.

4 REPLIES

Re: Help for understanding Alert & Activities in DFM

It is not that mysterius as it seems to be in first place;

The first part is how Fault Managment classifies the entity (component) for which the event is reported:

In you case it is as follows:

an interface of the device with mgmt IP 192.168.100.2, and the interface has the snmp ifIndex 92;

    IF     InterFace

    IPAddress   Mgmt IP address of the device known by DFM

   92      snmp ifIndex of the interface (for which the event is active)

in square brakets is following detailed information retrieved from SNMP:

    ifName  [1.3.6.1.2.1.31.1.1.1.1]

    ifAlias [1.3.6.1.2.1.31.1.1.1.18]

New Member

Re: Help for understanding Alert & Activities in DFM

thank you Martin ;-)

I wonder how could I find out if those indexes (IFindexes) are persistant or not,??

and do I have to pay attention to those cause those numbers are just important for

DFM to identify the inerfaces ??

thank you

Help for understanding Alert & Activities in DFM

on modular devices there is an IOS command to enable the ifIndex persistant feature:

    snmp-server ifindex persist

if confiugured, the command shows up in the config of the device. Also, the ifIndex-table is written into nvram :

   dir nvram:

here are some links for detailed information:

http://www.cisco.com/en/US/tech/tk648/tk362/technologies_tech_note09186a0080134eec.shtml

http://www.cisco.com/en/US/docs/ios/12_1t/12_1t5/feature/guide/dt5ifidx.html#20001

and here on the CSC forum in the "Documents" section for "Network Management":

https://supportforums.cisco.com/docs/DOC-4568

[there are other helpful docs:

https://supportforums.cisco.com/community/netpro/network-infrastructure/network-management?view=documents]

per default DFM rediscovers the devices once a week and will recognize changes through this process - I would say in most cases this is enough - for non modular devices new ifIndexes are generated when logical interfaces are configured and usually that is not very often, for modular device generally a change is known to the administrator and a manual rediscover of the device can be started in DFM.

DFM needs to know a device and its interfaces to correctly report on an error, but (in my opinion!) in most cases the one week rediscover is ok to start with for DFM (even with no ifIndex persistance). But HUM - (now, the "Monitor" part of LMS 4.x) works with ifIndexes and a change of ifIndexes could lead to graph showing data from different pyhiscal interfaces or suddenly showing no data any more.

New Member

Re: Help for understanding Alert & Activities in DFM

thank you indeed for your helpful guidance

350
Views
10
Helpful
4
Replies
CreatePlease to create content