Damaged Error With 0.48 Test 2 Compiled For Mac
Sep 12, 2018 - Apart from creation errors, I'm not seeing this issue in either 0.48-2, a custom 0.49-0 I. That I got the wrong tcl version, I can't even use deken when I compile it. Patch, the abstraction gets corrupted somehow and the same errors start. Porres changed the title from pd 049-test2 tcl crash (macOS) to pd. Stack Exchange network consists of 174 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers. Visit Stack Exchange.
Attention, Internet Explorer User Announcement: Jive has discontinued support for Internet Explorer 7 and below. In order to provide the best platform for continued innovation, Jive no longer supports Internet Explorer 7. Jive will not function with this version of Internet Explorer. Please consider upgrading to a more recent version of Internet Explorer, or trying another browser such as Firefox, Safari, or Google Chrome. (Please remember to honor your company's IT policies before installing new software!).
Mohamed When auto-negotiation is disabled on one switchport the switch at the other end of the link can use the Parallel detection function to determine the speed. Put simply the switch does not negotiate the speed with the other switch but it can still work it out.
However what it cannot work out without auto-negotiation is the duplex. Now as far as i know 10/100 ethernet interfaces default to half-duplex and gigabit interfaces default to full duplex. So you could interprete this to mean the port would set itself to 100 Full because of it's default setting is gigabit. But i think that would be wrong. Once the port has negotiated down to 100Mbps it then has to default to half-duplex because that is all it can do safely as Edison says.
John, Thanks for your reply and clarification. You said: ((When auto-negotiation is disabled on one switchport the switch at the other end of the link can use the Parallel detection function to determine the speed.
Put simply the switch does not negotiate the speed with the other switch but it can still work it ou)). I was refering to this point, as long as the other swith port speed sets to 100, the other switch negotiate it Or in a correct way it uses the parallel detection function of the other port speed. Thats why it becomes 100 Mbps port. However, when I said its duplex of full, I didnt mean negotiating a duplex, but rather it defaults to its Full duplex settings becuse its a GIG Interface. I still dont understand why the Gig port becomes half duplex in this situation? Do you have any reference for that?
Damaged Error With 0.48 Test 2 Compiled For Mac Free
Mohammed However, when I said its duplex of full, I didnt mean negotiating a duplex, but rather it defaults to its Full duplex settings becuse its a GIG Interface. Yes, i think that's where we interpret it differently but to be honest i can't test it because i don't have any gigabit capable switches handy. You are absolutely correct in that a gig interface defaults to full duplex as i said in my last post. But my understanding is that if the gig interface has to fall back to 100Mbps it must also fall back to half-duplex because of the speed it is running at. However as i said in my last post it really depends on interpretation of 'gig interfaces default to full duplex'. And your interpretation may well be correct and mine wrong. Sarah/All, I was able to test this with 2 3750-E switches.
In this scenario I am using port 1/0/48 on both switches. The switches are called switch B and switch C When I set the duplex to full and speed to 100 on switch C switch B's interface shows 100 Full Here is the config and show command for switch C Switch-C#sh run in gi1/0/48 Building configuration. Current configuration: 63 bytes! Hello Sarah, I may be wrong but my current understanding of auto-negotation is that when it is disabled we actually disable only the modulation of the pulse train with the line code capabilities 16 bit word.
However, even if FLP would be turned off completely (as it looks like in ), the ethernet frames sent by neighbor would provide its real speed (10 vs 100, as I noted 1000 Mbps can be detected by the fact that there would be activity in all 4 pairs not only on two pairs). Each ethernet frame has a 64 bits preamble that is used to synchronize to the frame (there is no framing structure with a permanent clock like in a serial interfaces) so neighbor speed can be sensed in one way or another. Here we have a theorical answer and an empirical answer from Reza's tests. We could say that humility comes from experience: many times theory and practice can give different answers, and only doing a specific test the empiric answer can be found. The test tells us about effective implementation on network devices Be also aware that CDP is Cisco proprietary and in any case also its standard based conteurpart LLDP it is at an upper layer in the OSI stack: a CDP frame is already an ethernet frame with a specific encapsulation (using 802.2 and SNAP with a well known multicast MAC destination) Hope to help Giuseppe. Hello Sarah, if your objective is to perform interoperability tests it is correct to consider Reza's results the sign of an implementation that differs from accepted standards. s why manufactures such as Cisco want to implement auto-negotiation process, clearly defined in 802.3 ab/z differently and cause unexpected results This can be the result of a software programming error just to make an example or of a broad interpretation of standards.
With a valid service contract you could open a service request to TAC. Current best practice for 10/100/1000 is to use autonegotiation at both sides. We see some times that a link to a server can negotiate at 100 Mbps or even at 10 Mbps. The way we deal with these cases is: we try to shut/unshut the port to make the two endpoints to negotiate again, if this doesn't solve we try to change a patch cable (a damaged cable can be the root cause). Hope to help Giuseppe. Mohamed When auto-negotiation is disabled on one switchport the switch at the other end of the link can use the Parallel detection function to determine the speed.
Put simply the switch does not negotiate the speed with the other switch but it can still work it out. However what it cannot work out without auto-negotiation is the duplex. Now as far as i know 10/100 ethernet interfaces default to half-duplex and gigabit interfaces default to full duplex. So you could interprete this to mean the port would set itself to 100 Full because of it's default setting is gigabit.
But i think that would be wrong. Once the port has negotiated down to 100Mbps it then has to default to half-duplex because that is all it can do safely as Edison says. John, Thanks for your reply and clarification. You said: ((When auto-negotiation is disabled on one switchport the switch at the other end of the link can use the Parallel detection function to determine the speed. Put simply the switch does not negotiate the speed with the other switch but it can still work it ou)). I was refering to this point, as long as the other swith port speed sets to 100, the other switch negotiate it Or in a correct way it uses the parallel detection function of the other port speed.
Thats why it becomes 100 Mbps port. However, when I said its duplex of full, I didnt mean negotiating a duplex, but rather it defaults to its Full duplex settings becuse its a GIG Interface. I still dont understand why the Gig port becomes half duplex in this situation? Do you have any reference for that? Mohammed However, when I said its duplex of full, I didnt mean negotiating a duplex, but rather it defaults to its Full duplex settings becuse its a GIG Interface. Yes, i think that's where we interpret it differently but to be honest i can't test it because i don't have any gigabit capable switches handy. You are absolutely correct in that a gig interface defaults to full duplex as i said in my last post.
But my understanding is that if the gig interface has to fall back to 100Mbps it must also fall back to half-duplex because of the speed it is running at. However as i said in my last post it really depends on interpretation of 'gig interfaces default to full duplex'. And your interpretation may well be correct and mine wrong. Sarah/All, I was able to test this with 2 3750-E switches. In this scenario I am using port 1/0/48 on both switches. The switches are called switch B and switch C When I set the duplex to full and speed to 100 on switch C switch B's interface shows 100 Full Here is the config and show command for switch C Switch-C#sh run in gi1/0/48 Building configuration. Current configuration: 63 bytes!
Hello Jon, Reza, neighbor speed detection is possible, detection of neighbor duplex is not possible without auto negotiation. First of all, 1000 Mbps uses 4 pairs (all wires in RJ-45) 10/100 Mbps uses only two pairs (wires 1,2,3,6). So if the switch sees activity on all pairs it detects neighbor is working at 1000 Mbps. If neighbor is set to 100 Mbps or 10 Mbps fast link pulses allows to detect the speed. Autonegotiation is the modulation of the pulses to carry few bits of information to tell capabilities (16 bits link code word) Ethernet is baseband and there is no framing structure between two ethernet frames there is silence.
The fast link pulses are not ethernet frames but a form of baseband digital modulation that is interleaved over time with ethernet frames (a sort of TDM we could say). I would say that after detecting neighbor speed is 100 Mbps a system not able to see neighbor duplex capabilities it should revert to half duplex, but Reza's tests shows something different. Also recommendations have changed over time: years ago hardcoding speed and duplex was recommended. Today autonegotiation is preferred. See Final note: compliments to Sarah that putting (what looks like) simple questions make us thinking of basic concepts Hope to help Giuseppe.
Thanks Giuseppe for your kind remarks. I have one more question Once auto-negotiation is turned off by configuring duplex and speed under the interface, there should not be any FLP ( fast link pulses) as auto-negotiation is off. So in absence of FLP, what other activity would enable adjacent switch to determine the speed? How about if cdp is turned off?
Thanks and have a nice weekend. I would like to thank all of you who responded to my post.
Damaged Error With 0.48 Test 2 Compiled For Mac
I am really learning a lot technical stuff from all of your experiences and knowledge. Jon, i am really impressed with your humility. I will try to emulate that.