11-03-2025 11:26 AM
Dear community,
Does anyone have experience of using GNXi on XE 17.12.05? We use the GNXi secure-server for telemetry data, and it appears that our Catalyst 9300 switches are sending data to a third-party collector. The problem is that the GNXi state is shown as "Down" and we would like to know why.
Cat9k-R-AA01#show gnxi state
State Status
--------------------------------
Enabled Down
!
!
!
Cat9k-R-AA01#show telemetry connection all
Telemetry connections
Index Peer Address Port VRF Source Address State State Description
----- -------------------------- ----- --- -------------------------- ---------- --------------------
54266 10.100.144.20 57500 0 10.144.184.250 Active Connection up
!
!
Cat9k-R-AA01#show telemetry internal subscription all stats
Telemetry subscription stats:
Subscription ID Msgs Sent Msgs Drop Bytes Sent Connection Info
---------------- ---------- ---------- ------------ -----------------------------------------
102 8301300 690 1358168855 (10.100.144.20:57500)
101 553398 50 1004403126 (10.100.144.20:57500)
100 4706 0 1244578 (10.100.144.20:57500)
!
!
!
Cat9k-R-AA01#show telemetry receiver all
Telemetry receivers
Name Type Profile State Explanation
--------------------------------------------------------------------------------------------------------------------------------------------
grpc-tls://cmpca@10.100.144.20:5 protocol cmpca Valid
Solved! Go to Solution.
11-04-2025 09:58 AM
@a.mitsova I asked internally and the answer I got is aligned to what @bigevilbeard shared:
gRPC dial-out telemetry (gRPC-based, but not gNMI) doesn't depend on the gNXI server. The pubd process initiates the gRPC dial-out connection. If gNMI/gNOI isn't being used the gnxi configuration isn't needed.
The gNXI server (gnmib) would be needed for gNMI Get/Set/Subscribe, gNOI and grpctunnel based dial-out
I looked for documentation that describes this scenario but I wasn't able, so I think this is the best answer for now.
11-03-2025 11:42 AM
From what I recall on this, telemetry dial out which you are using here does not strictly rely on the gNXI server being up for its operation. Your state is active up, sent and bytes sent are reporting they are reaching the collector.
If you only need the Dial-Out telemetry (which is working), you can likely forget about your "Down" status for the gNXI server.
The only reason I can think of this shows as down could be the trust point isn’t valid or a firewall in the path? Or it’s a bug
11-03-2025 11:49 AM
Hi Stuart,
Thank you!
The firewall is a very good point, and I will double-check this. Otherwise, yes, we can see the telemetry data in our monitoring. I was just curious why the gNXI server is "Down".
11-03-2025 12:42 PM
No problem, I’m struggling to find a document on this. I think I saw this in a Cisco Live session.
11-03-2025 12:48 PM
If you find any document, please share! I could not find anything in the On-demand library (Cisco Live presentations).
11-04-2025 03:19 AM
Tagging the super @Jesus Illescas he might know or be able to direct you for this.
11-04-2025 03:21 AM
Thanks @bigevilbeard
I'm not that familiar with XE, but let me ask around to see what I can find.
11-04-2025 03:33 AM
Thanks @Jesus Illescas I am sure Story or Jeremy did a session which included this.
11-04-2025 09:58 AM
@a.mitsova I asked internally and the answer I got is aligned to what @bigevilbeard shared:
gRPC dial-out telemetry (gRPC-based, but not gNMI) doesn't depend on the gNXI server. The pubd process initiates the gRPC dial-out connection. If gNMI/gNOI isn't being used the gnxi configuration isn't needed.
The gNXI server (gnmib) would be needed for gNMI Get/Set/Subscribe, gNOI and grpctunnel based dial-out
I looked for documentation that describes this scenario but I wasn't able, so I think this is the best answer for now.
11-04-2025 02:47 PM
Thank you very much @Jesus Illescas and @bigevilbeard !!!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide