-
Notifications
You must be signed in to change notification settings - Fork 164
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OSS_SNMP exception polling switch #815
Comments
Hi @Kergorn
I'm guessing this is unlikely to be related to a specific version / upgrade right now. We've been running the code that makes up v6.3 at INEX for months on Arista's with no issue. We'll need to dig into what the exception is. The logs you've provided come from the command line run I think (or cron). Looks like the error comes from this line. Could you edit that file so it looks like: } catch( Exception $e ) {
if( $sPolled ){
$this->error("ERROR: OSS_SNMP exception polling switch {$s->name} by SNMP");
throw $e; // <<< new line, only change
} else { And send the output? |
Thanks for your advice! Could not perform walk for OID .1.3.6.1.2.1.31.1.1.1.18 But if I do that: Then everything is fine and I see a correct output from the switch. |
I found the problem, it has to do with the lenght of interface's description (ifAlias). I'll see a error if the description is too long. |
Hi, can you send the output from storage/logs/laravel.log when you've made the change above and hit the error? The trace will identify the specific line. |
|
Hi Barry, |
Sorry @Kergorn - could you let me know the length of the alias string? |
Hmm. |
That's pretty descriptive 😉 DB can hold 255 so I'll need to have a closer look at the code. That's 234 bytes, right? No unicode etc? |
That's right, 234 bytes without unicode. |
Hi Barry, |
Hi @Kergorn I don't think this has anything to do with IXP Manager or OSS_SNMP. The issue will probably be further down the chain with php-snmp or libsnmp or the snmp implementation on the switch. Essentially, it appears ifAlias is not meant to be more than 64 characters per rfc2863 (see pg 43):
I suggest you reduce the content and that should solve the problem. |
[closed this issue as it is not an ixpm bug but feel free to follow up here] |
ISSUE TYPE
Bug Report
OS
VERSION
ENVIRONMENT
CONFIGURATION
SUMMARY
Hi, Team.
I have discovered a problem with snmp polling some of my switches (only Arista and only 4 switches from many others).
SNMP works itself, I have checked it via snmpwalk/snmpget.
The situation looks like this:
After this I have seen that OSS_SNMP has tried to start process (information from log is below). Also, I have seen only one added new interface without information from switch in web-interface of IXP and in the MySQL.
Worth adding that these 4 switches were already added earlier (in version 5.7.0) and statistics were successfully collected from them. Unfortunately, I have only discovered the problem now. I can't say for sure whether it appeared: after the transition to 6.2.0 or later. I also tried to update to 6.3.0 but that didn't help.
What should I do next for debug?
Thanks!
STEPS TO REPRODUCE
EXPECTED RESULTS
ACTUAL RESULTS
IMPORTANCE
RELEVANT LOGS
Polling ar7508-XXX with SNMP request to ar7508-XXX
ERROR: OSS_SNMP exception polling switch ar7508-XXX by SNMP
[2022-11-02 12:48:51] production.INFO: [ar7508-XXX] Platform: Found Model: DCS-7508
[2022-11-02 12:48:51] production.INFO: [ar7508-XXX] Platform: Found Os:
[2022-11-02 12:48:51] production.INFO: [ar7508-XXX] Platform: Updating OsDate from to Unknown
[2022-11-02 12:48:51] production.INFO: [ar7508-XXX] Platform: Found OsVersion: 4.24.5M
[2022-11-02 12:48:51] production.INFO: [ar7508-XXX] Platform: Found SerialNumber: (not implemented)
[2022-11-02 12:48:53] production.INFO: - ar7508-XXX - found pre-existing port for ifIndex 3001
[2022-11-02 12:48:53] production.INFO: [ar7508-XXX]:Ethernet3/1 [Index: 3001] Updating Name from [] to [Ethernet3/1]
[2022-11-02 12:48:54] production.INFO: [ar7508-XXX]:Ethernet3/1 [Index: 3001] Updating IfName from [] to [Ethernet3/1]
The text was updated successfully, but these errors were encountered: