Here at work we are migrating our Novell system to a cluster. We had a power loose to one of the switches and previous configs were not saved. When I went to plug into the console port the network went down. The switch reverted back to a previous ip address that our new servers were using. I reconfigured the switch with a new address and every thing works sort of. Our Network Manager believes the switch is the culprit for intermittent problems and that we need to get it replaced. How do you know when a switch is actually going south?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Failing Catalyst 3548 1
- Thread starter gsplsingr
- Start date
- Thread starter
- #3
-
1
- #4
Well you have to rule out physical layer type problems first if the switch is not showing any problems in the logs . Look for speed and duplex issues first , look at the uplinks for errors . If switch is set as auto then nics must be set as auto . If you hardcode the switch speed/duplex settings you must do the same for the clients . Do extended pings off the switch and see if you are seeing any dropped packets to other parts of you network . Without actual proof the switch is the problem you may be wasting your money .
- Status
Similar threads
- Locked
- Question