Application Notes for Empirix OneSight Profile with Avaya ...

Post on 30-Mar-2023

0 views 0 download

Transcript of Application Notes for Empirix OneSight Profile with Avaya ...

TLT; Reviewed:

SPOC 12/14/2010

Solution & Interoperability Test Lab Application Notes

©2010 Avaya Inc. All Rights Reserved.

1 of 14

OneSight-PCSNMP

Avaya Solution & Interoperability Test Lab

Application Notes for Empirix OneSight Profile with Avaya

Proactive Contact with PG230 – Issue 1.0

Abstract

These Application Notes describe the configuration steps required for Empirix OneSight

Profile to interoperate with Avaya Proactive Contact with PG230. Empirix OneSight Profile is

a monitoring and management solution that can monitor and report on a variety of e-business

components. In the compliance testing, Empirix OneSight Profile used the SNMP interface

from Avaya Proactive Contact to monitor PG230 alarms.

Information in these Application Notes has been obtained through DevConnect compliance

testing and additional technical discussions. Testing was conducted via the DevConnect

Program at the Avaya Solution and Interoperability Test Lab.

TLT; Reviewed:

SPOC 12/14/2010

Solution & Interoperability Test Lab Application Notes

©2010 Avaya Inc. All Rights Reserved.

2 of 14

OneSight-PCSNMP

1. Introduction These Application Notes describe the configuration steps required for Empirix OneSight Profile

to interoperate with Avaya Proactive Contact with PG230. Empirix OneSight Profile is a

monitoring and management solution that can monitor and report on a variety of e-business

components.

In the compliance testing, Empirix OneSight Profile used the SNMP interface from Avaya

Proactive Contact to monitor PG230 alarms. Upon detection of a PG230 alarm, Avaya Proactive

Contact sends a SNMP trap to Empirix OneSight Profile. The received SNMP trap is displayed

on the Empirix OneSight Profile monitoring screen. The compliance testing used SNMP version

2c.

Note that the integration requires a modified version of the Avaya Proactive Contact MIB file,

due to the third party AdventNet SNMP API, used by Empirix OneSight Profile, not supporting a

space in the DEFVAL statement syntax. This should be the only difference between the two

MIB files.

The detailed administration of basic connectivity among Avaya Proactive Contact, Avaya

AuraTM

Communication Manager, and Avaya AuraTM

Application Enablement Services are not

the focus of these Application Notes and will not be described.

This compliance test used the Avaya Proactive Contact with PG230 deployment option. The

results should be applicable to the Avaya Proactive Contact Standalone deployment option.

1.1. Interoperability Compliance Testing

The interoperability compliance test included feature and serviceability testing.

The feature testing focused on verifying the proper reporting of SNMP traps on the Empirix

OneSight Profile web-based monitoring screen, and comparing the reported SNMP traps with the

logged entries in the Avaya Proactive Contact PG230 alarm database.

The serviceability testing focused on verifying the ability of Empirix OneSight Profile to recover

from adverse conditions, such as disconnecting/reconnecting the Ethernet cable to Empirix

OneSight Profile, rebooting Avaya Proactive Contact, and restarting the Avaya Proactive

Contact processes.

1.2. Support

Technical support on Empirix OneSight Profile can be obtained through the following:

Phone: (866) 367-4749

Email: support@empirix.com

Web: http://esupport.empirix.com

TLT; Reviewed:

SPOC 12/14/2010

Solution & Interoperability Test Lab Application Notes

©2010 Avaya Inc. All Rights Reserved.

3 of 14

OneSight-PCSNMP

2. Reference Configuration The configuration used for the compliance testing is shown below.

3. Equipment and Software Validated The following equipment and software were used for the sample configuration provided:

Equipment Software

Avaya AuraTM

Communication Manager on

Avaya S8500 Server R015x.02.1.016.4

Avaya G650 Media Gateway

TN799DP C-LAN Circuit Pack

HW01 FW038

Avaya AuraTM

Application Enablement Services 5.2

Avaya Proactive Contact with PG230 4.2

Avaya 9600 Series IP Telephones (H.323) 3.1

Empirix OneSight on

Windows 2003 Server with Service Pack 2

Database Server

Modified Avaya Proactive Contact 4.1.2 MIB

Profile avaya_proactive contact pg230

7.3 SR1 Build Number 2135

Microsoft SQL Server 2005

07/7/10 11:11

10/5/10 3:22:22

TLT; Reviewed:

SPOC 12/14/2010

Solution & Interoperability Test Lab Application Notes

©2010 Avaya Inc. All Rights Reserved.

4 of 14

OneSight-PCSNMP

4. Configure Avaya Proactive Contact This section provides the procedures for configuring Avaya Proactive Contact. The procedures

include the following areas:

Administer PG230

Administer MIBs

Administer snmpd.conf

Administer snmpd links

Administer master.cfg

Administer trap

Initiate alarm and trap monitoring

The configuration of Proactive Contact is performed by Avaya technicians. The procedural steps

are presented in these Application Notes for informational purposes.

4.1. Administer PG230

Log in to the Linux shell of the Proactive Contact server with administrator credentials. Use the

command “telnet switch1” to telnet into the PG230, where “switch1” is the hostname of the

PG230. The DIGITAL SWITCH LOGIN screen is displayed. Log in using the appropriate

credentials.

D I G I T A L S W I T C H L O G I N

Username: _______________

Password: __________

The ADMINISTRATOR MAIN MENU screen is displayed next. Enter “B” for System

Configuration Menu, followed by “C” in the subsequent screen for Host Configuration.

A D M I N I S T R A T O R M A I N M E N U

Generic Version.Revision 15.2.3

A) Data Base Administration Menu

B) System Configuration Menu

C) Maintenance Menu

D) Diagnostics Menu

Enter Selection: B

TLT; Reviewed:

SPOC 12/14/2010

Solution & Interoperability Test Lab Application Notes

©2010 Avaya Inc. All Rights Reserved.

5 of 14

OneSight-PCSNMP

The HOST CONFIGURATION screen is displayed. Navigate to a page with a blank entry

line, and press Ctrl-A to add an entry for the SNMP port as shown below. For Loc. Port, enter

“2051” or any available port. For Host Name, enter a desired description. Retain the default

values in the remaining fields.

H O S T C O N F I G U R A T I O N

Interface Ethernet Connect.Password ________________ Loc. Port 2050

Host Name ENET3 Rem.Inet.Addr INADDR_ANY Rem. Port 0

Trace (1/0) 0 Failure Action None Failure Alarm None

Protocol TCP Alarm State On

Reset Time 2

Interface Ethernet Connect.Password ________________ Loc. Port 2051

Host Name SNMP Rem.Inet.Addr INADDR_ANY Rem. Port 0

Trace (1/0) 0 Failure Action None Failure Alarm MINOR

Protocol TCP Alarm State Off

Reset Time 60

Interface ___________ ________________ ________________ _____________ _____

Host Name __________ ________________ ________________ _____________ _____

Trace (1/0) _ ________________ ________________ _____________ _____

________ ____ ________________ ________________ _____________ _____

__________ ___ ________________ ________________ _____________ _____

4.2. Administer MIBs

Log in to the Linux shell of the Proactive Contact server with super user credentials. Navigate to

the /etc/snmp directory, and open the snmp.conf file.

Scroll to the end of the file, and add two entries for the MIB directory locations, and two entries

for the MIBs to load, as shown below.

# location of all MIBs

mibdirs +/usr/share/snmp/mibs:

mibdirs +/opt/Avaya/pds/config/snmp:

# load the MIBs

mibs +ALL

mibs +AVAYA-PROACTIVECONTACT-MIB

TLT; Reviewed:

SPOC 12/14/2010

Solution & Interoperability Test Lab Application Notes

©2010 Avaya Inc. All Rights Reserved.

6 of 14

OneSight-PCSNMP

4.3. Administer snmpd.conf

In the same /etc/snmp directory, open the snmpd.conf file.

Scroll to the end of the file, and add an entry to invoke the PG230 alarm script, as shown below.

# invoke script to process MIB for PG230 alarms

Pass .1.3.6.1.4.1.6889.2.40.1 /opt/Avaya/pds/shell/pass_pg230Alarms

Restart the snmpd service using the command “service snmpd restart”.

#xxxx# service snmpd restart

Stopping snmpd: [ OK ]

Starting snmpd: [ OK ]

Lzpds4b@/opt/avaya/pds [1012]

4.4. Administer snmpd Links

To enable the snmpd service to start up at boot time, execute the following commands to create

the links.

#xxxx# cd /etc/rc.d/rc3.d

#xxxx# ln –s ../init.d/snmpd S99snmpd

#xxxx# cd /etc/rc.d/rc5.d

#xxxx# ln –s ../init.d/snmpd S99snmpd

#xxxx# cd /etc/rc.d/rc6.d

#xxxx# ln -s ../init.d/snmpd K00snmpd

TLT; Reviewed:

SPOC 12/14/2010

Solution & Interoperability Test Lab Application Notes

©2010 Avaya Inc. All Rights Reserved.

7 of 14

OneSight-PCSNMP

4.5. Administer master.cfg

Log in to the Linux shell of the Proactive Contact server with administrator credentials.

Navigate to the /opt/avaya/pds/etc directory, and open the master.cfg file. Locate the

SWITCHALARMS and SWITCHNAME parameters, and make certain SWITCHALARMS

is set to the PG230 SNMP port from Section 4.1, and SWITCHNAME is set to the hostname of

the PG230, as shown below. In the event that a change is made to the master.cfg file, then run

the command “stop_pds” followed by “start_pds” to restart processes.

SKIP_LOCK_TIME:0

SSLIOP:YES

SWITCHALARMS:2051

SWITCHNAME:switch1

SWITCHPORTS:2048,2049,2050

SWITCHTESTMODE:NO

SWITCHTYPE:DIGITAL

4.6. Administer Trap

Navigate to the /opt/avaya/pds/config/snmp directory, and open the traps.cfg file.

Comment out the existing entries for snmptrapcmd1 and snmptrapcmd2. Add a new

snmptrapcmd1 entry as shown below, where “v2c” is the SNMP version, “avayapds” is any

desired community string, and “10.32.35.150” is the IP address of the Empirix OneSight Profile

server.

Make a note of the community string, which will be used later to configure Empirix OneSight

Profile.

#snmptrapcmd1=snmpinform –v 3 –u myuser –a MD5 –A mypassword –l authNoPriv localhost 0

#snmptrapcmd2=snmpinform –v 3 –u myuser –a MD5 –A mypassword –l authNoPriv localhost 0

snmptrapcmd1=snmptrap –v2c –c avayapds 10.32.35.150

4.7. Initiate Alarm and Trap Monitoring

Run the “init_pg230AlarmMonitor” command to initiate alarm monitoring, and run the

“init_pg230TrapsMonitor” command to initiate trap monitoring, as shown below.

#xxxx# init_pg230AlarmMonitor

#xxxx# pg230AlarmMonitor started.. pid=23137

#xxxx# init_pg230TrapsMonitor

#xxxx# pass_pg230Traps started.. pid=23471

TLT; Reviewed:

SPOC 12/14/2010

Solution & Interoperability Test Lab Application Notes

©2010 Avaya Inc. All Rights Reserved.

8 of 14

OneSight-PCSNMP

5. Configure Empirix OneSight Profile This section provides the procedures for configuring Empirix OneSight Profile. The procedures

include the following areas:

Launch web interface

Administer monitor group

Administer monitor

The configuration of Onesight is performed by Empirix technicians. The procedural steps are

presented in these Application Notes for informational purposes.

5.1. Launch Web Interface

Access the OneSight web interface by using the URL “http://ip-address:8080” in an Internet

browser window, where “ip-address” is the IP address of the OneSight server. Log in using the

appropriate credentials.

TLT; Reviewed:

SPOC 12/14/2010

Solution & Interoperability Test Lab Application Notes

©2010 Avaya Inc. All Rights Reserved.

9 of 14

OneSight-PCSNMP

In the subsequent screen, select I want to set up a monitor group now.

5.2. Administer Monitor Group

The Monitor Groups screen is displayed. Click Add to create a new monitor group.

The Monitor Group Editor screen is displayed next. Enter desired Name and Description, and

click Add New.

TLT; Reviewed:

SPOC 12/14/2010

Solution & Interoperability Test Lab Application Notes

©2010 Avaya Inc. All Rights Reserved.

10 of 14

OneSight-PCSNMP

5.3. Administer Monitor

The Add Monitor screen is displayed. Select Profiles > Avaya: Proactive Contact pg230

from the left pane.

The Monitor Creation Wizard screen is displayed. For Name, enter the IP address of the

OneSight server. Retain the default values in the remaining fields.

TLT; Reviewed:

SPOC 12/14/2010

Solution & Interoperability Test Lab Application Notes

©2010 Avaya Inc. All Rights Reserved.

11 of 14

OneSight-PCSNMP

The Monitor Editor screen is displayed next. Click System Editor.

The System Editor screen is displayed. Select the SNMP Trap tab. For Community, enter the

community string from Section 4.6.

TLT; Reviewed:

SPOC 12/14/2010

Solution & Interoperability Test Lab Application Notes

©2010 Avaya Inc. All Rights Reserved.

12 of 14

OneSight-PCSNMP

6. General Test Approach and Test Results The feature test cases were performed manually. Different SNMP traps were generated on

Avaya Proactive Contact and verified on the Empirix OneSight Profile web-based monitoring

screen. The verification also included checking the reported alarms by Empirix OneSight Profile

against the logged entries in the Avaya Proactive Contact PG230 alarm database. The different

SNMP traps included PG230 cards out of service and PG230 reboot.

The serviceability test cases were performed manually by disconnecting/reconnecting the

Ethernet cable to Empirix OneSight Profile, rebooting Avaya Proactive Contact, and restarting

the Avaya Proactive Contact processes.

All test cases were executed and passed.

7. Verification Steps Generate a PG230 alarm such as taking the PRI card out of service or rebooting the PG230.

With a protocol analyzer, verify the SNMP traps are sent to the Empirix OneSight Profile server.

From the Empirix OneSight Profile web interface, select Status > General from the top menu to

display the monitors. Expand on Avaya: Proactive Contact pg230, and verify that the received

traps are displayed, as shown below.

TLT; Reviewed:

SPOC 12/14/2010

Solution & Interoperability Test Lab Application Notes

©2010 Avaya Inc. All Rights Reserved.

13 of 14

OneSight-PCSNMP

8. Conclusion These Application Notes describe the configuration steps required for Empirix OneSight Profile

to successfully interoperate with Avaya Proactive Contact with PG230. All feature and

serviceability test cases were completed successfully.

9. Additional References This section references the product documentation relevant to these Application Notes.

1. Administering Avaya Proactive Contact, Release 4.2, May 2010, available at

http://support.avaya.com.

2. Handbook To Dynamic Logging & SNMP in Avaya Proactive Contact 4.2, Issue 1.03,

available via DevConnect support request.

3. Empirix OneSight Administrator Guide, Version 7.3, available upon request from Empirix

technical support.

4. Empirix OneSight Operator Guide, Version 7.3, available upon request from Empirix

technical support.

TLT; Reviewed:

SPOC 12/14/2010

Solution & Interoperability Test Lab Application Notes

©2010 Avaya Inc. All Rights Reserved.

14 of 14

OneSight-PCSNMP

©2010 Avaya Inc. All Rights Reserved.

Avaya and the Avaya Logo are trademarks of Avaya Inc. All trademarks identified by ® and ™

are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the

property of their respective owners. The information provided in these Application Notes is

subject to change without notice. The configurations, technical data, and recommendations

provided in these Application Notes are believed to be accurate and dependable, but are

presented without express or implied warranty. Users are responsible for their application of any

products specified in these Application Notes.

Please e-mail any questions or comments pertaining to these Application Notes along with the

full title name and filename, located in the lower right corner, directly to the Avaya DevConnect

Program at devconnect@avaya.com.