Inter-VLAN Routing not working correctly

[IT-SA]

Hello!

I just took over a System Administrator role for a company and trying to figure out what happened to one of their VLANs.
I am new to the Extreme Network devices. They currently have 3 stacked X450-e as their main switch stack/router.
The previous SA setup a new VLAN (VLAN11) to free up some IPs on the main subnet.
Some PCs started dropping from the network last week and we ended up figuring out that the VLAN had been removed from the switch configuration.
I readded it and tried to set everything up as it should be but its not working and I am starting to bang my head against the wall and need some other eyes on this to tell me where the issue might be.

I've gone through all the help guides on here and cannot get a PC to ping another PC on VLAN11 from VLAN1. I cannot even get VLAN11 to pass DHCP to the PC. Static set IP doesn't work either.
DHCP server IP is 192.168.0.17

Here is my current switch config:

[IT-SA]

VLAN Interface with name VLAN11 created by user
Admin State: Enabled Tagging: 802.1Q Tag 11
Description: None
Virtual router: VR-Default
IPv4 Forwarding: Enabled
Primary IP : 192.168.11.1/24
IPv6 Forwarding: Disabled
IPv6: None
STPD: None
Protocol: Match all unfiltered protocols
Loopback: Disabled
NetLogin: Disabled
QosProfile: None configured
Egress Rate Limit Designated Port: None configured
Flood Rate Limit QosProfile: None configured
Ports: 4. (Number of active ports=3)
Untag: *1:41, 2:21, *2:30, *3:7
Flags: (*) Active, (!) Disabled, (g) Load Sharing port
(b) Port blocked on the vlan, (m) Mac-Based port
(a) Egress traffic allowed for NetLogin
(u) Egress traffic unallowed for NetLogin
(t) Translate VLAN tag for Private-VLAN
(s) Private-VLAN System Port, (L) Loopback port
(e) Private-VLAN End Point Port
(x) VMAN Tag Translated port
(G) Multi-switch LAG Group port

[Eric_Burke]

Stupid question - the devices are untagged in V11, correct? Here's the list of items you show there: 1:41, 2:21, 2:30, 3:7. Try dumping a "show port vlan" and make sure that the devices needing to be routed are untagged. At first glance, it looks okay. Issue a "show ipconfig" and "show iproute" and make sure nothing jumps out there. You can also dump the arp cache on a PC (set IP manually first) and make sure the MAC of the DFGW is actually the extreme. Same on the DHCP server.

[IT-SA]

show iproute

Ori Destination Gateway Mtr Flags VLAN Duration
#s Default Route 192.168.0.2 1 UG---S-um--f- Default 5d:22h:16m:30s
d 10.90.0.0/29 10.90.0.1 1 -------um---- replication 5d:22h:16m:43s
#d 192.168.0.0/24 192.168.0.1 1 U------um--f- Default 5d:22h:16m:43s
#d 192.168.11.0/24 192.168.11.1 1 U------um--f- VLAN11 5d:6h:1m:47s
#d 192.168.100.0/24 192.168.100.1 1 U------um--f- VOICE 5d:22h:16m:43s
Origin(Ori): (b) BlackHole, (be) EBGP, (bg) BGP, (bi) IBGP, (bo) BOOTP
(ct) CBT, (d) Direct, (df) DownIF, (dv) DVMRP, (e1) ISISL1Ext
(e2) ISISL2Ext, (h) Hardcoded, (i) ICMP, (i1) ISISL1 (i2) ISISL2
(is) ISIS, (mb) MBGP, (mbe) MBGPExt, (mbi) MBGPInter, (mp) MPLS Lsp
(mo) MOSPF (o) OSPF, (o1) OSPFExt1, (o2) OSPFExt2
(oa) OSPFIntra, (oe) OSPFAsExt, (or) OSPFInter, (pd) PIM-DM, (ps) PIM-SM
(r) RIP, (ra) RtAdvrt, (s) Static, (sv) SLB_VIP, (un) UnKnown
(*) Preferred unicast route (@) Preferred multicast route
(#) Preferred unicast and multicast route
Flags: (B) BlackHole, (b) BFD protection requested, (c) Compressed, (D) Dynamic
(f) Provided to FIB, (G) Gateway, (H) Host Route, (L) Matching LDP LSP
(l) Calculated LDP LSP, (3) L3VPN Route, (m) Multicast, (P) LPM-routing
(p) BFD protection active, (R) Modified, (S) Static, (s) Static LSP
(T) Matching RSVP-TE LSP, (t) Calculated RSVP-TE LSP, (u) Unicast, (U) Up
MPLS Label: (S) Bottom of Label Stack
Mask distribution:
1 default routes 3 routes at length 24
1 routes at length 29
Route Origin distribution:
4 routes from Direct 1 routes from Static
Total number of routes = 5
Total number of compressed routes = 0

[IT-SA]

Yeah, those are the ports I have been playing with trying to get it working.
The ports are untagged.

[IT-SA]

The switch that I uploaded should be the device doing routing.