- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Recreating Late collisions
Operating System - HP-UX
1755653
Members
3125
Online
108837
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-15-2008 08:07 PM
12-15-2008 08:07 PM
Recreating Late collisions
HP OpenCall faces an issue with one of our customers wherein we saw a very high late collision count. The HPUX build is 11iv1. From the lanadmin output the Duplex mode seems to be HDplx, with Auto Nego. set to ON.
Here is the lanadmin output.
PPA Number = 3
Description = lan3 HP A5506B PCI 10/100Base-TX 4 Port [100BASE-TX,HD,AUTO,TT=
Type (value) = ethernet-csmacd(6)
MTU Size = 1500
Speed = 100000000
Station Address = 0x306e25947d
Administration Status (value) = up(1)
Operation Status (value) = up(1)
Last Change = 478
Inbound Octets = 2985218406
Inbound Unicast Packets = 1539151128
Inbound Non-Unicast Packets = 1922516
Inbound Discards = 0
Inbound Errors = 0
Inbound Unknown Protocols = 84
Outbound Octets = 4127381116
Outbound Unicast Packets = 2724403576
Outbound Non-Unicast Packets = 295857
Outbound Discards = 0
Outbound Errors = 0
Outbound Queue Length = 0
Specific = 655367
Ethernet-like Statistics Group
Index = 3
Alignment Errors = 0
FCS Errors = 0
Single Collision Frames = 50396204
Multiple Collision Frames = 1699987
Deferred Transmissions = 80177595
Late Collisions = 35657510
Excessive Collisions = 0
Internal MAC Transmit Errors = 0
Carrier Sense Errors = 0
Frames Too Long = 0
Internal MAC Receive Errors = 0
We are trying to recreate a similar scenario in lab for tests etc. But I am not sure how can we recreate the late collisions. I can see collision frame counts while configuring the host in AUTO_NEG ON, and setting the switch port to HD and pumping some traffic through this interface. However, no late collisions could be seen so far. From hp docs page ( http://docs.hp.com/en/J5683-90017/apds01.html ), late collisions is defined to be "the number of times that a collision is detected on a particular interface later than 512 bit-times into the transmission of a packet". In what all scenarios we can see collision on the same packet after 512 bit-time.
Here is the lanadmin output.
PPA Number = 3
Description = lan3 HP A5506B PCI 10/100Base-TX 4 Port [100BASE-TX,HD,AUTO,TT=
Type (value) = ethernet-csmacd(6)
MTU Size = 1500
Speed = 100000000
Station Address = 0x306e25947d
Administration Status (value) = up(1)
Operation Status (value) = up(1)
Last Change = 478
Inbound Octets = 2985218406
Inbound Unicast Packets = 1539151128
Inbound Non-Unicast Packets = 1922516
Inbound Discards = 0
Inbound Errors = 0
Inbound Unknown Protocols = 84
Outbound Octets = 4127381116
Outbound Unicast Packets = 2724403576
Outbound Non-Unicast Packets = 295857
Outbound Discards = 0
Outbound Errors = 0
Outbound Queue Length = 0
Specific = 655367
Ethernet-like Statistics Group
Index = 3
Alignment Errors = 0
FCS Errors = 0
Single Collision Frames = 50396204
Multiple Collision Frames = 1699987
Deferred Transmissions = 80177595
Late Collisions = 35657510
Excessive Collisions = 0
Internal MAC Transmit Errors = 0
Carrier Sense Errors = 0
Frames Too Long = 0
Internal MAC Receive Errors = 0
We are trying to recreate a similar scenario in lab for tests etc. But I am not sure how can we recreate the late collisions. I can see collision frame counts while configuring the host in AUTO_NEG ON, and setting the switch port to HD and pumping some traffic through this interface. However, no late collisions could be seen so far. From hp docs page ( http://docs.hp.com/en/J5683-90017/apds01.html ), late collisions is defined to be "the number of times that a collision is detected on a particular interface later than 512 bit-times into the transmission of a packet". In what all scenarios we can see collision on the same packet after 512 bit-time.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-16-2008 12:50 AM
12-16-2008 12:50 AM
Re: Recreating Late collisions
Hello,
It is almost certain that the port on the
switch/router end is set not to auto-negotiate.
Most of the time, late collisions are
caused by different settings on the server
and switch/router side.
Your problem sounds like a duplex and/or auto-negotiate mismatch between the server
and the switch/router port.
What you set on the HP-UX server side
is only one half of the set up. Check
the other side of the link.
Cheers,
VK2COT
It is almost certain that the port on the
switch/router end is set not to auto-negotiate.
Most of the time, late collisions are
caused by different settings on the server
and switch/router side.
Your problem sounds like a duplex and/or auto-negotiate mismatch between the server
and the switch/router port.
What you set on the HP-UX server side
is only one half of the set up. Check
the other side of the link.
Cheers,
VK2COT
VK2COT - Dusan Baljevic
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP