I am trying to digest about below config..........Some concerns occurs......
Why there is only one Pyhsical interface that attached to the AE30 below. What reason could be? We know that AE interface should be consisted of multiple Physical interfaces for some good reasons -redundancy or increasing bandwith etc. Secondly what purpose of many unit(s) on AE30? If Pysical interface (xe-2/0/2) is down, doesn't mean all Unit(s) down? Where is the redundancy? Do you know where I come from?
show configuration interfaces ae30 | display set
set interfaces ae30 description Bandwidth_Saler_WTGR-40G-Main_Connection
set interfaces ae30 flexible-vlan-tagging
set interfaces ae30 mtu 9192
set interfaces ae30 encapsulation flexible-ethernet-services
set interfaces ae30 aggregated-ether-options minimum-links 1
set interfaces ae30 aggregated-ether-options lacp active
set interfaces ae30 aggregated-ether-options lacp periodic fast
set interfaces ae30 unit 3000 description vNNI_00
set interfaces ae30 unit 3000 encapsulation vlan-bridge
set interfaces ae30 unit 3000 vlan-id 3000
set interfaces ae30 unit 3000 family ethernet-switching vlan members Vxxxxx01_VLAN3000
set interfaces ae30 unit 3001 description vNNI_01
set interfaces ae30 unit 3001 encapsulation vlan-bridge
set interfaces ae30 unit 3001 vlan-id 3001
set interfaces ae30 unit 3001 family ethernet-switching vlan members Vxxxxx02_VLAN3001
set interfaces ae30 unit 3002 description vNNI_02
set interfaces ae30 unit 3002 encapsulation vlan-bridge
set interfaces ae30 unit 3002 vlan-id 3002
set interfaces ae30 unit 3002 family ethernet-switching vlan members Vxxxxx03_VLAN3002
set interfaces ae30 unit 3003 description vNNI_03
set interfaces ae30 unit 3003 encapsulation vlan-bridge
set interfaces ae30 unit 3003 vlan-id 3003
set interfaces ae30 unit 3003 family ethernet-switching vlan members Vxxxxx04_VLAN3003
set interfaces ae30 unit 3004 description vNNI_04
set interfaces ae30 unit 3004 encapsulation vlan-bridge
set interfaces ae30 unit 3004 vlan-id 3004
set interfaces ae30 unit 3004 family ethernet-switching vlan members VVxxxxx05_VLAN3004
set interfaces ae30 unit 3005 description vNNI_05
set interfaces ae30 unit 3005 encapsulation vlan-bridge
set interfaces ae30 unit 3005 vlan-id 3005
set interfaces ae30 unit 3005 family ethernet-switching vlan members Vxxxxx06_VLAN3005
set interfaces ae30 unit 3006 description vNNI_06
set interfaces ae30 unit 3006 encapsulation vlan-bridge
set interfaces ae30 unit 3006 vlan-id 3006
set interfaces ae30 unit 3006 family ethernet-switching vlan members Vxxxxx07_-VLAN3006
set interfaces ae30 unit 3007 description vNNI_07
set interfaces ae30 unit 3007 encapsulation vlan-bridge
set interfaces ae30 unit 3007 vlan-id 3007
set interfaces ae30 unit 3007 family ethernet-switching vlan members Vxxxxx08_VLAN3007
set interfaces ae30 unit 3008 description vNNI_08
set interfaces ae30 unit 3008 encapsulation vlan-bridge
set interfaces ae30 unit 3008 vlan-id 3008
set interfaces ae30 unit 3008 family ethernet-switching vlan members VVxxxxx09_VLAN3008
set interfaces ae30 unit 3009 description vNNI_09
set interfaces ae30 unit 3009 encapsulation vlan-bridge
set interfaces ae30 unit 3009 vlan-id 3009
set interfaces ae30 unit 3009 family ethernet-switching vlan members VVxxxxx10_VLAN3009
> show lacp interfaces ae30
Aggregated interface: ae30
LACP state: Role Exp Def Dist Col Syn Aggr Timeout Activity
xe-2/0/2 Actor No No Yes Yes Yes Yes Fast Active
xe-2/0/2 Partner No No Yes Yes Yes Yes Fast Active
LACP protocol: Receive State Transmit State Mux State
xe-2/0/2 Current Fast periodic Collecting distributing
Ideally, AE would be configured with multiple child interfaces in order to add to its effective functioning. Having said that, it is still okay to have a single interface in LAG. Personally, I would configure something like that for configuration testing/compatibility testing purposes.
In the configuration, I see the several units on AE30 are configured for different VLANS ( you can see a unique VLAN-id number for each unit).
In this scenario, having our physical interface down will bring our AE bundle down. At least one LAG Child interface should be Active (Up/Up) to bring an Aggregate interface UP, by default. Also, the minimum links configured for AE30 are 1 and since there is only one link configured in AE30, the aggregated interface goes down.
Taking a look at the config, there does not appear to be any redundancy to me. Probably one can include multiple links. This would ensure that the AE is still up even if one physical interface goes down. ( because minimum links configured is 1 )
I further checked AE30 related config at the same Junos device consists of 2 identical MX(s) in Virtual Chassis. There is an AE40 and its configuration is exactly the same as what we are seeing on AE30. Only difference is AE40's Physical interface is different than AE30's. So in this case, there are only two Physical interfaces on the mx Chassis and each Physical interface is member of different AE interfaces(in this case AE30, AE40). This is more reliable, isn't it?
And also I like to ask how to check whether or not these (AE30, AE40) are doing balancing if there is? And what is encapsulation vlan-bridge meant?
ae30 and ae40 are two totally diffrent interfaces, they will only perform load balancing of the traffic for which the destination is rechable via both interfaces and you have load balancing enabled.
vlan-bridge—Use Ethernet VLAN bridge encapsulation on Ethernet interfaces that have IEEE 802.1Q tagging, flexible-ethernet-services, and bridging enabled and that must accept packets carrying TPID 0x8100 or a user-defined TPID.
Having two aggregated interfaces in itself will not make it a reliable configuration as compared to our previous discussion. You will have to check your configuration to ensure load balancing has been enabled or not.
For load balancing on aggregated interfaces, the following document is very helpful. You might want to refer to this -
Flexible Ethernet services is a type of encapsulation that enables a physical interface to support different types of Ethernet encapsulations at the logical interface level. Flexible Ethernet services encapsulation can be configured to support the service provided and the enterprise style configuration. When you encapsulate an interface by using flexible Ethernet services, you can configure a logical interface unit other than 0 withfamily ethernet-switching. You can also configure other logical interfaces on that same interface with different types of Ethernet encapsulations. This enables logical interfaces that are bound to a VLAN ID to coexist with logical interfaces configured withfamily ethernet-switching. For example, if you configure PVLAN on the same physical interface on which you are configuring Q-in-Q tunneling, you can use flexible ethernet services to support the enterprise style of configuration for PVLAN, using family ethernet-switching, along with vlan-bridge.