NSR E122 Trace codes

[Mike Johnston]

I have a situation where a UX 11i server is polling tape devices over the SAN (dm_stape is dconfirmed to be disabled). I am looking for documentaion that will help me decipher the NSR trace codes.

[Mike Johnston]

I appologize, the subject should read

NSR E1200 Trace Codes.

[Ralf Loehmann_2]

Hello Mike,

you are saying that the tape devices get polled, so you already decoding the trace somehow. There are some internal HP documents available about this, the problem here is that the information might look different from firmware version to firmware version. The trace is a lab debugging function and it is nothing else like bringing the internal command stack in a viewable information.

There are also documents available to check your environment for know issues (SAN checklists).

Than again talking about polling, not every polling is bad for the NSR and the backups. The question here is what commands are used to poll, the bridge is supporting for example inquiries for page 00 and page 80.

My recommendation would be to either talk with your HP contact about the SAN checklist and check for updates on firmware, patches, application and management software like OVSAM, commandview, etc.

Another important step would be to check the SAN configuration to reduce polling for other devices, like disk arrays, thru HBA zoning, etc. Here I would recommend to check the available document on the HP website:
http://www.hp.com
--> go to Storage,
than SAN infrastructure,
than SAN Design Guide.
Here you find: HP StorageWorks SAN Design Reference Guide (AA-RMPNQ-TE, September 2004)
http://h200001.www2.hp.com/bc/docs/support/SupportManual/c00093931/c00093931.pdf
It has a chapter: Best Practices, which might be useful.
You might also check:
HP StorageWorks Enterprise Backup Solution Design Guide (June 2004)
http://h200006.www2.hp.com/bc/docs/support/SupportManual/c00190922/c00190922.pdf

This should help to minimize problems.

If your are sure to have the problems in a trace, send me the trace and I look over it. In most cases I can not say which process/application is responsible for it, but we might see from which host it comes. This might be already help to find it.

Ralf.