Dageezah Posted December 7, 2010 Posted December 7, 2010 I have two VLANs set up.... VLAN (117) no DHCP or ip forwarding VLAN (100) ip forwarding to 10.100.0.1 255.255.252.0 I have tagged my port (C19) on 100 and on 117 I need to access both VLANs but am unable to do so... I think this may be to do with the route table??? I have static address of 10.100.1.165 (255.255.252.0) and also 10.100.13.206 (255.255.255.240) I can access VLAN 100 fine, but cant see anything on 117 Please does anyone have any idea why? I have tried to access the 117 server (10.100.13.200) by doing this.. to no avail! route add 10.100.13.200 MASK 255.255.255.255 10.100.13.206 METRIC 1 IF 1
paulfinlay Posted December 7, 2010 Posted December 7, 2010 your end client that is plugged into port C19 would need to be VLAN aware if this was to work. I imagine as it stands you'll only be able to communicate on the default VLAN as your end client can't tag the VLAN traffic appropriately.
spc-rocket Posted December 7, 2010 Posted December 7, 2010 Hi, You should use the untagged on C19 as workstations and servers should be set to untagged which means they belong to one vlan, at the moment your C19 port is tagged for two vlans i.e. carrying traffic from multiple vlan. The tagging is usually done on swicth to switch connections not on end devices. Ash.
teejay Posted December 7, 2010 Posted December 7, 2010 (edited) I think this can be done with the broadcom and intel network management utilities if I recall corectly, certainly one of them does it but you need that manufacturers nic in the pc/server. Edit: Yep, can be done with the Broadcom Server Manager which can be installed on a workstation as well as long as it has a broadcom nic. You just create a team, add the nic then you have the option to create multiple VLAN connections through virtual adaptors. This is very usefull if you don't want to route between LANS but still need certain machines to access them. Edited December 7, 2010 by teejay 1
Dageezah Posted December 7, 2010 Author Posted December 7, 2010 Hmm, thanks guys, I have about 15 different VLANS and connect to them all fine, but just this one with a 10.100.13.192/255.255.255.252 is causing a problem, which is why I thought it might be a routing issue.
Dageezah Posted December 7, 2010 Author Posted December 7, 2010 Not sure exact models, until I can check tomorrow but its all HP kit, 2510? maybe for the core, then 2910's for the PoE and 2610's for the normal switches.
teejay Posted December 7, 2010 Posted December 7, 2010 Ok, how exactly are you doing the routing between VLANS? I presume you've set up the routes on one of the switches and using that as your default gateway?
Dageezah Posted December 8, 2010 Author Posted December 8, 2010 Our normal switches are 2510's, our PoE switches are 2910al and the Core switch is a 8212zl.. this is the set up on the Core, but then similar on the other switches trunk C10,D10 Trk2 Trunk ip default-gateway 10.100.15.254 ip routing vlan 1 name "DEFAULT_VLAN" untagged E1-E4,F1-F4,G21-G24,Trk2 no untagged A1-A24,B1-B24,C1-C9,C11-C24,D1-D9,D11-D24,G1-G20 no ip address exit vlan 100 name "Curriculum" untagged A3-A4,A18-A20,A22,B2,B6-B12,B18-B22,C12,C17-C20,D12,D18-D20,G2-G10 ip address 10.100.0.1 255.255.252.0 tagged A13-A16,B13-B16,C1-C9,C21-C22,D1-D9,E1-E4,F1-F4,G20-G24,Trk2 ip igmp exit vlan 104 name "WirlesCurric" ip helper-address 10.100.0.8 ip address 10.100.4.1 255.255.254.0 tagged A13-A16,B13-B16,C1-C9,C21-C22,D1-D9,E1-E4,F1-F4,G20-G24,Trk2 ip igmp exit vlan 108 name "WrlesMbook" ip helper-address 10.100.0.8 ip address 10.100.8.1 255.255.254.0 tagged A13-A16,B13-B16,C1-C9,C21-C22,D1-D9,E1-E4,F1-F4,G20-G24,Trk2 ip igmp exit vlan 110 name "Legacy" ip address 10.100.10.1 255.255.254.0 tagged A13-A16,B13-B16,C1-C9,C21-C22,D1-D9,E1-E4,F1-F4,G20-G24 ip igmp exit vlan 112 name "Voice" untagged B1 qos priority 6 tagged A13-A16,B13-B16,C1-C9,C21-C22,D1-D9,E1-E4,F1-F4,G20-G24,Trk2 voice no ip address ip igmp exit vlan 113 name "cctv" ip helper-address 10.100.0.8 ip address 10.100.13.1 255.255.255.192 tagged A13-A16,B13-B16,C1-C9,C21-C22,D1-D9,E1-E4,F1-F4,G20-G24,Trk2 ip igmp exit vlan 114 name "IPTV_DigiSgn" untagged C21-C22,C24,D21-D24 ip address 10.100.13.65 255.255.255.192 tagged A13-A16,B13-B16,C1-C9,D1-D9,E1-E4,F1-F4,G20-G24 ip igmp exit vlan 115 name "CshlesCater" ip helper-address 10.100.0.8 ip address 10.100.13.129 255.255.255.192 tagged A13-A16,B13-B16,C1-C9,C21-C22,D1-D9,E1-E4,F1-F4,G20-G24 ip igmp exit vlan 118 name "ScienceTools" ip address 10.100.13.225 255.255.255.224 tagged A13-A16,B13-B16,C1-C9,C21-C22,D1-D9,E1-E4,F1-F4,G20-G24 exit vlan 120 name "WrlesGuests" ip helper-address 10.100.0.8 ip address 10.100.14.1 255.255.255.0 tagged A13-A16,B13-B16,C1-C9,C21-C22,D1-D9,E1-E4,F1-F4,G20-G24,Trk2 exit vlan 170 name "Management" untagged A17,A24,B4,B17,B23-B24,C11,C13-C16,D11,D13-D17,G1,G11-G20 ip helper-address 10.100.0.8 ip address 172.24.0.1 255.255.254.0 tagged A13-A16,B13-B16,C1-C9,C17-C18,C21-C22,D1-D9,E1-E4,F1-F4,G21-G24,Trk2 exit vlan 180 name "eReg" untagged A5-A12,A21,A23,B3,B5,C23 ip helper-address 10.100.0.8 ip address 172.24.4.1 255.255.255.0 tagged A13-A16,B13-B16,C1-C9,C21-C22,D1-D9,E1-E4,F1-F4,G20-G24 exit vlan 199 name "AuthtyEdge" untagged A1 ip address 10.100.15.249 255.255.255.248 tagged A13-A16,B13-B16,C1-C9,C21-C22,D1-D9,E1-E4,F1-F4,G20-G24 exit vlan 999 name "WANOutsdeLk" tagged A13-A16,B13-B16,C1-C9,C21-C22,D1-D9,E1-E4,F1-F4,G20-G24 no ip address exit vlan 130 name "FtreVlan130" tagged A13-A16,B13-B16,C1-C9,C21-C22,D1-D9,E1-E4,F1-F4,G20-G24 no ip address exit vlan 135 name "FtreVlan135" tagged A13-A16,B13-B16,C1-C9,C21-C22,D1-D9,E1-E4,F1-F4,G20-G24 no ip address exit vlan 140 name "FtreVlan140" untagged A2 tagged A13-A16,B13-B16,C1-C9,C21-C22,D1-D9,E1-E4,F1-F4,G20-G24 no ip address exit vlan 116 name "Access Control" ip helper-address 10.100.0.8 ip address 10.100.13.161 255.255.255.224 tagged A13-A16,B13-B16,C1-C9,C21-C22,D1-D9,E1-E4,F1-F4,G20-G24 exit vlan 117 name "BMS" ip address 10.100.13.193 255.255.255.252 tagged A13-A16,B13-B16,C1-C9,C19,C21-C22,D1-D9,E1-E4,F1-F4,G20-G24 exit vlan 300 name "SamsungUD" no ip address exit
paulfinlay Posted December 8, 2010 Posted December 8, 2010 First off I'd configure the edge port that you are connecting your client to to be an untagged port in VLAN 100 and check if you can ping VLAN 117. on 10.100.13.193 Also the static route you added "route add 10.100.13.200 MASK 255.255.255.255 10.100.13.206 METRIC 1 IF 1" looks to be pointing to the wrong default gateway. You shouldn't need this static route anyway.
jtotheb Posted December 8, 2010 Posted December 8, 2010 Our normal switches are 2510's, our PoE switches are 2910al and the Core switch is a 8212zl.. this is the set up on the Core, but then similar on the other switches vlan 117 name "BMS" ip address 10.100.13.193 255.255.255.252 tagged A13-A16,B13-B16,C1-C9,C19,C21-C22,D1-D9,E1-E4,F1-F4,G20-G24 exit and also 10.100.13.206 (255.255.255.240) Your subnet mask is wrong on the switch. The mask for the VLAN117 (255.255.255.252) would only allow one other host address (10.100.13.194).
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now