Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Viewing the Monitoring Page in Gateway View

 

When you log in to the Edge Services Director interface and navigate to the Monitoring page under Monitor mode, the Monitoring SDG is the landing page showing the details of a SDG. This view is split into two parts the left side is a navigation tree showing all the deployed SDGs. Each root node is the name of the SDG and the child nodes are the installed services ADC, TLB, CGNAT and SFW. Each service is a root node for the service instances.

The Monitoring page is refreshed automatically every 3 minutes. Static polling occurs to obtain and display data, and asynchronous collection is not used.

To view the SDGs and associated services to examine, analyze, and troubleshoot device problems and service failures

  1. From the View selector, select Gateway View. The workspaces that are available in this view are displayed.
  2. From the Junos Space user interface, click the Monitor icon on the Edge Services Director banner.

    The functionalities that you can configure in this mode are displayed in the task pane.
  3. From the View pane, select the All Network item in Gateway view. Click the plus sign to expand the tree and view the SDG group or the SDGs in a high availability SDG group or SDG pair.
  4. Drill down the tree and select the SDG or SDG pair for which you want to view monitoring statistics and charts of various system states. The Monitoring page is displayed.
    Figure 1: Monitoring Page
    Monitoring Page

    The page is divided into two panes. The left pane displays a tree structure of the SDG pairs or SDGs configured. For SDG pairs, you can view the master and standby device information; else, the health and performance of the separate, individual SDG is shown. With an SDG pair selected, the right pane is refreshed to show the corresponding master and standby device details.

    From Service View in Monitor mode, you can drill down the tree by clicking the plus sign (+) from the task pane to view the list of services, such as ADC or TLB. Drill down further to view the service template instances configured for the particular SDG or SDG pair. When you select a service instance, the right pane is refreshed to show the corresponding service details.

    You can search for a particular SDG name or service instance name by using the search filter displayed at the top of the left pane.

Viewing Device Details and Statistical Information

When you select an SDG pair on the left pane of the Monitoring page, the following monitors or quadrants are displayed on the right pane:

The Master and Standby tabs display information about the primary or master, and standby or secondary SDGs in an SDG pair. The Service Wait tab is displayed if the standby device is not fully active after a switchover.

The Service Gateway Details monitor provides basic information about the device, such as the running Junos OS version and release number, the management IP address, connection state of the device, hostname, the platform or model number, and the time from which the device has been up.

The Alarms monitor displays the SDG alarms for last 6 hours, 12 hours and 24 hours as line graphs. From the Time Interval drop-down list, select the 6 hours, 12 hours, or 24 hours options to view details for the last 6 hours, last 12 hours, and last 24 hours respectively. Click the Refresh icon at the top of the monitor to update and display the contents of the table. The time is shown on the horizontal axis and the count of alarms is shown on the vertical axis. Red denotes a critical alarm, orange denotes a major alarm, and yellow denotes a minor alarm. Mouse over the points in the line graph to expand and show the number of alarms at a particular time.

The SDG Availability monitor contains details for last 6, 12 and 24 hours. This availability representation is drawn based on the Critical Status from the HA. The purpose of this monitor is to show how much time the SDG was available. It is represented with two lines for each node. This display pattern represents if any switchover happened, and it also helps to identify the reason for it. From the Time Interval drop-down list, select the 6 hours, 12 hours, or 24 hours options to view details for the last 6 hours, last 12 hours, and last 24 hours respectively. Click the Refresh icon at the top of the monitor to update and display the contents of the table.

The lower part of the page displays the Statistics and Chassis View tabs. Under the Statistics tab, you can view the following:

The HA KPI Status monitor displays the KPIs configured for high availability as a line graph. The time period is shown on the x-axis and the KPI parameters are shown on the y-axis. The lines are colored red, yellow, and green based on the KPI definitions for the HA parameters. From the Time Interval drop-down list, select the 6 hours, 12 hours, or 24 hours options to view details for the last 6 hours, last 12 hours, and last 24 hours respectively. Click the Refresh icon at the top of the monitor to update and display the contents of the table.

The SDG Service Status monitor displays a line graph with the SDG service status is based on the KPIs defined for a particular service. The data collected is only for the master. Assume a scenario in which a SDG switchover happened in the last 4 hours, then the present master shows status only from the fourth hour to the selected scale. From the Time Interval drop-down list, select the 6 hours, 12 hours, or 24 hours options to view details for the last 6 hours, last 12 hours, and last 24 hours respectively. Click the Refresh icon at the top of the monitor to update and display the contents of the table.

If the SDGs status is green, then all the services are in green. The other possibilities are red and orange. If the selected SDG is red, it might be because of service-related problems, such as 30% real servers being down in a particular ADC instance. If a certain service is not defined on an SDG, the line corresponding to it in the graph is not color-coded.

SDG availability represents the hostname of the current master. At fourth hour, if a switchover occurs, the service status shows the details from the 4th hour because this particular device was standby earlier. After the standby device transitions to be the master, the data for monitoring the service status is restarted to be collected.

The Critical Messages monitor displays the messages of a severity level of critical. The date and time at which the message was generated, and a description of the message to highlight the module/protocol and the problem condition are shown. From the Time Interval drop-down list, select the 6 hours, 12 hours, or 24 hours options to view details for the last 6 hours, last 12 hours, and last 24 hours respectively. Click the Refresh icon at the top of the monitor to update and display the contents of the table. You can use the paging controls to move to a specific page, to the previous or next page, and to the first or last page.

The HA Switchover monitor displays line graphs for the master and standby devices. The master, standby, and service-wait states are shown on the vertical axis and the time period is shown on the horizontal axis. From the Time Interval drop-down list, select the 6 hours, 12 hours, or 24 hours options to view details for the last 6 hours, last 12 hours, and last 24 hours respectively. Click the Refresh icon at the top of the monitor to update and display the contents of the table.

You can mouse over the line graph that shows the time intervals when a switchover has occurred to view the switchover reason in a tooltip. The reasons for a failover from the master to the standby device might be power supply failure, a switchover initiated manually, or other causes to maintain high availability in a redundancy group. Edge Services Director obtains the reason for switchover from the SNMP traps received from the router and correlates the information with the HA Status KPI in the Edge Services Director database. Knowing the switchover reason enables quick identification of the underlying problem and correcting the failure.

SDG throughput is one of the KPIs to determine exactly how much throughput or capacity used through various services. This is one of the important KPIs to mark the status of SDGs as red, green and orange. The legends are TLB, ADC, SFW and CGNAT.

SDG CPU usage across the configured services for last 6 hours, 12 hours, and 24 hours is also shown. The legends are TLB, ADC, SFW and CGNAT.

Viewing the Chassis Image of Devices

Chassis View is enables the operator to see the details at hardware and software level in a symbolic manner. This view changes according to the type of chassis or device, and the display is modified correspondingly. In this view, the SDG is shown with the Master and Standby devices. This view helps the operator to know the health and status of a particular SDG deployed in the network. It provides a cohesive tool for the operator to quickly see the micro-level information and take any further corrective measure required. Consider a case in which an operator has deployed n number of SDGs in the network. If the operator observes that a particular SDG status and health is not in a satisfied or fully-operational state. The operator quickly navigates to the Monitoring SDG View and selects the particular SDG to see that in one of the slots, the MS-DPC is marked as red. Clicking on the slot indicates that for the slot, configured service ADC daemon is down. In such a case, the restoration measure can be taken. In this view you can quickly view the SDG Chassis details, hardware details, interface Details, important KPIs (CPU and Memory), and the standby details.

When you select an SDG pair on the left pane of the Monitoring page, the following monitors or quadrants are displayed on the right pane:

The Master and Standby tabs display information about the primary or master, and standby or secondary SDGs in an SDG pair.

The lower part of the page displays the Statistics and Chassis View tabs. Under the Chassis View tab, you can view the following:

The Alarms field displays the number of alarms that are critical, major, and minor. Red denotes critical, orange denotes major, and yellow denotes minor alarms.

The master and standby chassis are represented pictorially as an entire device, with the slot numbers on the chassis and the types of modules, such as FPC, PIC, or MIC, installed in each slot. If a particular slot is having trouble then it is colored appropriately. If a card is not installed in the slot, it shows an empty slot.

The Hardware Details table displays the chassis properties such as the model number of the module installed in the corresponding slot, the serial number, the amount of dynamic random access memory (DRAM), the percentage of time that the CPU uses on background processes, the percentage of time for which the CPU is idle, and the temperature of the air passing by the FPC, in degrees Celsius or in both Celsius and Fahrenheit. Click the information icon to view the Hardware Details table as a pop-up dialog box. The PIC Details table displays any attributes that relate to the interface of that particular slot, such as the slot number, the state of the line card in the slot, the total percentage of CPU being used by the FPC's processor, the percentage of the total CPU that is used for interrupts, the percentage of heap space (dynamic memory) being used by the FPC's processor, and the percentage of buffer space being used by the FPC's processor for buffering internal messages. The Service Details table displays the names of different services, such as CGNAT, stateful firewall, ADC, and TLB, configured for the router chassis.

In Edge Services Director Release 1.0, the services such as CGNAT, SFW, or TLB, configured for aggregated multiservices (AMS) interfaces did not account for the services PIC (sp- interfaces) that were part of the AMS bundle. Starting with Release 1.1, you can view the service types and service names configured on AMS interfaces, which also accounts for the member interfaces of the AMS bundle.

Each FPC is shown as a bar, with the different PICs installed on the FPC slots displayed as segments within the bar. In the PIC Details table, the following performance monitoring KPIs are available to measure the performance and the operational status of MS-MPCs (these KPIs are applicable only for the slots in which MS-MPCs are installed and not for other chassis slots):

  • The Heap Utilization column displays the percentage of memory region used for microkernel or heap memory, out of the total CPU memory being used by the Routing Engine or FPC processor. The microkernel memory is generic across the different types of line cards and signifies the heap memory buffers. Because a line card or an FPC in a particular slot can contain multiple Packet Forwarding Engine complexes, the memory utilized on the application-specific integrated circuits (ASICs) are specific to a particular Packet Forwarding Engine complex.

  • The Buffer Utilization column displays the percentage of buffer memory space being used by the Routing Engine or FPC processor for buffering internal messages.

  • The CPU Utilization column displays the percentage of CPU memory used by the Routing Engine or FPC processor. In the chassis view, each slot also represents the number of supported PICs on the service interface. You can select the PIC or the MPC/DPC and the corresponding real-time KPIs are displayed.

  • The CPU Interrupts column displays the percentage of CPU memory used for interrupts, out of the total CPU memory being used by the Routing Engine or FPC processor.

In Service View, click the Monitor icon in the Edge Services Director banner to view the workspaces available in Monitor mode. You can select the service type that you need from the View pane, and the SDG or high-availability pair of SDGs from the task pane to perform the following tasks: