Q1. if I go ahead and setup general mode on port 1/g24 ( i have to tag local created vLANS v10 & v20 instead of ISP supplied vlan ID). (correct? ) I would alter your VLAN IDs to match those of that the ISP is using. If you set to general mode and tag VLAN 10 and 20, the port will send packets tagged according to the VLAN they came from. But if the Cisco device does not know about these VLANs, then when it receives the VLAN tagged packets, it wont know what to do with them.  So if the ISP says that on the cisco device 192.158.13.1 belong to VLAN 110, then on the 6224 change VLAN 10 to VLAN 110. so now the port sends tagged packets to the Cisco, the Cisco sees a tagged packet for VLAN 110, Cisco has a VLAN 110 and it continues forwarding the packet on that VLAN. Q2  the command ip route 192.158.13.0 255.255.255.0 192.158.13.1 will forward the traffic from vlan 10 to outside via  port 24 because it has vlan 10 tagged. (correct? ) Since we will be using a General/Trunk connection, the static route may not even be needed on the 6224. The static route is used to help guide traffic to the next hop in the network. I would set it up without the static route first and see if you have connectivity. If not then look at the network setting on the clients connecting to the switch.  Devices in VLAN 10 IP address= 192.158.13.x Default gateway=192.158.13.1 Devices in VLAN 20 IP address= 192.158.14.x Default gateway=192.158.14.1 Then if still no connection try adding static routes.  Part of getting this to work may come down to trial and error. It is still a little unusual that there is no other device between the 6224 and your ISP. Does the ISP have these cisco devices located in the building your hardware resides in?  
Hello Everyone; Overview:  My ISP provided me with more than Public IP block i.e (192.158.13.1/24, 192.158.14.1/24)  that I would like to assign to my Hypervisor (Citrix XenServer) via vLAN isolation & make it accessible to my VMs to acquire public IPs directly.  (this is actually a requirement of the network I'm setting up).   I would like to know if this scenario is possible to implement via Dell 6224 L3 Switch.   [IMAGE] Network Setup:  - My ISP gave me one link feed to my rack that I'm using (I can assign any IP from both different blocks) that I was given.  - Currently the ISP link going to my Dell Power Connect 6224 L3 Switch port 24 then going to my XenServer box port 15 - I have number of vLANS Setup on the switch that are represented to the XenServer therefore port 15 is trunk port.    What I'm trying to do  Since all VMs requires public IPs .  1. on Dell Switch create 2 vlans 10 & 20  2. Assign public ip to each vlan  3. create route rule on the switch to foreword the traffic to ISP router 4. Add vLAN 10 & 20 to port 15 so my XenServer hypervisor can see the incoming traffic.   My Current Status  i'm unable to to have this working in this order can someone advice if the idea is correct to achieve this task  or I have to design different solution for this to work.  
vLANs for Public IP Assignment 