Great sentiment - love it (Not). You have posted this problem to the
'bay-networks' newsgroup several times now in the hope of getting an answer.
You also stated that you purchased this switch with port 6 not working, you
defaulted it and you enabled the extended diagnostics. It now 'hangs' after
failing on port 6.
I'm not saying that it is an ideal situation to be in (you should be able to
cancel the tests), but this is a situation of you own doing. You have
bought a unit second-hand, with no warranty or support and, probably, from
E-Bay or somewhere similar. You cannot expect to get the same level of
support from Bay / Nortel / whoever that you would if you paid full-price
for a new model with a support contract. If you had done this then you
could just RMA the unit and get a new one.
Sorry for the rant, but I get fed up of people here and on the Nortel / Bay
/ Cisco etc groups bitching because they can't get something for nothing!!
Simon
"Ian" <i...@networkninjas.net> wrote in message
news:3B90B4AC...@networkninjas.net...
> Maybe they wouldn't suck so bad if Nortel hadn't have bought them out,
> otherwise I might be able to get some support for my stupid disabled
switch.
>
> Problem: I can't turn off extended boot-time diagnostics because my
Baystack
> 302T switch hangs on port 6, which I know is messed up, but the switch
works
> just fine without it. Had I not turned on the extended diagnostics, I
would
> have a working switch (minus the sixth port, oc).
>
> If someone, ANYONE has any sort of suggestion as to how I can recover this
> switch, suggest away, because I'm about ready to pitch the stupid thing
out
> the window. Physically abusing it doesn't seem to reset the config
either... :)
>
> ~Ian
Hmmm that's odd, I've only posted this here once. I posted it twice to
comp dcom lans ethernet, then realized that there was this whole
lovely comp dcom sys bay-networks and nortel. So I posted it to those
groups as well since it was far more on topic here. Sorry about the
cross-posting
> You also stated that you purchased this switch with port 6 not working, you
> defaulted it and you enabled the extended diagnostics. It now 'hangs' after
> failing on port 6.
Well at least you read part of my post before flaming me
>
> I'm not saying that it is an ideal situation to be in (you should be able to
> cancel the tests), but this is a situation of you own doing. You have
> bought a unit second-hand, with no warranty or support and, probably, from
> E-Bay or somewhere similar. You cannot expect to get the same level of
> support from Bay / Nortel / whoever that you would if you paid full-price
> for a new model with a support contract. If you had done this then you
> could just RMA the unit and get a new one.
And I haven't asked for the same level of support, since I don't
believe this is a group run by nortel/bay. Correct me if I'm wrong (I
know you will).
I'm not expecting anything, I just posted a f***ing question to a
newgroup. I have no right to expect any reply to my question. On the
other hand, I can ask away with hope that someone will reply. Yeah,
had I paid whatever today's going price for one of these is, I would
totally expect support. But I didn't, and I can probably live with my
horrible horrible decision. "Gee," I thought, "maybe someone in the
BAY NETWORKS group would know something about my problem."
It's not like I haven't scoured the web and all of usenet regarding
this. I don't usually ask questions in newsgroups, and if I do it's
because I've exausted all of my other options. Some of us like to
learn about networking and computers, and don't want/need to spend
thousands of dollars on equipment. A switch with one non-working port
is just fine for this application, it also happens to work well for
running a small home net. All I'm trying to do is learn how to fix the
problem, and you seem to have (you guessed it) a problem with that.
Sorry for the sucks statement, that was totally rude and unnecassary,
and I apologize for that. However, I don't apologize for asking for
help.
OK - no wars here!! I have no problem with people asking questions. If I
did then I would be in the wrong as this is half the reason for newsgroups
(the other half being for answers) ;-}
What got my hackles up (and those of a few others given the direct mails
I've had) was the comment about Bay Networks Sucking just because you
couldn't get anywhere with this switch. If I knew the answer as to how to
help you I would do so - unfortunately I don't. I honestly believe that you
have probably 'killed' the switch for good by what you did.
If I do find out an answer I will let you know, but don't hold your breath.
Simon
"Ian" <i...@networkninjas.net> wrote in message
news:e0f5969c.01090...@posting.google.com...
Just to show I'm not an ogre I've even asked Nortel for some tech-support on
this issue. They can't make any suggestions (response is below);-
"In regards to this case there are a few possibilities. This is pretty
obvious, but all the same make sure nothing is in port 6 so that it isn't
detecting a port connectivity failure. If it is sill locking up on port 6
you can try this, which works with some of the older models. If you unplug
the power cable from the switch, it may reset to factory default. Do note
that this only works with some of the older models. If this is unsuccessful
we will have to RMA the switch to resolve the issue. Let me know if this
helps"
The only thing I can think is (as you've got nothing to lose) to take the
case apart and see if there is a battery keeping the config alive. This
might be a way to recover it, but I wouldn't count on it.
Do you have any friends in the industry who have a company support contract
with Nortel?
Simon
"Ian" <i...@networkninjas.net> wrote in message
news:e0f5969c.01090...@posting.google.com...