This article describes how a system administrator can check if a system has been rebooted after enabling Enhanced Subscriber Management.
On a fresh install of the Junos Subscriber Management build, the system must be rebooted according to Juniper's documentation on Configuring Junos OS Enhanced Subscriber Management.
Operating a system without a reboot may result in unexpected system behavior. How can a system administrator verify if the chassis rebooted or not at a later state?
Configured Enhanced Subscriber Management without system Reboot:
From Cli:
user@host> show system subscriber-management statistics
subscriber-management not enabled <-- System reports that Subscriber Management is "not enabled"
command not supported
From RE Shell:
% sysctl -a | grep enhance
net.enhanced_rpf_debug: 0
net.pfe.debug_ae_count_lag_enhanced: -1
net.pfe.debug_force_lag_enhanced: 0
net.disable_lag_enhanced: 0
net.enhanced_bbe_support: 2 <-- “2” indicates the system is not running Enhanced Subscriber Management
...
After System Reboot:
From Cli:
user@host> show system subscriber-management statistics
Session Manager started @ Thu Jun 1 09:59:32 2017
Session Manager cleared @ Thu Jun 1 09:59:32 2017
--------------------------------------------------------------
Packet Statistics
--------------------------------------------------------------
I/O Statistics: <-- I/O statistics displayed means that Subscriber Management has been "enabled"
--------------------------------------------------------------
Rx Statistics
packets : 0
Tx Statistics
packets : 0
Layer 3 Statistics
Rx Statistics
packets : 0
Tx Statistics
packets : 0
From RE Shell:
% sysctl -a | grep enhance
net.enhanced_rpf_debug: 0
net.pfe.debug_ae_count_lag_enhanced: -1
net.pfe.debug_force_lag_enhanced: 0
net.disable_lag_enhanced: 0
net.enhanced_bbe_support: 1 <-- “1” Indicates the system is enabled with Enhanced Subscriber Management
...