Switching

last person joined: 11 hours ago 

Ask questions and share experiences about EX and QFX portfolios and all switching solutions across your data center, campus, and branch locations.
Expand all | Collapse all

Set up two vlans on switch and trunk into SRX210

  • 1.  Set up two vlans on switch and trunk into SRX210

    Posted 07-29-2013 12:26

    Hey guys, I'm just getting into using Juniper products, and I've got an issue on my hands.

     

    I have the following set up I would like to deploy:

     

    diagram.png

     

     

     

    My problem is, I can't get anything plugged into either VLAN 10 or VLAN 20 to access the internet or ping anything on the SRX.  I also can't access the management of the EX2200 through the SRX210, nor the other way around.  My other issue is that due to guidelines, I have to have everything in the 192.168.222 subnet.  I've been trying to resolve this for a while now to no avail and would greatly appreciate any input.

     

    Here are my current config files (certain aspects edited for security reasons).  Thank you all so much.

     

     

    EX2200 CONFIG:

    ## Last changed: 2013-07-29 09:16:17 PDT
    version 11.4R1.6;
    system {
        host-name EX2200;
        domain-name juniper.com;
        time-zone America/Los_Angeles;
        root-authentication {
            encrypted-password "PASSWORD HERE";
        }
        name-server {
            7.7.7.7;
            8.8.8.8;
        }
        services {
            ssh {
                protocol-version v2;
            }
            netconf {
                ssh;
            }
            web-management {
                https {
                    system-generated-certificate;
                }
            }
            dhcp {
                router {
                    192.168.222.1;
                }
                pool 192.168.222.1/24 {
                    address-range low 192.168.222.127 high 192.168.222.254;
                }
            }
        }
        syslog {
            user * {
                any emergency;
            }
            file messages {
                any notice;
                authorization info;
            }
            file interactive-commands {
                interactive-commands any;
            }
        }
        ntp {
            server ntp.nasa.gov;
        }
    }
    chassis {
        alarm {
            management-ethernet {
                link-down ignore;
            }
        }
    }
    interfaces {
        ge-0/0/0 {
            unit 0 {
                family ethernet-switching;
            }
        }
        ge-0/0/1 {
            unit 0 {
                family ethernet-switching;
            }
        }
        ge-0/0/2 {
            unit 0 {
                family ethernet-switching;
            }
        }
        ge-0/0/3 {
            unit 0 {
                family ethernet-switching;
            }
        }
        ge-0/0/4 {
            unit 0 {
                family ethernet-switching;
            }
        }
        ge-0/0/5 {
            unit 0 {
                family ethernet-switching;
            }
        }
        ge-0/0/6 {
            unit 0 {
                family ethernet-switching;
            }
        }
        ge-0/0/7 {
            unit 0 {
                family ethernet-switching;
            }
        }
        ge-0/0/8 {
            unit 0 {
                family ethernet-switching;
            }
        }
        ge-0/0/9 {
            unit 0 {
                family ethernet-switching;
            }
        }
        ge-0/0/10 {
            unit 0 {
                family ethernet-switching;
            }
        }
        ge-0/0/11 {
            unit 0 {
                family ethernet-switching;
            }
        }
        ge-0/0/12 {
            unit 0 {
                family ethernet-switching;
            }
        }
        ge-0/0/13 {
            unit 0 {
                family ethernet-switching;
            }
        }
        ge-0/0/14 {
            unit 0 {
                family ethernet-switching;
            }
        }
        ge-0/0/15 {
            unit 0 {
                family ethernet-switching;
            }
        }
        ge-0/0/16 {
            unit 0 {
                family ethernet-switching;
            }
        }
        ge-0/0/17 {
            unit 0 {
                family ethernet-switching;
            }
        }
        ge-0/0/18 {
            unit 0 {
                family ethernet-switching;
            }
        }
        ge-0/0/19 {
            unit 0 {
                family ethernet-switching;
            }
        }
        ge-0/0/20 {
            unit 0 {
                family ethernet-switching;
            }
        }
        ge-0/0/21 {
            unit 0 {
                family ethernet-switching;
            }
        }
        ge-0/0/22 {
            unit 0 {
                family ethernet-switching;
            }
        }
        ge-0/0/23 {
            unit 0 {
                family ethernet-switching {
                    port-mode trunk;
                    vlan {
                        members [ data ex2200mgmt voice ];
                    }
                }
            }
        }
        ge-0/1/0 {
            unit 0 {
                family ethernet-switching;
            }
        }
        ge-0/1/1 {
            unit 0 {
                family ethernet-switching;
            }
        }
        ge-0/1/2 {
            unit 0 {
                family ethernet-switching;
            }
        }
        ge-0/1/3 {
            unit 0 {
                family ethernet-switching;
            }
        }
        vlan {
            unit 0 {
                family inet {
                    address 192.16.222.6/24;
                }
            }
            unit 10 {
                family inet {
                    address 192.16.222.128/24;
                }
            }
            unit 20 {
                family inet {
                    address 192.16.222.192/24;
                }
            }
        }
    }
    routing-options {
        static {
            route 0.0.0.0/0 next-hop 192.168.222.1;
        }
    }
    protocols {
        igmp-snooping {
            vlan all;
        }
        rstp;
        lldp {
            interface all;
        }
        lldp-med {
            interface all;
        }
    }
    ethernet-switching-options {
        storm-control {
            interface all;
        }
    }
    vlans {
        data {
            description "data vlan";
            vlan-id 20;
            interface {
                ge-0/0/12.0;
                ge-0/0/13.0;
                ge-0/0/14.0;
                ge-0/0/15.0;
                ge-0/0/16.0;
                ge-0/0/17.0;
                ge-0/0/18.0;
                ge-0/0/19.0;
                ge-0/0/20.0;
                ge-0/0/21.0;
                ge-0/0/22.0;
            }
            l3-interface vlan.20;
        }
        ex2200mgmt {
            vlan-id 100;
            interface {
                ge-0/0/0.0;
            }
            l3-interface vlan.0;
        }
        voice {
            description "voice vlan";
            vlan-id 10;
            interface {
                ge-0/0/1.0;
                ge-0/0/2.0;
                ge-0/0/3.0;
                ge-0/0/4.0;
                ge-0/0/5.0;
                ge-0/0/6.0;
                ge-0/0/7.0;
                ge-0/0/8.0;
                ge-0/0/9.0;
                ge-0/0/10.0;
                ge-0/0/11.0;
            }
            l3-interface vlan.10;
        }
    }

     

     

    SRX210 CONFIG:

     

    ## Last changed: 2013-07-29 11:06:19 PDT
    version 12.1X44.4;
    system {
        host-name SRX210;
        domain-name OURDOMAINNAME;
        domain-search OURDOMAINNAME;
        time-zone America/Los_Angeles;
        root-authentication {
            encrypted-password "OURPASSWORD";
        }
        name-server {
            7.7.7.7;
            8.8.8.8;
        }
        services {
            ssh;
            xnm-clear-text;
            web-management {
                https {
                    system-generated-certificate;
                    interface [ vlan.0 ge-0/0/0.0 ];
                }
            }
            dhcp {
                router {
                    192.16.222.1;
                }
                pool 192.168.222.0/24 {
                    address-range low 192.168.222.126 high 192.168.222.254;
                }
                propagate-settings ge-0/0/0.0;
            }
        }
        syslog {
            archive size 100k files 3;
            user * {
                any emergency;
            }
            file messages {
                any critical;
                authorization info;
            }
            file interactive-commands {
                interactive-commands error;
            }
        }
        max-configurations-on-flash 5;
        max-configuration-rollbacks 5;
        license {
            autoupdate {
                url https://ae1.juniper.net/junos/key_retrieval;
            }
        }
        ntp {
            server ntp.nasa.gov;
        }
    }
    interfaces {
        ge-0/0/0 {
            unit 0 {
                family inet {
                    address 88.614.191.12/28;
                }
            }
        }
        ge-0/0/1 {
            unit 0 {
                family ethernet-switching {
                    vlan {
                        members vlan-trust;
                    }
                }
            }
        }
        fe-0/0/2 {
            unit 0 {
                family ethernet-switching {
                    port-mode access;
                    vlan {
                        members vlan-trust;
                    }
                }
            }
        }
        fe-0/0/3 {
            unit 0 {
                family ethernet-switching {
                    port-mode access;
                    vlan {
                        members vlan-trust;
                    }
                }
            }
        }
        fe-0/0/4 {
            unit 0 {
                family ethernet-switching {
                    vlan {
                        members vlan-trust;
                    }
                }
            }
        }
        fe-0/0/5 {
            unit 0 {
                family ethernet-switching {
                    vlan {
                        members vlan-trust;
                    }
                }
            }
        }
        fe-0/0/6 {
            unit 0 {
                family ethernet-switching {
                    vlan {
                        members vlan-trust;
                    }
                }
            }
        }
        fe-0/0/7 {
            unit 0 {
                family ethernet-switching {
                    port-mode trunk;
                    vlan {
                        members [ voice data ];
                    }
                }
            }
        }
        st0 {
            unit 2 {
                family inet;
            }
            unit 3 {
                family inet;
            }
            unit 4 {
                family inet;
            }
            unit 5 {
                family inet;
            }
        }
        vlan {
            unit 0 {
                family inet {
                    address 192.168.222.1/24;
                }
            }
            unit 10 {
                family inet {
                    address 192.168.222.128/24;
                }
            }
            unit 20 {
                family inet {
                    address 192.168.222.192/24;
                }
            }
        }
    }
    routing-options {
        static {
            route 0.0.0.0/0 next-hop 88.614.191.12/28;
        }
    }
    protocols {
        rstp;
    }
    security {
        ike {
            traceoptions {
                file ike-trace;
                flag all;
            }
        }
        flow {
            inactive: traceoptions {
                file jtac size 3m world-readable;
                flag packet-drops;
                flag basic-datapath;
                packet-filter pf1 {
                    source-prefix 192.168.222.129/32;
                    destination-prefix 4.2.2.2/32;
                }
                packet-filter pf2 {
                    source-prefix 4.2.2.2/32;
                    destination-prefix 192.168.222.129/32;
                }
            }
        }
        screen {
            ids-option untrust-screen {
                icmp {
                    ping-death;
                }
                ip {
                    source-route-option;
                    tear-drop;
                }
                tcp {
                    syn-flood {
                        alarm-threshold 1024;
                        attack-threshold 200;
                        source-threshold 1024;
                        destination-threshold 2048;
                        timeout 20;
                    }
                    land;
                }
            }
        }
        nat {
            source {
                rule-set trust-to-untrust {
                    from zone trust;
                    to zone untrust;
                    rule nat-off {
                        match {
                            source-address 192.168.222.0/24;
                            destination-address 192.168.112.0/24;
                        }
                        then {
                            source-nat {
                                off;
                            }
                        }
                    }
                    rule source-nat-rule {
                        match {
                            source-address 0.0.0.0/0;
                        }
                        then {
                            source-nat {
                                interface;
                            }
                        }
                    }
                }
            }
        }
        policies {
            from-zone trust to-zone untrust {
                policy trust-to-untrust {
                    match {
                        source-address any;
                        destination-address any;
                        application any;
                    }
                    then {
                        permit;
                        log {
                            session-init;
                            session-close;
                        }
                    }
                }
            }
            from-zone trust to-zone trust {
                policy policy_out_Burbank {
                    match {
                        source-address addr_88_614_191_12/28;
                        destination-address addr_192_168_222_0;
                        application any;
                    }
                    then {
                        permit;
                    }
                }
                policy policy_in_Burbank {
                    match {
                        source-address addr_192_168_222_0;
                        destination-address addr_88_614_191_12/28;
                        application any;
                    }
                    then {
                        permit;
                    }
                }
            }
            from-zone untrust to-zone trust {
                policy untrust-to-trust {
                    match {
                        source-address any;
                        destination-address any;
                        application any;
                    }
                    then {
                        permit;
                        log {
                            session-init;
                            session-close;
                        }
                    }
                }
            }
            from-zone voice-zone to-zone untrust {
                policy voice-to-untrust {
                    match {
                        source-address any;
                        destination-address any;
                        application any;
                    }
                    then {
                        permit;
                        log {
                            session-init;
                            session-close;
                        }
                    }
                }
            }
            from-zone data-zone to-zone untrust {
                policy data-to-untrust {
                    match {
                        source-address any;
                        destination-address any;
                        application any;
                    }
                    then {
                        permit;
                        log {
                            session-init;
                            session-close;
                        }
                    }
                }
            }
        }
        zones {
            security-zone trust {
                address-book {
                    address addr_88_614_191_12/28 88.614.191.12/28;
                    address addr_192_168_222_0 192.168.222.0/24;
                }
                host-inbound-traffic {
                    system-services {
                        all;
                    }
                    protocols {
                        all;
                    }
                }
                interfaces {
                    vlan.0 {
                        host-inbound-traffic {
                            system-services {
                                all;
                            }
                            protocols {
                                all;
                            }
                        }
                    }
                }
            }
            security-zone untrust {
                screen untrust-screen;
                host-inbound-traffic {
                    system-services {
                        ike;
                    }
                }
                interfaces {
                    ge-0/0/0.0 {
                        host-inbound-traffic {
                            system-services {
                                https;
                                ike;
                                ssh;
                            }
                            protocols {
                                all;
                            }
                        }
                    }
                }
            }
            security-zone voice-zone {
                host-inbound-traffic {
                    system-services {
                        all;
                    }
                    protocols {
                        all;
                    }
                }
                interfaces {
                    vlan.10 {
                        host-inbound-traffic {
                            system-services {
                                all;
                            }
                            protocols {
                                all;
                            }
                        }
                    }
                }
            }
            security-zone data-zone {
                host-inbound-traffic {
                    system-services {
                        all;
                    }
                    protocols {
                        all;
                    }
                }
                interfaces {
                    vlan.20 {
                        host-inbound-traffic {
                            system-services {
                                all;
                            }
                            protocols {
                                all;
                            }
                        }
                    }
                }
            }
        }
    }
    vlans {
        data {
            vlan-id 20;
            l3-interface vlan.20;
        }
        vlan-trust {
            vlan-id 3;
            l3-interface vlan.0;
        }
        voice {
            vlan-id 10;
            l3-interface vlan.10;
        }
    }

     

     



  • 2.  RE: Set up two vlans on switch and trunk into SRX210

    Posted 07-29-2013 15:00

    Well, I did not  have time to download and look at it in any detail. But a quick glance shows that you have not tied any of your L2 ports on the SRX to any of your VLAN's. 



  • 3.  RE: Set up two vlans on switch and trunk into SRX210

    Posted 07-29-2013 15:41

    @Muttbarker

     

    I was under the impression that trunking all the ports from the EX2200 into the fe-0/0/7 port would cause me to have no need for L2 ports.  Is this incorrect?

     

    @Keithr

     

    It's not possible to have 2 vlans on the same subnet?  I would like the all IPs from 192.168.222.128 to 192.168.222.191 be dedicated for voice lines, and all IPs from 192.168.222.192 to 192.168.222.254 be dedicated to data lines.  Sorry for my newbieness, but I'm still trying to figure out how to set all these different network portions up.



  • 4.  RE: Set up two vlans on switch and trunk into SRX210

    Posted 07-29-2013 15:51

    @Avum_David wrote:

    I was under the impression that trunking all the ports from the EX2200 into the fe-0/0/7 port would cause me to have no need for L2 ports.  Is this incorrect?


    Your trunk port on the SRX will only carry VLANs 10 and 20 as you have it configured.  You also have a VLAN mismatch -- VLAN id 3 on the SRX and VLAN id 100 on the EX, and that won't work if you're trying to trunk them.  The VLAN numbers need to match because the 802.1Q header contains the VLAN ID for every frame.  If they don't match, the devices will throw away frames that it doesn't have a corresponding VLAN for.  Those are your L2 problems.

     

    Your L3 problem as I mentioned is with the /24 subnet shared across 3 VLANs.  If you want all the devices in the same /24 subnet, use 1 VLAN.  If you want 3 VLANs, segment your address space.

     



  • 5.  RE: Set up two vlans on switch and trunk into SRX210

    Posted 07-29-2013 16:05

    @Avum_David wrote:

     

    @keithr

     

    It's not possible to have 2 vlans on the same subnet?  I would like the all IPs from 192.168.222.128 to 192.168.222.191 be dedicated for voice lines, and all IPs from 192.168.222.192 to 192.168.222.254 be dedicated to data lines.  Sorry for my newbieness, but I'm still trying to figure out how to set all these different network portions up.


    VLANs are a layer 2 construct.

     

    IP space / ranges are a layer 3 construct.

     

    If your goal is simply to have addresses grouped, then you can simply manage your IP space as such when you allocate addresses.  No need for VLANs or multiple routed interfaces.

     

    If your requirements provide that you need to have a different Layer 2 segment for your devices, then you can use VLANs.  However your VLANs can't share the same /24 subnet.

     

    As I take a closer look at your configs, I see that you have L3 interfaces on both your EX and your SRX, however you're trying to connect them together with a trunk (L2).  You're mixing L2 and L3 where you really can't.  Your EX is going to try and act as a router for the connected VLANs, and the SRX is going to think that it's directly connected to those same segments, and it's not.  The EX has a 0/0 default route to the SRX, but the SRX has no route back to the EX, the SRX thinks itself is the gateway for those segments.

     

    The result is a conflict between L2 and L3 worlds on this network.

     

    I'd suggest you take a step back and look at the drawing board again.  Decide if you need L2 segmentation on your LAN or if simply managing / grouping your IP addresses logically is sufficient.  If you need L2 segmentation, then decide if your SRX is going to provide security between your LAN segments or if its only purpose is to provide security to/from the Internet (but no security between the LAN segments).

     

    Then you will have to decide where L2 boundaries exist and how to determine whether to trunk VLANs between devices or route traffic between devices (but not both).



  • 6.  RE: Set up two vlans on switch and trunk into SRX210

    Posted 07-30-2013 00:43

    "If your requirements provide that you need to have a different Layer 2 segment for your devices, then you can use VLANs.  However your VLANs can't share the same /24 subnet."

     

    PVLANS can allow him to do this. However without reading the rest of the config, not sure if this is what he wants to do. But there is not hard requirements that they must be absolutely different subnets. 

    Or for thaat matter, filter based vlans.



  • 7.  RE: Set up two vlans on switch and trunk into SRX210

    Posted 07-30-2013 10:42

    @lyndidon wrote:

     

    PVLANS can allow him to do this. However without reading the rest of the config, not sure if this is what he wants to do. But there is not hard requirements that they must be absolutely different subnets. 

    Or for thaat matter, filter based vlans.


    I think you're unnecessarily overcomplicating things and are likely to cause confusion.

     

    I strongly advocate keeping designs and implementations as simple as possible.

     

    The focus should be on defining the problem clearly and looking for a simple, clean, efficient solution rather than presenting a non-working case and then applying myriad complex tactics to achieve what would otherwise be a very simple goal.

     

    Based on the information given, I see absolultey no reason that PVLANs, filter-based VLANs, etc., are at all appropriate in this situation.  It appears to simply be a matter of someone who is learning the ins-and-outs of network administration and has gotten a little mixed up with switching vs. routing.  It's a simple problem, so we should try to keep the solutions simple to help the person learn.



  • 8.  RE: Set up two vlans on switch and trunk into SRX210
    Best Answer

    Posted 07-30-2013 16:28

    Avum_David:

     

    Here is a simple design and some suggestions for implementation.

     

    3 VLANs:

     

    ID | Description          | IP Subnet
       |                      |
    10 | Network Management   | 192.168.222.0/26
    30 | Voice                | 192.168.222.128/26
    40 | Data                 | 192.168.222.192/26
    

     

    Notice that VLAN 20 is left open (192.168.222.64/26).  This is for future growth should you need it, and it keeps your other 3 subnets the same size and using the address ranges you previously specified.

     

    /26 subnets means your subnet mask will be 255.255.255.192

     

    You will configure the 3 VLANs on your SRX with l3-interfaces:

     

    vlans {
      network-devices {
        description "Network Device Management";
        vlan-id 10;
        l3-interface vlan.10;
      }
      voice {
        description "Voice";
        vlan-id 30;
        l3-interface vlan.30;
      }
      data {
        description "Data";
        vlan-id 40;
        l3-interface vlan.40;
      }
    }

     

    Your L3 interfaces on the SRX could look something like this:

     

    interfaces {
      vlan {
        unit 10 {
          description "Network Device Management";
          family inet {
            address 192.168.222.1/26;
          }
        }
        unit 30 {
          description "Voice";
          family inet {
            address 192.168.222.129/26;
          }
        }
        unit 40 {
          description "Data";
          family inet {
            address 192.168.222.193/26;
          }
        }
      }
    }

     

    You can leave your default static route configured in the SRX.

     

    Here's a start for your DHCP pools (configured on the SRX😞

     

    dhcp {
      pool 192.168.222.128/26 {
        address-range low 192.168.222.130 high 192.168.222.190;
        router {
          192.168.222.129;
        }
        propagate-settings ge-0/0/0.0;
      }
      pool 192.168.222.192/26 {
        address-range low 192.168.222.194 high 192.168.222.254;
        router {
          192.168.222.193;
        }
        propagate-settings ge-0/0/0.0;
      }
    }

     

    I would suggest you put the 3 VLANs into separate security zones, this is a starting point but you'll probably want to tweak it (configured on the SRX😞

     

    zones {
      security-zone network-management {
        host-inbound-traffic {
          system-services {
            all;
          }
          protocols {
            all;
          }
        }
        interfaces {
          vlan.10;
        }
      }
      security-zone voice {
        host-inbound-traffic {
          system-services {
            all;
          }
          protocols {
            all;
          }
        }
        interfaces {
          vlan.30;
        }
      }
      security-zone data {
        host-inbound-traffic {
          system-services {
            all;
          }
          protocols {
            all;
          }
        }
        interfaces {
          vlan.40;
        }
      }
    }
    

     

     

    From there, if you fully trust your internal networks, you can configure simple any/any/permit policies between the zones.  You should probably restrict the network management zone so that you can easily control who can SSH to devices, etc.  You can also now create proper policies so that, for example, your data network can get to the Internet (from-zone data to-zone untrust), but your phones and network devices probably shouldn't be doing so.  Or maybe just in very controlled cases, etc.

     

    On your EX, remove your L3 interfaces for VLANs 30 and 40 (after you re-number the VLANs and clean up the configs).  Keep an L3 interface for VLAN 10, since that will be used for device management.  Optionally, you can of course use the me0 management interface, but I'll leave that as an exercise for you to read up on if you decide to go that route.

     

    Your EX config would look like this (relevant parts, of course):

     

    interfaces {
      vlan {
        unit 10 {
          description "Network Device Management";
          family inet {
            address 192.168.222.2/26;
          }
        }
      }
      
      ge-0/0/23 {
        unit 0 {
          family ethernet-switching {
            port-mode trunk;
          }
        }
      }
    }
    [ ... ]
    vlans { voice { description "Voice"; vlan-id 30; interface { ge-0/0/0.0; ge-0/0/1.0; ge-0/0/2.0; ge-0/0/3.0; ge-0/0/4.0; ge-0/0/5.0; ge-0/0/6.0; ge-0/0/7.0; ge-0/0/8.0; ge-0/0/9.0; ge-0/0/10.0; ge-0/0/11.0; ge-0/0/23.0; } } data { description "Data"; vlan-id 40; interface { ge-0/0/12.0; ge-0/0/13.0; ge-0/0/14.0; ge-0/0/15.0; ge-0/0/16.0; ge-0/0/17.0; ge-0/0/18.0; ge-0/0/19.0; ge-0/0/20.0; ge-0/0/21.0; ge-0/0/22.0; ge-0/0/23.0; } } network-devices { description "Network Device Management"; vlan-id 10; interface { ge-0/0/23.0; } l3-interface vlan.10; } }

     

    All 3 VLANs will be trunked (making sure the IDs match across devices) between your SRX and EX.  Keep your EX's default route pointed to your SRX.

     

    I've noticed that you were doing VLAN assignement in different ways on your EX vs. the SRX, and also you were using both methods on the EX itself.  It's easier to stick with one or the other, whichever is your preference.  If you look at the EX config above, I moved everything for your VLAN config into the vlan { } configuration stanza.  Note how all 3 VLANs on the EX are configured with interface ge-0/0/23.0 -- that's your trunk port and the configuration for that interface was cleaned up to simply set it as a trunk port.

    You were using the other method, configuring VLANs under each interface's configuration stanza, on your SRX, so I kept that method on the SRX.  On the SRX, the trunk port will look like this:

    interfaces {
      fe-0/0/7 {
        description "Trunk to EX";
        unit 0 {
          family ethernet-switching {
            port-mode trunk;
            vlan {
              members [ network-devices voice data ];
            }
          }
        }
      }
    }

     

    You do not need to do any DHCP relay or anything on the EX.  Remove the DHCP configuration on your EX completely (delete system services dhcp).

     

    That should get you started.  I may have missed a point or two, but this is a basic primer and should get you in the right direction.  Be sure you pay attention to subnet masks and proper / usable IP addresses within each subnet.  Post your questions here after you start over as outlined here and we can help you further if needed.

     

    Remember that you'll need to go through the configurations for both devices and clean up all the VLAN numbers and make sure they're corrected everywhere, and any other housekeeping that might need to be done.

     



  • 9.  RE: Set up two vlans on switch and trunk into SRX210

    Posted 07-29-2013 15:18

    The first thing I noticed was that you have 3 VLANs and 3 IP addresses tied to the same /24 subnet.

     

    That's going to cause problems on your SRX.  You'll need to separate your VLANs / IP subnet space correctly.



  • 10.  RE: Set up two vlans on switch and trunk into SRX210

    Posted 07-30-2013 00:47

    "I have to have everything in the 192.168.222 subnet. I've been trying to resolve this for a while now to no avail and would greatly appreciate any input."
    That requirement can be met; you have to use PVLANS. Let me look at the rest of the config.

     

    A little bit to add to what the others have noticed. You may want to decide exactly how you want the two devices to operate. Do you want to use your Switch for L2 and the SRX for L3?
    So you are pretty much running the SRX as a switch also and you apply L2 Security policies. Ok.
    I do not see any allowance for the ex2200mgmt vlan on the SRX. You have it configured to allow the voice and dat vlans, I can see how that would affect your accessing it from the SRX.
    In the meantime lets just test one thig at a time. Disable the voice vlan interfaces aand test if you get traffic from the data vlan. Making sure the workstations have the correct gateway which would be the address on the vlan.20 interface. Conversely the phones would have to have the gateway as the address on the vlan.10 interface.

    dhcp {
    router {
    192.16.222.1;
    }
    pool 192.168.222.0/24 {
    address-range low 192.168.222.126 high 192.168.222.254;
    }
    propagate-settings ge-0/0/0.0;

    dhcp {
    router {
    192.168.222.1;
    }
    pool 192.168.222.1/24 {
    address-range low 192.168.222.127 high 192.168.222.254;
    }
    }
    }

    I see you have configured both the EX and the SRX as DHCP servers. Use one. If you chose the SRX, then configure EX as DHCP relay. There are quite a bit of conflicts as the others have pointed out. I would go back to the drawing board and plan out exactly what roles you want the devices to play then configure them as such.
    It is much easier to configure the switch with the relevant vlans and use filterbased vlan assignment or PVLANs, in you case i would suggest PVLANS. The configure the SRX as security and then your trunk ports would allow your vlans to communicate with the SRX and the SRX would deal with the security.



  • 11.  RE: Set up two vlans on switch and trunk into SRX210

    Posted 07-30-2013 10:53

    @lyndidon wrote:

    "I have to have everything in the 192.168.222 subnet. I've been trying to resolve this for a while now to no avail and would greatly appreciate any input."

     

    That requirement can be met; you have to use PVLANS. Let me look at the rest of the config.


    PVLAN is absolutely not necessary to meet this requirement.

     

    The /24 can simply be segmented into /26 or /27 subnets.  DHCP can be used with open pools using regular VLANs.

     

    Based on what I've seen thus far, I think that's closest to the original intent.

     



  • 12.  RE: Set up two vlans on switch and trunk into SRX210

    Posted 07-31-2013 09:32

    Words can't express how grateful I am to you guys.  I think what we'll end up doing for our network eventually is using two seperate switches to meet the demands for the amount of connections we'll have, but for the time being, I'll configure the switch as per suggested above. 

     

    Again, I thank you for taking the time to help me with this issue.