|
1 | 1 | .. |
| 2 | + SPDX-FileCopyrightText: 2026 Intel Corporation |
2 | 3 | SPDX-FileCopyrightText: © 2020 Open Networking Foundation <support@opennetworking.org> |
3 | 4 | SPDX-License-Identifier: Apache-2.0 |
4 | 5 |
|
5 | | -Connectivity Troubleshooting FlowChart |
6 | | -====================================== |
| 6 | +Connectivity Troubleshooting |
| 7 | +============================ |
7 | 8 |
|
8 | | -4G Metrics |
9 | | ----------- |
10 | | -- eNB Status |
11 | | -- Subscriber information: IP address, IMSI |
| 9 | +This section provides guidance for troubleshooting connectivity issues in SD-Core deployments. |
12 | 10 |
|
13 | | -5G metrics |
14 | | ----------- |
15 | | -- eNB Status |
16 | | -- Subscriber information: IP address, IMSI |
| 11 | +Key Metrics to Monitor |
| 12 | +---------------------- |
| 13 | + |
| 14 | +4G Networks |
| 15 | +^^^^^^^^^^^ |
| 16 | + |
| 17 | +When troubleshooting 4G connectivity issues, monitor the following: |
| 18 | + |
| 19 | +- **eNB Status**: Check if the eNodeB is properly connected and registered |
| 20 | +- **Subscriber Information**: Verify IP address allocation and IMSI registration |
| 21 | +- **Bearer Status**: Ensure default and dedicated bearers are established correctly |
| 22 | +- **S1-AP Connection**: Verify the control plane connection between eNB and MME |
| 23 | +- **S1-U Connection**: Check the user plane connection between eNB and SGW/PGW |
| 24 | + |
| 25 | +5G Networks |
| 26 | +^^^^^^^^^^^ |
| 27 | + |
| 28 | +When troubleshooting 5G connectivity issues, monitor the following: |
| 29 | + |
| 30 | +- **gNB Status**: Check if the gNodeB is properly connected and registered |
| 31 | +- **Subscriber Information**: Verify IP address allocation and IMSI/SUPI registration |
| 32 | +- **PDU Session Status**: Ensure PDU sessions are established correctly |
| 33 | +- **NG-AP Connection**: Verify the control plane connection between gNB and AMF |
| 34 | +- **N3 Connection**: Check the user plane connection between gNB and UPF |
| 35 | + |
| 36 | +Common Troubleshooting Steps |
| 37 | +---------------------------- |
| 38 | + |
| 39 | +1. **Verify Pod Status**: Ensure all SD-Core pods are running without errors |
| 40 | +2. **Check Logs**: Review logs from relevant network functions (AMF, SMF, UPF, etc.) |
| 41 | +3. **Validate Configuration**: Confirm subscriber, device group, and network slice configurations |
| 42 | +4. **Network Connectivity**: Test connectivity between components |
| 43 | +5. **Resource Availability**: Check CPU, memory, and network resources |
0 commit comments