Cisco 2900XL Switch Configuration Question

[photoadrian]

Hi all,

I have a Cisco 2900XL switch and a Cisco 2650XM router. Basic configuration - FastEthernet0/1 on the router is configured with an IP address (192.168.1.1/24) and connected via a straight-thru cable to Fa0/24 on the switch. I've gone through the basic set up on the switch.

Problem: Link light is not lighting up on the switch for the connection.

Remedial Action already taken:
1) Use a different port on the switch (still no link)
2) Use a different cable (still no link)
3) Connect laptop via the cable to the switch (link)
4) Connect router to a different switch (link)

I'm guessing there is a problem with the configs, since I've ruled out every bit of physical components.

My router is configured thusly:

!
interface FastEthernet0/1
ip address 192.168.1.1 255.255.255.0
ip virtual-assembly
speed auto
duplex auto
no mop enabled
!

The switch is configured without any additional parameters on the ports, and only VLAN1 configured for the switch (IP address 192.168.1.254).

I've also tried, configuration-wise, pegging the speed on either end, pegging the duplex on either end, and pegging both the speed and duplex on both ends.

Can anyone suggest other configurations or trouble-shooting steps to try?

Thanks,

-Adrian

 

[burtsbees]

Post a complete config from the router and the switch.

/

 

[photoadrian]

(Note: These running configs are what are running now, but not what is normally running - I usually have access lists, etc.

2650XM Router (removing excess lines):
(From "sh ver")
Cisco IOS Software, C2600 Software (C2600-ADVSECURITYK9-M), Version 12.4(9)T2, RELEASE SOFTWARE (fc4)

gw.internal# sh run
Current configuration : 1585 bytes
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname gw.internal
!
boot-start-marker
boot-end-marker
!
enable secret 5 <secret>
enable password <secret>
!
no aaa new-model
!
resource policy
!
clock timezone MDT -7
clock summer-time MDT recurring
no network-clock-participate slot 1
no network-clock-participate wic 0
no ip source-route
ip cef
!
no ip bootp server
no ip domain lookup
!
interface ATM0/0
description Qwest-ADSL
no ip address
no ip redirects
no ip unreachables
no ip proxy-arp
no ip mroute-cache
no atm oversubscribe
no atm ilmi-keepalive
dsl operating-mode auto
hold-queue 224 in
pvc 0/32
encapsulation aal5mux ppp dialer
dialer pool-member 1
!
!
interface FastEthernet0/0
ip address 65.103.125.142 255.255.255.248
ip virtual-reassembly
speed 100
full-duplex
no mop enabled
!
interface FastEthernet0/1
ip address 192.168.1.1 255.255.255.0
ip virtual-reassembly
duplex auto
speed auto
no mop enabled
!
interface Dialer0
description Virtual Dialer Interface for Qwest ADSL
ip unnumbered FastEthernet0/0
encapsulation ppp
dialer pool 1
dialer-group 1
no cdp enable
ppp authentication pap callin
ppp pap sent-username <username> password 0 <password>
!
ip route 0.0.0.0 0.0.0.0 Dialer0
!
ip http server
no ip http secure-server
!
dialer-list 1 protocol ip permit
snmp-server community public RO
!
control-plane
!
line con 0
line aux 0
line vty 0 4
password <secret>
login
!
end

2900XL Switch (again, removing excess lines):
(From "sh ver")
IOS (tm) C2900XL Software (C2900XL-C3H2S-M), Version 12.0(5)WC17, RELEASE SOFTWARE (fc1)

XL-Switch# sh run

Current configuration:
!
version 12.0
no service pad
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname XL-Switch
!
enable secret 5 <secret>
!
ip subnet-zero
!
interface FastEthernet0/1
!
interface FastEthernet0/2
!
interface FastEthernet0/3
!
interface FastEthernet0/4
!
interface FastEthernet0/5
!
interface FastEthernet0/6
!
interface FastEthernet0/7
!
interface FastEthernet0/8
!
interface FastEthernet0/9
!
interface FastEthernet0/10
!
interface FastEthernet0/11
!
interface FastEthernet0/12
!
interface FastEthernet0/13
!
interface FastEthernet0/14
!
interface FastEthernet0/15
!
interface FastEthernet0/16
!
interface FastEthernet0/17
!
interface FastEthernet0/18
!
interface FastEthernet0/19
!
interface FastEthernet0/20
!
interface FastEthernet0/21
!
interface FastEthernet0/22
!
interface FastEthernet0/23
!
interface FastEthernet0/24
!
interface VLAN1
ip address 192.168.1.254 255.255.255.0
no ip directed-broadcast
no ip route-cache
!
ip default-gateway 192.168.1.1
snmp-server engineID local 000000090200000653EDC640
snmp-server community private RW
snmp-server community public RO
!
line con 0
transport input none
stopbits 1
line vty 0 4
password <secret>
login
line vty 5 15
password <secret>
login
!
end

 

[acrowe]

Stupid question, but did you try a crossover cable?

I know you said a different switch, but was it a Cisco? Lots of brands have auto crossover so you'll get a link.

 

[photoadrian]

The other switch is a Linksys/Cisco SR224 business series switch, which does indeed have auto-MDIX.

I thought Cisco enterprise switches also had auto-MDIX, but it seems there are only a handful (such as the 2940 series) that do.

I'll get a cross-over cable, test and let you know.

 

[vipergg]

A 2924 is like 15 years old now and out of support mdix wasn't even a glint in cisco's eye back in 1995 when this switch came out. Even now not all their switches have mdix .

 

[photoadrian]

vipergg: you may be right. I was following docs after searching for "auto-MDIX cisco" through google. Never auto-trust what you read. I don't have a 2940 to test on (and a 2924 isn't in the same series).

acrowe: Cross-over cable didn't work.

Now that I think about it, there is no reason it would work - router to switch needs a straight through cable. However, I needed a cross-over cable anyhow, so no loss.

Anyone else have any ideas?

 

[vipergg]

You may want to check the log , it may have failed POST for a group of ports or something . Really no other reason why it should not get a physical link . Try a port towards the beginning of the switch like port 1 .

 

[photoadrian]

I thought of that as well. Actually, it was the first thing I checked when I was getting failures. I also double-checked the port by plugging the laptop into the port I am using.

 

[robertjo24]

What is the effect of the command "ip virtual-reassembly" on the router interface? Have you tried removing this?

 

[photoadrian]

Good Question. It was an artifact of the configuration after running "setup". Removing it does not cause a change.

According to this:

http://www.cisco.com/en/US/prod/col.../ps6634/prod_white_paper0900aecd8043bc32.html

.. it's a Cisco recommended configuration element. However, that's for a SDM/IPS thing, but it seems to be a generic recommendation.

 

[photoadrian]

Just wanted to let the forums know I solved this problem.

Basically, the cable I was using was a straight-thru with 1,2,3,6 connected.

Switching this cable out to one that had all eight wires connected resulted in the solution.

Now, quite why connecting the four extra wires caused the problem to go away (or why that same cable worked when connected to my laptop) has not been explained. Maybe my Cisco studies will help me there.

 

[burtsbees]

All 8 wires is only used for full duplex gigabit. You had a bad cable, period. Anyone who is too effing LAZY to use all 8 wires should be taken out back and...well, you're a networker---use your imagination...lol

/

 

[cisconooblet]

ouch.

 

[photoadrian]

Burtsbees - Tend to agree with you. This is all 100Mbit and not 1000Mbit full-duplex, though.

Aside from the impending violence against my wires, there is really no reason the cable would work, as far as I can tell.

However, new cable with all 8 wires connected worked.

 

[burtsbees]

I know. In other words, if someone made a cable with only 1,2,3 and 6, chances are it's going to be bad. Any ethernet cable I have made, 10, 100 or gig, I have always used all 8, in case the future holds a place for gig in that network. The cables I make for antiquated stuff (10MBps) are all Cat6 and all 8 wires, yet hey are not gigabit...

/