Netgear GSM7248 Netgear 48 port switch error

I have the above switch Netgear GSM7248  installed on my network and wanted to see if anyone new what these errors mean.

Entry Filename Line TaskID Code Time
00001: EVENT> bootos.c 317 11385070 AAAAAAAA 0 0 0 11  
00002: EVENT> bootos.c 317 11385070 AAAAAAAA 0 0 0 11  
00003: EVENT> bootos.c 317 11385070 AAAAAAAA 0 0 0 11  
00004: EVENT> bootos.c 317 11385070 AAAAAAAA 0 0 0 11  
00005: EVENT> bootos.c 317 11385070 AAAAAAAA 0 0 0 11  
00006: EVENT> bootos.c 317 11385070 AAAAAAAA 0 0 0 11  
00007: EVENT> bootos.c 317 11385070 AAAAAAAA 0 0 0 11  
00008: EVENT> bootos.c 317 11385070 AAAAAAAA 0 0 0 11  
00009: EVENT> bootos.c 317 11385070 AAAAAAAA 0 0 0 11  
00010: EVENT> bootos.c 317 11385070 AAAAAAAA 0 0 0 11  
00011: EVENT> bootos.c 317 11385070 AAAAAAAA 0 0 0 11  
00012: EVENT> bootos.c 317 11385070 AAAAAAAA 0 0 0 11  
00013: EVENT> bootos.c 317 11385070 AAAAAAAA 0 0 0 11  
00014: EVENT> bootos.c 317 11385070 AAAAAAAA 0 0 0 11  
00015: EVENT> bootos.c 317 11385070 AAAAAAAA 0 0 0 11  
00016: EVENT> bootos.c 317 11385070 AAAAAAAA 0 0 0 11  
00017: EVENT> bootos.c 317 11385070 AAAAAAAA 0 0 0 11  
00018: EVENT> bootos.c 317 11385070 AAAAAAAA 0 0 0 11  
00019: EVENT> bootos.c 317 11385070 AAAAAAAA 0 0 0 11  
00020: EVENT> bootos.c 317 11385070 AAAAAAAA 0 0 0 11  
00021: EVENT> bootos.c 317 11385070 AAAAAAAA 0 0 0 11  
00022: EVENT> bootos.c 317 11385070 AAAAAAAA 0 0 0 11  
00023: EVENT> bootos.c 317 11385070 AAAAAAAA 0 0 0 11  
00024: EVENT> bootos.c 317 11385070 AAAAAAAA 0 0 0 11  
00025: EVENT> bootos.c 317 11385070 AAAAAAAA 0 0 0 11  
00026: EVENT> bootos.c 317 11385070 AAAAAAAA 0 0 0 11  
00027: EVENT> bootos.c 317 11385070 AAAAAAAA 0 0 0 8  
00028: EVENT> bootos.c 317 1121DFF0 AAAAAAAA 0 0 0 8  
00029: EVENT> bootos.c 317 1121DFF0 AAAAAAAA 0 0 0 8  
00030: EVENT> bootos.c 317 1121DFF0 AAAAAAAA 0 0 0 10  
00031: EVENT> bootos.c 317 1121DFF0 AAAAAAAA 0 0 0 8  
00032: EVENT> bootos.c 317 1121DFF8 AAAAAAAA 0 0 0 9  
00033: EVENT> bootos.c 317 1121DFF8 AAAAAAAA 0 0 0 10  
00034: EVENT> bootos.c 317 1121DFF8 AAAAAAAA 0 0 0 10  
00035: EVENT> bootos.c 317 1121DFF8 AAAAAAAA 0 0 0 8  
00036: EVENT> bootos.c 317 1121DFF8 AAAAAAAA 0 0 0 8  
00037: EVENT> bootos.c 317 1121DFF8 AAAAAAAA 0 0 0 8  
00038: EVENT> bootos.c 317 1121DFF8 AAAAAAAA 0 0 0 8  
00039: EVENT> bootos.c 317 1121DFF8 AAAAAAAA 0 0 0 8  
00040: EVENT> bootos.c 317 1121DFF0 AAAAAAAA 0 0 0 10  
00041: EVENT> bootos.c 317 1121DFF0 AAAAAAAA 0 0 0 9  
00042: EVENT> bootos.c 317 1121DFF0 AAAAAAAA 0 0 0 10  
00043: EVENT> bootos.c 317 1121DFF0 AAAAAAAA 0 0 0 45  
00044: EVENT> bootos.c 317 1121DFF0 AAAAAAAA 0 0 0 10  
00045: EVENT> bootos.c 317 1121DFF0 AAAAAAAA 0 0 0 8  
00046: EVENT> bootos.c 317 1121DFF0 AAAAAAAA 0 0 0 8  
00047: EVENT> bootos.c 317 1121DFF0 AAAAAAAA 0 0 0 8  
00048: EVENT> bootos.c 317 1121DFF0 AAAAAAAA 0 0 0 8  
00049: EVENT> bootos.c 317 1121DFF0 AAAAAAAA 0 0 0 9  
00050: EVENT> bootos.c 317 1121DE50 AAAAAAAA 0 0 0 8  
00051: EVENT> bootos.c 317 1121DE50 AAAAAAAA 0 0 0 10  
00052: ERROR> marv_uni.c 768 1121DE50 101A6114 0 0 0 9  
00053: EVENT> bootos.c 317 1121DE50 AAAAAAAA 0 0 0 10  
00054: ERROR> marv_uni.c 768 1121DE50 101A6114 0 0 0 10  
00055: EVENT> bootos.c 317 1121DE50 AAAAAAAA 0 0 0 11  
00056: ERROR> marv_uni.c 768 1121DE50 101A6114 0 0 0 10  
00057: EVENT> bootos.c 317 1121DE50 AAAAAAAA 0 0 0 11  
00058: ERROR> marv_uni.c 768 1121DE50 101A6114 0 0 0 10  
00059: EVENT> bootos.c 317 1121DE50 AAAAAAAA 0 0 0 10  
00060: ERROR> marv_uni.c 768 1121DE50 101A6114 0 0 0 9  
00061: EVENT> bootos.c 317 1121DE50 AAAAAAAA 0 0 0 10  
00062: EVENT> bootos.c 317 1121DE50 AAAAAAAA 0 0 0 10  
00063: EVENT> bootos.c 317 1121DE50 AAAAAAAA 0 0 0 10  
00064: EVENT> bootos.c 317 1121DE50 AAAAAAAA 0 0 0 10  
00065: EVENT> bootos.c 317 1121DE50 AAAAAAAA 0 0 0 10  
00066: EVENT> bootos.c 317 1121DE50 AAAAAAAA 0 0 0 10  
00067: EVENT> bootos.c 317 1121DE50 AAAAAAAA 0 0 0 11  
 


 
jseadrewAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
sgt_bestConnect With a Mentor Commented:
Errors are normal part of a collision domain.  If two packets occur at the same time you get a collision and this is recorded as an error.  The two packets then retry after a random wait.

This is all I could find on the log messages from the NETGEAR Managed Switches Software Administration Manual, Release 8.0.  Could not find a specific error chart.

<130> JAN 01 00:00:06 0.0.0.0-1 UNKN                [0x800023]: bootos.c  (386)         4 %%      Event (0xaaaaaaaa)
Priority Timestamp         Stack ID   Component name Thread ID    Filename Line numb Sequence numb Message

Your error log seems to be a truncated version of the above.  There may be a selection for the log file to be verbose and give more info.  Do you have the latest firmware?

supplemental info on the syslog feature

The Syslog feature: •      Allows you to store system messages and/or errors •      Can store to local files on the switch or a remote server running a syslog daemon •      Method of collecting message logs from many systems
Persistent Log Files •      Currently three - one for each of the last three sessions •      Each log has two parts:
•      Start up log is the first 32 messages after system startup
•      Operational log is the last 32 messages received after the startup log is full •      Files are stored in ASCII format
•      slog0.txt - slog2.txt •      olog0.txt - olog2.txt
Where 0 is for the boot, 1 is for the last boot, 2 is for the boot before that; the third one overflows upon the next boot.
•      Can be saved to local server to monitor at a later point in time The following illustration explains how to interpret log files.

0
 
jseadrewAuthor Commented:
how many times do i have to close or accept the solution to this question????????????????
CLOSE IT ALREADY!!!
0
 
jseadrewAuthor Commented:
thanks for your hep. this is so annoying trying to close a ticket.
0
All Courses

From novice to tech pro — start learning today.