North American Network Operators Group
Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

RE: Problems connectivity GE on Foundry BigIron to Cisco 2950T

  • From: Sam Stickland
  • Date: Sun Jan 15 16:03:06 2006

Hi,

Yup, it's definately a cross-over cable. ;) I had already tried this suggestion but the cisco 2950T doesn't appear to have the "no nego auto" command :/

(config)#int Gi0/2
(config-if)#no n?
% Unrecognized command
(config-if)#no n
(config-if)#no neg auto
^
% Invalid input detected at '^' marker.

Sam

On Sun, 15 Jan 2006, David Hubbard wrote:

You are using a crossover cable right?  If that's all set, you
do need to have neg-off on the Foundry and "no nego auto" on the
Cisco.  I haven't used the rj-45 gbics in the Foundry equipment
before, not sure if that could be an issue.  I would go with
the hard set 1000-full on both sides.

David

From: Sam Stickland

Hi,

I'm having a right mare trying to get a Foundry BigIron to
connect up to a cisco 2950T, via Gigabit copper.

The Foundry BigIron is using a cisco RJ45/copper GBIC that
was pulled from a live cisco 6500, where it was working
fine. The cisco 2950T has two fixed 10/100/1000 RJ45 ports.

The cables between the equipment have been tested and are fine.

The Foundry has three different types of the gigabit negiation modes:

   auto-gig        Autonegotiation
   neg-full-auto   Autonegotiation first, if failed try
non-autonegotiation
   neg-off         Non-autonegotiation

I've tried all three, complete with all the other
possibilities with the cisco 2950T (which has fixed full
duplex operation, but can be set to 'speed auto' or
'speed 1000').

None of these combinations bring up the link. The cisco 2950
never gets a link light. The Foundry gets a link light
regardless when it's mode is set to 'gig-default neg-off'.

I'm at a bit of a loss to explain this. Does anyone know of any
configuration issues that can explain this, or is it time to start
swapping out hardware components?

Sam