How to configure two vlan in one switch to communicate without using the tagging port

[zahirtalib]

Hi Guys,

I want to know it is possible to configure two vlan in one switch to communicate without using the tagging port?

[Dennis_Newman]

Ahh ok possibly my mistake in how I put it.

Currently my ASA 5512 has an inside interface of 10.10.10.1 and that is used as the default gateway for the 10.10 computers
Currently the Summit 400's have only the default vlan configured and the switch has a 10.10.10.20x ip address and the switches are passing 10.10 traffic as if they were L2 switches.
the ASA 5505 has an inside interface of 192.168.3.1 that is used as the default gateway for the 192.168 computers, and the 192.168 network in not currently plugged into the Summit switches.

The intent is to use vlans on the Summit to share ip printers and fileshares across both networks, and eventually let the 192.168 people use my faster internet connection (through the ASA 5512)

That being said, am I on the right track in planning to use the information here to accomplish this task? and if so, what changes do I need to make on the ASA devices once I have the vlan routing working?

Thanks

[Zubair_Ahmad]

I understood your earlier posts as, 10.10.10.1 is the IP address of VLAN10 in extreme 400 Switch. If that's true, then you can't use 10.10.10.1 for ASA5512x inside ip interface, however you can/should use 10.10.10.1 as a 'default GATEWAY' in ASA5512. Regards, ZA

[Zubair_Ahmad]

Dennis,

To respond to your statement above:
"but how do the 10.10 and 192.168 systems "see" their respective internet gates (formerly 10.10.10.1 and 192.168.3.1)?"

I believe that part should be taken care by "enable ip forwarding vlan 10" and "enable ip forwarding vlan 20" commands on extreme switch. (same command as 'ip routing' in cisco)

If that wouldn't be the case, you wouldn't be able to ping 10.10 hosts to 192.168 hosts.

Hope this clarifies something.

ZA

[Dennis_Newman]

Ok, I can see how this works to allow system at 10.10.10.190 to see printer at 192.168.3 224, and for system at 192.168.3.120 to see the server share at 10.10.10.9, but how do the 10.10 and 192.168 systems "see" their respective internet gates (formerly 10.10.10.1 and 192.168.3.1)?
What do I do for that?

Further information, the 10.10 gateway is a cisco ASA 5512x and the 192.168 gateway is a cisco ASA 5505 - the Extreme switches that we have are Summit 400 48-t's that until now have all been basically used as L2 switches. If I'm reading correctly I need to change the "inside" interface IP on the Ciscos and make sure that the ciscos and the switch know the route to each other, then eventually I can tell the 192.168 vlan to use the 10.10 internet route (but I'm not worried about that yet)

Dennis

[Prashanth_KG]

Hi Dennis,

The router or a Layer 3 switch which takes care of the inter-vlan routing in a network will ideally be the gateway of all the clients or PC.

In our case, if the switch should perform the inter-vlan routing, the IP address of the switches should have the default gateway IP address.

Client IP 10.10.10.xx with gateway IP 10.10.10.1
Switch VLAN 10 IP address 10.10.10.1

Client IP 192.168.3.xx with gateway IP 192.168.3.1
Switch vlan20 IP address 192.168.3.1

IPforwarding should be enabled on the switch for these 2 vlans.

Hope this helps!