Menu

couldn't open SNMP::Info session to $switch, perhaps wrong device FQDN or wrong community

2016-08-17
2016-08-17
  • Christian Rohmann

    Just like https://sourceforge.net/p/switchmap/discussion/378009/thread/a319a3e5/#c03d reports this error on HP devices I get the error "couldn't open SNMP::Info session to $switchname, perhaps wrong device FQDN or wrong community" with old and proven cisco switches as well:

    2016/08/17 09:29:05         PopulateEtherChannels::FillEtherChannels: adding child to parent 100000, child = Po3
    2016/08/17 09:29:05         PopulateEtherChannels::FillEtherChannels: returning
    2016/08/17 09:29:05         PopulateEtherChannels::CleanupEtherChannels: called
    2016/08/17 09:29:05         PopulateEtherChannels::CleanupEtherChannels: ParentIfIndex = 100000
    2016/08/17 09:29:05         PopulateEtherChannels::CleanupEtherChannels: NumberChildren = 18
    2016/08/17 09:29:05         PopulateEtherChannels::CleanupEtherChannels: returning
    2016/08/17 09:29:05       PopulateEtherChannels::PopulateEtherChannels: returning
    2016/08/17 09:29:05     Switch::PopulateSwitch: Ok, there's no mapping of port names to VLANs, so I'll try SNMP::Info
    couldn't open SNMP::Info session to $switchname, perhaps wrong device FQDN or wrong community
    

    This happens regardless if I run switchmap on just this one switch or all switches.
    There is no other error reported, not in the log or to STDERR, not even a line of code where this issue happens :-(

     
  • Christian Rohmann

    I might add that the devices causing trouble are "Cisco SF302-08P" and they receive a last SNMP getBulkRequest to OID 1.3.6.1.2.1.31.1.2.1.3. This request is answered by the switch, but Switchmap has already stopped working at that point.

     

Log in to post a comment.