ETHERNET CABLES
When using ethernet for hooking up streaming devices and dacs, what cat level of ethernet cable should be used. Is there any sonic improvement by going to a higher dollar cat 7 or 8 cable?
@nonoise again, all noise. a lot of very bombastic noise. I'll just ask this one last time, again.
Your claim, explain how that refutes anything I have said. The article does not address the electrical signal. Or just go away. Your noise is unnecessary. |
In general, just to show how small of an issue this is, my primary switch has an uptime of 82 days, and transmitted somewhere upwards to 3.3 billion packets in total, with 0 packets lost. Physical interface: ge-1/0/11, Enabled, Physical link is Up Interface index: 140, SNMP ifIndex: 537, Generation: 143 Link-level type: Ethernet, MTU: 1514, Speed: Auto, Duplex: Auto, BPDU Error: None, MAC-REWRITE Error: None, Loopback: Disabled, Source filtering: Disabled, Flow control: Enabled, Auto-negotiation: Enabled, Remote fault: Online, Media type: Copper, IEEE 802.3az Energy Efficient Ethernet: Disabled Device flags : Present Running Interface flags: SNMP-Traps Internal: 0x4000 Link flags : None CoS queues : 8 supported, 8 maximum usable queues Hold-times : Up 0 ms, Down 0 ms Current address: f0:1c:2d:b8:71:8e, Hardware address: f0:1c:2d:b8:71:8e Last flapped : 2015-03-02 21:43:05 CST (9w1d 10:11 ago) Statistics last cleared: Never Traffic statistics: Input bytes : 3322860227030 0 bps Output bytes : 247916852449 608 bps Input packets: 2475795752 0 pps Output packets: 818652044 0 pps IPv6 transit statistics: Input bytes : 0 Output bytes : 0 Input packets: 0 Output packets: 0 Egress queues: 8 supported, 4 in use Queue counters: Queued packets Transmitted packets Dropped packets 0 best-effort 0 814627347 0 1 assured-forw 0 0 0 5 expedited-fo 0 0 0 7 network-cont 0 4024698 0 Queue number: Mapped forwarding classes 0 best-effort 1 assured-forwarding 5 expedited-forwarding 7 network-control Active alarms : None Active defects : None MAC statistics: Receive Transmit Total octets 3322860227030 247916852449 Total packets 2475795752 818652044 Unicast packets 2475079840 814621375 Broadcast packets 12 5972 Multicast packets 715900 4024697 CRC/Align errors 0 0 FIFO errors 0 0 MAC control frames 0 0 MAC pause frames 0 0 Oversized frames 0 Jabber frames 0 Fragment frames 0 Code violations 0 Autonegotiation information: Negotiation status: Complete Link partner: Link mode: Full-duplex, Flow control: Symmetric, Remote fault: OK, Link partner Speed: 1000 Mbps Local resolution: Flow control: Symmetric, Remote fault: Link OK Packet Forwarding Engine configuration: Destination slot: 0 (0x00) CoS information: Direction : Output CoS transmit queue Bandwidth Buffer Priority Limit % bps % usec 0 best-effort 95 950000000 95 NA low none 7 network-control 5 50000000 5 NA low none
2200-C> show system uptime 8:55AM up 82 days, 22:57, 1 user, load averages: 0.09, 0.15, 0.10 |
Does oversubscription, errors and excessive delay cover that? The article makes it clear that it occurs and needs to be monitored. Any how....members here do hear a difference, for the better, all the while ignoring your advice. Now. practice what you preach, and just go away. Put down that bottle, or battle flag you carry around and get a life. All the best, |
@nonoise No, not at all. Explain how a cable fixes any of these. I am very curious have a cable will fix these, especially oversubscription and excessive delay (article mentions 2 seconds). Please go on, show us that you know what you are talking about. |
