A script enabled browser is required for this page to function properly.
Skip to main content
STA Reference Guide, v1.0.2
E28382-03
Table of Contents Previous Next Index


Managing Library SNMP Connections : SNMP Connection Management Tasks : ▼ Update the Library Engine ID After a Library Firmware Upgrade

Update the Library Engine ID After a Library Firmware Upgrade

Use this procedure to update the library and STA SNMP configurations after upgrading to one of the following library firmware versions or higher from any earlier version:

Starting with these firmware versions, the library engine ID is generated with a new 32‑bit value. If you do not perform this procedure, STA will be unable to receive SNMP traps from the library.

Note – This procedure does not apply to SL150 libraries, nor to SL500, SL3000, and SL8500 upgrades to earlier firmware versions.

The procedure is divided into the following parts:

“Update SNMP Settings on the Library” — These steps apply only if you are using SNMP v3 for SNMP communications between STA and the libraries; you can skip these steps if you are using SNMP v2c.

Update SNMP Settings in the STA Application

1.
2.

In the Define Library Connection Details dialog box, blank out the Library Engine ID field, and then click Save. This will force STA to update the engine ID to the new value when it reconnects to the library.

3.
4.

This is the new SNMP engine ID for the library, and you will use it in “Update SNMP Settings on the Library”, Step 4.

Update SNMP Settings on the Library

Note – Perform this procedure only if you are using SNMP v3 for SNMP communications between STA and the upgraded library. Skip this procedure if you are using SNMP v2c.

Note – The examples in this procedure are for an SL8500 library. Command syntax is similar for SL500 and SL3000 libraries. See “Configuring the Libraries for STA” in the STA Configuration Guide for complete details about the referenced commands.

1.
On the upgraded library, log in to the library CLI.
2.
snmp listTrapRecipients 

Example Command:

SL8500> snmp listTrapRecipients 
  requestId
requestId 1
Attributes Auth SHA
AuthPass *****
Engine Id 0x81031f88804b7e542f49811753
Host 10.80.123.92
Index 1
Name STAuser
Port 162
Priv DES
Priv Pass *****
Trap Level 1,2,3,4,11,21,25,27,41,45,61,63,65,81,85,100
Version v3
Object Snmp snmp
Done
Failure Count 0
Success Count 1
COMPLETED
3.

If it is “v3”, continue to Step 4; if it is “v2c”, you do not need to make any further changes, and you can quit this procedure.

4.
5.

You will use this in Step 6.

6.
snmp deleteTrapRecipient id index 

Where:

index is the index number of the STA server trap recipient.

Example Command:

SL8500> snmp deleteTrapRecipient id 1 
   requestId    1
requestId 2
Device 1,0,0,0,1
Success true
Done
Failure Count 0
Success Count 1
COMPLETED
7.
snmp addTrapRecipient trapLevel 1,2,3,4,11,21,25,27,41,45, 61,63,65,81,85,100 host STA_server_IP version v3 name recipient_name auth SHA authPass auth_password priv DES privPass priv_password engineId library_engineID 

Where:

STA_server_IP is the IP address of the STA server.
recipient_name is the SNMP user name for the STA server.
auth_password is the authorization password.
priv_password is the privacy password.
library_engineID is the new library engine ID.

Note – You must include the 0x prefix.

Example Command:

SL8500> snmp addTrapRecipient trapLevel 1,2,3,4,11,21,25,27,41,45,61,63,65,81,85,100 host 10.80.175.34 version v3 name STAuser auth SHA authPass authpwd1 priv DES privPass privpwd1 engineId 0x80001f880436303030323031303433 
   requestId
requestId 12345
Device 1,0,0,0,1
Success true
Done
Failure Count 0
Success Count 1
COMPLETED

Table of Contents Previous Next Index Link to documentation
Copyright © 2012 Oracle and/or its affiliates. All rights reserved.