Re: [c-nsp] EOBC0/0 ifInErrors

--- Begin Message --- The EOBC is a proprietary shared bus, and full duplex doesn't exist. Collisions are going to occur, and they can result in receive errors. Overall I wouldn't worry about it unless there are other symptoms. That being said I haven't worked on the Cat6K for a long time

Re: [c-nsp] NPE-G1s don't want to talk to each other over copper?

Actually during auto-negotiation one pair transmits fast link pulses and another pair receives them. The same basic AN protocol is used for 10/100/1000, gigabit just has some additional pages. So gigabit phys generally do support MDI/MDIX as well as auto-mdix, but the need goes away when

Re: [c-nsp] Oversubscription + port groups on WS-X6548-GE-TX

Hi Rolf, There is actually 6G of bandwith, 1G for each group of eight ports. I have pasted some information from the 12.2SX release notes about this card. Regards, Jim Product ID (append = for spares) Product Description Minimum Software Versions WS-X6548-GE-TX WS-X6548V-GE-TX

Re: [c-nsp] Cisco 6509-E with SUP32 and WS-X6148A-GE-45AF, interfaces flapping

Hi Renelson, Does this happen in the mornings in particular? We have seen a number of NIC cards that drop link speed down to 10mbps during the night to save power. Then in the mornings when everyone logs in the NIC cards go back to 1G operation and it causes lots of flaps. Regards, Jim

Re: [c-nsp] Cisco 6509e with PoE

Hi Wil, That inline power daughter card only supports Cisco proprietary inline power detection, it doesn't support 802.3af. Do you know if the wireless controller supports Cisco proprietary? Regards, Jim -Original Message- From: cisco-nsp-boun...@puck.nether.net

Re: [c-nsp] Cisco 6509e with PoE

Changing the config won't help the situation. The card can't tell that there is a powered device connected so it won't apply power. Jim -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Matlock, Kenneth L Sent: Wednesday,

Re: [c-nsp] Fun problem affecting only even-numbered ports

Actually on this card one Janus handles the even ports, and the other handles the odd ports. Jim -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Ben Lovell (belovell) Sent: Thursday, October 28, 2010 11:38 AM To: John

Re: [c-nsp] full duplex mismatch speed - dynamips

There is no such thing as gigabit half duplex, both link partners transmit on all four pairs simultaneously. So there can't be a duplex mismatch when running at gig. Auto-negotiation has to happen to link up at 1000. If you set a port to 1000 the phy is configured to not advertise 10/100 but it

Re: [c-nsp] full duplex mismatch speed - dynamips

Hi Gary, By bad, you are correct it is in 802.3. Thanks, Jim -Original Message- From: Gary Buhrmaster [mailto:gary.buhrmas...@gmail.com] Sent: Saturday, August 21, 2010 1:08 PM To: Jim Getker (getker) Cc: christopher.mar...@usc-bt.com; and...@2sheds.de; cisco-nsp

Re: [c-nsp] The myths of autonegotiate vs forced

The 6K gigabit copper ports support speed auto 10 100. Jim -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Peter Rathlev Sent: Friday, August 20, 2010 3:45 AM To: cisco-nsp@puck.nether.net Subject: Re: [c-nsp] The myths

Re: [c-nsp] The myths of autonegotiate vs forced

Well one problem with that is that a port configured to auto-negotiate can only link up in half duplex the link partner is configured as fixed speed. This is called parallel detection. The phy is transmitting fast link pulses (FLP's). On the receive side it can detect FLP's, MLT3 coding for

Re: [c-nsp] The myths of autonegotiate vs forced

We just didn't see a need to support 10 and 100 individually. There is no standard regarding this as far as I know. Jim -Original Message- From: Peter Rathlev [mailto:pe...@rathlev.dk] Sent: Friday, August 20, 2010 4:36 PM To: Jim Getker (getker) Cc: cisco-nsp@puck.nether.net Subject