It doesn't matter which release. This is not supported.


=====

If this worked for you please flag my post as an "Accepted Solution" so others can benefit. A kudo would be cool if you think I earned it.

Yes, this is correct, L2PT is not supported at this moment on QFX5100/EX4600.


=====

If this worked for you please flag my post as an "Accepted Solution" so others can benefit. A kudo would be cool if you think I earned it.

Hello,

After reading various posts in the forum and using Juniper's documentation, we managed to have a working QinQ configuration for our EXs: We can switch packets from a dot1Q trunk to a QinQ.

Example configuration:

# on ge-0/0/10, we send and receive simple tagged packets for VLANs 152-154
set interfaces ge-0/0/10 flexible-vlan-tagging
set interfaces ge-0/0/10 encapsulation extended-vlan-bridge
set interfaces ge-0/0/10 unit 129 vlan-id-list 152-154
set interfaces ge-0/0/10 unit 129 input-vlan-map push
set interfaces ge-0/0/10 unit 129 output-vlan-map pop

# on ge-0/0/22, we send and receive double tagged packets with S-VLAN = 129
set interfaces ge-0/0/22 flexible-vlan-tagging
set interfaces ge-0/0/22 encapsulation extended-vlan-bridge
set interfaces ge-0/0/22 unit 129 vlan-id 129

# Bridging them together
set vlans ID129 interface ge-0/0/10.129
set vlans ID129 interface ge-0/0/22.129

Now, we'd like to put an IP interface on a C-VLAN.

On a cisco 3750, we have a loop to care for the QinQ tunneling and then we can have standard GigabitEthernetxx/xx.C-VLAN interfaces. We haven't been able to replicate the behaviour on our EX.

We tried two different approaches:

• Use the inner/outer-vlan-tag directives => While they are accepted on the EX, we never managed to get them to work. Some forums suggest that it is MX-only?
• Looping a cable, do the de-encapsulation on an interface and put the l3-interface on the trunk => ARP response OK, but no IP traffic got through. Maybe a MAC table issue? We tried disabling MAC learning, it did not help.

Does anyone have experience regarding such configurations? Is it known no to be doable?

Regards,

I have a new EX4500 that I want to add to the existing VC.

So, my question is, do I need the config to be a basic config.?

Or will the VC populate this new EX4500 with the correct config, once I add it to the vc.?

Thanks for the response.

It looks like MC-LAG and vCP are both implementations of the  IEEE 802.1AX-2008 standard.

I can not fine anywhere that says they are compatible. In fact I find that each is a proprietary implementation of the said standard.

In this customers design, they have vCP between datacenters as well as vCP between core/aggregation/access 5K switches locally and at remote sites. If vCP and MC-LAG are proprietary, is there a way to make them interact?

Look for this cookbook and search for MC-LAG

http://networktest.com/jnpriop/cookbook.pdf

I am going to try and attach it

Hi all

Is there an Industrial  L2 Switch from Juniper/or IP65 Switch for outdoor?

Thanks

HI Amal,

Juniper does not have an industrial L2 switch or outdoor switches.

A few alternative options:

* Look at the ACX1100 which is temperature hardened without fans but requires an outdoor rack. It's a router but can do most of the L2 features needed

* ACX500-O has 3 copper and 3 SFP ports in a outdoor casing... but has a high price due to built-in GPS reciever.

Thank you Jonas

Good day everybody.

I have 2 sw ex4200 in virtual chassis/

I know about no-split-detection

But the point is:

When Master fails - Backup becames Master within 1-2 seconds.

But if I reboot new Master ( failed old Master is still down) - New Master became a line card.

If I starts each switch separatly  - it becames a line card.

It's very strange I think. In real life if one of switch fail, I need 1-2 days or so to buy new and change it

BUT if in this time I have a trouble with a light for example - my one Master switch change role to line card. And it's very bad

I use GRES, non-stop-routing also. Configs synchronyzed. And when I look config at switch that became lineecard I can see string with 

set virtual-chassis no-split-detection

HI

Please disable this config set virtual-chassis no-split-detection

This was introduced to avoid split brain. Without this config you should not go into linecard mode.

If it goes also just try the below commands

VC File

% cd /config/
% ls
db                      ssh_host_dsa_key        ssh_host_rsa_key
juniper.conf.1.gz       ssh_host_dsa_key.pub    ssh_host_rsa_key.pub
juniper.conf.2.gz       ssh_host_ecdsa_key      usage.db
juniper.conf.3.gz       ssh_host_ecdsa_key.pub  vchassis
juniper.conf.gz         ssh_host_key
juniper.conf.md5        ssh_host_key.pub
% cd vchassis/
% ls
vc.db                   vc.tlv.db.0             vclocal.conf.tlv
vc.param                vc.tlv.db.1             vclocal.conf.tlv.0
vc.tlv.db               vclocal.conf            vclocal.conf.tlv.1

% rm -rf *.*

And then try request virtual-chassis reactivate.

Thanks

Partha

HI

Are you talking about a scenario where PC / host is directly attached to PE?

Example of such is

QinQ with PC directly connected to PE Devices.

     +---------------+           +-----------------+         +------------------+        +-----------------+
     |               |           |                 |         |                  |        |                 |
     |          0/0/0+-----------+0/0/1        0/0/0---------+0/0/0        0/0/1+--------+0/0/0            |
     +---------------+           +-----------------+         +------------------+        +-----------------+
          2200-A                       4300-A                      4300-B                      2200-B
 
0/0/0-30.30.30.1                  svlan 4000                   svlan 4000                     0/0/0-30.30.30.2
                                  cvlan 100 200                cvlan 100 200                  


2200-A

set interfaces ge-0/0/0 unit 0 family inet address 30.30.30.1/24
set interfaces vlan unit 100 family inet address 10.10.10.1/24
set interfaces vlan unit 200 family inet address 20.20.20.1/24
set ethernet-switching-options storm-control interface all
set vlans v100 vlan-id 100
set vlans v100 interface ge-0/0/0.0
set vlans v100 l3-interface vlan.100
set vlans v200 vlan-id 200
set vlans v200 interface ge-0/0/0.0
set vlans v200 l3-interface vlan.200
                              
4300-A

set interfaces ge-0/0/0 flexible-vlan-tagging
set interfaces ge-0/0/0 encapsulation extended-vlan-bridge
set interfaces ge-0/0/0 unit 4000 vlan-id 4000
set interfaces ge-0/0/1 flexible-vlan-tagging
set interfaces ge-0/0/1 native-vlan-id 50
set interfaces ge-0/0/1 encapsulation extended-vlan-bridge
set interfaces ge-0/0/1 unit 4000 vlan-id-list 50
set interfaces ge-0/0/1 unit 4000 vlan-id-list 100-200
set interfaces ge-0/0/1 unit 4000 input-vlan-map push
set interfaces ge-0/0/1 unit 4000 output-vlan-map pop
set vlans Svlan interface ge-0/0/0.4000
set vlans Svlan interface ge-0/0/1.4000
set vlans v50 vlan-id 50

4300-B

set interfaces ge-0/0/0 flexible-vlan-tagging
set interfaces ge-0/0/0 encapsulation extended-vlan-bridge
set interfaces ge-0/0/0 unit 4000 vlan-id 4000
set interfaces ge-0/0/1 flexible-vlan-tagging
set interfaces ge-0/0/1 native-vlan-id 50
set interfaces ge-0/0/1 encapsulation extended-vlan-bridge
set interfaces ge-0/0/1 unit 4000 vlan-id-list 50
set interfaces ge-0/0/1 unit 4000 vlan-id-list 100-200
set interfaces ge-0/0/1 unit 4000 input-vlan-map push
set interfaces ge-0/0/1 unit 4000 output-vlan-map pop
set vlans Svlan interface ge-0/0/0.4000
set vlans Svlan interface ge-0/0/1.4000
set vlans v50 vlan-id 50

2200-B

set interfaces ge-0/0/0 unit 0 family inet address 30.30.30.2/24
set interfaces vlan unit 100 family inet address 10.10.10.2/24
set interfaces vlan unit 200 family inet address 20.20.20.2/24
set vlans v100 vlan-id 100
set vlans v100 interface ge-0/0/0.0
set vlans v100 l3-interface vlan.100
set vlans v200 vlan-id 200
set vlans v200 interface ge-0/0/0.0
set vlans v200 l3-interface vlan.200

Thanks

Partha

Hope this helps.

QinQ ELS Configs

+------------------+         +------------------+         +--------------------+         +--------------------+
|  EX2200          +---------+  QFX-5100        +---------+  EX3300            +---------+  EX2200            |
|                  |         |                  |         |                    |         |                    |
+----------------0/1/0      0/0/0-------------0/0/23     0/1/0-----------------0/0/0    0/1/0-----------------+
                             +

EX2200

root@2200-Left> show configuration vlans
v200 {
    vlan-id 200;
    interface {
        ge-0/1/0.0;
    }
    l3-interface vlan.200;
}
vlans {
    vlan-id 100;
    interface {
        ge-0/0/0.0;
        ge-0/1/0.0;
    }
}

{master:0}
root@2200-Left> show configuration interfaces vlan.200
family inet {
    address 20.20.20.1/24;
}

QFX5100

root@5100# show interfaces ge-0/0/0
flexible-vlan-tagging;
encapsulation extended-vlan-bridge;
unit 4000 {
    vlan-id-list 100-200;
    input-vlan-map push;
    output-vlan-map pop;
}

{master:0}[edit]
root@5100# show interfaces ge-0/0/23
flexible-vlan-tagging;
encapsulation extended-vlan-bridge;
unit 4000 {
    vlan-id 4000;
}

{master:0}[edit]
root@5100# show vlans
Svlan {
    interface ge-0/0/23.4000;
    interface ge-0/0/0.4000;
}

EX3300

"root@3300# show interfaces ge-0/1/0
unit 0 {
    family ethernet-switching {
        port-mode trunk;
        vlan {
            members 4000;
        }
    }
}

{master:0}[edit]
root@3300# show interfaces ge-0/0/0    
unit 0 {
    family ethernet-switching {
        port-mode access;
        vlan {
            members 4000;
        }
    }
}

{master:0}[edit]
root@3300# show vlans
Svlan {
    vlan-id 4000;
    ##
    ## Warning: requires 'dot1q-tunneling' license
    ##
    dot1q-tunneling {
        customer-vlans 100 200;
        layer2-protocol-tunneling {
            all;
        }
    }
}

{master:0}[edit]
root@3300# show ethernet-switching-options
dot1q-tunneling {
    ether-type 0x8100;
}
storm-control {
    interface all;
}

EX2200

root@2200-Right# show interfaces ge-0/1/0
unit 0 {
    family ethernet-switching {
        port-mode trunk;
        vlan {
            members all;
        }
    }
}

[edit]
root@2200-Right# show vlans
v200 {
    vlan-id 200;
    l3-interface vlan.200;
}

[edit]
root@2200-Right# show interfaces vlan.200
family inet {
    address 20.20.20.2/24;
}


QinQ with PC directly connected to PE Devices.

     +---------------+           +-----------------+         +------------------+        +-----------------+
     |               |           |                 |         |                  |        |                 |
     |          0/0/0+-----------+0/0/1        0/0/0---------+0/0/0        0/0/1+--------+0/0/0            |
     +---------------+           +-----------------+         +------------------+        +-----------------+
          2200-A                       4300-A                      4300-B                      2200-B
 
0/0/0-30.30.30.1                  svlan 4000                   svlan 4000                     0/0/0-30.30.30.2
                                  cvlan 100 200                cvlan 100 200                  


2200-A

set interfaces ge-0/0/0 unit 0 family inet address 30.30.30.1/24
set interfaces vlan unit 100 family inet address 10.10.10.1/24
set interfaces vlan unit 200 family inet address 20.20.20.1/24
set ethernet-switching-options storm-control interface all
set vlans v100 vlan-id 100
set vlans v100 interface ge-0/0/0.0
set vlans v100 l3-interface vlan.100
set vlans v200 vlan-id 200
set vlans v200 interface ge-0/0/0.0
set vlans v200 l3-interface vlan.200
                              
4300-A

set interfaces ge-0/0/0 flexible-vlan-tagging
set interfaces ge-0/0/0 encapsulation extended-vlan-bridge
set interfaces ge-0/0/0 unit 4000 vlan-id 4000
set interfaces ge-0/0/1 flexible-vlan-tagging
set interfaces ge-0/0/1 native-vlan-id 50
set interfaces ge-0/0/1 encapsulation extended-vlan-bridge
set interfaces ge-0/0/1 unit 4000 vlan-id-list 50
set interfaces ge-0/0/1 unit 4000 vlan-id-list 100-200
set interfaces ge-0/0/1 unit 4000 input-vlan-map push
set interfaces ge-0/0/1 unit 4000 output-vlan-map pop
set vlans Svlan interface ge-0/0/0.4000
set vlans Svlan interface ge-0/0/1.4000
set vlans v50 vlan-id 50

4300-B

set interfaces ge-0/0/0 flexible-vlan-tagging
set interfaces ge-0/0/0 encapsulation extended-vlan-bridge
set interfaces ge-0/0/0 unit 4000 vlan-id 4000
set interfaces ge-0/0/1 flexible-vlan-tagging
set interfaces ge-0/0/1 native-vlan-id 50
set interfaces ge-0/0/1 encapsulation extended-vlan-bridge
set interfaces ge-0/0/1 unit 4000 vlan-id-list 50
set interfaces ge-0/0/1 unit 4000 vlan-id-list 100-200
set interfaces ge-0/0/1 unit 4000 input-vlan-map push
set interfaces ge-0/0/1 unit 4000 output-vlan-map pop
set vlans Svlan interface ge-0/0/0.4000
set vlans Svlan interface ge-0/0/1.4000
set vlans v50 vlan-id 50

2200-B

set interfaces ge-0/0/0 unit 0 family inet address 30.30.30.2/24
set interfaces vlan unit 100 family inet address 10.10.10.2/24
set interfaces vlan unit 200 family inet address 20.20.20.2/24
set vlans v100 vlan-id 100
set vlans v100 interface ge-0/0/0.0
set vlans v100 l3-interface vlan.100
set vlans v200 vlan-id 200
set vlans v200 interface ge-0/0/0.0
set vlans v200 l3-interface vlan.200

Hold on.

Did you mean I shoud enable splin-deteciton ?

It's bad scenario for me. Because if I enable splin-deteciton and  Master switch fail - backup switch became a linecard at this mometn and I loss all my traffic.

"if the backup router or switch fails in a two-member Virtual Chassis configuration and split detection is enabled (the default behavior), the master router or switch takes a line-card role, and the line cards (FPCs) that do not host Virtual Chassis ports go offlin"

By the way

Best Practice: We recommend that you disable split detection for a two-member Virtual Chassis configuration if you think the backup router or switch is more likely to fail than the Virtual Chassis port interfaces

Hello Partha,

Many thanks for your answer; it does describe a QinQ configuration for transport, as this other post did show: https://forums.juniper.net/t5/Ethernet-Switching/Q-in-Q-QFX-5100/m-p/307779.

What we're trying to achieve here is different, as we want to have a l3-interface on the same switch that communicates over double dot1Q. Using your configurations, we would need two physical switches to do that, which is not what we're looking for.

Regards,

Hi,

I have bought QFX5100 to my datacenter. I would like configure private vlan domain with about 200 community vlans(one community vlan per customer)

On this qfx there would be L3 interface - irb with public ipv4 and ipv6 on it.  

As there are public ips in pvlans some customers might want to communicate between pvlans. 

Everythig is in this example:

https://www.juniper.net/documentation/en_US/junos/topics/example/private-vlans-multiple-switches-irb-qfx-series.html

"Note: Because the devices in the community and isolated VLANs are isolated at Layer 2, this step is required to allow ARP resolution to occur between the VLANs so that devices using IPv4 can communicate at Layer 3. (For IPv6 traffic, you must explicitly map an IRB address to the destination address to allow ARP resolution.)"

IPv4 is ok when i set proxy-arp, but i dont really understand what it means about ipv6?

Do I have to set static entries on hosts in different communities??

Do you know, anything similar to unrestricted proxy arp on ipv6?

Hello, We recently cahnged our cisco sf300 switch with juniper ex2300. It is great but we have one problem.
The switch is in default configuration only vlans are configured. The Hyper-V host is connected to 10GB xe-0/1/2 with DAC. When i try to ping the Host or the VMs i get DUP! ping response. I did some traffic monitoring and found that only one response is going out from the VM ethernet interface. Here is my config. Please help.

## Last changed: 2017-05-16 11:44:13 EEST
version 15.1X53-D55.5;
system {
    host-name switch1;
    auto-snapshot;
    domain-name local.traykovtrans.com;
    time-zone Europe/Sofia;
    root-authentication {
        encrypted-password ;
    }
    name-server {
        10.10.100.3;
        10.10.100.4;
    }
    services {
        ssh {
            protocol-version v2;
        }
        netconf {
            ssh;
        }
        web-management {
            http {
                interface irb.0;
            }
        }
    }
    syslog {
        user * {
            any emergency;
        }
        file messages {
            any notice;
            authorization info;
        }
        file interactive-commands {
            interactive-commands any;
        }
    }
    ntp {
        server 79.124.14.141;
        server 212.233.131.131;
        server 212.70.148.19;
    }
}
chassis {
    aggregated-devices {
        ethernet {
            device-count 1;
        }
    }
}
interfaces {
    ge-0/0/0 {
        native-vlan-id 100;
        unit 0 {
            family ethernet-switching {
                interface-mode trunk;
                vlan {
                    members [ 30 100 ];
                }
                storm-control default;
            }
        }
    }
    ge-0/0/1 {
        native-vlan-id 100;
        unit 0 {
            family ethernet-switching {
                interface-mode trunk;
                vlan {
                    members [ 30 100 ];
                }
                storm-control default;
            }
        }
    }
    ge-0/0/2 {
        native-vlan-id 100;
        unit 0 {
            family ethernet-switching {
                interface-mode trunk;
                vlan {
                    members [ 30 100 ];
                }
                storm-control default;
            }
        }
    }
    ge-0/0/3 {
        native-vlan-id 100;
        unit 0 {
            family ethernet-switching {
                interface-mode trunk;
                vlan {
                    members [ 30 100 ];
                }
                storm-control default;
            }
        }
    }
    ge-0/0/4 {
        native-vlan-id 100;
        unit 0 {
            family ethernet-switching {
                interface-mode trunk;
                vlan {
                    members [ 30 100 ];
                }
                storm-control default;
            }
        }
    }
    ge-0/0/5 {
        native-vlan-id 100;
        unit 0 {
            family ethernet-switching {
                interface-mode trunk;
                vlan {
                    members [ 30 100 ];
                }
                storm-control default;
            }
        }
    }
    ge-0/0/6 {
        native-vlan-id 100;
        unit 0 {
            family ethernet-switching {
                interface-mode trunk;
                vlan {
                    members [ 30 100 ];
                }
                storm-control default;
            }
        }
    }
    ge-0/0/7 {
        native-vlan-id 100;
        unit 0 {
            family ethernet-switching {
                interface-mode trunk;
                vlan {
                    members [ 30 100 ];
                }
                storm-control default;
            }
        }
    }
    ge-0/0/8 {
        native-vlan-id 100;
        unit 0 {
            family ethernet-switching {
                interface-mode trunk;
                vlan {
                    members [ 30 100 ];
                }
                storm-control default;
            }
        }
    }
    ge-0/0/9 {
        native-vlan-id 100;
        unit 0 {
            family ethernet-switching {
                interface-mode trunk;
                vlan {
                    members [ 30 100 ];
                }
                storm-control default;
            }
        }
    }
    ge-0/0/10 {
        native-vlan-id 100;
        unit 0 {
            family ethernet-switching {
                interface-mode trunk;
                vlan {
                    members [ 30 100 ];
                }
                storm-control default;
            }
        }
    }
    ge-0/0/11 {
        native-vlan-id 100;
        unit 0 {
            family ethernet-switching {
                interface-mode trunk;
                vlan {
                    members [ 30 100 ];
                }
                storm-control default;
            }
        }
    }
    ge-0/0/12 {
        native-vlan-id 100;
        unit 0 {
            family ethernet-switching {
                interface-mode trunk;
                vlan {
                    members [ 30 100 ];
                }
                storm-control default;
            }
        }
    }
    ge-0/0/13 {
        native-vlan-id 100;
        unit 0 {
            family ethernet-switching {
                interface-mode trunk;
                vlan {
                    members [ 30 100 ];
                }
                storm-control default;
            }
        }
    }
    ge-0/0/14 {
        native-vlan-id 100;
        unit 0 {
            family ethernet-switching {
                interface-mode trunk;
                vlan {
                    members [ 30 100 ];
                }
                storm-control default;
            }
        }
    }
    ge-0/0/15 {
        native-vlan-id 100;
        unit 0 {
            family ethernet-switching {
                interface-mode trunk;
                vlan {
                    members [ 30 100 ];
                }
                storm-control default;
            }
        }
    }
    ge-0/0/16 {
        native-vlan-id 100;
        unit 0 {
            family ethernet-switching {
                interface-mode trunk;
                vlan {
                    members [ 30 100 ];
                }
                storm-control default;
            }
        }
    }
    ge-0/0/17 {
        native-vlan-id 1;
        unit 0 {
            family ethernet-switching {
                interface-mode trunk;
                vlan {
                    members [ default 20 30 100 200 300 ];
                }
                storm-control default;
            }
        }
    }
    ge-0/0/18 {
        native-vlan-id 100;
        unit 0 {
            family ethernet-switching {
                interface-mode trunk;
                vlan {
                    members [ 30 100 ];
                }
                storm-control default;
            }
        }
    }
    ge-0/0/19 {
        native-vlan-id 100;
        unit 0 {
            family ethernet-switching {
                interface-mode trunk;
                vlan {
                    members [ 30 100 ];
                }
                storm-control default;
            }
        }
    }
    ge-0/0/20 {
        native-vlan-id 1;
        unit 0 {
            family ethernet-switching {
                interface-mode trunk;
                vlan {
                    members [ 100 200 default ];
                }
                storm-control default;
            }
        }
    }
    ge-0/0/21 {
        native-vlan-id 1;
        unit 0 {
            family ethernet-switching {
                interface-mode trunk;
                vlan {
                    members [ 100 200 default ];
                }
                storm-control default;
            }
        }
    }
    ge-0/0/22 {
        ether-options {
            802.3ad ae0;
        }
    }
    ge-0/0/23 {
        ether-options {
            802.3ad ae0;
        }
    }
    ge-0/1/0 {
        unit 0 {
            family ethernet-switching {
                storm-control default;
            }
        }
    }
    xe-0/1/0 {
        unit 0 {
            family ethernet-switching {
                storm-control default;
            }
        }
    }
    ge-0/1/1 {
        unit 0 {
            family ethernet-switching {
                storm-control default;
            }
        }
    }
    xe-0/1/1 {
        unit 0 {
            family ethernet-switching {
                storm-control default;
            }
        }
    }
    ge-0/1/2 {
        unit 0 {
            family ethernet-switching {
                storm-control default;
            }
        }
    }
    xe-0/1/2 {
        native-vlan-id 1;
        unit 0 {
            family ethernet-switching {
                interface-mode trunk;
                vlan {
                    members [ default 4 20 30 100 200 300 ];
                }
                storm-control default;
            }
        }
    }
    ge-0/1/3 {
        unit 0 {
            family ethernet-switching {
                storm-control default;
            }
        }
    }
    xe-0/1/3 {
        unit 0 {
            family ethernet-switching {
                interface-mode access;
                vlan {
                    members 100;
                }
                storm-control default;
            }
        }
    }
    ae0 {
        description "Switch 2 LAG";
        native-vlan-id 1;
        aggregated-ether-options {
            lacp {
                active;
            }
        }
        unit 0 {
            family ethernet-switching {
                interface-mode trunk;
                vlan {
                    members [ 4 20 30 100 200 300 default ];
                }
            }
        }
    }
    irb {
        unit 0 {
            family inet {
                address 10.10.10.254/24;
            }
        }
        unit 1 {
            family inet {
                address 10.10.20.254/24;
            }
        }
        unit 2 {
            family inet {
                address 10.10.30.254/24;
            }
        }
        unit 3 {
            family inet {
                address 10.10.100.254/24;
            }
        }
    }
}
forwarding-options {
    storm-control-profiles default {
        all;
    }
}
routing-options {
    static {
        route 0.0.0.0/0 next-hop 10.10.10.1;
    }
}
protocols {
    lldp {
        interface all;
    }
    lldp-med {
        interface all;
    }
    igmp-snooping {
        vlan default;
    }
    rstp {
        interface ge-0/0/0;
        interface ge-0/0/1;
        interface ge-0/0/2;
        interface ge-0/0/3;
        interface ge-0/0/4;
        interface ge-0/0/5;
        interface ge-0/0/6;
        interface ge-0/0/7;
        interface ge-0/0/8;
        interface ge-0/0/9;
        interface ge-0/0/10;
        interface ge-0/0/11;
        interface ge-0/0/12;
        interface ge-0/0/13;
        interface ge-0/0/14;
        interface ge-0/0/15;
        interface ge-0/0/16;
        interface ge-0/0/17;
        interface ge-0/0/18;
        interface ge-0/0/19;
        interface ge-0/0/20;
        interface ge-0/0/21;
        interface ge-0/1/0;
        interface xe-0/1/0;
        interface ge-0/1/1;
        interface xe-0/1/1;
        interface ge-0/1/2;
        interface xe-0/1/2;
        interface ge-0/1/3;
        interface xe-0/1/3;
        interface ae0;
    }
}
vlans {
    Guest {
        description "Guest Network";
        vlan-id 200;
    }
    IPCams {
        description "IP Cameras Network";
        vlan-id 20;
        l3-interface irb.1;
    }
    SIP {
        description "MTel SIP Trunk";
        vlan-id 4;
    }
    Storage-1 {
        description "Storage-1 Network";
        vlan-id 300;
    }
    Users {
        description "Users Network";
        vlan-id 100;
        l3-interface irb.3;
    }
    VoIP {
        description "VoIP Network";
        vlan-id 30;
        l3-interface irb.2;
    }
    default {
        description "Default Network";
        vlan-id 1;
        l3-interface irb.0;
    }
}
poe {
    interface all;
}

Hello,

I'm in charge of a branch where currently only an EX2300-C POE switch is deployed.
Besides that there's only a gateway and no aggregation devices.

From what I understand, EX2300-C only supports 10GbE for virtual chassis;
but only 1GbE when using the SFP+ ports for end-device connections.

I'd like to ask for help evaluating options for adding 10GbE connections to servers and storage.

As far as I can find my options are to

(1) Add an EX2300 switch - either with or without virtual chassis.

Pros
. Supports 10GbE for end-device connections (see datasheet)
. Same level of functionality as existing EX2300-C

. Virtual chassis works with existing EX2300-C
. Lower power consumption than other options

Cons
. Additional licenses required for virtual chassis
. Some 10GbE ports sacrificed when using virtual chassis

(2) Replace by one or more EX3400 switches.

Pros
. No additional licenses required for virtual chassis
. Virtual chassis over 40GbE doesn't require sacrificing 10GbE ports (which means more 10GbE ports)
. Same Junos OS version as EX2300
. Less expensive than EX2300 with virtual chassis licenses

Cons
. Existing EX2300-C has to be managed seperately or decommissioned from this branch
. Higher power consumption

(3) Replace by one or more EX4300 switches.

I've also looked into the EX4300 switches but I'm not sure these are for me.
When compared to EX3400 I don't see any added benefit for my setup.

----- ----- ----- ----- -----

Is my evaluation correct so far?

Can someone add more info about 10GbE end-device connections in that setup?

Are there additional options?

Thank you.

Dominic