Or, Jarrod, currently we pass blank as the snmp version if switches.snmpversion is not defined. Should we pass in 1 instead when creating the snmp session?
Ling From: Ling Gao/Poughkeepsie/IBM To: xCAT Users Mailing list <[email protected]> Date: 08/13/2015 10:09 AM Subject: Re: [xcat-user] v2.10: tabdump says xCat defaults to SNMPv1, but actually use SNMPv3 Hi Chris, Thanks for pointing it out. xCAT uses perl SNMP module which has default snmp version 3. The Net::SNMP sets default snmp version to 1. So the doc on switches table for snmpversion is wrong. We will remove the default phrase and the user is expected to in explicitly set it up. Thanks, Ling From: Christopher Samuel <[email protected]> To: xCAT Users Mailing list <[email protected]> Date: 08/12/2015 11:53 PM Subject: [xcat-user] v2.10: tabdump says xCat defaults to SNMPv1, but actually use SNMPv3 Hi folks, This is xCAT 2.10 on RHEL 6.7. Just trying to set up some FCP's here and have had a devil of a time trying to get them to be discovered, was always seeing: [root@snowy-m xcat]# configfpc --verbose -i bond0 --ip 172.30.101.131 Default IP address is 172.30.101.131 Default route address is 172.30.101.132/16 Running ip addr add dev bond0 172.30.101.132/16 Found 172.30.101.131 address Creating default FPC node deffpc with IP 172.30.101.131 for later use with rspconfig Found IP 172.30.101.131 and MAC 6c:ae:8b:09:4b:66 Mapped MAC 6c:ae:8b:09:4b:66 to node Error: No FPC found that is associated with MAC address 6c:ae:8b:09:4b:66. Check to see if the switch and switch table contain the information needed to locate this FPC MAC Removing default IP 172.30.101.131 from the arp table Running ip addr del dev bond0 172.30.101.132/16 Removing default FPC node definition deffpc Running internal xCAT command: noderm ... To cut a long story short, investigating with wireshark revealed that whilst "tabdump -d switches" says: snmpversion: The version to use to communicate with switch. SNMPv1 is assumed by default. This is not actually true, it uses SNMPv3 by default. Changing our switch definition to force SNMPv1 makes everything work (hooray). Is this a known issue? All the best, Chris -- Christopher Samuel Senior Systems Administrator VLSCI - Victorian Life Sciences Computation Initiative Email: [email protected] Phone: +61 (0)3 903 55545 http://www.vlsci.org.au/ http://twitter.com/vlsci ------------------------------------------------------------------------------ _______________________________________________ xCAT-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xcat-user
------------------------------------------------------------------------------
_______________________________________________ xCAT-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xcat-user
