Did you find a solution, I have been banging my head against the wall on this.
↧
Re: ICCP goes down when enabling aeX mc-ae lag option
↧
Re: VRRP Master
Gotta thank you for pointing out the timers had to match. Solved it for me!
↧
↧
Virtual chassis for Ex9208
Greeting folks
as im moved from Cisco to Juniper I've been doing some resersh for the equivalent from VSS in juniper, but the issue all what i found is th VC in juniper is directly connected as in Cisco called cisco stack which is all next to each other.
I have 2 Ex9200 in diffrent racks and i want to make them VC that they act as one Ex9200.
whats the best secnario that i have and i would approciate any link to some configuration guides
thanks in advance
↧
Re: Virtual chassis for Ex9208
The equivalent of Cisco VSS in Juniper is called MC-LAG. Basically, 2 different switches appearing as one to external devices with a dual, separate control plane. Generally, each switch must be configured on their own, although Juniper has some enhancements to make this type of config easier - I posted something on another thread about this. Both VSS and MC-LAG are limited to 2 switches max for the core nodes.
Cisco "stacking" and Juniper "virtual-chassis" are basically the same concept but in general allow for more than 2 switches in the 'stack' and have a single control plane, potentially with some redundancy built in. For Juniper, this would be master/back-up REs, and things like GRES, NSB, NSR, etc.
Juniper EX9200 is one EX model that does NOT support VC configuration. EX9200 in terms of node level redundancy and failover can be accomplished by using MC-LAG (search for this) or Junos Fusion for Enterprise (JFE) or now IP Fabric using EVPN/VXLAN (or EVPN/MPLS - EX9200 supports both).
I might suggest whomever you purchased these EX9200s from, you sit down and discuss design options and pros and cons of each approach.
Good luck!
↧
LACP Trunk between QFX5100 VC and MX480 MC-LAG Routers
Greetings Everyone!
I am attempting to connect two 10G links from our QFX5100 switches (VC Configuration) into our MX480 edge routers and having 20G LACP bonded connections.
I am able to get the LACP trunk up and working (so both ends say) but I am not able to pass L3 traffic between the VLANs. Can someone point out where I am messing up ?
MX480-01
set interfaces xe-2/1/2 description "qfx5100__xe-0/0/47" set interfaces xe-2/1/2 gigether-options 802.3ad ae1 set interfaces ae1 description "AE-LINK" set interfaces ae1 flexible-vlan-tagging set interfaces ae1 multi-chassis-protection 192.168.10.2 interface ae0 set interfaces ae1 aggregated-ether-options lacp active set interfaces ae1 aggregated-ether-options lacp periodic fast set interfaces ae1 aggregated-ether-options lacp fast-failover set interfaces ae1 aggregated-ether-options lacp system-priority 100 set interfaces ae1 aggregated-ether-options lacp system-id 01:00:00:00:00:01 set interfaces ae1 aggregated-ether-options lacp admin-key 1 set interfaces ae1 aggregated-ether-options mc-ae mc-ae-id 1 set interfaces ae1 aggregated-ether-options mc-ae redundancy-group 1 set interfaces ae1 aggregated-ether-options mc-ae chassis-id 0 set interfaces ae1 aggregated-ether-options mc-ae mode active-active set interfaces ae1 aggregated-ether-options mc-ae status-control active set interfaces ae1 unit 0 family bridge interface-mode trunk set interfaces ae1 unit 0 family bridge vlan-id-list 1151 set bridge-domains vlan-1151 description "AE-LINK" set bridge-domains vlan-1151 vlan-id 1151 set bridge-domains vlan-1151 routing-interface irb.1151 set interfaces irb unit 1151 family inet address 192.168.12.2/29 vrrp-group 0 virtual-address 192.168.12.1 set interfaces irb unit 1151 family inet address 192.168.12.2/29 vrrp-group 0 priority 110 set interfaces irb unit 1151 family inet address 192.168.12.2/29 vrrp-group 0 preempt set interfaces irb unit 1151 family inet address 192.168.12.2/29 vrrp-group 0 accept-data set interfaces irb unit 1151 family inet address 192.168.12.2/29 vrrp-group 0 track interface ae1 priority-cost 100
MX480-02
set interfaces xe-2/1/2 description "qfx5100__xe-1/0/47" set interfaces xe-2/1/2 gigether-options 802.3ad ae1 set interfaces ae1 description "AE-LINK" set interfaces ae1 flexible-vlan-tagging set interfaces ae1 multi-chassis-protection 192.168.10.1 interface ae0 set interfaces ae1 aggregated-ether-options lacp active set interfaces ae1 aggregated-ether-options lacp system-priority 100 set interfaces ae1 aggregated-ether-options lacp system-id 01:00:00:00:00:01 set interfaces ae1 aggregated-ether-options lacp admin-key 1 set interfaces ae1 aggregated-ether-options mc-ae mc-ae-id 1 set interfaces ae1 aggregated-ether-options mc-ae redundancy-group 1 set interfaces ae1 aggregated-ether-options mc-ae chassis-id 1 set interfaces ae1 aggregated-ether-options mc-ae mode active-active set interfaces ae1 aggregated-ether-options mc-ae status-control standby set interfaces ae1 unit 0 family bridge interface-mode trunk set interfaces ae1 unit 0 family bridge vlan-id-list 1151 set bridge-domains vlan-1151 description "AE-LINK" set bridge-domains vlan-1151 vlan-id 1151 set bridge-domains vlan-1151 routing-interface irb.1151 set interfaces irb unit 1151 family inet address 192.168.12.3/29 vrrp-group 0 virtual-address 192.168.12.1 set interfaces irb unit 1151 family inet address 192.168.12.3/29 vrrp-group 0 priority 100 set interfaces irb unit 1151 family inet address 192.168.12.3/29 vrrp-group 0 preempt set interfaces irb unit 1151 family inet address 192.168.12.3/29 vrrp-group 0 accept-data set interfaces irb unit 1151 family inet address 192.168.12.3/29 vrrp-group 0 track interface ae1 priority-cost 100
QFX5100 (VC Cluster)
set interfaces xe-0/0/47 description "mx480-01_xe-2/1/2" set interfaces xe-0/0/47 ether-options 802.3ad ae0 set interfaces xe-1/0/47 description "mx480-02_xe-2/1/2" set interfaces xe-1/0/47 ether-options 802.3ad ae0 set interfaces ae0 description "AE-LINK" set interfaces ae0 flexible-vlan-tagging set interfaces ae0 aggregated-ether-options minimum-links 1 set interfaces ae0 aggregated-ether-options lacp active set interfaces ae0 aggregated-ether-options lacp periodic fast set interfaces ae0 unit 0 family ethernet-switching interface-mode trunk set interfaces ae0 unit 0 family ethernet-switching vlan members 1151 set vlans vlan-1151 description "AE-LINK" set vlans vlan-1151 vlan-id 1151 set vlans vlan-1151 l3-interface irb.1151 set interfaces irb unit 1151 family inet address 192.168.12.4/29
MX480-01 (LACP Status | MC-AE Status)
# run show lacp interfaces ae1
Aggregated interface: ae1
LACP state: Role Exp Def Dist Col Syn Aggr Timeout Activity
xe-2/1/2 Actor No No Yes Yes Yes Yes Fast Active
xe-2/1/2 Partner No No Yes Yes Yes Yes Fast Active
LACP protocol: Receive State Transmit State Mux State
xe-2/1/2 Current Fast periodic Collecting distributing
# run show interfaces mc-ae
Member Link : ae1
Current State Machine's State: mcae active state
Local Status : active
Local State : up
Peer Status : active
Peer State : up
Logical Interface : ae1.0
Topology Type : bridge
Local State : up
Peer State : up
Peer Ip/MCP/State : 192.168.10.2 ae0.0 up
QFX5100 (LACP Status)
# run show lacp interfaces ae0
Aggregated interface: ae0
LACP state: Role Exp Def Dist Col Syn Aggr Timeout Activity
xe-0/0/47 Actor No No Yes Yes Yes Yes Fast Active
xe-0/0/47 Partner No No Yes Yes Yes Yes Fast Active
xe-1/0/47 Actor No No Yes Yes Yes Yes Fast Active
xe-1/0/47 Partner No No Yes Yes Yes Yes Fast Active
LACP protocol: Receive State Transmit State Mux State
xe-0/0/47 Current Fast periodic Collecting distributing
xe-1/0/47 Current Fast periodic Collecting distributing
I've attached a diagram of the connections for a visual idea of what i'm attempting to accomplish.
Any assistance would be greatly appreciated.
↧
↧
Re: Virtual chassis for Ex9208
thanks for your prompet, but what about VCE "Virtual chassis Extension" is it also not supported on the Ex9200?
↧
routing-instances without having a vlan assigned to an active physical interface?
I have created a routing instance, vlan and the irb interface. I have everything configured properly: the interface is added to the routing-instance and the irb interface is added to the vlan.
What I am trying to accomplish is to have this routing-instance only route internally between other routing instances on the same switch. There is no need for routing to happen externally of the switch.
The issue I am running into is that the routing instance will not actually route any traffic unless I assign the vlan to an actually physical interface. When I view the route table of the routing instance without first adding the vlan to a physical interface then the tabe shows that local/o is reject. If I add the vlan to any existing physical interface then the route table shows as "via irb.xxx" and then traffic starts to work.
Is it possible to make this work without assigning the vlan to a physical interface?
↧
Re: routing-instances without having a vlan assigned to an active physical interface?
A vlan interface will go into a down state and its routes removed from the routing table if no interfaces in that vlan are active. I don't know of any way to force the vlan interface up, short of plugging a loopback cable into a physical port assigned to that vlan.
↧
Re: Virtual chassis for Ex9208
The EX9200 does support VC but only with the older RE module (EX9200-RE, not EX9200-RE2)
While configuration and management of a VC is easier you give up fully seperated control planes and lose some level of resiliency. If you've invested in expensive gear such as this I would consider rccpgm's advice and look at other protocols or talk to an SE for other design options.
↧
↧
Re: Virtual chassis for Ex9208
@AAsh if by VCE, you mean Nexus 2K extension of Nexus 5K (and maybe 6K as well? I am no Cisco expert), then Juniper similar solution is Junos Fusion [for Enterprise]. Please note there are 3 different Junos Fusion solutions, all based upon the same underlying technology, but with a slight difference for the 3 different use cases. These are:
JFE - Junos Fusion Enterprise (EX9200 Core or Aggregation Device [AD])
JFDC - Junos Fusion Data Center (QFX10K Core or Aggregation Device [AD])
JFP - Junos Fusion Provider Edge (MX Core or Aggregation Device [AD])
Google search you provide you with additional info.
↧
Re: Virtual chassis for Ex9208
@smiker - actually that is an old link which should be depreciated. I have sent feedback to doc group about this. When EX9200 first came out, VC was supported, but an [internal] decision was made 3/4+ years ago to instead move to MC-LAG only support. So VC is now not officially supported on EX9200, even though it might actually work. Not been part of EX9200 test plans for many years now.
Now EX9200 supports MC-LAG, JFE, and EVPN/VXLAN or MPLS, but not VC.
FYI
↧
Re: routing-instances without having a vlan assigned to an active physical interface?
Hello,
wrote:
What I am trying to accomplish is to have this routing-instance only route internally between other routing instances on the same switch. There is no need for routing to happen externally of the switch.
Well, to "route" You have to have packets/traffic. And how do You actually plan to "inject" traffic into this routing instance? Or do You actually plan to redirect locally-/switch-originated packets (originated from within other routing-instances or GRT on the same switch) into this routing-instance? If that's the case, I'd reckon You just need a stable/always-up interface in this instance and it does not need to be IRB. You can use loopback unit:
set interfaces lo0 unit 5 family inet address 203.0.113.1/24 set routing-instances blah instance-type virtual-router set routing-instances blah interfaces lo0.5
If the traffic is ICMP Echo Request/ping then You can go interface-less/have a "receive" route:
set routing-instances blah routing-options static route 203.0.113.0/24 receive
ICMP Echo Request packets matching this route will be answered, provided there is a route back to the source(s) of ICMP Echo Requests/pings.
HTH
Thx
Alex
↧
Re: LACP Trunk between QFX5100 VC and MX480 MC-LAG Routers
Have you configured the Service -ID on both the MXs ?
Also confirm are we seeing the ARP entries on the MX side
-Kiran
↧
↧
Re: LACP Trunk between QFX5100 VC and MX480 MC-LAG Routers
I'm not that used to bridge-domains on MX, but I think you are missing adding the interface to the bridge-domain on both MX's:
set bridge-domains vlan-1151 interface ae1.0
set bridge-domains vlan-1151 domain-type bridge
↧
Re: Virtual chassis for Ex9208
thanks for your assist
dose juniper have a tool or virtual enviroument thank i can use or even rent that support ex9200 and MC-LAG to practice in?
↧
EX9200 virtual environment
hello Junos
dose juniper have a tool or virtual environment i can use or even rent that support ex9200 and MC-LAG to practice in?
↧
Re: EX9200 virtual environment
The virtual QFX platform would be your best bet for this. You can download the vQFX from the support site.
https://www.juniper.net/support/downloads/?p=vqfxeval
If your account is not authorizied for it already, open an admin support case with the url requesting access for demo download.
↧
↧
Re: EX9200 virtual environment
thanks Steve for your feedback, i did what you suggest but somehow the xe intterface wont appear
root@vqfx-re> show chassis fpc pic-status
{master:0}
root@vqfx-re> show chassis fpc
Temp CPU Utilization (%) CPU Utilization (%) Memory Utilization (%)
Slot State (C) Total Interrupt 1min 5min 15min DRAM (MB) Heap Buffer
0 Empty
1 Empty
2 Empty
3 Empty
4 Empty
5 Empty
6 Empty
7 Empty
8 Empty
9 Empty
{master:0}
its been like this since an hour or so
↧
Re: EX9200 virtual environment
@aash - I might suggest that VMX would be a better option for this, as MX and EX9200 are very similar products. Juniper does not have VEX SW, but VMX might be easier to use as this is a released product, with documentation and such, while VQFX is still non-productized. You can get VMC 60-day trial at:
https://www.juniper.net/us/en/dm/free-vmx-trial/
Good luck.
↧
Re: IPv6 static routes and virtual routers?
show routing-instances R1
instance-type virtual-router;
routing-options {
rib R1.inet6.0 {
static {
route 0::0/0 next-hop 2001:0001:0002:0003::5;
}
}
}
↧