No snmp response

[mario.romeropons]

Hi,

We have tms 13.2.1 with several codec enables : C series, ex, mxp, Polycom hdx.

The problem is that from few week appears the error "No snmp response" in all codecs. The conectivity to codec is correct, i can make ping and response correctly. The error disappears to few minutes or also disappears if i run "force refresh" on codec but the error appears again soon.

Guess it may be related to the firewall ports but security department tell me that this is all right.

Any suggestion to solve the problem ?

Best Regards!

[Ravi Yadav · Accepted solution]

Hi Mario,

If that was working fine earlier and now it stopped or started giving you error then there could be othr issues however in terms of snmp support on Tc software is very limited, it does not support corporate MIBs. On the other hand mxp gives full support .

any corporate MIBs are not supported  on the C-series that why we do not get information from SNMP regarding packet loss, calls etc.

supported OID's (described in RFC1213):

1.3.6.1.2.1.1.1
1.3.6.1.2.1.1.2
1.3.6.1.2.1.1.3
1.3.6.1.2.1.1.4
1.3.6.1.2.1.1.5
1.3.6.1.2.1.1.6
1.3.6.1.2.1.1.7

(sysDescr, sysObjectID, sysUpTime, sysContact, sysName, sysLocation, sysServices

No support for traps.

I am not sure of the polycom.

Thanks
Ravi kr.

Sent from Cisco Technical Support Android App

[Magnus Ohm]

Hey

Do you know if you have a proxy in your network?

It is most likely related to a proxy issue or some other network issue. The reason why you get connectivity when you click force refresh is that the connection refresh is made by a different user. After a few minutes the scanner service which is refreshing the system automatically will trigger and is most likely used by the "Local System" user. This user might have a proxy setting of "Auto Detect" or using a specific proxy defined by group policy (I don't know your setup).

It could be other issues as well. But the best way of identifying this is to start a wireshark trace on your TMS server then do a force refresh to gain connectivity. Let the trace run for a few minutes until the unit goes "No  SNMP response" or "No HTTP(S) response" and then look for a 407 Proxy authentication code. If you see this, you have a proxy issue which is causing this issue.

/Magnus

[mahkrish]

Hi Mario, I concur with Magnus. You can also try running the enforce now for bulk systems from TMS web -->Administrative Tools --> Configuration --> Network Settings --> TMS services --> Enforce now.

Also check Enforce Management Settings on Systems: is seto yes in Network Settings --> TMS services

Best regards,

Mahesh Adithiyha