Switching

Is this switch is capable of stand alone inter vlan routing or needs help for higher end L3 switch / Router? 

 

to do OSPF requires an advanced license, but it will certainly do Static, and (I THINK) RIP without any licenses.  I'm not 100% sure if there are any limitations for OSPF or not with the license

 

IIRC no BGP support period.

 

Will

The EX2200 is a layer 3 switch and supports RVIs, so you should be able to do inter-vlan routing directly on it.

The software abilities of all the EX series switches is locate at http://www.juniper.net/techpubs/en_US/junos/topics/concept/ex-series-software-features-overview.html#layer-3-protocols-features-by-platform-table

 

The ex2200 does support RVI's, but doesn't support virtual routers.  Depending on what you are trying to accomplish, you may be able to get your configuration working without the help of a higher-end L3 device.

What do virtual routers have to do with inter-vlan routing? Unless he wants each VLAN to have its own seperate routing table (which wouldn't really be inter-vlan routing), all he needs is to setup RVIs.

acording to KB10972, Juniper EX series support L3-interface Vlan which is called Routed Vlan Interface (RVI) without any specific license.

just create vlan name and vlan-id,  assign interface into vlan, Create the subnet for the VLAN’s, and then promote vlan into L3 should be fine

I creating  L3 interface with this switch but  inter vlan is not working properly

 

client in vlan 1 can ping to L3 interface of Vlan 1, L3 interface in Vlan 2 and client to Vlan 2

 

but client in vlan 2  to cannot ping client in vlan 3 but can ping L3 interface of Vlan 1 and Vlan 2

 

at the coreswitch I'm able to ping the client of both Vlans

 

 

Please check my configuration of the coreswitch  attached the configuration of Coreswitch

 

I need to achieve the following 

 

all vlans can access the internet through firewall

other Vlans will able to access server Vlans.

 

 

 

 

 

I'm not sure you are going to be able to route traffic through your firewall with this type of setup. The configuration below allows for access between all vlans. I'm using vswitches in vmware instead of physical switches for the access layer. I haven't been able to get the clients to route to the Internet without using virtual routers.
## Last changed: 2011-05-08 08:27:23 UTC
version 11.1R2.3;
system {
services {
ssh;
dhcp {
pool 192.168.101.0/24 {
address-range low 192.168.101.50 high 192.168.101.100;
name-server {
8.8.8.8;
}
router {
192.168.101.2;
}
}
pool 192.168.102.0/24 {
address-range low 192.168.102.50 high 192.168.102.100;
name-server {
8.8.8.8;
}
router {
192.168.102.2;
}
}
pool 192.168.200.0/24 {
address-range low 192.168.200.50 high 192.168.200.100;
name-server {
8.8.8.8;
}
router {
192.168.200.2;
}
}
}
}
syslog {
user * {
any emergency;
}
file messages {
any notice;
authorization info;
}
file interactive-commands {
interactive-commands any;
}
}
}
interfaces {
ge-0/0/0 {
description "Trunk to SRX210 ge-0/0/0";
unit 0 {
family inet {
address 10.10.200.2/24;
}
}
}
ge-0/0/1 {
description "Trunk to ESX vSwitch3";
unit 0 {
family ethernet-switching {
port-mode trunk;
vlan {
members Intranet;
}
}
}
}
ge-0/0/13 {
description "Trunk to ESX vSwitch2";
unit 0 {
family ethernet-switching {
port-mode trunk;
vlan {
members [ Customer_1 Customer_2 ];
}
}
}
}
me0 {
unit 0 {
family inet {
address 192.168.1.252/24;
}
}
}
vlan {
unit 101 {
description "Customer_1 l3 Interface";
family inet {
address 192.168.101.2/24;
}
}
unit 102 {
description "Customer_2 l3 Interface";
family inet {
address 192.168.102.2/24;
}
}
unit 200 {
description "Intranet l3 Interface";
family inet {
address 192.168.200.2/24;
}
}
}
}
routing-options {
traceoptions {
file routing;
flag all;
}
static {
defaults {
active;
}
route 192.168.101.0/24 next-hop 192.168.101.2;
route 192.168.102.0/24 next-hop 192.168.102.2;
route 192.168.200.0/24 next-hop 192.168.200.2;
route 0.0.0.0/0 next-hop 10.10.200.1;
route 10.10.200.0/24 next-hop 10.10.200.2;
}
}
protocols {
igmp-snooping {
vlan all;
}
rstp;
lldp {
interface all;
}
lldp-med {
interface all;
}
}
ethernet-switching-options {
storm-control {
interface all;
}
}
vlans {
Customer_1 {
vlan-id 101;
l3-interface vlan.101;
}
Customer_2 {
vlan-id 102;
l3-interface vlan.102;
}
Intranet {
vlan-id 200;
l3-interface vlan.200;
}
}

The problem is in your trunk. please add all the vlan member in your trunk.
Second is you do not need to add
route 192.168.101.0/24 next-hop 192.168.101.2;
route 192.168.102.0/24 next-hop 192.168.102.2;
route 192.168.200.0/24 next-hop 192.168.200.2;
i think its useless.

Just try it.

You are right about the next hop.

As long as the gateway is set to be the RVI for the hosts with in theVLAN the traffic should pass between VLAN's.