On Sat, Jan 30, 2010 at 08:43, Ahmed Haji Munye <[email protected]> wrote:
> > > If the interface is showing as not connected, then it cannot be more > obvious tha that. No matter if you shutdown or enable it again. Because if > the cable is not physically connected on that port, then it will never come > up. > > Anyway taka a look on where that port goes to: > > *Cat3550-1*#sho running-config interface fastEthernet 0/2 > Building configuration... > Current configuration : 122 bytes > ! > interface FastEthernet0/2 > *description goes to R2 port Fa1/0* > switchport access vlan 12 > switchport mode dynamic desirable > end > Hello Ahmed, Tyson's advice is by far the best. If you are having technical difficulties that you think are the result of physical connectivity, please, get in touch with our support. Please, have in mind that they probably can't help you with the lab itself :-) Now, that being said, we are working on removing the use of NM-16ESW on R2 from our labs. All our recently published labs should be without this interface used. Are you using the latest revision of our material for your practice? You can also always swap Fa0/2 with Gi0/2 (connected to R2's Gi0/0 SFP port) and proceed with lab like that. * Just for my reference - what lab are you working on? -- Marko Milivojevic - CCIE #18427 Senior Technical Instructor - IPexpert Mailto: [email protected] Telephone: +1.810.326.1444 Fax: +1.810.454.0130 Community: http://www.ipexpert.com/communities
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
