• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1266
  • Last Modified:

Cisco Switch IP Address Assign

Hi,

I have got two Cisco Catalyst 3500 XL series switches which I have reset recently and now trying to assign an IP address for the router. I have successfully ran the IP address change commands  and save the running config to startup config, but when I check the config again, it is not been saved. Here are the steps I have used to reset the IP address.


1. From the command line, use the enable command to enter privileged EXEC mode.
 
2. Use the configure terminal to enter configuration mode.
 
3. Enter interface vlan1 to choose the switch interface for configuration.
 
4. Use the command ip address 192.168.1.40 255.255.255.0.

5. Then exit EXEC mode using end command.

6. Finally save the config using copy running-config startup-config

Also I have used show running-config command before save and I cannot see the IP address assign there either.

Can some one help me on this please?

Thanks in advance.

Sx
0
SHALINDRA
Asked:
SHALINDRA
  • 9
  • 7
  • 6
  • +2
1 Solution
 
Don JohnstonInstructorCommented:
Please post the output of a "show run" after you have assigned the address.

Also, it would help if you could post the output of the session (where you enter the commands).
0
 
SHALINDRAAuthor Commented:
Hi DonJohnston,

Thanks for your comment, please see the output below.



User Access Verification

Password: xxxxxxxxxx

WC3_Cisco_3524>
WC3_Cisco_3524>enable

Password: xxxxxxxxxxxxx

WC3_Cisco_3524#
WC3_Cisco_3524#configure  terminal

Enter configuration commands, one per line.  End with CNTL/Z.
WC3_Cisco_3524(config)#
WC3_Cisco_3524(config)#interface  vlan1

WC3_Cisco_3524(config-if)#
WC3_Cisco_3524(config-if)#ip  address  192.168.1.40  255
.255.255.0

WC3_Cisco_3524(config-if)#
WC3_Cisco_3524(config-if)#end

WC3_Cisco_3524#
WC3_Cisco_3524#
05:26:47: %SYS-5-CONFIG_I: Configured from console by console
WC3_Cisco_3524#show  running-config

Building configuration...

Current configuration:
!
version 12.0
no service pad
service timestamps debug uptime
service timestamps log uptime
service password-encryption
!
hostname WC3_Cisco_3524
!
enable secret 5 $1$bl3/$qjJrtqBd2TQa5d24bOvyo.
enable password 7 132316110E2A05293F377A
!
!
!
!
!
!
ip subnet-zero
no ip domain-lookup
!
cluster commander-address 00d0.9753.66c0 member 3 name Quaestor

WC3_Cisco_3524#copy  running--config  startup-config


Destination filename [startup-config]?
Building configuration...

WC3_Cisco_3524#show  running-config

Building configuration...

Current configuration:
!
version 12.0
no service pad
service timestamps debug uptime
service timestamps log uptime
service password-encryption
!
hostname WC3_Cisco_3524
!
enable secret 5 $1$bl3/$qjJrtqBd2TQa5d24bOvyo.
enable password 7 132316110E2A05293F377A
!
!
!
!
!
!
ip subnet-zero
no ip domain-lookup
!
cluster commander-address 00d0.9753.66c0 member 3 name Quaestor

WC3_Cisco_3524#show  startup-config

Using 2384 out of 32768 bytes
!
version 12.0
no service pad
service timestamps debug uptime
service timestamps log uptime
service password-encryption
!
hostname WC3_Cisco_3524
!
enable secret 5 $1$bl3/$qjJrtqBd2TQa5d24bOvyo.
enable password 7 132316110E2A05293F377A
!
!
!
!
!
!
ip subnet-zero
no ip domain-lookup
!
cluster commander-address 00d0.9753.66c0 member 3 name Quaestor
!

WC3_Cisco_3524#
0
 
keno44Commented:
Did you first enable routing by using this command?

Switch(config)#ip routing

I think I had to do that on a similar Catalyst model.

K
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
B8ZSCommented:
Your output seems cut off.  After you type show run, make sure to scroll all the way to the bottom by pressing the space bar.

Make sure when you're in VLAN 1 configuration type no shut.

Here are some more troubleshooting commands: From global exec type show ip interface brief, does the IP address show up there for VLAN 1?  Also do you have a trunk port or access port between the router and the switch (default is auto negotiate)? Use show interface trunk to view active trunks, and show interface status to view the mode of all ports.

Edit:

Just noticed you have a switch cluster.  You will have to configure your VLAN 1 interface from the cluster master.

http://anetworkerblog.com/2007/09/09/how-to-configure-a-cluster-member-switching-yeah/
0
 
SHALINDRAAuthor Commented:
Hi,

Basically can I erase all configurations in this switch and do a factory reset?

I have followed the below link to reset the switch and have tried to assign the IP again, but still no luck.

http://www.oleksiygayda.com/2009/02/how-to-reset-cisco-catalyst.html#!/2009/02/how-to-reset-cisco-catalyst.html

Any help please? Also I have given the dir flash: results after follow the reset procedure in the above link, if that helps.

WC3_Cisco_3524#
WC3_Cisco_3524#dir  flash:

Directory of flash:/

  2  -rwx     1645807   Jul 18 2000 01:47:40  c3500XL-c3h2s-mz-120.5.2-XU.bin
  3  -rwx       94680   Jul 18 2000 01:47:40  c3500XL-diag-mz-120.5.2-XU
  4  drwx        6784   Jul 18 2000 01:47:41  html
111  -rwx         269   Jan 01 1970 00:00:23  env_vars
112  -rwx        2384   Mar 01 1993 00:05:00  config.text

3612672 bytes total (844800 bytes free)
WC3_Cisco_3524#
WC3_Cisco_3524#

Thanks in advance.
0
 
keno44Commented:
Shalindra, have you tried all of the suggestions posted above?
0
 
SHALINDRAAuthor Commented:
Hi Keno44,

Sorry, I missed your comment. I have tried it now. But it return an error. Do I need any additional details on this comand.
Here is the output,

WC3_Cisco_3524(config)#
WC3_Cisco_3524(config)#ip  routing

                           ^
% Invalid input detected at '^' marker.

WC3_Cisco_3524(config)#
WC3_Cisco_3524(config)#ip  route

% Invalid input detected at '^' marker.

Thanks
0
 
keno44Commented:
I just read a post that the 3524 does NOT support L3 routing. Trying to confirm...stand by please....

https://supportforums.cisco.com/thread/148019

K
0
 
B8ZSCommented:
Your switch is configured as a cluster member, you will have to make the configuration changes from the cluster master.
0
 
mat1458Commented:
Your switch is a 3524XL, end of support since July 27, 2007. It cannot do any ip routing, it's layer 2 only.

The IP address is probably configured correctly, it seems that you have problems with the scrolling. You might have a look at the settings of your terminal program or try another one. If you want to see the part of the config file with the ip address do the following:

show running-config | begin an1

The config is shown beginning with the line "interface vlan1". The IP address should be visible now. I cannot remember the command on the XL switches that allowed to suppress the scrolling, on newer switches it is "terminal length 0" but I doubt that you can use it on your device.
0
 
keno44Commented:
I concur with MAT1458. If you in fact have a 3524, it will NOT support routing. I am suprised that in your initial post, it appears that the switch accepted the 'ip address' command.

Best of luck.

K
0
 
mat1458Commented:
Well keno44, you still can set one ip address for management purposes on these type of switches. You can assign them to whichever vlan that you use as management vlan.
0
 
keno44Commented:
Ah, thanks for that..

Cheers - K
0
 
SHALINDRAAuthor Commented:
So I presume all these answers mean I cannot use this switch to re-configure to install a new network for a new subnet mask, is that so?

Thanks
0
 
B8ZSCommented:
Your switch is configured as a cluster member, you will have to make the configuration changes from the cluster master.
0
 
keno44Commented:
Shalindra...Not exactly true...

If you want, you may still create several VLANs on your switch and attach hosts from different subnets to the switch. BUT these hosts will not be able to talk to each other.

If you want to accomplish routing between hosts from different VLANs, you would also need a separate router in the mix. You would then create a trunk port on your switch and attach it to one of the router's interfaces (e1) and then configure routing at the e1 interface.  

K
0
 
mat1458Commented:
And to answer your question about the factory reset, please enter:

erase startup-config
reload

Then all config is gone and you can start from scratch.
0
 
SHALINDRAAuthor Commented:
Hi mat1458,

I have run the commands above and reloaded, but still in the configurations, it shows as a cluster member.

B8zs - I don't have the cluster master switch with me, is there any other way to delete the config and get this switch to factory default?

Thanks
Sx
0
 
mat1458Commented:
Can you try the following in config mode:

no cluster commander-address 00d0.9753.66c0 member 3 name Quaestor

and the reload the switch again. Can you add a show run after the reload?
0
 
SHALINDRAAuthor Commented:
Hi mat1458,

Well....it seems to be that has removed the cluster. Here is the output and I will wait for your reply before proceed anything.

WC3_Cisco_3524#

WC3_Cisco_3524#show  running-config



Building configuration...



Current configuration:

!

version 12.0

no service pad

service timestamps debug uptime

service timestamps log uptime

service password-encryption

!

hostname WC3_Cisco_3524

!

enable secret 5 $1$bl3/$qjJrtqBd2TQa5d24bOvyo.

enable password 7 132316110E2A05293F377A

!

!

!

!

!

!

ip subnet-zero

no ip domain-lookup

!

!



WC3_Cisco_3524#

WC3_Cisco_3524#

Thanks
Sx
0
 
mat1458Commented:
Looks better. With "show cluster members" you could see if the cluster still exists. The output should be somethng like "no cluster exists" or similar.

You still seem to have your scrolling problem over the console port. Define the ip adress on the box and telnet or ssh to it. you then should be able to see the entire running configuration.
0
 
SHALINDRAAuthor Commented:
Hi mat1458,

Do you recon any good freeware? I am using hyperterminal and have tried to connect with PuTTY, but it is not working.

Also here is the output of the 'show cluster memebers' command



WC3_Cisco_3524#show  cluster



% Not a management cluster member

WC3_Cisco_3524#

WC3_Cisco_3524#

I have again assigned the IP address, save and reloaded. But still show run is not showing any IP address?

I have also connected a cross-over cable and connected to a laptop, but the network port of the laptop is disconnected still.

Any comment?


Thanks
Sx
0
 
SHALINDRAAuthor Commented:
Also I have ran 'show interfaces' command and it return the following, if that any help.

WC3_Cisco_3524#show  interfaces

s

VLAN1 is up, line protocol is up

  Hardware is CPU Interface, address is 0004.ddd2.8c40 (bia 0004.ddd2.8c40)

  Internet address is 192.168.1.40/24

  MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec,

     reliability 255/255, txload 1/255, rxload 1/255

  Encapsulation ARPA, loopback not set

  ARP type: ARPA, ARP Timeout 04:00:00

  Last input never, output 01:24:57, output hang never

  Last clearing of "show interface" counters never

  Queueing strategy: fifo

  Output queue 0/40, 0 drops; input queue 0/75, 0 drops

  5 minute input rate 0 bits/sec, 0 packets/sec

  5 minute output rate 0 bits/sec, 0 packets/sec

     0 packets input, 0 bytes, 0 no buffer

     Received 0 broadcasts, 0 runts, 0 giants, 0 throttles

     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored

     0 input packets with dribble condition detected

     2 packets output, 120 bytes, 0 underruns

     0 output errors, 0 collisions, 0 interface resets

     0 babbles, 0 late collision, 0 deferred

     0 lost carrier, 0 no carrier

     0 output buffer failures, 0 output buffers swapped out



WC3_Cisco_3524#

WC3_Cisco_3524#
0
 
mat1458Commented:
The reason why you don't see the ip address on vlan 1 is because your terminal emulation sends something that interrupts the scrolling on the switch. The configuration of the interface is there but it comes below the no ip domain-lookup.

Connect our PC with a straight cable (no crossover) to interface Fa0/1, give it an IP address in the same VLAN as the switch and the try to ping it. If the interface is up (green LED) you should have no problems with pinging and maybe telnet-ing to the switch afterwards to have a look at the running config. In the telnet session it should work fine.

Maybe issue a "show interface Fa0/1" first to see if the interface is not admin down. If this is the case do a no shutdown of this interface.
0
 
SHALINDRAAuthor Commented:
Hi mat1458,

I have followed your instructions and managed to ping to the router and alsoI have logged to router from web interface.

So the problem is sorted now and many thanks for your help on this.

Sx
0
 
B8ZSCommented:
Chopped liver over here.
0
 
mat1458Commented:
You're very welcome. Thanks.
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

  • 9
  • 7
  • 6
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now