08-05-2003 03:59 PM - edited 03-02-2019 09:22 AM
Hi all,
Does anyone know what a SW error 2051 is on the BPX and what causes one to occur? I have pasted the SW error snapshot below if you can also decode it!
Also if anyone has a listing of other BPX errors, which identifies the catalyst and the recommended action to follow, I would be ever so interested to see. Personally I have a few descriptions on some of the SW errors but I have no means of decoding them...
Regards, DK.
sb11442a TN Service BPX 8620 9.2.38 Aug. 6 2003 10:47 G+10
Active CC's Software Log
No. Type Number Data(Hex) PC(Hex) PROC SwRev Date Time
1. Error 2051 00001E5E 303BBFA6 TRNS 9.2.38 07/31/03 15:09:42
sb11442a TN Service BPX 8620 9.2.38 Aug. 6 2003 10:48 G+1
Active CC's Software Log
No. Type Number Data(Hex) PC(Hex) PROC SwRev Date Time
1. Error 2051 00001E5E 303BBFA6 TRNS 9.2.38 07/31/03 15:09:42
US 306549A4 30 3B BF A6 00 00 08 03 00 00 1E 5E 00 00 1C 00 0;.........^....
US 306549B4 07 D3 07 1F 01 05 00 00 00 00 1E 1A 41 43 54 56 ............ACTV
US 306549C4 00 00 00 C0 00 00 00 03 30 65 4A 30 30 40 AE 00 ........0eJ00@..
US 306549D4 30 3B B9 E8 30 65 4A 28 30 65 4A 6C 30 40 A0 0A 0;..0eJ(0eJl0@..
US 306549E4 32 F3 D4 50 00 00 00 05 00 00 1E 5E 00 00 1E 1A 2..P.......^....
US 306549F4 30 65 4A 26 2C 59 FE 95 31 49 0E FC 00 00 01 2C 0eJ&,Y..1I.....,
US 30654A04 31 35 B8 F2 2C 59 FE 96 31 35 B8 D4 31 35 B8 D4 15..,Y..15..15..
US 30654A14 30 75 34 70 00 00 00 00 32 F3 D4 4C 00 01 00 0D 0u4p....2..L....
US 30654A24 00 02 00 10 00 00 1E 5F 00 00 1E 08 00 00 1E 5E ......._.......^
US 30654A34 00 00 00 09 00 00 1E 1A 00 00 00 00 00 00 00 FF ................
Solved! Go to Solution.
08-08-2003 12:02 PM
This is what I found -
Software error 2051 was logged, but not every file collection. The separation of the swerrs may be days or weeks. There may not be any statistics activity at the time the files were logged (no statistics enabled or disabled, and no objects (connections, lines, trunks, ports, or physical lines) added or deleted.
The dspstatfiles screen shows files with write errors. The files with write errors show a "File Length" equal to "Data Length". The file is full and additional statistics can not be written into the file.
Conditions:
Observed in two networks, with software releases 9.2.33 and 9.2.36. There may not be any statistics activity, but there are probably a large number of statistics enabled per object. There may also be multiple buckets for a stat in each TFTP statistics file (the bucket interval is less than the file interval, as displayed on dspstatparms).
Workaround:
This problem is due to a bucket index wraparound calculation error. Two statistics characteristics will increase the probability of the wraparound error causing a swerr 2051 to be logged:1. There are many statistics enabled per object. The size of the wraparound error is multiplied by the number of statistics enabled for the object. Thus the more statistics enabled per object the greater the probability that the error will result in a TFTP file overflow. 2. The configured bucket interval is less than the configured file interval. The greater the number of buckets per statistic the greater the probability of the wraparound error.
Reducing the statistics enabled per object and the number of buckets per TFTP statistics file will reduce the probability of the file overflow.
08-08-2003 12:02 PM
This is what I found -
Software error 2051 was logged, but not every file collection. The separation of the swerrs may be days or weeks. There may not be any statistics activity at the time the files were logged (no statistics enabled or disabled, and no objects (connections, lines, trunks, ports, or physical lines) added or deleted.
The dspstatfiles screen shows files with write errors. The files with write errors show a "File Length" equal to "Data Length". The file is full and additional statistics can not be written into the file.
Conditions:
Observed in two networks, with software releases 9.2.33 and 9.2.36. There may not be any statistics activity, but there are probably a large number of statistics enabled per object. There may also be multiple buckets for a stat in each TFTP statistics file (the bucket interval is less than the file interval, as displayed on dspstatparms).
Workaround:
This problem is due to a bucket index wraparound calculation error. Two statistics characteristics will increase the probability of the wraparound error causing a swerr 2051 to be logged:1. There are many statistics enabled per object. The size of the wraparound error is multiplied by the number of statistics enabled for the object. Thus the more statistics enabled per object the greater the probability that the error will result in a TFTP file overflow. 2. The configured bucket interval is less than the configured file interval. The greater the number of buckets per statistic the greater the probability of the wraparound error.
Reducing the statistics enabled per object and the number of buckets per TFTP statistics file will reduce the probability of the file overflow.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide