Hi,

We have two distributed offices and there are connected right now but only using 2 VLans from the provider. We want to use QinQ and one of these two Vlans to extend all of our vlans between these two sites.

Office one :

EX4200– All Vlans and routing on it

(Read this one already: https://www.juniper.net/documentation/en_US/junos/topics/example/qinq-tunneling-ex-series.html )

Office two

EX3400 – all vlans and routing on it

(Read this one already: https://www.juniper.net/documentation/en_US/junos/topics/task/configuration/qinq-tunneling-ex-series-cli-els.html )

I have read juniper examples for configuring QinQ, but there it is supposed to have traffic arriving/leaving  from/to customer ports at end switches. In my case we don’t have specific customer port. All of our vlans are defined and used on only these two switches.

Con you give me some advice how is the correct way to do it ?

Regards,

Georgi

I have problem with EX3300 (Junos 15.1R6-S2.1) which is connected to EX4300-32F (14.1X53-D45.3). EX3300 is sending SNMP traps every second with errors regarding LLDP and discarded TLVs.

root@EX33> show lldp neighbors
Local Interface    Parent Interface    Chassis Id          Port info          System Name
ge-0/1/3.0         -                   XX:XX:XX:XX:XX:XX         PII                       EX43
root@EX33> show lldp statistics
Interface    Parent Interface  Received  Unknown TLVs  With Errors  Discarded TLVs  Transmitted  Untransmitted
ge-0/1/3.0   -                 9666      0             134050       134050          9701         0
root@EX43> show lldp neighbors
Local Interface    Parent Interface    Chassis Id          Port info          System Name
ge-0/0/0           -                   XX:XX:XX:XX:XX:XX          Uplink               EX33
root@EX43> show lldp statistics
Interface    Parent Interface  Received  Unknown TLVs  With Errors  Discarded TLVs  Transmitted  Untransmitted
ge-0/0/0     -                 2576      0             0            0               2583         0

I tried disabling SNMP traps for LLDP yet the command doesnt work like it should as described in below KB:

https://www.juniper.net/documentation/en_US/junos/topics/task/configuration/layer-2-services-lldp-configuring.html

https://www.juniper.net/documentation/en_US/junos/topics/reference/configuration-statement/lldp-configuration-notification-interval-edit-protocols-lldp.html

{master:0}[edit protocols lldp]
root@EX33# set ptopo-configuration-trap-interval 0
{master:0}[edit protocols lldp]
root@EX33# set lldp-configuration-notification-interval 0
                                                               ^
Value 0 is not within range (5..3600) at '0'
root@EX33# show
ptopo-configuration-trap-interval 0;

Don't know how to troubleshoot this problem and fix it. I also don't have any idea how to stop the flood of SNMP traps beside disabling LLDP on all uplinks for EX3300.

Added a 10gb SFP and made it Layer-2 uplink, now getting this error.

Total bandwidth allocation for low priority queues exceeds 100 percent for scheduler-map juniper-port-profile-map

I am not sure what to change.!!

class-of-service {
    classifiers {
        dscp juniper_dscp_classifier {
            import default;
            forwarding-class voice {
                loss-priority low code-points [ 101110 011000 ];
            }
            forwarding-class video {
                loss-priority low code-points [ 100000 100010 ];
            }
        }
        ieee-802.1 juniper_ieee_classifier {
            import default;
            forwarding-class voice {
                loss-priority low code-points [ 110 101 011 ];
            }
            forwarding-class video {
                loss-priority low code-points 100;
            }
        }
    }
    forwarding-classes {
        class voice queue-num 3;
        class video queue-num 4;
        class expedited-forwarding queue-num 1;
        class assured-forwarding queue-num 2;
        class best-effort queue-num 0;
    }
    interfaces {
        ge-* {
            scheduler-map juniper-port-profile-map;
            unit 0 {
                classifiers {
                    dscp juniper_dscp_classifier;
                    ieee-802.1 juniper_ieee_classifier;
                }
            }
        }
        xe-* {
            scheduler-map juniper-port-profile-map;
            unit 0 {
                classifiers {
                    dscp juniper_dscp_classifier;
                    ieee-802.1 juniper_ieee_classifier;
                }
            }
        }
    }
    scheduler-maps {
        juniper-port-profile-map {
            forwarding-class voice scheduler strict-priority-scheduler;
            forwarding-class video scheduler expedited-scheduler;
            forwarding-class assured-forwarding scheduler assured-scheduler;
            forwarding-class best-effort scheduler best-effort-scheduler;
        }
    }
    schedulers {
        strict-priority-scheduler {
            buffer-size percent 5;
            priority strict-high;
        }
        expedited-scheduler {
            transmit-rate percent 30;
            buffer-size percent 30;
            priority low;
        }
        assured-scheduler {
            transmit-rate percent 25;
            buffer-size percent 25;
            priority low;
        }
        best-effort-scheduler {
            transmit-rate percent 35;
            buffer-size percent 40;
            priority low;
        }
    }
}

We have a stack of two EX4500s that form the core of our network in a hub and spoke configuration. Our 24 edge data closets all have stacks of EX4200s that terminate at the core via single mode fiber and SFPs. We have 8 servers and two storage arrays in our data center that are connected to the core using 10G DAC cabling. Eighteen of the 20 vlans that are configured have routable interfaces so we are using the EX4500s for layer 3.

We will soon be replacing this setup with a stack of EX4600s. In order to get the proper 10G port count, we will be using some Juniper DACBO cables which break out a 40G port on this switch into 4x10G ports. My question is how easy will this transition be with our Junos switch code? We are currently running Junos 15.1R6-S2 on the EX4500s. Can our current code be dropped onto the EX4600s, cleaned up a bit, and just run?

I have multiple MC-LAG deployments at an extreamly large site. Occasionally I need to track a MAC address to an access port, so I get the MAC assosicated with the devices IP address off of my firewall then login to the access switch and do show ethernet-switching table | match <MAC>. The problem is some MAC addresses associate with the aggergation interface (ae0.0) instead of the physical interface then I have no idea what acesse port I need to look at.

So my question is why do some MACs in the ARP table associate with the logical interface while others associate with the physical interface? WIll MAC address associating with ae0.0 cause problems? And is there another way to see which MAC addresses are connected to what interface?

(Example)

pack-plc 00:07:af:e6:be:a0 D - ge-0/0/7.0
pack-plc 00:07:af:e6:c7:b0 D - ge-0/0/18.0
pack-plc 00:07:af:e7:49:00 D - ge-0/0/10.0
pack-plc 00:0c:29:0f:0b:b9 D - ae0.0
pack-plc 00:0c:29:1c:86:a0 D - ae0.0
pack-plc 00:0c:29:52:25:66 D - ae0.0

In several weeks we will take delivery of two EX4600s to replace two EX4500's at the core of our network. I want to get a jump on the layout of the interfaces before these switches arrive. This is what I do know

    - Each EX4600 comes with 24 SFP+ ports

    - We are adding two 8 port expansion modules to each switch

    - We are adding two DACBO cables to each switch. These breakout two of the 40Gbe ports into a total of eight 10GBe

    - These two switches will be in a virtual chassis by connecting two of their QSFP+ ports

What I am not sure of are the interface names. The 24 SFP+ ports seem straight forward using Media-SwitchInStack/0/PortNumber

Port numbers range between 0 and 23

For example, xe-0/0/10

What I am not sure of are the interface names for the two expansion modules, the DACBO cabling, or the QSFP+ ports connected to form the virtual chassis. I have read these two articles multiple times and am still confused

https://www.juniper.net/documentation/en_US/junos/topics/concept/interfaces-naming-conventions-qfx-series.html

https://www.juniper.net/documentation/en_US/junos/topics/task/configuration/qfx3500-3600-standalone-channel-configuring.html

I have just taken delivery of several EX4600 switches.  THese will be stacked with a couple of EX4300 switches.  Looking at the configuration it shows that the 4 40Gb QSFP ports are apparently channelized.  It shows the ports et-0/0/24 through et-0/0/27 as each having virtual interfaces of xe-0/0/x:0 through xe-0/0/x:3.  I understand that to stack using the QSFP ports they cannot be channelized.  

All I have found is to use a command 'edit chassis fpc 0 pic 0 port port-number and then set channel-speed to disable-auto-speed-detection as shown here: (https://www.juniper.net/documentation/en_US/junos/topics/task/configuration/qfx3500-3600-standalone-channel-configuring.html)

but doing so still shows the sub xe interfaces for each et interface.  It appears they are still channelized.

How can I disable channelization for the 4 40gb ports?  I am brand new to junos so this is new to me.

Hello Experts,

I'm  a newbie to Juniper!

I have a got a couple of EX4300 which I am trying to authenticate against a Cisco ACS server using Radius. I see  that authentication requests are reaching to the ACS and ACS reports show that the authentication request is permitted by ACS. But still I am not able to login to Juniper device. However, I am still able to login with the local creds that I defined in Juniper device.

Here is the relevant config:

User@EX4300-2> show configuration system radius-server 
10.10.11.68 {
    secret "xxxxxxxxxx"; ## SECRET-DATA
    source-address 10.10.1.100;
}

Any help with this would be appreciated!

I have a support case open, but the engineer want to try reproducing the issue in their lab which could be a few days. So I thought I'd, ask the community as well.

The switches in question are EX4300s running the current JTAC recommended software(14.1X53-D45). They were installed over the weekend, and replaced EX4200s which did not have any issue.

I am having problems with DHCP in a primarily wireless environment.  DHCP is set up on a server and a DHCP relay pointing to that server is configured for several subnets. The initial DHCP request sequence of Discover, Offer, Request, ACK succeeds in all cases, as well, the periodic DHCP Request packets when a client requests an IP renew (or when doing ipconfig /renew) succeed. These renews are unicast to the server.

The issue is when a client roams to an access point on a new subnet. After wireless association, the client sends a DHCP Renew (broadcast this time), which the server does not see. The client repeats the DHCP Renew until it times out. Eventually, the client starts the DHCP process over again starting with a Discover, and gets an IP. This whole process is 1-3 minutes. On occasion (5% or less), it will work correctly and the server will recieve the Renew request broadcast from the relay, reply with a NAK, and the client will send the DHCP Discover immediatley and get an IP.

I have checked with another compuer running Wireshark and associated to the same access point, that the DHCP Renew broadcast is being forwarded by the AP, just not seen by the server.

This feels like a software bug to me..

Hello,

Can anyone please confirm if this is right way to convert an L2 switch to a L3 routed ported in Ex4300.

user@EX4300-2> show configuration interfaces ge-0/0/17 
unit 0 {
    family inet {
        address 1.1.1.1/24;
    }
}

Hi,

We have restored configuration file on EX4200 and successfully commit the configuration. All interface configuration already there on EX.

But while i run "show interface terse" command, there is no interface shown on the screen.

I also run "show chassis fpc" command but there is no result.

Plz suggest how can i fix this issue.

Thank you..

Hi,

I have stucked in creating a simple trunk between switch and server. I have created trunks between switches and all of them work fine. But trunk to server just doesn't work. 

Short story, I'm migrating a linux server from Cisco switch to Juniper switch. Server has redundant trunk ports.

In Cisco my standard trunk port config for such a port was:

interface GigabitEthernet0/23
 switchport trunk encapsulation dot1q
 switchport trunk allowed vlan 110-112,114-116,122,145,160,173,174
 switchport mode trunk
 storm-control broadcast level 20.00
 spanning-tree portfast
 spanning-tree bpduguard enable

And that was flying like a boss.

I assumed in Juniper it should be easy enough to do this config:

    ge-0/0/40 {
        unit 0 {
            family ethernet-switching {
                interface-mode trunk;
                vlan {
                    members [ 110-112 114-116 122 145 160 173-174 ];
                }
                storm-control default;
            }
        }
    }

Why the hell that doesn't work ? 

Good time gentlemen!

We are going to purchase this switch, I have a question regarding the operation of the mirror (analyzer)

ethernet-switching-options {
analyzer COPM {
input {
ingress {
interface ae3;
interface ae4;
interface xe-0/0/12;
interface xe-0/0/13;
}
}
output {
interface {
xe-0/0/11.0;
}
}
}
ethernet-switching-options {
analyzer DPI {
input {
ingress {
interface ae3;
interface ae4;
interface ge-0/0/14;
interface ge-0/0/15;
}
}
output {
interface {
xe-0/0/10.0;
}
}
}

Will this configuration work here? I need to do a mirror traffic with mixed ports of the source in different destination ports in several analyzer sessions.

I read the https://www.juniper.net/documentation/en_US/junos/topics/concept/port-mirroring-ex-series.html#port-mirror-terminology and https://kb.juniper.net/InfoCenter/index?page=content&id=KB21200 but I do not fully understand

JUNOS 15.1R6-S2.1 and its EX 3300 

Hello.
Company has an headquarter and several remore branch offices. Provider provides L2 VPN from the HQ to the each branch office. To the HQ packets comes into the VLANs. One branch - 1 VLAN.
At the HQ there are 1 cable from the provider and it's connected to Juniper EX2200 JunOS 11.4R1.6 at port ge-0/0/23. Port ge-0/0/4 is connected to the LAN of the HQ.

IP addressing is the same at the HQ and branches.
The goal is to give an access to the local resources of the HQ to a branch and vice versa.
On the Juniper there are created VLANs with provider's IDs 1800-1807. They are named. Port ge-0/0/23 is setted as trunk and is a member of all VLANs.
Problem is, I can assign to ge-0/0/4 only 1 VLAN. And there will be a connection to only 1 branch. But if I make another access port with another VLAN ID and connect it to the HQ LAN, then only one of them will be working. And I can't switch ge-0/0/4 to trunk because it's goes to the simple switch.

With this Juniper, how can I make the HQ to see all of the branches? And I need to the IP addressing stays the same.

I installed several SFP's in an EX4500, they do not show as present.

This is a VC, do I need to boot just the one member to make the SFP's show up.?

Thanks

We had a vendor come in and help setup our environment, and since I'm basically a noob when it comes to this stuff (though did try out some setting changes) I'm asking for your assistance. I've never been too sure about the current settings and if they are actually setup correctly or not. For instance it seems like the queues are usually in a different order and our DSCP code-points look sparse for AF. We have VoIP and some video, otherwise we are fairly generic when it comes to traffic. Below is the configuration for a EX3300, any suggestions or things that you would change would be very much appreciated. If anything, just to give me the piece of mind that things are good.

set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-NC loss-priority low code-points 110000
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-EF loss-priority low code-points 101110
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-AF loss-priority low code-points 100010
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 000000
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 000001
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 000010
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 000011
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 000100
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 000101
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 000110
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 000111
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 001000
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 001001
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 001010
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 001011
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 001100
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 001101
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 001110
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 001111
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 010000
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 010001
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 010010
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 010011
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 010100
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 010101
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 010110
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 010111
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 011000
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 011001
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 011010
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 011011
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 011100
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 011101
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 011110
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 011111
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 100000
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 100001
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 100011
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 100100
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 100101
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 100110
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 100111
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 101000
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 101001
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 101010
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 101011
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 101100
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 101101
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 101111
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 110001
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 110010
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 110011
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 110100
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 110101
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 110110
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 110111
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 111000
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 111001
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 111010
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 111011
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 111100
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 111101
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 111110
set class-of-service classifiers dscp CLASSIFIER-DSCP forwarding-class FC-BE loss-priority low code-points 111111
set class-of-service forwarding-classes class FC-EF queue-num 3
set class-of-service forwarding-classes class FC-NC queue-num 2
set class-of-service forwarding-classes class FC-AF queue-num 1
set class-of-service forwarding-classes class FC-BE queue-num 0
set class-of-service interfaces ge-* scheduler-map SCHEDMAP-ALL
set class-of-service interfaces ge-* unit 0 classifiers dscp CLASSIFIER-DSCP
set class-of-service interfaces ge-* unit 0 rewrite-rules dscp RWR-ALL
set class-of-service interfaces xe-* scheduler-map SCHEDMAP-ALL
set class-of-service interfaces xe-* unit 0 classifiers dscp CLASSIFIER-DSCP
set class-of-service interfaces xe-* unit 0 rewrite-rules dscp RWR-ALL
set class-of-service interfaces ae* scheduler-map SCHEDMAP-ALL
set class-of-service interfaces ae* unit 0 classifiers dscp CLASSIFIER-DSCP
set class-of-service interfaces ae* unit 0 rewrite-rules dscp RWR-ALL
set class-of-service rewrite-rules dscp RWR-ALL forwarding-class FC-NC loss-priority low code-point 110000
set class-of-service rewrite-rules dscp RWR-ALL forwarding-class FC-EF loss-priority low code-point 101110
set class-of-service rewrite-rules dscp RWR-ALL forwarding-class FC-AF loss-priority low code-point 100010
set class-of-service rewrite-rules dscp RWR-ALL forwarding-class FC-BE loss-priority low code-point 000000
set class-of-service scheduler-maps SCHEDMAP-ALL forwarding-class FC-AF scheduler SCHED-AF
set class-of-service scheduler-maps SCHEDMAP-ALL forwarding-class FC-BE scheduler SCHED-BE
set class-of-service scheduler-maps SCHEDMAP-ALL forwarding-class FC-EF scheduler SCHED-EF
set class-of-service scheduler-maps SCHEDMAP-ALL forwarding-class FC-NC scheduler SCHED-NC
set class-of-service schedulers SCHED-NC transmit-rate percent 20
set class-of-service schedulers SCHED-NC buffer-size percent 20
set class-of-service schedulers SCHED-NC priority strict-high
set class-of-service schedulers SCHED-EF shaping-rate percent 10
set class-of-service schedulers SCHED-EF buffer-size percent 10
set class-of-service schedulers SCHED-EF priority strict-high
set class-of-service schedulers SCHED-AF transmit-rate percent 30
set class-of-service schedulers SCHED-AF buffer-size percent 30
set class-of-service schedulers SCHED-AF priority low
set class-of-service schedulers SCHED-BE transmit-rate remainder
set class-of-service schedulers SCHED-BE buffer-size remainder
set class-of-service schedulers SCHED-BE priority low

Thoughts, comments? Absolute trash? Very good, wouldn't change a thing?

Hello All,

I'm completely new to JUNOS, and I came across an EX4200-24P that I'm trying incorporate into a small home office network.  I cannot figure out how to configure a default static route to a cable modem with a DHCP IP.  

I can pull the IP from the modem, but it is not static.  So I would have to re-configure the route after every power cycle.  In Cisco, I could simply route all traffic (0.0.0.0/0) to an interface, but I cannot figure out how to do it in JUNOS.   

Any insight is appreciated.

I understand what jumbo frames are and the purpose for them.  Larger frames with less header data etc.  My question is about the best place to use them and where not to use them.

We have some site to site rpelication traffic that is currently set to use jumbo frames.  If I allow jumbo frames on the MPLS link.  Does that mean that all traffic uses jumbo frames?  Does normal workstation traffic that is using standard frames get changed to a jumbo frame before transmit.    If not - I am trying to see the con of allowing jumbo frames. 

My assumption was that you only allow jumbo frames where it is really needed.  If allowing jumbo frames within the network does not impact standard frame traffic - what is the downside of allowing it everywhere ?

Thanks
John