Needs your feedback on SAM's Networking and Communications Functional Area

[Hemanth Gurunath Basrur]

Hello Everybody,

HP-UX System Administration Manager (HP SAM) is used today to manage Network Interface Cards, Network File Systems, DHCPv6, DNS etc. through SAM's Networking and Communications functional area (FA).

Today, you can manage the following from SAM's Networking and Communications FA:

Bootable Devices
DHCPv6
DNS (BIND)
NIS
NIS+
Name Service Switch
Network Interface Cards
Network Services
Networked File Systems
System Access
Virtual LAN

We need your inputs and suggestions. Is there any other feature that can be included?

Your thoughts or inputs would be appreciated.

Thanks,
Hemanth

[Arunvijai_4 · Accepted solution]

Hi Hemanth,

It would be nice to control HBAs from SAM. Presently, it doesn't have the capability to do that.

-Arun

[Devender Khatana]

Hi,

I do not use SAM much so will not ask for much as well. But I have been viewving a lot of people adding default route to networks. It would be great if this can be done using a option in SAM.

Best Regards,
Devender

[Steve Lewis]

Some of these may be configurable in sam already:

Since it does NIS, then how about LDAP?

Not totally networky:
host keys for ssh.
the ability to chroot accounts for ftp access.

What about simple firewall configuration (ipfilter)? Advanced configuration can be done by editing the file, but sam might be a good utility to help people get it up and running in the first place.

[Bill Hassell]

Network security is becoming so important that it makes sense to include SSH, LDAP, IPfilter as part of the core OS, then have SAM setup/configure them. Another area in security is setgting up the /etc/default/security file as well as Trusted policies. The features are all related but not integrated. For the security file, a big oversight is a validity checker (parameter spelling, useable values).

Configuring additional LAN cards with SAM has had a poor history of success. Ideally, SAM could also configure APA (if installed). And a section for common ndd settings such as dead gateway detection, subnet mask rules, etc).

[Bharat Katkar]

How about integrating "lanadmin" into sam!!
Regards,

[Geoff Wild]

To be really honest - I don't use SAM at all for Networking - prefer to do it myself.

I'd rather like to see HP focus on continuing to make the kernel more modular and dynamic as well as removing swap on the fly.

The one part of SAM I do like is the "restricted SAM".

Rgds...Geoff

[Mark Greene_1]

Adding an interface in SAM for fcmsutil would be helpful, as would lanscan.

Also, if HP would bundle snort and include support for that in SAM, that would be awesome.


mark

[Alzhy]

A check that warns/forbids the user to proceeed doing a networking change if the current TTY (Terminal) the user is running SAM at will potentially hang.

Enhancements to APA configuration.

[John Payne_2]

Hemanth,

I divorsed myself from SAM al long time ago. If I were to want something in it for someone else, (like a currently non-existant junior admin, or someone on my team who doesn't do HPUX, but maybe I'm gone...), I would definitely like a subsection on HBA's. (As previously stated.)

Also, more troubleshooting tools would be nice.

Thanks
John