Junos OS

 View Only
last person joined: 2 days ago 

Ask questions and share experiences about Junos OS.

  • 1.  Chassis hardware ( tunnel-service vs inline service ) - subscriber managment

    Posted 04-16-2018 09:05

    hi

     

    i have MX480 configured to serve as LNS to provide DSL service . i user hardware as you see below the FPC0 hane 3 PIC

    so i want to use PIC3 to connect to BRAS ( LAC ) we have about 30 LAC connected to our LNS with 2X10G links .

     

    Spoiler
    Hardware inventory:
    Item             Version  Part number  Serial number     Description
    Chassis                                JN126ADABAFB      MX480
    Midplane         REV 46   750-047862   ACRK4568          Enhanced MX480 Midplane
    FPM Board        REV 04   760-059208   CAJP6899          Front Panel Display
    PEM 0            Rev 01   740-063046   QCS1746U0BK       PS 1.4-2.52kW; 90-264V AC in
    PEM 1            Rev 01   740-063046   QCS1744U1FA       PS 1.4-2.52kW; 90-264V AC in
    PEM 2            Rev 01   740-063046   QCS1746U023       PS 1.4-2.52kW; 90-264V AC in
    PEM 3            Rev 01   740-063046   QCS1746U0CV       PS 1.4-2.52kW; 90-264V AC in
    Routing Engine 0 REV 16   750-054758   CAJX7941          RE-S-2X00x6
    CB 0             REV 09   750-062572   CAJZ4066          Enhanced MX SCB 2
    FPC 0            REV 11   750-063184   CAJX6658          MPC2E NG PQ & Flex Q
      CPU            REV 13   711-045719   CAJX1272          RMPC PMB
      MIC 0          REV 18   750-049846   CAJW9955          3D 20x 1GE(LAN)-E,SFP
        PIC 0                 BUILTIN      BUILTIN           10x 1GE(LAN) -E  SFP
          Xcvr 0     REV 01   740-031850   NYF1QKM           SFP-LX10
          Xcvr 2     REV 01   740-031850   NYF0WGJ           SFP-LX10
        PIC 1                 BUILTIN      BUILTIN           10x 1GE(LAN) -E  SFP
          Xcvr 0     REV 01   740-031850   NS31L2S           SFP-LX10
          Xcvr 1     REV 01   740-031850   NS23QGQ           SFP-LX10
          Xcvr 2     REV 01   740-031850   NYF0X8L           SFP-LX10
          Xcvr 3     59C 19   NON-JNPR     MY222VN012        SFP-LX
          Xcvr 4     REV 01   740-031850   NS31LCB           SFP-LX10
          Xcvr 5              NON-JNPR     FNS112623PC       SFP-SX
          Xcvr 6     REV 01   740-031851   PRM03UK           SFP-SX
          Xcvr 7              NON-JNPR     FNS1128C007       SFP-SX
      MIC 1          REV 33   750-028387   CAHX5975          3D 4x 10GE  XFP
        PIC 2                 BUILTIN      BUILTIN           2x 10GE  XFP
        PIC 3                 BUILTIN      BUILTIN           2x 10GE  XFP
          Xcvr 0     REV 01   740-031833   AYF1ND3           XFP-10G-LR
          Xcvr 1     REV 01   740-031833   AYF1BLL           XFP-10G-LR
    Fan Tray                                                 Enhanced Left Fan Tray

    I will use PIC2 ( 2x 10G ) as 2 internet links with 20G Bandwidth . the PIC 1 ( 8 X1G ) AS link aggeregation with other router . so

     

    i need to configure sutibale value of tunnel-services  and inline-services .

    i try to connected the 15000 user through our 2X10G on pic 3 but we have a sloness and long time to connect all users!!!!

    what the differance between tunnel-services and inline-services ???

    i modify to this configuretiom is that right ????

    show chassis haradware

    Spoiler
    set chassis aggregated-devices ethernet device-count 8
    set chassis fpc 0 pic 0 max-queues-per-interface 8
    set chassis fpc 0 pic 3 tunnel-services bandwidth 20g
    set chassis fpc 0 pic 3 inline-services bandwidth 20g
    set chassis fpc 0 flexible-queuing-mode
    set chassis network-services enhanced-ip

     
    How i can determined the sutable Bandwidth for inline-services and tunnel-services  ?



  • 2.  RE: Chassis hardware ( tunnel-service vs inline service ) - subscriber managment

    Posted 04-16-2018 19:26

    what the differance between tunnel-services and inline-services ???

     

    Basically tunnel services are the one which does encapsulation/decapsulation ie: GRE, IP-IP,  PIM encap/decap.

     

    Below are the Inline services:

     

    Sampling information and statistics
    Network Address Translation (NAT)
    Port mirroring
     

     

     

     

     



  • 3.  RE: Chassis hardware ( tunnel-service vs inline service ) - subscriber managment

    Posted 04-17-2018 02:02

    good . mean tunnel-service inlude L2tp service 

     

    the question that our MPC is MPC2E-3D-NG and the capacity of it 80G see below 

    https://www.juniper.net/documentation/en_US/release-independent/junos/topics/reference/general/mpc2e-3d-ng.html

     

    there ar 3 PICs can i installed on it . 10X1g module or 2X10G module . so the total throughput for physical interfaces is 60G 

     now i can create up to 4 inline service si-0/[pic-num]/0 . 

    assume that the acctual bandwith i used 

    PIC1 ( 1X1g interfaces ) = 8G as link aggragation with another router .

    PIC2 (2X10g interfaces ) = 20G as internet 

    PIC3 (2X10g interfaces ) = 20g used to connect to LAC to serve L2tp tunnel . 

     

    the total is 48g

    the maximam bandwidth that i can dedicate to si is 30g .

     

    the question is if i create si-0/2/0 and give it 30g as bandwidth , the point that i can't understand it  si-0/2/0 and 2X10G physically interface with handle by PIC2 and the total troughtput is 30g+20g = 50g . can PIC2 handle it without problem ????

    if yes , that mean the total throughput share between PICs . 

     



  • 4.  RE: Chassis hardware ( tunnel-service vs inline service ) - subscriber managment
    Best Answer

    Posted 04-17-2018 22:16

     

     

     

    this is the answer that i get from JTAC

     

    Please find below some  guidance in configuration and explantion:

    • The overall PFE bandwidth is shared between the following.
      • WAN traffic
      • Inline tunnel traffic
      • Inline services traffic
    • The maximum WAN traffic is based on the number of WAN ports connected to a PFE.
    • The maximum inline tunnel and inline services traffic is based on the bandwidth of the inline tunnel and inline services configured.
    • Just configuring the inline tunnel or inline services doesn’t statically reserve any PFE bandwidth. The overall PFE bandwidth is shared between the following.

    -WAN traffic

    -Inline tunnel traffic

    -Inline services traffic

    • The maximum WAN traffic is based on the number of WAN ports connected to a PFE. ( the MPC2E-NG module has only one PFE)
    • With a mix of WAN, inline tunnel and inline services traffic, the PFE bandwidth is shared between them.

    The proportion of the bandwidth sharing depends on the traffic rate and the maximum bandwidth of the traffic types and the maximum PFE bandwidth.

    MPC2E.png