T.R | Title | User | Personal Name | Date | Lines |
---|
3754.1 | I believe these are un-solicited resets.... | NETCAD::BATTERSBY | Don't use time/words carelessly | Mon Jul 29 1996 15:49 | 19 |
| RE: the 20624 resets
>> 39 days 03:06:25 20624 resets
I believe these 20624 are the results of un-solicited resets.
>>SysUpTime : 254 days 03:59:54 5 resets
These 5 resets are the ones that fall into the category of
management resets.
I went out to the lab and checked out a DEFBA, noticed some qty of
what I believe are un-solicited resets. I did a reset-to-factory
settings and all of these dissappeared. Of course I had to
re-configure my IP address, subnet mask, default gateway, but I
did verify that those resets I believe are a running count of the
un-solicited variety do get cleared out.
Bob
|
3754.2 | Un-solicited resets ? | PHHSS1::DMIGNOGNA | | Tue Jul 30 1996 10:01 | 9 |
| Thank you,
Do you know what the impact to the ring is by the having un-solicited resets?
Is there something on the ring that we should be worried about?
or the big question - what causes a un-solicited reset....
Don...
|
3754.3 | More on un-solicited resets... | NETCAD::BATTERSBY | Don't use time/words carelessly | Tue Jul 30 1996 11:01 | 26 |
| By the ring, I assume you mean an FDDI ring configuration that
the switch is part of. Perhaps more insight as to the configuration
this particular switch is in might be helpful. So if you could
provide a configuration or word description of the configurations
of both the FDDI port config, and the Ethernet port configurations,
it might prove useful.
The un-solicited resets are resets to the switch other than those
done on purpose as a management command from either the switch
console interface or as a remote management reset from
HUBwatch/clearVISN. The un-solicited resets might be crashes, or
fault detection by the switch firmware of a condition that is not
interpreted as a soft failure, or as a recoverable failure. These
type of resets could also be caused by some systemic problem with
the hardware logic, such as an overtemp condition (would have to
be a red overtemp to cause a hardware reset), or some problem with
the power up logic, or even an intermittent +5v short somewhere on
one of the logic boards inside. These are examples of things that
might cause an un-planned (un-solicited) reset.
I don't know of any known problems hardware/firmware that would
result in un-solicited resets occuring.
The impact on the FDDI ring this switch is connected to is that
each time the switch resets, the ring would be disrupted long
enough for the ring to wrap itself, and would be disrupted again
when the switch came back up to re-connect itself to the ring.
Bob
|
3754.4 | re .2 | NPSS::RAUHALA | | Tue Jul 30 1996 13:33 | 3 |
| I would not worry too much about this, the last reset was 254 days ago!
You can enter choice #5 on the menu to dump the error log.
|
3754.5 | re .4 | NETCAD::BATTERSBY | Don't use time/words carelessly | Tue Jul 30 1996 14:11 | 4 |
| Isn't it 39 days?
Isn't the 254 days for the last time a management reset occured?
Bob
|
3754.6 | Hub/ring config. | PHHSS1::DMIGNOGNA | | Tue Jul 30 1996 16:08 | 30 |
|
Prison Campus has 33 Hub900's on a FDDI ring . All of the switches show this
high number of resets, Each hub900 is attached to a UPS
If I understand what you said about the un-solicited reset correctly I am
concerned that the FDDI ring is wrapping and un-wrapping intermittently
throughout the day.
Does the reset have to be generated on the Hub the switch it is connected to
or could a one device located in another hub affect every switch on the ring?
Hub900 configuration:
Slot 8 DECswitch 900EF
Slot 7 DECrepeater 900TM or 90TS (In-band Agent)
Slots 6 - 4 could have additional repeaters or DECserver 900TM or 90M
Revision Levels
Hub900 HW=F, RO=v1.1.6, SW=v4.1.0
DECswitch HW=v1/2, RO=v0.4, SW=v1.5.2
Rep. 90TS HW=v3, RO=v01.00 SW=v2.0.0
Rep. 900TM HW=v3, RO=v01.04 SW=v2.0.0
Management PC = Hubwatch Ver 4.1.1
Don Mignogna - Network Services
dtn 328-3045
|
3754.7 | Some additional elaboration on the network is needed.... | NETCAD::BATTERSBY | Don't use time/words carelessly | Tue Jul 30 1996 16:30 | 13 |
| >> Slot 8 DECswitch 900EF
???
What are the other components of the FDDI configuration
that this DECswitch is connected to?
Is part of the fddi ring on the HUB backplane, or is all
external out the front of the DECswitch?
What protocols are being used in this setup?
What kind of end nodes are being used in this network?
Is this a client/server environment?
Can't conjecture on things without more information.
-
|
3754.8 | I don't think there is a real problem here | NPSS::RAUHALA | | Tue Jul 30 1996 16:36 | 13 |
| SysUpTime is 254 days which is how long it's been running since
last reset. If there was a problem, it looks like it went away
with V1.5.2
The 39 days is how long the switch was running just before being
loaded with the v1.5.2 image.
Given that it takes about 2 minutes for the switch to go thru the
reset cycle (run diags and come back up) 20624 resets is 41248 minutes
or about 29 days strait of doing nothing but crashing and resetting.
I suspect it's some kind of software bug with this reset counter and
you really did not have 20624 resets.
|
3754.9 | additional info | PHHSS1::DMIGNOGNA | | Tue Jul 30 1996 17:36 | 34 |
| This site is all digital equipment products
>> What are the other components of the FDDI configuration
that this DECswitch is connected to?
FDDI ring consists of 33 DEFBA-MA DAS attached and 3 DEF6X-MA DAC attached
two DEF6X's have Bay Networks routers DAS attached and the other one is
used to serve the AXP2100 - SAS attached.
>> Is part of the fddi ring on the HUB backplane, or is all
external out the front of the DECswitch?
All but 3 DEFBA's are external of hub - where the DEF6X's are we have the
FDDI Ring entering the DEF6X A port - Backplane - exiting DEFBA B port
>> What protocols are being used in this setup?
Ring Preformance - Total peak utilization 6%, average <1% util.
Average Frames size 191, Average Token Rot. 150us
Protocol distribution - 53% IBM NB, 22% IP, 11% decnet, 6% MAC/SMT
Pathworks 5.1 - LAT 5.2 - REFLECTIONS Ver 4 (TELNET)
>> What kind of end nodes are being used in this network?
2 AXP2100 servers SAS to DEF6X, (Cluster has its own FDDI ring), PC's are
DEC Venturis with etherworks 3 NIC's attached 10baseT to repeaters.
>>Is this a client/server environment?
Not yet... but will be.
|
3754.10 | anymore ideas? | PHHSS1::DMIGNOGNA | | Tue Aug 06 1996 10:12 | 3 |
| Do you have anymore ideas....
Don...
|
3754.11 | No sign of anything actually broken.... | NETCAD::BATTERSBY | | Tue Aug 06 1996 10:47 | 8 |
| From the supplied information, it doesn't sound like there
is a systemic problem or something actually broken.
Outside of the reset numbers, there hasn't been a specific
problem stated or mentioned. Like Ken said, if there isn't
anything else broken, and things seem to be working fine,
I wouldn't be concerned with the reset numbers.
Bob
|
3754.12 | | NPSS::RAUHALA | | Tue Aug 06 1996 11:00 | 7 |
| for starters you can dump the error log, choice #5 on the menu.
This can give some insight into why it crashed.
Of course you have been running for 254 days without a reset,
and before loading the current image you had been running for
39 days, so whatever problem you had before is not there now.
In this case the error log might provide some info.
ken
|
3754.13 | Something is broken somewhere | PHHSS1::DMIGNOGNA | | Tue Aug 06 1996 11:05 | 15 |
| We are having problems at this site ..Please reference note 3668
Also the customer is requesting an answer on the reset question, since
they brought it to my attention.
Their network manager has seen a high retransmission rate on tcp/ip and
intermittent LAT disconnects, I am trying to define this problem now
with them
I am concerned that the ring is wrapping and unwrapping through
out the day. If this is the case then it would account for the
intermittent LAT disconnects and high retransmit rate. So the question
of why the high reset count and what does it mean becomes important.
Don...
|
3754.14 | anymore ideas | PHHSS1::DMIGNOGNA | | Tue Aug 13 1996 11:23 | 5 |
| If there is documentation I can review that can help me resolve these
questions, I would greatly appreciate it.
Thanks,
|
3754.15 | | NPSS::WADE | Network Systems Support | Tue Aug 13 1996 13:22 | 26 |
| I'm not sure what the large number of resets means.
>Status of Last Downline Upgrade : TFTP Write
> 39 days 03:06:25 20624 resets
But, if you want help with this I need -
A complete network map detailing the FDDI and Ethernet devices,
media types and DEChub configurations.
Description of the traffic problems seen and points in the
configuration that are impacted.
Listing of the current config and errror logs for all DEChubs and
all hub modules.
Regarding the FDDI ring wraps:
Using an FDDI analyzer you can determine pretty quickly the state
of the ring, get a ring map and monitor events (wraps) on the ring.
Bill
|