StorageTek Service Delivery Platform (SDP2)
 
Sun StorageTek SL3000 Modular Library System
 
Sun StorageTek SL8500 Modular Library System
 

PLA-Support>Sun Systems>TAPE>SDP2>SN-TP: VOP
 

In this Document

Goal

Solution

References

Created from <SR 3-10118887481>

Applies to:

Goal

SL3000/SL8500 - How to test ASR creation functionality on a library attached to a SDP2 server (doesn't work on SL500)
 

Solution

While dealing with ASR issues on SDP2 it's always tricky to know if the SDP2 will open an Automatic SR upon libraries failure.

If you have ssh or serial access to the library you can easily create a dummy error that will generate a trap and open an ASR using a single snmp command.

Become the sdp2admin: su – sdp2admin
Run the date command to verify the correct date and time

If the date is incorrect, return to the user sdp2cse menu and correct the date.  Customer you can

Find the library to test >

Look in either the domain.vop or domain.xml > more domain.xml

Move to the lib directory > cd /home/sdp2admin/.mdvop/lib

Check to make sure the library is in the snmpConfigFile.txt file > strings snmpConfigFile.txt

Move to the transcripts directory >

Login on the library:

Check if snmp is enabled on the port (doesn’t work on port 1a)

SL8500> snmp ports print

Enable port 1A

SL8500> snmp enable port1A

Check the serial number
SL8500> prom print

Check the snmp trap recipient

SL8500> snmp listTrapRecipients

SL8500 > snmp deleteTrapRecipient id 99

This will generate a 3301 and 4025 Error on the library.

Note : As for now the SDP2/ASR filtering is opening a CASE against the 3301 Error Code, it may differ in the future :

(ASR coverage for Storage Products can be checked out here :

http://docs.oracle.com/cd/E37710_01/doc.41/e37205/toc.htm#6.Fault Coverage Delivered via Service Delivery Platform 2 (SDP2)|outline )

Look at the snmp_IP.Address.0.txt file for the trap > tail snmp_10.80.53.104.0.txt

If the trap isn't in the file, check, The sdp2 servers profile :

Change to root

Move to /opt/Oracle/MdvopServer/bin

 Run the profile :

 Customer network is 2, Oracle services network running VLAN's is 1

1 - Confirm the snmp communication is good from the server with snmpwalk or snmpget command :

snmpwalk -v 2c -c public library_IP system.sysUpTime.0

If you're fine, the result will be similar to the one below, otherwise it will just timeout
[root@Orcl-SDP2-C3-lan sdp2cse]# snmpwalk -v 2c -c public <Library IP> system.sysUpTime.0
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (136872086) 15 days, 20:12:00.86

2- Customer's firewall problem

Wait 3 minutes for the SDP2 and library to process the alert

Run the ls command to see if all of the files have been created > ls -ltrh *10.80.53.104*

 Customer can check their MOS to see when the SR comes in and when the log is uploaded to the SR.

Check FEMS in a web browser to find the SR number:
https://fems.us.oracle.com/FEMSService/resources/femsservice/femsview/516000200712

Look for the 3301 event :

Check MOS for the SR :

Make sure that the library log was attached to the SR :

If the test went well and there are no other errors on the library, Splat will analyze the log and put in the SR”
Support Actions
_____________________________________
2018-02-22 18:37:02 (SA-533) Event code 3301/Result code 4025 occurs as a result of SDP2 testing. This event can be safely ignored and no further action is necessary.

References

This solution has no attachment