After creating the SSR instance, the 128T service is not running.
The following log shows the status of the 128T service ######128T.service status########################## [root@router t128]# systemctl status 128T.service ● 128T.service - 128T service Loaded: loaded (/usr/lib/systemd/system/128T.service; disabled; vendor preset: disabled) Active: inactive (dead) Jun 25 05:22:56 router.ec2.internal systemd[1]:[/usr/lib/systemd/system/128T.service:67] Unknown lvalue 'StateDirectory' in section 'Service' Jun 25 05:22:56 router.internal systemd[1]: [/usr/lib/systemd/system/128T.service:68] Unknown lvalue 'StateDirectoryMode' in section 'Service' Jun 25 05:24:12 router.internal systemd[1]: 128T service is not active.
When trying to start service, will get below error.
[root@router t128]# systemctl start 128T.service Broadcast message from [email protected] (Tue Jun 25 05:30:38 2024): 128T Environment Configuration is invalid. The product will not be able to launch until this is resolved. - /etc/128technology/global.init: file does not exist - /etc/128technology/local.init: file does not exist Job for 128T.service failed because the control process exited with error code. See "systemctl status 128T.service" and "journalctl -xe" for details.
128T service fails to start due to missing global.init and local.init
These files are auto generated once you run the "initialize128t" utility from shell prompt and hence this can happen on SSR instances which are fresh and not initialized properly.
shell # initialize128t
Upon running the command it will start a wizard where you need to provide below information
Choose the options that applies for your scenario, Once the wizard is completed try starting 128T service.
shell # systemctl start 128T
Check the status of service using below command
shell # systemctl status 128T