icx 7150 routing

[tony_butler_9y6]

Needing a little help here please.  We have an environment with no router, but we do have a layer 3 switch.  Please refer to the diagram; we have a server with IP address 192.168.1.3 connected to Ethernet port 1 of the Brocade Ruckus ICX 7150 switch.  We have a fiber link on port 9 that goes out to a layer 2 switch.  On port 9 we have virtual interfaces for vlan 51 at 10.174.241.99 and vlan 351 at 11.174.246.99.  From the Brocade Ruckus we can ping the Camera at 11.174.246.30, so we are routing traffic as intended from the Brocade through the layer 2 switch (that has tagging) to the camera at 11.174.246.30.  What we need to do is have the server connect from its IP address of 192.168.1.3 to the camera at 11.174.246.30.  What configuration method would work best to achieve this goal?

[adam_foss]

Duplicate IP somewhere?
you don't have anything else configured as 192.168.1.1 do you?
it could be responding to the pings when you think you are pinging the VE.

[tony_butler_9y6]

Pretty much a closed lab network.  Just the server, ruckus, layer 2 switch, and camera.  Nothing duplicate.  Here's the running config:

RuckusSWitch#sh running-config 
Current configuration:
!
ver 08.0.90eT213
!
stack unit 1
  module 1 icx7150-c12-poe-port-management-module
  module 2 icx7150-2-copper-port-2g-module
  module 3 icx7150-2-sfp-plus-port-20g-module
  stack-port 1/3/1
  stack-port 1/3/2
!
vlan 1 name DEFAULT-VLAN by port
 router-interface ve 1
!
vlan 51 by port
 tagged ethe 1/3/1 
 router-interface ve 51
!
vlan 192 by port
 untagged ethe 1/1/1                                              
 router-interface ve 192
!
vlan 351 by port
 tagged ethe 1/3/1 
 router-interface ve 351
!
aaa authentication web-server default local
aaa authentication enable default local
aaa authentication login default local
aaa authentication login privilege-mode
enable telnet password .....                                      
enable super-user-password .....
enable aaa console
hostname RuckusSWitch
ip add-host-route-first
ip router-id 192.168.2.1
!
username admin password .....
!
sz registrar
!
interface management 1                                            
 ip address 192.168.45.44 255.255.255.0
!
interface ethernet 1/3/1
 speed-duplex 1000-full
!
interface ve 1
!
interface ve 51
 ip address 10.174.241.99 255.255.255.0
!
interface ve 192
 ip address 192.168.1.1 255.255.255.0
!
interface ve 351
 ip address 11.174.246.99 255.255.255.0
!
end

[tony_butler_9y6]

Firewall was turned on at the server blocking our pings.  We can now ping from the ICX 7150 switch to the server, however the server still cannot ping the ve addresses of 10.174.241.99 or 11.174.246.99, or the end devices at 10.174.241.20 and 11.174.246.30.  Any ideas?  Help please.

[tony_butler_9y6]

We've made a few updates since this was posted, but we still can't communicate across the subnets.  I realize I left off a lot of information while trying to stick to the basics.  We've figured a lot out, but we're not there yet.  We made a VE on port 1/1/1 of the ruckus and assigned it vlan 192 with ip 192.168.1.1.  We set the gateway of the server to 192.168.1.1.  We can now ping the gateway on the switch, and from the switch we can ping the server.  We still cannot ping across the subnets.  

The fiber port isn't on port 9, it's actually on port 1/3/1.   

We've added the static routes below on the server, but it didn't help, still can't ping the camera at 11.174.246.30.

route add 10.174.241.0 mask 255.255.255.0 192.168.1.1
route add 11.174.246.0 mask 255.255.255.0 192.168.1.1

Here is a copy of our running switch config:

RuckusSWitch#sh running-config 

Current configuration:
!
ver 08.0.90eT213
!
stack unit 1
  module 1 icx7150-c12-poe-port-management-module
  module 2 icx7150-2-copper-port-2g-module
  module 3 icx7150-2-sfp-plus-port-20g-module
  stack-port 1/3/1
  stack-port 1/3/2
!
vlan 1 name DEFAULT-VLAN by port
 router-interface ve 1
!
vlan 51 by port
 tagged ethe 1/3/1 
 router-interface ve 51
!
vlan 192 by port
 untagged ethe 1/1/1                                             
 router-interface ve 192
!
vlan 351 by port
 tagged ethe 1/3/1 
 router-interface ve 351
!
aaa authentication web-server default local
aaa authentication enable default local
aaa authentication login default local
aaa authentication login privilege-mode
enable telnet password .....                                     
enable super-user-password .....
enable aaa console
hostname RuckusSWitch
ip add-host-route-first
ip router-id 192.168.2.1
!
username admin password .....
!
sz registrar
!
interface management 1                                           
 ip address 192.168.45.44 255.255.255.0
!
interface ethernet 1/3/1
 speed-duplex 1000-full
!
interface ve 1
!
interface ve 51
 ip address 10.174.241.99 255.255.255.0
!
interface ve 192
 ip address 192.168.1.1 255.255.255.0
!
interface ve 351
 ip address 11.174.246.99 255.255.255.0
!

end

Any and all help/suggestions are appreciated.

[tony_butler_9y6]

Our original configurations left out gateway as we had no router and were working on layer 2.  After adding the layer 3 switch with ve's we never went back and added the gateways.  Once we added the ve ip's as the gateways for each device in its subnet it worked like a charm.