From: Scott M Vermillion (scott_ccie_list@it-ag.com)
Date: Sun Mar 15 2009 - 13:49:34 ART
Are we talking lab or real world here?  In the lab, if you're really  
concerned about it, there are only so many interfaces in active  
service, so you could always hard-code everything (using the  
'interface range' command, that would likely take less time that going  
around and verifying everything with 'sh int').  But the lab's all  
Cisco, so I'm not sure that would be a wise use of time.  With an all  
Cisco IOS environment, the only time I occasionally see duplex  
problems in this current day and age is where Dynamips is in use.
For real-world applications, I wouldn't worry about speed too much, as  
that is easily detected.  Duplex can only be negotiated (vs. detected)  
or, failing that, defaulted.  With 10 and 100 Mbps, the default is  
half-duplex.  With Gig-E, the default is full-duplex.  I actually ran  
into this on a project maybe a year-and-half or so back.  A client had  
leased a Metro Ethernet service from a carrier in the UK.  Their  
equipment was 100 Mbps, full-duplex - and it wouldn't negotiate.  The  
client's 6504 attached to that ME service defaulted to 100 Mbps, half- 
duplex.  Guess what?  Problemo.
On Mar 15, 2009, at 3:43 , Khurram Noor wrote:
> Dear all,
> can you tell me where to leave duplex and speed settings to auto and  
> where
> to statically set them. i get confused with it sometimes. In my
> understanding if the router and switch interfaces are same like both  
> are
> fast ethernet we can leave it to auto on both end. and if there is a
> mismatch i.e. like router has an ethernet interface which is connected
> switch fastethernet, then we need to statically set speed and duplex.
>
> Am i wrong?
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net
This archive was generated by hypermail 2.1.4 : Mon Apr 06 2009 - 06:44:05 ART