Ubuntu Forums - View Single Post - SNMP and Dell OMSA on a PE 2950 with Ubuntu 6.06LTS server.

Ubuntu Forums - View Single Post - SNMP and Dell OMSA on a PE 2950 with Ubuntu 6.06LTS server.: "SNMP and Dell OMSA on a PE 2950 with Ubuntu 6.06LTS server.
The web interface will start up with /etc/init.d/dsm_om_connsvc start

If you want it to start automatically when you boot up, run this line without the quotes.

'/usr/sbin/update-rc.d dsm_om_connsvc start 20 2 3 4 5 . stop 19 0 1 6 . >/dev/nullssh'

To enable snmp to work with OMSA, you need to enable it. Run '/etc/init.d/dataeng enablesnmp'.
This will add a line at the bottom of your /etc/snmp/snmpd.conf so OMSA can connect to SNMP via smux.

This is the line it adds. 'smuxpeer .1.3.6.1.4.1.674.10892.1'

You still need to configure your snmpd.conf to allow connections to read the snmp. Here is a sample. NOTE: public is always the default community. For added security, change it to something else.


rwcommunity public 127.0.0.1
rocommunity public 127.0.0.1
rwcommunity public servername
rocommunity public servername
trapcommunity public
trapsink servername public
trapsink servername public
syscontact Root <root@localhost>
syslocation corp

Trapsink sends traps to that server, with the community string. I do localhsot AND the servers monitoring it. ro and rwcommunity is pretty self explanatory.

NOTE: Check your /etc/default/snmpd file and remove 127.0.0.1 from the line it's on. That is extra security so only localhost can read your snmp traps. Obviously you want others to read it, so make sure to remove it. When you are done, the line should look like this:

SNMPDOPTS='-Lsd -Lf /dev/null -u snmp -I -smux -p /var/run/snmpd.pid' <-- don't copy and paste this in, just delete 127.0.0.1 out of that line. You need the back tics and the forum format may change them.

Now do: /etc/init.d/snmpd restart
then a /etc/init.d/dataeng restart

That should get you working for 32bit users.

64bit users, keep going.

If you cannot log in at https://servername:1311 and you keep getting log in, incorrect(and it should if you are running a 64 bit distro), you need to copy some files, as OMSA 5 uses PAM and not it's own authentication anymore.

Change /lib/security path to /lib32 in /etc/pam.d/omauth
This is what omauth will look like afterwards

auth required /lib32/pam_unix.so nullok
auth required /lib32/pam_nologin.so
account required /lib32/pam_unix.so nullok


and copy from a 32bit install (a server running a 32bit ubuntu/debian distro) theses files :

/lib/libsepol.so.1
/lib/libselinux.so.1
/lib/security/pam_unix.so
/lib/security/pam_nologin.so

copy into /lib32 on your amd64 servers.

I just run these lines on the 32bit server, to copy over to my amd64 server.

scp /lib/security/libse* root@server:/lib32/

scp /lib/security/pam_* root@server:/lib32/

then edit the /etc/pam.d/omauth as described above.

after a ldconfig (run ldconfig) you should be able to pam login to the web interface at https://server:1311

For snmp to work, I would restart a few services.

Do a /etc/init.d/snmpd restart
then a /etc/init.d/dataeng restart

If you don't have a 32 bit install, PM me, I could zip the files up and send them to you.

That should do it.

Good luck."