Description

This document provides steps for recovery when there is network-service mismatch between configuration and kernel settings. Even after routing engine reboot configuration is not getting applied in kernel.

Symptoms

Verified network service mode configuration using cli and compared it with kernel settings:

 

LabRouter> show chassis network-services

Network Services Mode: Enhanced-IP



# sysctl net.netsvc

net.netsvc: 0 >>>>>>> should be 2 for enhanced-ip

 

Performed RE reboot, but still kernel setting was not in sync for "enhanced-ip" configuration.

 

Solution

While trying to perform a "commit synchronize force" and received below error message about a duplicate IP configuration.

 

error: remote lock-configuration failed on re1

note: consider using 'commit synchronize force' to

terminate remote edit sessions and force the commit

failed to lock re1

[edit]

LabRouter# commit synchronize force

re0:

configuration check succeeds

re1:

[edit]

'chassis'

warning: Chassis configuration for network services has been changed. A system reboot is mandatory. Please reboot *ALL* routing engines NOW. Continuing without a reboot might result in unexpected system behavior.

[edit interfaces ae17 unit 1161 family inet]

'address 10.10.10.1/29'

identical local address found on rt_inst [default], intfs [ae17.1161 and ae0.1101], family [inet].

error: configuration check-out failed

re0:

error: remote commit-configuration failed on re1

 

To resolve the issue, correct the configuration and give reboot to routing engine.

Modification History

2024-12-03 : Article Created