Symptom/Cause | Solution |
|---|---|
SR MPLS entries are not populated | 1.Check if basic SR configuration is done and neighborship is up. 2.Routes are learnt properly. It can be verified by the command show ip route. 3. ISIS/OSPF database is properly populated with Self and Received LSPs/LSAs in levels they are configured. It can be verified by checking show isis/ospf database 4. If database is not populated correctly re-verify configuration |
PHP Calculation for SR entries | In case PHP is not calculated properly, it's recommended to do clear ISIS or IP OSPF process. PHP calculation is not supported for interfaces with no neighbor. For loopback interface, IP address should be same as router ID. |
SRGB allocation | Getting SRGB used by another process error: Following is the priority thumb rule for SRGB allocation for protocol: • SRGB configured in router process mode. (ISIS router mode or OSPF router mode) • SRGB configured in global mode. • Default SRGB (16000-23999). SRGB is allocated in first come first serve way. Once a particular block of SRGB is allocated to particular IGP or IGP process, same cannot be assigned/allocated to other IGP or other router process. They need to use corresponding ISIS/OSPF SRGB command to allocate non-overlapping blocks for themselves. |
Mapping Server entries are not advertised | Check advertised-local command is configured and receive-disabled is not configured |
SR-LSP stitching | SR and LDP entries are not getting stitched: Make sure mpls lsp-sticthing is configured. |