This post is more than 5 years old
2 Intern
•
129 Posts
0
21779
July 23rd, 2015 10:00
pc6224 vlans & routing
dear everybody
I have a default vlan1 with management interface and a port based vlan2 with "switchport mode access", have given vlan2 an IP and routing then "ip routing" as per docs.
I must be missing something because I still cannot ping that vlan2.
please advise, many thanks.
0 events found
No Events found!


lejeczek
2 Intern
•
129 Posts
0
July 24th, 2015 06:00
I guess I don't quite get "Note: A host has to be in the VLAN for the state to come up." for cannot ping that newly create IP on vlan1.
Ok, and it seems that I had to assign an IP and turn routing on/to my vlan2 and now I can ping vlan1. Without it #show ip route - was empty, now shows:
C 192.168.2.0/24 [0/1] directly connected, vlan 1
C 192.168.3.0/24 [0/1] directly connected, vlan 2
That would makes sense, right? This way having minimum three vlan is a MUST, correct?
lejeczek
2 Intern
•
129 Posts
0
July 24th, 2015 08:00
yes, but it seems a bit strange to me, as I followed those instructions: I had vlan99 and vlan1 with IP x.x.2.254 and I could NOT ping that IP of vlan1. I had to add vlan2 with an IP (x.x.3.254) only then I could ping (from a host) vlan1's IP (x.x.2.254). Not strange?
but I'm not quite there yet - now a host connected to another switch (and this switch links to the switch in question on a port that is unconfigured thus belongs to default vlan1) can ping IP of vlan2 (x.x.3.254) but cannot ping anything else on that vlan2.
Is this switch or hosts or both missing something?
many thanks for your help Daniel.
lejeczek
2 Intern
•
129 Posts
0
July 24th, 2015 10:00
client was connected to both vlan1 & vlan2 with IP x.x.2.10 & x.x.3.10 respectively at the time vlan2 did not have and IP, so effectively it was trying to ping switch's vlan1 x.x.2.254 from client's x.x.2.10 but no replies.
That is why I said "weird" because it was the same one vlan1 on x.x.2.0/24.
Never mind, now when I try to replicate that symptom having vlan2 IP removed it is pinging OK, maybe because switch had not default gateway it did not ping first time. Hmm..
How could I send you a private message with a little scribble of whole topology?
What I've come up with might be a flop, would be great to get an expert insight.
lejeczek
2 Intern
•
129 Posts
0
July 29th, 2015 02:00
ok, that was a missing gateway on a host which in this case was an Equallogic group member, so it pings now ok.
Daniel, having two switches linked up (but not in stack) via A.link and wanting to enable both vlan1 & vlan2 (which exists on both switches) to talk, to see each other across that A.link, I understand that:
a) ports (a single port on each switch) of A.link have to be members of both vlan1 & vlan2? (also default vlan?)
b) these have to be tagged ports?
c) any other precautions when vlan2 is for Equallogic iscsi? (above what's in Equallogic manual)
many thanks.
lejeczek
2 Intern
•
129 Posts
0
July 30th, 2015 04:00
it works, you guys do great job with putting it all online, some others docs I read and pieced it together.
This switches have no firewall/filtering but I imagine there must be a way to control access to the vlans, can you point me in correct direction?
regards