Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation  Back up to About Overview 
ContentIndex
  
[+] Expand All
[-] Collapse All

No index entries found.

Known Behavior

This section contains the known behavior, system maximums, and limitations in hardware and software in Junos OS Release 15.1F3 for the MX Series and T Series.

General Routing

  • The following request commands are not available for the Routing Engine RE-S-X6-64G on the MX240, MX480, MX960, MX2010, and MX2020:
    • request system halt
    • request system partition
    • request system power off
    • request system power on

    The scope of functionality of the following commands is limited to Junos OS guest level:

    • request system reboot
    • request system snapshot
    • request system software add
    • request system zeroize

    You can use the following equivalent request vmhost commands to achieve the functionality:

    • request vmhost cleanup
    • request vmhost file-copy
    • request vmhost halt
    • request vmhost hard-disk-test
    • request vmhost power-off
    • request vmhost power-on
    • request vmhost reboot
    • request vmhost snapshot
    • request vmhost software abort
    • request vmhost software add
    • request vmhost software in-service-upgrade
    • request vmhost software rollback
    • request vmhost zeroize

    The output of the following show commands are modified for the Routing Engine RE-S-X6-64G:

    • show chassis environment routing-engine
    • show chassis hardware
    • show chassis hardware extensive
    • show chassis routing-engine
    • show system software

    The following new show commands are introduced for the Routing Engine RE-S-X6-64G:

    • show vmhost bridge
    • show vmhost crash
    • show vmhost hardware
    • show vmhost information
    • show vmhost logs
    • show vmhost netstat
    • show vmhost processes
    • show vmhost resource-usage
    • show vmhost snapshot
    • show vmhost status
    • show vmhost uptime
    • show vmhost version

    The following new configuration statements are introduced for the Routing Engine RE-S-X6-64G:

    • edit system processes app-engine-virtual-machine-management-service
    • edit vmhost
  • During deletion and restoration of scaled configurations on MX240, MX480, MX960, MX2010, and MX2020, error messages related to next hops are displayed.
  • The configuration of the smartd process, which monitors the status of the disk on the host OS of MX240, MX480, MX960, MX2010, and MX2020, is not deleted completely even after you delete the configuration. When you configure the smart check feature, smartd continues to use parameters that were configured previously. Therefore, while enabling smart check, remember to configure the threshold values for smartd instead of retaining the default values that were previously configured.
  • FIFO handles of SSD-monitoring smartd are not cleared on the host OS after multiple commits or checks. Smartd stops working when the FIFO limit reaches a maximum. Therefore, we recommend that you do not change smartd configurations too often and perform SSD smart checks after long intervals of time. When the FIFO limit reaches a maximum, reboot the host OS.
  • In a dual Routing Engine system, while Junos OS has just started booting in the master Routing Engine, the backup Routing Engine might be powered-off if it is removed and reinserted.

    As a workaround, plug in the backup Routing Engine after master Routing Engine is running stable and all the FPCs are in operational state. If the other Routing Engine gets powered-off accidentally, issue the commands request chassis cb slot number power off and request chassis cb slot number power on to turn the power on the Routing Engine. The slot number signifies the Routing Engine that has to be powered-on.

  • During graceful Routing Engine switchover (GRES) on MX240, MX480, MX960, MX2010, and MX2020, the 802.1x daemon crashes if the number of logical interfaces configured is equal to 64,000 or more. After the crash, the daemon restarts and resumes normal operations.

Related Documentation

Modified: 2016-08-18