Troubleshooting SRC Problems on JUNOS Routing Platforms
To troubleshoot SRC problems on the JUNOS routing platform, review the log files for the SAE and the log files generated by the SRC software process on the router.
- If the log files indicate that the SRC software process is not responding, see Troubleshooting Problems with the SRC Software Process.
- If the log files indicate a problem with a specific interface, see Troubleshooting Problems with Interfaces.
- If the log files indicate a problem with a specific service or its associated firewall rules, see Troubleshooting Problems with Services.
Troubleshooting Problems with the SRC Software Process
If the log files indicate that the SRC software process is not responding:
- Look at the status of the process on the JUNOS routing platform.
root@ui1>show system services service-deployment
Connected to 172.17.20.151 port 3333 since 2004-02-06 14:50:31 PSTKeepalive settings: Interval 15 secondsKeepalives sent: 100, Last sent: 6 seconds agoNotifications sent: 0Last update from peer: 00:00:06 ago- If you see the message "error: the service-deployment subsystem is not running," reenable the SRC software process (see Disabling Interactions Between the SAE and JUNOS Routing Platforms).
- If the process is already enabled, review the configurations of the router and the SAE in the directory, and fix any problems.
- Restart the SRC software process on the router.
root@ui1>restart service-deployment
The SAE synchronizes with the SRC software process and deletes unnecessary data from the router.
Troubleshooting Problems with Interfaces
If the log files indicate a problem with a specific interface or its associated firewall rules:
![]()
For more information on these fields, see SRC-PE Monitoring and Troubleshooting Guide, Chapter 16, Monitoring SAE Data with the C-Web Interface.
The Policies pane displays the interfaces available on the router.
- If you find any errors, fix the configuration in the directory, and proceed to Step 5. Otherwise, proceed to Step 2.
![]()
The Interfaces pane displays the interfaces available on the router.
- If you find any errors, fix the configuration in the directory, and proceed to Step 5. Otherwise, proceed to Step 2.
- Display the corresponding interfaces on the JUNOS routing platform.
root@olive1#show groups sdx interfaces
<fe-0/0/0> {unit <0> {family inet {filter {input SDX_PRIVATE_ID0000000000001092282;output SDX_PRIVATE_ID0000000000001223352;}}}}If you find any errors, fix the configuration in the directory, and proceed to Step 5. Otherwise, proceed to Step 4.
- Disable the SRC software process.
root@ui1#set system processes service-deployment disable
root@ui1#commit
- Delete the interfaces from the router.
delete groups sdx interfaces <interfaceName> <interfaceIdentifier>root@ui1#commitFor example, to delete the interface with identifier fe-0/0/0 unit 0, enter:
root@ui1#delete groups sdx interfaces <fe-0/0/0> unit <0>
root@ui1#commit
- Reenable the SRC software process.
root@ui1#delete system processes service-deployment disable
root@ui1#commit
The SAE reconfigures the interface that you deleted.
If the action you took did not fix the problem, return to the last step you performed, and proceed with this troubleshooting procedure. If you have performed all the tasks in the troubleshooting procedure and the problem persists, delete all SRC data on the JUNOS routing platform (see Deleting All SRC Data on JUNOS Routing Platforms).
Troubleshooting Problems with Services
If the log files indicate a problem with a specific service or its associated firewall rules:
![]()
For more information on these fields, see SRC-PE Monitoring and Troubleshooting Guide, Chapter 16, Monitoring SAE Data with the C-Web Interface.
The Policies pane displays the interfaces available on the router.
- If you find any errors, fix the configuration in the directory, and proceed to Step 5. Otherwise, proceed to Step 2.
![]()
For more information on these fields, see SRC-PE Monitoring and Troubleshooting Guide, Chapter 16, Monitoring SAE Data with the C-Web Interface.
The Services pane displays the interfaces available on the router.
- Locate an active service session for this service, and observe the ProvisioningSet field of that session.
- Locate an identifier that is associated with the service that is causing the problem.
For example, in the above display, the identifier
SDX_PRIVATE_ID0000000000002075317
is associated with a Network Address Translation (NAT) rule.
- Review the corresponding configuration on the JUNOS routing platform.
root@olive1#show groups sdx services nat rule SDX_PRIVATE_ID0000000 000002075317
match-direction input;term SDX_PRIVATE_TERM {from {source-address {0.0.0.0/0;}destination-address {0.0.0.0/0;}}then {translated {source-pool SDX_PRIVATE_ID0000000000002009780;translation-type source dynamic;}}}If you find any errors, fix the configuration in the directory and proceed to Step 5. Otherwise, proceed to Step 4.
- Disable the SRC software process.
root@ui1#set system processes service-deployment disable
root@ui1#commit
- Delete the service on the JUNOS routing platform.
delete groups sdx services <serviceName> <filterID>
root@ui1#commit
For example, to delete a firewall filter of the service called firewall with filterID SDX_PRIVATE_ID0000000000001223352, enter:
delete groups sdx services firewall filter SDX_PRIVATE_ID0000000000001223352
- Reenable the SRC software process.
root@ui1#delete system processes service-deployment disable
root@ui1#commit
The SAE reconfigures the service that you deleted on the JUNOS routing platform.
If the action you took did not fix the problem, return to the last step you performed, and proceed with this troubleshooting procedure. If you have performed all the tasks in the troubleshooting procedure and the problem persists, delete all SRC data on the JUNOS routing platform (see Deleting All SRC Data on JUNOS Routing Platforms).
Deleting All SRC Data on JUNOS Routing Platforms
If deleting parts of the SRC data on a JUNOS routing platform fails to solve problems, delete all the SRC data and restart the SRC software process. To do so:
- Delete all SRC interfaces and services.
delete groups sdx
root@ui1#commit
- If you are running SDX software releases 5.0 through 6.1, you should also delete interface sessions. (After release 6.2, session data is no longer stored on the router, it is stored on the SAE host using the session store feature.)
delete groups sdx-sessions
root@ui1#commit
- Restart the SRC software process on the router.
root@ui1>restart service-deployment
The SAE reconfigures all the interfaces and services that you deleted from the router.