How to switch over an AE selected port from the primary interface to the secondary interface then revert it back. This article just introduces one useful method how to switch-over one member interface of AE to another, which can be used for lab replication or issue isolation during troubleshooting. As per configuration, the primary interface ge-1/0/8 is selected for … [Read more...]
L2TPD_SERVER_START_FAILED
The L2TPD_SERVER_START_FAILED message is reported when the Layer 2 Tunneling Protocol (L2TP) server did not start. L2TP facilitates the tunneling of PPP packets across an intervening network in a way that is as transparent as possible to both end-users and applications. The startup of the L2TP server failed to start. These errors are caused when L2TP cannot bind to the … [Read more...]
‘/kernel: IPv6 ESP input: no key association found for spi xxxxxx’
This article provides information about the /kernel: IPv6 ESP input: no key association found for spi xxxxxx syslog message and on how to avoid this message: % grep -i IPv6 messages Dec 28 10:35:35.907 Jam-re0 /kernel: IPv6 ESP input: no key association found for spi 3715243453 Dec 28 10:40:28.980 Jam-re0 /kernel: IPv6 ESP input: no key association found for spi … [Read more...]
Under WLAN hierarchy, static-mac-filter allows only 32 mac-addressES as part of allow/deny list
This article explains a limitation of Junos OS, wherein users can add only 32 mac-address in an allow/deny list of static-mac-filter. This is working as designed. When user adds more than 32 mac-addresses in the allow/deny list of static-mac-filter, and then commits the configuration, the following error appears: [edit wlan access-point test access-point-options … [Read more...]
LIBSERVICED_SOCKET_BIND
An attempt to bind a server socket for receiving client requests failed. The LIBSERVICED_SOCKET_BIND message is logged each time there is a failed attempt to bind a server socket for receiving client requests. When an attempt to bind a server socket for receiving client requests fails, the system will log a syslog message beginning with "LIBSERVICED_SOCKET_BIND". The … [Read more...]
Error message “ddr_sdram_periodic” is seen in core output after an FPC/DPC reboots
This article addresses the case where a Flexible PIC Concentrator (FPC) and/or Dense Port Concentrator (DPC) reboot occurs, and a core dump containing the backtrace item ddr_sdram_periodic is generated. If SDRAM errors appear in the NVRAM output, then this is most likely a hardware issue. An RMA is recommended. An FPC/DPC rebooted and generated a core dump. The backtrace of … [Read more...]
Adaptive Scans count not incrementing after configuring adaptive knob for an AE interface
Adaptive Scans is a counter which periodically increments. Under certain conditions, we may find this counter remain at zero or does not incremented and this KB mentions those conditions. With ALB, it may be desirable not to increment the Adaptive Scans count under certain circumstances. Minimum configuration under AE Interface for enabling adaptive … [Read more...]
LIBSERVICED_CLIENT_CONNECTION
An attempt to establish a client connection failed. The LIBSERVICED_CLIENT_CONNECTION message is logged each time that an attempt to establish a client connection fails. When an attempt to establish a client connection fails, the system will log a syslog message that will look similar to the following: LIBSERVICED_CLIENT_CONNECTION: Client connection error: unexpected … [Read more...]
SERVICED_EVENT_FAILED
The Services PICs process (serviced) could not continue processing a task because a call to a function in the event library failed. The problem related to this syslog message is described in the following sections: The attempt to execute a call function the services daemon (servicesd) in the Services PIC failed. The failure happened when attempting to call a function from … [Read more...]
SPD_EVLIB_CREATE_FAILURE
The adaptive services process (spd), which provides the user interface for management and configuration of Adaptive Services and Multi Service Physical Interface Cards and also Multi Service Dense Port Concentrators (ASPICs, MSPICs and MSDPCs), could not create a context used for handling all asynchronous events (such as timers and message availability). This only applies to M, … [Read more...]