PowerConnect 3348 ip interface

It sounds like the problem may be due to how the IP address was configured on the switch. When you set the IP address, did you bind it to a specific physical ethernet interface, or did you configure it on a VLAN?

If you bind an IP address to a physical interface, that interface is removed from VLAN 1. In this case, only a device directly connected to that interface will be able to manage the switch. The recommended way to configure the IP address is to bind it to a VLAN, like VLAN 1. When the IP address is assigned to the VLAN, any device on that VLAN will be able to manage the switch.

The error you are seeing is output when you try to assign two IP addresses to the switch that are on the same subnet. Use the "show ip interface" command to see the IP address bindings and remove the addresses that are assigned before trying to assign another address.

Im having some similar issues as well... I have figured out how to negate the ip of Vlan1, but in doing so, this removes all connectivity to the switch except through the console. If you try to 'give' a specific port like 1/g1 an IP address, it says the ip address is duplicated on the subnet because vlan1 already has an IP, and totally hoses the switch up to the point of having to reboot. And naturally, the http interface gives no support for easily changing the ip for vlan1.

My question is...

How do you change the ip of the switch through telnet for vlan1? We want to migrate our network to a different configuration in the near future and unless there is an easier way, we will have to drag a laptop around to every switch to console into it and switch the IP. (atleast 8 or so and some will require a ladder to reach...)

Will telnet or ssh be posible to do this? Or do I get to revert back to the stone age of actually having to do some physical work?

Script the configuration changes you want to make using notepad.
  Ex. interface vlan 1
        no ip address
        ip address x.x.x.x /x

Copy the file to the backup-config using tftp. (copy tftp:// / backup-config

Copy the backup-config to the running-config.

That sounds fine and dandy, but it doesn't seem to like the 'no ip address' command...

--------
console# copy backup-config running-config
Copy: Error in configuration download Line: 2 Command: no ip address
console# 01-Jan-2000 01:16:23 %COPY-W-TRAP: The copy operation has failed
--------

Here is the current config I have:

interface vlan 1
no ip address
ip address XXX.XX.XX.XXX 255.255.0.0

Obviously, the X's are in place of the actual numbers...

I named the config file: '3348_ipchange'

Whats the next step?

Well, I was able to duplicate the setup you mentioned by assigning the switch with a dhcp address, then applying the 'no ip address dhcp' (worked correctly) But, I was unable to do the same with a static IP. I did try the 'no ip address xx.xx.xx.xx' like you mentioned, as well as 'no ip address xx.xx.xx.xx XX.XX.XX.XX' neither of which worked. Any way you can set your testing switch up with a static ip and test by giving it a different IP?

Something else,
'no ip address' and
'no ip address xx.xx.xx.xx'
wipes the static IP as well as the gateway clean...

but it does not wipe the IP and gateway if you use:
'no ip address xx.xx.xx.xx XX.XX.XX.XX'
(command with subnet)

Firmware problem maybe??

Im using:
SW version 1.2.0.6 ( date 15-Nov-2004 time 14:22:46 )
Boot version 1.0.0.13 ( date 11-May-2003 time 14:58:20 )
HW version 00.00.03

I am beginning to think I could have consoled into each switch and changed the IP's by now...

1. Copy the running-config file from the switch to the TFTP server.
2. Modify IP address using Wordpad (Notepad does not handle the page breaks correctly).
3. TFTP the new configuration file to the startup-config.
4. Reboot the switch.

Hey!! Worked like a charm!! I read the post and thought 'duh!!' Only took me about 3 min including the reboot on the test switch I am using.
It was just one of those things I didn't think to try...

Only now to figure out how to get it back to the original IP... :p

Thanks a lot Greg! You've been a great help!