WS-C3560 L3 Switch ip address x.x.x.x x.x.x.x secondary

[packet.tracert]

I am trying to configure a secondary ip address on a VLAN interface

VLAN 10

ip address 10.10.10.1 255.255.255.0

ip address 20.20.20.1 255.255.255.0 secondary

I receive unrecognized command.

Trying to do this in packet tracer for testing.

I can do this on other manufacturer switches.

Not sure if something needs to be enabled first on the Cisco switch or it does not support it?

Amy help is appreciated..

[Richard Burts]

I want to make sure that I understand correctly what you are telling us. You are doing this in Packet Tracer and not on a real 3560?

I do not have access to a 3560 right now to test it. But I would be very surprised if you have that error on a real switch. In Packet Tracer I am pretty comfortable that it is a flaw in PT.

HTH

Rick

[packet.tracert]

Thanks for the input provided.

I guess i was wondering if i was missing something that needed to be enabled.

Naturally it could be a bug in Packet Tracer or IOS.

WS-C3560-24PS      12.2(37)SE1

Version 6.01.0011

Switch(config)#int vlan 10

Switch(config-if)#ip address 20.20.20.20 255.255.255.0

Switch(config-if)#ip address 20.20.21.20 255.255.255.0 secondary

                                                       ^

% Invalid input detected at '^' marker.

WS-C3560-24PS      12.2(37)SE1
Packet Tracer Version 6.01.0011

I can break out an old 3550 to confirm testing on, would have been nice to build it virtually instead of breaking out the switches.

[Jason Whitehead · Accepted solution]

Hello Richard,

I happen to have 3560's in my lab, I powered them on and tested the command:

int VLAN 10

ip address 10.10.10.1 255.255.255.0

ip address 20.20.20.1 255.255.255.0 secondary

This worked without any error, I beleive this could be a limitation with Packet Tracer.

For reference I am running code:

12.2(35)SE5

Hope this was helpful

[Richard Burts]

Thanks for doing the testing and for posting back to the forum to let us know the results. I am glad that the results show that the command works as expected on real switches and that the problem was a flaw in the implementation of Packet Tracer.

HTH

Rick

[packet.tracert]

Thanks for your help, greatly appreciated!