10

you can copy the configuration from the 'source' switch like this (assuming you've got a domestic software release supporting SSH): show configuration | save user@otherswitch:myconfig And then on 'otherswitch' in edit-mode: load replace myconfig


8

You are looking for the "Logical Interface (Aggregate) Policer": http://www.juniper.net/techpubs/en_US/junos11.4/topics/concept/policer-logical-interface-aggregate-overview.html Unfortunately they are only available on EX9200 (which is a castrated MX) if the information on the EX feature page is correct: http://www.juniper.net/techpubs/en_US/release-...


7

Unfortunately EX switches cannot terminate double-tagged vlans. You would need a bigger box like the MX or M series with IQ/IQ2 module if sticking with Juniper. The best you could do with the EX is strip off the outer-tag and push those inner frames to another EX.


7

This looks like a simple layer two domain. MPLS is typically used only as backbone or distribution transit, that is, among routers. To implement MPLS, you would need to push the VLAN interfaces down to the access switches (and thus split Host5 into a new network or move it to switch 2) and run MPLS among the multilayer switches. Although, this wouldn't bring ...


7

There are 3 real ways to fix this, all of which are fairly simple. Automated Storage Cleanup Juniper has a system cleanup tool for handling this automatically. It operates almost exclusively under the /var/* directory structure; meaning it isn’t all that critical, unless you care about your log files (which you should!). Below is a system storage cleanup ...


6

This issue is a result of the engine-id changing. If you run into this syslog message, that is the exact definition of the problem. Nov 6 09:44:35 MHN00416AN01 snmpd[1260]: SNMPD_ENGINE_ID_CHANGED: Warning: Local engine ID has changed. Passwords for all the users under [edit snmp v3 usm local-engine] need to be reconfigured. Unfortunately, I have ...


6

Per port, not aggregate. Schedulers are not global, rather per interface queue.


6

Interface jsrv.1 is always associated to IP address 128.0.0.127. jsrv up up jsrv.1 up up inet 128.0.0.127/2 An archive at SourceForge has the below command output snippet that shows a connection between 128.0.0.127 and port 6343 (sFlow port)1: tcpdump -v udp port 6343 -s 1500: 11:52:07.624977 IP (tos 0x0, ...


5

You should consider policing since your concern is that they don't get more bandwidth than they have been allotted. This will give you a hard limit. Your shaping in this instance is just ensuring that 31457280 goes into the BE forwarding-class, not that they can't get more bandwidth than 31457280.


5

Rule #1: in a mixed vendor environment, one avoids use of vendor proprietary protocols There are (apparently) several complications attempting to use VSTP (a Juniper protocol) with PVST (RPVST actually, a Cisco protocol) -- while they both run a per-vlan RSTP instance, they don't do it exactly the same (something about tagged/untagged native vlans, etc.) ...


5

Starting with JunOS 12.1 there is wildcard range set in edit mode. You can use it with various range formats, as a starting point "Wildcard range commands for EX switches" is a good read.


5

There is a quite nice and simple solution: We have utilized the voice VLAN to send Magic Packets. Voice VLAN is configurable under: ethernet-switching-options { voip { interface access-dot1x { vlan VOIP; forwarding-class assured-forwarding; } } } We were already using it to connect VoIP phones. The feature ...


5

ARP is an IPv4 process. You are seeing IPv6 traffic. (IPv4 and IPv6 don't share anything beyond the "I" and "P".) What you are seeing is the normal initial messages from a host's interface coming online. Instead of waiting for an RA broadcast (multicast in v6), the host sends a Router Solicitation to trigger any routers to send one ahead of schedule. You ...


4

I don't think it's supported natively. Fortunately you don't need to create the SLAX script yourself, as such script already exists. Essentially you configure normal interface-range, but upon commit its content is expanded to the real interfaces and the interface-range config is removed, creating approximation of the IOS behavior.


4

There's a big difference between "allowed" vlans and "created" vlans. Very few (read: NONE) of the switches I'm aware of can handle 4095 vlans. Entering the equiv of vlan create 1-4095 (i.e. all vlans) will result in an error. switchport trunk allowed vlan 1-4095 is not the same as having all vlans on the switch -- just that the port will not filter any ...


4

You can, of course, also in config mode just: save somefilename And then you move that file to the other switch someway, usign ftp, sftp, scp WinSCP, etc., to the other switch, where you load replace somefilename Another option is to just view the config in the normal way show config and then copy it in your client (clipboard). Then on the new switch, ...


4

Judging by your comments, you're simply trying to simplify your initial set statements. The easiest solution is to use the wildcard range statements released after 12.1. Example usage: user@host# wildcard range set interfaces ge-0/0/[0-23] unit 0 family vpls Equivalent to: user@host# set interfaces ge-0/0/0 unit 0 family vpls user@host# set interfaces ...


4

Quick test: Swap the SFPs with a known working ones on the switch (if possible) and see if the condition stays with the ports or follow the SFPs. If the other SFP works in the current "problematic SFP ports" there is less possibility of this being the switch's problem (I still could be, but just unlikely). You can try to plug it in the other switch's too......


4

Unfortunately the DOM MIB does not seem to be supported on any of the EX 22/32/42/82xx switches. I've been bitten by this in the past. The values are present on the device eg: show interfaces diagnostics optics xe-1/1/0, but not exported into the MIB tree.


4

It looks like you have the VLAN mtnc_os configured on the interface as well. When you add the MTNC_ALOM VLAN it is added to the vlan list. Your port is probably an access port and can only have one VLAN configured. Try to reconfigure your port to a trunk port or remove the existing VLAN before comitting. Paste the output of "show interfaces ge-1/0/44" if ...


4

Junos Olive is an unofficial and unsupported image/version that was developed by Juniper for development purposes. As for the vMX, it's "a full-featured, virtualized MX Series 3D Universal Edge Router" (quote from Juniper). It's an official and supported product that allows the usage of a virtualized MX router in a cloud/virtual network environment. As such, ...


4

You don't have any layer-3 interfaces in area 0 other than the link between the two switches, so you don't have any routes to exchange between them. You need to add the layer-3 interfaces you wish to advertise under the [ protocol ospf ] stanza, preferably as "passive" interface (so you can't inadvertently form adjacencies on those interfaces. For example: ...


4

The sfid process is the software forwarding infrastructure daemon. This process handles all traffic that the switch cannot handle in hardware alone. Common examples of such traffic are: GRE encapsulation ARP resolution management traffic High CPU usage for the sfid process might indicate a problem, and certainly could impact performance when you have ...


4

Q-in-Q on the 4200 is super non-intuitive, but here is the configuration that will work for you: If you're mixing Q-in-Q and dot1q, you need to set the dot1q tunnelling ethertype to be 0x8100 set ethernet-switching-options dot1q-tunneling ether-type 0x8100 Now, configure the interface you'll be receiving the C-TAGs on - note that you will only configure ...


3

If you aren't trying to exchange subnet information with neighboring routers about these /64's, then you'll be fine with the stock EX4200 loadout. However, if you were going to, you'll need routing protocol support (i.e. RIPng, OSPFv3, ISIS, BGP) that only comes with an AFL. Given your design intentions, you don't need the AFL. Check out Juniper's "...


3

For four devices applying a default configuration by hand is a good option. However if you'd like to upgrade or downgrade and apply a default configuration to multiple devices then Zero Touch Provisioning (ZTP) might be a more convenient solution for Juniper hardware. KB27327 has some good information regarding the process as well the Configuring Zero ...


3

You can use a script to share parts of the config quite easily. I use the script share-data. You can create your config like this on the switch/router: groups { juniper-distro { apply-macro share-data { device3; device2; device1; } system { domain-name mydomain.com; ...


3

I followed the directions in this Juniper document: http://kb.juniper.net/InfoCenter/index?page=content&id=KB12022 Briefly, I backed up the configured switch's config file to a USB key, and then mounted the USB key on the new switch, and did a load override /mnt/juniper.conf.gz as per the document's "restore" section. Worked like a champ!


3

It sounds like you're in a bad situation there, and trying to make it worse. Heck, I'm game - the following should get you halfway there: firewall { family ethernet-switching { filter SUBNET-TRAFFIC { term SUBNET-11 { from { source-address { 192.168.1.0/24; ...


3

One thing to keep in mind with trunk redundancy is that STP fails over slowly, even with Rapid STP. If you set up the two links as an aggregated channel, the link failover is much faster. STP failover is the slowest, routing protocol failover is an order of magnitude faster, and the aggregation channel failover is another order of magnitude faster still.


Only top voted, non community-wiki answers of a minimum length are eligible