Please send the configuration of both VC switches to look further.
Thanks
Amit
↧
Re: connecting EX4300 VC to EX4600 non-VC
↧
Scheduled JUNOS upgrade
Hello
Is there any way to schedule automatic upgrade of JUNOS in EX series swithces. For exampe
We have 50 number of swithes that need upgrade and I need some kind of script that can schedule the upgrade of JUNOS code at specific period of time without any user intervention.
Overall means automatic upgarde of JUNOS at specific period of time.
Thanks in advance !!!
Amit
↧
↧
Re: connecting EX4300 VC to EX4600 non-VC
I removed some non-sense to make the configs shorter:
EX4600A:
version 14.1X53-D35.3;
system {
**REMOVED**
}
}
syslog {
user * {
any emergency;
}
file messages {
any notice;
authorization info;
}
file interactive-commands {
interactive-commands any;
}
}
processes {
inactive: dhcp-service {
traceoptions {
file dhcp_logfile size 10m;
level all;
flag all;
}
}
app-engine-virtual-machine-management-service {
traceoptions {
level notice;
flag all;
}
}
}
ntp {
**REMOVED**
}
}
chassis {
aggregated-devices {
ethernet {
device-count 249;
}
}
}
interfaces {
xe-0/0/0 {
description Area-A;
unit 0 {
family ethernet-switching {
interface-mode trunk;
vlan {
members vlan240;
}
}
}
}
xe-0/0/1 {
description area-B;
unit 0 {
family ethernet-switching {
interface-mode trunk;
vlan {
members vlan232;
}
}
}
}
et-0/0/24 {
description trunk-to-B-node;
unit 0 {
family ethernet-switching {
interface-mode trunk;
vlan {
members all;
}
}
}
**REMOVED**
em1 {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ex4600-40f;
}
}
}
}
irb {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ex4600-40f;
}
}
}
unit 200 {
family inet {
address 172.18.200.2/21 {
vrrp-group 200 {
virtual-address 172.18.200.1;
priority 200;
accept-data;
}
}
}
}
unit 208 {
family inet {
address 172.18.208.2/21 {
vrrp-group 208 {
virtual-address 172.18.208.1;
priority 200;
accept-data;
}
}
}
}
unit 216 {
family inet {
address 172.18.216.2/21 {
vrrp-group 216 {
virtual-address 172.18.216.1;
priority 200;
accept-data;
}
}
}
}
unit 224 {
family inet {
address 172.18.224.2/21 {
vrrp-group 224 {
virtual-address 172.18.224.1;
priority 200;
accept-data;
}
}
}
}
unit 232 {
family inet {
address 172.18.232.2/21 {
vrrp-group 232 {
virtual-address 172.18.232.1;
priority 200;
accept-data;
}
}
}
}
unit 240 {
family inet {
address 172.18.240.2/21 {
vrrp-group 240 {
virtual-address 172.18.240.1;
priority 200;
accept-data;
}
}
}
}
unit 248 {
family inet {
address 172.18.248.2/22 {
vrrp-group 248 {
virtual-address 172.18.248.1;
priority 200;
accept-data;
}
}
}
}
}
vme {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ex4600-40f;
}
}
}
}
}
forwarding-options {
storm-control-profiles default {
all;
}
}
protocols {
inactive: ospf {
traceoptions {
file OSPF-DEBUG.txt size 5m files 5;
flag error detail;
flag hello detail;
}
area 0.0.0.41 {
interface irb.232;
interface irb.248;
interface irb.240;
interface irb.224;
interface irb.216;
interface irb.208;
interface irb.200;
interface xe-0/0/22.0;
}
}
lldp {
interface all;
}
lldp-med {
interface all;
}
igmp-snooping {
vlan default;
}
rstp {
interface xe-0/0/0;
interface xe-0/0/1;
interface xe-0/0/2;
interface xe-0/0/3;
interface xe-0/0/4;
interface xe-0/0/5;
interface xe-0/0/6;
interface xe-0/0/7;
interface xe-0/0/8;
interface xe-0/0/9;
interface xe-0/0/10;
interface xe-0/0/11;
interface xe-0/0/12;
interface xe-0/0/13;
interface xe-0/0/14;
interface xe-0/0/15;
interface xe-0/0/16;
interface xe-0/0/17;
interface xe-0/0/18;
interface xe-0/0/19;
interface xe-0/0/20;
interface xe-0/0/21;
interface xe-0/0/22;
interface xe-0/0/23;
interface et-0/0/24;
interface xe-0/0/24:0;
interface xe-0/0/24:1;
interface xe-0/0/24:2;
interface xe-0/0/24:3;
interface et-0/0/25;
interface xe-0/0/25:0;
interface xe-0/0/25:1;
interface xe-0/0/25:2;
interface xe-0/0/25:3;
interface et-0/0/26;
interface xe-0/0/26:0;
interface xe-0/0/26:1;
interface xe-0/0/26:2;
interface xe-0/0/26:3;
interface et-0/0/27;
interface xe-0/0/27:0;
interface xe-0/0/27:1;
interface xe-0/0/27:2;
interface xe-0/0/27:3;
}
}
vlans {
default {
vlan-id 1;
l3-interface irb.0;
}
vlan200 {
vlan-id 200;
l3-interface irb.200;
}
vlan208 {
vlan-id 208;
l3-interface irb.208;
}
vlan216 {
vlan-id 216;
l3-interface irb.216;
}
vlan224 {
vlan-id 224;
l3-interface irb.224;
}
vlan232 {
vlan-id 232;
l3-interface irb.232;
}
vlan240 {
vlan-id 240;
l3-interface irb.240;
}
vlan248 {
vlan-id 248;
l3-interface irb.248;
}
}
{master:0}
EX4600B:
version 14.1X53-D35.3;
system {
**REMOVED**
}
syslog {
user * {
any emergency;
}
file messages {
any notice;
authorization info;
}
file interactive-commands {
interactive-commands any;
}
}
processes {
dhcp-service {
traceoptions {
file dhcp_logfile size 10m;
level all;
flag all;
}
}
app-engine-virtual-machine-management-service {
traceoptions {
level notice;
flag all;
}
}
}
ntp {
**REMOVED**
}
}
chassis {
aggregated-devices {
ethernet {
device-count 249;
}
}
}
interfaces {
xe-0/0/0 {
description Area-A;
unit 0 {
family ethernet-switching {
interface-mode trunk;
vlan {
members vlan240;
}
}
}
}
xe-0/0/1 {
description area-B;
unit 0 {
family ethernet-switching {
interface-mode trunk;
vlan {
members vlan232;
}
}
}
}
xe-0/0/2 {
description area-C1;
unit 0 {
family ethernet-switching {
vlan {
members vlan216;
}
}
}
}
et-0/0/24 {
description trunk-to-A-node;
unit 0 {
family ethernet-switching {
interface-mode trunk;
vlan {
members all;
}
}
}
}
**REMOVED**
em1 {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ex4600-40f;
}
}
}
}
irb {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ex4600-40f;
}
}
}
unit 200 {
family inet {
address 172.18.200.3/21 {
vrrp-group 200 {
virtual-address 172.18.200.1;
priority 150;
}
}
}
}
unit 208 {
family inet {
address 172.18.208.3/21 {
vrrp-group 208 {
virtual-address 172.18.208.1;
priority 150;
}
}
}
}
unit 216 {
family inet {
address 172.18.216.3/21 {
vrrp-group 216 {
virtual-address 172.18.216.1;
priority 150;
}
}
}
}
unit 224 {
family inet {
address 172.18.224.3/21 {
vrrp-group 224 {
virtual-address 172.18.224.1;
priority 150;
}
}
}
}
unit 232 {
family inet {
address 172.18.232.3/21 {
vrrp-group 232 {
virtual-address 172.18.232.1;
priority 150;
}
}
}
}
unit 240 {
family inet {
address 172.18.240.3/21 {
vrrp-group 240 {
virtual-address 172.18.240.1;
priority 150;
}
}
}
}
unit 248 {
family inet {
address 172.18.248.3/22 {
vrrp-group 248 {
virtual-address 172.18.248.1;
priority 150;
}
}
}
}
}
vme {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ex4600-40f;
}
}
}
}
}
forwarding-options {
storm-control-profiles default {
all;
}
}
protocols {
inactive: ospf {
traceoptions {
file OSPF-DEBUG.txt size 5m files 5;
flag error detail;
flag hello detail;
}
area 0.0.0.41 {
interface irb.232;
interface irb.248;
interface irb.240;
interface irb.224;
interface irb.216;
interface irb.208;
interface irb.200;
interface xe-0/0/22.0;
}
}
lldp {
interface all;
}
lldp-med {
interface all;
}
igmp-snooping {
vlan default;
}
rstp {
interface xe-0/0/0;
interface xe-0/0/1;
interface xe-0/0/2;
interface xe-0/0/3;
interface xe-0/0/4;
interface xe-0/0/5;
interface xe-0/0/6;
interface xe-0/0/7;
interface xe-0/0/8;
interface xe-0/0/9;
interface xe-0/0/10;
interface xe-0/0/11;
interface xe-0/0/12;
interface xe-0/0/13;
interface xe-0/0/14;
interface xe-0/0/15;
interface xe-0/0/16;
interface xe-0/0/17;
interface xe-0/0/18;
interface xe-0/0/19;
interface xe-0/0/20;
interface xe-0/0/21;
interface xe-0/0/22;
interface xe-0/0/23;
interface et-0/0/24;
interface xe-0/0/24:0;
interface xe-0/0/24:1;
interface xe-0/0/24:2;
interface xe-0/0/24:3;
interface et-0/0/25;
interface xe-0/0/25:0;
interface xe-0/0/25:1;
interface xe-0/0/25:2;
interface xe-0/0/25:3;
interface et-0/0/26;
interface xe-0/0/26:0;
interface xe-0/0/26:1;
interface xe-0/0/26:2;
interface xe-0/0/26:3;
interface et-0/0/27;
interface xe-0/0/27:0;
interface xe-0/0/27:1;
interface xe-0/0/27:2;
interface xe-0/0/27:3;
}
}
vlans {
default {
vlan-id 1;
l3-interface irb.0;
}
vlan200 {
vlan-id 200;
l3-interface irb.200;
}
vlan208 {
vlan-id 208;
l3-interface irb.208;
}
vlan216 {
vlan-id 216;
l3-interface irb.216;
}
vlan224 {
vlan-id 224;
l3-interface irb.224;
}
vlan232 {
vlan-id 232;
l3-interface irb.232;
}
vlan240 {
vlan-id 240;
l3-interface irb.240;
}
vlan248 {
vlan-id 248;
l3-interface irb.248;
}
}
EX4300 (virtual chassis):
version 14.1X53-D35.3;
**REMOVED**
}
syslog {
user * {
any emergency;
}
file messages {
any notice;
authorization info;
}
file interactive-commands {
interactive-commands any;
}
}
processes {
dhcp-service {
traceoptions {
file dhcp_logfile size 10m;
level all;
flag all;
}
}
}
}
interfaces {
ge-0/0/0 {
unit 0 {
family ethernet-switching {
interface-mode access;
vlan {
members 240;
}
storm-control default;
}
}
**REMOVED**
ge-0/0/47 {
unit 0 {
family ethernet-switching {
interface-mode access;
vlan {
members 240;
}
storm-control default;
}
}
}
xe-0/2/0 {
unit 0 {
family ethernet-switching {
interface-mode trunk;
vlan {
members [ 7 240 ];
}
}
}
}
**REMOVED**
xe-2/2/0 {
unit 0 {
family ethernet-switching {
interface-mode trunk;
vlan {
members [ 7 240 ];
}
}
}
}
**REMOVED**
ge-3/0/47 {
unit 0 {
family ethernet-switching {
interface-mode access;
vlan {
members 240;
}
storm-control default;
}
}
}
irb {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ex4300-48p;
}
}
}
}
vme {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ex4300-48p;
}
}
}
}
}
forwarding-options {
storm-control-profiles default {
all;
}
}
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/0/22;
interface ge-0/0/23;
interface ge-0/0/24;
interface ge-0/0/25;
interface ge-0/0/26;
interface ge-0/0/27;
interface ge-0/0/28;
interface ge-0/0/29;
interface ge-0/0/30;
interface ge-0/0/31;
interface ge-0/0/32;
interface ge-0/0/33;
interface ge-0/0/34;
interface ge-0/0/35;
interface ge-0/0/36;
interface ge-0/0/37;
interface ge-0/0/38;
interface ge-0/0/39;
interface ge-0/0/40;
interface ge-0/0/41;
interface ge-0/0/42;
interface ge-0/0/43;
interface ge-0/0/44;
interface ge-0/0/45;
interface ge-0/0/46;
interface ge-0/0/47;
interface ge-0/2/0;
interface xe-0/2/0;
interface ge-0/2/1;
interface xe-0/2/1;
interface ge-0/2/2;
interface xe-0/2/2;
interface ge-0/2/3;
interface xe-0/2/3;
interface xe-2/2/0;
}
}
virtual-chassis {
**REMOVED**
}
}
vlans {
default {
vlan-id 1;
l3-interface irb.0;
}
vlan240 {
description pc/data;
vlan-id 240;
}
vlan7 {
description management;
vlan-id 7;
}
}
poe {
interface all;
}
↧
Re: connecting EX4300 VC to EX4600 non-VC
Hi
I am not able to see this type of configuration (combine 2 interconnected ports to make aggregated ethernet) used for switch to switch connectivity.
Use your numbers instead of xxx.
xe-x/x/x {
ether-options {
802.3ad ae2;
}
}
xe-x/x/x {
ether-options {
802.3ad ae2;
ae2 {
description xxxxx;
aggregated-ether-options {
link-speed 10g;
lacp {
active;
periodic fast;
}
}
unit 0 {
family ethernet-switching {
port-mode trunk;
vlan {
members [ xxx ];
↧
Re: connecting EX4300 VC to EX4600 non-VC
Thanks for the reply. I have always used AE interfaces with LACP in the past, but as mentioned with dual uplinks to each physical switch.
Will I still need that configured on the 4300 stack AND the 4600s?
↧
↧
Re: connecting EX4300 VC to EX4600 non-VC
Hello
I have used AE's each and every time while doing switch to switch interconnection.
Please try that one and let me know if working then marked as accepted solution.
Thanks
Amit
↧
Re: Scheduled JUNOS upgrade
Hi,
Here are a few tools available that could perform this.
- Junos Space (http://www.juniper.net/techpubs/en_US/junos-space15.2/platform/topics/concept/junos-space-deviceimagesscripts-overview.html)
- Ansible (http://www.juniper.net/techpubs/en_US/junos-ansible1.0/topics/example/junos-ansible-playbooks-device-os-installing.html)
- PyEz (http://junos-pyez.readthedocs.io/en/latest/jnpr.junos.utils.html#module-jnpr.junos.utils.sw)
Of course, it all depends greatly on what you would feel comfortable doing this with etc.
I recently did an upgrade of 100+ EX-4300's VC's (approx 600 members in total) using Ansible 2.0 and this included pre-checks, upgrade and post-checks, and ran in just under an hour.
Regards,
Andy
↧
Re: connecting EX4300 VC to EX4600 non-VC
I actually tried this intinally. Did it again, and ae2 comes up on the 4300VC LACP shows distributing and collecting.
On the 4600 side, I se the "A" switch to periodic fast active, the "B" switch I did the same but ae2 never shows as up. I tried doing periodic fast passive, but the same results.
So in summary, I setup ae2 on all 2 devices:
ae2 on 4300 VC = up @ 10G
ae2 on 4600A = up @ 10G
ae2 on 4600B = down
I'm still seeing the same behavior, I think it may have something to do with spanning tree priority between each 4600 since I am using et-0/0/24 as a trunk port between the two.
↧
Re: connecting EX4300 VC to EX4600 non-VC
Amit it is not possible to configure LACP between three physically separate switches.
SRXs, your options are either MC-LAG or just regular layer 2 STP. Make sure you configure a layer 2 link between the 4600's trunking all of your VRRPed vlans.
Also, assuming your diagram is correct, your vlan tags are not matching up. xe-0/0/1 on the two 4600's is trunking vlan 232 but the 4300 is trunking vlans 7 and 240 on xe-0/2/0 and xe-2/2/0.
↧
↧
Re: ocx1100: start linux juniper but doesnt start junos
He's already in the shell, he's asking how to enter Juniper CLI. That done with the cli command.
root@test:RE:0% cli
{master:0}
root@test>
↧
Re: MAC addresses per port
He's not asking how to configure max allowed per port, he's asking what the maximum learned can be per port.
Mannan I don't think there is a per-port limit that is less than the global but your SE can probably tell for sure for the models you list. I'm able to generate the maximum number of addresses on a single port on an EX2200.
root@rno03-spi-mgmt> show ethernet-switching table interface ge-0/0/1|count
Count: 16387 lines
↧
Re: [QFX5100] dhcp-relay options
You might want to review the helper statistics and configure the trace options recommended in this troubleshooting kb to confirm that the dhcp request is received by the port and actually forwarded.
https://kb.juniper.net/InfoCenter/index?page=content&id=KB11020
If the forwarding is working, then start down the list of this general kb beginning at step 7
https://kb.juniper.net/InfoCenter/index?page=content&id=KB23335
↧
Re: QFX really weird OPTIC issue
It does seem like the bad optic is damaging something.
With the bad optic in a bad port can you run the hardware list to see if it is seen at all. Substitute your fpc and pic slot numbers this should return the make model of all the optics for that pic currently inserted.
show chassis pic fpc-slot 0 pic-slot 0
↧
↧
Re: connecting EX4300 VC to EX4600 non-VC
Could you confirm the spanning tree status of all the ports involved? Perhaps blocking ports are working against your communication paths.
↧
Re: connecting EX4300 VC to EX4600 non-VC
Hi,
I believe LACP [802.3ad] LAG can only be setup between 2 logical switches.
In this case, there's 3 logical switches EX4300VC, EX4600A and EX4600B.
LACP on EX4600B stays down because EX4300VC sees a different system ID other than the other LAG partner i.e EX4600A. Thus, no synchronisation flag is sent back in the LACP PDU to EX4600B.
MC-LAG allows for LAG over 2 different logical partners.
MC-LAG is supported as fromJunos OS 13.2X51-D25 on EX4600.
Cheers,
Ashvin
↧
How to add or remove multiple VLANs from few interfaces without using full VLAN name?
Hi
I'm confusing with managing VLANs on my EX4550. In Extreme Summit X650 I could simple use AWK to prepare commnads for adding or removing VLANs without using full names:
config vlan v118- add ports tagged 17,28
config vlan v150- add ports tagged 17,28
config vlan v315- add ports tagged 17,28
where v118- have full name v118-R1C1 and tag 118, v150- full name is v150-D3T2 and tag 150, and so on.
How can I manage VLANs on my EX4550 in the same way?
↧
Re: How to add or remove multiple VLANs from few interfaces without using full VLAN name?
Hi,
There are 2 ways possible to assign vlans to an interface in JUNOS:
1. Under edit vlans vlan-name -> set interface x/x/x
2. Under edit interfaces x/x/x unit 0 family ethernet-switching -> set vlan members vlan-name
With method 1, if you have multiple vlans on same group of interfaces you could use copy vlan xxx to vlan yyy. The vlan-id will need to be changed but the interfaces will be copied.
In Junos EX config, the vlan-name is the reference for the vlan.
Cheers,
Ashvin
↧
↧
Re: How to add or remove multiple VLANs from few interfaces without using full VLAN name?
Unfortunately for these ways I need to know full names of all VLANs or do it manualy using TAB key.
Is there any way using tags instead of vlan-names?
Can I change a vlan-name though all system config in one command?
↧
VC not showing neighbor
Hi,
We have a 4300 virtual chassis stack of 3 and is configured preprovisioned. When I do show virtual-chassis status, only unit 1 is showing neighbors for 0 and 2. But unit 0 and 2 are not showing each other as neighbors. We have 4200 stacks and have never seen this. Stack has been rebooted, and cable from Unit 0 to 2 replaced. Any help is appreciated!
root@NOC-ES-01> show virtual-chassis status
Preprovisioned Virtual Chassis
Virtual Chassis ID: 9984.6180.d8a9
Virtual Chassis Mode: Enabled
Mstr Mixed Route Neighbor List
Member ID Status Serial No Model prio Role Mode Mode ID Interface
0 (FPC 0) Prsnt xxxxxxxxx ex4300-24p 129 Master* N VC 1 vcp-255/1/0
1 (FPC 1) Prsnt xxxxxxxxx ex4300-24p 0 Linecard N VC 2 vcp-255/1/0
0 vcp-255/1/1
2 (FPC 2) Prsnt xxxxxxxxx ex4300-24p 129 Backup N VC 1 vcp-255/1/1
> show virtual-chassis device-topology
fpc0:
--------------------------------------------------------------------------
Neighbor List
Member Device Status System ID Member Device Interface
0 0 Prsnt 100e.7ea6.33c0 1 1 vcp-255/1/0
1 1 Prsnt ec3e.f790.27c0 0 0 vcp-255/1/1
2 2 vcp-255/1/0
2 2 Prsnt 100e.7ea6.3f60 1 1 vcp-255/1/1
fpc1:
--------------------------------------------------------------------------
Neighbor List
Member Device Status System ID Member Device Interface
0 0 Prsnt 100e.7ea6.33c0 1 1 vcp-255/1/0
1 1 Prsnt ec3e.f790.27c0 0 0 vcp-255/1/1
2 2 vcp-255/1/0
2 2 Prsnt 100e.7ea6.3f60 1 1 vcp-255/1/1
fpc2:
--------------------------------------------------------------------------
Neighbor List
Member Device Status System ID Member Device Interface
0 0 Prsnt 100e.7ea6.33c0 1 1 vcp-255/1/0
1 1 Prsnt ec3e.f790.27c0 0 0 vcp-255/1/1
2 2 vcp-255/1/0
2 2 Prsnt 100e.7ea6.3f60 1 1 vcp-255/1/1
{master:0}
Model: ex4300-24p
Junos: 14.1X53-D35.3
↧
Re: How to add or remove multiple VLANs from few interfaces without using full VLAN name?
Hi,
AFAIK, we cannot use vlan-ids or tags on EXs. This is possible under family bridge [MX/SRX] with vlan-id-list. Example:
interfaces ae2 {
unit 0 {
family bridge {
interface-mode trunk;
vlan-id-list 100, 200–205;
}
}
}To change vlan-name in whole config, you could use "replace pattern xxxx with yyyy"
With method 1, the vlan-name would be present in only one line of the configuration hierarchy.
Hope this helps.
Cheers,
Ashvin
↧