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 Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Collisions
- Thread starter Valhalla
- Start date
Solarwinds doesnt have a sniffer but it can query via SNMP the various ports and counters to see where the problems are.
You need to understand how networks and collision zones work. The collision zone on the router's E0/0 port will be between E0/0 and the next switch on that segment. No further.. Collisions are stopped at the switch since it's layer2 issue. Broadcasts on the other hand will traverse the entire network.
router--collision zone--switch---switch, server etc
IF you have a high count of collisions on the segment, I would look at misconfiguration of full duplex, I would turn OFF autoneg on the 10/100 ports and lock down manually, check the cabling for any pinching or other damage.
Since the router more then likely has a straight shot to the switch.. it's fairly easy to figure out.
With all that said, if you have HUB on the router, now life gets ugly as a hub doesn NOT break up the collision zones. And if you do have a hub feeding the route, I would highly recommend trotting down to your local network supply house and get a cheapo switch for starters so you can break up the collision zone.
MikeS
"Diplomacy; the art of saying 'nice doggie' till you can find a rock" Wynn Catlin
You need to understand how networks and collision zones work. The collision zone on the router's E0/0 port will be between E0/0 and the next switch on that segment. No further.. Collisions are stopped at the switch since it's layer2 issue. Broadcasts on the other hand will traverse the entire network.
router--collision zone--switch---switch, server etc
IF you have a high count of collisions on the segment, I would look at misconfiguration of full duplex, I would turn OFF autoneg on the 10/100 ports and lock down manually, check the cabling for any pinching or other damage.
Since the router more then likely has a straight shot to the switch.. it's fairly easy to figure out.
With all that said, if you have HUB on the router, now life gets ugly as a hub doesn NOT break up the collision zones. And if you do have a hub feeding the route, I would highly recommend trotting down to your local network supply house and get a cheapo switch for starters so you can break up the collision zone.
MikeS
"Diplomacy; the art of saying 'nice doggie' till you can find a rock" Wynn Catlin
Full duplex disables the sense-then-send feature of the ethernet transmit function. It just assumes that there are dedicated Tx/RX channels so it doesn't worry about the Tx pair having a packet on it to collide with. Oddly enough they do still happen but I've always assumed that any damage to the packet as it traverses the line is treated as a collision for simplicity.
Fiber runs are obviously dedicated Rx/Tx and I have yet to see a collision counter increment on one.
The benefit to full duplex is:
half duplex - only one side can speak at a time (like a walkie talkie)
full duplex - both sides can speak independently (like a telephone) which sort of doubles the capacity of the line.
----------------------------------------
Wassabi Pop Tarts! Write Kellogs today!
Fiber runs are obviously dedicated Rx/Tx and I have yet to see a collision counter increment on one.
The benefit to full duplex is:
half duplex - only one side can speak at a time (like a walkie talkie)
full duplex - both sides can speak independently (like a telephone) which sort of doubles the capacity of the line.
----------------------------------------
Wassabi Pop Tarts! Write Kellogs today!
- Status
Similar threads
- Locked
- Question