Network Management

I just purchased 2 JL253A's to connect 2 networks over point to point wireless devices (2 wirless devices on the roofs of our buildings (about 80ft away from each other).  Currently the wireless is configured as a bridge.  I have two Vlans in building 1 and two Vlans in building 2.  Vlan 1 in both (default vlan) is data while VLAN 200 in both buildings is VoIP.  I want Vlan 1 to talk with Vlan1 and Vlan2 to talk with Vlan2 (each being different IP's) Ex:

Building 1 Vlan 1 192.168.1.0   Vlan 200 192.168.200.0

Building 2 Vlan 1 10.1.100.0     Vlan 200 10.1.200.0

 

Can these layer 3 switches accomplish this?  They don't show any capabilies for Static Routes (as it's Dynamic) nor do I see anything for intervlan (unless I'm missing something).

 

Thank You

Can you tell me a bit about the topology of the network? Is there a internet point on both sides of the link?

You can't have the same VLANs with different IP subnets communicating.

Hi JRWhitehead

Thanks for the response.

 

Yes both locations have their own internet (Comcast).  Both locations have their one phone systems (Mietel) on their own PRI line.

 

I didn't realize that you can't have 2 vlans with the same ID's.  That would mean that I could not use even the default VLAN on one of the sides. (I know, Cisco best practices states one should not use VLAN 1 - to change the default to another vlan :) ).

 

I'm still unsure about traversing over the bridge, to the other buildings network, to access the corresponding vlan (i.e. VoIP to VoIP VLAN or Data to Data VLAN) even if I did change their current VLAN ID's.

I didn't see any interlan option on the Aruba.

 

Thank You

 

Jim

Jim

 

You can't have the same VLAN ID with different IP subnets communicating.

 

I don't have much experience with those switches but looking at the documentation it appears to support static routes.

 

So you could do this:

Building A 

VLAN 1 192.168.1.0  

VLAN 200 192.168.200.0

 

Building B

VLAN 1 10.1.100.0

VLAN 200 10.1.200.0

 

Point 2 Point Link

VLAN 99 172.16.99.0/24

 

Configure VLAN 99 on both switches on and patch the P2P link into them.

Switch A VLAN 99 172.16.99.1

Switch B VLAN 99 172.16.99.2

 

Configure a route on switch A to route traffic to building B networks via switch B.

 

E.g.: 

(switch-a)# ip route 10.1.100.0/24 172.16.99.2

(switch-a)# ip route 10.1.200.0/24 172.16.99.2

 

Then on switch B add the routes going the other way:

 

(switch-b)# ip route 192.168.1.0  /24 172.16.99.1

(switch-b)# ip route 192.168.200.0/24 172.16.99.1

 

 

 

Hi James,

 

Could you tell me which VLAN's in your example are tagged and untagged. 

I assume VLAN 200, VLAN 201 and VLAN 99 are all tagged.

VLAN 1 is default and untagged (which is my data)

 

Thank You

 

Jim

Hi,

I haven't described any ports as being trunked or in access mode. In my example all could be in access mode.

I'm not 100% sure my example would work.

Are the switches layer 3 capable?What is the gateway on your VLANs??

Thanks for the replay!!

 

 Sorry for my late reply.  I was trying to reconfigure the switches to get off VLAN 1 (best practices) and get vmail to email working in Building A.

Currently I have:

Building A: VLAN 100 192.168.1.0  VLAN 200 192.168.200.0

Building B: VLAN 101 10.1.100.0  VLAN 201 10.1.200.0

VLAN's 100 and 101 are data traffic thats untagged

VLAN's 200 and 201 are VoIP traffic thats tagged

 

The Proxima wireless Bridge is connected but I havn't programmed anything on the Aurba switch yet.

Based on your example, I'm creating a VLAN 99 for a port on the Aruba's (both buildings) with static IP's 172.16.99.1 and 2.  I see this would allow for 1 VLAN with same IP's at both ends to pass traffic.

I would direct traffic at either end to 172.16.99.1 or 2 (depending on coming or going).

I still have to get the traffic to the correct VLAN and IP for Voice to goto Voice and Data to goto Data communications.

 

  i.e. VLAN 200 (tagged) with IP address of 192.168.200.20 hits the port with VLAN 99.  It's looking for VLAN 201 for IP 10.1.200.10.

 

I'm still a little confused about this.

 

I know I want t0 separate buildings with separate IP's (not having the buildings joined as one large network as it can cause issues with DHCP and if the wirless bridge went down (buildings run independent).

So same VLANs with same IP range is out.

I also know based on your statements earlier that you can't have 2 same VLANs with different IP's try to communcate - makes sense. 

All this reminds me of VPN - shouldn't have to similar networks (netwoks with same IP's) talking to each other - causes many issues.

 

Could you explain how what I need to do to get the traffic to the destination once it's passed through VLAN99?  Is it as simple as adding a route?

 

Thanks

 

Jim