When you install a license certificate or create a metered certificate, a License Certificate object is added to the License Container object in the eDirectory database. If License Container object doesn’t already exist, NLS creates it.
You can use Novell iManager to view information about licenses and their usage for the License Certificate container or license.
In Novell iManager, click > .
Navigate to and select a license file, then click .
Click the tab corresponding to the information you want to view.
You can view a server’s licensing information through the Novell Remote Manager Health Monitor. You can also set trace information for NLS components by completing the following:
The Licensing Information section displays the same information as the version console command, allows you to set licensing system options, and create a licensing system report.
NOTE:The NetWare usage information that was provided through Novell Remote Manager in NetWare 6.0 has been moved to iManager. See Section 4.0, Metering Network and Product Usage.
Log in to Novell Remote Manager.
See the NW 6.5 SP8: Novell Remote Manager Administration Guide for more information.
Click > .
(Optional) Click to configure the trace settings or click to view or e-mail a report about licensing on this server.
Licensing information has been added to the version command executed at the server console. The version command now displays the information about the server license and user licenses.
If you are using a 90-day evaluation license included with an earlier version of NetWare in the \LICENSE folder, the following is displayed by the version command:
Server License: Novell NetWare 6 Server Eval 650 SN:123456789
User License: Novell NetWare 6.5 User Eval 650 (Hard Stop)
If you installed an MLA license, the following is displayed:
Server License: Novell NetWare 6.5 Server 650 SN:123456789
User License: Audited
If a license has not been installed or has not yet been identified by the server, the following is displayed:
Server License: Novell NetWare 6.5 Server Eval 650 Not Acquired
If a license has expired, the following is displayed:
Server License: Novell NetWare 6.5 Server 650 Expired
When deleting and installing licenses, you need to flush the NLS cache. For more information, see Section 7.30, I replaced my expired licenses. Why am I still getting messages saying that my licenses are expired?.
You can use SNMP to find out about licensing service events on your network.
SNMP is a management interface and high-level protocol. General-purpose protocols such as IPX™, TCP/IP, and UDP can host SNMP. NLS takes events and errors, wraps them in one of these protocols, and sends them to a management utility or console.
For example, suppose you instruct SNMP to raise an event whenever a license unit is conveyed to a User object. Every time a license unit is conveyed, SNMP sends a packet to a management console. The console registers that event. As network administrator, you can view these packets at the management console.
With SNMP, you can send out a wide variety of different events. NLS provides a list of events and errors that the licensing service can send out notifications on. As network administrator, you choose the events that you are interested in. You can turn off all events, turn them all on, or turn on selected events.
For example, NLS sends broadcast messages. Using SNMP, you can send an SNMP message with the same content to a management console.
In short, SNMP enables you to be aware of what’s happening on the network.
An SNMP management product—for example, OpenView* or ManageWise®— resides on the network and registers itself as the management console. An SNMP agent (snmp.nlm) runs on a NetWare server. The SNMP pieces on each server send the SNMP datagrams to the console. You use the console to track what’s happening on the network.
You can place the management console anywhere on the network. This console reads the SNMP packets and displays their contents to you, as the network administrator. Typically these consoles are run on client computers for convenience, but that functionality can be implemented on any computer on the network.
NLS uses three configuration files for SNMP. The configuration files allow the various systems which provide SNMP information to tailor that information to your needs as you manage the network. All three files are installed into sys:\etc.
snmp.cfg lets you add descriptive strings that might be included in SNMP packets. These packets provide you with specific information, such as server name, computer hardware description, location, and whom to contact in case of an issue.
nlstrap.cfg lets you specify which NLS events and errors you want to track. nlstrap.cfg has a list of all possible events that NLS could ever send out. The file contains two lines for each event. The first line is a description. The second line enables or disables notification for that event. If the line begins with a pound sign (#), no message is sent.
By default, all lines (events) are commented out. To see an event, you edit nlstrap.cfg. The file contains a description at the top about the format and what to do with each value. You just turn on what you want to see.
If nlstrap.nlm detects an event that is enabled in the nlstrap.cfg file, nlstrap.nlm calls routines provided by snmp.nlm to place the SNMP packet on the network.
traptarg.cfg lets you specify all targets (or receivers) that are to receive SNMP trap messages generated by the SNMP agent (snmp.nlm). It pairs targets with a protocol for SNMP packet addressing. For example, a server named PUFFIN in the IPX section of traptarg.cfg instructs NLS to send SNMP messages to server PUFFIN using IPX.
Edit nlstrap.cfg to set events that you want to monitor.
Specify parameters by using a parameter keyword followed by the desired parameter value. Then unload and reload nlstrap.nlm. (The changes won’t take effect until you reload nlstrap.nlm.)
Edit snmp.cfg.
Edit traptarg.cfg to specify all targets that are to receive SNMP trap messages.
Run the management console.
Load snmp.nlm on a server.
Snmp.nlm (the SNMP agent) provides the APIs and framework to allow SNMP to work on NetWare. snmp.nlm traps events, generates SNMP messages about the trapped events, and sends the messages to the management console.
At the management console, view the SNMP messages.