User's Manual
DragonWave Inc. 
110 
Horizon Compact Plus Release 1.0.1    Wireless Ethernet Product User Manual – Volume 2 
Hovering the mouse cursor over a port icon (red, or green, square, or “handle”) on the graphic reveals 
information about that port. A green handle depicts a connected port and a red handle a disconnected 
port. Both Ethernet and wireless port handles are displayed. Click on a handle while hovering to pin, or 
un-pin, the information bubble to/from the screen. Clicking on any value shown in the bubble will link you 
to the relevant configuration detail which displays below the graphic in place of the Information Pane. 
Figure 17-4 Web Interface – Graphics Features 
When alarms occur, the alarm icon (bell) background colour will change to reflect the severity of the alarm 
(Red, Amber,  Yellow, Green for  Critical, Major, Minor and no alarms respectively). When hovering the 
mouse  cursor over  the  alarm  icon  the number  of  Critical, Major  and  Minor alarms currently present is 
shown.  Clicking  on  the  number  of  active  alarms  links  you  to  the  related  alarms  detail  which  displays 
below the graphic in place of the Information Pane. 
Hovering over the CLI icon reveals a “Web CLI” link. Click on “Web CLI” to open a CLI session with the 
selected  node.  Depending  on  what  node  you  have  initially  logged  onto,  you  may,  or  may  not,  be  
prompted for user name and password. You may then configure features that are not accessible via the 
normal web interface (e.g. user accounts). To expand the CLI session window drag the right hand bottom 
corner to the right and down. To close the CLI window click on the “X” in the top right hand corner of the 
CLI window. 
Figure 17-5 Web Interface – Graphics – Loss of Signal 
Figure 17-5 shows the graphic display when a system node loses synchronization (down). The arrows are 
shown in green for the local node egress indicating that the local node is transmitting. The red arrows 
indicate  that  the  peer  node  is  not  transmitting  modem  blocks  and  therefore  the  link  is broken.  In  this 
instance the cause of the failed node in the figure was a system reset (traffic affecting). The rotating icon 
in the overlay indicates that the peer node will be trying to reconnect in 10 seconds.   










