Document status: Standard
Document issue: 01.01
Document date: August 2009
Product release: BCM 5.0
Job function: Fault and Performance
Type: Technical Publication
Language type: EN
The information in this chapter applies to both the BCM50 and the BCM450
platforms running BCM 5.0.
This section provides information about managing alarms generated by the
system and administering alarm settings.
Navigation
•BCM fault management scope (page 11)
•BCM alarms (page 12)
•Alarm administration (page 12)
•Alarm to email forwarding (page 16)
•Alarms and LEDs (page 18)
•SNMP traps manager for remote monitoring (page 18)
•Alarm configuration scope (page 19)
BCM fault management scope
You can view and manage real-time alarms generated by the BCM system.
Alarms arise from components that run on the system; these alarms indicate
faults or informational conditions that may require resolution from the system
administrator. Examples of alarm conditions include:
•a T1 circuit on the system is down
•an administrator stopped a service that runs on the BCM
You can receive alarm information through any of the following means:
•the Alarms Panel in the Business Element Manager
•the Alarm Banner in the Business Element Manager
•Simple Network Management Protocol (SNMP) traps for remote
•email notification - alarm email notification can be per alarm or based on
alarm severity
You can manage alarms and alarm information by:
•configuring alarm settings, for example, filter alarms so that only the
desired subset of alarms display in the Business Element Manager Alarms
Panel are sent as SNMP traps
•administering alarms, for example, acknowledge selected alarms and
clear the alarm log
•email notification, for example configuring settings so you receive
notification about all critical alarms
BCM alarms
Software components that run on the BCM system generate alarms related to
BCM services and applications.
Each component includes a range of alarm IDs, so each BCM alarm retains a
unique alarm ID.
Alarms and log files
The system logs all alarms that appear in the Business Element Manager
Alarms Panel in the alarms.systemlog file. This file is capped at 1 MB in size;
when the file reaches this size, the system creates a new alarms.systemlog
file. The BCM keeps the current file as well as three previous files. A new file
starts when the BCM system reboots.
You can retrieve the alarms.systemlog files (the current file and the three
previous files) from the BCM system using the Log Management task in the
Business Element Manager. You can view the files using the BCM Log
Browser. For more information, seethe BCM 5.0 Administration and Security Guide (NN40170-603).
Alarm severities
By default, all major and critical alarms are visible on the alarm set, sent as
email or SNMP traps. Most, but not all alarms are visible in the Business
Element Manager Alarm Panel. When BCM raises a Critical, Major, Minor and
Warning alarm, this is reflected in the Alarm Banner.
Alarm administration
Alarm information can be delivered to you by any of the following means:
•on the alarm banner on the bottom right corner of the Business Element
Manager
•on the alarm set
Alarms and the Alarms Panel
You can view real-time alarm information using the Alarms Panel in the
Business Element Manager. Each alarm has a unique identifier. Alarms are
displayed in the Alarms table, sorted by date and time by default, with the
newest at the top of the table. The Alarms table displays from 100 to 1000
alarms. For information about setting the number of alarms that are displayed,
see Configuring the alarm set (page 24). The Alarms table contains the
following elements:
•Time — the date and time of the alarm
•Alarm Acked — indicates whether the Business Element Manager has
acknowledged the alarm.
•Alarm ID — the unique alarm ID associated with the alarm
•Severity — the severity of the alarm (Critical, Major, Minor, Warning, and
Information)
Fault and performance management fundamentals 13
•Problem Description — a description of the alarm condition
•Component ID — the process that has generated the alarm, in a 3-part DN
format. The component ID always identifies the system as a BCM,
includes the name of the system that generated the alarm, and identifies
the component that generated the alarm. In this way, remote monitoring
stations can easily identify what type of system generated an SNMP trap
and which system generated the trap.
When you select an alarm in the table, an Alarm Details pane is displayed for
the selected alarm. The Alarm Details pane displays the following information:
•Time — the date and time of the alarm
•Problem description — a description of the alarm condition
•Problem resolution — the course of action for the alarm
You can acknowledge an alarm to indicate that you are troubleshooting an
alarm. You can specify whether to include acknowledged alarms in the Alarm
Banner so that the alarm count remains concise.For more information about
the Alarm Banner, see Alarm banner (page 14).The alarm list in the Business
Element Manager remains after BCM reboots.
You can use the Alarm Banner in the Business Element Manager to view
current alarm counts and recent alarm activity on the BCM system. The Alarm
Banner appears on the bottom-right corner of the Business Element Manager
window. The Alarm Banner is visible at all times, so you do not have to
navigate to the Alarms Panel to view alarms. If you notice a change in alarm
conditions in the Alarm Banner — for example a red spike in the Critical
category — you can navigate to the Alarms Panel to view the actual alarm.
Alarm banner
The Alarm Banner provides counts of Critical, Major, Minor, and Warning
alarms; Information alarms are not included. You can specify whether to
include acknowledged alarms in the Alarm Banner.
Each alarm severity counter has a graph, which represents a data sample of
the last 20 polling intervals. The system polls for new alarms every 30 seconds
by default. The graph has a color to indicate a data change. The colors are as
follows:
Table 1 Alarm graph colors
ColorIndicates
GreenThere are no alarms of this severity, or there are
alarms of this severity but the count has decreased
since the last polling interval.
YellowThere are alarms of this severity, but they are older
than at least one polling interval.
RedA new alarm has occurred since the last polling
interval.
If you clear the alarm log from the Business Element Manager, the alarms
displayed on the Alarm Banner are also cleared and reset to 0.
You can view critical and major alarms on a telephone set on the BCM system.
This allows a system administrator to monitor alarm activity without having a
Business Element Manager and a personal computer.
You can specify the telephone to serve as the alarm set in the Business
Element Manager. The telephone set used for alarms must have a 2-line
display and three soft keys.
The alarm set displays an alarm as follows:
XXXXX-YYYY
Where XXXXX is the alarm ID and YYYY is additional alarm information.
The following options are available when an alarm is sent to the alarm set:
•Time — indicates the date and time when the alarm occurred
•Clear — use this soft key to remove the alarm from the alarm set
Fault and performance management fundamentals 15
Attention: Clearing an alarm from the alarm set does not change the status
of alarms on the Business Element Manager or reset the LEDs on the front
panel of the unit.
Attention: When an alarm is displayed on the alarm set, it remains visible
until you clear the alarm by using a softkey on the alarm set. More recent
alarms are not be displayed until the current alarm is cleared on the alarm
set.
The following figure shows an example of an alarm on the alarm set.
You can forward alarms to email and use the email forwarding option to
•monitor alarms on the BCM
•forward alarms to a third party for the BCM support
Destinations you have provisioned to receive alarms have the following
parameters:
•variable number of TO recipients
•variable number of CC recipients
•From field
•Simple Mail Transfer Protocol (SMTP) server field that can be IP address
or hostname
•SMTP port
•option to enable Transport Layer Security (TLS)
•option to enable authentication
•user name and password for SMTP authentication
The following alarm details are included in the alarm email notification:
•title
— hostname
— alarm severity
— alarm ID
•email body
— date of alarm
— alarm ID
— alarm severity
— alarm description
— alarm resolution
Use the Test Alarm feature in the Business Element Manager to test the
settings.
If any of the destinations do not successfully receive the email, the alarms are
not retransmitted. To view the alarms, log into the Business Element Manager
or download the alarm.systemlog.
Emails are not sent under the following conditions:
•network failure between the BCM and the SMTP server
•invalid SMTP server address or SMTP port
•conditions causing the SMTP server to reject the email including wrong
TO address, wrong FROM address, or incorrect user ID and password
details
Alarm profile
An alarm profile simplifies alarm management by automatically enabling or
disabling alarms in bulk based on their severity. This can be done for each
supported alarm destination. BCM supports five profiles, as detailed in Table
2.
The BCM supports the following alarm destinations:
•Business Element Manager alarm list — viewable in the alarm panel of the
Business Element Manager
•Email — alarm is sent as an email to any provisioned destinations
Fault and performance management fundamentals 17
•SNMP — alarm is sent as a SNMP trap to any configured trap receivers
•Alarm set — alarm is sent to the BCM designated telephone set
See Table 2 for details on the alarm profile types.
To refine alarms that should be sent to a specified destination, select the
alarm profile name and the alarm destination, and then apply settings. For
more information about selecting an alarm profile, seeNotify and select an
alarm profile (page 26).
Table 2 BCM alarm profiles
ProfilesDescription
CriticalAny alarm in this category has critical alarm designation.
Critical and MajorThis category has critical and major alarm designation.
Critical, Major and MinorAny alarm in this category has critical, major or minor alarm
When an alarm condition occurs on the system, the Status LED on the front
of the BCM main unit, changes to reflect the alarm condition. In normal
operation, both LEDs are green. All alarms with a severity of Major and Critical
change the Status LED to solid red, except in the event of a Failed Startup
Profile, which is indicated by a flashing red LED.
Using the Business Element Manager, you can reset the Status LEDs on the
front pane of the BCM 5.0 to a normal state.
Attention: Once the Status LED has changed to red in response to a Critical
or Major alarm condition, it remains in the alarmed state until you reset it
using the Business Element Manager.
For information about LEDs and what they indicate, see System LEDs
reference (page 65).
SNMP traps manager for remote monitoring
You can use an SNMP trap manager to remotely monitor BCM alarms via
SNMP traps. A trap is an indication from the BCM system to configured trap
managers that an alarm has occurred in the BCM system. Any BCM alarm
can generate an SNMP trap.
If you want the BCM to send SNMP traps, you must first configure the SNMP
agent using the Business Element Manager. You must enable an SNMP agent
and then configure how the system handles SNMP trap notifications. For
information about configuring SNMP settings, see Enabling or disabling
SNMP traps for alarms (page 26).
The BCM system uses the Small Site Events Management Information Base
(MIB) for alarms. The trap format is specified in this MIB. You capture and view
traps using any standard SNMP fault monitoring framework or trap watcher.
By default, the BCM sends SNMP traps for alarms with a severity of Major and
Critical. You can change the default alarms that are set for SNMP to limit the
volume and type of SNMP information, and to control essential information
that is transferred on the network. For information about how to change the
default alarms, see Configuring the alarm set (page 24).
Although the BCM system provides a default mapping of alarms that are
displayed in the Alarms table and that are sent as an SNMP trap, you may
want to monitor additional alarms using either of these means, or you may
want to reduce the number of alarms that are displayed in the Alarms table or
sent via SNMP traps.You can specify how each alarm is handled, according
to your business requirements.
You can specify the following settings for alarms:
•the maximum number of alarms displayed in the Alarms Panel (from 100
to 1000)
•whether to enable or disable SNMP traps for selected alarms; by default,
the system sends all Critical and Major alarms as SNMP traps if you
specify one or more trap destinations
•whether to display selected alarms in the Alarms table; by default all
Critical, Major, Minor, and Warning alarms are displayed in the Alarms
table
•whether to display selected alarms on the alarm set; by default, only
Critical and Major alarms are sent to this set
Fault and performance management fundamentals 19
You can also test a selected alarm. This allows you to test whether the LED or
SNMP traps are functioning as expected. Testing an alarm generates an
alarm in the system. Alarms generated using the Test Alarm feature are
identified in the Alarms table by the words “Test Event” in the alarm Problem
Description field.
For more information about using SNMP to monitor your system see, the BCM
•whether to display selected alarms in the Alarms table; by default all
Critical, Major, Minor, and Warning alarms are displayed in the Alarms
table
•whether to display selected alarms on the alarm set; by default, only core
telephony Critical and Major alarms are sent to this set
• use email forwarding
Notifying and selecting an alarm profile
Use the Alarm Setting panel to select the Notification Type which describes
where the alarm will be presented and Profile Selection which selects an
alarm profile.
Notify and select an alarm profile
Use the following procedure to select a Notification Type and an Alarm Profile.
StepAction
1Click on the Administration tab.
2Open the General folder, and then click the Alarm Settings task.
The Alarm Settings panel opens.
3Select the Notification Type that you want from the list.
4Select the Profile Selection that you want from the list.
--End--
Enabling or disabling SNMP traps for alarms
Use the following procedure to enable to disable SNMP traps for alarms.
Procedure steps
StepAction
1Click the Administration tab.
2Open the General folder, and then click the Alarm Settings task.
4In the Enable SNMP Trap column, select or clear the check box to enable
or disable SNMP traps for the selected alarm. If you select the check box for
a selected alarm, an SNMP trap will be generated if that particular alarm
condition occurs.
--End--
Enabling or disabling monitoring for selected alarms
Use the following procedure to enable or disable alarms.
Procedure steps
StepAction
1Click the Administration tab.
2Open the General folder, and then click the Alarm Settings task.
The Alarm Settings pane opens.
3In the Alarms Settings table, select an alarm.
4In the Enable GUI View column, select or clear the check box to enable or
disable a view of the selected alarm in the Alarms Panel. If you clear the
check box for a selected alarm, the alarm will not be displayed in the Alarms
table if that particular alarm condition occurs in the system.
Monitoring settings for the alarm set
Use the following procedure to monitor settings for the alarm set.
Procedure steps
StepAction
1Click the Administration tab.
2Open the General folder, and then click the Alarm Settings task.
The information in this section applies to both the BCM50 and the BCM450
platforms running BCM 5.0.
You can use the Business Element Manager to view detailed information
about the performance of the BCM and about the performance of system
resources. This chapter provides procedures for monitoring quality of service
(QoS) and other system metrics.
Using the Business Element Manager, you can monitor overall system
performance and other performance-related information.
You can monitor system metrics using the following tools:
•QoS Monitoring
•UPS Status
•NTP Metrics
This section contains information on the following topics:
•QoS Monitoring (page 33)
•UPS metrics (page 37)
•NTP metrics (page 38)
QoS Monitoring
QoS Monitor monitors the quality of service (QoS) of IP trunk services. The
tool periodically monitors the delay and packet-loss of IP networks between
two peer gateways. The main objective of the QoS Monitor is to allow new IP
telephony calls to fall back to the PSTN if the voice quality of the IP network
falls below the specified transmit threshold.
For information about setting the transmit threshold, see Nortel Business Communications Manager 5.0 Configuration—Telephony (NN40170-502).
You can set the threshold in the Business Element Manager in the Telephony
Resources panel.
You configure the QoS Monitor using the QoS Monitor panel on the
Administration tab. You can configure the following:
•the monitoring mode
•logging parameters
Procedure steps
StepAction
1Click the Administration tab.
2In the Navigation tree, click System Metrics >QoS Monitor.
3From the Monitoring Mode drop-down menu, select a monitoring mode.
Table 6 Variable definitions
System metrics monitoring 35
--End--
VariableValue
Disabled—
Enabled in Link-Monitor modeContinuously test the connection between the BCM and remote
endpoints.
Enabled in QoS-Monitor modeSelect this option if you want to calculate MOS values for each
endpoint, determine whether the connection has fallen below a
specific threshold, send MOS scores to FCAPS applications, and
create a log history of the MOS scores.
Configuring QoS logging attributes
Configure the logging attributes to set the size and frequency of QoS logs.
Procedure steps
StepAction
1Click the Administration tab.
2In the Navigation tree, click System Metrics>QoS Monitor.
3In the Logging area, select or clear the Enable Logging check box.
4In the Maximum log file size field, type the value of the maximum log size
5In the Logging Frequency field, type the value of the interval between logs.
After the interval you specified, the QoS system metrics appear in the Mean
Opinion Scores table.
--End--
Table 7 Variable definitions
VariableValue
Enable LoggingEnable the check box if you want to enable the logging of MOS
scores.
Maximum log file sizeEnter a value for the maximum size of the log file, from 1 to 10240
kilobytes (KB). The default is 10 KB.
Logging FrequencyEnter the time interval between each MOS log: 1 to 1440
minutes. The default is 1 minute.
Viewing QoS logs
The Mean Opinion Scores table displays the current network quality
described as a Mean Opinion Score (MOS) for each IP destination. You can
view the MOS mapping. Unlike the BCM 3.x where both transmit and receive
values were reported, the QoS Monitor collects only the transmit values.
Procedure steps
StepAction
1Click the Administration tab.
2In the Navigation tree, click System Metrics>QoS Monitor.
The QoS system metrics appear in the Mean Opinion Scores table.
3To update the MOS table with the most current values, select View >
Refresh, press F5, or select the Refresh icon from the toolbar.
--End--
Table 8 Variable definitions
VariableValue
NameDisplays the name of the Remote Gateway.
IP AddressDisplays the IP address of the Remote Gateway.
QoS IndicatorDisplays a text description of the current MOS value. The MOS
G.711Displays the current MOS value calculated when using a G.711
aLaw codec to transmit VoIP packets to this Remote Gateway.
The MOS can be a value from 0.00 to 5.00, where 0.00 is the
worst score (Poor) and 5.00 is best score (Excellent).
G.723-5.3kbit/sDisplays the current MOS value calculated when using a G.723
5.3 kbit/s codec to transmit VoIP packets to this Remote
Gateway.
The MOS can be a value from 0.00 to 5.00, where 0.00 is the
worst score (Poor) and 5.00 is best score (Excellent).
G.723-6.3kbit/sDisplays the current MOS value calculated when using a G.723
6.3 kbit/s codec to transmit VoIP packets to this Remote
Gateway.
The MOS can be a value from 0.00 to 5.00, where 0.00 is the
worst score (Poor) and 5.00 is best score (Excellent).
G.729Displays the current MOS value calculated when using a G.729
codec to transmit VoIP packets to this Remote Gateway.
The MOS can be a value from 0.00 to 5.00, where 0.00 is the
worst score (Poor) and 5.00 is best score (Excellent).
G.729ADisplays the current MOS value calculated when using a G.729A
codec to transmit VoIP packets to this remote Gateway.
The MOS can be a value from 0.00 to 5.00, where 0.00 is the
worst score (Poor) and 5.00 is best score (Excellent).
UPS metrics
BCM can support an Uninterruptible Power Supply (UPS) device to ensure
continuous operation during power interruption and failure conditions. The
UPS feature provides power source monitoring and battery backup so that
critical system functionality required to maintain and provide warning time to
either correct the problem or to activate a contingency plan for impacted
services is possible. UPS is described in Nortel Business Communication
Manager 450 5.0 Installation—System (NN40170-303) and BCM450 5.0
Installation Checklist and Quick Start Guide (NN40170-302) or the BCM50 5.0
Installation Checklist and Quick Start Guide (NN40170-308).
The UPS connects and communicates with the BCM through USB. Enable the
UPS feature by plugging the UPS USB cable into the BCM USB connector
before you power up the BCM. The UPS must be present during the boot up
process for the BCM to function.
The UPS Status panel tracks occurrences of alarms pertaining to UPS
operation. These alarms are also sequentially viewable in the Alarm panel.
The metrics correspond to alarms in the BCM and appear in the alarm panel
as well.
Accessing the UPS status
Complete this procedure to verify the status of the UPS before you boot up the
BCM system.
Procedure steps
StepAction
1Click the Administration tab.
2In the Navigation tree, click System Metrics >UPS Metrics > Status tab.
The status of the UPS appears. The UPS Status panel confirms that a UPS
is connected including model and serial number, its current status, and
provides a read out of the current values. Additionally, an indication is given
whether the value is within the normal range or not.
3To check the metrics of the UPS, click the Metrics tab.
NTP metrics
The metrics information appears in the panel.
--End--
Using Network Time Protocol (NTP), you can configure the time on the BCM
indirectly from a single time server. NTP is a network protocol designed to
synchronize the clocks of computers over an IP network. The NTP Metrics
provide an overview of the integrity of the NTP time source. If the BCM clock
control has not been configured to use NTP (Configuration>System>Date &
Time), then the NTP Metrics panel displays no data.
2In the Navigation tree, click System Metrics>NTP Metrics.
The NTP metrics appear in the panel.
--End--
Table 9 Variable definitions
VariableValue
Last SynchronizedWhen the last synchronization occurred.
Minimum time difference (s)The minimum time change that occurred since NTP was running.
Maximum time difference (s)The maximum time difference that occurred since NTP was
running.
Last Synchronization StatusThe results of the last synchronization: successful or
unsuccessful. If unsuccessful the reason for the failure is given:
failed to contact, or failed security check. A status of Not Running
indicates that NTP is not configured.
The information in this section applies to both the BCM50 and the BCM450
platforms running BCM 5.0.
You can use the Business Element Manager to view detailed information
about the performance of telephony resources on the BCM 5.0 system.
The Telephony Metrics folder allows you to track different aspects of
Telephony services.
This section contains information on the following topics:
•Proactive Voice Quality Management (page 41)
•Activity Reporter Basic (page 48)
•Trunk module metrics (page 50)
•Trunk module CSU statistics (page 52)
•CbC limit metrics (page 58)
•Hunt group metrics (page 60)
•PSTN Fallback metrics (page 62)
Proactive Voice Quality Management
Use Proactive Voice Quality Management (PVQM) metrics to monitor the
quality of VoIP calls. You can also use the PVQM metrics to diagnose
infrastructure problems in your network.
PVQM is fully supported on Phase 2 IP sets. Phase 1 IP sets support only the
following PVQM metrics: packet loss, inter arrival jitter, and rould trip delay.
The following table lists the IP Phones that support PVQM.
This task flow shows you the sequence of tasks you perform to configure and
monitor PVQM telephony metrics on the BCM system. To link to any
procedures, click on PVQM telephony metrics monitoring procedures
You can use PVQM to configure and report threshold violations for the
following voice quality metrics:
•
packet loss—packets lost in transit due to errors or network failures
•inter arrival jitter—the variable delay on a packet as it traverses a network
•round trip delay
•listening R factor—the transmission quality as experienced by the user; this
metric reflects the segment of the call that is carried over the RTP session
There are two thresholds for PVQM metrics: Warning, and Unacceptable. A
violation of the Warning threshold indicates that the voice quality is reduced
but is still within an acceptable range. A violation of the Unacceptable
threshold indicates a severe degradation in voice quality.
If an alarm is generated to report a threshold violation, additional information
is included in the alarm to indicate the source of the alarm and provide other
troubleshooting information. Table 11PVQM Alarms (page 43) lists the
abbreviations used in the alarm text to present this additional information.
Telephony metrics monitoring 43
Table 11 PVQM Alarms
Abbreviation AttributeValueDescription
cTcodec typealphanumericVocoder type used on this call
eTendpoint typeS or DS indicates softclient
D indicates desktop
nLRnetwork loss ratepercentage, scaled by 256
(e.g. 354 = 1.4%)
dRaverage discard ratepercentage, scaled by 256Average rate of discards due to
bDburst loss densitypercentage, scaled by
256
bLburst lengthmillisecondsAverage length of bursts
gDgap loss densitypercentage, scaled by 256Density of lost and discarded
gLaverage length of gap millisecondsaverage length of gap
eSDend system delaymillisecondsAverage end system delay on
Rate of network packet los
jitter
Density of lost and discarded
packets during burst periods
Polling interval(s)The interval at which the metrics are polled. The
Attention: The term “desktop” indicates IP sets that are desktop models. The term
“soft client” indicates IP sets that are software applications, such as the 2050 and
the 2050MVC. Because desktop IP sets can provide better voice quality than
software-based IP sets, you can specify different threshold levels for each type of IP
set.
Viewing PVQM telephony metrics
Use this procedure to view PVQM metrics.
Procedure steps
StepAction
1Click the Administration tab.
2In the Navigation tree, click Telephony Metrics >PVQM >Metrics.
Telephony metrics monitoring 47
value for this field is XXXXX. The default value is
XXXXX.
The PVQM metrics panel appears.
3Click a column heading to sort the metrics by a particular value.
Number of connectionsDisplays the total number of connections by IP sets
Last restDisplays the time of the last reset.
Most recent date and timeDisplays the time of the most recent threshold
Most recent DNDisplays the DN of the most recent threshold violation.
Count (desktop)Displays the number of times a desktop client
on the system since the last reset. This count
includes non-interactive features such as dial
tones, call progress tones, and music on hold.
violation.
violated a threshold.
Count
(softclient)
MTBV (desktop)Displays the mean time between threshold
MTBV (soft client)Displays the mean time between threshold
Reset metricsClick this button to clear out the metrics table. The
Activity Reporter Basic
This section contains information on the following topics:
•Enabling Activity Reporter Basic (page 48)
•Disabling Activity Reporter Basic (page 49)
Enabling Activity Reporter Basic
Activity Reporter Basic allows you to monitor the performance of the BCM.
You can use the Activity Reporter Basic to generate the following reports:
•telephone call activity
Displays the number of times a soft client violated
a threshold.
violations of a particular metric for desktop clients
(measured in seconds).
violations of a particular metric for soft clients
(measured in seconds).
Last reset time displays the current date and time.
•custom call routing activity
•voice mail receive statistics
•hunt group performance
When you enable Activity Reporter Basic, the BCM automatically generates
reports and updates them each night. The reports reflect the performance of
the BCM during the past four days. The panel displays the date and time of
the most recent report.
Enable daily data collectionClear the check box to disable Activity Reporter
Trunk module metrics
This section contains information on the following topics:
•Viewing the trunk module status (page 50)
•Viewing performance history information (page 50)
•Viewing D-channel information (page 51)
•Disabling or enabling a B-channel setting (page 51)
•Provisioning a PRI B-channel (page 52)
Viewing the trunk module status
View the trunk module status to isolate malfunctioning parts of your BCM
system. In addition, you can use the trunk module selection to disable and
enable modules and devices.
The window displays the locations for the modules connected to the system.
2Select the module that you want to view.
3Click Start Loopback Test to start the network test without having to
remove the
4Select a loopback type from the list.
5Click Stop Loopback Test when done the test of the network.
module.
--End--
Viewing performance history information
The Performance History tab displays the performance information over 15minute intervals collected in the past 24 hours. The performance information
collected includes the number of errored seconds, severely errored seconds,
and unavailable seconds over each 15-minute interval.
4Click the B-channel you want to enable or disable (B1 or B2).
5Select Enable or Disable.
If you are disabling the channel, you are prompted by a dialog box to confirm
your action. The State box indicates the mode of operation for the port. If the
port is enabled, this box is blank unless a device is physically connected.
Provisioning a PRI B-channel
When you purchase PRI from your service provider, you can request the
number of B-channels that are allocated for you to use. For example, you can
use 12 B-channels. If you do not have all of the PRI B channels, disable all the
B-channels that you do not need.
Prerequisites
•Nortel recommends that the number of lines you deprovision on a DTM
(configured as PRI) be the same as the number of B-channels that you
disable. For example, if the DTM is on Expansion 1, when you disable Bchannels 13 to 23, you should deprovision lines 77 to 87.
5Click the Enable or Disable button to change the setting for the channel.
Trunk module CSU statistics
Each trunk module has an internal channel service unit (CSU). When
enabled, the internal CSU monitors the quality of the received T1 signal and
provides performance statistics, alarm statistics, and diagnostic information.
--End--
Trunk modules must be individually programmed to establish parameters for
collecting and measuring transmission performance statistics by the CSU.
The system accumulates three performance parameters:
•errored seconds (ES)
•severely errored seconds (SES)
•unavailable seconds (UAS)
These parameters are defined according to TIA-547A. Errored seconds are
enhanced to include control slip (CS) events. Only near-end performance data
is recorded.
The internal CSU continuously monitors the received signal and detects four
types of transmission defects:
•any active carrier failure alarms (CFA), such as loss of signal (LOS), out
of frame (OOF), alarm indication signal (AIS), and remote alarm indication
(RAI)
•the number of bipolar violations that occurred in the last minute
•any defects that occurred in the last minute, such as loss of signal (LOS),
out of frame (OOF), and alarm indication signal (AIS)
•the number of milliseconds of short-term alarms in the last minute, such
as loss of signal (LOS), out of frame (OOF), alarm indication signal (AIS),
and remote alarm indication (RAI).
A short term alarm is declared when the detected defects persist for tens of
milliseconds. A carrier failure alarm (CFA) is a duration of carrier system
outage.
The criteria for declaring and clearing the alarms is selectable to meet those
in TIA-547A or TR64211. You can also view Carrier Failure Alarms as Core
Telephony Alarms in the Alarm Viewer.
The Current interval displays the duration of the current 15-minute interval
of the selected card, the number of errored seconds (ES), the number of
severely errored seconds (SES), and the number of unavailable time
seconds (UAS).
4Click the 24-hour summary heading for an overall summary of the previous
24 hours.
The Number of intervals, Errored Seconds, Severely Errored Seconds,
Unavailable Seconds appear in the summary.
The system displays a message indicating that this will remove all of the
statistics.
6Click OK to erase all the current statistics and begin collecting statistics
again.
Checking the CSU alarms
Check the CSU alarms to view the active loss of signal (LOS), out of frame
(OOF), remote alarm indicator (RAI), or alarm indication signal (AIS) alarms.
The display shows all the active alarms of the types LOS (loss of signal),
OOF (out of Frame), RAI (Remote alarm indicator), or AIS (Alarm indication
signal).
Checking carrier failure alarms
Check carrier failure alarms to view a history of alarms for a module. CFA
types reported by the BCM can be mapped to CFAs defined in TIA-547A and
TR62411 as shown in the table below.
The display shows all the occurrences of that alarm.
CbC limit metrics
This section contains information on the following topics:
--End--
•Accessing CbC limit metrics (page 58)
•Clearing CbC limit metrics (page 60)
Accessing CbC limit metrics
Call-by-call service (CbC) on public PRI protocol (NI-2) allows a PBX to use
channels more effectively by expanding or contracting the number of channels
available to different call types such as INWATS, OUTWATS, Foreign
Exchange (FX), and tie lines.
The call-by-call service is a method of offering and receiving services to
Customer Premises Equipment (CPE) on ISDN PRI without the use of
dedicated circuits (i.e. interface or B-channels). The Call-By-Call service
conveys signaling information over an ISDN Primary Rate Interface (PRI) that
indicates, on a per-call basis, the specific service type required to complete
the call.
Although PRI-MCDN and IP trunks do not have multiple call types, CbC limits
can be used on these trunks to limit the number of incoming or outgoing trunks
that may be in use simultaneously.
When the CbC the feature is configured, use the CbC Limit metrics panel to
monitor denied call activity for each service on each line pool.
PRI lines that support call-by-call services have maximum and minimum call
limits for each service. Use this panel to view reports for the services and to
assess the capacity of the PRI call services on your system. These limits are
set as part of the numbering plan programming.
Procedure steps
StepAction
1Click the Administration tab.
2In the Navigation tree, click Telephony Metrics >CbC Limit Metrics.
3In the Call by CallLimit Metrics table, select the line pool for which you
want to view CbC traffic.
The denied call details for each type of service supported by the line pool
appears in the Details for Pool table.
--End--
Variable definitions
VariableValue
Line Pool The pool of lines that call-by-call limits are applied
to.
Service TypeThe type of service that the limits apply to.
INCOMING due to Outgoing
Min.
due to Incoming Max.The number of incoming calls that have been
OUTGOING due to Incoming
Min.
due to Outgoing Max.The number of outgoing calls that have been
The number of incoming calls that have been
blocked due to the call-by-call limits.
blocked due to call-by-call limits.
The number of outgoing calls that have been
blocked due to the call-by-call limits.
Use this procedure to clear the Details for Pool table of the current CbC limit
metrics, and start a new monitoring period.
Procedure steps
StepAction
1Click the Administration tab.
2In the Navigation tree, click Telephony Metrics>CbC Limit Metrics.
3In the Call by Call Metrics table, select the line pool for which you want to
view CbC traffic.
The denied call details for each type of service supported by the line pool
appears in the Details for Pool table.
4Select one of the calls in the Calls denied because CbC limits were
exceeded list.
5Click the Reset Metrics button.
Hunt group metrics
This section contains information on the following topics:
•Accessing Hunt Group metrics (page 60)
•Resetting the Hunt Group metrics (page 62)
Accessing Hunt Group metrics
Hunt groups provide a service where incoming calls ring on a targeted group
of telephones called a Hunt group. When you designate a Hunt group, you
define the group as a unique Directory Number (DN). This DN receives and
distributes calls to the telephones assigned to the group.
You can include Hunt Group hourly metrics files with the CDR data files when
the are transferred to the central server. For more information on configuring
this option, refer to the Call Detail Recording System Configuration Guide
(NN40020-605).
Access the Hunt Group metrics to evaluate total call processing by hunt group
member.
Use this procedure to reset the Hunt Group metrics.
Procedure steps
StepAction
1Click the Administration tab.
2In the Navigation tree, click Telephony Metrics>Hunt Group Metrics.
The Hunt Groups table appears.
3In the Hunt Groups table, select the Hunt Group for which you want to reset
the metrics.
The Details for Hunt Group table appears.
4Click the Reset button.
--End--
PSTN Fallback metrics
This section contains information on the following topics:
•Accessing PSTN Fallback metrics (page 62)
•Resetting PSTN Fallback metrics (page 63)
Accessing PSTN Fallback metrics
When trunks are out of service, traffic can be switched to PSTN fallback lines.
Use this procedure to view how many fallback attempts and fallback failures
occur within a specific period using the PSTN Fallback Metrics panel.
Procedure steps
StepAction
1Click the Administration tab.
2In the Navigation tree, click Telephony Metrics>PSTN Fallback Metrics.
The PSTN Fallback Metrics panel appears with the metrics displayed.
The information in this section applies to both BCM450 and BCM50 platforms
running BCM 5.0.
This section provides information about the main unit LED status during
normal operation, startup, and reboot.
Navigation
•System status monitor LEDs (page 65)
System status monitor LEDs
The BCM system status LEDs on the main unit provide information about the
status of the BCM system. Use these LEDs to determine if the system is
functioning properly and if the system generates an alarm.
Table 13 System status LEDs states and descriptions
Power StatusDescription
Start-up sequence
Solid yellow
Solid yellowOffPower on self test (POST); 9 seconds.
Publication: NN40170-701
Document status: Standard
Document issue: 01.01
Document date: August 2009
Product release: 1.0
Job function: Planning and Engineering
Type: Publication
Language type: EN
NORTEL, the globemark design, and the NORTEL corporate logo are trademarks of Nortel Networks.
Windows is a trademark of Microsoft Corporation.
All other trademarks are the property of their respective owners.
To provide feedback or report a problem with this document, go to www.nortel.com/documentfeedback.
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.