cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
742
Views
0
Helpful
6
Replies

3550 under 3254 - IP address set but cannot telnet or ping

tennille.spence
Level 1
Level 1

I have two switches at a remote office. The primary switch is a 3524 and the secondary switch is a 3550. Each switch has a static ip IP address assigned to it and default gateway configured as:

interface VLAN1

ip address <IP ADDRESS> <SUBNET MASK>

ip default-gateway <IP ADDRESS>

"SH CDP NE" on the primary reveals the secondary switch is present but no IP address shows. I did have someone telnet locally into the secondary switch (3550) this morning to verify the settings and the switch had ip, subnet mask and default gateways exactly like the primary. Is there a setting I am missing on either of these switches to make the second switch accessible?

6 Replies 6

Hello,

can both your switches ping the default gateway ? Can you post the configuration of both switches ?

Regards,

GP

Thank you for the reply. Here is the config for the 3524 (primary) along with ping and sh cdp ne details...

sh run

Building configuration...

Current configuration:

!

version 11.2

no service pad

no service udp-small-servers

no service tcp-small-servers

!

hostname 3524

!

!

!

!

!

interface VLAN1

ip address XXX.XXX.XXX.83 255.255.255.224

no ip route-cache

!

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 GigabitEthernet0/1

!

interface GigabitEthernet0/2

!

ip default-gateway XXX.XXX.XXX.65

!

end

3524#ping XXX.XXX.XXX.65

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to XXX.XXX.XXX.65, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/3 ms

3524#sh cdp ne det

-------------------------

Device ID: 3550

Entry address(es):

Platform: cisco WS-C3550-24-PWR, Capabilities: Switch IGMP

Interface: GigabitEthernet0/1, Port ID (outgoing port): GigabitEthernet0/1

Holdtime : 139 sec

Version :

Cisco Internetwork Operating System Software

IOS (tm) C3550 Software (C3550-I5Q3L2-M), Version 12.1(20)EA1a, RELEASE SOFTWARE

(fc1)

Copyright (c) 1986-2004 by cisco Systems, Inc.

Compiled Mon 19-Apr-04 21:50 by yenanh

advertisement version: 2

Protocol Hello: OUI=0x00000C, Protocol ID=0x0112; payload len=27, value=0000000

0FFFFFFFF010229FF000000000000001360E37E00FF0000

VTP Management Domain: ''

Native VLAN: 1

Duplex: full

3524#

The person who was helping me with morning is on his way back so I don't have anyone who can look at locally now. But here is what I pasted into the config and what he verified this morning...could kick myself for not logging the config when I had the chance to see whith my own eyes. I may have to wait until the next trip to settle this but thought I would at least try..

hostname 3550

!

interface VLAN1

ip address XXX.XXX.XXX.66 255.255.255.224

!

ip default-gateway XXX.XXX.XXX.65

!

end

Hello,

which port on the 3524 is connected to the 3550 ? Do the hosts connected to the 3550 have network connectivity at all ? If not, you problem might be related to trunking. It would indeed be useful to see the configuration of the 3550...

Regards,

GP

The 3550 is connected to 3254 via GigabitEthernet0/1. When I tried to turn trunking on for that port on the 3524 (switchport mode trunk..maybe this is the wrong command..although I have that set for other stacked switches)..it killed the network connectivity for both switches..As I entered the command I lost telnet access to the 3524 and then users began complaining that the network was down...then we powered the swicth off to default back to the previous config.

This sounds like the correct action from changing the port mode. The two ports must match configs, and spanning tree will most likely want to re-converge (~30sec) and then you should start passing traffic again.

Hi,

it's difficult without looking into the config, but I'd guess following possibilities:

1) there is shutdown command on int VLAN1

2) no port active in VLAN1

3) another int VLANx configured as the management one

on your 3350.

Regards,

Milan