Home

Dialogic BorderNet 4000 SBC Maitenance and Troubleshooting Guide

1. LoginStatuses xml LoginStatuses xml Success Success Success 2012 03 06 01 24 26 SECMANAGER LoginStatuses xml Success 2012 03 06 00 38 33 SBCMANAGER LoginStatuses xml Success WI UJ NE 2012 03 05 23 30 12 SBCMANAGER NpVlanifCfg 24 xml Success 2012 03 05 23 30 12 SBCMANAGER NplpCfg 29 xml Success 2012 03 05 23 20 22 SBCMANAGER LoginStatuses xml Success 2012 03 05 21 19 19 SBCMANAGER YI 201 2 03 05 21 14 05 SBCMANAGER LoginStatuses xml Success LoginStatuses xml Success os Lay NJ LT 2012 03 05 20 17 45 2012 03 05 19 18 21 2012 03 05 19 13 10 2012 03 03 14 16 24 2012 03 03 14 10 45 2012 03 03 02 25 42 SBCMANAGER SBCMANAGER LoginStatuses xml LoginStatuses xml Success Success T SBCMANAGER SBCMANAGER SBCMANAGER LoginStatuses xml SBCMANAGER LoginStatuses xml LoginStatuses xml LoginStatuses xml Success Success Success Success E 2012 03 03 02 16 40 SYSMANAGER Page of30 gt gt 20 MA LoginStatuses xml Success View 1 20 of 600 A 2 Click the filter button to refine the results lt EI g 3 Enter the filtering from the screen below Audit Filter User Name Event Resource Date YYYY MM DD and Time HH24 MI 55 a
2. Interface Statistics IST page 1 of2 b b Total Sessions Total Sessions Total Attempts Answer to Seizure Interface Name Attempted Answered with Media Ratio 6 Received Packets Dropped Packets Dropped Messages I10 jan 2072 00 00 SIP IF1 145 428 145 428 145 428 SIP IF2 145 428 145 428 145 428 SIP IF3 145 148 145 147 145 148 SIP IF4 145 148 145 148 145 148 10 Jan 2012 SIP IF1 201 657 201 657 201 657 SIP IF2 201 657 201 657 201 657 SIP IF3 198 056 198 057 198 056 SIP IF4 198 056 198 056 198 056 10 Jan 2012 SIP IF1 201 640 201 640 201 640 SIP IF2 201 640 201 640 201 640 SIP IF3 193 040 193 039 193 039 SIP IF4 198 039 198 039 198 039 10 jan 2072 SIP IF1 201 640 201 640 201 640 SIP IF2 201 640 201 639 201 640 20 Statistical Reports Reporting Incoming Sessions 1 From the Diagnostics menu select Incoming Sessions under Interface Statistics Report Filter InterfaceStatsincoming Hourly Start Data 2012 01 10 End Date 2012 01 10 2 Select whether you want to report the Interface Statistics hourly or five minute intervals 3 Select the Start Date and End Date of the period that you want to report Interface Statistics 4 Click OK and the following appears Interface Statistics AA page 1 of3 b bM Rejecied Sessions Sessions Max Active Active Sessions Incoming Interface Name jeu Average Kate Peak Rate SERM Rate Exceeded Limit Sessions Limit Overload Tibjgn X012 3IP IF1 3IP IF2 SIP IF3 3IP I
3. 192 168 200 0 10 55 10 0 3 3 2 0 100 100 208 0 10 52 0 0 169 254 0 0 169 254 0 0 169 254 0 0 default 10 53 21 1 10 53 21 1 10 53 21 1 10 53 21 1 10 5 20 1 session3 321 session3 321 session1 session1 200 session3 321 session3 321 session3 22 session3 223 session4 mgmt ha session3 321 session2 22 session3 11 session2 ha mgmt session3 mgmt 33 Dialogic BorderNet 4000 SBC Maintenance and Troubleshooting Guide Real Time Status and Performance All functionalities are accessible through the WebUI Alarms On the WebUI three color coded boxes at the top displays the number of current alarms in three categories e Critical Red e Major Orange e Minor Yellow E mi2 go Each of these boxes represent the numbers of outstanding alarms by severity Periodic refreshing these alarm numbers indicates ongoing alarm notification for the operator s visibility See the Troubleshooting chapter for an explanation of alarms and corrective actions Dashboard The dashboard provides real time information on how BorderNet 4000 SBC is functioning including the platform status and system performance above including the following e Current alarms color coded by severity e Real time charts on the last 60 seconds of CPU and memory usages e Hardware component status e Memory Utilization e Storage utilization and thermal status e Current total number of live signaling and media sessions e C
4. BorderNet 4000 SBC Maintenance and Troubleshooting Guide CPU Usage The chart below displays the last 60 seconds of CPU activity and bandwidth Storage and Temperature Storage 17 Temperature LB T The Storage indicates the disk space usage as a percentage The Image is made up of 10 bands When storage exceeds 709 capacity it changes the color of the exceeded space above 70 to orange When it exceeds 80 exceeded space is represented in red to get the operator s attention For example if storage space consumption is 85 the eighth band is shown in orange and the ninth band is shown in red Temperature is shown in both Centigrade and Fahrenheit The band at the bottom is color coded When it goes up to the warning threshold the band shows the exceeded range in orange At critical threshold the band color shows the exceeded value in red to get operator attention Alarm Severity Packet Drop License Capacity Alarm Severity A Packet Drop None License Capacity 32000 The Alarm Severity indicates the highest level of alarm found in the system For example if there are zero outstanding critical alarms red two major alarms orange and five minor alarms yellow then dashboard would show an orange alert The Packet Drop indicates the level of discarded Ethernet packets in the system It has the following three levels e None 0 10 percent packets being dropped e Low 10 25 percent packets being droppe
5. e g VLAN IP IPROUTE etc and the object identified e g Id or the Name of the object that failed to get configuration on the platform When the Session Detail Record SDR is disabled no SDR records are generated while both Signaling and media traffic are on going A particular peer gets more packets than configured and entered into the Blacklist The system received a high session rate more than configured The system received malformed SIP messages from a peer more than allowed so it is blacklisted Too many packets are being dropped in the system usually provides the error not received from the operating system which can be used to further debug the issues with the configuration data The operator should check and correct remove the invalid configuration data from the provisioning system and manually clear the alarm To enable the Session Detail Record select SDR Configuration from the System menu Select Enable Verify with Security Profile and Reports peer level statistics will be needed Operator should first check if this is the desired behavior If it is then monitor to see if the peer is removed from blacklist after the timeout otherwise the dynamic blacklisting can be re configured Verify with the Security Profile and Reports peer level statistics will be needed First check if this is the desired behavior If it is then monitor to see if the peer is remo
6. link is administratively disabled The alarm gets cleared when this Ethernet link is administratively Enabled When the platform becomes active from standby the configuration data is validated If the validation fails then this alarm is raised Raised when the Ethernet link is administratively disabled The alarm gets cleared when this Ethernet link is administratively Enabled The received configuration failed to get configured applied on the BorderNet 4000 SBC platform The following are the configuration failure examples that could result in this alarm IP Address assignment un assignment failure The FDN and additional respective Peer Check availability of the gatekeeper from the BorderNet 4000 interface Turn Off and On the interface to reinitiate registration Follow the detail error message in the alarm and delete the objects that caused the validation to fail and restart the platform Delete the object that caused the problem Then restart the platform The alarm is the result of user action disabling the link User can enable the link from Ethernet Links Screen Follow the detail error message in the alarm and delete the objects that caused the validation to fail and restart the platform Delete the object that caused the problem Then restart the platform The alarm is the result of user action disabling the link User can enable the link from Ethernet L
7. 06 366 283 62 366 529 3 0 75 228 011 83 228 014 34 251 780 8 251 788 T 0 19 313 179 88 313 180 277 366 506 24 366 507 19 0 19 313 178 06 373 180 69 366 506 28 366 506 62 15 Dialogic BorderNet 4000 SBC Maintenance and Troubleshooting Guide Peer Statistics Reporting Summary 1 From the Diagnostics menu select Summary under Peer Statistics Report Filter Peer Stats Summary Report Interval f Hourly Date f Five Minutes atan Date End Date 2 12 07 16 Select whether you want to report the Peer Statistics hourly or five minute intervals Select the Start Date and End Date of the period that you want to report Peer Statistics 4 Click OK and the following appears A i 4 pagetof7 b b Peer Statistics Summary Hourly Total Sessions Total Sessions Total Attempts Answer to Attempted Answered with Media Seizure Ratio Peer Name 2012 02 04 03 00 ASTRA C4 70 C4 x86 132 EAST UA1 EAST UA2 Linksys 1 Linksys 2 MB1 MB2 Prot c4 o oc cO 8 O oO O oc oco oc uoc SIP 5060 UAC SIP 5060 UAS SIP 5060 UAS 2060 16 Statistical Reports Reporting Peer Packet Statistics 1 From the Diagnostics menu select Packet Statistics under Peer Statistics Report Filter PeerStatsPackets Report Interval f Hourly Five Minutes Date Start Date 2012 07 1 5 End Date 2 12 07 16 2 Select whether you want to report the Peer Statistics hourly
8. 08 AM POT System Trace Submissions Summary Username Trace Profile StartTime Duration seconds sbcmanager Interface March 22 2012 10 23 50 M PDT 1800 A Do you really want to Stop this 8 trace E Media Capture The BorderNet 4000 SBC supports media capture and recording from any connection point on the network The GUI displays basic RTP stream characteristics and multiple media streams can be selected and played back at any given time 31 Dialogic BorderNet 4000 SBC Maintenance and Troubleshooting Guide System Status The Management System reports the following real time system status information for the active platform on the management screen e ACL Status e IP Route Status Reporting ACL Status Access Control Lists ACLS selectively allow or deny traffic from specified remote entities You can create a set of static filtering rules to accept or block traffic and BorderNet 4000 creates service specific ACLs based on other configurations These service aware ACLs enable fine grain control over BorderNet 4000 traffic and prevent DoS attacks from random sources Follow the steps below to report the security Access Control List ACL Status summary 1 From the Diagnostics menu select ACL Status under System Status Security ACL Status Filter Application Action 4 Click OK 32 System Status Security Access Control List Status Summary e Remote IP Remote Hetmask Re
9. Alarm Customization A Severity Category Severity Editable Operator Clearable Logging Enabled SNMP Traps aj a Configuration Interface Creation Failed Yes No Overload Bandwidth Limit Reached at Interface Yes No Security TLS Connectivity to Un Configured Peer Fe Yes No Security TLS Connectivity to Configured Peer Failec Yes No Overload Session License Limit Reached Yes No Overload System Session Limit Reached Yes No Overload Approaching Session License Limit Yes No Overload Approaching System Session Limit Yes No Session Connectivity Failure with Peer No Configuration Interface Activation Failed No Configuration Registration with Gatekeeper failed Yes No Qos Packet Rate Limit exceeded at Peer Yes No Qos Packet Rate Limit exceeded at Interface Yes No Security Excessive Packet Drops Yes No Security Peer Backlisted Yes No Qos Maximum Active Sessions reached on Pee Yes No Qos Maximum Active Sessions reached on Inte Yes No Maximum Outgoing Active Sessions reach Yes No Maximum Outgoing Active Sessions reach Yes No PPP PP PP PP PP PP PPP Fr Fr PR gt A A A A A A A A A A zt f zt A A A A A A Al Maximum Incoming Active Sessions reach Yes No Page of2 View 1 20 of 39 3 The following screen appears 10 4 You can change the alarm definition including the severity Reporting Pending Alarms Customize Alarm Event Display Name Category severity Editable severity Operator Cle
10. NNI EndDate SatTme Emme Note The User Name and Resources fields are case sensitive 47 Dialogic BorderNet 4000 SBC Maintenance and Troubleshooting Guide 4 To display the details on a record select the record and click the audit button You can also double click any record to display the audit details Audit Details Time 2012 03 06 03 41 26 User Name SBCMANAGER Device Event UPDATE Resource LoginStatuses xml Result Success Details Content LastLoginT5 2012 03 DBTO0Z2 35 23 ILastLoginTS Lastl oginTS22012 03 06703 41 26 LastLoginTS gt 48 Troubleshooting Troubleshooting This section help you determine the cause of a problem with the BorderNet 4000 SBC and includes corrective actions to follow Alarms The table below lists each alarm that the BorderNet 4000 SBC produces along with descriptions and corrective actions Ethernet Link Failed Network Critical Raised when the system detects the Ethernet link both Primary and Secondary Ethernet links of the link pair to have failed Network Major The system detects the physical interface failure Configuration Critical The system failed to open up a listening ip port for the configured interfaces Physical Ethernet Interface Failed Interface Activation Failed Registration with Gatekeeper failed Configuration Critical The H 323 Interface failed to register with t
11. Network 2012 07 09 17 47 21 Physical Ethernet Interface Faile Interface Platform walnut Interface Eth9 Physical ethernet interface E Raise Raise Network 2012 07 09 17 47 21 Physical Ethernet Interface Faile Interface Platform walnut Interface Eth8 Physical ethernet interface Raise Network 2012 07 09 17 47 21 Physical Ethernet Interface Faile Interface Platform walnut Interface Eth7 Physical ethernet interface Raise Network 2012 07 09 17 47 21 Physical Ethernet Interface Faile Interface Platiorm walnut Interface Eth1 Physical ethernet interface PrP PP PP RP Raise Network 2012 07 09 17 47 21 Physical Ethernet Interface Faile Interface Platform walnut Interface Eth3 Physical ethernet interface 2 Click the filter button to further refine the results ie mi is 3 Change the reporting criteria from the screen below alarmFilter Severity Major I Minor Category spr Session F Qos Peer License Configuration Security T HA Overload Network I Hardware System Date YYYY MM DD and Time HH24 MIE SS StartDate Eae santime nd Time Reported Type See also the Alarms section in the Troubleshooting chapter 13 Dialogic BorderNet 4000 SBC Maintenance and Troubleshooting Guide Statistical Reports The BorderNet 4000 SBC generates reports to show traffic and operational information Statistical data is stored locally on the BorderNet 4000
12. Utilization O MEth11 Eth7 B Eth10 Ethe 20 Eth3 Eth5 E Eths Eth SEC J The Session Link Utilization percentage provides a graphical representation of all four session interfaces in the system It captures utilization every second and graphs it overa one minute time interval If a session link is set to 1 Gbps and if it carries a traffic of 500 Mbps the utilization is represented as 50 Reporting CPU Utilization Follow the steps below to report CPU utilization 1 From the Diagnostics menu select CPU Usage under the System Performance section Report Filter CPU Usage Report Interval f Hourly Date f Five Minutes Start Date End Date 20 Select whether you want to report the CPU Utilization hourly or five minute intervals 3 Select the Start Date and End Date of the period that you want to report CPU Utilization 4 Click OK and the following appears 39 Dialogic BorderNet 4000 SBC Maintenance and Troubleshooting Guide i 4 pagetor2 b M CPU Utilization Report Hourly Max Usage Platform 04 Feb 2042 1 04 Feb 2012 1 04 Feb 2012 1 04 Feb 2042 4 04 Feb 2042 1 01 Feb 2012 1 01 Feb 2012 4 40 Software Management Software Management This section explains how to perform the following Displaying software information Uploading new software Upgrading software Rolling back software Backing up and restoring configuration data Displaying Software In
13. Yes or in five minute intervals No 3 Select the Start Date and End Date of the period that you want to report Peer Statistics 4 Click OK and the following appears Peer Packet Statistics Hourly Signaling Dropped Packets Dro Mes Received Packets Rate oes Peer Name 27 Feb 2012 C470 Mu B1 SIP 5060 UAC SIP 5060 UA5 Spectra 3 27 Fob 2012 01 00 C4 70 Mu B1 SIP 5060 U4C SIP 5060 UA5 Spectra 9 27 Feb 2012 02 00 C470 Mu B1 SIP 5060 UAC SIP 5060 U4 5 Spectra 3 27 Feb 2012 03 00 C4 70 Page 1 of 3 17 Dialogic BorderNet 4000 SBC Maintenance and Troubleshooting Guide Reporting Incoming Sessions 1 From the Diagnostics menu select Incoming Session under Peer Statistics Report Filter PeerStatsincoming Report Interval Hourly Five Minutes Date Start Date End Date Select whether you want to report the Peer Statistics hourly or five minute intervals 3 Select the Start Date and End Date of the period that you want to report Peer Statistics 4 Click OK and the following screen appears Peer Statistics pagetora P M Rejected Sessions Max Active Active Sessions Incoming Peer Name mcn Rate Exceeded Limit Sessions Limit Overload IgA I012 Peerl Peerl term Peerd Feerd orig Peers Peer3 terra Peerd Peerd ong TOA Peer 100 828 100 828 Peerl term 0 D Peer 0 o Peer2 org 100 229 100 529 Peer 97 227 07 228 Peer3 term 0 Peerd 0 0 Peerd ong 100 829 1
14. and so forth BorderNet 4000 SBC enables operators to change severity generate an SNMP trap or generate email notices for each individual alarm See also the Alarms section in the Troubleshooting chapter for listing of alarms and corrective actions Alarm History Alarms from the last seven days are retained in the system by default Non pending alarms older than seven days are purged every 24 hours Diagnostics Categories The BorderNet 4000 SBC supports the following category of alarms QoS Configuration HA License Peer Overload Hardware Network System Security Session The following are the severity levels and the corresponding icon color Critical amp Red Critical alarms are a subgroup of the major alarms Critical alarms are issued when service has stopped and an immediate corrective action is required Major Orange A major alarm is raised when service affecting condition has developed and an immediate corrective action is required Minor Yellow A minor alarm condition is raised due to the existence of non service affecting fault condition and that corrective action should be taken in order to prevent a more serious fault Dialogic BorderNet 4000 SBC Maintenance and Troubleshooting Guide Alarm Customization From the Alarm Customization screen you can edit each alarm by clicking on alarm from the action list 1 From the Diagnostics menu select Customization under the Alarms section
15. owners This document discusses one or more open source products systems and or releases Dialogic is not responsible for your decision to use open source in connection with Dialogic products including without limitation those referred to herein nor is Dialogic responsible for any present or future effects such usage might have including without limitation effects on your products your business or your intellectual property rights Table of Contents About this PUDICATION Narra ia 6 Related Documenta Omara ads 6 OVVIE Winnie ai i a anal a 7 DIAGN OSUCS aiii 8 PMNS mat cita a ad ii a i du oa 0 ua e E id UD a E a ta a A 8 Alarmi Ena E Po ume 8 Kell COONS T e oo A e Pee E 9 ART CASO NN ALON a iesea tai atit dim i al a A a Cota a ta a 10 Reporting Pending Alarms c ceea eee eee ahhh nna aan 11 Reporting Alarm FIISEOIY sume puma maia mc puii ice ina ati a ao n a a au in a aa i 13 Statistical REDOMES siia RR E CN CR CR iai ia e ERR COR iai ia mai ER i aia i ata intaia ia mai dona Ara iu ata aaa inainta 14 Reporta Btnermnet LI ICE on is it aia a n Ea aa a aa a taia 15 Peer SUALISUCS sticcseantaebeccnaeacasendenrsiandecdnennteasnGcnteadmearsemintandeaseensdanentcsdaadecantends 16 RCDOFUNG UA Vaze oamnei aie a dragi aa Bica a aaa do Aa ti ata ea late Daia a N aa e aa ai 16 Reporting Peer Packet Statistics seen ese nnne nnn amen rn nnn 17 Reporting Incoming Sessions eessseeeesseeee nennen nnn nha nhan
16. 0 12 06 39 56 201 1 10 12 06 39 56 Physical Interface Failed Link Failed Link Failed Platform walnut Interface Eth9 Platform walnut Link Sessionlf 3 Plattorm walnut Link Session f 4 Eth9 Physical interface has failed Failure in Ethernet Link on interface Sess Failure in Ethernet Link on interface Sess Pr rrr rr rr PP Pr pp pp pp p 201 1 10 12 06 39 56 2011 10 12 07 22 49 201 1 10 12 07 22 50 2011 10 12407 22 50 2011 10 12407 22 50 2011 10 12 07 22 50 2011 10 12407 22 50 2011 10 12407 22 50 2011 10 12 07 22 50 201 1 10 12 07 22 50 Link Failed Physical Interface Failed Physical Interface Failed Physical Interface Failed Physical Interface Failed Physical Interface Failed Physical Interface Failed Physical Interface Failed Physical Interface Failed Link Failed Platform walnut Link Sessionif 2 Platform cashew Interfsce Eth WPiationm cashew Interface Eth Piatform cashew Interface Eth10 Pistform cashew Interface Eth7 Platform cashew Interface Eth11 Platform cashew Interface Eth8 Platform cashew Interface Eth5 Pistformscsshew Interface Eth3 Platform cashew Link Session f 3 Failure in Ethernet Link on interface Sess Eth3 Physical interface has failed Eth6 Physical interface has failed Eth10 Physical interface has failed Eth7 Physical interface has failed Etht Physical interface has failed Eths Physical interface has failed Eth5 Physical
17. 00 829 18 Statistical Reports Reporting Outgoing Sessions 1 From the Diagnostics menu select Outgoing Sessions under Peer Statistics Report Filter Peer StatsOutgoing Report Interval Hourly Five Minutes Date start Date End Date Select whether you want to report the Peer Statistics hourly or five minute intervals 3 Select the Start Date and End Date of the period that you want to report Peer Statistics 4 Click OK and the following appears Peer Statistics OEA pagetofa P PM Rejected Sessions Max Active Active Sessions Outgoing Peer Name Sessions Rate Exceeded Limit Sessions Limit Overload O I3 Peerl Peerl term Peer Peer2 ong Peers Peer3 term Peerd Peerd ong Tih fan 2072 Peer 0 0 Peerl term 100 829 100 829 Peer2 100 828 100 828 Peer2 ong o Peers 0 Peer3 term 100 829 100 829 Peer 91 321 91 227 Peerd ong o 19 Dialogic BorderNet 4000 SBC Maintenance and Troubleshooting Guide Interface Statistics Reporting Summary 1 From the Diagnostics menu select Summary under Interface Statistics Report Filter Interface Stats Summary Report Interval v Date Hourly Five Minutes start Date End Date 2 Select whether you want to report the Interface Statistics hourly or five minute intervals 3 Select the Start Date and End Date of the period that you want to report Interface Statistics 4 Click OK and the following appears
18. CP e UDP e Host e Port e Arp The remaining Wireshark filters can be used to narrow down the traces The operators and logical operations follows the Wireshark syntax Note Tracing may not capture all packets when the packet traffic is too high on the interface or when system is processing a high amount of traffic Dialogic recommends that you use specific capture filters instead of display filters which are applied on the captured messages to narrow down the packet traffic of interest 30 Tracing Session Tracing You can display current sessions that are connected from Wireshark Trace Sessions The data displays the following e Wireshark trace requests in progress e TraceProfile used for tracing e Start time of the trace For session traces the TraceProfile shows the Interface and for recording profiles the trace profile shows the actual profile used You can stop each of these traces from the WebUI Click the Edit button to see the options to stop the trace Double click on the entry to show a detailed view of the trace request 1 From the Diagnostics menu select Sessions under Trace System Trace Submissions Summary Username Trace Profile StartTime Duration seconds sbcmanager SignalingWoMedia January 26 2012 12 41 38 PM PST 1800 2 To stop the session trace select Stop from the edit button Click Confirm Welcome SBCMANAGER Logout Dialogic BorderNet 4000 SBC System March 22 2012 10 28
19. Dialegic Dialogic BorderNet 4000 Session Border Controller SBC Maintenance and Troubleshooting Guide October 2012 64 0549 04 www dialogic com Copyright and Legal Notice Copyright 2012 Dialogic Inc All Rights Reserved You may not reproduce this document in whole or in part without permission in writing from Dialogic Inc at the address provided below All contents of this document are furnished for informational use only and are subject to change without notice and do not represent a commitment on the part of Dialogic Inc and its affiliates or subsidiaries Dialogic Reasonable effort is made to ensure the accuracy of the information contained in the document However Dialogic does not warrant the accuracy of this information and cannot accept responsibility for errors inaccuracies or omissions that may be contained in this document INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH DIALOGIC PRODUCTS NO LICENSE EXPRESS OR IMPLIED BY ESTOPPEL OR OTHERWISE TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT EXCEPT AS PROVIDED IN A SIGNED AGREEMENT BETWEEN YOU AND DIALOGIC DIALOGIC ASSUMES NO LIABILITY WHATSOEVER AND DIALOGIC DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY RELATING TO SALE AND OR USE OF DIALOGIC PRODUCTS INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS FOR A PARTICULAR PURPOSE MERCHANTABILITY OR INFRINGEMENT OF ANY INTELLECTUAL PROPERTY RIGHT OF A THIRD PARTY Dialogic
20. FA Tibfgn X012 3IP IF1 100 828 100 828 3IP IF2 100 829 100 829 SIP IF3 97 2277 91 228 3IP IFA 100 829 100 829 Ihen ia SIP IF1 100 520 100 820 SIP IF2 100 820 100 820 SIP IF3 971 220 77 419 SIP IFA 100 820 100 820 Tibfgn 2012 gag SIP IF1 100 820 100 820 21 Dialogic BorderNet 4000 SBC Maintenance and Troubleshooting Guide Reporting Outgoing Sessions 22 1 From the Diagnostics menu select Outgoing Sessions under Interface Statistics Report Filter Peer Statsincoming Report Interval Hourly Date f Five Minutes start Date End Date Select whether you want to report the Interface Statistics hourly or five minute intervals Select the Start Date and End Date of the period that you want to report Interface Statistics Click OK and the following appears Interface Statistics going ipageiot3 P PM Rejecied Sessions Sessions Sessions Max Active Active Sessions Outgoing Overload Interface Mame Attempted a Average Rate Peak Rate Rate Exceeded TO SIP IF1 SIP IF2 SIP IF3 SIP IFA O O SIP IF1 100 529 100 529 SIP IF2 100 828 100 828 SIP IF3 100 829 100 829 SIP IFA 91 AI Ida da ra aul Ia SIP IF1 100 820 100 820 SIP IF2 100 820 100 820 SIP IF3 100 220 100 220 SIP IFA 97 219 971 219 20 a 2012 SIF IF1 100 20 100 20 Sessions Limit Sessions Limit Statistical Reports System Statistics Reporting Packet Statistics 1 From the Diagnostics menu select Packet Statist
21. Maintenance and Troubleshooting Guide Diagnostics This section explains how to use the Monitor and Diagnostics module to maintain your BorderNet 4000 SBC including the following e alarms e reports e performance e tracing e system status The procedures in this section are available from the Diagnostics menu below Diagnostics Application System Software Alarms Reports Reports Pending system Performance Interface Statistics History Customization Trace Sessions Plugin system Status ACL Status IP Route Status CPU Usage Traffic statistics Ethernet Links aystem Statistics Summary Packet Statistics Incoming Sessions Outgoing Sessions Summary Incoming Sessions Outgoing Sessions Feer Statistics Summary Packet Statistics Incoming Sessions Outgoing Sessions Alarms The WebUI gathers and presents alarms as follows e Pending Alarm screen which allows operators to view all pending alarms and to filter all pending alarms based on severity category time and name e Alarm History screen which allows operators to view all historical alarms and to filter alarms based on severity name category time reported object type and FDN e Alarm Customization screen which enables operators to customize severity to set whether to generate SNMP trap whether to generate email notice on each individual alarm Alarms can be filtered by severity category time
22. Maintenance and Troubleshooting Guide Platform Status The WebUI reports the following real time platform status information for the active platform Note You can toggle the view between the Active and Secondary platforms The color coding for the LEDs are as follows e Red Down e Gray Not configured or disabled e Green Up or active Component Management High Availability and Media and Signaling Links PS 1 PS 2 Hard Disks e HD 1 ae HD 0 Fans FAN 1 FAN2 FAN3 FAN4 Integrated Platform Status LEDs 38 Supported Status e Dark green Active e Pale Green Standby e Red Down e Gray Not Configured e Green Functional e Red Non functional or down e White Not installed e Green Functional e Red Non functional or down e White Not installed e Green Functional e Red Non functional or down e White Not installed Top left M Fault indicates a major fault warning such as if a component temperature reaches a critical reading Top right P Fault indicates a power supply fault This LED illuminates if a fault occurs with a fan temperature or voltage reading associated with the power supply Bottom left C Fault indicates a critical non recoverable event The BorderNet 4000 SBC will perform a graceful shutdown to protect components from thermal damage Bottom right Not currently used Real Time Status and Performance Session Link Utilization Session Link
23. Media packets dropped for different reasons Follow the procedures in this section to run the BorderNet 4000 SBC reports 14 Statistical Reports Reporting Ethernet Links 1 From the Diagnostics menu select Ethernet Links under Traffic Statistics Report Filter EthernetLink Report Interval Date f Five Minutes f Hourly start Date End Date Select whether you want to report the Ethernet Links hourly or five minute intervals Select the Start Date and End Date of the period that you want to report Ethernet Links 4 Click OK and the following appears Packets Transmitied n Millions Packets Recemed in Millons Byies Transmitied Bytes Received dde MBytes MBytes Transmit Errors ZJgn 3012 mi ag ZiJgn 3012 ura 2073 bnetqaet Ftho bnetqaet Etha bnetga Eths bnetqaet Fth bnetqac Eth bnetqaet Ftho bnetqad Eth bnetqaet Eth5 bnetqad Eth bretoaldlEth bnetqaet Etho bretoadLEthd bnetqadbEth bnetqadLEth bretoadbEth 0 00 1 279 72 1 279 93 1 275 64 1 279 25 of dd 0 01 1 850 72 1 551 18 1 517 68 1 518 71 pu du 0 01 1 850 86 1 551 11 1 817 58 1 518 52 0 00 1 260 49 1 280 50 1 279 41 1 279 41 0 00 1 852 06 1 352 06 1 515 93 1 818 98 0 00 1 552 04 1 352 06 1 518 96 1 518 97 3 51 221 597 14 257 940 19 251 574 22 251 794 22 10S 372 966 72 373 058 00 366 301 72 366 504 19 ERIE 372 905 47 373 047
24. SBC for up to seven days Statistical data is automatically calculated at well defined time intervals throughout the day To generate and view a report you can define the time intervals to be either five minute intervals or one hour intervals for the BorderNet 4000 SBC activity You can export the reports to Adobe PDF Microsoft Word or Microsoft Excel format from the WebUI The BorderNet 4000 automatically generates the following data e Ethernet and CPU usage statistics e QoS statistics including incoming and outgoing session statistics on the following o SIP and H 323 peers o SIP and H 323 interfaces o System wide e Packet statistics including the number of packets dropped because of various security checks Ethernet and CPU Packet Statistics Total Receive Transmit packets and bytes Receive Transmit errors Total Inbound Sessions Total Inbound Sessions Rejected due to constraints violation or Insufficient Bandwidth Highest Concurrent Inbound Sessions Total Outbound Sessions Total Outbound Sessions Rejected due to constraints violation or Insufficient Bandwidth Signaling packets received Packets dropped by security checks CPU min max and average usage Highest Concurrent Outbound Sessions Peak Rate of Inbound Outbound Traffic Average Rate of Inbound Outbound traffic Total Attempts Seizures Total Answered Sessions Answer to Seizure Ratio Percentage Media packets received
25. arable Logging Enabled Generate SNMP Trap Generate Email Interface Creation Failed Diagnostics Pending alarms are outstanding alarms that are currently reported on the BorderNet 4000 SBC that have not been cleared Alarm history shows cleared alarms Follow the steps below to report the pending alarms 1 3 Change the reporting criteria from the screen below Pending Alarm Summary d 3 Network Network Time 2011 10 12408 29 58 201 1 10 12 06 39 56 201 1 10 12 08 29 56 201 1 10 12 06 39 56 2011 10 12406 39 56 2011 10 12 08 28 56 2011 10 12 08 39 56 Name Physical Interface Failed Physical Interface Failed Physical Interface Failed Physical Interface Failed Physical Interface Failed Physical Interface Failed Physical Interface Failed From the Diagnostics menu select Pending under the Alarms section Reported FDN Platformewalnut Interface Eth3 Platform wainut Interface Eth Platform walnut Interface Eth10 Platform wainut Interface Eth7 Pistform wainut Interface Etht 1 Pistform wainut Interface Eth8 Ptatform wainut Interface Eth5 4 ici mi is Content Eth3 Physical interface has failed Eth6 Physical interface has failed Eth10 Physical interface has failed Eth Physical interface has failed Eth Physical interface has failed Eth8 Physical interface has failed Eth5 Physical interface has failed 201 1 10 12 06 39 56 201 1 1
26. ate Sessions Media ID a 13 220 576 290 576 290 576 I a i 2007 3 399 113 322 713 399 713 ZU Jgu 2 399 580 399 079 399 079 IJn 399 679 399 679 399 680 OMe 3 399 079 399 878 399 679 IOn 399 679 399 079 399 079 ID MM 2 399 079 399 079 399 079 FORA 399 680 399 079 399 079 ID 2 399 078 399 680 99 679 TO ERA 399 079 399 079 399 078 24 Statistical Reports Reporting Outgoing Sessions 1 From the Diagnostics menu select Outgoing Sessions under System Statistics Report Filter System StatsOutgoing Report Interval Hourly Date f Five Minutes Start Date End Date 2 Select whether you want to report the System Statistics hourly or five minute intervals 3 Select the Start Date and End Date of the period that you want to report System Statistics 4 Click OK and the following appears System Statistics Outcome Hourly Em E 4 4 pagetof2 P M Sessions Sessions Sessions Sessions Highest Active Answered Rejected Average Rate Peak Rate Sessions Start Hour IU Jga W 2 00 00 290 576 290 576 Ioen 399 713 399 713 Ira 2072 399 572 399 572 IOa 399 020 399 020 Ioen 399 572 399 572 I Jga M 2 392 572 399 070 T kJga M 2 392 572 399 078 I kJga 2M 2 392 572 392 680 IOa 399 070 399 572 I jga A 2 399 579 399 579 25 Dialogic BorderNet 4000 SBC Maintenance and Troubleshooting Guide Tracing The BorderNet 4000 SBC supports Wireshark remote trac
27. d e High greater than 25 percent being dropped 36 Real Time Status and Performance License Capacity indicates the number of sessions licensed When the number of concurrent sessions in the system exceed 80 of license capacity this number turns to Orange When the threshold increases beyond 90 the License Capacity turns red System Performance The Management System reports real time performance information for the active platform at the system level e Total Sessions Signaling and Media e Incoming Session Rate e System Bandwidth Consumption for Media System Performance Signaling Media Bandwidth mbps Total Sessions 1 Rx Media 0 Sessions sec 5 TxMedia 0 Total Sessions Signaling represents the count of all the calls which are attempted not necessarily answered Total Sessions Media represents all answered calls for which the BorderNet 4000 SBC does media interception Sessions sec is the number of new incoming session attempts per second across all session interfaces Media Bandwidth in Mbps indicates system level media bandwidth utilization transmit and receive across all session interfaces For example on a system with 4 GigE interfaces in Full Duplex mode Rx and Tx can each show values closer to 4096 Mbps However signaling packets and other dropped packets are not considered for this usage representation As stated it is representative of RTP stream only 37 Dialogic BorderNet 4000 SBC
28. d to implement any concepts or applications and does not condone or encourage any intellectual property infringement and disclaims any responsibility related thereto These intellectual property licenses may differ from country to country and it is the responsibility of those who develop the concepts or applications to be aware of and comply with different national license requirements Dialogic Dialogic Pro Dialogic Blue Veraz Brooktrout Diva Diva ISDN Making Innovation Thrive Video is the New Voice VisionVideo Diastar Cantata TruFax SwitchKit SnowShore Eicon Eiconcard NMS Communications NMS stylized SIPcontrol Exnet EXS Vision PowerMedia PacketMedia BorderNet inCloud9 I Gate ControlSwitch NaturalAccess NaturalCallControl NaturalConference NaturalFax and Shiva among others as well as related logos are either registered trademarks or trademarks of Dialogic Inc and its affiliates or subsidiaries Dialogic s trademarks may be used publicly only with permission from Dialogic Such permission may only be granted by Dialogic s legal department at 9800 Cavendish Blvd 5th Floor Montreal Quebec Canada H4M 2V9 Any authorized use of Dialogic s trademarks will be subject to full respect of the trademark guidelines published by Dialogic from time to time and any use of Dialogic s trademarks requires proper acknowledgement The names of actual companies and products mentioned herein are the trademarks of their respective
29. e pistachio Release Select Select BN4000 1 0 0 015 2 Select the software release and click Upgrade 43 Dialogic BorderNet 4000 SBC Maintenance and Troubleshooting Guide Rolling Back Software Follow the steps below to roll back the software to a previous release 1 From the Software menu select Rollback Software Rollback Platform Hame bnetqad Select Version Rollback 2 Select the software version to roll back to and click Rollback Restoring and Backing Up Configuration Data Backing up software differs on a standalone system and an HA system as follows e Ona standalone system when you back up the configuration data the provisioning process is shut down It is started up once the backup is completed e Onan HA system configuration data backup is taken on a standby platform and is also transferred to the active platform automatically Follow the steps below to back up and restore configuration data 1 From the Software menu select Backup amp Restore under Data Management The follow screen appears Configuration Data Management Start Backup Upload Backup List of Data Backup Available Bh4000 1 0 0 0183 2011 11 23 00 15 52 BM4000 1 0 0 079a 2011 11 23 00 16 17 BNA4O000 1 0 0 018d 2011 11 23 00 25 23 Bh4000 1 0 0 020 2011 11 22 17 21 51 BN4000 1 0 0 020a 204 1 11 22 17 21 34 BM4000 1 0 0 020a 201 1 11 22 1 7 21 51 BN4000 1 0 0 020d 2011 11 22 1 7 23 26 re x ie
30. e Upload Backup button to upload the configuration data backup file from the local machine to the BorderNet 4000 application platform 45 Dialogic BorderNet 4000 SBC Maintenance and Troubleshooting Guide Audit Logs The Audit Logging functionality audits every data change happening in the system and writes the information into an audit record file The system maintains the file for one year The following audit records are recorded into the file Time Date time N Date Time in seconds when the audit trail is generated Username String N Name of the user who requested the change Device String IP address or device name from where WebUI was accessed Event String DL QA CREATE UPDATE DELETE Lo MEN String Name of the resource filename that was modified Note You must have Security Auditor privileges to view the audit records 46 Viewing Audit Logs 1 From the System menu select Audit Logs under Administration Audit Logs Audit Logs e m a Time 2012 03 06 15 05 03 SECMANAGER Lage ay 2012 03 06 03 41 26 2012 03 06 03 14 33 2012 03 06 02 41 37 SBCMANAGER Resource Result LoginStatuses xml Success LoginStatuses xml SYSMANAGER Success LoginStatuses xml Success SBCMANAGER e wy 2012 03 06 02 35 24 2012 03 06 01 25 06 SBCMANAGER SYSMANAGER NpSysServicesCfg 7 xml
31. eceived more than Troubleshooting Interface the configured packet rate Bandwidth Overload Critical Bandwidth at the network Verify from reports if Exceeded at interface level is there are peers that are Network exhausted as computed generating more traffic Interface from the session capacity than they should and if configurations are accurate Traffic generating peers on the network interface level can be reconfigured or locked to avoid traffic Session License Limit Reached Overload Critical The number of concurrent sessions reached the licensed limit CPU Utilization Overload Major The CPU usage crossed a Reached Minor predefined threshold The Overload Level Critical severity changes based on the threshold crossed CPU Utilization Overload This alarm is raised if CPU Reached Overload Level Minor Maj or Critical usage crosses a predefined threshold The severity changes based on the threshold crossed License Critical Indicates either that the Verify the License trial production license Contents on WebUI and has expired purchase an updated new license License Critical Indicates either that the Verify the License trial production expiry is Contents on WebUI and nearing 15 days prior purchase an updated new license Critical Raised when the platform Check the connectivity deployed in HA between the paired configuration detects platforms of the HA communication failure configuratio
32. et Rate At Interface Connectivity Failure with Peer Packet Rate Limit Exceeded at Peer Packet Rate Limit Q Exceeded at 54 Qos QoS QoS QoS QoS QoS oS Major Major Minor Minor Major Minor Minor The rate of rejection for the incoming calls exceeded 10 of the maximum incoming rate at the Interface A peer received more than the configured packet rate An interface receives more than the configured Packet rate A configured peer fails to respond to OPTIONS sent by the system Indicative alarm Peer received more than the configured packet rate Verify the Security Profile and Reports Check the security profile Verify the Security Profile and Reports Check the security profile Verify the Security Profile and Reports Verify with Security Profile and Reports If calls can be sent over that peer regardless then turn off connectivity for that peer If the peer is supposed to respond verify that if there are routes to the peer Also see if routes to that peer need to determined Verify that what is configured from WebUI has made it properly to the internal components by another debug mechanism See if there are any configuration errors if any See if there are internal configuration errors by intrusive debugging into the platform such as debug access on process and logs No corrective action Indicative alarm No corrective action Peer r
33. formation There can be a maximum of five versions installed on the platform Follow the step below to display software information 1 From the Software menu select About For standalone deployments the following screen appears Software Information Deployment Type Standalone Active Platform Software Information Hostname bnetqad Designated Role Primary Active Version BM4000 1 0 0 025 Other versions installed BM4000 1 0 0 024c BH4000 1 0 0 024d er14000 1 0 0 024e er14000 1 0 0 024f Updates available none For HA systems the following screen appears 41 Dialogic BorderNet 4000 SBC Maintenance and Troubleshooting Guide Software Information Deployment Type HA Active Platform Software Information Hostname pistachio Designated Role Secondary Active Version BN4000 1 0 0 020a Other versions installed BN4000 1 0 0 019d BN4000 1 0 0 020 Updates available none Standby Platform Software Information Hostname hazelnut Designated Role Primary Active Version BN4000 1 0 0 020a Other versions installed BMN4000 1 0 0 019a BN4000 1 0 0 020 Updates available none Uploading a New Software Release You can upload a new release to the system In an HA deployment the software upload is done only once and it is synched automatically to the standby platform Uploaded software releases are cleaned up automatically Only the last three releases are kept on the system Follow the s
34. he Gatekeeper Peer Check both the physical interfaces for the given Ethernet link and ensure they are properly connected to the switch If the problem persist check the cables and the Ethernet properties such as speed duplex auto negotiation is configured Same on both ends of the Ethernet link Check the physical interfaces and ensure they are properly connected to the switch If the problem persist check the cables and the Ethernet link properties such as speed duplex auto negotiation is configured same on both ends of the Ethernet link Check the interface configuration on the WebUI Turn off and Turn on the configuration Remove Associations Clone and delete old rename the clone to the previous one source On the interface screen sort on the IP and ensure the same IP and port does not exist Restart IBCF service Check the accuracy of the Gatekeeper information on the 49 Dialogic BorderNet 4000 SBC Maintenance and Troubleshooting Guide Configuration Configuration Data Validation Failure Minor Configuration Link Disabled Configuration Data Validation Failure Configuration Ethernet Link Administratively Disabled Configuration IP Address Configuration Failure Configuration 50 When the platform becomes active from standby the configuration data is validated If the validation fails then this alarm is raised Raised when the Ethernet
35. he power supply that is detected as failed and the cause of the failure Is the power supply is not present or not connected Hardware Major The Fan speed sensors Check the platform fan detect that the fan failed or operating below configured fan speed thresholds indicating potential mechanical failures Hardware Major The platform chassis inlet Check the system temperature is detected hardware fan and to be going above critical operating environment or non recoverable conditions and take thresholds adequate steps to provide proper system cooling Hardware Major The system detected the Check hard disks on the RAID degraded possibly platform that is showing due to HDD failure The RAID degraded Platform Memory Size not As Expected Power Supply Failed Fan Speed Sensor Reached Threshold Temperature Sensor Reached Threshold RAID Device Degraded SDR File Transport Failure 56 alarm details indicate which of the two HDD failed Critical The SDR file transport to Ensure that the SDR the billing server failed destination IP Address and directory name are Troubleshooting both correct Make sure the network is working properly and the destination host has enough disk space Unsent SDR Files Critical SDR files are not sent Change the TCP Accumulated promptly parameters to increase the speed Also if SDR files are not compressed you can change the setting to compress them 57
36. ics under System Statistics Report Filter System StatsPackets Report Interval e Date Hourly Five Minutes start Date End Date 2072 07 16 2 Select whether you want to report the System Statistics hourly or five minute intervals 3 Select the Start Date and End Date of the period that you want to report System Statistics 4 Click OK and the following appears System Statistics Summary Hourly Signaling Media In Thousands Rate No Accept Packets Packets Rate Dropped ae ACL ae Dropped Exceeded Black List No Pinhole 27 Feb 2072 0000 27 Feb 2012 27 Feb 2012 27 Feb 2012 27 Feb 2012 27 Feb 2012 27 Feb 2012 27 Feb 2012 27 Feb 2012 114 110 23 Dialogic BorderNet 4000 SBC Maintenance and Troubleshooting Guide Reporting Incoming Statistics 1 From the Diagnostics menu select Incoming Sessions under System Statistics Report Filter System Statsincoming Report Interval f Hourly Date f Five Minutes Start Date End Date 2 Select whether you want to report the System Statistics hourly or five minute intervals 3 Select the Start Date and End Date of the period that you want to report System Statistics 4 Click OK and the following appears system Statistics Incoming Hourly Em H 4 pagliotta P M Dropped Answer to Messager Seizure Rabo Malformed 55 Sessions Sessions Sessions Sessions Highest Active Attempts with Answered Rejected Averare Rate Peak R
37. ing The BorderNet 4000 SBC enhances the remote trace functionality of Wireshark with a custom wpcap dll The custom plug in supports additional message based filters along with the existing IP level filters All messages that match the filter are streamed to Wireshark client in pcap format Note The Wireshark application is not included with the BorderNet 4000 SBC See the link on the screen below to download the application from wireshark org Once you have downloaded Wireshark and installed it you can download the plug in also from the screen below Wireshark uses remote tracing to capture the trace messages You can also store the messages By default the BorderNet 4000 SBC streams to the Wireshark client The custom plug in allows profile based traces and interface traces Downloading the Trace Plug in Follow the steps to download the Trace Plug in 1 From the Diagnostics menu select Plugin under the Trace section 2 Follow the instructions from screen below Download Page for BorderNet 4000 Trace This page will allow you to download and install BorderNet 4000 Trace plug in BorderNet 4000 allows tracing using Wireshark a popular network protocol analyzer You need to download Wireshark from here and install it on your client platform before downloading and installing this plug in Minimum version of Wireshark must be 1 6 System Requirements Steps to download and install Wireshark plug in Wireshark plug in supports the foll
38. inks Screen The operator provided a configuration of the IP Address IP Route etc that was rejected by the underlying OS layer This may happen when the given configuration is either not valid or already exists or conflicts with another configuration on the platform Troubleshooting IP Route Configuration Minor Configuration Failure VLAN Configuration Critical Configuration Failure alarm details contains the information for the object type for example VLAN IP and IPROUTE and the object identified for example Id or the Name of the object that failed to get configuration on the platform The received configuration failed to get configured applied on the BorderNet 4000 SBC platform The following are the configuration failure examples that could result in this alarm IPROUTE configuration failure The FDN and additional alarm details contains the information for the object type for example VLAN IP and IPROUTE and the object identified for example Id or the Name of the object that failed to get configuration on the platform The received configuration fails to get configured and applied on the BorderNet 4000 platform VLAN addition deletion is a configuration failure that could result in this alarm The FDN and additional The additional detail string in the alarm usually provides the error not received from the operating system which can be used to further debug the i
39. interface has failed Eth9 Physical interface has failed Failure in Ethernet Link on interface Sess 11 Dialogic BorderNet 4000 SBC Maintenance and Troubleshooting Guide alarmFilter Xx Severity Critical Major Minor Category M spR session Qos Peer License Configuration Security HA Overload Network Hardware System Date YYYY MM DD and Time HH24 MIESS SatDae End Date o Reported Type FDN NNNM 4 Select All in the Show field 5 You can change the severity or category of the alarm 6 Click OK 12 Diagnostics Reporting Alarm History Follow the steps below to report the history of alarms on the BorderNet 4000 SBC 1 From the Diagnostics menu select History under the Alarms section Alarm History Severity Category Time Name Reported Type Reported FDN Network 2012 07 09 17 47 21 Physical Ethernet Interface Faile Interface Platform walnut Interface Eth3 Physical ethernet interface E Raise Raise Configuration 2012 07 09 17 47 21 Configuration Data Validation F Configuration Data Platform walnut ObjectType Tir Constructing add XML for Ti Configuration 2012 07 09 17 47 21 Configuration Data Validation Fz Configuration Data Platform walnut ObjectType SE Constructing add XML for S Raise Configuration 2012 07 09 17 47 21 Configuration Data Validation Fz Configuration Data Platform walnut ObjectType Pc Constructing add XML for Pa Raise
40. mote Port Application Action Management Management Management Management Management Management SIP SIP SIP SIP SIP SIP SIP SIP Configured By User User User User System System System System System System System System System System Local IP Local Port 10 3 1 164 10 3 1 174 10 3 1 164 10 3 1 164 10 3 1 164 10 3 1 164 10 134 164 10 13 3 164 10 13 1 164 10 13 2 164 10 13 4 164 10 13 3 164 10 13 1 164 10 13 2 164 Reporting IP Route Status 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 10 3 1 0 10 3 1 0 10 13 4 180 10 13 3 180 10 131 180 10 13 2 180 10 13 4 181 10 13 3 181 10 13 1 181 10 13 2 181 on O fon o fen O fon O Ref o fo e hoy Oo From the Diagnostics menu select IP Route Status under System Status IPRoute Status Filter Include System Routes iai Yes O Ma 2 Select whether to report system routes or not Routes that are automatically added by the System for example when VLAN Access IP addresses are configured on the System are referred to as system added routes This option allows you to see the routing table entries as they exists on the system Routes that are explicitly provisioned by the operator are referred as non system routes 3 Click OK IP Route Status Summary Destination IP Address Subnet Mask Gateway IP Address Interface 10 55 10 22 10 55 10 21 10 50 10 0 10 5 200 0 10 53 21 0 10 55 20 0 10 4 3 0 10 53 23 0 10 7 26 0 10 5 20 0
41. mum incoming limit allowed at the interface The rate of rejection for the outgoing calls exceeded 10 of the maximum outgoing rate at the peer The rate of rejection for the outgoing calls exceeds 10 of the maximum outgoing rate Troubleshooting and cipher suites configured on the TLS profile for the interface used to connect to this peer Verify the certificates and cipher suites configured on the TLS profile for the interface used to connect to this peer Verify the Security Profile and Reports Check the security profile Verify the Security Profile and Reports Check the security profile Verify the Security Profile and Reports Check the security profile Verify the Security Profile and Reports Check the security profile Verify the Security Profile and Reports Check the security profile Verify the Security Profile and Reports Check the security profile Verify the Security Profile and Reports Check the security profile Verify the Security Profile and Reports Check the security profile 53 Dialogic BorderNet 4000 SBC Maintenance and Troubleshooting Guide Severity Maximum The rate of rejection for the incoming calls exceeded 10 of the maximum incoming rate at the peer Incoming Sessions Rate Reached on Peer Maximum Incoming Sessions Rate Reached on Interface High Packet Rate At Peer High Pack
42. n Also verify with paired platform the paired platform with which the communication failure is reported is up and running BorderNet 4000 SBC software Major This alarm is This alarm is informational to the informational to the operator when the operator to indicate platform failed over and platform failover and its the fault failure or the reason operation that resulted in this failover action 55 License Expired License Nearing Expiry Lost Communication with Peer Platform Platform Failover Dialogic BorderNet 4000 SBC Maintenance and Troubleshooting Guide Critical System Critical The system detects the The operator should failure of some critical review the available system component in the diagnostics to platform that affects the understand what system functionality component failed and Ire sure Ss the reason If the issue detected on the platform persists seal that is serving the ACTIVE Ser eta tui ea ear role the system may g decide to failover to the paired platform if one is available The system continues to provide the desired functionality Component Failed Hardware Major The BorderNet 4000 SBC Replace the bad memory system checks for the card s available physical memory on the platform during powerup checks If memory is not as expected the system raises this alarm Hardware Indicates a power supply Check the power supply failure on the platform The Alarm detail identifies t
43. nd or and not SignalingWithMedia Message based capture filters For example CallingPartyUserName CalledPartyDomainName IncomingInterface IncomingPeer Multiple Call trace Criteria can be combined using a logical operator and SignalingNoMedia Message based capture filters For example CallingPartyUserName CalledPartyDomainName IncomingInterface IncomingPeer Multiple Call trace Criteria can be combined using a logical operator and MeidaDropped FlowsDropped No Filter required All the dropped packets are captured even if a filter is specified 28 Tracing Recording Profiles Recording profiles help to trace sessions based on Message specific filter criteria Each profile has a specific type of message to trace SignalingNoMedia This profile will trace all the signaling messages which match the message specific capture filter SignalingWithMedia This profile will trace all the signaling messages and RTP media which match the message specific capture filter MediaDropped This profile will trace all the Media packets that are dropped in the kernel It does not require a filter MediaDropped This profile will trace all the non Media packets traffic that is dropped in the kernel It does not require a filter Message Based Capture Filters The custom Wireshark plug in supports message based capture filters The following message based capture filters are supported CallingPartyUse
44. nnns 18 Reporting Outgoing SESSIONS serrera ta na i a aa aia a at 19 Era e Sta OS nao 20 Reporting SUMMA ssctccceasicaacewcutosdeasecnreimentcsdeasecantancetenaeatesandearnicnaesdeemeeads 20 Reporting INCOMING SESSIONS waisted at aaa a usa nec ati ta a ls a a a a 21 Reporting Outgoing Sessions AP Sia nb nt Dale iai M DM 22 System SLauiSUi sm OO E EEC danii n dada id daia d dana d 23 Reporting Packet Statistics imss 23 R porting Incoming StatisStiCS escritor n Eton a nl ds 24 Reporting Outgoing SCSSIONS is cccsccasccacsscrenatetetciadasendacssceiadetasersinseeescsasaqenenae 25 WAI aia 26 Downloading the Trace PIO Mrs 26 Connecting to the BorderNet 4000 SBC from Wireshark cccceeeeeeeeeeeeeeeeeeeeeees 27 Recording Profiles iii ceace nina ic tac a aim a i e 0 ac a dei oa na d aan a la 29 Message Based Capture FNte Sisa 29 Interface based capture filters eee 30 ie AP ia pi inte ai oo O aa ata ap AA 31 Meta Capture rra eat t i Sat toot vans 31 System Salles 32 Reporting ACL SLACUS orei atei ana ere aa ina azot sar iaca er pad a 32 Reporting AP ROULE SEUL Sean acota aia Ana d aula N 33 Real Time Status and Performance si suta uta mata ta otita otita aliata a arata 34 i OI TS ia au nat On aa ia e a ada n ia a a ata 34 Da ADOT oaie ea toiag ornat iai aa ca un d la ina a a ice ial a ca 34 MELO e APPS E e ft REO Eo i ot ai e a nl 35 CPU MGS iu n na a ani pati ta m 36 S
45. ntroduction Refer to www dialogic com for product updates and for information about support policies warranty information and service offerings Dialogic BorderNet 4000 SBC Maintenance and Troubleshooting Guide About this Publication The Dialogic BorderNet 4000 SBC Maintenance and Troubleshooting Guide provides the information that you need to operate the Dialogic BorderNet 4000 SBC after it is installed deployed and configured The Dialogic BorderNet 4000 SBC is also referred to herein as the BorderNet 4000 SBC and or the BorderNet 4000 Related Documentation e Dialogic BorderNet 4000 SBC Product Description e Dialogic BorderNet 4000 SBC Installation and Deployment Guide e Dialogic BorderNet 4000 SBC Configuration Guide e Dialogic BorderNet 4000 SBC Regulatory Notice e Dialogic BorderNet 4000 SBC Field Replaceable Unit documents o Replacing a Fan Assembly o Replacing the Air Filter o Replacing a Power Supply Overview Overview The BorderNet 4000 SBC contains a WebUI which includes the following two modules that allow you to maintain your system e Diagnostics e Software Management The Monitor and Diagnostics module enables the following e Alarms e Statistical Reports e System Performance e Tracing e System Status The Software Management module enables the following e Upgrading software e Uploading new releases of software Dialogic BorderNet 4000 SBC
46. owing configurations Click on the download link below and save the file wpcap dilto your local files system Platform WireShark version When download finishes copy wpcap dll to Windows 98 NT 2000 XP 12003 1 6 or higher cwindowsisystem32 directory NM For Windows 7 64 bit copy vvpcap dll to Windows 1 6 or higher 32 bit version L ELSE i 4d d E clwindows sysvYOVV64 directory If the file already exists overwrite it with downloaded file Caution If you have previously downloaded another plug in named wpcap dll for a different device do not overwrite it Rename it before downloading this wpcap dll 26 Tracing Connecting to the BorderNet 4000 SBC from Wireshark Follow the steps below to connect to the BorderNet 4000 SBC from Wireshark 1 Select Options from the Capture menu The Wireshark Network Analyzer apa 240 4 08xX 0 ans Interface List Open Fs Website Liwe st of the capture interfaces counts incoming packet Open a prawko captured file Visit the project s webi ia Srart capture on interface M BOHMMxXOU2 Dell Wireless 1510 Wireless N WLAN ER cp scena Check Point Virtual Network Adapter C Documents and Settings dmurthy host 10 3 1 165 8899 Bytes it dslicAdpt 19 Juniper Network Connect Virtual Ad CiMbempl Trinity best on 25 06 1 201 1 ppm 447 kB di Security pe elyexpress10 Intel R 825670M Gigabit Network Werk with Werezhark at securely a poz
47. products are not intended for use in certain safety affecting situations Please see http www dialogic com company terms of use aspx for more details Due to differing national regulations and approval requirements certain Dialogic products may be suitable for use only in specific countries and thus may not function properly in other countries You are responsible for ensuring that your use of such products occurs only in the countries where such use is suitable For information on specific products contact Dialogic Inc at the address indicated below or on the web at www dialogic com It is possible that the use or implementation of any one of the concepts applications or ideas described in this document in marketing collateral produced by or on web pages maintained by Dialogic may infringe one or more patents or other intellectual property rights owned by third parties Dialogic does not provide any intellectual property licenses with the sale of Dialogic products other than a license to use such product in accordance with intellectual property owned or validly licensed by Dialogic and no such licenses are provided except pursuant to a signed agreement with Dialogic More detailed information about such intellectual property is available from Dialogic s legal department at 9800 Cavendish Blvd 5th Floor Montreal Quebec Canada H4M 2V9 Dialogic encourages all users of its products to procure all necessary intellectual property licenses require
48. rPart CallingPartyDomain CallingPartyURIScheme CallingPartyNumber CalledPartyUserPart CalledPartyDomain CalledPartyURIScheme DialedNumber IncomingInterface IncomingPeer Three operators are supported for matching the filters BeginsWith for example CalledPartyUserName 408 This filter will trace all the sessions whose CalledPartyUserName begins with 408 EndsWith for example CalledPartyUserName 9000 This filter will trace all the sessions whose CalledPartyUserName ends with 900 IsEqualTo for example CalledPartyUserName 4087509000 This filter will trace all the sessions whose CalledPartyUserName equals 4087509000 The operators can be used with all the message based capture filters To narrow down the traces further any capture filters can be combined using a logical and operation 29 Dialogic BorderNet 4000 SBC Maintenance and Troubleshooting Guide For example CalledPartyUserName 408 and IncomingInterface SIPIntf1 This will capture all the messages that arrive on SIPInterface SIPIntf1 and whose CalledPartyUserName begins with 408 Note Message Based Capture filters are case sensitive The filter should exactly match the specified syntax with case Interface based capture filters Interface based capture filters are used with the session options Though Wireshark Supports several interface based capture filters only the following capture filters are qualified with the BorderNet 4000 SBC e IP e T
49. ssues with the configuration data The operator should check and correct remove the invalid configuration data from the invalid configuration data from the provisioning system and manually clear the alarm The operator provided a configuration of IP Address IP Route etc that was rejected by the underlying OS layer This may happen when the given configuration is either not valid or already exists or conflicts with another configuration on the platform The additional detail string in the alarm usually provides the error not received from the operating system which can be used to further debug the issues with the configuration data The operator should check and correct remove the invalid configuration data from the provisioning system and manually clear the alarm The operator provided a configuration of VLAN that was rejected by the underlying OS layer This may happen when the given configuration is either not valid or already exists or conflicts with other configuration on the platform The additional detail string in the alarm 51 Dialogic BorderNet 4000 SBC Maintenance and Troubleshooting Guide Session Data Record Disabled in Configuration Peer Blacklisted Due to Packet Rate Peer Blacklisted Due to Exceeded Session Rate or Malformed Messages Excessive Packet Drops 52 Configuration Security Minor alarm details contains the information for the object type
50. teps below to upload a new software release 1 From the Software menu select Upload New Release The following screen appears Upload Software 2 Click Browse to select the file for upload 3 Click Upload to upload the software 42 Software Management Upgrading Software The following applies to upgrading software e Ina standalone deployment you must upgrade software during a maintenance window because it affects traffic e All application processes are shutdown during the upgrade process e Application services are started as soon as the upgrade is completed e In an HA deployment the upgrade is allowed only on the standby platform e The following operations should be done for HA deployment upgrade o Upgrade current standby platform o Failover o Upgrade current standby platform Follow the steps below to upgrade the current software version 1 From the Software menu select Upgrade In a standalone deployment the following screen appears Upgrade Software Note This is Standalone deployment upgrade process will shutdown applications on this S Select release to upgrade Platform Name almond Release Select Select BN4000 1 0 0 015 In an HA deployment the following screen appears Upgrade Software Note This is HA deployment only standby platform will be upgraded To upgrade currently active platform do failover and then upgrade the standby platform Select release to upgrade Platform Nam
51. tibda ph tapoas21 TAP Wini32 Adapter OAS pec ise User s Guide caltiniport 25 to 7 captured 547 KB Tha User Guide local version installed in Capture Options Ci Documents and Settings ydmurthylDesktoplaftab cap 7572 KB Stat capture with decided options TT gj Sample Captures XAalOOIloGo gL UnDBo e died ne eg bev to Capture Shep by step to a sucoert d capture setup di Network Media Specific inFoemation for capturing ona Ethernet VILAM a 2 Select Remote from the Interface drop down box Wireshark Capture Options Capture Interface Local e cp scena Check Point Virtual Network Adapter Microsoft 1P address e e Capture 19 3 1 164 node L Capture 1o c 2 185 pt experimental ree size 1 O mk ea 6 5 25 1855 UE Capture Fi 10 3 1 162 Captura Filet 10 6 2 77 Display Options File Clear ket v Update list of packets in real time megsbyte s use prultiple files v Automatic scrolling in bve capture v Hide capture info dialog v Enable MAC name resolution Enable network name resolution v Enable transport name resolution 3 Enter he management IP address of the BorderNet 4000 system for the Host The port number for the Port is 2010 27 Dialogic BorderNet 4000 SBC Maintenance and Troubleshooting Guide Note The host IP address from which the trace request is triggered must be entered in the ACL without which the trace req
52. torage and Temperature eeeeecesseeeehnnnnnnnnhnnmee ahhh aha aa nnn nans 36 Alarm Severity Packet Drop License Capacity eee eee eee 36 System Peron ma CS sima oia ia a ul oia 37 zie A een OO o E pl la ap aa al d 38 SESSION VIN ZAC pasota a a ta a a a tal ma ta e ta 39 Reporting CPU UCI VIZE CO II canas 39 Dialogic BorderNet 4000 SBC Maintenance and Troubleshooting Guide Software Management 41 Displaying Software Information aria aa 41 Uploading a New Software ReleaSe ccccseeeeeeeeeeeeeeeseeccennennneneneeesesssseeeaaaaes 42 Upgrading SOW AC vis vacate etre saad AAA 43 ROING Back SOPEWel Sir SAS na EL afe tei eae DE 44 Restoring and Backing Up Configuration Data sseeseeeeeeeenen nnn 44 Starting the Backups estie tio e FERE edo inam das rag rado Caesa laa tace Dead vaa taa taa 45 FRESCO UNG Ine Ba CICUD uesdsecnvetbu iati deno loans Gea talis Coto te aa aa 45 Downloading the Batista tarani act a uta e Oates ARA 45 Deletina THE Backups dades ioana onn ra ca Rats itd nora iced nece te Bes iub nest t 45 Uploading the BaeKkulbasscewikise me Dv Rel Era at Ro t racc RS Rr er d re b 45 Audit LOIS AA KE FREE VI EU VEN ENS 46 MAizsnePiuelNEoscc c 47 Troubleshooting nr 49 Alar MS DEED C D TTD D DIEITUR 49 Revision History Revision Release date Notes 64 0549 03 September 2012 Release 2 1 64 0549 02 July 2012 Release 2 0 64 0549 01 March 2012 Controlled I
53. uests coming into the BorderNet 4000 will be dropped This is a security feature Also remote tracing as a service should be enabled on the BorderNet 4000 SBC See the Dialogic BorderNet 4000 SBC Configuration and Provisioning Guide for instructions on how to create ACL entries Select Password authentication 5 Enter the Username and Password The user must have the tracing role assigned Without it the trace requests cannot be initiated See the Dialogic BorderNet 4000 SBC Configuration and Provisioning Guide 6 Click OK If the connection is successful the system shows the following capture options including session interfaces and recording profiles Session Interface e SessionIf1 e SessionIf2 e SessionIf3 e SessionIf4 Recording Profiles e SignalingNoMedia e SignalingWithMedia e MediaDropped e FlowsDropped 8 To start a trace request choose from one of the options above Based on the option selected you can either enter an interface level capture filter or a message level capture filter to narrow down the trace criteria The list below gives the valid combinations of options and filter criteria that are supported Option Supported capture filters SessionIf1 SessionIf4 All IP based capture filters are supported These are default Wireshark capture filters For example IP host port TCP UDP A combination of these filters are also supported using the logical operators a
54. urrent processing rate in calls per second e Status and usage level at each network interface Follow the step below to display the dashboard 1 Click Dashboard from the WebUI 2 The following screen appears 34 Real Time Status and Performance EH Mu o Primary Welcome SBCMANAGER Logout Dialogic BorderNet 4000 SBC a Om EX Pp February 28 2012 08 21 34 PM UTC Storage 9 Temperature e sa System Performance Alarm Severity A Signaling Bandwidth mbps Packet Drop None Total Sessions 4655 Rx Media 0 License Capacity 32000 Sessions sec 199 Tx Media 0 Primary Secondary Platform Session Link Utilization 0 Eth11 Eth7 Wl Eth10 Eth6 Eth9 Eth5 BN EthS Eth4 HD1i e FAN 1 FAN 2 FAN 3 FAN 4 e HD 0 Memory The Memory utilization dial on the dashboard gives the percentage of total memory allocated to the application Memory is statically allocated in BorderNet 4000 which means that application memory consumption does not increase drastically as an increasing number of calls flow through the BorderNet 4000 SBC Similarly there is memory allocation even when the system is not having any traffic flow When utilization goes beyond 90 percent or if the utilization is varying in real time then operator would need to run other diagnostics to find out the cause 35 Dialogic
55. ved from the blacklist after the timeout otherwise the dynamic blacklisting can be re configured Verify the System Statistics This is an indicative alarm and no correction required TLS Connectivity Security The TLS handshake with Verify the certificates to Un Configured the remote unconfigured o LLL o TLS Connectivity to Configured Peer Failed Maximum Active Sessions reached on Peer Maximum Active Sessions reached on Interface Maximum Outgoing Active Sessions Reached on Peer Maximum Outgoing Active Sessions reached on Interface Maximum Incoming Active Sessions Reached on Peer Maximum Incoming Active Sessions Reached on Interface Maximum Outgoing Session Rate Reached on Peer Maximum Outgoing Session Rate reached on Interface The TLS handshake with the remote configured peer fails Calls were rejected at the Peer due to exceeding the configured Max Active Sessions at the Peer in the security profile Calls were rejected at the Interface due to exceeding the configured Max Active Sessions at the Interface in the security profile The outgoing sessions at a peer exceeded the maximum outgoing limit allowed at the peer The outgoing sessions at an interface exceeded the maximum outgoing limit allowed at the interface Incoming sessions at a peer exceeded the maximum incoming limit allowed at the peer Incoming sessions at an interface exceeded the maxi
56. x r x le x re x fe x fe x ie x BN4000 1 0 0 021 2011 11 22 17 23 26 2 This screen shows the list of configuration data backups available on the system You can do the following from this screen e Start Backup e Restore Backup e Download Backup e Delete Backup e Upload Backup 44 Software Management Starting the Backup 1 Click Start Backup to backup the configuration data 2 Click Confirm Restoring the Backup Note Restoring configuration data is a service impacting action The process for restoring configuration data differs on a standalone system and an HA system as follows e Ona standalone system when you are restoring data application services are Shutdown and started once the backup restoration is complete e Onan HA system you restore data on the standby platform and then the automatic failover happens You do not have to restore data on both platforms Note The system that you are restoring the data to has to be on the same version as what was backed up In addition the filename has to be the same as the original filename that was downloaded 1 Click I to restore the configuration data backup 2 Click Confirm Downloading the Backup 1 Click to download the configuration data to the local machine 2 Click Confirm Deleting the Backup 1 Click to delete the configuration data backup 2 Click Confirm Uploading the Backup Click th

Dialogic BorderNet 4000 SBC Maitenance and Troubleshooting Guide

Contents

Download Pdf Manuals

Related Search

Related Contents