Thanks  Matt and Scott for your input. I  reseated the  the card   then took 
the   etherchannel  config off the the  10G port  and  the port came up  so 
then I  redid the config and it worked .
 
 


From: [EMAIL PROTECTED]: [EMAIL PROTECTED]; [EMAIL PROTECTED]: Thu, 17 Apr 2008 
18:36:26 -0500Subject: Re: [OSL | CCIE_RS] Physical port in etherchannel bundle 
will not come up


Will try that and see what happens  will  lwt you know most likely tomorrow 
what the outcome was thanks for your  help keith 

> Date: Fri, 18 Apr 2008 09:04:36 +0930> From: [EMAIL PROTECTED]> To: [EMAIL 
> PROTECTED]> Subject: Re: [OSL | CCIE_RS] Physical port in etherchannel bundle 
> will not come up> CC: [email protected]> > Hmmm ok... Can the 
> individual ports come up when they are not> bundled? Ie point to point? If 
> you put the xenpaks from the working> blade into the not working blade does 
> anything happen?> > On 18/04/2008, keith quaye <[EMAIL PROTECTED]> wrote:> >> 
> > Yes to all your questions Zenpaks at both ends right cable being used> > 
> distance is 3ft so definitely not a problem No need for attenuators> >> >> >> 
> > ________________________________> > > Date: Fri, 18 Apr 2008 08:57:01 
> +0930> > > From: [EMAIL PROTECTED]> > > To: [EMAIL PROTECTED]> > > Subject: 
> Re: [OSL | CCIE_RS] Physical port in etherchannel bundle will not> > come up> 
> > > CC: [email protected]> >> > >> > > What media type are they? 
> Same ZENPAKs at each end? Is the right> > > cable being used (SM vs MM etc) 
> Is the distance ok? Do you need> > > attenuators?> > >> > > Cheers,> > > 
> Matt> > >> > > On 18/04/2008, keith quaye <[EMAIL PROTECTED]> wrote:> > > >> 
> > > >> > > > I am connecting to core switches together via etherchannel on 
> their 10G> > > > ports> > > > I AM Running 
> s72033-ipservices_wan-vz.122-18.SXF9.bin> > on> > > > THE 2 6509s for some 
> reason the 10G ports on core B will not come> > > > up. Current running 
> Config listed below. I do a no shut and it still> > says> > > > shut down> > 
> > >> > > >> > > > interface TenGigabitEthernet9/1> > > > switchport> > > > 
> switchport trunk encapsulation dot1q> > > > switchport mode trunk> > > > 
> switchport nonegotiate> > > > no ip address> > > > channel-group 1 mode on> > 
> > > !> > > > interface TenGigabitEthernet9/2> > > > switchport> > > > 
> switchport trunk encapsulation dot1q> > > > switchport mode trunk> > > > 
> switchport nonegotiate> > > > no ip address> > > > channel-group 1 mode on> > 
> > >> > > >> > > > interface Port-channel1> > > > description Etherchannel 
> link to Core B> > > > switchport> > > > switchport trunk encapsulation dot1q> 
> > > > switchport mode trunk> > > > switchport nonegotiate> > > > no ip 
> address> > > >> > > > interface TenGigabitEthernet9/1> > > > description 
> Etherchannel link to Core A> > > > switchport> > > > switchport trunk 
> encapsulation dot1q> > > > switchport mode trunk> > > > switchport 
> nonegotiate> > > > shutdown> > > > no ip address> > > > channel-group 1 mode 
> on> > > > !> > > > interface TenGigabitEthernet9/2> > > > description 
> Etherchannel link to Core A> > > > switchport> > > > switchport trunk 
> encapsulation dot1q> > > > switchport mode trunk> > > > switchport 
> nonegotiate> > > > shutdown> > > > no ip address> > > > channel-group 1 mode 
> on> > > > interface Port-channel1> > > > description Etherchannel Port to 
> Core A> > > > switchport> > > > switchport trunk encapsulation dot1q> > > > 
> switchport mode trunk> > > > switchport nonegotiate> > > > no ip address> > > 
> >> > > >> >

Reply via email to