[c-nsp] Copper SFP with ME3600X
Tóth András
diosbejgli at gmail.com
Mon Dec 10 14:55:12 EST 2012
GLC-T does not seem to be supported in the SFP+ port, only supported in the
client ports.
http://www.cisco.com/en/US/docs/interfaces_modules/transceiver_modules/compatibility/matrix/OL_6981.pdf
If you move the SFP to a client port, does it work?
Andras
On Mon, Dec 10, 2012 at 8:44 PM, Lobo <lobotiger at gmail.com> wrote:
> Normally I would agree with this command but it's not supported. The
> only "speed" command is nonegotiate and it doesn't make a difference when
> plugging the SFP in.
>
> Jose
>
>
> On 12/10/2012 2:40 PM, Tóth András wrote:
>
> Given that this is a 1G in a 10G port, you might need to add "speed 1000"
> to the interface config?
>
> Best regards,
> Andras
>
>
> On Mon, Dec 10, 2012 at 8:12 PM, Lobo <lobotiger at gmail.com> wrote:
>
>> Hi everyone. Been having a hard time trying to get a copper SFP to work
>> on our ME-3600X-24TS-Ms. According to Cisco documentation, the GLC-T SFP
>> is supposed to be supported on one of the fiber ports. However every Cisco
>> SFP we've tried always spits back an error message:
>>
>> Switch#
>>
>> *Dec 6 19:48:30.448: %PHY-4-SFP_NOT_SUPPORTED: The SFP in Te0/1 is not
>> supported
>>
>> *Dec 6 19:48:30.448: %PM-4-ERR_DISABLE: gbic-invalid error detected on
>> Te0/1, putting Te0/1 in err-disable state
>>
>> Switch#
>>
>>
>> Has anyone had any success with trying to use these on this platform?
>> Fiber based SFPs are fine so long as they're Cisco branded. Are there
>> different versions of GLC-T that we may have the wrong type?
>>
>> Thanks.
>>
>> Jose
>> _______________________________________________
>> cisco-nsp mailing list cisco-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-nsp
>> archive at http://puck.nether.net/pipermail/cisco-nsp/
>>
>
>
>
More information about the cisco-nsp
mailing list