Cariden mate tool

In addition to this, however, Cariden Mate provides tools to enrich the plan file with currently measured interface link utilisation data collected from SNMP.

The mathematics and exact algorithm I confess to not understanding at all beyond the premise that the software seems to consider all possible traffic matrices that could be put to the network and how they would effect the links and offers the most likely traffic candidate. The traffic matrix is very valuable data when one considers the difficulties in acquiring an actual observed matrix different network platforms, different line cards with different features etc.

It can be based on data collections from a perceived network high-tide and then be made available offline in order to run simulations against in order to determine where new circuits would best be placed and what the likely impact of planned works would be. This presents a dynamically rendered image which shows the plan file with links coloured according to usage from continuous data stored in archive file. Licensing is typically per-node and per-seat.

The per-node licensing is reasonable but it de-values the topology discovery mechanism which happily disovers every node in the IGP database — inferring location from network naming convention as it goes — whether you intend to use the Cariden Mate functionality for it or not.

Per-seat licensing is enforced through a stubborn adherence to MAC address for client installations which is frustrating. But in conclusion, Cariden Mate provides a very useful complement to the usual first-generation network performance reporting tools that measure interface usage by offering various levels of user both a topology understanding and visibility, and also a view on end-to-end traffic which cannot be gleaned from SNMP data alone. You are commenting using your WordPress.

You are commenting using your Google account. You are commenting using your Twitter account. You are commenting using your Facebook account. Notify me of new comments via email. The total traffic on these interfaces is still measured. As a result, per class-of-service demands estimated through Demand Deduction are less accurate. Estimates of traffic totals over all classes of services, however, are not affected.

If both are used to configure users, MATE uses the most recently updated information. The recommendation is to use only the System UI to manage users.

The wae-ha-deploy script is not updated with the proper version, rendering the wae-core modules unable to start in a multiserver HA environment.

The workaround is as follows:. Run the wae-ha-deploy script. Some newer Linux distributions have started using a new way via biosdevname of naming hardware devices, including the network interfaces. This causes some software that depends on the traditional naming for example, eth0 , eth1 to fail on license checks, including MATE. Syntax varies among distributions. After reboot, you should be able use ifconfig to verify that the NIC are named eth0 or eth1 , The symptom is an error message similar to the following:.

An example setting is as follows:. The following information is missing from the documentation set. For assistance, contact your support representative. For convenience, the entire definition and example are given here:. For example, if set to , to determine the rate of incoming packet errors, the Continuous Poller server takes the average of these incoming packet errors over the last seconds.

These traffic statistics are added to the plan file each time it is generated. The minimum value is seconds. Skip to content Skip to search Skip to footer. Available Languages. Download Options. Step 1 Go to the directory where you installed FlexNet Publisher license server package, and execute the installer.

The package is, itself, the executable that automates the installation process. Example: chmod Note The following instructions are for using either the CLI or license web server, but not both. The recommended practice is to install and use one or the other. For more information, see lmadmin -help.

Start the lmadmin process with its default settings. Step 2 Start the license server web UI, which by default uses a non-secure port of By entering the following in a web browser, you are redirected to the secure port. Step 3 Click the Administration link, and log in using the an administrative username and password. Step 1 Verify the license server port is running. For example, you can telnet to this port to verify that it is running.

Step 2 Verify the license server is running and listening to port , as well as to the established connections. Example: netstat -a egrep '[]'. Step 3 Either distribute the same floating. If you are using the web server to administer licenses, you can set up an access control list.

This is optional, but doing so can improve the security of who can access the web server, as well as give you an easily maintainable list of license users. To do this, you need to know the user ID for all users who are checking out licenses from the license server.