Flow Administration option --> under "Monitored Items Management" is not available

Products

Network Observability Network Flow Analysis

Issue/Introduction

The Flow Administration option is not visible under the Monitored Items Management menu in DX NetOps Portal version 25․4․4, even when logged in as an administrator with full rights․‌Symptoms include a missing menu entry and failures in the System Status page for NetOps Flow registration․

ERROR MESSAGE:

"Failed to register Flow Service with PC System Status"

SYMPTOMS:

Navigation path Administration > Monitored Items Management does not show "Flow Administration".
PCService.log shows: "Failed to send rest GET http://[Portal_IP]:80/flow-data-mgmt/public/status".
NetOps Flow data management pod logs show "Returned error status code 400" during registration attempts.

CONTEXT: Occurs after installation or upgrade of NetOps Flow where the service access address is incorrectly configured to the Portal address instead of the Kubernetes nodes.

IMPACT: Administrators cannot manage flow definition mappings or view netops flow status within the portal.

Environment

Platform: Kubernetes / Helm

Product Version: 25.4.4

Component: NetOps Flow / Performance Management

Cause

The flow-data-mgmt.serviceAccessHostForPc parameter was incorrectly set to the NetOps Portal IP during installation.
This prevented the Portal from retrieving status data required to populate the administration menu.

Resolution

CHECK LOGS FOR REGISTRATION ERRORS:

Review the PCService.log for communication failures between the Portal and Flow.
- Log Path: /opt/CA/PerformanceCenter/PC/logs/PCService.log.
- Search for: Failed to send rest GET .../flow-data-mgmt/public/status.
VERIFY FLOW POD CONFIGURATION AND LOGS:

Check the flow-data-mgmt pod configuration and debug logs for registration failures.
- Config File: flow-data-mgmt-[pod_id]_config.yaml.
- Debug Log: flow-data-mgmt-[pod_id]_debug.log.
- Verify SERVICE_ACCESS_HOST_FOR_PC value matches the Kubernetes node IP, not the Portal IP.
VERIFY INGRESS ACCESSIBILITY:

Command:
```
kubectl -n default get ingress flow-data-mgmt. 
```
Check if the address listed is accessible from the Portal server using curl:
```
curl -o /dev/null -s -w "%{http_code}\n" http://[Node_IP]:80/flow-data-mgmt/public/status 
```
EXPECTED: A return code of 200. If 000 or 404, the portal cannot reach the flow management service.
UPDATE DEPLOYMENT CONFIGURATION:

Set the serviceAccessHostForPc parameter to the IP address of a Kubernetes control plane or worker node.

Command:
```
helm upgrade netops-flow-analytics [chart_name].tgz --set flow-data-mgmt.serviceAccessHostForPc=[K8S_NODE_IP] 
```
Example: helm upgrade netops-flow-analytics netops-flow-analytics-25.4.4.tgz --set flow-data-mgmt.serviceAccessHostForPc=10.119.2.167

EXPECTED: The deployment updates and the pod restarts with the new configuration.

Additional Information

Collect basic configuration files and logs:

1. kubectl get svc flow-aggregator -n flow -o yaml > flow-aggregator_svc_config.yaml

2. Create that script and run to collect rest of the files, please:

# List Pods
NAMESPACE="default"
PODS=$(kubectl get pods -n $NAMESPACE -o jsonpath='{.items[*].metadata.name}')

# Loop and Collect Information Per Pod
for POD in $PODS; do
    # 1. Collect Pod Configuration
    kubectl get pod $POD -n $NAMESPACE -o yaml > ${POD}_config.yaml

    # 2. Collect Current Pod Logs
    kubectl logs $POD -n $NAMESPACE > ${POD}_debug.log

    # 3. Collect Previous Pod Logs (if the pod recently restarted)
    kubectl logs --previous $POD -n $NAMESPACE > ${POD}_prev_debug.log 2>/dev/null
done