Completely Puzzled - VLAN / LAGG

Status
Not open for further replies.

aXcelio

Cadet
Joined
Mar 22, 2013
Messages
3
Hi Guys,

I have an issue, that for the life of me I can't figure out. I rebuilt my box based on some networking issues I was having…..as such I went out an purchased a couple of quad port intel ethernet adapters. In setting this up, I went configured a failover lag (which appears to be working fine) which is on a 172.120.140.x/24 network. I configured two additional lags, one being on a 172.120.150.x/24 network the other being on a 172.120.160.x network.

I on the FreeNAS box can ping the IP's associated with these lags, but I cannot ping the gateway for these networks (e.g 172.120.150.2 and 160.2) I can ping them from any other network, but not the FreeNAS box…..which is why I am reaching out to you guys…with hopes that someone here can provide some insight. To add to the mix, two ESXi servers……both with two nic's one on the 150 network, the other on the 160, when establishing an SSH session, I can consistently ping the 150.x interface on the FreeNAS box, but can't ping the 160.x interface at all.

The switch ports on my Cisco small business SG300-10's are setup as follows: access ports, in a trunk, tagged with vLAN 1505 and 1605 (these are going to the FreeNAS box)…….I have the same configuration on the switch ports going to the ESXi boxes. I've not configured vLAN's on the FreeNAS box, nor have I tagged the vLAN's on the ESXi boxes. I have however added static routes on the FreeNAS box representing these networks to no avail……..in short my problem appears to be communication, whereas I don't have consistent access from one network to another……but only on the FreeNAS bo

Can anyone assist?
 

titan_rw

Guru
Joined
Sep 1, 2012
Messages
586
I don't have any answers to your main question, but I thought I'd point something out.

The ip addresses you're using are not private ip's, and defined by RFC1918. I'm assuming these ip ranges have not been allocated to you by IANA.

Using non private ip's on a private lan can cause problems. I would stick to rfc1918 ip's for private use:

10.0.0.0/8
172.16.0.0/12
192.168.0.0/16
 

KTrain

Dabbler
Joined
Dec 29, 2013
Messages
36
Was this issue ever resolved?
 
Status
Not open for further replies.
Top