T.R | Title | User | Personal Name | Date | Lines |
---|
1316.1 | Use Firmware Version 1.1 when it becomes available | NACAD::PAGLIARO | Rich Pagliaro, Hub Products Group | Tue Aug 16 1994 19:26 | 46 |
| >> I guess,
>>
>> repeaters were not crash form repeater's dump error log .
>> (there are seviral entry, but these entry time stamp all zero.)
>>
This is an incorrect assumption. The DECrepeater 900TM firmware
version 1.0G does not put correct time stamp information in the error
log entries. Please enter error log information here to provide more
of a clue as to what is really happening.
>> module environment are warm place. but not hot condition.
>> about 35 degree below under module temperature.
I doubt that you are experiencing an over-temperature condition. The
DECrepeater 900TM actually powers itself down when it gets too hot.
>> I want know,
>>
>> A. The way of dump error log reset operation each modules.
The only way to dump repeater error log entries is from the setup menu.
When in a hub this is accomplished via the hub manager's redirect mode.
>> B. The simple way of repeater's uptime .
>> (Bridge900 and Concent900's uptime can get "show current setting"
>> in hub manager menu redirect mode, but repeater uptime can't get
>> the same way.)
DECrepeater 900TM firmware version 1.0G does not display the repeater's
up time from the "show current settings" screen. One way to read the
module's up time is from the HUBwatch module summary screen. Repeater
firmware version 1.1 *WILL* show the up time from the "show current
settings" screen.
Again, please enter your error log entries to help us find the reason
for your module crashes. DECrepeater 900TM firmware version 1,1 is
scheduled to be submitted to SSB some time at the end of this month.
It fixes a number of known bugs which cause module crashes.
Regards,
Rich
|
1316.2 | repeater idle time | TKTVFS::OHTSUKA_MU | | Tue Aug 23 1994 11:18 | 51 |
|
Hi! Rich. Thank you for your quick response.
>> I want know,
>>
>> A. The way of dump error log reset operation each modules.
> The only way to dump repeater error log entries is from the setup menu.
> When in a hub this is accomplished via the hub manager's redirect mode.
I want know the way of dump error log "CLEAR ENTRY" operation.
If I can clear dump error log entry, I decide new error log entry
is entry of reset operation or not.
I got a few information for this repeater problem .
Customer had P.M. for ac POWER SYSTEM. (8/20&21)
Both time, all DEChub900 were powered down except hubs in machine room.
( M.R. suppled power from UPS system)
And power on, DEChub900 and many hub modules reset UPTIME counter at same time.
Today (8/23) I checked all hub module's uptime by DECmcc.
15 hub system keeped alive on power down hour,and got a few
feature below .
a. 14 repeater's UPTIME count were smaller than DECbridge on same
HUB. ( It seems repeater reseted)
b. 15 hub supplied power in good air condition environment.
c. 2 repeater were reseted when I access HUB management port.
When I selected redirect mode( menu 13) and input slot number of
repeater, HUB did'nt respond about 10 second and display " module
not response" . This timing, repeater operated reset that sence by
LED. These repeater were connected no network device.
I think,
When DECrepeater900 had many idle time, DEChub900 don't keep
connect to DECrepeater900 correctly.
When DEChub900 is requested access of repeater on flexible channel
thinwire, it doesn't get correct repeater response and reset occur.
I hope any information !!
Thank you.
|
1316.3 | How old is a log entry? ANSWER | NACAD2::SLAWRENCE | | Wed Aug 24 1994 12:23 | 31 |
|
You can read the error logs using the pcomErrLog group in the DEChub
public common MIB.
You can also use the pcomEsys group in that same MIB to read separate
counters for Management Resets, Power Ups, and Unsolicited Resets (a
polite term for 'crashes').
In that version of the repeater error logs, the timestamps are always
zero, so ignore them. The total reset count in the log entry is
correct, however - by comparing it to the total of the three counters
above, you can tell whether or not the most recent log entry (which
will always be the first entry returned in the table) was also the most
recent reset:
IF ( ( pcomEsysMgmtResets
+ pcomEsysPowerUps
+ pcomEsysUnsolicitedResets
)
== pcomErrLogResetCount
THEN
the error log entry was a crash that happened since the last
management reset or power cycle of the device
This works for everything that supports these objects.
There is new firmware coming soon for these repeaters that does fix
some problems that can cause crashes; if you can get the error log
entries with SNMP and send them or post them here, we'll be able to
tell if you have one of those problems or something new.
|
1316.4 | errorlog entry of 8 REPEATERS | TKTVFS::OHTSUKA_MU | | Fri Aug 26 1994 01:05 | 67 |
|
I can get errorlogs of 8 repeaters below, because these repeaters look like
re-reset to compare uptime. I compare errorlog past entry and present one
of each hub. Entry increase one by one each hub.
Can I get more information ?
Thanks.
AP01.LOG;1
Entry = 4
Time Stamp = 0 0
Reset Count = 0
Bus/Addr write exc. @20035h, PC=245F88h
AT01.LOG;1
Entry = 2
Time Stamp = 0 0
Reset Count = 0
Bus/Addr write exc. @BEC3FB0Ch, PC=24621
BF01.LOG;1
Entry = 2
Time Stamp = 0 0
Reset Count = 0
Bus/Addr read exc. @9h, PC=241470h
DC01.LOG;1
Entry = 6
Time Stamp = 0 0
Reset Count = 0
Bus/Addr read exc. @Dh, PC=241470h
FG01.LOG;1
Entry = 2
Time Stamp = 0 0
Reset Count = 0
Bus/Addr read exc. @7h, PC=246744h
FI01.LOG;1
Entry = 3
Time Stamp = 0 0
Reset Count = 0
Bus/Addr read exc. @C00F30B9h, PC=24678A
FJ01.LOG;1
Entry = 3
Time Stamp = 0 0
Reset Count = 0
Bus/Addr read exc. @23CE89h, PC=245FDEh
PF01.LOG;1
Entry = 2
Time Stamp = 0 0
Reset Count = 0
Bus/Addr read exc. @23CE89h, PC=245FDEh
|
1316.5 | available new image DETMM ? | TKTVFS::OHTSUKA_MU | | Fri Sep 02 1994 01:47 | 6 |
|
Can I get new DETMM image and release note ?
If new image available, where are there directory ?
|
1316.6 | See note 1368.0 | ROGER::GAUDET | Because the Earth is 2/3 water | Fri Sep 02 1994 08:54 | 1 |
|
|
1316.7 | DECrepeater900TM v1.1 on DEChub900 v3.0 | TKTVFS::OHTSUKA_MU | | Wed Sep 14 1994 04:16 | 15 |
| Can I use DECrepeater900 TM F/W V1.1 on DEChub900 v3.0.0?
DECrepeater900TM V1.1 require on DEChub900 V3.0.0. but
there are up to 100 DEChub900s in cutomor and I must consump
many update time.
I want update 2 phase.
phase1. DECrepeater900TMs only update to V1.1
If it sucess stop to repeater crash
phase2. DEChub900 f/w and DECbridge900 and DECconcent900
f/w update
|