Needed MIB for ISDN!!!

[Xelha]

Dear Forum,

I am using NNM 6.1 on Sun Solaris. Our devices are Cisco.

We are using ISDN as Backup for the serial lines.

What I need is a MIB for ISDN which gives me information on ISDN Connect/Disconnect, Calling/Called number, Connection Time etc.

Does someone has a suggestion which MIB to use and where to find it. I have loaded the MIB CISCO-ISDN-MIB_VS1MI.MY, but this one does not give the information needed.

Thanks in advance.

Kind Regards,

Xelha
Netherlands

 

[vlan52]

Hi Xelha, right below is a link to the RFC for ISDN and a lot of info + links to download the mib you need.

http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t1/isdn_mib.htm

Regards,
vlan52
vlan52
The end of wisdom is freedom. The end of culture is perfection. The end of
education is character. The end of knowledge is love.

 

[Xelha]

Dear Vlan,

Thanks again for your support.

The MIB you mention does not support 2600 Cisco Routers and supports other devices only with IOS release 12.0T or later release of 12.0T.

Unfortunately we use a lot off 2600s and the suppored routers we have are not all using the required IOS release.

Do you have other suggestions?

Kind regards,

Xelha
Netherlands

 

[vlan52]

Yes, it is supposed to be an add-on to the standard and current set of MIB for ISDN (both work independently, the one you already have + this one), have been looking around, and seems that, in order for you to get the right info regarding ISDN interfaces + calls + conection time + calling/called, accounting, etc...you should probably consider upgrading your IOS (to 12.0X)...sorry about that...

Anyway, right below there is an interesting link regarding this particular issue with the full description of every branch on the MIB.

http://www.simpleweb.org/ietf/mibs/modules/html/?category=IETF&module=ISDN-MIB

If I find anything new related to this issue (starting on monday...hehe...)I'll let you know, please tell me, so we can find the right solution for you, when you talk about getting info from this interfaces, are you looking for a management or reporting solution or both?

Because one thing is getting traps and another completely different thing is being able to retrieve the data from the routers and making graphs out of it, whenever possible just tell me about it, ok?

Regards,
vlan52


vlan52
The end of wisdom is freedom. The end of culture is perfection. The end of
education is character. The end of knowledge is love.

 

[Xelha]

Dear Vlan,

I need this for management. I want to know when ISDN comes up, connect to, disconnect and idealy : connection time.

Kind regards,

Xelha.

 

[vlan52]

Good then, let´s keep an eye on the IOS's version for the routers (regarding the proper snmp traps for ISDN) but also I think is going to be better for you to configure syslog messages to be sent as traps from the network devices.

Just configure syslog-traps enabled + destination server on the routers, pointing to your management station, generate the condition you are looking for on the routers, making a call, disconnect it, and watch on the syslog log or NNM's alarm browser, the messages arriving from the routers.

You'll be receiving a lot of interesting messages this way, also make sure you configure on the routers logging facility 0 (debug or everything, if I'm not mistaking) just for the test.

Does it sound too complicated?Hope not!
Regards,
vlan52


vlan52
The end of wisdom is freedom. The end of culture is perfection. The end of
education is character. The end of knowledge is love.

 

[Xelha]

Dear Vlan52,

Thanks.

Using syslog is - in my case - the best way I guess. I was hoping not to need this because of the additional load on the network, using and maintaining a separate syslog server, unexperienced helpdesk and some other reasons. But again - it is the best way I guess.

Now I am using Cisco Works RME as the Syslog Server. I do filtering on the messages and start an automatic action sending an email to the helpdesk informing them that ISDN is connected or is disconnected. With the ISDN-6-CONNECT and ISDN-6-DISCONNECT also information is showed as Connected TO and Connection Time.

This is what I need. But is a pity not getting this information out of the NNM.

Thanks for your support.

Kind regards,

Xelha
Netherlands

 

[vlan52]

Well great, using syslog is really helpfull, but remember that you could get the syslog messages under NNM anyway, just set your NNM server as the syslog-trap server and syslog is going to generate a snmp trap for every message as well as writing the syslog message to your syslog server (RME).

The Enterprise ID for syslog message genenrating snmp traps is:
.1.3.6.4.1.9.9.41.2
And under NNM you may configure your event at-a-glance of course.

Glad that we found a solution then.
Regards,
vlan52


vlan52
The end of wisdom is freedom. The end of culture is perfection. The end of
education is character. The end of knowledge is love.

 

[Xelha]

Thanks. I will try getting this done.

Kind regards,

Xelha

 

[netconsult]

Hi All,

I am trying to monitor ISDN status of 2611 thro HP openView NNM 6.0. I would like to know what are the steps to configure?
1) what is needed to do in HP OpenView?
2) what are the conf in cisco router 2611?


For that as I read here, i tried to load MIB, CISCO-ISDN-MIB-V1SM1.my , during its loading I faced this problem giving me the error message:-

------------------------------------------------------
" Error detected while loading MIB File L:\CISCO-ISDN-MIB-V1SM1.my.
This MIB cannot be loaded until foll problem is corrected:

Line 25: Error defining object 'ciscoIsdnMib': Parent 'ciscoMgmt' not defined.
Load the MIB that defines 'ciscoMgmt' before laoding this MIB. "
--------------------------------------------------------

can anyone help me out?
thanks in advance

 

[vlan52]

Hi there netconsult, hope the followinfg helps:
1.)In HPOV server configure a snmp community (ro community would do just fine for this) for the segment you are interested on, or you may use any global settings for SNMP an any segment, no problem.
Make sure you can get through, by doing a &quot;snmpwalk -c community <node-to-manage>, you shoul retrieve a lot of info from the node...
2.) At the router, you should configure snnmp-destination server (your management server), snmp ro community, and snmp traps enabled too.

And this is enough to start getting traps from that particular node.Any firewalls in between?Make sure they have open 161-162 ports...

Regarding the MIB loading which failed, seems that you need a prior MIB definition, which you can retrieve from

http://www.cisco.com

and then add the specific MIB for ISDN, should be no problem there...

Hope this helps,
vlan52

vlan52
The end of wisdom is freedom. The end of culture is perfection. The end of
education is character. The end of knowledge is love.