Home > Articles > Programming > Java

  • Print
  • + Share This
Like this article? We recommend

Creating Software to Ease the Management Task

Using Java DMK, we can create software that both listens for events and proactively reads the device status. Here I focus on the latter, just to illustrate the principles.

To begin with, I’ll write a simple program that looks at a specific network link and tries to determine if it’s prone to congestion. We do this by sampling and averaging some SNMP counters on an interface at one end of this link. These are standard objects that are maintained by the SNMP entity running on the device. Sometimes, the SNMP entity is not running by default—in this case, I’ll assume the network manager (i.e., your predecessor!) has chosen to run SNMP on all of those devices where it is available. Let’s now describe the simple requirements for the code.

Our Selected Set of Management Requirements

We want to create some software that fulfils the following simple requirements:

  • Return the operational status of a specified interface.
  • Calculate the traffic level for a specified interface.
  • Determine if a specified link is approaching a state of congestion.

An interface usually has an administrative state and an operational state. The administrative state is the one desired by the network manager—"I want this interface to be up." The operational state is the actual state of the interface. Try to think about the operational state as the network’s response to the requested state. If the administrative state is up and the operational state is down, then we know there’s a problem.

The interface type I’ll be using is Ethernet, specifically 10Mbps (or 10,000,000 bps). I’ll be retrieving a snapshot of the count of incoming bits received at an interface at one end of Link 1 in Figure 1. This will give us an instantaneous picture of the inward traffic level at that interface. Then, we’ll wait a bit and retrieve the same counter value. The difference between these two values gives us the required utilization value. Let’s have a look at some source code now.

The Source Code

The Java class I use is called RequestData. It contains a main() method and makes use of the following Java DMK resources (among others):

import com.sun.management.snmp.SnmpDefinitions;
import com.sun.management.snmp.SnmpOid;
import com.sun.management.snmp.SnmpVarBindList;
import com.sun.management.snmp.manager.SnmpPeer;

To begin with, I initialize the SNMP Manager API. This allows us to access the generated table mentioned in the introduction.

final SnmpOidTableSupport oidTable =
  new RFC1213_MIBOidTable();

Next, I create an SnmpPeer object. This represents the entity with which we will communicate. Note that this uses the port passed in as a command-line parameter.

final SnmpPeer agent =
  new SnmpPeer(host, Integer.parseInt(port));

We must now create a communications session with the remote entity. This requires us to specify SNMP community strings. These data elements are then associated with the agent.

final SnmpParameters params =
  new SnmpParameters("public", "private");


We’re nearly there! We now have to build the session to manage the data request and then we’re ready to create the data request list (or variable binding list):

final SnmpSession session =
    new SnmpSession("SyncManager session");

final SnmpVarBindList list =
    new SnmpVarBindList(
    "SyncManager varbind list");

The program is a single Java DMK class that builds an SNMP request message. This message specifies four objects of interest, using the following code:

// A description of the host device

// The operational state of interface 1

// The number of incoming octets on interface 1

// The speed of interface 1

Our four required objects are packed into an SNMP getRequest message and sent to the receiving entity as follows:

SnmpRequest request =
  session.snmpGetRequest(null, list);

We now retrieve the same set of objects twice; the difference in time between the samples is found using this Java code:

// Calculate the time between messages
long oldTime = date1.getTime();
long newTime = new Date().getTime();
long elapsed = (newTime - oldTime) / MS_DIVIDEND;

println("Elapsed time in seconds " + elapsed);

In this section, we get the most recent time and subtract a time value recorded just before the first retrieval. This gives us a rough estimate of the elapsed time between the data samples.

When the returned data is displayed, we see the following major elements:

Value : 25625, Object ID : (Syntax : Gauge32)
Value : 10000000

>> Press Enter to resend the request.

Elapsed time in seconds 16

Value : 26005, Object ID : (Syntax : Gauge32)
Value : 10000000

The three bold data items above represent the two values of the ifInOctets object taken at an interval of 16 seconds. The selected interface (which supports a speed of 10,000,000 bps) has received 25,625 octets (or bytes) at the time T1 and 26,005 octets at the time T2. To determine the incoming link utilization, we apply the following formula:

Incoming Link % Utilization =
     ((T2 octets - T1 octets) * 8 * 100) /
     (ifSpeed * Sample speed)

Plugging in the values above gives us a utilization of (26005 - 25625) * 8 * 100/(10,000,000 * 16), or 0.0019 percent.

Clearly, the interface is very lightly loaded on the incoming side! A similar measurement can be made for the outgoing direction (using the ifOutOctets object instead). Then, both values can be summed to determine the overall loading. Obviously, care is required in drawing any conclusions from the figures (they are instantaneous snapshots of data that can change rapidly), but they do provide some minimal level of understanding of the loading on the interface.

Plying this program with diligence and observing loading trends over a period of a day might lead us to understand why the outgoing network manager made the comment concerning Link 1. In any case, it means that you are beginning to learn about the secrets that the network holds in store! Extending this approach to other regions of the network should help in acquiring a broader understanding again.

Running the Example

To run the example program, you’ll need to install Java DMK. Free evaluation copies can be downloaded from Sun Microsystems, though these copies expire after 90 days. So don’t be too leisurely about running this code! Alternatively, if you win a couple of lotteries, you might be tempted to purchase Java DMK.

In either case, just follow the instructions in the examples\current\Snmp\Manager\ReadMe file, and the example should compile and run successfully. I used Java DMK version 5.1. Also, there’s detail and further Java examples in my book, Network Management, MIBs & MPLS: Principles, Design, & Implementation—no lottery win required!

Remember: Use Patterns

I strongly encourage using the adapter pattern to hide the complexity of the Java DMK API. Really, Java DMK isn’t complex per se, but it is proprietary. For this reason, it’s important to not litter your application code with calls into such an API. The adapter provides a useful model for achieving this noble design aim.

The adapter serves to insulate the application code from the details of the Java DMK (or other) technology. Your code then calls into the adapter, rather than directly using the Java DMK interface. So, if you later decide to change from Java DMK and use another technology, any required changes to your code will have been minimized ahead of time.

Further details on the adapter pattern and its applications can be found in design pattern books, such as O’Reilly’s Head First Design Patterns.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020