After doing

Switch1(config)#interface fastethernet 0/35

Switch1(config-if)#switchport

Switch1(config-if)#switchport access vlan 2

Switch1(config-if)#end

I am not been able to assign IP to this port since it now becomes a L2 Port.

Is there a way to add it in to Vlan2 and assign the port IP as with different ports which are in Vlan2 having perticular IP's

After doing

Switch1(config)#interface fastethernet 0/35

Switch1(config-if)#switchport

Switch1(config-if)#switchport access vlan 2

Switch1(config-if)#end

I am not been able to assign IP to this port since it now becomes a L2 Port.

Is there a way to add it in to Vlan2 and assign the port IP as with different ports which are in Vlan2 having perticular IP's

If you make it a routed ported ie "no switchport" then you cannot allocate an IP address to it out of a subnet you have already used on the switch.

So, as Kevin says, if you have allocated vlan 2 layer 3 interface an ip address you cannot then allocate another ip address from the same subnet to this routed port.

What is it you are trying to achieve ?

Jon

Basically I have connected that interface to a router and I want to assign an IP to interface where that router is connected so I can make few routers like to router data intended towards that destination connected to that router.

What is the best possible way

Either I should remove the port from VLAN 2 and assign an IP but that IP is from the same series of Vlan 2 so it gives an error that

207.XXX.XXX.XX overlaps with Vlan2 address

Do let me know the best possible way

The external router has an interface, with an IP address, right? And the hosts are also in the subnet of that IP address?

If that is the case, you don't need the layer-3 functions of the switch at all, and you don't need to configure any IP addresses on it. Just leave each port as a switchport and put them all in VLAN 2, including the one where the router is connected. As far as layer-3 is concerned, the external router will be talking directly to the hosts.

Kevin Dorrell

Luxembourg.

If you want the router interface to have an IP address from vlan 2 subnet allocate the port on the switch into vlan 2.

If you want the router interface to not have an IP address out of vlan 2 then allocate a small P2 subnet eg. 192.168.1.0/30 and

router fa0/0 192.168.1.1 255.255.255.252

switchport 192.168.1.2 255.255.255.252

The switch will need to be running ip routing for the second option to work.

HTH

Jon

There are only two architectures you can go for.

1. Have your ports in VLAN 2, in which case they are layer-2 ports. They share one IP address. (Actually, you can give them more, but then they share all of them.) In this case, you put the IP address on int vlan 2, and also any secondary addresses, but they are all shared. Forwarding between members of the VLAN are by MAC address.

2. Have your ports in layer-3 no switchport. In that case you can assign a subnet to each port, and port to port communication is via the routing element of the switch. In that case, the IP ranges may not overlap, otherwise router element does not know which one to route to. Forwarding is by IP address.

I suspect there is a more basic misunderstanding though. What are you trying to achieve?

Kevin Dorrell

Luxembourg

Switch1#show run int vlan 2

Building configuration...

Current configuration : 214 bytes

!

interface Vlan2

description MIXIT Client VLAN

ip address 207.xxx.xxx.xxx 255.255.255.192

no ip redirects

ip pim sparse-dense-mode

standby 1 ip 207.xxx.xxx.xxx

standby 1 priority 105

standby 1 preempt

end

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

Switch1#show int F0/35 switchport

Name: Fa0/35

Switchport: Enabled

Administrative Mode: dynamic desirable

Operational Mode: down

Administrative Trunking Encapsulation: negotiate

Negotiation of Trunking: On

Access Mode VLAN: 2 (ClientVLAN)

Trunking Native Mode VLAN: 1 (default)

Administrative Native VLAN tagging: enabled

Voice VLAN: none

Administrative private-vlan host-association: none

Administrative private-vlan mapping: none

Administrative private-vlan trunk native VLAN: none

Administrative private-vlan trunk Native VLAN tagging: enabled

Administrative private-vlan trunk encapsulation: dot1q

Administrative private-vlan trunk normal VLANs: none

Administrative private-vlan trunk private VLANs: none

Operational private-vlan: none

Trunking VLANs Enabled: ALL

Pruning VLANs Enabled: 2-1001

Capture Mode Disabled

Capture VLANs Allowed: ALL

Protected: false

Unknown unicast blocked: disabled

Unknown multicast blocked: disabled

Appliance trust: none

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

Above are the results you mentioned before.

Basically I want to use that Port to connect to a router So that if some request is intended towards that router IP i will add a route to pass that request from the switch port to router

# ip "router IP" "switch port IP"

No need for any IP addresses anywhere on the switch then. Just put the port where the router connects in switchport access vlan 2, and all the host machine ports as well.

Kevin Dorrell

Luxembourg

You mean i should put the IP on router insted of switch. The same Vlan2 IP so I can place that route

It's a bit difficult to see what is going on with all those X.x.x. in the IP addresses. Could you tell us the addresses - alter them to disguise them if you want, but keep the relationship between them.

What address range do your hosts have. What address is on the external router?

For example, if you external router is 172.16.22.1 255.255.255.192, then your hosts can be anything from 172.16.22.2 to 172.16.22.62. Forget about the VLAN 2 interface on the switch - just blow it away. Put all the ports in VLAN 2 as switchports, and the hosts will talk to your external router.

Kevin Dorrell

Luxembourg