gcavert

Greetings! Thanks to all for your help on telling me how to modify the alternative presentation number on outbound caller ID. I've inheritied two IP Office systems with a new job and now everyone is going to think I'm an expert. Now I have another question:

I run a home grown SNMP tool to monitor the health of our 412 and 403. I have the MIBs off the Admin CD, but does anyone have a OID list for polling the system for useful little tidbits like trunk alarms or capacity or CPU % or environmental status, blah blah blah...

Thanks in advance!
Glenn

Tooqui

uhhh uhhh,
Not that fast read this documentation I grabbed from engineering,
Sorry for the size of the post :write:




1.1 SNMP Installation Notes

1.1.1 SNMP Functionality

The IP Office SNMP Agent implements SNMPv1 on a read-only basis for security reasons.

1.1.2 SNMP Agent Configuration

The following operational items may be configured for the IP Office SNMP Agent using the IP Office Manager:

SNMP Server:

• Enable/disable
– Enabled: the device to respond to SNMP requests and send traps for any associated events that occur if so configured.
– Disabled: the SNMP agent on the device does not respond to SNMP requests or send traps.

• UDP Port (default 161)
– Changes the default port value of the SNMP Agent.

• Read-only community
– Community string of up to 32 alphanumeric characters for read-only access.

Two trap destinations:
• IP Address
• UDP Port (default 162)
• Community string of up to 32 alphanumeric characters.
• Event mask specifying the events the trap destination is interested in receiving
– generic (coldStart, warmStart, linkDown, linkUp, authenticationFailure)
– licence – License Key Server access fault notifications
– phone change – connected phone change notification


1.1.3 MIBs Supported

The following MIBs are supported by the IP Office SNMP Agent:

• IETF RFC1213 mib-2 (RFC1213-MIB)
– Provides statistics for LAN, WLAN and WAN interfaces
– Groups supported: system, interfaces, at, ip, icmp, tcp, udp and snmp

• IETF RFC1215
– Provides definitions of generic SNMP traps
– Traps supported: warmStart, coldStart, linkDown, LinkUp and authenticationFailure

• IETF RFC2737 ENTITY-MIB
– Provides architectural representation
– Groups supported: entityPhysical and entityGeneral

• Avaya IPO-PROD-MIB
– Provides device/entity identification OIDs

• Avaya IPO-MIB
– Provides root OIDs for functional MIBs
– Provides system wide notifications for events relating to functional entities.
• ipoGenLKSCommsFailureEvent and ipoGenLKSCommsOperationalEvent for License Key Server communication events

• Avaya IPO-PHONES-MIB
– Provides extension/user/phone-port map.
• Phone-port mapping via cross-reference to entPhysicalEntry for port with entPhysicalIndex value
– Provides notifications of phone change event.
• IpoPhonesChangeEvent


1.1.4 Trap Generation

1.1.4.1 RFC1215 Generic SNMP Traps:

Trap type Generated
warmStart Upon soft reboot.
coldStart Upon unexpected reboot such as a power outage.
linkDown Upon transition of an interface (PPP or Frame-Relay) from the up operational state into the down operational state.
linkUp Upon transition of an interface (PPP or Frame-Relay) from the down operational state into the up operational state.
authenticationFailure Upon attempted SNMP request with mismatched community for the type of operation.

1.1.4.2 Hardware Traps:

The following hardware traps are supported in this release on a PRI line only:

Trap type Generated
ipoGenEntityFailureEvent Generated for PRI line when it transitions from a Line Up state to Line down state. This can be done by simply unplugging an operational PRI line, which will in turn switch the green trunk light off at the front of the IP Office.
ipoGenEntityOperationalEvent Generated for PRI line when it transitions from a non-operational state to an operational state. Done simply by plugging the line back in, which in turn activates the green trunk light at the front of the ipoffice.
ipoGenLKSCommsFailureEvent Upon loss of communication with a configured License Key Server.
ipoGenLKSCommsOperationalEvent Upon re-gaining communication with a configured License Key Server.

The ipoGenEntityFailureEvent and ipoGenEntityOperationalEvent traps are issued for the following physical hardware entities:

• Expansion Modules
In relation to connecting cable disconnection and reconnection or power changes:
- Phone 8, 16 and 30; DT 16 and 30; DS 16 and 30; Analogue Trunk 16; S08

• Trunk Interfaces
In relation to link status changes:
- Analogue - Quad Analogue Modules (not supported)
- Q.SIG BRI or PRI (including yellow alarms) – BRI and single/dual PRI modules, E1R2,

• Voice Compressor Modules
In relation to data access problems that result in code reload:
- IP401 and Small Office on board VCMs; VCM 5, 10, 20 and 30.

1.1.4.3 PO-MIB:

Trap type Generated
ipoGenLKSCommsFailureEvent Upon loss of communication with a configured License Key Server.
ipoGenLKSCommsOperationalEvent Upon re-gaining communication with a configured License Key Server.


1.1.4.4 IPO-PHONES-MIB:

Trap type Generated
ipoPhonesChangeEvent Upon change of a DT, DS or IP extension phone type after normal start-up. No traps are issued for POT extensions as the presence or absence of such phones cannot be established hence the ipoPhonesType for such extensions is always potPhone.



1.1.5 MIB Loading

In order to SNMP manage an IP Office system, that is browse its MIBs and fully interpret the traps it sends out, the MIBs supported by IP Office must be loaded and compiled for use with your Network Management System. The supported standard and proprietary MIBs together with the MIB files relied upon for definitions are provided on the IP Office Admin CD off the directory snmp_mibs. Detailed below are details of how to install the appropriate MIBs with a number of Network Management Systems.



1.1.6 CastleRock SNMPc 5.1.6c and earlier:

For MIBs to be used with SNMPc they must first be copied into its mibfiles directory, which is normally C:\Program Files\SNMPc Network Manager\mibfiles. MIBs are installed by selecting Config and MIB Database from the SNMPc menu and then using the Add option and selecting the MIB file from the list presented to load and compile it. The following MIBs must be installed in the order listed to fully SNMP manage an IP Office system:

MIB file Source
ENTITY-MIB snmp_mibs\Standard on IP Office Admin CD
AVAYAGEN-MIB.mib snmp_mibs\IPOffice on IP Office Admin CD
IPO-PROD-MIB.mib snmp_mibs\IPOffice on IP Office Admin CD
IPO-MIB.mib snmp_mibs\IPOffice on IP Office Admin CD
INET-ADDRESS-MIB.mib snmp_mibs\Standard on IP Office Admin CD
INTEGRATED-SERVICES-MIB snmp_mibs\Standard on IP Office Admin CD
DIFFSERV-DSCP-TC.mib snmp_mibs\Standard on IP Office Admin CD
DIFFSERV-MIB.mib snmp_mibs\Standard on IP Office Admin CD
IPO-PHONES-MIB.mib snmp_mibs\IPOffice on IP Office Admin CD



1.1.7 HP OpenView Network Node Manager 6.41 and earlier:

MIBs are installed in Network Node Manager by selecting Options and Load/Unload MIBs: SNMP from the menu and then using the Load… option and browsing for MIB files to load and compile. The following MIBs must be installed in the order listed to fully SNMP manage an IP Office system:

MIB file Source
RFC2737-ENTITY-MIB snmp_mibs\standard on OpenView install CD
AVAYAGEN-MIB.mib snmp_mibs\IPOffice on IP Office Admin CD
IPO-PROD-MIB.mib snmp_mibs\IPOffice on IP Office Admin CD
IPO-MIB.mib snmp_mibs\IPOffice on IP Office Admin CD
INET-ADDRESS-MIB.mib snmp_mibs\Standard on IP Office Admin CD
RFC2213-INTEGRATED-SERVICES-MIB snmp_mibs\standard on OpenView install CD
DIFFSERV-DSCP-TC.mib snmp_mibs\Standard on IP Office Admin CD
DIFFSERV-MIB-HPOV.mib snmp_mibs\Standard on IP Office Admin CD
IPO-PHONES-MIB.mib snmp_mibs\IPOffice on IP Office Admin CD

PBXtech.info