cancel
Showing results for 
Search instead for 
Did you mean: 

How to deploy updated MIBs for Avaya

Cedric_Jackson
08 Mountaineer

How to deploy updated MIBs for Avaya

What is the procedure for deploying updated MIBs for Avaya?
2 ACCEPTED SOLUTIONS

Accepted Solutions
Anon
Community Manager

Re: How to deploy updated MIBs for Avaya

Hi Cedric,

you can upload the new MIB file into the :\Prognosis\Server\Configuration\IPTM\Avaya\MIBs directory. Be careful to back up any existing MIB files if they have the same naming convention.

Thanks!
Randy

View solution in original post

SCOTT_BALDWIN
Expert

Re: How to deploy updated MIBs for Avaya

Hello Cedric_Jackson,

 

Both ".my" and ".txt" file extensions for MIB files can be read by Prognosis as long as the contents are in plain text.

 

Please note:

• The OIDs used in the MIBs provided with Prognosis are read by Prognosis and then converted into Prognosis records by Prognosis code. This means adding a new MIB will not automatically cause Prognosis to create new Prognosis records (or fields) for new OIDs from the new MIB.

 

Thank you,

Scott Baldwin

 

View solution in original post

3 REPLIES 3
Anon
Community Manager

Re: How to deploy updated MIBs for Avaya

Hi Cedric,

you can upload the new MIB file into the :\Prognosis\Server\Configuration\IPTM\Avaya\MIBs directory. Be careful to back up any existing MIB files if they have the same naming convention.

Thanks!
Randy

View solution in original post

Cedric_Jackson
08 Mountaineer

Re: How to deploy updated MIBs for Avaya

While auditing the MIB files within the folder D:\Prognosis\Server\Configuration\IPTM\Avaya\MIBs, I see that there are a mixture of files that have the .my extension and the .txt extension.  Which is preferred, which is better?

 

SCOTT_BALDWIN
Expert

Re: How to deploy updated MIBs for Avaya

Hello Cedric_Jackson,

 

Both ".my" and ".txt" file extensions for MIB files can be read by Prognosis as long as the contents are in plain text.

 

Please note:

• The OIDs used in the MIBs provided with Prognosis are read by Prognosis and then converted into Prognosis records by Prognosis code. This means adding a new MIB will not automatically cause Prognosis to create new Prognosis records (or fields) for new OIDs from the new MIB.

 

Thank you,

Scott Baldwin

 

View solution in original post