Nope, this is a misnomer.
No static route should be needed giving the diagram above because there is only one (1) layer-3 device doing any routing, and this device would automatically add to its routing table the directly-connected routes for any IPs assigned to its interfaces - typically VRIs (Virtual Router Interfaces), which are your "interface ve xxx". Other vendors call these SVIs (Software Virtual Interfaces), and those are typically "interface vlan xxx." It is the same concept though.
Regardless, as a general rule of thumb once you place an IP address with its Mask on an interface, that entire subnet will show up in the routing-table as a directly-connected route meaning that layer-3 device owns that subnet.
A static-route would be to tell another layer-3 device that doesn't have that subnet or know how to get to that subnet to get to that subnet via a next-hop IP or via one of its interfaces.
In this case with this diagram, the routing table will look something like this if Op assigns 192.168.1.1/24 to ve 192, and places at least one actual interface that is UP into that VLAN, so the VE changes its state to up/up (required to get the route inserted):
SSH@OPsICX7150#sh ip route
Total number of IP routes: 1
Type Codes - B:BGP D:Connected O:OSPF R:RIP S:Static; Cost - Dist/Metric
BGP Codes - i:iBGP e:eBGP
OSPF Codes - i:Inter Area 1:External Type 1 2:External Type 2
Destination Gateway Port Cost Type Uptime
1 192.168.1.0/24 DIRECT ve 192 0/0 D 1d6h
SSH@OpsICX7150#
There would be other routing table entries for subnets directly-connected on ve 52, and ve 351, too.
****
If you are referring to the server needing a static route, while that's true, it will already have a default route, which is used by the OS to get to any network which is not in the 192.168.1.x network the server is assigned. Any other IP would cause the server to forward those packets to its default-gateway, which if the config tweaks I suggested are made would be 192.168.1.1, and the server would find that being its subnet 192.168.1.3/24 is within the same subnet as the default-gateway. That is to say the server is on the same layer-2 subnet as the default-gateway. In reality, it is just plugged into interface 1/1/1
In Windows, you can do a c:\>print route if you really want from a cmd prompt.
You would be looking for something like this
print route
Unable to initialize device PRN
C:\Users\Netwizz>route print
===========================================================================
Interface List
===========================================================================
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.3 281
