>show configuration interfaces ge-0/0/2 | display set
set interfaces ge-0/0/2 vlan-tagging set interfaces ge-0/0/2 unit 71 vlan-id 71 set interfaces ge-0/0/2 unit 71 family inet address XXXX/30
set interfaces ge-0/0/2 unit 74 vlan-id 74 set interfaces ge-0/0/2 unit 74 family inet filter input FWFilter-VirR-netaccess set interfaces ge-0/0/2 unit 74 family inet filter output FWfilter-lim-download set interfaces ge-0/0/2 unit 74 family inet address YYYY/28
set interfaces ge-0/0/2 unit 86 vlan-id 86 set interfaces ge-0/0/2 unit 86 family inet filter input FWFilter-lim-upload set interfaces ge-0/0/2 unit 86 family inet address MMMM/28
set interfaces ge-0/0/2 unit 87 vlan-id 87 set interfaces ge-0/0/2 unit 87 family inet address KKKK/29
Regarding the MTU size, as Avinash explained, it is because of the vlan-tagging which adds 4 bytes to the L2 frame.
"L2 Channel errors arise due to the following reasons:
An untagged interface on the SRX receiving VLAN tagged packets
An interface on the SRX, which is tagged with the VLAN id (for example, 'x'), receives packets with some other VLAN id's or tags. This usually happens when the SRX interface is configured as an access port; but the interface of the switch connected to it, if any, is configured as a Trunk.
STP runs on the interface of the device connected to the interface of the SRX
Specifically, this counter increases when the Junos software cannot find a valid logical interface (that is, something like ge-0/0/1.0) for an incoming frame. Conversely, the packet is dropped.
In such scenarios, it is recommended to obtain Wireshark packet captures on the device, which is connected to SRX. This will facilitate deep inspection of the packets being sent to SRX. Any such packet will be isolated and can be removed from the flow."
This issue is due to Junos software not being able to find an entry for the layer 2 circuit identifier, which is receiving a frame with a given VLAN tag, when the VLAN is not configured on the corresponding interface. An external connected device has trunked VLANS; of which the interface on the SRX is unaware.
Thanks, Pradeep Please Mark My Solution Accepted if it Helped, Kudos are Appreciated too!!!