Download Denika
Want to try Denika? Contact us for an evaluation copy today!
|Frequently Asked Questions|
Click the question to view the answer.
Q: What is SOE?
A: SOE is the Somix Operating Environment. Installing Denika automatically installs SOE, which includes Apache, MySQL, Active Perl, CRON, and the easy to use SOE web interface.
The SOE web interface includes a User Manager, Configuration Editor, Update Manager, Rotate Manger, and many more useful tools.
Q: Can I monitor any SNMP OID with Denika?
A: Yes. Denika uses a report template system based on MRTG configurations. Templates can be created to trend any SNMP OID.
Q: Is there any documentation that can help me with Denika 6.0?
A: If you need help installing or configuring Denika 6.0, review the documents below:
 SOE: Install Guide SOE: Backup/Restore Guide Denika 6.0: Quick Start Guide Denika 6.0: Upgrade Guide Denika 6.0: How to Setup Email Reports |
Q: I had a problem with the install, what should I do?
A: Call Somix at 207-324-8805 for free, pre-sales support.
Q: Can I automatically create Denika reports?
A: Yes. Denika includes a command line utility for discovering a list of devices or an IP range.
Q: What about devices that go away?
A: Every night Denika checks to make sure reports are still collecting data. If they are not, the reports are disabled at the polling level and the Denika administrator is notified by email and/or syslog.
Q: Where is the Denika Manual?
A: The Denika manual can be accessed by clicking on the SOE button in the Denika web interface. If Denika is not installed you can click here to access our manuals.
Q: How do I setup Cisco IP SLA?
A: Please review the Cisco IOS IP Service Level Agreements User Guide for information on configuring Cisco's IP SLA Technology.
Q: How do I setup NBAR on my Cisco router?
A: Make sure you enable NBAR on the router for the interfaces you want to collect statistics on. Call us if you need help setting it up. You must first enable Cisco Express Forwarding (CEF) on the router before enabling NBAR.
Interfacing with NBAR on your Cisco router is done through the Modular QoS Command-Line Interface (Modular QoS CLI). In order to configure a QoS policy you must configure traffic classes, policies that will be applied to those traffic classes, and the attaching of policies to interfaces using the following commands:
Interfacing with NBAR on your Cisco router is done through the Modular QoS Command-Line Interface (Modular QoS CLI). In order to configure a QoS policy you must configure traffic classes, policies that will be applied to those traffic classes, and the attaching of policies to interfaces using the following commands:
 |
class-map - defines traffic classes by specifying the criteria by which traffic is classified. |
|
policy-map - defines QoS policies which are applied to traffic defined by a class map. |
|
server-policy - attaches certain traffic to an interface on the router. |
Q: How do I configure a traffic class?
A: Here you can assign traffic matching a specified protocol to be classified as belonging to this specific traffic class. The easiest way to put it would be, the traffic class classifies traffic, while the traffic policy determines how to handle the traffic.
To configure a traffic class and the match criteria that will be used to identify traffic as belonging to that class, use the class-map global configuration command. To set the match criteria, use the following commands in global configuration mode.
Step #1
Router(config)# class-map [match-all | match-any] class-name
Specifies the user-defined name of the class map. The match-all option specifies that all match criteria in the class map must be matched. The match-any option specifies that one or more match criteria must match.
Step #2
Router(config-cmap)# match protocol protocol-name
Specifies a protocol as matching criteria.
To configure a traffic class and the match criteria that will be used to identify traffic as belonging to that class, use the class-map global configuration command. To set the match criteria, use the following commands in global configuration mode.
Step #1
Router(config)# class-map [match-all | match-any] class-name
Specifies the user-defined name of the class map. The match-all option specifies that all match criteria in the class map must be matched. The match-any option specifies that one or more match criteria must match.
Step #2
Router(config-cmap)# match protocol protocol-name
Specifies a protocol as matching criteria.
Q: How do I configure a traffic policy?
A: To specify the QoS policies to apply to traffic classes defined by a traffic class, use the following commands beginning in global configuration mode:
Step #1
Router(config)# policy-map policy-name
Specifies the traffic policy name.
Step #2
Router(config-pmap)# class class-name
Specifies the name of a traffic class.
Step #3
Router(config-pmap-c)#
Enters policy-map class configuration mode.
Step #1
Router(config)# policy-map policy-name
Specifies the traffic policy name.
Step #2
Router(config-pmap)# class class-name
Specifies the name of a traffic class.
Step #3
Router(config-pmap-c)#
Enters policy-map class configuration mode.
Q: How do I attach a traffic policy to an interface?
A: Use the following commands in interface configuration mode to attach a traffic policy to an interface and to specify if it is inbound or outbound traffic.
Router(config-if)# service-policy output policy-map-name
Specifies the name of the traffic policy to be attached to all outbound traffic on the interface.
Router(config-if)# service-policy input policy-map-name
Specifies the name of the traffic policy to be attached to all inbound traffic on the interface.
To separate a policy map from an interface, use the no service-policy [input | output] policy-map-name command.
Router(config-if)# service-policy output policy-map-name
Specifies the name of the traffic policy to be attached to all outbound traffic on the interface.
Router(config-if)# service-policy input policy-map-name
Specifies the name of the traffic policy to be attached to all inbound traffic on the interface.
To separate a policy map from an interface, use the no service-policy [input | output] policy-map-name command.
|Denika Product Manual|
An easier way to get help
Denika's context sensative manual makes finding help on the screen currently being viewed much easier. On any given screen, click on the help icon 
to bring up help information specific to the current view.
Need Help?
View the on-line product manual for Denika Performance Trender.
|System Requirements|
Computer Hardware Specifications
Below are the minimum requirements for SOE and its individual components.
 Component |
Recommended Specifications (for production environments) |
|
|
|
20Gb hard disk space |
|
|
| Operating System |
Windows 2000/XP/2003 |
NOTE: As more software is installed and integrated with SOE, the hardware specifications will increase. For example, the Plixer product WebNM requires a dual-processor 2.0 GHz system with 2GB RAM and 80GB of disk space. For Denika trending you will need to allow 5 MB per report or 5 GB per thousand reports. The suggested drive size is 80 GB or more.
Network Traffic Monitoring & Diagnostics Tools
Plixer International - Setting Standards in NetFlow & sFlow Analysis© 2002 - 2010 Plixer International, Inc.
Follow Plixer