Junos
Junos

subscriber management - auto-configure "not working"

[ Edited ]
‎05-20-2019 01:42 AM

> show version

Model: mx5-t

Junos: 14.2R7-S9

 

I'll start with showing you the version we're running, and you probably going to say that this version is not supported for the subscriber management feature of JunOS. You might be right, but a lot of issues that I had with this feature were fixed anyway, despite using this version.

And upgrading to a new version cannot be done that easily since it is in production for a lot of customers.

 

I recently came accross a mysterious issue using the auto-configure statement for creating dynamic auto-sensed VLAN interfaces.

We're using this for quite some time (a couple of years now) and had not issue with it before.

Recently more and more interfaces were added to the "problem pool" where JunOS was not able to create these underlying demux0 interfaces anymore. Simply adding the logical unit + concerned vlan-id and associated dymamic-profile fixed it.

 

I had this on one interface only, but more and more interfaces are having this problem as well.

Looking at the auto-configuration.log log doesn't help much. I'm happy to share any of it if it helps along with other subscriber management related log files.

The issue is clear, but not how and/or why this is happening.

 

Any ideas?

17 REPLIES 17
Junos

Re: subscriber management - auto-configure "not working"

‎05-20-2019 01:59 AM

 

Although you already aware that JUNOS 14.2R7 is not quailied build for subscriber use, there are many issues that you can run into using JUNOS 14.2R7. Debugging the problem may lead you to a workaround, but it will be more of troublesome than upgrading to supported & qualified build. 

 

Can tell you tell more about "Recently more and more interfaces were added to the "problem pool"?

could you share what exactly your configuring that triggers the issue? and share your interface config and dynamic-profile used?

 

 

 

/Karan Dhanak
# Please mark my solution as accepted if it helped, Kudos are appreciated as well.

Junos

Re: subscriber management - auto-configure "not working"

‎05-20-2019 02:20 AM

Hey Karand,

 

I agree on the JunOS version, I just find it strange that this issue suddenly arose with no changes to any related configurations of subscriber management (dynamic profiles, accepted VLAN ranges, etc.).

 

The problem pool is a figurative pool with all interfaces where dynamic demux interfaces are not created anymore.

 

There is no known configuration statement that could have triggered this. 

The first interface where this happened, the issue suddenly arose. 

Same with the second interface.

With the third interface, our glass fiber carrier had a failing node and, when it was replaced, two customer locations could not reconnect to our MX's PPPoE server. We talk a bunch of VLANs with their first core device, and that part has not changed. I mean, adding a logical unit with VLAN ID and dynamic profile automatically brings the PPPoE session alive.

 

Interface configuration:

 

flexible-vlan-tagging;
auto-configure {
    stacked-vlan-ranges {
        dynamic-profile DEMUX-QinQ {
            accept pppoe;
            ranges {
                any,any;
            }
        }
    }
    vlan-ranges {
        dynamic-profile DYNINTF-VLAN-DHCP-INET {
            accept any;
            ranges {
                1-2008;
                2010-2011;
                2014-2014;
                2023-2023;
                2033-2033;
                2037-2037;
                2041-2041;
                2049-2049;
                2053-2054;
            }
        }
        dynamic-profile DEMUX-Q {
            accept pppoe;
            ranges {
                2009-2009;
                2012-2013;
                2015-2022;
                2024-2028;
                2029-2032;
                2034-2036;
                2038-2040;
                2042-2048;
                2052-2052;
                2055-4000;
            }
        }
    }
    remove-when-no-subscribers;
}

Dynamic profile configuration (DEMUX-Q + PPPoE-SUBSCRIBER):

 

DEMUX-Q {
    interfaces {
        demux0 {
            unit "$junos-interface-unit" {
                demux-source inet;
                proxy-arp;
                vlan-id "$junos-vlan-id";
                demux-options {
                    underlying-interface "$junos-interface-ifd-name";
                }
                family inet {
                    unnumbered-address lo0.0 preferred-source-address xx.xx.xx.xx;
                }
                family inet6 {
                    unnumbered-address lo0.0 preferred-source-address xx:xx:xx:xx;
                }
                family pppoe {
                    duplicate-protection;
                    dynamic-profile PPPoE-SUBSCRIBER;
                }
            }
        }
    }
}


PPPoE-SUBSCRIBER {
    predefined-variable-defaults {
        inactive: input-filter police-unlimited;
        inactive: output-filter police-unlimited;
    }
    routing-instances {
        "$junos-routing-instance" {
            interface "$junos-interface-name";
            routing-options {
                access {
                    route $junos-framed-route-ip-address-prefix next-hop "$junos-framed-route-nexthop";
                }
                access-internal {
                    route $junos-subscriber-ip-address {
                        qualified-next-hop "$junos-interface-name";
                    }
                }
            }
        }
    }
    interfaces {
        pp0 {
            unit "$junos-interface-unit" {
                ppp-options {
                    pap;
                    authentication [ pap chap ];
                    mru 1492;
                    mtu 1492;
                }
                pppoe-options {
                    underlying-interface "$junos-underlying-interface";
                    server;
                }
                keepalives interval 60;
                family inet {
                    filter {
                        input "$junos-input-filter";
                        output "$junos-output-filter";
                    }
                    unnumbered-address "$junos-loopback-interface";
                }
                family inet6 {
                    address $junos-ipv6-address;
                }
            }
        }
    }
}
Junos

Re: subscriber management - auto-configure "not working"

‎05-20-2019 05:18 AM

New information: a new case came in where I already configured a logical interface with VLAN ID + dynamic profile.

My idea was that a statically configured VLAN interface would take precedence over auto-configure statements.

The interface was not present in the show interfaces xe-1/3/0.499, but it was when we deleted interface xe-1/3/0.499 and added it again.

Junos

Re: subscriber management - auto-configure "not working"

‎05-20-2019 10:35 PM

it sounds like dynamic vlan interface (demux0.xyz) is staled & system believes that dynamic vlan already exists thus system attempts to bring up subscriber ip interface over it and eventually fials becuase the dynamic interface is staled. 

 

And then when you configure a static logical interface with vlan and dynamic-profile (i assume pppoe profile) the subscriber comes up.

 

If thats the case, system should remove dynamic vlan interface when subscriber logs out when you have configured "remove-when-no-subscribers" at the interface. This knob ensures that system doesn't keep or leave dynamically created vlan interface (demux0.xyz).  but for some reason, if this dynamic vlan interface remains active with no subscriber on it, there are chances it can go stale over the period of time.

 

There is known PR in this area PR1322745 (internal viewable only) in which similar issue was seen.

This PR was logged orginally in JUNOS 14.1x50D-xx (JSM build) and closed the JUNOS 14.1x50 build was considered end of life/devolpement and the issue was no longer seen in newer junos build that were qaulified for JSM (Junos Subscriber Mgmt) builds/version.

 

To recover, can you try to clear the vlan interface over which subscriber is coming.

 

> clear auto-configuration interfaces <demux.xyz>

 

if that doesn't help, restart auto-configd processes.

 

> restart auto-configuration

 

 

 

 

 

 

 

 

 

 

/Karan Dhanak
# Please mark my solution as accepted if it helped, Kudos are appreciated as well.

Junos

Re: subscriber management - auto-configure "not working"

[ Edited ]
‎05-21-2019 12:32 AM

Hi Karand,

 

Well, it seems like it's not always an issue of the demux0 dynamic VLAN interface is still there when the subscriber tries to log out.

There has been some cases where this did happen, but then I was able to remove the interface.

This time, nothing is there at all and the auto-configure.log log doesn't get me further.

 

> clear auto-configuration interfaces <demux.xyz>

Not applicable here.

 

> restart auto-configuration

This might work, although the issue is not present on all subscriber management interfaces (yet).

Will this log out all current active subscribers?

 

 

Oh btw, the Problem Report PR1322745 doesn't give me any result on https://prsearch.juniper.net
I am logged in with my J-Net Account.

Junos

Re: subscriber management - auto-configure "not working"

‎05-21-2019 03:05 AM

PR is internal, so its not viewable.

restart auto-configd should not affect existing subscribers.

/Karan Dhanak
# Please mark my solution as accepted if it helped, Kudos are appreciated as well.

Junos

Re: subscriber management - auto-configure "not working"

‎05-21-2019 03:45 AM

Hi karand,

 

Thanks for your answer.

Can anyone confirm that this absolutely does not affect existing subscribers?

"should not" is not good enough nowadays :-)

Highlighted
Junos

Re: subscriber management - auto-configure "not working"

‎05-21-2019 04:24 AM

Hello Beeelzebub,

 

I believe your expectations are a bit too high Smiley Happy In my experience, restart of autoconfd doesn't have any impact on the existing subscribers, however, all depends on the exact issue you've hit (especially if the release is not supported for JSM). At this point it's very obvious that you're hitting a SW bug, and given that you don't want to upgrade the possible options are very limited. The failure seems to be in autoconfd (unless proven otherwise), and its restart would be the first suggested option by JTAC anyway.

 

Best regards,

Sergii

Junos

Re: subscriber management - auto-configure "not working"

‎05-22-2019 12:33 AM

Hi Sergii,

 

My expectations are always high :-)

Just confirmed that restarting the autoconfd process doesn't affect active subscribers nor does it fix the creation of dynamic VLAN interface issue.

Wondering if this is a SW bug after all, why not a HW bug?

 

JTAC would be indeed the next step. However, I'm not near any JTAC contract yet in order to open cases with them.

Junos

Re: subscriber management - auto-configure "not working"

‎05-22-2019 12:41 AM

 

Auto-configd process restart would not affect existing subscribers. Restarting the auto-configd it can either fix your issue, or not fix your issue or can even wrosen the condition given that you're non JSM qualified build.

 

Its certainly not H/w issue but is a S/w issue given the fact you're non junos subscriber qualified build.

Could you share show chassis hardware model to know what type/model of MPC from h/w standpoint.

/Karan Dhanak
# Please mark my solution as accepted if it helped, Kudos are appreciated as well.

Junos

Re: subscriber management - auto-configure "not working"

‎05-22-2019 12:53 AM

Hi Beeelzebub,

 

Well, if it were HW issue, you'd see other, more severe and permanent symptoms. In other words, HW components involved in dynamic vlan creation for working and not working vlans are the same, which rule out any HW problem.

 

As the next step, you may want to restart interface-control, but please do it during MW - again, it shouldn't have any impact on existing subscribers, but this restart will incur more load on the system when compared with autoconfd restart.

 

As you may have noticed, on this forum you have a chance to discuss issues with JTAC engineers without a need to create JTAC case - enjoy Smiley Happy

 

HTH


Best regards,
Sergii
-------------------------------------------------------------------
Please accept the solution if your problem is resolved Smiley Happy
-------------------------------------------------------------------

Junos

Re: subscriber management - auto-configure "not working"

‎05-22-2019 01:30 AM

Hi Karand, Sergii,

 

As requested: output of the show chassis hardware command.

 

beelze@core1> show chassis hardware 
Hardware inventory:
Item             Version  Part number  Serial number     Description
Chassis                                F2732             MX80
Midplane         REV 08   711-031594   ZP7935            MX80
PEM 0            Rev 05   740-028288   XJ11301           AC Power Entry Module
PEM 1            Rev 04   740-028288   VL10876           AC Power Entry Module
Routing Engine            BUILTIN      BUILTIN           Routing Engine
TFEB 0                    BUILTIN      BUILTIN           Forwarding Engine Processor
  QXM 0          REV 05   711-028408   ZL8928            MPC QXM
FPC 0                     BUILTIN      BUILTIN           MPC BUILTIN
  MIC 0                   BUILTIN      BUILTIN           4x 10GE XFP
    PIC 0                 BUILTIN      BUILTIN           4x 10GE XFP
      Xcvr 0     REV 02   740-014279   T09L46849         XFP-10G-LR
      Xcvr 1     REV 02   740-014279   T09L25892         XFP-10G-LR
      Xcvr 2     REV 02   740-014279   T09L46806         XFP-10G-LR
      Xcvr 3     REV 02   740-014279   T10B39517         XFP-10G-LR
FPC 1                     BUILTIN      BUILTIN           MPC BUILTIN
  MIC 0          REV 30   750-028392   ABCY8345          3D 20x 1GE(LAN) SFP
    PIC 0                 BUILTIN      BUILTIN           10x 1GE(LAN) SFP
      Xcvr 1     REV 01   740-011783   SOS131L_1D8       SFP-LX10
      Xcvr 5     REV 01   740-031849   SOSC49Z0704       SFP-LH
      Xcvr 6     REV 01   740-031849   SOSC51Z0560       SFP-LH
      Xcvr 7     REV 01   740-011783   SOS131L_WA074     SFP-LX10
      Xcvr 8     REV 01   740-011783   SOS131L_WA070     SFP-LX10
      Xcvr 9     REV 01   740-011783   SOS131L_7Z7       SFP-LX10
    PIC 1                 BUILTIN      BUILTIN           10x 1GE(LAN) SFP
      Xcvr 0     REV 01   740-013111   SOSR45C_08547     SFP-T
      Xcvr 1     `        NON-JNPR     FNS1138A037       SFP-LX10
      Xcvr 3     REV 01   740-011783   SOS131L_1D7       SFP-LX10
      Xcvr 4     REV 01   740-011783   SOS131L_7Z0       SFP-LX10
      Xcvr 5     LX       740-011783   F785TMR           SFP-LX10
      Xcvr 6     REV 01   740-011783   SOS131L_WN941     SFP-LX10
      Xcvr 7     REV 01   740-011783   SOS131L_WN942     SFP-LX10
  MIC 1          REV 21   750-028380   CAAV8120          3D 2x 10GE XFP
    PIC 2                 BUILTIN      BUILTIN           1x 10GE XFP
      Xcvr 0     REV 02   740-014279   T08D79790         XFP-10G-LR
    PIC 3                 BUILTIN      BUILTIN           1x 10GE XFP
Fan Tray                                                 Fan Tray

 

Subscriber license:

 

 

beelze@core1> show system license 
License usage: 
                                 Licenses     Licenses    Licenses    Expiry
  Feature name                       used    installed      needed 
  subscriber-accounting                 0            1           0    permanent
  subscriber-authentication             0            1           0    permanent
  subscriber-address-assignment         1            1           0    permanent
  subscriber-vlan                       0            1           0    permanent
  subscriber-ip                         0            1           0    permanent
  scale-subscriber                    455         1000           0    permanent
  scale-l2tp                            0         1000           0    permanent
  scale-mobile-ip                       0         1000           0    permanent
  l2tp-inline-lns                       0            1           0    permanent

 

@Sergii, thanks for the tip about restarting interface-control. 

interface-control—(Optional) Restart the interface process, which controls the router's or switch’s physical interface devices and logical interfaces.

I get that, but does it bring down the interface and all its logical sub-interfaces well and bring them quickly up again?

 

And I was not aware about JTAC engineers in this forum but very helpful and skilled engineers who use Juniper equipment as well.

I had some satisfying answers in the past, so now I know why.

 

Junos

Re: subscriber management - auto-configure "not working"

‎05-22-2019 01:45 AM

Hi Beeelzebub,

 

It's good to hear that we were able to help Smiley Happy


@Beeelzebub wrote:

interface-control—(Optional) Restart the interface process, which controls the router's or switch’s physical interface devices and logical interfaces.

I get that, but does it bring down the interface and all its logical sub-interfaces well and bring them quickly up again?

If everything goes well - no, all interfaces stay up, and usually this is the case. However, we don't really know how bad the state of the system is, so in theory there can be issues - that's why it's better to perform this operation during maintenance window.

 

HTH


Best regards,
Sergii
-------------------------------------------------------------------
Please accept the solution if your problem is resolved Smiley Happy
-------------------------------------------------------------------

Junos

Re: subscriber management - auto-configure "not working"

‎05-24-2019 10:57 AM

Hi Sergii,

 

I have a standalone MX80 and did the 'restart interface-control' command.

Anything special looking at the messages.log log?

 

I did a continuous ping to an active subscriber and it did not drop one ping.

Only the fxp0 and em0/em1 interfaces flapped.

 

May 24 19:24:29  PPPOE-CONCENTRATOR mgd[61778]: UI_CMDLINE_READ_LINE: User 'beelze', command 'restart interface-control '
May 24 19:24:29  PPPOE-CONCENTRATOR mgd[61778]: UI_RESTART_EVENT: User 'beelze' restarting daemon 'Interface control process'
May 24 19:24:29  PPPOE-CONCENTRATOR init: interface-control (PID 61809) exited with status=0 Normal Exit
May 24 19:24:29  PPPOE-CONCENTRATOR init: interface-control (PID 61818) started
May 24 19:24:30  PPPOE-CONCENTRATOR /kernel: agg_pfe_get_fwd_options: demux0.123: ifd is NULL or ifl is not aggregate
May 24 19:24:30  PPPOE-CONCENTRATOR /kernel: pp0.1073874427: ENTERED: calculate_ppp_mru with lower_mru  (9166) ppp_local_mtu = 1492  ppp_cfg_mru = 1492 , lower_max_mtu = 9166 , pppoe_rwlen = 24, pppoe_ifl_l2hdr_len = 24
May 24 19:24:30  PPPOE-CONCENTRATOR /kernel: agg_pfe_get_fwd_options: pp0.1073874427: ifd is NULL or ifl is not aggregate
May 24 19:24:30  PPPOE-CONCENTRATOR mgd[61778]: UI_COMMIT_PROGRESS: Commit operation in progress: signaling 'Init daemon', pid 1, signal 1, status 0 with notification errors enabled
May 24 19:24:30  PPPOE-CONCENTRATOR init: can not access /usr/sbin/relayd: No such file or directory
May 24 19:24:30  PPPOE-CONCENTRATOR init: relay-process (PID 0) started
May 24 19:24:30  PPPOE-CONCENTRATOR init: can not access /usr/sbin/gstatd: No such file or directory
May 24 19:24:30  PPPOE-CONCENTRATOR init: gstatd (PID 0) started
May 24 19:24:30  PPPOE-CONCENTRATOR init: can not access /usr/sbin/transportd: No such file or directory
May 24 19:24:30  PPPOE-CONCENTRATOR init: transport-control (PID 0) started
May 24 19:24:30  PPPOE-CONCENTRATOR dcd[61818]: parse_mix_rate_parent_ae : ifd ae0 no configured link-speed
May 24 19:24:31  PPPOE-CONCENTRATOR /kernel: ae0: Unknown TLV type 280
May 24 19:24:31  PPPOE-CONCENTRATOR /kernel: mcae_ifd_pfe_update: ae0: MCAE Color update to PFE
May 24 19:24:31  PPPOE-CONCENTRATOR /kernel: if_pfe_ge_mcae_color_update: ge-1/1/1: MCAE Color update to PFE
May 24 19:24:31  PPPOE-CONCENTRATOR /kernel: if_pfe_ge_mcae_color_update: ge-1/1/0: MCAE Color update to PFE
May 24 19:24:30  PPPOE-CONCENTRATOR cosd[1772]: link protection 0 for intf ae0
May 24 19:24:31  PPPOE-CONCENTRATOR /kernel: if_pfe_iflconfig_tlv_helper ae0.32767: header->tlv_type 371 received
May 24 19:24:31  PPPOE-CONCENTRATOR rpd[1767]: EVENT <MTU> dsc index 5 <Up Broadcast Multicast>
May 24 19:24:31  PPPOE-CONCENTRATOR /kernel: if_pfe_ge_mcae_color_update: ge-1/0/0: MCAE Color update to PFE
May 24 19:24:31  PPPOE-CONCENTRATOR rpd[1767]: EVENT <MTU> esi index 136 <Up Broadcast Multicast>
May 24 19:24:31  PPPOE-CONCENTRATOR /kernel: if_pfe_ge_mcae_color_update: ge-1/0/1: MCAE Color update to PFE
May 24 19:24:31  PPPOE-CONCENTRATOR /kernel: if_pfe_ge_mcae_color_update: ge-1/0/2: MCAE Color update to PFE
May 24 19:24:31  PPPOE-CONCENTRATOR /kernel: if_pfe_ge_mcae_color_update: ge-1/0/3: MCAE Color update to PFE
May 24 19:24:31  PPPOE-CONCENTRATOR /kernel: if_pfe_ge_mcae_color_update: ge-1/0/4: MCAE Color update to PFE
May 24 19:24:31  PPPOE-CONCENTRATOR /kernel: if_pfe_ge_mcae_color_update: ge-1/0/5: MCAE Color update to PFE
May 24 19:24:31  PPPOE-CONCENTRATOR /kernel: if_pfe_ge_mcae_color_update: ge-1/0/6: MCAE Color update to PFE
May 24 19:24:31  PPPOE-CONCENTRATOR /kernel: if_pfe_ge_mcae_color_update: ge-1/0/7: MCAE Color update to PFE
May 24 19:24:31  PPPOE-CONCENTRATOR /kernel: if_pfe_ge_mcae_color_update: ge-1/0/8: MCAE Color update to PFE
May 24 19:24:31  PPPOE-CONCENTRATOR /kernel: if_pfe_ge_mcae_color_update: ge-1/0/9: MCAE Color update to PFE
May 24 19:24:31  PPPOE-CONCENTRATOR /kernel: if_pfe_ge_mcae_color_update: ge-1/1/0: MCAE Color update to PFE
May 24 19:24:31  PPPOE-CONCENTRATOR /kernel: if_pfe_iflconfig_tlv_helper ge-1/1/0.32767: header->tlv_type 371 received
May 24 19:24:31  PPPOE-CONCENTRATOR /kernel: agg_pfe_get_fwd_options: ge-1/1/0.32767: ifd is NULL or ifl is not aggregate
May 24 19:24:31  PPPOE-CONCENTRATOR /kernel: if_pfe_ge_mcae_color_update: ge-1/1/1: MCAE Color update to PFE
May 24 19:24:31  PPPOE-CONCENTRATOR rpd[1767]: EVENT <MTU> gre index 10 <Up Broadcast Multicast>
May 24 19:24:31  PPPOE-CONCENTRATOR /kernel: if_pfe_iflconfig_tlv_helper ge-1/1/1.32767: header->tlv_type 371 received
May 24 19:24:31  PPPOE-CONCENTRATOR /kernel: agg_pfe_get_fwd_options: ge-1/1/1.32767: ifd is NULL or ifl is not aggregate
May 24 19:24:31  PPPOE-CONCENTRATOR /kernel: if_pfe_ge_mcae_color_update: ge-1/1/2: MCAE Color update to PFE
May 24 19:24:31  PPPOE-CONCENTRATOR /kernel: if_pfe_ge_mcae_color_update: ge-1/1/3: MCAE Color update to PFE
May 24 19:24:31  PPPOE-CONCENTRATOR /kernel: if_pfe_ge_mcae_color_update: ge-1/1/4: MCAE Color update to PFE
May 24 19:24:31  PPPOE-CONCENTRATOR /kernel: if_pfe_ge_mcae_color_update: ge-1/1/5: MCAE Color update to PFE
May 24 19:24:31  PPPOE-CONCENTRATOR /kernel: if_pfe_ge_mcae_color_update: ge-1/1/6: MCAE Color update to PFE
May 24 19:24:31  PPPOE-CONCENTRATOR /kernel: if_pfe_ge_mcae_color_update: ge-1/1/7: MCAE Color update to PFE
May 24 19:24:31  PPPOE-CONCENTRATOR /kernel: if_pfe_ge_mcae_color_update: ge-1/1/8: MCAE Color update to PFE
May 24 19:24:31  PPPOE-CONCENTRATOR /kernel: if_pfe_ge_mcae_color_update: ge-1/1/9: MCAE Color update to PFE
May 24 19:24:31  PPPOE-CONCENTRATOR rpd[1767]: EVENT <MTU> ipip index 11 <Up Broadcast Multicast>
May 24 19:24:31  PPPOE-CONCENTRATOR rpd[1767]: EVENT <MTU> mtun index 66 <Up Broadcast Multicast>
May 24 19:24:31  PPPOE-CONCENTRATOR rpd[1767]: EVENT <MTU> tap index 12 <Up Broadcast Multicast>
May 24 19:24:31  PPPOE-CONCENTRATOR /kernel: if_pfe_ge_ifdconfig_tlv: cleared autoconf options on xe-1/2/0
May 24 19:24:31  PPPOE-CONCENTRATOR /kernel: if_pfe_ge_mcae_color_update: xe-1/2/0: MCAE Color update to PFE
May 24 19:24:31  PPPOE-CONCENTRATOR /kernel: if_pfe_iflconfig_tlv_helper xe-1/2/0.0: header->tlv_type 105 received
May 24 19:24:31  PPPOE-CONCENTRATOR /kernel: if_pfe_iflconfig_tlv_helper xe-1/2/0.0: header->tlv_type 371 received
May 24 19:24:31  PPPOE-CONCENTRATOR /kernel: agg_pfe_get_fwd_options: xe-1/2/0.0: ifd is NULL or ifl is not aggregate
May 24 19:24:31  PPPOE-CONCENTRATOR /kernel: if_pfe_ge_mcae_color_update: xe-1/3/0: MCAE Color update to PFE
May 24 19:24:32  PPPOE-CONCENTRATOR mgd[61778]: UI_CMDLINE_READ_LINE: User 'beelze', command 'show subscribers extensive | match login '
May 24 19:24:32  PPPOE-CONCENTRATOR mgd[61778]: UI_CHILD_START: Starting child '/usr/sbin/subinfo'
May 24 19:24:32  PPPOE-CONCENTRATOR mgd[61778]: UI_CHILD_STATUS: Cleanup child '/usr/sbin/subinfo', PID 61820, status 0
May 24 19:24:35  PPPOE-CONCENTRATOR mgd[61778]: UI_CMDLINE_READ_LINE: User 'beelze', command 'show interfaces | match flap '

It does say 'cleared autoconf options on xe-1/2/0' although nothing is configured on that interface.

 

It seems to be a safe option.

But why would it incur more load on the system than the 'restart auto-configuration' command?

 

Beeelze

Junos

Re: subscriber management - auto-configure "not working"

‎05-28-2019 07:14 AM

Hi Beeelzebub,

 

My understanding was that neither fxp0, nor em0/em1 shouldn't flap when dcd is restarted. In any case, dcd is responsible for maintaining information and programming all interface structures in kernel - and the scope is much bigger than autoconfd's. My point is that dcd restart may clear incorrect programming for those problematic vlans that were mentioned earlier, and subscribers will be able to connect again, without any need for any configuration changes. But dcd restart can also lead to issues, so if you're planning to give it a try, please perform dcd restart only during maintenance window.

 

HTH


Best regards,
Sergii
-------------------------------------------------------------------
Please accept the solution if your problem is resolved Smiley Happy
-------------------------------------------------------------------

Junos

Re: subscriber management - auto-configure "not working"

‎05-28-2019 11:54 PM

Thanks Sergii for your confirmation on this one.

Where does dcd actually stand for? I saw it once in my test logs and read somewhere that it is related to interface-control.

I will propose the restart of this process to my management team and will let you guys know if it did anything to this issue.

 

Junos

Re: subscriber management - auto-configure "not working"

‎05-29-2019 12:33 AM

Beeelzebub,

 

dcd stands for  'device control daemon" ( dcd ) is responsible for configuring interfaces.

to restart dcd, use "restart interface-control" knob.

 

 

/Karan Dhanak
# Please mark my solution as accepted if it helped, Kudos are appreciated as well.