Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

BUG 1500

Status
Not open for further replies.

hubcap1324

IS-IT--Management
Aug 12, 2003
60
US
Ok I was cleaning up some sets today and got the below message popping up constantly:

BUG1500
BUG1500 : 0003CB35 00000003 000CC7C8 00000500 0000820A 00000000 0003CB35 000000
02 5173 00000084 00003715 00000000 00000000 00000000 00000000 00000000
BUG1500 + 105E63E4 1030DAE0 107482F4 1059CFD2 1059CE46
BUG1500 + 1059C432 1059BB0A 10C895A2 10C80B00 10C7FC6E
BUG1500 + 10C7FA7E 10C7F10A 10C7D5BE

The system messages says this:
BUG1500 Parameters to NUM_DN_MEMBERS do not identify a valid SL-1
DNBLOCK. Procedure NUM_DN_MEMBERS
Action:
Severity: Minor. Critical to Monitor: No. SNMP trap: Yes

Might as well be written in Chinese......

I was making changes to sets when this popped up, mainly erasing CPND values on vacant sets and outing vm boxes on vacant sets. I noticed in the message the number 5173 which is an extension I made a change to. That number may be a coincidence though.

Any sugestions on how to handle this?
 
If that message has gone away - problem solved. If it still keeps printing over and over, OUT the sets you changed when it started and rebuild them. That's what I'd do

GHTROUT.com | FAQs | Recent Replies
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top