Junos OS

Hello

working MX240 Enhanced MX SCB MPC 3D 16x 10GE

PIC 3                   BUILTIN      BUILTIN           4x 10GE(LAN) SFP+

it has virtual logical-systems

there is a tunnel, there bgp

 run show interfaces lt-1/3/0
Physical interface: lt-1/3/0, Enabled, Physical link is Up
  Interface index: 148, SNMP ifIndex: 1507
  Type: Logical-tunnel, Link-level type: Logical-tunnel, MTU: Unlimited, Speed: 100000mbps
  Device flags   : Present Running
 

so, we have grown a little traffic, respectively, he grew up in the tunnel.

BUT! Do not pump more than 16g , although he and Speed: 100000mbps

increases ping even between peering tunnel types and the speed sags of course for everyone who goes through the tunnel

forced speed was not set

run show configuration chassis fpc 1
pic 3 {
    tunnel-services;
}
 

No filters on the interface

just

unit 100 {
    encapsulation ethernet;
    peer-unit 200;
    family inet {
        address 10.10.10.1/30;
    }
unit 200 {
    encapsulation ethernet;
    peer-unit 100;
    family inet {
        address 10.10.10.2/30;
    }

what could be the problem? help me please

Hi,

Could you set the bandwithd and check?

[edit]
labroot@test# set chassis fpc 1 pic 3 tunnel-services bandwidth 20g

[edit]
labroot@test# show | compare
[edit chassis fpc 1]
+    pic 3 {
+        tunnel-services {
+            bandwidth 20g;
+        }
+    }

Hi,

in this configuration does not work

set chassis fpc 1 pic 3 tunnel-services bandwidth 20g

show log messages 

 Err: tunnel bandwidth 20000000000 not supported(1/3)

set chassis fpc 1 pic 3 tunnel-services bandwidth 40g

show log messages 

 Err: tunnel bandwidth 40000000000 not supported(1/3)

work

 delete chassis fpc 1 pic 3 tunnel-services bandwidth

Feb 9 08:22:46 RE0-MX240 chassisd[3359]: CHASSISD_IFDEV_CREATE_NOTICE: fpc_create_devs_from_queue: created interface device for pd-1/3/0
Feb 9 08:22:46 RE0-MX240 chassisd[3359]: CHASSISD_IFDEV_CREATE_NOTICE: fpc_create_devs_from_queue: created interface device for pe-1/3/0
Feb 9 08:22:46 RE0-MX240 chassisd[3359]: CHASSISD_IFDEV_CREATE_NOTICE: fpc_create_devs_from_queue: created interface device for gr-1/3/0
Feb 9 08:22:46 RE0-MX240 chassisd[3359]: CHASSISD_IFDEV_CREATE_NOTICE: fpc_create_devs_from_queue: created interface device for ip-1/3/0
Feb 9 08:22:46 RE0-MX240 chassisd[3359]: CHASSISD_IFDEV_CREATE_NOTICE: fpc_create_devs_from_queue: created interface device for vt-1/3/0
Feb 9 08:22:46 RE0-MX240 chassisd[3359]: CHASSISD_IFDEV_CREATE_NOTICE: fpc_create_devs_from_queue: created interface device for mt-1/3/0
Feb 9 08:22:46 RE0-MX240 chassisd[3359]: CHASSISD_IFDEV_CREATE_NOTICE: fpc_create_devs_from_queue: created interface device for lt-1/3/0
Feb 9 08:22:46 RE0-MX240 chassisd[3359]: CHASSISD_IFDEV_CREATE_NOTICE: fpc_create_devs_from_queue: created interface device for ut-1/3/0
Feb 9 08:22:46 RE0-MX240 chassisd[3359]: CHASSISD_IFDEV_CREATE_NOTICE: fpc_create_devs_from_queue: created interface device for ud-1/3/0
Feb 9 08:22:47 RE0-MX240 mgd[60511]: UI_COMMIT_COMPLETED: commit complete

Could you share "show chassis hardware" & "show configuration chassis fpc 1"

admin@RE0-MX240> show chassis hardware
Hardware inventory:
Item Version Part number Serial number Description
Chassis JN12219C3AFC MX240
Midplane REV 07 760-021404 ACAX0280 MX240 Backplane
FPM Board REV 04 760-021392 ABBS1818 Front Panel Display
PEM 0 Rev 10 740-029970 QCS1307U00A PS 1.4-2.52kW; 90-264V AC in
PEM 3 Rev 09 740-029970 QCS1213U128 PS 1.4-2.52kW; 90-264V AC in
Routing Engine 0 REV 07 740-013063 9009009280 RE-S-2000
Routing Engine 1 REV 07 740-013063 9009010324 RE-S-2000
CB 0 REV 18 750-031391 ABCE9994 Enhanced MX SCB
CB 1 REV 18 750-031391 ABCF0101 Enhanced MX SCB
FPC 1 REV 36 750-028467 ABCG5269 MPC 3D 16x 10GE
CPU REV 12 711-029089 ABCG4941 AMPC PMB
PIC 0 BUILTIN BUILTIN 4x 10GE(LAN) SFP+
Xcvr 0 NON-JNPR AGN04P8 SFP+-10G-SR
Xcvr 1 NON-JNPR AGN04MH SFP+-10G-SR
Xcvr 2 NON-JNPR EA111124019 SFP+-10G-CU3M
Xcvr 3 NON-JNPR EXP96S01 SFP+-10G-SR
PIC 1 BUILTIN BUILTIN 4x 10GE(LAN) SFP+
Xcvr 0 + 5M NON-JNPR LS17071168-CH1 SFP+-10G-CU5M
Xcvr 1 + 5M NON-JNPR LS17071168-CH2 SFP+-10G-CU5M
Xcvr 2 + 5M NON-JNPR LS17071168-CH3 SFP+-10G-CU5M
Xcvr 3 + 5M NON-JNPR LS17071168-CH4 SFP+-10G-CU5M
PIC 2 BUILTIN BUILTIN 4x 10GE(LAN) SFP+
PIC 3 BUILTIN BUILTIN 4x 10GE(LAN) SFP+
Fan Tray 0 REV 01 710-030216 CAAP6112 Enhanced Fan Tray

admin@RE0-MX240> show configuration chassis fpc 1
pic 3 {
tunnel-services;
}

{master}

I would like to review your config, could you post config in the file.txt and attach here please?

I believe you're over subscribing bandwith per PFE as your graph.

PFE0 serves = x/0/x & x/1/x

PFE1 serves = x/2/x & x/3/x

Please refer this document:

https://www.juniper.net/documentation/en_US/junos/topics/concept/chassis-mpc-16-port-10-gigabit-ethernet-mpc-overview.html

-> Supports one full-duplex 10-Gigabit Ethernet tunnel interface for each Packet Forwarding Engine

https://www.juniper.net/documentation/en_US/junos/topics/task/configuration/chassis-tunnel-interfaces-mx-series-16-port-10-ge-3d-mpc-configuring.html

Can see the same on my test node:

Feb  9 17:50:48.839  jtac-MX-re0 chassisd[18630]: Err: tunnel bandwidth 20000000000 not supported(4/3)
Feb  9 17:50:48.840  jtac-MX-re0 chassisd[18630]: Err: tunnel bandwidth 20000000000 not supported(4/3)
Feb  9 18:27:39.273  jtac-MX-re0 chassisd[18630]: Err: tunnel bandwidth 100000000000 not supported(1/2)

So just to add more info, you're limited to 10g per PFE.

1/3/x & 1/2/x  LT = 10g

1/0/x & 1/1/x  LT = 10g

In your case, if you want to continue on FPC1, use pic0 or pic1 for LT bandwithd.