4021339 Rev B

Prisma II XD Platform
System Guide - System Release 2.02
For Your Safety

Explanation of Warning and Caution Icons

Avoid personal injury and product damage! Do not proceed beyond any symbol
until you fully understand the indicated conditions.
The following warning and caution icons alert you to important information about
the safe operation of this product:
You may find this symbol in the document that accompanies this product.
This symbol indicates important operating or maintenance instructions.

You may find this symbol affixed to the product. This symbol indicates a live
terminal where a dangerous voltage may be present; the tip of the flash points
to the terminal device.
You may find this symbol affixed to the product. This symbol indicates a
protective ground terminal.

You may find this symbol affixed to the product. This symbol indicates a
chassis terminal (normally used for equipotential bonding).

You may find this symbol affixed to the product. This symbol warns of a
potentially hot surface.

You may find this symbol affixed to the product and in this document. This
symbol indicates an infrared laser that transmits intensity-modulated light
and emits invisible laser radiation or an LED that transmits intensity-
modulated light.

Important
Please read this entire guide. If this guide provides installation or operation
instructions, give particular attention to all safety statements included in this guide.
Notices

Trademark Acknowledgments
  Cisco, the Cisco logo, Cisco Systems, the Cisco Systems logo, Scientific Atlanta,
the Scientific Atlanta logo, Prisma, Prisma II, and SciCare are trademarks or
registered trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and
certain other countries.
  All other trademarks mentioned in this document are property of their respective owners.

Publication Disclaimer
Cisco Systems, Inc. assumes no responsibility for errors or omissions that may
appear in this publication. We reserve the right to change this publication at any
time without notice. This document is not to be construed as conferring by
implication, estoppel, or otherwise any license or right under any copyright or
patent, whether or not the use of any information in this document employs an
invention claimed in any existing or later issued patent.

Copyright
© 2008 Cisco Systems, Inc. All rights reserved. Printed in the United States of America.
Information in this publication is subject to change without notice. No part of this
publication may be reproduced or transmitted in any form, by photocopy,
microfilm, xerography, or any other means, or incorporated into any information
retrieval system, electronic or mechanical, for any purpose, without the express
permission of Cisco Systems, Inc.
 Contents

Product Notices xiii

Important Safety Instructions xv

Laser Safety xxv

Warning Labels ................................................................................................................. xxvii

Chapter 1 Quick Start Guide 1

Step 1: Install the Chassis in a Rack....................................................................................... 2
To Install the Chassis in a Rack................................................................................. 2
Step 2: Make Chassis-to-Chassis ICIM Connections........................................................... 3
Chassis-to-Chassis ICIM Connections ..................................................................... 3
ICIM IN and ICIM OUT Connectors........................................................................ 3
To Make ICIM IN and ICIM OUT Cable Connections .......................................... 3
ICIM IN and ICIM OUT Cables................................................................................ 5
Step 3: Make Electrical Power Connections ......................................................................... 6
Electrical Power Connections.................................................................................... 6
Chassis Wiring and Fusing........................................................................................ 6
Power Inlet Illustration .............................................................................................. 9
To Install the Power Cord.......................................................................................... 9
To Install the Power Supply in the Chassis........................................................... 10
To Share Power Between Two Chassis .................................................................. 11
Step 4: Install the ICIM2........................................................................................................ 14
To Install the ICIM2-XD........................................................................................... 14
Step 5: Set Network Parameters from the Command Line Interface (CLI) ................... 15
Step 6: Connect the ICIM to the Network .......................................................................... 19
To Set Up a Telnet CLI Session ............................................................................... 19
Step 7: Install Modules in the Chassis................................................................................. 20
To Install the Module ............................................................................................... 20
Step 8: Set Additional Parameters via CLI (Optional)..................................................... 22
To Set Additional Users for Telnet or CLI Access................................................ 22
Step 9: Set and Verify SNMP Community Strings ............................................................ 23
Step 10: Perform Chassis-to-Chassis ICIM Activation (Optional) .................................. 25
Step 11: Make Changes to Traps and Enterprise MIBs..................................................... 26
MIB Software ............................................................................................................. 26
Trap Overview .......................................................................................................... 26
Step 12: Make Physical Connections to Modules .............................................................. 27
To Make Transmitter RF Connections ................................................................... 27

4021339 Rev B iii

Contents

To Connect Optical Cables ...................................................................................... 27

Step 13: Verify System Release and Module Firmware Versions ................................... 29

Chapter 2 Introduction 31
Related Publications .............................................................................................................. 33
Prisma II XD Platform ........................................................................................................... 34
XD Platform Components ....................................................................................... 34
XD Chassis ................................................................................................................. 35
XD Chassis Fan Assembly ....................................................................................... 35
Chassis Power Supply Architecture....................................................................... 35
ICIM2-XD................................................................................................................... 37
XD Application Modules ......................................................................................... 38
Prisma II XD Chassis ............................................................................................................. 39
Chassis Features........................................................................................................ 39
Chassis Configuration .............................................................................................. 40
Typical Chassis Block Diagram .............................................................................. 41
Chassis Illustrations.................................................................................................. 42
Chassis Front Panel Features................................................................................... 42
Chassis Back Panel Features.................................................................................... 43
Chassis Midplane...................................................................................................... 44
Fan Assembly ............................................................................................................ 44
Midplane Bus Connectors........................................................................................ 45
XD Chassis Control Board ....................................................................................... 45
XD Chassis Fan Assembly .................................................................................................... 47
Fan Operation............................................................................................................ 47
Fan Assembly Illustration........................................................................................ 47
AC-to-DC Bulk Power Supply Modules............................................................................. 48
Power Sharing ........................................................................................................... 48
Power Supply Configurations................................................................................. 48
Electrical Input Voltages .......................................................................................... 50
Power Inlets ............................................................................................................... 50
AC-to-DC Bulk Power Supply Illustration ........................................................... 51
AC-to-DC Bulk Power Supply Features ................................................................ 51
DC-to-DC Converters............................................................................................................ 52
DC-to-DC Converter Illustration............................................................................ 52
Prisma II ICIM2-XD ............................................................................................................... 53
ICIM2-XD Block Diagram........................................................................................ 53
ICIM2-XD Illustration (Front Panel) ...................................................................... 54
ICIM2-XD Front Panel Features.............................................................................. 54

Chapter 3 Hardware Installation 55

Before You Begin.................................................................................................................... 56
Unpacking and Inspecting the Chassis.................................................................. 56
Required Equipment and Tools .............................................................................. 56

iv 4021339 Rev B
 Contents

Site Requirements .................................................................................................................. 57

Operating Environment ........................................................................................... 57
Chassis Wiring and Fusing...................................................................................... 57
Rack Location Requirements................................................................................... 59
Unused Slots .............................................................................................................. 60
Mounting the Chassis in a Rack........................................................................................... 61
To Install the Chassis in a Rack............................................................................... 61
Chassis Dimensions.................................................................................................. 62
Connector Interface Panel..................................................................................................... 63
Connecting the ICIM to Additional Chassis ...................................................................... 64
To Make ICIM IN and ICIM OUT Cable Connections ........................................ 64
To Change the Chassis ID Number........................................................................ 65
ICIM IN and ICIM OUT Cables.............................................................................. 66
Chassis-to-Chassis ICIM Activation....................................................................... 66
Connecting a Chassis to the TNCS Server.......................................................................... 68
Cable Kits for Connecting a Chassis to the TNCS Server ................................... 68
To Connect TNCS to the Chassis EM IN Port....................................................... 68
Using TNCS with Multiple Chassis ....................................................................... 69
External Alarms Connections............................................................................................... 70
Master-Slave Operation ........................................................................................... 70
ALARM IN and OUT Connections ........................................................................ 70
Master-Slave Illustration.......................................................................................... 71
ALARM IN and OUT Terminal Blocks.................................................................. 71
Fan Assembly ......................................................................................................................... 72
To Remove the Fan Assembly................................................................................. 72
Installing the Power Supply ................................................................................................. 73
Power Supply Requirements................................................................................... 73
Electrical Power Connections.................................................................................. 74
Chassis Wiring and Fusing...................................................................................... 74
DC Power Connectors.............................................................................................. 76
Power Inlet Illustration ............................................................................................ 77
To Install the Power Cord........................................................................................ 77
To Install the Power Supply in the Chassis........................................................... 78
Power Supply Cooling Fans .................................................................................... 79
To Install the DC-to-DC Converter ........................................................................ 79
To Monitor the Power Supply................................................................................. 81
To Enable Power Passing......................................................................................... 81
Installing the ICIM................................................................................................................. 83
To Install the ICIM2-XD........................................................................................... 83
Installing Application Modules ........................................................................................... 84
To Install the Module ............................................................................................... 84
To Remove the Module............................................................................................ 85
Connecting Optical Cables ................................................................................................... 87
To Connect Optical Cables ...................................................................................... 87
Connecting RF Cables ........................................................................................................... 88
To Connect RF Cables .............................................................................................. 88

4021339 Rev B v
Contents

Chapter 4 Equipment Configuration 89

HyperTerminal Session Setup.............................................................................................. 90
To Set Up a HyperTerminal Serial Port Session ................................................... 90
CLI Parameters....................................................................................................................... 93
Login ........................................................................................................................... 93
To Set Additional Users for Telnet or CLI Access................................................ 94
To Set and Verify SNMP Community Strings ...................................................... 94
Telnet Session ......................................................................................................................... 96
To Set Up a Telnet CLI Session ............................................................................... 96
SNMP Parameters.................................................................................................................. 98

Chapter 5 Operation using ICIM 99

ICIM Introduction................................................................................................................ 100
Laser Warning ......................................................................................................... 100
Overview.................................................................................................................. 100
ICIM2-XD Block Diagram...................................................................................... 101
ICIM Front Panel.................................................................................................................. 102
ICIM2-XD Illustration (Front Panel) .................................................................... 102
ICIM2-XD Front Panel Features............................................................................ 102
Operating the ICIM ............................................................................................................. 103
Operating Status Parameters................................................................................. 103
User Alarm Data Parameters ................................................................................ 104
Module Alarm Data Parameters........................................................................... 104
Manufacturing Data Parameters .......................................................................... 105
SNMP Considerations ............................................................................................ 106
Basic SNMP Setup................................................................................................... 106
Default Community Strings .................................................................................. 107
Setting Trap Receive Parameters ....................................................................................... 108

Chapter 6 Operation using LCI 109

LCI Introduction .................................................................................................................. 110
LCI Function ............................................................................................................ 110
System Requirements .......................................................................................................... 111
Computer Requirements........................................................................................ 111
Cable Requirements................................................................................................ 111
Installing LCI ........................................................................................................................ 112
To Install the LCI Software.................................................................................... 112
Connecting Your Computer to the Chassis...................................................................... 115
To Connect a Computer to the Chassis................................................................ 115
Starting LCI Software .......................................................................................................... 116
To Start LCI Software ............................................................................................. 116

vi 4021339 Rev B
 Contents

LCI Module Tree .................................................................................................................. 117

Module Tree............................................................................................................. 117
Accessing the Module Detail Information ....................................................................... 118
Module Details Window........................................................................................ 118
To Access the Module Details, Double-Click the Chassis................................. 119
To Access the Module Details, Right-Click the Chassis .................................... 120
To Access the Module Details, Double-Click the Module ................................ 121
To Access the Module Details, Right-Click the Module.................................... 122
Checking the Operating Status .......................................................................................... 124
To Check the Operating Status using LCI ........................................................... 124
Operating Status Parameters................................................................................. 124
Configuring the Module using LCI................................................................................... 126
To Set Control Parameters using LCI................................................................... 126
XD Chassis Control Parameters............................................................................ 127
Checking the Module Alarms using LCI.......................................................................... 128
To Check Alarms using LCI .................................................................................. 128
Alarm Data Parameters.......................................................................................... 129
Modifying Module Alarm Limits using LCI.................................................................... 131
To Modify Alarm Limits using LCI...................................................................... 131
Alarm Limit Parameters ........................................................................................ 132
Checking Manufacturing Data using LCI ........................................................................ 134
To Check Manufacturing Data using LCI ........................................................... 134
Manufacturing Data Parameters .......................................................................... 134

Chapter 7 User Management 137

Introduction .......................................................................................................................... 138
User Accounts ......................................................................................................... 138
Usernames................................................................................................................ 138
Passwords ................................................................................................................ 139
Security Levels ........................................................................................................ 139
Account Enable or Disable .................................................................................... 139
Login Thresholds .................................................................................................... 140
User Lockout ........................................................................................................... 140
Inactivity Timeout................................................................................................... 140
Replacing the Default Admin Account............................................................................. 141
To Replace the Default Admin Account.............................................................. 141
Working With User Accounts ............................................................................................ 144
To Add a New User................................................................................................ 144
To Change a User Password ................................................................................. 145
To Change a User Security Level.......................................................................... 146
To Change User Account Status ........................................................................... 147
To Unlock User Accounts ...................................................................................... 148
To Delete a User Account ...................................................................................... 148
To List All Currently Logged In Users ................................................................ 149

4021339 Rev B vii

Contents

User Lockout......................................................................................................................... 151

To View the Current Lockout Interval................................................................. 151
To Specify a New Lockout Interval...................................................................... 152
To View Locked-Out Users ................................................................................... 153
To View Lockout Time Remaining by User........................................................ 154
To Unlock a Locked-Out User............................................................................... 154

Chapter 8 Event Log 157

Introduction .......................................................................................................................... 158
Event Log Fields...................................................................................................... 158
Event Action IDs ..................................................................................................... 159
Viewing the Event Log........................................................................................................ 161
To View the Event Log through the CLI ............................................................. 161
To View the Event Log through the ICIM Web Interface ................................. 162
Clearing the Event Log........................................................................................................ 163
To Clear the Event Log through the CLI ............................................................. 163
To Clear the Event Log through the Web............................................................ 163
Setting Event Log Filter Parameters.................................................................................. 164
To View Filter Parameters through the CLI........................................................ 164
To Set Filter Parameters through the CLI............................................................ 164
To View Filter Parameters through the Web ...................................................... 165
To Set Filter Parameters through the Web .......................................................... 165
Event Log-Related Traps .................................................................................................... 166
Example: 80% Full Trap ......................................................................................... 166
Example: 100% Full Trap ....................................................................................... 167
Downloading and Viewing the Event Log Remotely..................................................... 168
To Download the Event Log File .......................................................................... 168

Chapter 9 SNMP Management 171

Introduction .......................................................................................................................... 172
Prisma II Enterprise MIBs...................................................................................... 172
ICIM MIB .............................................................................................................................. 173
To View the ICIM MIB ........................................................................................... 173
ICIM MIB Elements ................................................................................................ 173
Event Log File Management ................................................................................. 184
Trap Handling......................................................................................................... 188
Trap Recv Table....................................................................................................... 188
Trap Logging Auxiliaries....................................................................................... 192
Trap Logging Table ................................................................................................ 193
Module MIB.......................................................................................................................... 198
Module MIB Tables ................................................................................................ 198
Module Table........................................................................................................... 199
Module Alarm Table .............................................................................................. 207
Alarm Severity ........................................................................................................ 213

viii 4021339 Rev B

 Contents

Current Alarm Table .............................................................................................. 213

Module Monitor Table ........................................................................................... 216
Module Control Table ............................................................................................ 219
Insert Module Table................................................................................................ 222
Remove Module Table ........................................................................................... 222
Remote Reboot of ICIM and Modules .............................................................................. 225
To Reboot the ICIM via SNMP ............................................................................. 225
To Reboot a Module via SNMP ............................................................................ 225
Prisma II Traps ..................................................................................................................... 226
About Traps ............................................................................................................. 226
Standard and Enhanced Traps.............................................................................. 227
Trap Receiving Configuration............................................................................... 228
To Configure Trap Destination............................................................................. 229
Trap Types ............................................................................................................... 229
Enhanced Trap Binding Information ................................................................... 239
Enhanced Trap Alarms .......................................................................................... 243
Enhanced Trap Events ........................................................................................... 246
Delay in the Discovery Process.......................................................................................... 263
Alarm Threshold Modification .......................................................................................... 264
System Behavior................................................................................................................... 266
ICIM as Proxy for Module Information............................................................... 266
Module Removal and Enhanced Traps ............................................................... 266
Frequently Asked Questions .............................................................................................. 267
How do I configure trap destination?.................................................................. 267
Why do the same alarm values represent different conditions?...................... 267
How do Enhanced Traps differ from other trap types? .................................... 268
When do traps associated with module insertion, removal, and alarms
occur?..................................................................................................................... 268
Where can I find trap definitions?........................................................................ 269
What is the Trap Logging Table?.......................................................................... 269

Chapter 10 Maintenance and Troubleshooting 271

Maintenance.......................................................................................................................... 273
Maintenance Record ............................................................................................... 273
Troubleshooting ................................................................................................................... 274
Chassis Troubleshooting........................................................................................ 274
Alarm Troubleshooting.......................................................................................... 275
Additional Assistance ............................................................................................ 275
Fan Ok Alarms ..................................................................................................................... 276
Fan Alarm Parameters ........................................................................................... 276
Suggested Actions................................................................................................... 276
ChasTemp Alarm................................................................................................................. 277
ChasTemp Alarm Parameters ............................................................................... 277
Suggested Actions................................................................................................... 277

4021339 Rev B ix
Contents

ConvAIn Alarm.................................................................................................................... 278

ConvAIn Alarm Parameters.................................................................................. 278
Suggested Actions................................................................................................... 278
ConvA+24 Alarm................................................................................................................. 279
ConvA+24 Alarm Parameters ............................................................................... 279
Suggested Actions................................................................................................... 279
To Access the DC-to-DC Converter ..................................................................... 279
ConvA+5 Alarm................................................................................................................... 281
ConvA+5 Alarm Parameters ................................................................................. 281
Suggested Actions................................................................................................... 281
To Access the DC-to-DC Converter ..................................................................... 281
ConvA-5 Alarm .................................................................................................................... 283
ConvA-5 Alarm Parameters .................................................................................. 283
Suggested Actions................................................................................................... 283
To Access the DC-to-DC Converter ..................................................................... 283
ConvBIn Alarm .................................................................................................................... 285
ConvBIn Alarm Parameters .................................................................................. 285
Suggested Actions................................................................................................... 285
ConvB+24 Alarm.................................................................................................................. 286
ConvB+24 Alarm Parameters................................................................................ 286
Suggested Actions................................................................................................... 286
To Access the DC-to-DC Converter ..................................................................... 286
ConvB+5 Alarm.................................................................................................................... 288
ConvB+5 Alarm Parameters.................................................................................. 288
Suggested Actions................................................................................................... 288
To Access the DC-to-DC Converter ..................................................................... 288
ConvB-5 Alarm..................................................................................................................... 290
ConvB-5 Alarm Parameters................................................................................... 290
Suggested Actions................................................................................................... 290
To Access the DC-to-DC Converter ..................................................................... 290
Cleaning Optical Connectors ............................................................................................. 292
Recommended Equipment .................................................................................... 292
Tips for Optimal Fiber-Optic Connector Performance...................................... 292
To Clean Optical Connectors ................................................................................ 293
Fiber Optic Connector Cleaning Instructions ..................................................... 293
Connecting Optical Cables ................................................................................................. 296
To Connect Optical Cables .................................................................................... 296

Chapter 11 Customer Support Information 297

Obtaining Product Support ................................................................................................ 298
Support Telephone Numbers................................................................................ 298
Return Product for Repair .................................................................................................. 300
Obtaining an RMA Number and Shipping Address ......................................... 300
Completing the Scientific Atlanta Transmission Networks Repair Tag ......... 301
Packing and Shipping the Product....................................................................... 304

x 4021339 Rev B
 Contents

Appendix A Prisma II Permitted CLI Commands 307

From CLI ............................................................................................................................... 308
From ICIM............................................................................................................................. 309
From */* MODULE ............................................................................................................. 315
From TERMINAL ................................................................................................................ 318

Appendix B Features Available via Remote User Interface 319

Overview............................................................................................................................... 320
ICIM Data.............................................................................................................................. 321
Module Data ......................................................................................................................... 324
Current Alarms .................................................................................................................... 325
Module Alarms .................................................................................................................... 326
Module Controls .................................................................................................................. 327
Module Monitors ................................................................................................................. 328
System Information ............................................................................................................. 329
User Management................................................................................................................ 330

Appendix C Module Parameter Descriptions 331

XD Chassis Parameters ....................................................................................................... 332
XD Chassis Control Parameters............................................................................ 332
XD Chassis Alarm Data Parameters..................................................................... 332
XD Chassis Monitor Parameter Examples .......................................................... 333
XD Chassis Manufacturing Data Parameter Examples..................................... 334

Glossary 335

Index 343

4021339 Rev B xi
 Product Notices

Product Notices
System Release
The information in this guide pertains to Prisma II System Release 2.02.09 and ICIM2
Firmware Release 2.02.10.

Operating Temperature
CAUTION:
The warranty may be voided and the equipment damaged if you operate the
equipment outside the specified temperature limits (32 to 122°F or 0 to 50°C).
Specification temperature limits are measured in the air stream at the fan tray
inlet and may be higher than room ambient temperature.

4021339 Rev B xiii

 Important Safety Instructions

Important Safety Instructions

Read and Retain Instructions
Carefully read all safety and operating instructions before operating this equipment,
and retain them for future reference.

Follow Instructions and Heed Warnings

Follow all operating and use instructions. Pay attention to all warnings and cautions
in the operating instructions, as well as those that are affixed to this equipment.

Terminology
The terms defined below are used in this document. The definitions given are based
on those found in safety standards.
Service Personnel - The term service personnel applies to trained and qualified
individuals who are allowed to install, replace, or service electrical equipment. The
service personnel are expected to use their experience and technical skills to avoid
possible injury to themselves and others due to hazards that exist in service and
restricted access areas.
User and Operator - The terms user and operator apply to persons other than service
personnel.
Ground(ing) and Earth(ing) - The terms ground(ing) and earth(ing) are synonymous.
This document uses ground(ing) for clarity, but it can be interpreted as having the
same meaning as earth(ing).

Electric Shock Hazard

This equipment meets applicable safety standards.
WARNING:
To reduce risk of electric shock, perform only the instructions that are
included in the operating instructions. Refer all servicing to qualified service
personnel only.

Electric shock can cause personal injury or even death. Avoid direct contact with
dangerous voltages at all times. The protective ground connection, where provided,
is essential to safe operation and must be verified before connecting the power
supply.
Know the following safety warnings and guidelines:
  Dangerous Voltages

4021339 Rev B xv
Important Safety Instructions

- Only qualified service personnel are allowed to perform equipment

installation or replacement.
- Only qualified service personnel are allowed to remove chassis covers and
access any of the components inside the chassis.
  Grounding
- Prisma II equipment is suitable for installation as part of the common
bonding network (CBN).
- Do not violate the protective grounding by using an extension cable, power
cable, or autotransformer without a protective ground conductor.
- Take care to maintain the protective grounding of this equipment during
service or repair and to re-establish the protective grounding before putting
this equipment back into operation.
Note: See the Installation section of this document for specific information regarding
the AC and DC power, wiring, fusing, and grounding requirements for this product.

Installation Site
When selecting the installation site, comply with the following:
  Protective Ground - The protective ground lead of the building’s electrical
installation should comply with national and local requirements.
  Environmental Condition – The installation site should be dry, clean, and
ventilated. Do not use this equipment where it could be at risk of contact with
water. Ensure that this equipment is operated in an environment that meets the
requirements as stated in this equipment’s technical specifications, which may be
found on this equipment’s data sheet.

Installation Requirements
WARNING:
Allow only qualified service personnel to install this equipment. The
installation must conform to all local codes and regulations.

Equipment Placement
WARNING:
Avoid personal injury and damage to this equipment. An unstable mounting
surface may cause this equipment to fall.

Prisma II equipment is suitable for installation in network telecommunications

facilities.

xvi 4021339 Rev B

 Important Safety Instructions

To protect against equipment damage or injury to personnel, comply with the

following:
  Install this equipment in a restricted access location.
  Do not install near any heat sources such as radiators, heat registers, stoves, or
other equipment (including amplifiers) that produce heat.
  Place this equipment close enough to a DC input voltage source to accommodate
the length of this equipment’s power cord.
  Route all power cords so that people cannot walk on, place objects on, or lean
objects against them. This may pinch or damage the power cords. Pay particular
attention to power cords at plugs, outlets, and the points where the power cords
exit this equipment.
  Use only with a cart, stand, tripod, bracket, or table specified by the
manufacturer, or sold with this equipment.
  Make sure the mounting surface or rack is stable and can support the size and
weight of this equipment.
  The mounting surface or rack should be appropriately anchored according to
manufacturer’s specifications. Ensure this equipment is securely fastened to the
mounting surface or rack where necessary to protect against damage due to any
disturbance and subsequent fall.

Ventilation
This equipment has openings for ventilation to protect it from overheating. To
ensure equipment reliability and safe operation, do not block or cover any of the
ventilation openings. Install the equipment in accordance with the manufacturer’s
instructions.

Rack Mounting Safety Precautions

Mechanical Loading
Make sure that the rack is placed on a stable surface. If the rack has stabilizing
devices, install these stabilizing devices before mounting any equipment in the rack.
WARNING:
Avoid personal injury and damage to this equipment. Mounting this
equipment in the rack should be such that a hazardous condition is not caused
due to uneven mechanical loading.

4021339 Rev B xvii

Important Safety Instructions

Reduced Airflow
When mounting this equipment in the rack, do not obstruct the cooling airflow
through the rack. Be sure to mount the blanking plates to cover unused rack space.
Additional components such as combiners and net strips should be mounted at the
back of the rack, so that the free airflow is not restricted.
CAUTION:
Installation of this equipment in a rack should be such that the amount of
airflow required for safe operation of this equipment is not compromised.

Elevated Operating Ambient Temperature

Only install this equipment in a humidity- and temperature-controlled environment
that meets the requirements given in this equipment’s technical specifications.
CAUTION:
If installed in a closed or multi-unit rack assembly, the operating ambient
temperature of the rack environment may be greater than room ambient
temperature. Therefore, install this equipment in an environment compatible
with the manufacturer’s maximum rated ambient temperature.

Handling Precautions
When moving a cart that contains this equipment, check for any of the following
possible hazards:
WARNING:
Avoid personal injury and damage to this equipment! Move any equipment
and cart combination with care. Quick stops, excessive force, and uneven
surfaces may cause this equipment and cart to overturn.

  Use caution when moving this equipment/cart combination to avoid injury from
tip-over.
  If the cart does not move easily, this condition may indicate obstructions or
cables that may need to be disconnected before moving this equipment to
another location.
  Avoid quick stops and starts when moving the cart.
  Check for uneven floor surfaces such as cracks or cables and cords.

Grounding
If this equipment is equipped with an external grounding terminal, attach one end of
an 18-gauge wire (or larger) to the grounding terminal; then, attach the other end of
the wire to a ground, such as a grounded equipment rack.

xviii 4021339 Rev B

 Important Safety Instructions

Equipotential Bonding
If this equipment is equipped with an external chassis terminal marked with the IEC
60417-5020 chassis icon ( ), the installer should refer to CENELEC standard EN
50083-1 or IEC standard IEC 60728-11 for correct equipotential bonding connection
instructions.

Connection to IT Power Systems

This equipment has been tested for IT power systems 240 VAC phase-to-phase.

Connection to -48 V DC/-60 V DC Power Sources

If this equipment is DC-powered, refer to the specific installation instructions in this
manual or in companion manuals in this series for information on connecting this
equipment to nominal -48 V DC/-60 V DC power sources.

Circuit Overload
Know the effects of circuit overloading before connecting this equipment to the
power supply.
CAUTION:
Consider the connection of this equipment to the supply circuit and the effect
that overloading of circuits might have on overcurrent protection and supply
wiring. Refer to the information on the equipment-rating label when
addressing this concern.

General Servicing Precautions

WARNING:
Avoid electric shock! Opening or removing this equipment’s cover may
expose you to dangerous voltages.

CAUTION:
These servicing precautions are for the guidance of qualified service
personnel only. To reduce the risk of electric shock, do not perform any
servicing other than that contained in the operating instructions unless you
are qualified to do so. Refer all servicing to qualified service personnel.

Be aware of the following general precautions and guidelines:

  Servicing - Servicing is required when this equipment has been damaged in any
way, such as power supply cord or plug is damaged, liquid has been spilled or
objects have fallen into this equipment, this equipment has been exposed to rain
or moisture, does not operate normally, or has been dropped.
  Wristwatch and Jewelry - For personal safety and to avoid damage of this

4021339 Rev B xix

Important Safety Instructions

equipment during service and repair, do not wear electrically conducting objects
such as a wristwatch or jewelry.
  Lightning - Do not work on this equipment, or connect or disconnect cables,
during periods of lightning.
  Labels - Do not remove any warning labels. Replace damaged or illegible
warning labels with new ones.
  Covers - Do not open the cover of this equipment and attempt service unless
instructed to do so in the instructions. Refer all servicing to qualified service
personnel only.
  Moisture - Do not allow moisture to enter this equipment.
  Cleaning - Use a damp cloth for cleaning.
  Safety Checks - After service, assemble this equipment and perform safety
checks to ensure it is safe to use before putting it back into operation.

Electrostatic Discharge
Electrostatic discharge (ESD) results from the static electricity buildup on the human
body and other objects. This static discharge can degrade components and cause
failures.
Take the following precautions against electrostatic discharge:
  Use an anti-static bench mat and a wrist strap or ankle strap designed to safely
ground ESD potentials through a resistive element.
  Keep components in their anti-static packaging until installed.
  Avoid touching electronic components when installing a module.

Fuse Replacement
To replace a fuse, comply with the following:
  Disconnect the power before changing fuses.
  Identify and clear the condition that caused the original fuse failure.
  Always use a fuse of the correct type and rating. The correct type and rating are
indicated on this equipment.

Batteries
This product may contain batteries. Special instructions apply regarding the safe use
and disposal of batteries:
Safety

xx 4021339 Rev B
 Important Safety Instructions

  Insert batteries correctly. There may be a risk of explosion if the batteries are
incorrectly inserted.
  Do not attempt to recharge ‘disposable’ or ‘non-reusable’ batteries.
  Please follow instructions provided for charging ‘rechargeable’ batteries.
  Replace batteries with the same or equivalent type recommended by
manufacturer.
  Do not expose batteries to temperatures above 100°C (212°F).
Disposal
  The batteries may contain substances that could be harmful to the environment
  Recycle or dispose of batteries in accordance with the battery manufacturer’s
instructions and local/national disposal and recycling regulations.

  The batteries may contain perchlorate, a known hazardous substance, so special

handling and disposal of this product might be necessary. For more information
about perchlorate and best management practices for perchlorate-containing
substance, see www.dtsc.ca.gov/hazardouswaste/perchlorate.

Modifications
This equipment has been designed and tested to comply with applicable safety, laser
safety, and EMC regulations, codes, and standards to ensure safe operation in its
intended environment. Refer to this equipment's data sheet for details about
regulatory compliance approvals.
Do not make modifications to this equipment. Any changes or modifications could
void the user’s authority to operate this equipment.
Modifications have the potential to degrade the level of protection built into this
equipment, putting people and property at risk of injury or damage. Those persons
making any modifications expose themselves to the penalties arising from proven
non-compliance with regulatory requirements and to civil litigation for
compensation in respect of consequential damages or injury.

4021339 Rev B xxi

Important Safety Instructions

Accessories
Use only attachments or accessories specified by the manufacturer.

Electromagnetic Compatibility Regulatory Requirements

This equipment meets applicable electromagnetic compatibility (EMC) regulatory
requirements. Refer to this equipment's data sheet for details about regulatory
compliance approvals. EMC performance is dependent upon the use of correctly
shielded cables of good quality for all external connections, except the power source,
when installing this equipment.
  Ensure compliance with cable/connector specifications and associated
installation instructions where given elsewhere in this manual.
Otherwise, comply with the following good practices:
  Multi-conductor cables should be of single-braided, shielded type and have
conductive connector bodies and backshells with cable clamps that are
conductively bonded to the backshell and capable of making 360° connection to
the cable shielding. Exceptions from this general rule will be clearly stated in the
connector description for the excepted connector in question.
  Ethernet cables should be of single-shielded or double-shielded type.
  Coaxial cables should be of the double-braided shielded type.

EMC Compliance Statements

Where this equipment is subject to USA FCC and/or Industry Canada rules, the
following statements apply:

FCC Statement for Class A Equipment

This equipment has been tested and found to comply with the limits for a Class A
digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to
provide reasonable protection against harmful interference when this equipment is
operated in a commercial environment.
This equipment generates, uses, and can radiate radio frequency energy and, if not
installed and used in accordance with the instruction manual, may cause harmful
interference to radio communications. Operation of this equipment in a residential
area is likely to cause harmful interference in which case users will be required to
correct the interference at their own expense.

Industry Canada - Industrie Canadienne Statement

This apparatus complies with Canadian ICES-003.
Cet appareil est confome à la norme NMB-003 du Canada.

xxii 4021339 Rev B

 Important Safety Instructions

CENELEC/CISPR Statement with Respect to Class A Information Technology Equipment

This is a Class A equipment. In a domestic environment this equipment may cause
radio interference in which case the user may be required to take adequate
measures.

4021339 Rev B xxiii

 Laser Safety

Laser Safety
Introduction
This equipment contains an infrared laser that transmits intensity-modulated light
and emits invisible radiation.

Warning: Radiation
WARNING:

ƒ Avoid personal injury! Use of controls, adjustments, or procedures other

than those specified herein may result in hazardous radiation exposure.

ƒ Avoid personal injury! The laser light source on this equipment (if a
transmitter) or the fiber cables connected to this equipment emit invisible
laser radiation. Avoid direct exposure to the laser light source.

ƒ Avoid personal injury! Viewing the laser output (if a transmitter) or fiber
cable with optical instruments (such as eye loupes, magnifiers, or
microscopes) may pose an eye hazard.

  Do not apply power to this equipment if the fiber is unmated or unterminated.

  Do not stare into an unmated fiber or at any mirror-like surface that could reflect
light emitted from an unterminated fiber.
  Do not view an activated fiber with optical instruments (e.g., eye loupes,
magnifiers, microscopes).
  Use safety-approved optical fiber cable to maintain compliance with applicable
laser safety requirements.

Warning: Fiber Optic Cables

WARNING:
Avoid personal injury! Qualified service personnel may only perform the
procedures in this manual. Wear safety glasses and use extreme caution when
handling fiber optic cables, particularly during splicing or terminating
operations. The thin glass fiber core at the center of the cable is fragile when
exposed by the removal of cladding and buffer material. It easily fragments
into glass splinters. Using tweezers, place splinters immediately in a sealed
waste container and dispose of them safely in accordance with local
regulations.

4021339 Rev B xxv

Laser Safety

Safe Operation for Software Controlling Optical Transmission Equipment

If this manual discusses software, the software described is used to monitor and/or
control ours and other vendors’ electrical and optical equipment designed to
transmit video, voice, or data signals. Certain safety precautions must be observed
when operating equipment of this nature.
For equipment specific safety requirements, refer to the appropriate section of the
equipment documentation.
For safe operation of this software, refer to the following warnings.
WARNING:

ƒ Ensure that all optical connections are complete or terminated before

using this equipment to remotely control a laser device. An optical or laser
device can pose a hazard to remotely located personnel when operated
without their knowledge.

ƒ Allow only personnel trained in laser safety to operate this software.

Otherwise, injuries to personnel may occur.

ƒ Restrict access of this software to authorized personnel only.

ƒ Install this software in equipment that is located in a restricted access area.

xxvi 4021339 Rev B

 Laser Safety

Warning Labels
The following illustrations display the warning labels on this equipment.

4021339 Rev B xxvii

 1 Chapter 1
Quick Start Guide
Introduction
This chapter provides streamlined step-by-step instructions for
installing and configuring the platform hardware and firmware. Later
chapters of this guide provide more detailed information on platform
design, operation, and maintenance.

In This Chapter
ƒ Step 1: Install the Chassis in a Rack...................................................... 2
ƒ Step 2: Make Chassis-to-Chassis ICIM Connections.......................... 3
ƒ Step 3: Make Electrical Power Connections ........................................ 6
ƒ Step 4: Install the ICIM2....................................................................... 14
ƒ Step 5: Set Network Parameters from the Command Line
Interface (CLI) ....................................................................................... 15
ƒ Step 6: Connect the ICIM to the Network ......................................... 19
ƒ Step 7: Install Modules in the Chassis................................................ 20
ƒ Step 8: Set Additional Parameters via CLI (Optional).................... 22
ƒ Step 9: Set and Verify SNMP Community Strings ........................... 23
ƒ Step 10: Perform Chassis-to-Chassis ICIM Activation
(Optional)............................................................................................... 25
ƒ Step 11: Make Changes to Traps and Enterprise MIBs.................... 26
ƒ Step 12: Make Physical Connections to Modules ............................. 27
ƒ Step 13: Verify System Release and Module Firmware
Versions.................................................................................................. 29

4021339 Rev B 1
Chapter 1 Quick Start Guide

Step 1: Install the Chassis in a Rack

To Install the Chassis in a Rack
WARNING:
The Prisma II XD Chassis weighs approximately 25 lbs (11.3 kg) empty and 40
lbs (18.1 kg) fully loaded. To avoid personal injury and equipment damage,
use safe handling and lifting practices in accordance with your organization's
procedures.

Complete the following steps to mount the chassis in a 19-inch rack.

1 Use a torque wrench to tighten the bracket mounting screws to 12 to 14 in-lbs
(1.36 to 1.58 Nm).
2 Position the chassis in the rack with the fan assembly installed, but otherwise
empty.
3 Insert a mounting screw through each of the four mounting holes on chassis
front panel, and then into the rack.

4 Use a medium-sized Phillips-head screwdriver to tighten each mounting screw

until it is tight.
5 Install additional cable and fiber management hardware as needed and in
accordance with local practice.

2 4021339 Rev B
 Step 2: Make Chassis-to-Chassis ICIM Connections

Step 2: Make Chassis-to-Chassis ICIM

Connections
Chassis-to-Chassis ICIM Connections
The Prisma II XD platform allows the ICIM2-XD to be located in one chassis and
monitor application modules located in up to four other chassis. This
communication “daisy-chain” can be enabled by connecting cables to the ICIM IN
and ICIM OUT connectors located on the chassis interface panel. Such a connection
is required for an ICIM2-XD in one chassis to communicate with or control any
application module in a separate chassis.
Note: The ICIM2-XD can control up to 64 application modules in a chassis daisy-
chain configuration of up to four chassis.

ICIM IN and ICIM OUT Connectors

Every chassis has a DB9 ICIM IN and a DB9 ICIM OUT connector for the purpose
of chassis-to-chassis ICIM connections. ICIM IN is a female connector and ICIM
OUT is a male connector.

To Make ICIM IN and ICIM OUT Cable Connections

Complete the following steps to make chassis-to-chassis ICIM IN and ICIM OUT
connections.
1 Connect the serial extension cable from the ICIM OUT of the chassis containing
the ICIM2-XD to the ICIM IN connector of the second chassis.
2 Connect a serial extension cable from the ICIM OUT of the second chassis to the
ICIM IN of the third chassis, if installed.
3 Connect a serial extension cable from the ICIM OUT of the third chassis to the
ICIM IN of the fourth chassis, if installed.

4021339 Rev B 3
Chapter 1 Quick Start Guide

4 Change the chassis ID numbers as needed to give each chassis an appropriate

unique ID number. See To Change the Chassis ID Number below for further
details and cautions.
5 Connect a serial extension cable from the ICIM OUT of the second chassis to the
ICIM IN of the third chassis.
6 The ICIM OUT port of the last chassis in the daisy-chain must be terminated
with an ICIM OUT terminator, part number 4013014, which ships with the
ICIM2-XD.

EM In
ICIM Out

Serial Chassis with

Extension ICIM
Cable
ICIM In
ICIM Out

Serial Chassis
Extension
Cable
ICIM In
ICIM Out

Serial
Chassis
Extension
Cable
ICIM In
ICIM Out

Chassis

ICIM Out
Terminator
TP477

Note:
  Up to two chassis can share the use of a single bulk power supply module or pair
of modules. See To Share Power Between Two Chassis (on page 11) for details.
  All chassis connected in this daisy-chain must be powered and have fans
installed. For correct operation, proper cooling of the chassis must be maintained
over the specified temperature range.
  A single chassis equipped with an ICIM2-XD must also have its ICIM OUT port
terminated with an ICIM OUT terminator, part number 4013014. The ICIM OUT
terminator ships with the ICIM2-XD.

To Change the Chassis ID Number

Complete the following steps to change the chassis ID number.

4 4021339 Rev B
 Step 2: Make Chassis-to-Chassis ICIM Connections

1 Locate the chassis ID switch at upper right on the front panel of each chassis. The
switch can be set to any two-digit value from 00 to 99 (but avoid setting the value
to 00, as explained below).

2 Use the chassis ID switch to set each chassis ID number to a unique value.
Note:
  The chassis ID number can be changed while the chassis is under power.
However, the new ID number will not become effective until chassis power is
cycled or the ICIM2-XD is rebooted.
  The chassis numbering scheme used is discretionary, except that each
interconnected chassis must have a unique ID number.
  It is important to avoid using chassis ID number 00 in some circumstances, as
explained in the following caution.
CAUTION:
Setting the chassis ID to 00 is not recommended as it causes the entity MIB to violate
RFC-2737 by creating an invalid object identifier. This may affect operation with some
management systems that use the entity MIB. In particular, attempts to access the fans
(in virtual slot 0) in chassis 00 will fail if made via serial TNCS (or ROSA-EM) or LCI.

Important: If you change the chassis ID number while the chassis is under power,
you must cycle power to the chassis or reboot the ICIM2-XD in order for the new
number to take effect.

ICIM IN and ICIM OUT Cables

The cable required for both ICIM IN and ICIM OUT connections is a shielded 9-
wire serial extension cable, DB9 Female to DB9 Male. This cable can be purchased
locally or from the factory. The chassis data sheet lists the part number for a 6-foot
DB9 Female to DB9 Male serial extension cable. The connectors are a serial 9-pin D-
shell (EIA 574/232).

4021339 Rev B 5
Chapter 1 Quick Start Guide

Step 3: Make Electrical Power Connections

Electrical Power Connections
The chassis back panel has an IEC standard AC power inlet and a three-conductor
DC power connector for each bulk DC power supply module slot.
  The AC power inlet accepts line voltage at 100 to 240 VAC, 50 or 60 Hz.
  The DC power connector accepts DC input voltage at -40 to -72 VDC (-48 VDC
nominal).
The power connectors on the left side of the chassis supply power to the left power
supply slot, while those on the right supply power to the right power supply slot.
Except for their chassis ground pins, all four power connectors are electrically
independent of each other.
Important: Tie the system to earth ground via the ground stud.
Note: For DC power supplies, the return terminal is an "isolated DC return," i.e., it is
not connected to the chassis framework.

Chassis Wiring and Fusing

Important: All chassis configurations require an external fuse or circuit breaker (AC
and DC current ratings differ; see below) and #16 AWG wiring for both power and
grounding.

AC Power Systems
AC power for each AC-to-DC bulk power supply module enters the chassis through
a dedicated back-panel IEC power inlet for each power supply module.
Confirm that the IEC power cord or cords supplied with the chassis have the correct
plug configuration for the country of use.
The voltage input range for AC systems is 100 to 240 VAC, single phase, 50-60 Hz.
AC input current is 14 A maximum. The chassis should be connected to a single
outlet circuit with fuse or circuit breaker overcurrent protection rated 15 A
minimum.

Important:
  Use only a grounded electrical outlet when connecting the unit to a power
source. If you do not know whether the outlet is grounded, consult with a
qualified electrician.
  Maintain reliable earth grounding of rack-mounted equipment. Pay particular
attention to supply and ground connections made via power strips or any

6 4021339 Rev B
 Step 3: Make Electrical Power Connections

method other than direct connection to the branch circuit.

DC Power Systems
External -48 VDC operating power for each DC-to-DC converter (mounted in the
chassis just behind the fan assembly) enters the chassis via a dedicated DC power
inlet mounted on the chassis back panel.
The voltage input range for DC power systems is -40 VDC to -72 VDC.
Use #16 AWG wire for DC field wiring. The #16 AWG wiring from the external -48
VDC supply is attached to a 3-pin nylon connector which, in turn, plugs into the DC
power inlet.
Terminate the chassis side of the cable with a nylon plug of the type supplied with
the chassis. Order additional nylon plugs and connector pins from your preferred
supplier, as follows:
  Molex #03-12-1036 nylon 3-pin connector
  Molex #18-12-1222 crimp socket contact (3)
Use a Molex Crimp Service Tool #63811-1000 or equivalent to crimp the pins to the
cable.
After terminating the cable, twist the conductors loosely (a full turn every few inches
is sufficient).
As installed in the DC power connector with the locking tab down, the left pin of the
nylon connector is the return, the right pin carries -48 VDC, and the center pin is
chassis ground.

Connect the chassis to a reliably grounded DC power source that is electrically

isolated from the AC power source.
Important:
  Branch circuit overcurrent protection must be provided by a fuse or circuit
breaker with a voltage rating of 72 VDC minimum and a current rating of 18 A
maximum.
  The DC field wiring must include a readily accessible disconnect device that is
suitably approved and rated.

4021339 Rev B 7
Chapter 1 Quick Start Guide

Earth-Grounding Conditions
The chassis is designed to permit connection of the earthed conductor of the DC
supply circuit to chassis ground. Before making this connection, confirm that all of
the following conditions are met:
  The chassis is connected directly to the DC supply system earthing electrode
conductor or to a bonding jumper from an earthing terminal bar or bus to which
the DC supply system earthing electrode conductor is connected.
  The chassis is located in the same immediate area as other equipment connected
between the earthed conductor of the same DC supply circuit and earthing
conductor, such as in an adjacent cabinet. Also, the point of earthing of the DC
system must not be earthed elsewhere.
  The DC power source is located within the same premises as the chassis.
  There are no switching or disconnecting devices in the earthed circuit conductor
between the DC source and the point of connection of the earthing electrode
conductor.

DC Power Passing
An XD chassis with at least one AC-to-DC bulk power supply module installed can
serve as an external DC power source for a second XD chassis. Passing DC power
from one chassis to another requires a DC power-passing cable made up as
described above, but with both ends of the cable terminated by a nylon DC power
connector. Two assembled DC power-passing cables are also available from the
factory:
  Part number 4011730, 3 m DC power-passing cable
  Part number 4023718, 2 ft DC power-passing cable

8 4021339 Rev B
 Step 3: Make Electrical Power Connections

Power Inlet Illustration

The following illustration shows locations of the AC and DC power connectors on
the chassis back panel.

To Install the Power Cord

AC Power Cord
Important: The XD chassis is not supplied with an AC power cord. To complete this
procedure, you must order the correct power cord for your region. For ordering
information, see the Prisma II XD Platform Data Sheet, part number 7012804.
Complete the following steps to install an AC power cord for each bulk power
supply module.
1 Confirm the location(s) of bulk power supply modules installed in slot A or slot
B, or both A and B.
2 Insert the IEC plug of each AC power cord into the back-panel IEC power inlet
for each installed bulk DC power supply module.
3 Attach the plug end of each AC power cord into an AC power receptacle.

DC Power Cord
Complete the following steps to install one or more DC power cords for each unused
bulk DC power supply slot as needed.

4021339 Rev B 9
Chapter 1 Quick Start Guide

1 Confirm that each unused bulk power supply slot is empty and covered by a
blanking panel.
2 Locate the DC wire terminal block (white nylon plug) pre-installed in each back-
panel DC power connector.
3 Remove the terminal block and note the locations of the left, middle, and right
terminals as shown below.

4 Obtain conductive pins (Molex #18-12-1222) for each DC wire terminal block for
each conductor to be used.
5 Attach #16 AWG power cable from the fuse panel to the pins and install them in
the terminal block as follows:
ƒ Left terminal: Return conductor
ƒ Middle terminal: Chassis ground (optional)
ƒ Right terminal: -48V DC conductor
6 Insert the wire terminal block into the DC power connector until it locks. Tug
lightly on the terminal block to confirm that it is locked in position.
7 Twist the conductors together loosely along the full length of the power cord (a
full turn every few inches is sufficient).

To Install the Power Supply in the Chassis

Complete the following steps to install an AC-to-DC bulk power supply module in
an available chassis slot.
CAUTION:
Always use a screwdriver to loosen or tighten the screws holding the
application modules, ICIM2-XD, fan assembly, power supply modules, DC-to-
DC converters, or blanking panels in place. Do not attempt to loosen or
tighten these screws solely by hand.
1 On the chassis back panel, loosen the two screws holding the fan assembly in
place. Remove the fan assembly and set it aside temporarily.
2 Remove the blanking panel that covers the bulk power supply slot opening.
3 Pick up the bulk power supply module by its handle and insert the module into
the open module slot, as shown below.

10 4021339 Rev B
 Step 3: Make Electrical Power Connections

4 Gently slide the power supply module into the chassis until its power
connections join connectors on the midplane bus. Do not force the module into the
chassis. If properly aligned, it should slide in with minimal force.
5 If installing a second power supply, repeat the steps above for the second power
supply slot, and then continue with step 6.
6 Confirm that a DC-to-DC converter assembly is installed inside the chassis next
to the new bulk power supply module. This converter will be visible inside the
fan opening, mounted horizontally and held in place by a retaining screw.
7 Reinstall the fan assembly and tighten the two screws holding it and the power
supply module(s) in position.
8 Apply power and verify that the green LED on the front panel of each power
supply module illuminates, indicating normal operation.
9 Confirm that the fan assembly is operational. The fans should be audible once
the power supply is operating.

To Share Power Between Two Chassis

You can set up two XD chassis so that the first operates from AC power and supplies
-48 VDC to the second. This obviates the need for a second bulk DC power supply
module or pair of modules.
The following instructions assume that the first chassis contains two bulk DC power
supply modules.
Complete the following steps to configure two XD chassis for power sharing:
1 If necessary, disconnect AC power from the supply chassis by unplugging the
AC power cords from the AC line.
2 Confirm that the second chassis power supply slot(s) are both empty and
covered by blank panels.

4021339 Rev B 11
Chapter 1 Quick Start Guide

CAUTION:
To preserve proper airflow within the chassis, all unused slots must be
covered by suitable blanking panels, as follows:

ƒ AC-to-DC bulk power supply module blanking panel, part number 4021618

ƒ ICIM2-XD module blanking panel, part number 4021163

ƒ Prisma II XD application module blanking panel, part number 4023066

Failure to observe this precaution may result in equipment malfunction or
reduced operating life due to overheating.
1 Connect a DC power-passing cable from DC power connector A of the first
chassis to DC power connector A of the second chassis, as shown below.
2 Connect a second DC power-passing cable from DC power connector B of the
first chassis to DC power connector B of the second chassis, as shown below.
CAUTION:
When connecting chassis together for power sharing, use either a factory DC
power-passing cable, part number 4011730 (3 m) or 4023718 (2 ft), or a custom
cable made in accordance with the instructions in this document. Use of other
cables for this purpose is not supported.

DC DC
AC OUT A OUT B AC
IN A IN B

Twist Twist
conductors conductors

DC DC
IN A IN B

TP476

12 4021339 Rev B
 Step 3: Make Electrical Power Connections

Note: The steps described above assume that the first chassis contains two AC-to-DC
bulk power supply modules. This is the recommended configuration, as it provides
redundancy in the event of failure of one bulk power supply module or of one DC-
to-DC converter in either or both chassis. Other power configurations are possible.
To request further information, see Customer Support Information (on page 297).

4021339 Rev B 13
Chapter 1 Quick Start Guide

Step 4: Install the ICIM2

To Install the ICIM2-XD
Complete the following steps to install the ICIM2-XD in the chassis.
CAUTION:
Always use a screwdriver to loosen or tighten the screws holding the
application modules, ICIM2-XD, fan assembly, power supply modules, DC-to-
DC converters, or blanking panels in place. Do not attempt to loosen or
tighten these screws solely by hand.
1 Remove the blanking panel covering the ICIM slot in the lower right corner of
the chassis back panel.
2 Hold the ICIM2-XD so that the front panel silkscreen is in correct reading
position.
3 Align the two ridges on the bottom of the ICIM2-XD with the module guide slots
located in the chassis.

4 Gently slide the ICIM2-XD into the chassis until its power and communications
connections join connectors on the back plane bus and its front panel rests
against the chassis. Do not force the ICIM2-XD into the chassis. If properly aligned,
it should slide in with minimal force.
5 Tighten the retaining screws on either side of the ICIM2-XD to secure it in the
chassis. Use a 3/8-in. flat-blade screwdriver to secure. Do not over-tighten.

14 4021339 Rev B
 Step 5: Set Network Parameters from the Command Line Interface (CLI)

Step 5: Set Network Parameters from the

Command Line Interface (CLI)
1 Connect one end of a DB-9 to DB-9 straight-through serial cable to an available
COM port on the personal computer, and the other end to the ICIM2 or ICIM2-
XD front-panel serial port.
2 Open a HyperTerminal session on your laptop (or desktop) PC that you will use
to connect to the ICIM2 or ICIM2-XD. The HyperTerminal program is typically
found at:
Start\All Programs\Accessories\Communication\Hyperterminal
The new Connection Description dialog box appears.

4021339 Rev B 15
Chapter 1 Quick Start Guide

3 Type in a name for the connection, select an icon of your choice, and click OK.
The Connect To dialog box appears.

4 In the Connect Using field, click the drop-down arrow and select the serial port
that you will use for the connection, and then click OK. The COM Properties
dialog box appears.
Note: For most applications, the serial port is COM1 or COM2.
5 Set the following port setting in the COM Properties dialog box.

16 4021339 Rev B
 Step 5: Set Network Parameters from the Command Line Interface (CLI)

6 Click OK. The HyperTerminal main program window appears.

7 On the File menu, click Save to save the settings.

8 Wait for the ICIM2 or ICIM2-XD boot to finish. Once finished, press Enter to
display the ICIM login prompt:
Scientific-Atlanta Intelligent Communications Interface Module (ICIM)
---------------------
W A R N I N G
---------------------
Unauthorized or improper use of this system may result in
administrative disciplinary action and civil or criminal penalties.
By continuing to use this system you indicate your awareness of and
consent to these terms and conditions of use. LOG OFF IMMEDIATELY
if you do not agree to the conditions stated in this warning.

login:
9 Log in using the default username Administrat0r and the default password
AdminPassw0rd. Note the 0 (zero) character in each string.
Scientific-Atlanta Intelligent Communications Interface Module (ICIM)
login: Administrat0r
Password: AdminPassw0rd
Successful login will return the following prompt:
login: Administrat0r
Password:
User Administrat0r logged in successfully on 11/13/06 at 15:25:35
Previous successful login was on 11/13/06 at 15:22:16
There were no failed attempts to login with this user id previously
CLI>
10 Enter the ICIM submenu by typing icim at the CLI> prompt.
CLI> icim
Successful entry into the ICIM menu tree will return the following prompt:
ICIM>

4021339 Rev B 17
Chapter 1 Quick Start Guide

11 Configure the shelf (chassis) IP address, subnet mask, gateway, and clock using
the following commands:
set ip xxx.xxx.xxx.xxx
set subnet xxx.xxx.xxx.xxx
set gateway xxx.xxx.xxx.xxx
set clock "month/day/year hour:minute:second"
Note:
ƒ Be sure to include the quote symbols, e.g., set clock "3/15/2006 13:09:51".

ƒ Clock time is in the 24-hour format.

12 To enable these changes, reboot the ICIM2 or ICIM2-XD as follows:
ICIM> reboot
13 After the ICIM2 or ICIM2-XD reboots, repeat the login steps described above to
return to the ICIM command prompt. Then use the show command to verify
each of the above changes, as follows:
show ip
show subnet
show gateway
show clock
14 Type logout, and then press Enter to exit the session.
15 Remove the serial cable. It is no longer required.
Important:
  For Telnet operation, the computer you are using must have a network
connection through which it can reach the ICIM2 or ICIM2-XD via its IP address.
  No more than four Telnet sessions are allowed at one time.
CAUTION:
Always use the Logout command to close a serial port or Telnet CLI session.
Closing a serial port session without issuing the Logout command leaves the
session open for a possible future connection. This may allow unauthorized
access by a new user if the previous user had a higher authorization privilege
level.

18 4021339 Rev B
 Step 6: Connect the ICIM to the Network

Step 6: Connect the ICIM to the Network

1 Using a Category 5 Ethernet (CAT5) cable, connect the ICIM2 or ICIM2-XD front
panel Ethernet port to your local network.
2 Verify connectivity by pinging the ICIM2 or ICIM2-XD IP address. For example:
C:\> ping 172.18.50.100
Note: The ICIM2 or ICIM2-XD must have an IP address assigned in order to
perform this procedure. This step should have been performed earlier, but if it
was not, perform Step 5: Set Network Parameters from the Command Line
Interface (CLI) (on page 15) before continuing with these instructions.
3 Follow the steps described in To Set up a Telnet CLI Session (on page 19) to set
up a Telnet Session with the ICIM2 or ICIM2-XD.

To Set Up a Telnet CLI Session

Complete the following steps to initiate a CLI session with the ICIM2 or ICIM2-XD
using Telnet.
Important: The ICIM2 or ICIM2-XD must have an IP address assigned before
performing this procedure.
1 Open a DOS window on the PC that will connect to the ICIM2 or ICIM2-XD.
2 At the DOS command prompt, type:
telnet <IP address>
where <IP address> is the IP address of the ICIM2 or ICIM2-XD. The session
starts and the Telnet login: prompt appears.

3 At the login: prompt, type Administrat0r (note the zero character in the string),
and then press Enter.
4 At the Password: prompt, type AdminPassw0rd (note the zero character in the
string), and then press Enter. The CLI> command prompt appears.

4021339 Rev B 19
Chapter 1 Quick Start Guide

Step 7: Install Modules in the Chassis

To Install the Module
WARNING:
Avoid damage to your eyes! Do not look into any optical connector while the
system is active. Even if the unit is off, there may still be hazardous optical
levels present.

Complete the following steps to install the module in the chassis.

CAUTION:
Always use a screwdriver to loosen or tighten the screws holding the
application modules, ICIM2-XD, fan assembly, power supply modules, DC-to-
DC converters, or blanking panels in place. Do not attempt to loosen or
tighten these screws solely by hand.
1 Locate the fiber guides at the bottom of the chassis and the module guide slots
inside the chassis as shown in the following illustration.

2 Align the ridges on the top and bottom of the module with the module guide
slots located on the chassis.
3 Gently slide the module into the chassis until its power and communications
connections join connectors on the midplane bus. Do not force the module into the
chassis. If properly aligned, it should slide in with minimal force.

20 4021339 Rev B
 Step 7: Install Modules in the Chassis

4 Tighten the screw at the top of the module to secure it in the chassis. Use a 3/8-
in. flat-blade screwdriver to secure. Do not over-tighten.
5 Fill any unused chassis slots with module blanks to help ensure proper cooling
air flow.

4021339 Rev B 21
Chapter 1 Quick Start Guide

Step 8: Set Additional Parameters via CLI

(Optional)
Additional parameters may be set as needed from the command line interface (CLI)
for each application module installed.
Refer to Prisma II Permitted CLI Commands (on page 307) and the Prisma II Platform
Remote User Interface Guide, part number 4012441 for information and additional
instructions on available commands and using the CLI.
The following CLI commands are pertinent to most installations.

To Set Additional Users for Telnet or CLI Access

Refer to the Prisma II Platform Remote User Interface Guide, part number 4012441 for
CLI login settings information.
Note: It is strongly recommended that a new administrator login be created and that
the default administrator login be removed.
The table below lists the ICIM mode CLI commands for setting user login
parameters.

Commands Description
ICIM > show user Shows all users
ICIM > user change password [user name] Changes user password
ICIM > user add [user name] [access level] enable Adds a user
ICIM > user delete [user name] Deletes a user

Note: Usernames and passwords must be 6 to 14 characters long and contain at least
1 alphabetic character and at least 1 number.

22 4021339 Rev B
 Step 9: Set and Verify SNMP Community Strings

Step 9: Set and Verify SNMP Community Strings

At the ICIM> command prompt in CLI, use the set command to change the SNMP
Community write, read, and trap strings to corresponding user-defined strings to
allow for remote monitoring and control via a network management system (NMS).
After entering these commands, use the info command to verify the new settings.
The sample dialog below shows how to enter these commands. In the example
below:
  myCommWriteString is the user-defined community write string.
  myCommReadString is the user-defined community read string.
  myCommTrapString is the user-defined community trap string.
Refer to SNMP Management for SNMP parameter information.
From the CLI command prompt, switch to ICIM command mode and define SNMP
Read, Write, and Trap Community strings, as shown below.
CLI> icim
ICIM> set commwrite “myCommWriteString”
NOTE: This change will not fully take effect until the ICIM is restarted.
Until that time, some operations will not perform as expected.
SUCCESS!
ICIM> set commread “myCommReadString”
NOTE: This change will not fully take effect until the ICIM is restarted.
Until that time, some operations will not perform as expected.
SUCCESS!
ICIM> set commtrap “myCommTrapString”
NOTE: This change will not fully take effect until the ICIM is restarted.
Until that time, some operations will not perform as expected.
SUCCESS!

You can then verify the community string settings, as follows.

ICIM> info commread commwrite commtrap
COMMREAD COMMWRITE COMMTRAP
myCommReadString myCommWriteString myCommTrapString
SUCCESS!
ICIM>

Note:
  We strongly recommend restarting the ICIM2 or ICIM2-XD after changing any of
the community strings. Otherwise, some operations will continue to work
normally, while others will appear to fail.
  We strongly recommend creating new SNMP community strings and removing
the default SNMP community strings. Default SNMP community string values
are listed below.

4021339 Rev B 23
Chapter 1 Quick Start Guide

SNMP Community String Default Value

Read Community public
Write Community private
Trap Community SNMP_trap

24 4021339 Rev B
 Step 10: Perform Chassis-to-Chassis ICIM Activation (Optional)

Step 10: Perform Chassis-to-Chassis ICIM

Activation (Optional)
Once the chassis are interconnected, the shared ICIM2 or ICIM2-XD should be
forced to search for all new modules, rather than be allowed to find them
incrementally over the course of a polling cycle.
The recommended method for forcing a search for new modules is to reboot the
ICIM2 or ICIM2-XD. This can be accomplished either by physically removing and
reinserting the ICIM2 or ICIM2-XD module or by issuing a reboot command via the
CLI interface.
To reboot the ICIM2 or ICIM2-XD module via CLI, open a console session and type
the following commands at the CLI prompt.
CLI> icim
ICIM> reboot

The response will be:

The ICIM2 is about to reboot. This will end all current login and web sessions
Are you sure you want to proceed (Yes/No)> yes
SUCCESS!
ICIM>
Scientific-Atlanta Intelligent Communications Interface Module (ICIM)
---------------------
W A R N I N G
---------------------
Unauthorized or improper use of this system may result in
administrative disciplinary action and civil or criminal penalties.
By continuing to use this system you indicate your awareness of and
consent to these terms and conditions of use. LOG OFF IMMEDIATELY
if you do not agree to the conditions stated in this warning.
login:

Each of the additional modules will then be added to the ICIM2 or ICIM2-XD polling
cycle.
Note: Use of the CLI reboot command is preferred over the updateid command in
this case because a reboot will maintain synchronization with the element
management system.

4021339 Rev B 25
Chapter 1 Quick Start Guide

Step 11: Make Changes to Traps and Enterprise

MIBs
Trap settings and other parameters can be set in either of two ways:
  Using Simple Network Management Protocol (SNMP) commands. Refer to
SNMP Management (on page 171) for details on accessing the ICIM MIB tables.
  Using the Command Line Interface (CLI) traps enable command. Refer to the
Prisma II Platform Remote User Interface Guide, part number 4012441 for details on
using this command.
Once this is accomplished, changes can be made to the entries in the ICIM Trap
table. There are 10 entries in this table, one for each destination IP address.
Following are the objects in the p2TrapRecvEntry table that should be set.

MIB Object Value

p2TrapRecvEnable 1-disabled; 2-enabled
p2TrapRecvAddr IP address of trap receiver
p2TrapRecvTelcoAlarm 1-disabled; 2-enabled

MIB Software
MIBs are available in the software system release and should be compiled in your
SNMP tool. They are labeled as follows:
  SCIATL-PRISMAII-ICIM-MIB.mib
  SCIATL-PRISMAII-MODULE-MIB.mib

Trap Overview
The Prisma II system can be configured to provide various alarm and warning
conditions to an NMS or system monitor application.
There are nine different trap categories that can be independently enabled to provide
the desired level of information on events occurring in a system. These traps can be
forwarded to up to 10 different IP addresses. The trap filtering can be configured
uniquely for each user.
See SNMP Management (on page 171) for trap details.
Note: All trap types (module insertion, alarm events, etc.) are reported through the
Enhanced Alarm trap. Therefore, only the Enhanced Alarm traps are enabled by
default, and this is the recommended configuration.

26 4021339 Rev B
 Step 12: Make Physical Connections to Modules

Step 12: Make Physical Connections to Modules

Once all configuration changes are complete, you are ready to make the physical
connections to the modules.

To Make Transmitter RF Connections

1 Note the chassis slot number in which an optical transmitter module is installed
(e.g., slot 5).
2 Connect a coaxial cable to RF input port A of the corresponding slot number
(e.g., slot 5) for broadcast input.
3 Check the optical transmitter test point for input modulated analog carrier levels
at 27 dBmV and digital carrier levels at 21 dBmV.
Note:
ƒ Levels will vary based on local channel load. Anticipated channel loads are
24-28 dBmV for analog, and roughly 6 dB less for digital.
ƒ The optical transmitter test point is 20 dB down from the RF input level.
4 At the CLI> prompt, enter module command mode and verify with the ICIM2 or
ICIM2-XD that the RF drive level is zero on the RF drive scale, as follows:
CLI> module
*/* MODULE> chassis x slot y
x/y MODULE> show monitor inrf
where x is the module chassis number and y is the module slot number. In
response, the MODULE> prompt will change to show the chassis and slot
selected.
5 Verify that the automatic gain control (AGC) is turned on through CLI or
through the ICIM2 or ICIM2-XD as follows (note that the MODULE> prompt has
now changed to show chassis 1, slot 5 selected):
01/05 MODULE> show control agc
MODID NAME SETTING UNITS
01/05 AGC On (1)
6 Repeat the steps above for each optical transmitter module installed in the
chassis.
7 Make all necessary optical connections as described below.

To Connect Optical Cables

CAUTION:
High power density exists on fiber when optical power is present. To avoid
microscopic damage to fiber mating surfaces, turn off optical power or reduce
power below 15 dBm before making or breaking optical connections.

4021339 Rev B 27
Chapter 1 Quick Start Guide

Complete the following steps for each optical cable connection to be made and on
every module to be installed.
1 Clean the end of the fiber to be connected as described in Cleaning Optical
Connectors (on page 292).
2 Connect the optical cable to the module connector.
3 Route the cable to the appropriate destination.
4 Clean the remaining cable end, and then connect the cable to the mating module
connector.
Note: Remember to observe minimum bend radius and other accepted handling
practices when working with fiber-optic cables.
5 After cable installation is complete, return the module control settings to their
original states.
6 After all optical connections are made, enable the optical output (or turn off
Service mode) from each optical amplifier via CLI, as shown in this example:
01/05 MODULE> set control enable on
Note: All pre- and post-amplifier modules ship from the factory in the disabled
optical output mode for safety reasons.
7 As a check, verify that there are no active alarms within the ICIM2 or ICIM2-XD
domain via CLI, as shown in this example:
01/05 MODULE> alarm
No active alarms found
Note: Alarms can also be checked via NMS or through the ICIM2 or ICIM2-XD.
8 Make additional changes to other module options per local company practices
using CLI commands. See the Prisma II Platform Remote User Interface Guide, part
number 4012441 for further instructions as needed.

28 4021339 Rev B
 Step 13: Verify System Release and Module Firmware Versions

Step 13: Verify System Release and Module

Firmware Versions
To check the current firmware revision levels in all modules in the ICIM2 or ICIM2-
XD domain, enter the following CLI command at the ICIM> prompt:
ICIM> show domain

A column labeled ACTIVEREV in the response lists the active firmware revision
numbers for each module in the domain.

4021339 Rev B 29
 2 Chapter 2
Introduction
Overview
This guide describes the Prisma II™ Extreme Density (XD) Platform.
This platform consists of the Prisma II XD Chassis and its power
supplies, fan assembly, application modules, and control systems.

Purpose
This guide provides information and instructions for implementing
the Prisma II XD Chassis, internal components, and external control
systems.

Who Should Use This Document

This document is intended for authorized service personnel who have
experience working with similar equipment. The service personnel
should have appropriate background and knowledge to complete the
procedures described in this document.

Qualified Personnel
WARNING:
Allow only qualified and skilled personnel to install, operate,
maintain, and service this product. Otherwise, personal injury or
equipment damage may occur.

4021339 Rev B 31
Chapter 2 Introduction

Only appropriately qualified and skilled personnel should attempt to

install, operate, maintain, and service this product.

Scope
This guide discusses the following topics.
  The Prisma II XD Platform and its components
  Installation procedures
  Equipment configuration
  Features of the ICIM2-XD control module
  Local Command Interface (LCI) operation
  User management
  Event log
  SNMP management
  Chassis maintenance and troubleshooting
  CLI command reference
  Features available via remote user interface
  Descriptions of module parameters

Document Version
This is the second release of this guide (Rev B).

In This Chapter
ƒ Related Publications ............................................................................. 33
ƒ Prisma II XD Platform .......................................................................... 34
ƒ Prisma II XD Chassis ............................................................................ 39
ƒ XD Chassis Fan Assembly ................................................................... 47
ƒ AC-to-DC Bulk Power Supply Modules ........................................... 48
ƒ DC-to-DC Converters........................................................................... 52
ƒ Prisma II ICIM2-XD.............................................................................. 53

32 4021339 Rev B
 Related Publications

Related Publications
You may find the following publications useful as you implement the procedures in
this document.
  Prisma II Platform Remote User Interface Guide, part number 4012441
  Prisma II™ High Density Dual Reverse Receiver Installation and Operation Guide, part
number 4015908
  Prisma II™ 1550 nm High Density QAM Transmitter Installation and Operation
Guide, part number 4019959
  Prisma II™ High Density Forward Receiver Installation and Operation Guide, part
number 4020002
  Prisma II™ 1310 nm High Density Transmitter Installation and Operation Guide, part
number 4009700
  Prisma II™ Multi-Wavelength High Density Transmitter Installation and Operation
Guide, part number 4023013

4021339 Rev B 33
Chapter 2 Introduction

Prisma II XD Platform
The Prisma II XD Platform is a configurable and expandable system for providing
transmit and receive functions to fiber-optic communications networks.

The Prisma II XD Platform can be configured for use in a variety of environments,

from CATV headends and hubs to Telecom central offices.
Key features of the Prisma II XD Platform are:
  High module density
  Broad operating temperature range
  Rapid installation and setup
  Support for local and remote system monitoring and control

XD Platform Components
The Prisma II XD Platform consists of the following products.
  Prisma II XD Chassis
  Prisma II XD fan assembly
  Prisma II XD AC-to-DC bulk power supply modules (one or two)
  Prisma II ICIM2-XD Intelligent Communications Interface Module
  Prisma II High-Density Platform application modules
  Prisma II XD Chassis application module blanking panels
Note: The ICIM2-XD can control up to 64 application modules in a daisy-chain
configuration of up to four full chassis.

34 4021339 Rev B
 Prisma II XD Platform

XD Chassis
The chassis houses all other system components. A midplane bus system inside the
chassis distributes electrical power to all installed modules. The midplane bus
system also transports communication and control signals between installed
application modules and the ICIM2-XD.

XD Chassis Fan Assembly

The chassis uses a negative pressure fan system to pull cooling air from the ambient
environment. Three fans are housed in a field-replaceable assembly attached at the
back of the chassis.
The fan assembly can be removed for inspection and maintenance, to provide access
to the DC-to-DC converters inside the chassis, or to remove either of the AC-to-DC
bulk power supply modules.

Chassis Power Supply Architecture

The chassis can operate from utility AC power or from external -48 VDC power.
For AC operation, one or two AC-to-DC bulk power supply modules are installed in
the chassis. Each of these modules supplies -48 VDC power to one of two DC-to-DC
converter assemblies inside the chassis. The DC-to-DC converter assemblies, in turn,
generate the midplane bus working voltages at +24, +5, and -5 VDC.
A single AC-to-DC bulk power supply module is sufficient to operate two fully
populated chassis. Installing a second AC-to-DC bulk power supply in one chassis
adds redundancy in the event of a power supply module failure.
For DC operation, one or both AC-to-DC bulk power supply modules are removed,
and power for one or both internal DC-to-DC converter assemblies is supplied from
a battery room, another XD chassis, or some other external -48 VDC power source.
External DC power enters the chassis via a DC power connector associated with each
power supply module slot.
The DC power connector can serve one of two functions, depending on the power
supply configuration:
  When the associated AC-to-DC bulk power supply slot is empty, its DC power
connector acts as an inlet for external -48 VDC.
  When the associated AC-to-DC bulk power supply slot is populated, its DC
power connector acts as an outlet for -48 VDC from the bulk power supply
module.
This functionality enables two chassis to be interconnected via their DC power
connectors so that the power supply module(s) in one chassis provide operating
power for the second chassis.

4021339 Rev B 35
Chapter 2 Introduction

CAUTION:
A single DC power connector cannot act as in input and an output connector at
the same time. Before applying external DC power, confirm that the AC-to-DC
bulk power supply slot associated with the DC power connector is empty and
covered by a blanking panel.

CAUTION:
To preserve proper airflow within the chassis, all unused slots must be
covered by suitable blanking panels, as follows:

ƒ AC-to-DC bulk power supply module blanking panel, part number 4021618

ƒ ICIM2-XD module blanking panel, part number 4021163

ƒ Prisma II XD application module blanking panel, part number 4023066

Failure to observe this precaution may result in equipment malfunction or
reduced operating life due to overheating.

CAUTION:
When connecting chassis together for power sharing, use either a factory DC
power-passing cable, part number 4011730 (3 m) or 4023718 (2 ft), or a custom
cable made in accordance with the instructions in this document. Use of other
cables for this purpose is not supported.

The following diagram shows the general power supply architecture for a single
Prisma II XD Platform chassis.
+24 VDC

+5 VDC

-5 VDC

0 VDC

Application Module Power Bus

DC-to-DC DC-to-DC
Converter Converter
Module A Module B

RETURN RETURN
AC-to-DC AC-to-DC
Bulk Supply -48 VDC -48 VDC Bulk Supply
Module A Module B

AC DC DC AC
IN A IN/OUT IN/OUT IN B
A B
TP552

36 4021339 Rev B
 Prisma II XD Platform

As shown above, each AC-to-DC bulk power supply module feeds a separate,
dedicated DC-to-DC converter assembly. The chassis ships with two DC-to-DC
converters installed, but without either AC-to-DC bulk power supply module
installed.
Each DC-to-DC converter can power a full chassis on its own. The use of dual
independent converters, together with dual AC-to-DC bulk power supplies, allows
for full power supply redundancy.

Power Sharing
Routing of -48 VDC power from an AC powered chassis to a second chassis is
achieved by connecting a DC power-passing cable between the DC power
connectors of the two chassis. Two such cables are currently available from the
factory:
  Part number 4011730, 3 m DC power passing cable
  Part number 4023718, 2 ft DC power passing cable
CAUTION:
When connecting chassis together for power sharing, use either a factory DC
power-passing cable, part number 4011730 (3 m) or 4023718 (2 ft), or a custom
cable made in accordance with the instructions in this document. Use of other
cables for this purpose is not supported.

WARNING:
Any external power supply must provide proper electrical components to
power the chassis or risk serious equipment damage or personal injury.

ICIM2-XD
The Prisma II Intelligent Communications Interface Module 2 for the XD platform
(ICIM2-XD) provides users with access to application module configuration settings,
status monitoring, and alarm monitoring.
The ICIM2-XD is logically identical to the ICIM2 module designed to fit the Prisma II
Platform chassis. However, the ICIM2-XD is physically smaller than the ICIM2 and
lacks a front-panel keypad or liquid-crystal display. Because of these physical
differences, the ICIM2-XD can only be installed in an XD chassis and an ICIM2 can
only be installed in a Prisma II chassis.
Note: When a Prisma II chassis and a Prisma II XD chassis are part of a daisy-chain
connection of two or more chassis, a single ICIM2 or ICIM2-XD can and must be
used to control both chassis.

4021339 Rev B 37
Chapter 2 Introduction

XD Application Modules
Prisma II XD application modules perform a prescribed set of independent transmit
or receive functions. These modules install from the front of the chassis, are hot-
swappable, and have plug-and-play capability.
All XD application modules share a common half-height, high-density form factor.
Four modules are currently available:
  Prisma II 1310 nm High Density Transmitter
  Prisma II 1550 nm High Density QAM Transmitter
  Prisma II High Density Forward Receiver
  Prisma II High Density Dual Reverse Receiver
Additional applications may become available in the future. For further information,
contact Scientific Atlanta using the information provided in Customer Support
Information (on page 297).
Detailed information about each application module is provided in the installation
and operation guide for that module. For document ordering information, see
Related Publications (on page 33).

38 4021339 Rev B
 Prisma II XD Chassis

Prisma II XD Chassis
The XD chassis houses the fan assembly, one or two AC-to-DC bulk power supply
modules, a chassis control board (CCB), two internal DC-to-DC converter
assemblies, the ICIM2-XD, and up to 16 high-density application modules.
Through an internal midplane bus, the chassis provides modules with electrical
power, a shared serial bus, a high-speed ICIM2-XD data bus, and connections to two
back-panel RF connections per application module. The midplane interface is
designed so that application modules can be replaced even when the system is
under power and fully operational.
Ports on the front and back of the chassis support external communication with an
ICIM2 or ICIM2-XD via the midplane bus. This communication enables system
management via local craft interface (LCI), command line interface (CLI), hypertext
transfer protocol (HTTP), or Simple Network Management Protocol (SNMP)
commands.
A fiber tray built into the chassis provides strain relief and facilitates front-to-back
routing for optical cables connected to the application modules.

Chassis Features
The chassis has several noteworthy operational features, including hot-swap,
resource sharing, and redundancy. These are described in more detail below.

Hot-Swap (Application Modules and ICIM2-XD)

The chassis and its application modules embody several design features that help to
ensure a smooth and non-destructive module hot-swap.
  The ICIM2-XD and chassis control board have circuits that limit inrush current to
no more than 120% of the maximum allowed for each power bus.
  Each module contains bus isolation and power management circuits to ensure a
gentle power ramp-up. This reduces the possibility of arcing and voltage spikes.
  The system software notifies the ICIM2-XD of a hot-swap as soon as it occurs,
rather than when the ICIM2-XD polls for information. This results in faster status
updates.
  The connector pins on each module are staged, so that the first connection made
on insertion and the last connection broken on removal is ground, followed by
power, and finally, the signal pins.

4021339 Rev B 39
Chapter 2 Introduction

CAUTION:
For a chassis under power, field replacement of the fans, AC-to-DC bulk
power supply modules, or DC-to-DC converter assemblies must be completed
in two minutes or less to prevent possible chassis overheating due to
temporary removal of the fan assembly.

CAUTION:

ƒ Before removing an AC-to-DC bulk power supply module from the chassis, disable
AC input power to the module by disconnecting the associated AC power cord.

ƒ Before removing a DC-to-DC converter assembly from the chassis, disable DC input
power to the converter assembly by disconnecting the associated AC power cord (if
AC operated) or DC power-passing cable (if DC operated).

ƒ Do not disable power to both sides of the chassis at the same time when such action
may cause a loss of service.

Resource Sharing
The AC-to-DC bulk power supply modules and the ICIM2-XD control module are
resources that can be shared by multiple chassis.
An AC-to-DC bulk power supply module installed in one chassis can provide
operating power for a second chassis by connecting a DC power-passing cable
between the two chassis. Power sharing saves cost and improves polling cycle times
by reducing the number of intelligent modules, and thus the polling overhead,
associated with each chassis.
The ICIM2-XD in one chassis can be used to control modules installed in up to three
additional chassis (four chassis total) through a series "daisy chain" connection from
the ICIM OUT port of the first chassis to the ICIM IN port of the second, and so on.

Redundancy
Terminal blocks on the back panel of the chassis provide ALARM IN and ALARM
OUT control lines for each of the 16 application module slots (32 alarm signal lines
total). The alarm outputs are brought HIGH (+5 VDC) by hardware or software
during module removal or other fault condition. The alarm signal lines allow for
external configuration of redundancy options, including the option to locate master
and slave modules in separate chassis.

Chassis Configuration
The chassis has front slots that support up to 16 Prisma II XD half-height, high-
density application modules. Two slots on the chassis back panel accept up to two
AC-to-DC bulk power supply modules. A third slot on the back holds the ICIM2-XD
control module.

40 4021339 Rev B
 Prisma II XD Chassis

Chassis and Slot Numbering

For management purposes, every chassis in an ICIM2 or ICIM2-XD domain is
assigned a unique chassis number. The chassis has a switch on the front panel that
permits selection of a chassis ID number from 00 through 99.
Note: It is important to avoid using chassis ID number 00 in some circumstances, as
explained in the following caution.
CAUTION:
Setting the chassis ID to 00 is not recommended as it causes the entity MIB to violate
RFC-2737 by creating an invalid object identifier. This may affect operation with some
management systems that use the entity MIB. In particular, attempts to access the fans
(in virtual slot 0) in chassis 00 will fail if made via serial TNCS (or ROSA-EM) or LCI.

Each application module installed in the chassis is identified by a unique slot

number from 1 to 16. Together with the chassis numbers, these slot numbers enable
network management software to address each application module individually.
Note: The fan assembly and ICIM2-XD module installed in the chassis back panel
have the following virtual slot number assignments.

Module Virtual Slot

Fan assembly 00
ICIM2-XD control module 17

Typical Chassis Block Diagram

The block diagram below shows a typical Prisma II XD Chassis configuration with
two power supplies, an ICIM2-XD, and several application modules installed.
AC Power AC Power
-48 VDC -48 VDC
Input A Input B
Power Power
In/Out A In/Out B
Ethernet RS-232
Port CLI Port In Out
RF AC-to-DC AC-to-DC
Bulk Power Bulk Power
Alarm
ICIM2-XD Supply A Supply B
Interface

DC-to-DC DC-to-DC
Converter A Converter B
Signals &
- 48 VDC Voltages - 48 VDC
In +24 / +5 / -5 VDC In

Midplane Power and Data Bus

Fan
Module 1 Module 2 Module n Front Panel
Assembly
Interface

Status ID LCI Port

TP473 LEDs Switch DB-9

4021339 Rev B 41
Chapter 2 Introduction

Chassis Illustrations
The following illustration shows the front of the chassis as it appears when filled
with application modules. The LED indicators, chassis ID switch, and LCI port are
visible across the top panel.

The following illustration shows the back of the chassis as it appears with both
power supplies and the ICIM2-XD installed. The fans, I/O connectors, RF
connectors, and power inlets are located as indicated on the back of the chassis.

Chassis Front Panel Features

Part Function
ESD Jack ESD (electrostatic discharge) jack, to be used before touching any
modules.

42 4021339 Rev B
 Prisma II XD Chassis

Part Function
ON LED (green) Indicates the presence of +5 VDC on the chassis midplane bus.
Flashes to indicate active ICIM2-XD communication via the LCI
port.
At power-up, flashes to indicate failure of chassis self-test.
ALARM LED (red) Indicates a fault condition in one or more installed application
modules.
Glows steadily to indicate a critical fault condition.
Flashes to indicate a non-critical fault condition.
At power-up, flashes to indicate failure of chassis self-test.
ICIM LED (green) Illuminates to indicate that an ICIM2-XD is installed.
Chassis ID Switch Located at the top right of the front panel, allows the operator to
assign an identification number to every chassis for addressing via
the ICIM2-XD or through CLI or SNMP commands. In the ICIM2
front-panel interface, this number is referred to as the Shelf
number.
Note: Every chassis daisy-chained to an individual ICIM2 or
ICIM2-XD must have a unique chassis ID number.

Chassis Back Panel Features

Part Function
ESD Jack ESD (electrostatic discharge) jack, to be used prior to touching any
modules.
ALARMS Allows for an ALARM OUT connection and an ALARM IN connection
IN/ALARMS OUT for each module slot in the chassis.
EM IN/EM OUT An RS-485 bus that enables serial communication with the ICIM2-XD
using Transmission Network Control System (TNCS) or another
element management system.
ICIM IN/ICIM OUT A dedicated bus that enables serial communication between the ICIM2-
XD and modules in other chassis for control and monitoring purposes.
Power Supply Inlets One or two AC-to-DC bulk power supply modules can be installed in
the chassis. Utility AC power enters via a standard IEC power
connector.
A DC power connector for each bulk power supply slot provides -48
VDC output when using one chassis to power a second through a
power-chain connection. Or, if the associated bulk power supply slot is
not populated, this DC power connector serves as a -48 VDC input for
DC operation.
Ground Studs Ground studs.

4021339 Rev B 43
Chapter 2 Introduction

Part Function
RF Connectors A pair of RF connectors for each application module slot (1-16) support
up to two independent RF ports per module.

Chassis Midplane
The chassis midplane provides bus connections for distribution of power and
communication signals. The midplane also connects two RF ports on the module
back panel to each of the 16 application module slots.
The chassis midplane layout is shown below.

Fan Assembly
The fan assembly is installed in the back of the chassis at the factory. It is held in
place by two screws, one on either side of the assembly. The assembly can be
removed as a unit for periodic maintenance or inspection. Tools are needed to
remove or install the fan assembly.
The fan assembly must be removed to install or remove either of the AC-to-DC bulk
power supply modules, or to gain access to the DC-to-DC converter assemblies
mounted in the chassis just behind the fans.
Important: Do not operate the chassis for more than two minutes without the fan
assembly installed. For safe operation, proper cooling of the chassis must be
maintained over the specified temperature range.
CAUTION:

ƒ Before removing an AC-to-DC bulk power supply module from the chassis, disable
AC input power to the module by disconnecting the associated AC power cord.

ƒ Before removing a DC-to-DC converter assembly from the chassis, disable DC input
power to the converter assembly by disconnecting the associated AC power cord (if
AC operated) or DC power-passing cable (if DC operated).

ƒ Do not disable power to both sides of the chassis at the same time when such action
may cause a loss of service.

44 4021339 Rev B
 Prisma II XD Chassis

Midplane Bus Connectors

The connectors on the chassis midplane bus accommodate electrical power, digital
signals, and analog signals for each module. All connectors are self-guiding and
allow a blind-mate connection.

XD Chassis Control Board

The chassis has an internal chassis control board that provides the following
functions:
  Fan monitoring and control
  AC-to-DC bulk power supply monitoring
  DC-to-DC converter monitoring
  Chassis temperature monitoring
  LED control
  Alarm signaling
Each of these functions is described in greater detail below.

Fan Monitoring and Control

The chassis control board monitors and controls all fans used for chassis air
circulation. It reports an alarm (Fan1_Ok, Fan2_Ok, Fan3_Ok) if any of the three fans
in the fan assembly is disconnected, broken, or jammed. It monitors internal chassis
temperature (ChasTemp), disables all three fans if the temperature falls below 0°C,
and enables all three fans if the temperature rises above 10°C.

AC-to-DC Bulk Power Supply Monitoring

The chassis control board monitors the following AC-to-DC bulk power supply
conditions:
  AC-to-DC bulk power supply module A installed (PSA Inst)
  AC-to-DC bulk power supply module B installed (PSB Inst)
PSA Inst and PSB Inst monitor for two conditions at their respective power supply
slots. First, they check whether an AC-to-DC bulk power supply module is installed.
If the power supply module is installed, they then check for the presence of AC
input power to that slot. The absence of AC input power to a populated power
supply slot will trigger an alarm condition.
This alarm behavior can be temporarily muted for slot A (AlmMuteA) or slot B
(AlmMuteB) to prevent alarms from occurring during servicing. For example,
muting can be used to prevent an alarm when temporarily removing AC input
power to a populated power supply slot during field replacement of a DC-to-DC
converter.

4021339 Rev B 45
Chapter 2 Introduction

DC-to-DC Converter Monitoring

The chassis control board monitors the following DC-to-DC converter module
conditions:
  DC-to-DC converter A -48 VDC input (ConvAIn)
  DC-to-DC converter B -48 VDC input (ConvBIn)
  DC-to-DC Converter A +24 VDC output (ConvA+24)
  DC-to-DC Converter B +24 VDC output (ConvB+24)
  DC-to-DC Converter A +5 VDC output (ConvA+5)
  DC-to-DC Converter B +5 VDC output (ConvB+5)
  DC-to-DC Converter A -5 VDC output (ConvA-5)
  DC-to-DC Converter B -5 VDC output (ConvB-5)

Chassis Temperature Monitoring

The chassis control board monitors the internal temperature of the chassis and
reports an alarm if the temperature (ChasTemp) falls outside normal limits.

LED Control
The chassis control board controls three front-panel LED indicators:
  The On LED lights to indicate that the midplane bus has all required DC
operating voltage.
  The Alarm LED blinks to indicate a minor alarm, and glows steady to signal a
major alarm.
  The ICIM LED lights to indicate that an ICIM2-XD module is installed in the
chassis.

Alarm Signaling
The chassis control board has alarm-out contacts to control an external alarming
device triggered by an event. It can also read an input alarm from an external source.
These two lines are routed to ALARM IN and ALARM OUT connectors on the back
of the chassis.

Fuse Protection
The chassis control board is protected by a fuse to reduce the chance of losing the
entire chassis in the event of a component failure on the board. This fuse is soldered
in place, and is not intended to be replaced in the field.

46 4021339 Rev B
 XD Chassis Fan Assembly

XD Chassis Fan Assembly

The fan assembly cools the chassis and its application modules. The fan assembly
also contains the sensor circuits that provide temperature and power supply status
information to monitoring devices.

Fan Operation
Cooling air is allowed to enter the front of the chassis through perforated panels on
either side of the fiber tray. The fans draw air through these panels, up through the
cooling fins of the application modules, across the inside top of the enclosure, and
out the back of the chassis.
Note: The AC-to-DC bulk power supply modules contain their own smaller fans for
cooling the power supply circuits. These fans work independently of the chassis fan
assembly.

Fan Assembly Illustration

4021339 Rev B 47
Chapter 2 Introduction

AC-to-DC Bulk Power Supply Modules

The chassis AC-to-DC bulk power supply modules convert incoming AC utility
power to -48 VDC. This DC voltage feeds a separate DC-to-DC converter for each
bulk power supply module inside the chassis to produce +24, +5, and -5 VDC chassis
working voltages. These voltages are made available to the ICIM2-XD and all
application modules via the chassis midplane bus.
Two dedicated slots for AC-to-DC bulk power supply modules are located in the
back of the chassis. The use of two power supply systems allows for redundant
power feeds. The AC-to-DC bulk power supply modules are held in place by tabs on
either side of the fan assembly. Installation or removal of a bulk power supply
module or its associated DC-to-DC converter requires temporary removal of the fan
assembly.
CAUTION:
For a chassis under power, field replacement of the fans, AC-to-DC bulk
power supply modules, or DC-to-DC converter assemblies must be completed
in two minutes or less to prevent possible chassis overheating due to
temporary removal of the fan assembly.

Power Sharing
The -48 VDC output from an AC-to-DC bulk power supply module in one XD
chassis can be passed to a second XD chassis. A DC-to-DC converter in the second
chassis then uses the external -48 VDC to provide local working voltages to the
chassis midplane bus. This bulk power-sharing scheme avoids the need to purchase
a new set of bulk power supply modules when adding a chassis.
If two AC-to-DC bulk power supplies are installed in one XD chassis, the DC output
from each bulk supply can be passed to the corresponding DC input of a second
chassis. This scheme provides redundant power for both chassis: if one bulk DC
power supply should fail, the remaining power supply takes the full load for both
chassis.

Power Supply Configurations

A Prisma II XD Chassis can operate with one or two AC-to-DC bulk power supply
modules installed, or with no bulk power supplies installed if external -48 VDC is
applied to the chassis at one or both back-panel DC power connectors. The chassis
thus supports a wide range of power supply configurations, subject to two
requirements:
  If an AC-to-DC bulk power supply slot is populated, its corresponding DC
power connector cannot be used as a power inlet.
  If an AC-to-DC bulk power supply slot is empty, its corresponding DC power

48 4021339 Rev B
 AC-to-DC Bulk Power Supply Modules

connector cannot be used as a power outlet.

Not all of the possible power supply configurations satisfy both of these
requirements. The following table lists all possible configurations and identifies
those which are valid.

Power Power External External Configuration

Supply A Supply B -48 VDC A -48 VDC B Status
- - - Applied Valid
- - Applied - Valid
- - Applied Applied Valid
- Installed - - Valid
- Installed - Applied -
- Installed Applied - Valid
- Installed Applied Applied -
Installed - - - Valid
Installed - - Applied Valid
Installed - Applied - -
Installed - Applied Applied -
Installed Installed - - Valid
Installed Installed - Applied -
Installed Installed Applied - -
Installed Installed Applied Applied -

Important: Only the power supply configurations identified as valid above are
supported. Other configurations may produce unexpected results, and therefore are
not supported.

DC-to-DC Converter Alarms

Two alarm parameters, ConvAIn (converter A input) and ConvBIn (converter B
input), are designed to alert the operator in the event of a loss of DC input power to
the chassis. Each alarm activates if the associated AC-to-DC bulk power supply slot
is empty and there is no DC power at the associated DC power connector.
Important:
  If both sides of the chassis lose DC power, no converter alarms are (or can be)
generated.
  Chassis configurations in which an AC-to-DC bulk power supply slot is empty
but intentionally not supplied with external DC power will generate a converter
alarm unless the muted using the AlmMuteA or AlmMuteB control parameters.

4021339 Rev B 49
Chapter 2 Introduction

Electrical Input Voltages

  AC-to-DC bulk power supply modules accept AC input in the range of 100 to
240 VAC.
  DC-to-DC converter assemblies accept DC input in the range of -40 to -72 VDC
and deliver +24, +5, and -5 VDC output to the chassis midplane.

Power Inlets
Two sets of power inlets are available on the chassis back panel to match the
electrical power source available at different installation sites.
  The DC power inlets accept a nominal -48 VDC input (-40 to -72 VDC). When not
used as an input, these connectors can be used to route -48 VDC out for use by
other chassis.
  The AC power inlets accept local utility power (100 to 240 VAC, 50 or 60 Hz) via
standard IEC power inlets.
The DC power inlets are provided with locking three-wire terminal blocks, which
come pre-inserted in the DC power inlets.
Important: Use an equipotential bonding conductor to make a connection from the
chassis ground stud to a reliable earthing mechanism at the installation site. For
additional information, refer to EN 50083-1/A1:1977.
Note: The chassis ships with the CCB, fan assembly, and DC-to-DC converter
assemblies and with no AC-to-DC bulk power supplies installed. The chassis can be
ordered with or without an ICIM2-XD installed. See the Prisma II XD Platform Data
Sheet, part number 7012804 for ordering information.

50 4021339 Rev B
 AC-to-DC Bulk Power Supply Modules

AC-to-DC Bulk Power Supply Illustration

AC-to-DC Bulk Power Supply Features

Part Function
AC OK LED Amber ON – AC OK
Amber OFF – No AC
DC OK LED Green ON – DC OK
Green OFF – No DC
Internal fan Locally controlled by the power supply thermostat

4021339 Rev B 51
Chapter 2 Introduction

DC-to-DC Converters
All XD chassis ship with two DC-to-DC converter assemblies installed. Both
converters are mounted inside the chassis just behind the fan assembly. Each DC-to-
DC converter uses the -48 VDC output from its corresponding bulk power supply
module to develop +24, +5, and -5 VDC chassis working voltages.
Each DC-to-DC converter has a red LED mounted on its PC board. This LED glows
if a fault occurs in the converter while it is under power.
Inspection of the status LEDs and removal and replacement of the DC-to-DC
converters requires removal of the fan assembly.
CAUTION:
For a chassis under power, field replacement of the fans, AC-to-DC bulk
power supply modules, or DC-to-DC converter assemblies must be completed
in two minutes or less to prevent possible chassis overheating due to
temporary removal of the fan assembly.

Note:
  Do not operate the chassis with the fan assembly removed for more than two
minutes. Otherwise, overheating may result.
  DC-to-DC converters can be replaced in the field but they are not hot-swappable.
Before replacing a converter, disconnect its -48 VDC power supply, and do not
restore DC power until the converter has been fully installed in the chassis.
  The chassis can remain operational during the converter replacement as long as
the second DC-to-DC converter is operating.

DC-to-DC Converter Illustration

52 4021339 Rev B
 Prisma II ICIM2-XD

Prisma II ICIM2-XD
The ICIM2-XD provides an interface to Prisma II High Density application modules.
It supports communication with the application modules via command line interface
(CLI), Simple Network Management Protocol (SNMP), or through a user-friendly
ICIM Web Interface.
The ICIM2-XD can control up to 64 application modules through a daisy-chain
connection of up to four chassis.
Important:
  All chassis connected in a daisy-chain must be powered and have their own fan
assembly installed.
  All chassis connected in this daisy-chain must have a unique chassis
identification (ID) number.
  To ensure communications with all application modules, only one ICIM2-XD
may be installed per daisy-chain configuration.

ICIM2-XD Block Diagram

The main components and functions of the ICIM2-XD are illustrated in the block
diagram below.

Prisma II XD Chassis
Midplane
ICIM Configuration and Monitoring Bus ICIM
In
DB-9 DB-9 Out
Midplane
Connection

Microprocessor

Hardware
Interface

Hardware
RS-232 CLI
Interface

Hardware Ethernet
RJ-45
Interface

ICIM2-XD
Module

TP472

4021339 Rev B 53
Chapter 2 Introduction

ICIM2-XD Illustration (Front Panel)

ICIM2-XD Front Panel Features

Part Function
Ethernet connector Directly connects the ICIM2-XD to an IP network. The front-panel
Ethernet port is suitable for connection to intra-building wiring,
non-exposed wiring or cabling only.
RS232 connector Used to connect a co-located PC to the Prisma II Enhanced system
for local console port CLI communication and setup.

54 4021339 Rev B
 3 Chapter 3
Hardware Installation
Introduction
This chapter describes site requirements, equipment, tools needed,
and instructions for installation of the Prisma II XD Chassis and
application modules.

In This Chapter
ƒ Before You Begin................................................................................... 56
ƒ Site Requirements ................................................................................. 57
ƒ Mounting the Chassis in a Rack.......................................................... 61
ƒ Connector Interface Panel.................................................................... 63
ƒ Connecting the ICIM to Additional Chassis ..................................... 64
ƒ Connecting a Chassis to the TNCS Server......................................... 68
ƒ External Alarms Connections ............................................................. 70
ƒ Fan Assembly ........................................................................................ 72
ƒ Installing the Power Supply ................................................................ 73
ƒ Installing the ICIM................................................................................ 83
ƒ Installing Application Modules .......................................................... 84
ƒ Connecting Optical Cables .................................................................. 87
ƒ Connecting RF Cables .......................................................................... 88

4021339 Rev B 55
Chapter 3 Hardware Installation

Before You Begin

The chassis back panel provides all RF ports, I/O connectors, power inlets and
connectors, and ground connections.
ESD jacks are provided on the front and back panels for use when installing or
removing application modules, cabling, the fan assembly, AC-to-DC bulk power
supplies, DC-to-DC converters, or the ICIM2-XD.

Unpacking and Inspecting the Chassis

As you unpack the chassis, inspect it for shipping damage. If you find any damage,
contact Customer Service. Refer to Customer Support Information (on page 297) for
information on contacting Customer Service. Record the chassis serial number and
date of installation for future reference.

Required Equipment and Tools

Before you begin, gather the equipment and tools listed in the following table.

You need . . . To . . .
a medium-sized Phillips-head or flat-blade tighten the screws that secure the
screwdriver chassis to the equipment rack.
a medium-sized flat-blade screwdriver tighten and loosen the screws that
secure the application modules to the
chassis front pane and the fan
assembly to the chassis back panel.
a small Phillips-head or flat-blade screwdriver tighten the screws that secure the
ICIM2-XD module to the chassis back
panel.
application module extraction tool, part number remove application modules from the
4022921 (supplied with XD chassis) chassis as needed.

Note: Always use a tool when loosening or tightening the screws that hold the
application modules to the chassis front panel.

56 4021339 Rev B
 Site Requirements

Site Requirements
This section describes environmental, physical, and wiring requirements to be met
prior to equipment installation. Before you begin, make certain that your installation
site meets the requirements discussed in this section.

Operating Environment
CAUTION:
Avoid damage to this product! Operating this product outside the specified
operating temperature limits voids the warranty.

Follow these recommendations to maintain an acceptable operating temperature for

the equipment.

  Operating temperature at the air inlet must be between 0°C and 50°C (32°F and
122°F).
  Keep cooling vents clear and free of obstructions.
  Provide ventilation as needed using one or more of the following methods.
- Air-deflecting baffles
- Forced-air ventilation
- Air outlets above enclosures, either alone or in combination
Note: Refer to module data sheets and product guides for product-specific module
temperature specifications.

Chassis Wiring and Fusing

Important: All chassis configurations require an external fuse or circuit breaker (AC
and DC current ratings differ; see below) and #16 AWG wiring for both power and
grounding.

AC Power Systems
AC power for each AC-to-DC bulk power supply module enters the chassis through
a dedicated back-panel IEC power inlet for each power supply module.
Confirm that the IEC power cord or cords supplied with the chassis have the correct
plug configuration for the country of use.
The voltage input range for AC systems is 100 to 240 VAC, single phase, 50-60 Hz.
AC input current is 14 A maximum. The chassis should be connected to a single
outlet circuit with fuse or circuit breaker overcurrent protection rated 15 A
minimum.

4021339 Rev B 57
Chapter 3 Hardware Installation

Important:
  Use only a grounded electrical outlet when connecting the unit to a power
source. If you do not know whether the outlet is grounded, consult with a
qualified electrician.
  Maintain reliable earth grounding of rack-mounted equipment. Pay particular
attention to supply and ground connections made via power strips or any
method other than direct connection to the branch circuit.

DC Power Systems
External -48 VDC operating power for each DC-to-DC converter (mounted in the
chassis just behind the fan assembly) enters the chassis via a dedicated DC power
inlet mounted on the chassis back panel.
The voltage input range for DC power systems is -40 VDC to -72 VDC.
Use #16 AWG wire for DC field wiring. The #16 AWG wiring from the external -48
VDC supply is attached to a 3-pin nylon connector which, in turn, plugs into the DC
power inlet.
Terminate the chassis side of the cable with a nylon plug of the type supplied with
the chassis. Order additional nylon plugs and connector pins from your preferred
supplier, as follows:
  Molex #03-12-1036 nylon 3-pin connector
  Molex #18-12-1222 crimp socket contact (3)
Use a Molex Crimp Service Tool #63811-1000 or equivalent to crimp the pins to the
cable.
After terminating the cable, twist the conductors loosely (a full turn every few inches
is sufficient).
As installed in the DC power connector with the locking tab down, the left pin of the
nylon connector is the return, the right pin carries -48 VDC, and the center pin is
chassis ground.

Connect the chassis to a reliably grounded DC power source that is electrically

isolated from the AC power source.
Important:
  Branch circuit overcurrent protection must be provided by a fuse or circuit
breaker with a voltage rating of 72 VDC minimum and a current rating of 18 A

58 4021339 Rev B
 Site Requirements

maximum.
  The DC field wiring must include a readily accessible disconnect device that is
suitably approved and rated.

Earth-Grounding Conditions
The chassis is designed to permit connection of the earthed conductor of the DC
supply circuit to chassis ground. Before making this connection, confirm that all of
the following conditions are met:
  The chassis is connected directly to the DC supply system earthing electrode
conductor or to a bonding jumper from an earthing terminal bar or bus to which
the DC supply system earthing electrode conductor is connected.
  The chassis is located in the same immediate area as other equipment connected
between the earthed conductor of the same DC supply circuit and earthing
conductor, such as in an adjacent cabinet. Also, the point of earthing of the DC
system must not be earthed elsewhere.
  The DC power source is located within the same premises as the chassis.
  There are no switching or disconnecting devices in the earthed circuit conductor
between the DC source and the point of connection of the earthing electrode
conductor.

DC Power Passing
An XD chassis with at least one AC-to-DC bulk power supply module installed can
serve as an external DC power source for a second XD chassis. Passing DC power
from one chassis to another requires a DC power-passing cable made up as
described above, but with both ends of the cable terminated by a nylon DC power
connector. Two assembled DC power-passing cables are also available from the
factory:
  Part number 4011730, 3 m DC power-passing cable
  Part number 4023718, 2 ft DC power-passing cable

Rack Location Requirements

Follow these recommendations when installing the chassis in a rack.
  Locate the rack away from strong RF radiation and line transients that can
damage the equipment.
  Locate the rack in an area that permits access to connectors on the front and rear
of the chassis as needed.

4021339 Rev B 59
Chapter 3 Hardware Installation

Unused Slots
Important: All unused slots in the chassis must be filled with blanking panels.
Application module blanking panels, part number 4023066, are available from the
factory. Replacement AC-to-DC bulk power supply blanking panels (part number
4021618) and ICIM2-XD blanking panels (part number 4021163) are also available, if
needed.

60 4021339 Rev B
 Mounting the Chassis in a Rack

Mounting the Chassis in a Rack

To Install the Chassis in a Rack
WARNING:
The Prisma II XD Chassis weighs approximately 25 lbs (11.3 kg) empty and 40
lbs (18.1 kg) fully loaded. To avoid personal injury and equipment damage,
use safe handling and lifting practices in accordance with your organization's
procedures.

Complete the following steps to mount the chassis in a 19-inch rack.

1 Use a torque wrench to tighten the bracket mounting screws to 12 to 14 in-lbs
(1.36 to 1.58 Nm).
2 Position the chassis in the rack with the fan assembly installed, but otherwise
empty.
3 Insert a mounting screw through each of the four mounting holes on chassis
front panel, and then into the rack.

4 Use a medium-sized Phillips-head screwdriver to tighten each mounting screw

until it is tight.
5 Install additional cable and fiber management hardware as needed and in
accordance with local practice.

4021339 Rev B 61
Chapter 3 Hardware Installation

Chassis Dimensions
Use the dimensions given below to determine clearance requirements for installing
the chassis in the rack.

Dimension English Metric

Height 5.25 in. 13.3 cm
Width 17.5 in. 44.5 cm
Depth 22 in. 55.9 cm

62 4021339 Rev B
 Connector Interface Panel

Connector Interface Panel

All electrical and non-optical interface connections are made at the chassis back
panel.

4021339 Rev B 63
Chapter 3 Hardware Installation

Connecting the ICIM to Additional Chassis

The Prisma II XD platform allows the ICIM2-XD to be located in one chassis and
monitor application modules located in up to three additional chassis. This
communication daisy-chain is enabled by connecting cables to the ICIM IN and
ICIM OUT connectors on the chassis back panel. Such a connection is required for
an ICIM2-XD in one chassis to communicate with or control any application module
in another chassis.
Note: The ICIM2-XD can control up to 64 application modules in a daisy-chain
configuration of up to four chassis.

To Make ICIM IN and ICIM OUT Cable Connections

Complete the following steps to make chassis-to-chassis ICIM IN and ICIM OUT
connections.
1 Connect the serial extension cable from the ICIM OUT of the chassis containing
the ICIM2-XD to the ICIM IN connector of the second chassis.
2 Connect a serial extension cable from the ICIM OUT of the second chassis to the
ICIM IN of the third chassis, if installed.
3 Connect a serial extension cable from the ICIM OUT of the third chassis to the
ICIM IN of the fourth chassis, if installed.
4 Change the chassis ID numbers as needed to give each chassis an appropriate
unique ID number. See To Change the Chassis ID Number below for further
details and cautions.
5 Connect a serial extension cable from the ICIM OUT of the second chassis to the
ICIM IN of the third chassis.

64 4021339 Rev B
 Connecting the ICIM to Additional Chassis

6 The ICIM OUT port of the last chassis in the daisy-chain must be terminated
with an ICIM OUT terminator, part number 4013014, which ships with the
ICIM2-XD.

EM In
ICIM Out

Serial Chassis with

Extension ICIM
Cable
ICIM In
ICIM Out

Serial Chassis
Extension
Cable
ICIM In
ICIM Out

Serial
Chassis
Extension
Cable
ICIM In
ICIM Out

Chassis

ICIM Out
Terminator
TP477

Note:
  Up to two chassis can share the use of a single bulk power supply module or pair
of modules. See To Share Power Between Two Chassis (on page 11) for details.
  All chassis connected in this daisy-chain must be powered and have fans
installed. For correct operation, proper cooling of the chassis must be maintained
over the specified temperature range.
  A single chassis equipped with an ICIM2-XD must also have its ICIM OUT port
terminated with an ICIM OUT terminator, part number 4013014. The ICIM OUT
terminator ships with the ICIM2-XD.

To Change the Chassis ID Number

Complete the following steps to change the chassis ID number.
1 Locate the chassis ID switch at upper right on the front panel of each chassis. The
switch can be set to any two-digit value from 00 to 99 (but avoid setting the value
to 00, as explained below).

4021339 Rev B 65
Chapter 3 Hardware Installation

2 Use the chassis ID switch to set each chassis ID number to a unique value.
Note:
  The chassis ID number can be changed while the chassis is under power.
However, the new ID number will not become effective until chassis power is
cycled or the ICIM2-XD is rebooted.
  The chassis numbering scheme used is discretionary, except that each
interconnected chassis must have a unique ID number.
  It is important to avoid using chassis ID number 00 in some circumstances, as
explained in the following caution.
CAUTION:
Setting the chassis ID to 00 is not recommended as it causes the entity MIB to violate
RFC-2737 by creating an invalid object identifier. This may affect operation with some
management systems that use the entity MIB. In particular, attempts to access the fans
(in virtual slot 0) in chassis 00 will fail if made via serial TNCS (or ROSA-EM) or LCI.

Important: If you change the chassis ID number while the chassis is under power,
you must cycle power to the chassis or reboot the ICIM2-XD in order for the new
number to take effect.

ICIM IN and ICIM OUT Cables

The cable required for both ICIM IN and ICIM OUT connections is a shielded 9-
wire serial extension cable, DB9 Female to DB9 Male. This cable can be purchased
locally or from the factory. The chassis data sheet lists the part number for a 6-foot
DB9 Female to DB9 Male serial extension cable. The connectors are a serial 9-pin D-
shell (EIA 574/232).

Chassis-to-Chassis ICIM Activation

Once the chassis are interconnected, the shared ICIM2 or ICIM2-XD should be
forced to search for all new modules, rather than be allowed to find them
incrementally over the course of a polling cycle.

66 4021339 Rev B
 Connecting the ICIM to Additional Chassis

The recommended method for forcing a search for new modules is to reboot the
ICIM2 or ICIM2-XD. This can be accomplished either by physically removing and
reinserting the ICIM2 or ICIM2-XD module or by issuing a reboot command via the
CLI interface.
To reboot the ICIM2 or ICIM2-XD module via CLI, open a console session and type
the following commands at the CLI prompt.
CLI> icim
ICIM> reboot

The response will be:

The ICIM2 is about to reboot. This will end all current login and web sessions
Are you sure you want to proceed (Yes/No)> yes
SUCCESS!
ICIM>
Scientific-Atlanta Intelligent Communications Interface Module (ICIM)
---------------------
W A R N I N G
---------------------
Unauthorized or improper use of this system may result in
administrative disciplinary action and civil or criminal penalties.
By continuing to use this system you indicate your awareness of and
consent to these terms and conditions of use. LOG OFF IMMEDIATELY
if you do not agree to the conditions stated in this warning.
login:

Each of the additional modules will then be added to the ICIM2 or ICIM2-XD polling
cycle.
Note: Use of the CLI reboot command is preferred over the updateid command in
this case because a reboot will maintain synchronization with the element
management system.

4021339 Rev B 67
Chapter 3 Hardware Installation

Connecting a Chassis to the TNCS Server

Cable Kits for Connecting a Chassis to the TNCS Server
Connecting the chassis to the TNCS server requires two special cable kits that are
available from the factory.
  The RS-485 cable kit, part number 735748, includes the following:
- Breakout boxes, 4 each
- RS-485 cable assemblies (50 feet), 4 each
- Breakout box mounting brackets, 4 each
- 6-32 screws (1.25 inches), 100 each
  The Prisma II cable kit, part number 738686, includes the following:
- Prisma II cable assemblies, 4 each
The RS-485 cable kit is used to communicate with the RS-485/422/TTL devices.

To Connect TNCS to the Chassis EM IN Port

1 Mount one of the breakout boxes (included in the RS-485 cable kit) in a rack
location central to the appropriate chassis.

2 Connect a RS-485 cable assembly (included in the RS-485 cable kit) from the
breakout box to the RS-485 COM port on the TNCS server.
3 Connect one Prisma II cable assembly (included in the Prisma II cable kit) from
the breakout box to the EM IN port of each chassis containing an ICIM2-XD.

68 4021339 Rev B
 Connecting a Chassis to the TNCS Server

Note: As a general rule, it is recommended that the total number of ICIM2-XD

control units connected to any single COM port on the TNCS server be limited to
four. However, you may connect more than four per TNCS COM port as long as the
total number of application modules monitored by a single COM port does not
exceed 400. The total number of devices monitored by any single ICIM2-XD cannot
exceed 64.

Using TNCS with Multiple Chassis

All chassis within an ICIM2-XD domain are connected in series via the ICIM
IN/ICIM OUT connectors using standard “off the shelf” serial extension cable, DB9
Female to DB9 Male. Using the EM IN/EM OUT connectors, a chassis with an
ICIM2-XD installed is connected to a breakout box as shown below. The breakout
box is connected to the TNCS server with the cable included in the RS-485 cable kit.

4021339 Rev B 69
Chapter 3 Hardware Installation

External Alarms Connections

The XD chassis platform supports hardware redundancy through external alarm
connections provided on the back of each chassis. This feature can be used to set up
a "master-slave" relationship between a primary set of modules in one chassis and a
backup set of similar modules located in a separate chassis.

Master-Slave Operation
All Prisma II modules ship from the factory configured as a “master.” They can be
reconfigured as "slave" or redundant modules through command line interface (CLI)
commands. The chassis allows for local hard-wired redundancy by using the
ALARM IN and ALARM OUT connectors on the connector interface panel. With
these connectors, a master-slave pair of modules can be configured so that if the
master fails, the slave takes over.

ALARM IN and OUT Connections

The XD chassis provides two sets of connections for external alarms to and from
each module slot. These alarm connections are provided via a pair of 16-pin wire
terminal blocks on the chassis back panel, labeled ALARM IN and OUT.
When a critical alarm occurs in a master module, the master turns off and the slave
(redundant module) is enabled. To make this happen, the pin representing the
master module slot in the ALARM OUT terminal block must be wired to the pin
representing the slave module slot in the ALARM IN terminal block.
Master and slave modules can be installed either in the same chassis or in different
chassis, as long as the modules are correctly configured and interconnected.
Note:
  After setting up the modules, it is important to ensure that they are not moved to
different slots. Otherwise, the ALARM IN and OUT terminal block connections
will have to be rearranged.
  A module cannot act as both a master and a slave. Accordingly, any module
configured as a master ignores its own ALARM IN contacts.
  To verify proper wiring and redundant configuration, unplug the master device
and confirm that the slave module turns on as a result.

70 4021339 Rev B
 External Alarms Connections

Master-Slave Illustration

ALARM IN and OUT Terminal Blocks

4021339 Rev B 71
Chapter 3 Hardware Installation

Fan Assembly
To Remove the Fan Assembly
The fan assembly is installed at the factory. It can be removed for maintenance or
inspection or to access the DC-to-DC converter assemblies by loosening the two
screws located on either side of the assembly, as shown below.

Important: Do not operate any chassis without the fans installed. For correct
operation, proper cooling of the chassis must be maintained over the specified
temperature range.
CAUTION:
Always use a screwdriver to loosen or tighten the screws holding the
application modules, ICIM2-XD, fan assembly, power supply modules, DC-to-
DC converters, or blanking panels in place. Do not attempt to loosen or
tighten these screws solely by hand.

CAUTION:
For a chassis under power, field replacement of the fans, AC-to-DC bulk
power supply modules, or DC-to-DC converter assemblies must be completed
in two minutes or less to prevent possible chassis overheating due to
temporary removal of the fan assembly.

72 4021339 Rev B
 Installing the Power Supply

Installing the Power Supply

Power Supply Requirements
The chassis accepts one or two AC-to-DC bulk power supply modules. These
modules fit in dedicated slots on either side of the chassis back panel.
AC-to-DC bulk power supplies convert incoming utility AC power (100 to 240 VAC,
50 or 60 Hz) to -48 VDC for use by DC-to-DC converters inside the chassis. The
internal DC-to-DC converters in turn generate the chassis midplane bus working
voltages at +24, +5, and -5 VDC.

Power Sharing
Two Prisma II XD Chassis can operate from a single AC-to-DC bulk power supply
module or from a pair of bulk power supply modules. A power-chain connection is
used to route -48 VDC from a chassis with one or both bulk power supply modules
installed to a second chassis whose corresponding bulk power supply module slots
are empty and have blanking panels installed.
The following illustration shows the recommended cabling for power sharing
between an exclusively AC powered chassis (top) and an exclusively DC powered
chassis (bottom).

DC DC
AC OUT A OUT B AC
IN A IN B

Twist Twist
conductors conductors

DC DC
IN A IN B

TP476

4021339 Rev B 73
Chapter 3 Hardware Installation

Electrical Power Connections

The chassis back panel has an IEC standard AC power inlet and a three-conductor
DC power connector for each bulk DC power supply module slot.
  The AC power inlet accepts line voltage at 100 to 240 VAC, 50 or 60 Hz.
  The DC power connector accepts DC input voltage at -40 to -72 VDC (-48 VDC
nominal).
The power connectors on the left side of the chassis supply power to the left power
supply slot, while those on the right supply power to the right power supply slot.
Except for their chassis ground pins, all four power connectors are electrically
independent of each other.
Important: Tie the system to earth ground via the ground stud.
Note: For DC power supplies, the return terminal is an "isolated DC return," i.e., it is
not connected to the chassis framework.

Chassis Wiring and Fusing

Important: All chassis configurations require an external fuse or circuit breaker (AC
and DC current ratings differ; see below) and #16 AWG wiring for both power and
grounding.

AC Power Systems
AC power for each AC-to-DC bulk power supply module enters the chassis through
a dedicated back-panel IEC power inlet for each power supply module.
Confirm that the IEC power cord or cords supplied with the chassis have the correct
plug configuration for the country of use.
The voltage input range for AC systems is 100 to 240 VAC, single phase, 50-60 Hz.
AC input current is 14 A maximum. The chassis should be connected to a single
outlet circuit with fuse or circuit breaker overcurrent protection rated 15 A
minimum.

Important:
  Use only a grounded electrical outlet when connecting the unit to a power
source. If you do not know whether the outlet is grounded, consult with a
qualified electrician.
  Maintain reliable earth grounding of rack-mounted equipment. Pay particular
attention to supply and ground connections made via power strips or any
method other than direct connection to the branch circuit.

74 4021339 Rev B
 Installing the Power Supply

DC Power Systems
External -48 VDC operating power for each DC-to-DC converter (mounted in the
chassis just behind the fan assembly) enters the chassis via a dedicated DC power
inlet mounted on the chassis back panel.
The voltage input range for DC power systems is -40 VDC to -72 VDC.
Use #16 AWG wire for DC field wiring. The #16 AWG wiring from the external -48
VDC supply is attached to a 3-pin nylon connector which, in turn, plugs into the DC
power inlet.
Terminate the chassis side of the cable with a nylon plug of the type supplied with
the chassis. Order additional nylon plugs and connector pins from your preferred
supplier, as follows:
  Molex #03-12-1036 nylon 3-pin connector
  Molex #18-12-1222 crimp socket contact (3)
Use a Molex Crimp Service Tool #63811-1000 or equivalent to crimp the pins to the
cable.
After terminating the cable, twist the conductors loosely (a full turn every few inches
is sufficient).
As installed in the DC power connector with the locking tab down, the left pin of the
nylon connector is the return, the right pin carries -48 VDC, and the center pin is
chassis ground.

Connect the chassis to a reliably grounded DC power source that is electrically

isolated from the AC power source.
Important:
  Branch circuit overcurrent protection must be provided by a fuse or circuit
breaker with a voltage rating of 72 VDC minimum and a current rating of 18 A
maximum.
  The DC field wiring must include a readily accessible disconnect device that is
suitably approved and rated.

Earth-Grounding Conditions
The chassis is designed to permit connection of the earthed conductor of the DC
supply circuit to chassis ground. Before making this connection, confirm that all of
the following conditions are met:

4021339 Rev B 75
Chapter 3 Hardware Installation

  The chassis is connected directly to the DC supply system earthing electrode

conductor or to a bonding jumper from an earthing terminal bar or bus to which
the DC supply system earthing electrode conductor is connected.
  The chassis is located in the same immediate area as other equipment connected
between the earthed conductor of the same DC supply circuit and earthing
conductor, such as in an adjacent cabinet. Also, the point of earthing of the DC
system must not be earthed elsewhere.
  The DC power source is located within the same premises as the chassis.
  There are no switching or disconnecting devices in the earthed circuit conductor
between the DC source and the point of connection of the earthing electrode
conductor.

DC Power Passing
An XD chassis with at least one AC-to-DC bulk power supply module installed can
serve as an external DC power source for a second XD chassis. Passing DC power
from one chassis to another requires a DC power-passing cable made up as
described above, but with both ends of the cable terminated by a nylon DC power
connector. Two assembled DC power-passing cables are also available from the
factory:
  Part number 4011730, 3 m DC power-passing cable
  Part number 4023718, 2 ft DC power-passing cable

DC Power Connectors
The chassis back panel provides a separate DC power connector for each AC-to-DC
bulk power supply slot. The chassis ships with a white nylon plug installed in each
DC power connector. These white nylon plugs have no pins installed, and serve
mainly to guard against potential improper use of the DC power connector.
CAUTION:
A single DC power connector cannot act as in input and an output connector at
the same time. Before applying external DC power, confirm that the AC-to-DC
bulk power supply slot associated with the DC power connector is empty and
covered by a blanking panel.

Each DC power connector on the chassis back panel can serve as either a DC power
inlet or a DC power outlet, but not both, as follows:
  With no AC-to-DC bulk power supply module installed, the corresponding DC
power connector can serve as an inlet for -48 VDC supplied by a battery room, a
second XD chassis, or another external DC power source. In this configuration,
however, the same DC power connector cannot be used as a -48 VDC output.
  With an AC-to-DC bulk power supply module installed, the corresponding DC
power connector can serve as an outlet for -48 VDC to power a second XD

76 4021339 Rev B
 Installing the Power Supply

chassis. In this configuration, however, the same DC power connector cannot be

used as a DC power inlet.
CAUTION:
When connecting chassis together for power sharing, use either a factory DC
power-passing cable, part number 4011730 (3 m) or 4023718 (2 ft), or a custom
cable made in accordance with the instructions in this document. Use of other
cables for this purpose is not supported.

Power Inlet Illustration

The following illustration shows locations of the AC and DC power connectors on
the chassis back panel.

To Install the Power Cord

AC Power Cord
Important: The XD chassis is not supplied with an AC power cord. To complete this
procedure, you must order the correct power cord for your region. For ordering
information, see the Prisma II XD Platform Data Sheet, part number 7012804.
Complete the following steps to install an AC power cord for each bulk power
supply module.
1 Confirm the location(s) of bulk power supply modules installed in slot A or slot
B, or both A and B.

4021339 Rev B 77
Chapter 3 Hardware Installation

2 Insert the IEC plug of each AC power cord into the back-panel IEC power inlet
for each installed bulk DC power supply module.
3 Attach the plug end of each AC power cord into an AC power receptacle.

DC Power Cord
Complete the following steps to install one or more DC power cords for each unused
bulk DC power supply slot as needed.
1 Confirm that each unused bulk power supply slot is empty and covered by a
blanking panel.
2 Locate the DC wire terminal block (white nylon plug) pre-installed in each back-
panel DC power connector.
3 Remove the terminal block and note the locations of the left, middle, and right
terminals as shown below.

4 Obtain conductive pins (Molex #18-12-1222) for each DC wire terminal block for
each conductor to be used.
5 Attach #16 AWG power cable from the fuse panel to the pins and install them in
the terminal block as follows:
ƒ Left terminal: Return conductor
ƒ Middle terminal: Chassis ground (optional)
ƒ Right terminal: -48V DC conductor
6 Insert the wire terminal block into the DC power connector until it locks. Tug
lightly on the terminal block to confirm that it is locked in position.
7 Twist the conductors together loosely along the full length of the power cord (a
full turn every few inches is sufficient).

To Install the Power Supply in the Chassis

Complete the following steps to install an AC-to-DC bulk power supply module in
an available chassis slot.
CAUTION:
Always use a screwdriver to loosen or tighten the screws holding the
application modules, ICIM2-XD, fan assembly, power supply modules, DC-to-
DC converters, or blanking panels in place. Do not attempt to loosen or
tighten these screws solely by hand.
1 On the chassis back panel, loosen the two screws holding the fan assembly in
place. Remove the fan assembly and set it aside temporarily.

78 4021339 Rev B
 Installing the Power Supply

2 Remove the blanking panel that covers the bulk power supply slot opening.
3 Pick up the bulk power supply module by its handle and insert the module into
the open module slot, as shown below.

4 Gently slide the power supply module into the chassis until its power
connections join connectors on the midplane bus. Do not force the module into the
chassis. If properly aligned, it should slide in with minimal force.
5 If installing a second power supply, repeat the steps above for the second power
supply slot, and then continue with step 6.
6 Confirm that a DC-to-DC converter assembly is installed inside the chassis next
to the new bulk power supply module. This converter will be visible inside the
fan opening, mounted horizontally and held in place by a retaining screw.
7 Reinstall the fan assembly and tighten the two screws holding it and the power
supply module(s) in position.
8 Apply power and verify that the green LED on the front panel of each power
supply module illuminates, indicating normal operation.
9 Confirm that the fan assembly is operational. The fans should be audible once
the power supply is operating.

Power Supply Cooling Fans

Each power supply module has internal fans that provide airflow for cooling.

To Install the DC-to-DC Converter

Complete the following steps as needed to install a DC-to-DC converter assembly in
the chassis.

4021339 Rev B 79
Chapter 3 Hardware Installation

CAUTION:
Always use a screwdriver to loosen or tighten the screws holding the
application modules, ICIM2-XD, fan assembly, power supply modules, DC-to-
DC converters, or blanking panels in place. Do not attempt to loosen or
tighten these screws solely by hand.
1 If necessary, loosen the two screws holding the fan assembly in place, remove the
fan assembly, and set it aside temporarily.
2 Locate the appropriate position for the DC-to-DC converter assembly on top of
the horizontal shelf just inside the fan assembly opening.
Note: There are two positions for DC-to-DC converter assemblies, one for each
possible AC-to-DC bulk power supply module installed.

3 Gently slide the DC-to-DC converter assembly into the chassis until its power
connections join connectors on the midplane bus. Do not force the converter into the
chassis. If properly aligned, it should slide in with minimal force.
4 If installing a second DC-to-DC converter, repeat the steps above for the second
converter, and then continue with step 5.
5 Briefly apply power and verify that the red LED on the DC-to-DC converter
board(s) remains unlit, indicating normal operation.
CAUTION:
For a chassis under power, field replacement of the fans, AC-to-DC bulk
power supply modules, or DC-to-DC converter assemblies must be completed
in two minutes or less to prevent possible chassis overheating due to
temporary removal of the fan assembly.
6 Reinstall the fan assembly and tighten the two screws holding it and the power
supply module(s) in position.
7 Confirm that the fan assembly is operational. The fans should be audible once
the power supply is operating.

80 4021339 Rev B
 Installing the Power Supply

To Monitor the Power Supply

The AC-to-DC bulk power supplies and DC-to-DC converters may be monitored
remotely via the ICIM2 or ICIM2-XD using CLI or SNMP commands. Use any of the
following methods to monitor power supply operational and alarm status.
  LEDs on each bulk power supply indicate its operational and alarm status. The
ON LED monitors electrical power into the module, and the ALARM LED
monitors alarms in module temperature or module failure.
  Command Line Interface (CLI) commands may be used to obtain power supply
or other module status information either through an attached personal
computer or over a network.
  Simple Network Management Protocol (SNMP) commands also may be used to
obtain power supply or other module status information remotely.
For information on power supply monitoring using CLI commands, refer to the
Prisma II Platform Remote User Interface Guide, part number 4012441. For information
on power supply monitoring using SNMP commands, refer to SNMP Management
(on page 171).

To Enable Power Passing

Complete the following steps to enable power passing between two Prisma II XD
Platform chassis.
1 On the chassis supplying power, identify an available DC power connector
whose corresponding AC-to-DC bulk power supply slot is populated.
2 On the chassis receiving power, identify an available DC power connector whose
corresponding AC-to-DC bulk power supply slot empty and covered by a
blanking panel.
3 Install a DC power-passing cable (described below) between the two DC power
connectors just identified.

DC Power-passing Cable
Two assembled DC power-passing cables are currently available from the factory:
  Part number 4011730, 3 m DC power passing cable
  Part number 4023718, 2 ft DC power passing cable
DC power-passing cables can also be made up in custom lengths to suit the needs of
specific installations. The cable used to pass DC power from one chassis to another
must have the following characteristics:
  Return (left) conductor - #16 AWG insulated stranded wire
  -48 VDC (right) conductor - #16 AWG insulated stranded wire
  Ground (center) conductor - #16 AWG insulated stranded wire

4021339 Rev B 81
Chapter 3 Hardware Installation

  Conductors twisted together loosely (a full turn every few inches is sufficient)
  Both ends terminated by white nylon connectors of the type supplied with the
chassis

82 4021339 Rev B
 Installing the ICIM

Installing the ICIM

Note: To ensure communications with all application modules, install the ICIM2-XD
in the dedicated ICIM slot on the back of the chassis. Install only one ICIM2-XD per
daisy-chain configuration.

To Install the ICIM2-XD

Complete the following steps to install the ICIM2-XD in the chassis.
CAUTION:
Always use a screwdriver to loosen or tighten the screws holding the
application modules, ICIM2-XD, fan assembly, power supply modules, DC-to-
DC converters, or blanking panels in place. Do not attempt to loosen or
tighten these screws solely by hand.
1 Remove the blanking panel covering the ICIM slot in the lower right corner of
the chassis back panel.
2 Hold the ICIM2-XD so that the front panel silkscreen is in correct reading
position.
3 Align the two ridges on the bottom of the ICIM2-XD with the module guide slots
located in the chassis.

4 Gently slide the ICIM2-XD into the chassis until its power and communications
connections join connectors on the back plane bus and its front panel rests
against the chassis. Do not force the ICIM2-XD into the chassis. If properly aligned,
it should slide in with minimal force.
5 Tighten the retaining screws on either side of the ICIM2-XD to secure it in the
chassis. Use a 3/8-in. flat-blade screwdriver to secure. Do not over-tighten.

4021339 Rev B 83
Chapter 3 Hardware Installation

Installing Application Modules

All XD application modules are hot-swappable and plug-and-play. This means that
they can be installed or replaced without removing power from the chassis, and
without affecting the operation of other modules installed in the chassis.
Important:
  The following procedure assumes that the chassis is mounted in a rack.
  When an application module is inserted into the chassis, one or more alarms may
be generated momentarily while the module powers up. This will be briefly
indicated on the module LED and may also generate an alarm in the event log.
This is normal and does not indicate a module problem.

To Install the Module

WARNING:
Avoid damage to your eyes! Do not look into any optical connector while the
system is active. Even if the unit is off, there may still be hazardous optical
levels present.

Complete the following steps to install the module in the chassis.

CAUTION:
Always use a screwdriver to loosen or tighten the screws holding the
application modules, ICIM2-XD, fan assembly, power supply modules, DC-to-
DC converters, or blanking panels in place. Do not attempt to loosen or
tighten these screws solely by hand.
1 Locate the fiber guides at the bottom of the chassis and the module guide slots
inside the chassis as shown in the following illustration.

84 4021339 Rev B
 Installing Application Modules

2 Align the ridges on the top and bottom of the module with the module guide
slots located on the chassis.
3 Gently slide the module into the chassis until its power and communications
connections join connectors on the midplane bus. Do not force the module into the
chassis. If properly aligned, it should slide in with minimal force.

4 Tighten the screw at the top of the module to secure it in the chassis. Use a 3/8-
in. flat-blade screwdriver to secure. Do not over-tighten.
5 Fill any unused chassis slots with module blanks to help ensure proper cooling
air flow.

To Remove the Module

WARNING:
Avoid damage to your eyes! Do not look into any optical connector while the
system is active. Even if the unit is off, there may still be hazardous optical
levels present.

Complete the following steps to remove the module from the chassis.
CAUTION:
Always use a screwdriver to loosen or tighten the screws holding the
application modules, ICIM2-XD, fan assembly, power supply modules, DC-to-
DC converters, or blanking panels in place. Do not attempt to loosen or
tighten these screws solely by hand.
1 Loosen the screw at the top of the module to be removed using a 3/8-in. flat-
blade screwdriver.
Important: Make sure that the screw is completely loose before performing the
next step.

4021339 Rev B 85
Chapter 3 Hardware Installation

2 Locate the module extraction tool, part number 4022921, which was supplied
with the chassis.
3 Insert the hooked end of the tool behind the upper right corner of the module
front panel. Rotate the tool upward as shown below to pry the module away
from the chassis mounting flange.

4 Using your fingers, gently slide the module completely out of the chassis slot.
5 If necessary, fill the empty chassis slot with a module blanking panel to help
ensure proper cooling air flow.

86 4021339 Rev B
 Connecting Optical Cables

Connecting Optical Cables

Important:
  Make all connections with the optical power off. This will reduce the risk of
damage to fiber-optic connectors.
  Clean the optical connectors as needed before making optical connections. See
Cleaning Optical Connectors (on page 292) for instructions.
Note: Observe laser safety precautions. Refer to Laser Safety (on page xxv) for
further information.

To Connect Optical Cables

CAUTION:
High power density exists on fiber when optical power is present. To avoid
microscopic damage to fiber mating surfaces, turn off optical power or reduce
power below 15 dBm before making or breaking optical connections.

Complete the following steps for each optical cable connection to be made and on
every module to be installed.
1 Clean the end of the fiber to be connected as described in Cleaning Optical
Connectors (on page 292).
2 Connect the optical cable to the module connector.
3 Route the cable to the appropriate destination.
4 Clean the remaining cable end, and then connect the cable to the mating module
connector.
Note: Remember to observe minimum bend radius and other accepted handling
practices when working with fiber-optic cables.
5 After cable installation is complete, return the module control settings to their
original states.

4021339 Rev B 87
Chapter 3 Hardware Installation

Connecting RF Cables
The chassis back panel has two RF connectors, A and B, for each application module
slot. Each pair of RF connectors is numbered (1-16) to show its corresponding slot
number. RF port A, leftmost in each pair, is marked by a black semicircle or nut at
the base of the connector. RF port A provides connection to the upper of two
independent RF channels on the chassis midplane, while RF port B provides
connection to the lower RF channel.

Note: The application module installed in each chassis slot determines whether and
how the two RF channels are used. See the appropriate application module
documentation for further information.

To Connect RF Cables
Complete the following steps for each RF cable connection to be made.
1 Connect the RF cable to the appropriate back-panel module connector.
2 Route the cable to the appropriate destination.

88 4021339 Rev B
 4 Chapter 4
Equipment Configuration
Introduction
This chapter provides instructions for configuring the chassis and
application modules for remote management. There are several
different ways to configure the equipment. This chapter presents one
approach for configuration.
Refer to Prisma II Permitted CLI Commands (on page 307) for a
summary listing of CLI commands.
For further information on configuration using the CLI or ICIM Web
Interface, see the Prisma II Platform Remote User Interface Guide, part
number 4012441.

In This Chapter
ƒ HyperTerminal Session Setup............................................................. 90
ƒ CLI Parameters...................................................................................... 93
ƒ Telnet Session ........................................................................................ 96
ƒ SNMP Parameters................................................................................. 98

4021339 Rev B 89
Chapter 4 Equipment Configuration

HyperTerminal Session Setup

HyperTerminal is a terminal emulation program that is included with the Microsoft
Windows operating system.
The following equipment is required to perform this procedure.
  A personal computer (preferably a laptop computer for a local connection)
  A terminal emulation program such as Windows HyperTerminal or a remote
terminal emulation program such as Telnet
  A DB-9 to DB-9 straight-through serial cable
You can use HyperTerminal to initiate a direct-connect communications session with
an ICIM2-XD through its front-panel serial port.

To Set Up a HyperTerminal Serial Port Session

Complete the following steps to set up the HyperTerminal emulation program.
1 Connect one end of a DB-9 to DB-9 straight-through serial cable to an available
COM port on the personal computer, and the other end to the ICIM2 or ICIM2-
XD front-panel serial port.
2 Open a HyperTerminal session on your laptop (or desktop) PC that you will use
to connect to the ICIM2 or ICIM2-XD. The HyperTerminal program is typically
found at:
Start\All Programs\Accessories\Communication\Hyperterminal
The new Connection Description dialog box appears.

90 4021339 Rev B
 HyperTerminal Session Setup

3 Type in a name for the connection, select an icon of your choice, and click OK.
The Connect To dialog box appears.

4 In the Connect Using field, click the drop-down arrow and select the serial port
that you will use for the connection, and then click OK. The COM Properties
dialog box appears.
Note: For most applications, the serial port is COM1 or COM2.
5 Set the following port setting in the COM Properties dialog box.

4021339 Rev B 91
Chapter 4 Equipment Configuration

6 Click OK. The HyperTerminal main program window appears.

7 On the File menu, click Save to save the settings.

92 4021339 Rev B
 CLI Parameters

CLI Parameters
Additional parameters may be set as needed from the command line interface (CLI)
for each application module installed.
Refer to Prisma II Permitted CLI Commands (on page 307) and the Prisma II Platform
Remote User Interface Guide, part number 4012441 for information and additional
instructions on available commands and using the CLI.
Following are examples of parameters available through the CLI.

Login
1 Log in using the default username Administrat0r and the default password
AdminPassw0rd. Note the 0 (zero) character in each string.
Scientific-Atlanta Intelligent Communications Interface Module (ICIM)
login: Administrat0r
Password: AdminPassw0rd
Successful login will return the following prompt:
login: Administrat0r
Password:
User Administrat0r logged in successfully on 11/13/06 at 15:25:35
Previous successful login was on 11/13/06 at 15:22:16
There were no failed attempts to login with this user id previously
CLI>
2 Enter the ICIM submenu by typing icim at the CLI> prompt.
CLI> icim
Successful entry into the ICIM menu tree will return the following prompt:
ICIM>
3 Configure the shelf (chassis) IP address, subnet mask, gateway, and clock using
the following commands:
set ip xxx.xxx.xxx.xxx
set subnet xxx.xxx.xxx.xxx
set gateway xxx.xxx.xxx.xxx
set clock "month/day/year hour:minute:second"
Note:
ƒ Be sure to include the quote symbols, e.g., set clock "3/15/2006 13:09:51".

ƒ Clock time is in the 24-hour format.

4 To enable these changes, reboot the ICIM2 or ICIM2-XD as follows:
ICIM> reboot
5 After the ICIM2 or ICIM2-XD reboots, repeat the login steps described above to
return to the ICIM command prompt. Then use the show command to verify
each of the above changes, as follows:
show ip
show subnet
show gateway

4021339 Rev B 93
Chapter 4 Equipment Configuration
show clock
6 Type logout, and then press Enter to exit the session.
7 Remove the serial cable. It is no longer required.
Important:
  For Telnet operation, the computer you are using must have a network
connection through which it can reach the ICIM2 or ICIM2-XD via its IP address.
  No more than four Telnet sessions are allowed at one time.
CAUTION:
Always use the Logout command to close a serial port or Telnet CLI session.
Closing a serial port session without issuing the Logout command leaves the
session open for a possible future connection. This may allow unauthorized
access by a new user if the previous user had a higher authorization privilege
level.

To Set Additional Users for Telnet or CLI Access

Refer to the Prisma II Platform Remote User Interface Guide, part number 4012441 for
CLI login settings information.
Note: It is strongly recommended that a new administrator login be created and that
the default administrator login be removed.
The table below lists the ICIM mode CLI commands for setting user login
parameters.

Commands Description
ICIM > show user Shows all users
ICIM > user change password [user name] Changes user password
ICIM > user add [user name] [access level] enable Adds a user
ICIM > user delete [user name] Deletes a user

Note: Usernames and passwords must be 6 to 14 characters long and contain at least
1 alphabetic character and at least 1 number.

To Set and Verify SNMP Community Strings

From the CLI command prompt, switch to ICIM command mode and define SNMP
Read, Write, and Trap Community strings, as shown below.
CLI> icim
ICIM> set commwrite “myCommWriteString”
NOTE: This change will not fully take effect until the ICIM is restarted.
Until that time, some operations will not perform as expected.
SUCCESS!

94 4021339 Rev B
 CLI Parameters
ICIM> set commread “myCommReadString”
NOTE: This change will not fully take effect until the ICIM is restarted.
Until that time, some operations will not perform as expected.
SUCCESS!
ICIM> set commtrap “myCommTrapString”
NOTE: This change will not fully take effect until the ICIM is restarted.
Until that time, some operations will not perform as expected.
SUCCESS!

You can then verify the community string settings, as follows.

ICIM> info commread commwrite commtrap
COMMREAD COMMWRITE COMMTRAP
myCommReadString myCommWriteString myCommTrapString
SUCCESS!
ICIM>

Note:
  We strongly recommend restarting the ICIM2 or ICIM2-XD after changing any of
the community strings. Otherwise, some operations will continue to work
normally, while others will appear to fail.
  We strongly recommend creating new SNMP community strings and removing
the default SNMP community strings. Default SNMP community string values
are listed below.

SNMP Community String Default Value

Read Community public
Write Community private
Trap Community SNMP_trap

4021339 Rev B 95
Chapter 4 Equipment Configuration

Telnet Session
Telnet is a remote terminal emulation program included with the Microsoft
Windows operating system. In the absence of an element management system, you
can use Telnet to initiate a remote communications session with an ICIM2 or ICIM2-
XD and configure it using CLI commands.
Important:
  For Telnet operation, the computer you are using must have a network
connection through which it can reach the ICIM2 or ICIM2-XD via its IP address.
  No more than four Telnet sessions are allowed at one time.
CAUTION:
Always use the Logout command to close a serial port or Telnet CLI session.
Closing a serial port session without issuing the Logout command leaves the
session open for a possible future connection. This may allow unauthorized
access by a new user if the previous user had a higher authorization privilege
level.

To Set Up a Telnet CLI Session

Complete the following steps to initiate a CLI session with the ICIM2 or ICIM2-XD
using Telnet.
Important: The ICIM2 or ICIM2-XD must have an IP address assigned before
performing this procedure.
1 Open a DOS window on the PC that will connect to the ICIM2 or ICIM2-XD.
2 At the DOS command prompt, type:
telnet <IP address>
where <IP address> is the IP address of the ICIM2 or ICIM2-XD. The session
starts and the Telnet login: prompt appears.

96 4021339 Rev B
 Telnet Session

3 At the login: prompt, type Administrat0r (note the zero character in the string),
and then press Enter.
4 At the Password: prompt, type AdminPassw0rd (note the zero character in the
string), and then press Enter. The CLI> command prompt appears.

4021339 Rev B 97
Chapter 4 Equipment Configuration

SNMP Parameters
Trap settings and other parameters can be set in either of two ways:
  Using Simple Network Management Protocol (SNMP) commands. Refer to
SNMP Management (on page 171) for details on accessing the ICIM MIB tables.
  Using the Command Line Interface (CLI) traps enable command. Refer to the
Prisma II Platform Remote User Interface Guide, part number 4012441 for details on
using this command.
Once this is accomplished, changes can be made to the entries in the ICIM Trap
table. There are 10 entries in this table, one for each destination IP address.
Following are the objects in the p2TrapRecvEntry table that should be set.

MIB Object Value

p2TrapRecvEnable 1-disabled; 2-enabled
p2TrapRecvAddr IP address of trap receiver
p2TrapRecvTelcoAlarm 1-disabled; 2-enabled

98 4021339 Rev B
 5 Chapter 5
Operation using ICIM
Introduction
The procedures in this chapter apply if you are using an ICIM2 or
ICIM2-XD software interface to configure and operate the Prisma II
XD Platform.

Scope of This Chapter

This chapter includes procedures for using the ICIM2-XD software
interface to configure and operate the Prisma II XD Platform. A Prisma
II ICIM2 front-panel interface can also be used to configure and
operate the Prisma II XD Platform through a daisy-chain connection.
For further information, see the appropriate Prisma II system
documentation.

In This Chapter
ƒ ICIM Introduction............................................................................... 100
ƒ ICIM Front Panel................................................................................. 102
ƒ Operating the ICIM ............................................................................ 103
ƒ Setting Trap Receive Parameters ...................................................... 108

4021339 Rev B 99
Chapter 5 Operation using ICIM

ICIM Introduction
Laser Warning
WARNING:

ƒ Avoid personal injury! Use of controls, adjustments, or procedures other

than those specified herein may result in hazardous radiation exposure.

ƒ Avoid personal injury! The laser light source on this equipment (if a
transmitter) or the fiber cables connected to this equipment emit invisible
laser radiation. Avoid direct exposure to the laser light source.

ƒ Avoid personal injury! Viewing the laser output (if a transmitter) or fiber
cable with optical instruments (such as eye loupes, magnifiers, or
microscopes) may pose an eye hazard.

  Do not apply power to this equipment if the fiber is unmated or unterminated.

  Do not stare into an unmated fiber or at any mirror-like surface that could reflect
light emitted from an unterminated fiber.
  Do not view an activated fiber with optical instruments (e.g., eye loupes,
magnifiers, microscopes).
  Use safety-approved optical fiber cable to maintain compliance with applicable
laser safety requirements.
  Even if the unit is off, there may still be hazardous optical levels present.

Overview
The ICIM2-XD serves as the interface between the user and the application modules
installed in a chassis or daisy chain. It also serves as the interface between each
application module in the chassis or daisy chain and the Transmission Network
Control System (TNCS). The ICIM2-XD supports configuration and status
monitoring for up to 64 modules located in 4 Prisma II XD chassis.
In most respects, ICIM2-XD operation is identical to that of ICIM and ICIM2 control
modules found in other Prisma II chassis. The ICIM2-XD features easy-to-use
software that is navigated remotely via CLI, SNMP, or the ICIM Web Interface.
Unlike the ICIM and ICIM2, however, the ICIM2-XD is mounted in the back of the
chassis and has no LCD display or keypad.
Important:
  There can be only one ICIM2-XD per daisy-chain connection of Prisma II XD
chassis.
  All chassis connected in a daisy chain must have a unique chassis identification
(ID) number.

100 4021339 Rev B

 ICIM Introduction

  The last chassis in a daisy chain must have a terminator installed in the ICIM
OUT connector. Otherwise, faulty communication with the ICIM2-XD may
occur.

ICIM2-XD Block Diagram

The main components and functions of the ICIM2-XD are illustrated in the block
diagram below.

Prisma II XD Chassis
Midplane
ICIM Configuration and Monitoring Bus ICIM
In
DB-9 DB-9 Out
Midplane
Connection

Microprocessor

Hardware
Interface

Hardware
RS-232 CLI
Interface

Hardware Ethernet
RJ-45
Interface

ICIM2-XD
Module

TP472

4021339 Rev B 101

Chapter 5 Operation using ICIM

ICIM Front Panel

ICIM2-XD Illustration (Front Panel)

ICIM2-XD Front Panel Features

Part Function
Ethernet connector Directly connects the ICIM2-XD to an IP network. The front-panel
Ethernet port is suitable for connection to intra-building wiring,
non-exposed wiring or cabling only.
RS232 connector Used to connect a co-located PC to the Prisma II Enhanced system
for local console port CLI communication and setup.

102 4021339 Rev B

 Operating the ICIM

Operating the ICIM

Once the XD platform is installed, it runs without the aid of an operator. If alarms
are generated or your system configuration changes, you can use the ICIM2-XD to
make any adjustments needed beyond the initial setup.

Operating Status Parameters

The following tables describe the parameters used to monitor and control operation
of the XD chassis itself. Operating parameters for each application module are
described in the module documentation. See Related Publications (on page 33).

Monitor Parameters and Examples

Parameter Function Initial Operating

Value Value (typ)
PSA Inst 1 if power supply A is installed and 1 (Installed 1 (Installed
powered, 0 if not and and
powered) powered)
ConvAIns 1 if converter A is installed, 0 if not 1 (Installed) 1 (Installed)
ConvA+24 Measured +24 V DC of slot A 24.1148 V 24.1148 V
ConvA+5 Measured +5 V DC of slot A 5.29054 V 5.29054 V
ConvA-5V Measured -5 V DC of slot A -5.29926 V -5.29926 V
PSB Inst 1 if power supply B is installed and 0 (Not 1 (Installed)
powered, 0 if not installed)
ConvBIns 1 if converter B is installed, 0 if not 1 (Installed) 1 (Installed)
ConvB+24 Measured +24 V DC of slot B 24.1481 V 24.1481 V
ConvB+5 Measured +5 V DC of slot B 5.0949 V 5.0949 V
ConvB-5V Measured -5 V DC of slot B -5.02933 V -5.02933 V
Chas+24 Chassis +24 V bus 24.14 V 24.14 V
Chas+5 Chassis +5 V bus 5.08 V 5.08 V
Chas-5 Chassis -5 V bus -5.05 V -5.05 V
ChasTemp Chassis internal temperature 26.5°C 26.5°C

Note: All monitored values may vary from module to module. The values shown
above are examples only.

4021339 Rev B 103

Chapter 5 Operation using ICIM

Control Parameters

Control Function Value Default

AlmMuteA Alarm muting for power section A 0 (OFF) 0 (OFF)
1 (ON)
AlmMuteB Alarm muting for power section B 0 (OFF) 0 (OFF)
1 (ON)

User Alarm Data Parameters

The table below describes the user alarm data parameters for the XD chassis.

Alarm Function Major Minor Minor Major Hysteresis Typical

Low Low High High Range/
Threshold Threshold Threshold Threshold Nom.
Value
ChasTemp Fan tray -40°C -35°C 60°C 65°C 1°C -40°C to
temperature 65°C /
25°C
ConvA+24 +24 V alarm 18.0 VDC 18.4 VDC 25.9 VDC 26.1 VDC 0.1 VDC 23.8 to
for supply A 25.6
VDC /
24.7 V
ConvA+5 +5 V alarm 3.6 VDC 3.7 VDC 5.9 VDC 6.1 VDC 0.1 VDC 4.9 to
for supply A 5.3 VDC
/ 5.4 V
ConvA-5 -5 V alarm -5.6 VDC -5.5 VDC -4.6 VDC -4.5 VDC 0.1 VDC -5.3 to
for supply A -4.9
VDC / -
5.4 V
ConvB+24 +24 V alarm 18.0 VDC 18.4 VDC 25.9 VDC 26.1 VDC 0.1 VDC 23.8 to
for supply B 25.6
VDC /
24.7 V
ConvB+5 +5 V alarm 3.6 VDC 3.7 VDC 5.9 VDC 6.1 VDC 0.1 VDC 4.9 to
for supply B 5.3 VDC
/
5.4 V
ConvB-5 -5 V alarm -5.6 VDC -5.5 VDC -4.6 VDC -4.5 VDC 0.1 VDC -5.3 to
for supply B -4.9
VDC / -
5.4 V

Module Alarm Data Parameters

The table below describes the module alarm data parameters for the XD chassis.

104 4021339 Rev B

 Operating the ICIM

Alarm Function Major Minor Minor Major Hysteresis Typical

Low Low High High Range/
Threshold Threshold Threshold Threshold Nom.
Value
Fan 1_Ok Fan 1 status na na na na na OK or
Fault
Fan 2_Ok Fan 2 status na na na na na OK or
Fault
Fan 3_Ok Fan 3 status na na na na na OK or
Fault
ConvAIn Converter A na na na na na OK or
power status Fault
ConvBIn Converter B na na na na na OK or
power status Fault

Manufacturing Data Parameters

The tables below describe the manufacturing data available for this module.

XD Chassis

Manufacturing Data Typical Values

Module Name P2-XD-CHASSIS
Module Type 5020
Manufacturing Data <NULL>
Serial # [1] AAFHJJT
Date Code [1] K06
Module ID <NULL>
CLLI Code [1] <NULL>
CLEI Code [1] <NULL>
Sw Ver (Software Version) [1] 1.01.00
In Service Hours [1] 372

ICIM2-XD

Manufacturing Data Typical Values

Module Name P2-ICIM2-XD
Module Type 5011
Manufacturing Data ICIM2
Serial # [1] ~AAVGTHZ

4021339 Rev B 105

Chapter 5 Operation using ICIM

Manufacturing Data Typical Values

Date Code [1] C07
Module ID <NULL>
CLLI Code [1] <NULL>
CLEI Code [1] <NULL>
Hardware Revision BdRev87A
Sw Ver (Software Version) [1] 2.02.10
In Service Hours [1] 372

Note: [1] These values may vary from module to module. The values shown above
are examples only.

SNMP Considerations
The following items should be considered when implementing SNMP.
  The SNMP connection is made through the Ethernet port on the front of the
ICIM2 or ICIM2-XD. (Use 10baseT cable with an RJ-45 connector.) In order to
meet the requirements of GR1089-CORE, a shielded cable must be used and both
ends must be grounded.
  The network management system (NMS) must be installed behind a firewall to
prevent any ill-intentioned persons with an SNMP manager from accessing and
tampering with the ICIM2 or ICIM2-XD.
  When the ICIM2 or ICIM2-XD has to handle excessive SNMP traffic, it will
respond slowly to both SNMP control and front panel input. If this occurs,
reduce the update rate of the SNMP manager.

Basic SNMP Setup

Refer to your SNMP manager documentation or MIB information for instructions on
implementing SNMP. Before you can use and reconfigure SNMP services, you need
to know the community strings in your network and the IP addresses or computer
names for SNMP management hosts to which traps are sent.

106 4021339 Rev B

 Operating the ICIM

Default Community Strings

The community string provides primitive security and context checking for both
agents and managers that request and initiate trap operations. An agent does not
accept a request from a manager outside the community.
Community strings that the expects are:
Read Community public
Write Community private
Trap Community SNMP_trap

4021339 Rev B 107

Chapter 5 Operation using ICIM

Setting Trap Receive Parameters

You can use the ICIM Web Interface to specify up to 10 IP addresses to which
proprietary traps will be sent. You can also specify the events that will result in a
trap being sent to the network management systems at these IP addresses. For
details, see the Prisma II Platform Remote User Interface Guide, part number 4012441.
Note: The Cold Start trap will always be sent to all network management systems.

108 4021339 Rev B

 6 Chapter 6
Operation using LCI
Introduction
This chapter provides installation and operating instructions for Local
Craft Interface (LCI). This information is useful if you are using LCI to
configure, operate, or monitor a module.

In This Chapter
ƒ LCI Introduction ................................................................................. 110
ƒ System Requirements......................................................................... 111
ƒ Installing LCI ....................................................................................... 112
ƒ Connecting Your Computer to the Chassis..................................... 115
ƒ Starting LCI Software ......................................................................... 116
ƒ LCI Module Tree ................................................................................. 117
ƒ Accessing the Module Detail Information ...................................... 118
ƒ Checking the Operating Status ......................................................... 124
ƒ Configuring the Module using LCI.................................................. 126
ƒ Checking the Module Alarms using LCI......................................... 128
ƒ Modifying Module Alarm Limits using LCI................................... 131
ƒ Checking Manufacturing Data using LCI ....................................... 134

4021339 Rev B 109

Chapter 6 Operation using LCI

LCI Introduction
LCI Function
Local Craft Interface (LCI) is software that functions as a user interface to the Prisma
II XD Platform. LCI is installed on a laptop or desktop PC, which is then connected
to the chassis via the LCI port. You can use LCI to configure, operate, and monitor
the modules in the chassis to which the PC is connected.

110 4021339 Rev B

 System Requirements

System Requirements
You will need the following computer software and hardware to run LCI.

Computer Requirements
  Pentium II 300 MHz processor or equivalent
  128 MB RAM
  10 MB available hard drive space
  CD-ROM Drive
  Windows 95 or later operating system software

Cable Requirements
The required cable is a standard serial extension cable, DB9 Female to DB9 Male.
This cable can be purchased locally or ordered from the factory as part number
180143. The connectors are a serial 9-pin D-shell (EIA 574/232).

4021339 Rev B 111

Chapter 6 Operation using LCI

Installing LCI
This section describes how to install your LCI software.

To Install the LCI Software

Complete the following steps to install the LCI software.
1 Close all programs that are running on your computer.
2 Insert the LCI CD-ROM into your CD-ROM drive.
Results:
ƒ The LCI software installation program starts automatically. If the installation
program does not start automatically, open Windows Explorer and double-
click the file setup.exe on the LCI CD-ROM.
ƒ The Welcome screen appears as shown in the following illustration.

3 Click Next to continue with the installation process.

112 4021339 Rev B

 Installing LCI

Result: The Ready to Install the Program screen appears as shown in the
following illustration.

4 Click Install to begin installation.

Result: After a moment, the Setup Status screen appears displaying a progress
indicator, as shown in the following illustration.

4021339 Rev B 113

Chapter 6 Operation using LCI

5 When finished, the Installation Wizard Complete screen appears, as shown in the
following illustration.

6 Click Finish to exit the Install wizard.

Result: An LCI shortcut is placed on your Windows desktop, as shown in the
following illustration.

The LCI software is now ready to use.

114 4021339 Rev B

 Connecting Your Computer to the Chassis

Connecting Your Computer to the Chassis

Before you start LCI, you must first connect your computer to the chassis that
contains the module(s) you want to check.
Important:
  LCI only communicates with modules installed in the chassis to which your
computer is connected. To check other modules, you must connect your
computer to the chassis in which they are installed.
  If LCI does not communicate with a module in the chassis to which your
computer is connected, it may be necessary to update the LCI application.

To Connect a Computer to the Chassis

1 Plug one end of a 9-pin serial extension cable into your computer.
2 Plug the other end of the cable into the LCI port, labeled Local Craft Interface.

4021339 Rev B 115

Chapter 6 Operation using LCI

Starting LCI Software

When LCI is started, it polls the module(s) located in the chassis to which your
computer is attached. For each module it finds, LCI does the following:
  Represents the module in the module tree of the main LCI window
  Makes the polling information available so you can check and configure various
parameters
Important: Your computer must be connected to the chassis before you start LCI. For
instructions, refer to Connecting Your Computer to the Chassis (on page 115).

To Start LCI Software

To start the software, double-click the LCI icon on your Windows desktop.

Results:
  LCI polls the modules in the chassis.
  The main LCI window appears.

116 4021339 Rev B

 LCI Module Tree

LCI Module Tree

The LCI main window contains a tree that represents your system in a hierarchical
manner.

Module Tree
The module tree shown above represents a computer connected to a chassis that
contains no application modules. The following table describes the three tree levels
in the hierarchy.

Module Tree Level Description

Local (System 0) Computer being used
Chassxx (Chassis) Chassis to which the computer is connected
Sxxxx (Module name) Module(s) located within the chassis. Each module is of the
format chassis slot location (module name).
Example: In the module tree shown above, S3000 (Chassis)
represents a power supply located in slot 0 of chassis 30.
Note: If this chassis had application modules installed, they
would be listed together with the power supply with
designations S30xx, where xx would indicate the slot number.

4021339 Rev B 117

Chapter 6 Operation using LCI

Accessing the Module Detail Information

The Module Details window displays information about module parameters, alarms,
and status. You can access this window from the module tree using any of these
methods:
  Double-click the chassis and select the module in the graphic that appears.
  Right-click the chassis and select Open from the menu that appears.
  Double-click the module.
  Right-click the module and select Details from the menu that appears.
Although you can use the method most convenient for you, the procedures
throughout this chapter are described using the right-click module technique.
Note: Two items that may appear in the Module Details window are mode-specific.
Manual Alarm status only appears in the Controls section when Master mode is
selected. Relay status only appears in the Status section when Slave mode is selected.

Module Details Window

118 4021339 Rev B

 Accessing the Module Detail Information

To Access the Module Details, Double-Click the Chassis

1 Double-click the chassis.

Result: A graphic representation of the chassis appears.

2 Double-click the module whose information you want to view or configure.

Result: The Module Details window appears.

4021339 Rev B 119

Chapter 6 Operation using LCI

3 Proceed with viewing or configuring information.

To Access the Module Details, Right-Click the Chassis

1 Right-click the chassis, and then click Open.

Result: A graphic representation of the chassis appears.

2 Double-click the module whose information you want to view or configure.

120 4021339 Rev B

 Accessing the Module Detail Information

Result: The Module Details window appears.

3 Proceed with viewing or configuring information.

To Access the Module Details, Double-Click the Module

1 Double-click the module.

4021339 Rev B 121

Chapter 6 Operation using LCI

Result: The Module Details window appears.

2 Proceed with viewing or configuring information.

To Access the Module Details, Right-Click the Module

1 Right-click the module, and then click Details.

122 4021339 Rev B

 Accessing the Module Detail Information

Result: The Module Details window appears.

2 Proceed with viewing or configuring information.

4021339 Rev B 123

Chapter 6 Operation using LCI

Checking the Operating Status

To Check the Operating Status using LCI
Using the LCI, you can check the status of all operating parameters of this module.
1 In the module tree, right-click the module, and then click Details.

Result: The Module Details window appears. The monitored parameters are
displayed under Parameters and Status.

2 Check the operating parameters.

Operating Status Parameters

The table below describes the operating status parameters for the chassis.

124 4021339 Rev B

 Checking the Operating Status

Parameter Function Operating Range

or Nominal Value
PS A Installed Displays installation status of AC-to-DC bulk Yes or No
power supply module A
PS B Installed Displays installation status of AC-to-DC bulk Yes or No
power supply module B
Converter A Displays installation status of DC-to-DC converter Yes or No
Installed assembly A
Converter B Displays installation status of DC-to-DC converter Yes or No
Installed assembly B
+24V Chassis Displays current +24 VDC chassis midplane bus 24.2 VDC
voltage level
+5V Chassis Displays current +5 VDC chassis midplane bus +5.2 VDC
voltage level
-5V Chassis Displays current -5 VDC chassis midplane bus -5.2 VDC
voltage level

4021339 Rev B 125

Chapter 6 Operation using LCI

Configuring the Module using LCI

To Set Control Parameters using LCI
Using LCI, you can configure the parameters of this module.
1 In the module tree, right-click the module, and then click Details.

Result: The Module Details window appears.

2 Under Controls, double-click the parameter you want to configure.

126 4021339 Rev B

 Configuring the Module using LCI

Result: The Change Value dialog box appears. This example shows the dialog
box for the Mute Converter A Alarm parameter.

3 Depending on the parameter you chose, select or type a new value.

4 Click Execute.
Result: The new value appears next to the parameter.

XD Chassis Control Parameters

Control Function Value Default
AlmMuteA Alarm muting for power section A 0 (OFF) 0 (OFF)
1 (ON)
AlmMuteB Alarm muting for power section B 0 (OFF) 0 (OFF)
1 (ON)

4021339 Rev B 127

Chapter 6 Operation using LCI

Checking the Module Alarms using LCI

Using LCI, you can check the alarm status of various parameters. Alarms that you
can check are listed below.
Alarms limits fall into one of the following categories.
  Major low
  Minor low
  Minor high
  Major high

To Check Alarms using LCI

Right-click the module, and then click Details.

128 4021339 Rev B

 Checking the Module Alarms using LCI

Result: The Module Details window appears. The alarms are shown under
Parameters and Alarms.

Alarm Data Parameters

The tables below describe the alarm data parameters for this module.

User Alarm Data Parameters

Alarm Function Major Minor Minor Major Hysteresis Typical

Low Low High High Range/
Threshold Threshold Threshold Threshold Nom.
Value
ChasTemp Fan tray -40°C -35°C 60°C 65°C 1°C -40°C to
temperature 65°C /
25°C
ConvA+24 +24 V alarm 18.0 VDC 18.4 VDC 25.9 VDC 26.1 VDC 0.1 VDC 23.8 to
for supply A 25.6
VDC /
24.7 V
ConvA+5 +5 V alarm 3.6 VDC 3.7 VDC 5.9 VDC 6.1 VDC 0.1 VDC 4.9 to
for supply A 5.3 VDC
/ 5.4 V
ConvA-5 -5 V alarm -5.6 VDC -5.5 VDC -4.6 VDC -4.5 VDC 0.1 VDC -5.3 to
for supply A -4.9
VDC / -
5.4 V

4021339 Rev B 129

Chapter 6 Operation using LCI

Alarm Function Major Minor Minor Major Hysteresis Typical

Low Low High High Range/
Threshold Threshold Threshold Threshold Nom.
Value
ConvB+24 +24 V alarm 18.0 VDC 18.4 VDC 25.9 VDC 26.1 VDC 0.1 VDC 23.8 to
for supply B 25.6
VDC /
24.7 V
ConvB+5 +5 V alarm 3.6 VDC 3.7 VDC 5.9 VDC 6.1 VDC 0.1 VDC 4.9 to
for supply B 5.3 VDC
/
5.4 V
ConvB-5 -5 V alarm -5.6 VDC -5.5 VDC -4.6 VDC -4.5 VDC 0.1 VDC -5.3 to
for supply B -4.9
VDC / -
5.4 V

Module Alarm Data Parameters

Alarm Function Major Minor Minor Major Hysteresis Typical

Low Low High High Range/
Threshold Threshold Threshold Threshold Nom.
Value
Fan 1_Ok Fan 1 status na na na na na OK or
Fault
Fan 2_Ok Fan 2 status na na na na na OK or
Fault
Fan 3_Ok Fan 3 status na na na na na OK or
Fault
ConvAIn Converter A na na na na na OK or
power status Fault
ConvBIn Converter B na na na na na OK or
power status Fault

130 4021339 Rev B

 Modifying Module Alarm Limits using LCI

Modifying Module Alarm Limits using LCI

To Modify Alarm Limits using LCI
Using LCI, you can modify alarm limits for several parameters. Parameters whose
alarm limits you can change are listed below.
1 In the module tree, right-click the module, and then click Details.

Result: The Module Details window appears. The alarm limits are shown under
Parameters.

2 Double-click the limit you want to change.

4021339 Rev B 131

Chapter 6 Operation using LCI

Result: The Change Value dialog box appears. This example shows the dialog
box for the chassis temperature Minor Low limit parameter.

3 In the Command to box, type the value to use for the limit.
4 Click Execute.
Result: The new value appears in the alarm limit column.

Alarm Limit Parameters

The table below describes the alarm limit parameters for this module.

User Alarm Limit Parameters

Alarm Function Major Minor Minor Major Hysteresis Typical

Low Low High High Range/
Threshold Threshold Threshold Threshold Nom.
Value
ChasTemp Fan tray -40°C -35°C 60°C 65°C 1°C -40°C to
temperature 65°C /
25°C
ConvA+24 +24 V alarm 18.0 VDC 18.4 VDC 25.9 VDC 26.1 VDC 0.1 VDC 23.8 to
for supply A 25.6
VDC /
24.7 V
ConvA+5 +5 V alarm 3.6 VDC 3.7 VDC 5.9 VDC 6.1 VDC 0.1 VDC 4.9 to
for supply A 5.3 VDC
/ 5.4 V
ConvA-5 -5 V alarm -5.6 VDC -5.5 VDC -4.6 VDC -4.5 VDC 0.1 VDC -5.3 to
for supply A -4.9
VDC / -
5.4 V
ConvB+24 +24 V alarm 18.0 VDC 18.4 VDC 25.9 VDC 26.1 VDC 0.1 VDC 23.8 to
for supply B 25.6
VDC /
24.7 V

132 4021339 Rev B

 Modifying Module Alarm Limits using LCI

Alarm Function Major Minor Minor Major Hysteresis Typical

Low Low High High Range/
Threshold Threshold Threshold Threshold Nom.
Value
ConvB+5 +5 V alarm 3.6 VDC 3.7 VDC 5.9 VDC 6.1 VDC 0.1 VDC 4.9 to
for supply B 5.3 VDC
/
5.4 V
ConvB-5 -5 V alarm -5.6 VDC -5.5 VDC -4.6 VDC -4.5 VDC 0.1 VDC -5.3 to
for supply B -4.9
VDC / -
5.4 V

Module Alarm Limit Parameters

Alarm Function Major Minor Minor Major Hysteresis Typical

Low Low High High Range/
Threshold Threshold Threshold Threshold Nom.
Value
Fan 1_Ok Fan 1 status na na na na na OK or
Fault
Fan 2_Ok Fan 2 status na na na na na OK or
Fault
Fan 3_Ok Fan 3 status na na na na na OK or
Fault
ConvAIn Converter A na na na na na OK or
power status Fault
ConvBIn Converter B na na na na na OK or
power status Fault

4021339 Rev B 133

Chapter 6 Operation using LCI

Checking Manufacturing Data using LCI

To Check Manufacturing Data using LCI
Using LCI, you can check the manufacturing data of the module.
1 In the module tree, right-click the module, and then click Details.

Result: The Module Details window appears. The manufacturing data is

displayed under Properties.

2 Proceed with viewing the manufacturing data.

Manufacturing Data Parameters

The table below describes the manufacturing data available for this module.

134 4021339 Rev B

 Checking Manufacturing Data using LCI

XD Chassis

Manufacturing Data Typical Values

Module Name P2-XD-CHASSIS
Module Type 5020
Manufacturing Data <NULL>
Serial # [1] AAFHJJT
Date Code [1] K06
Module ID <NULL>
CLLI Code [1] <NULL>
CLEI Code [1] <NULL>
Sw Ver (Software Version) [1] 1.01.00
In Service Hours [1] 372

ICIM2-XD

Manufacturing Data Typical Values

Module Name P2-ICIM2-XD
Module Type 5011
Manufacturing Data ICIM2
Serial # [1] ~AAVGTHZ
Date Code [1] C07
Module ID <NULL>
CLLI Code [1] <NULL>
CLEI Code [1] <NULL>
Hardware Revision BdRev87A
Sw Ver (Software Version) [1] 2.02.10
In Service Hours [1] 372

Note: [1] These values may vary from module to module. The values shown above
are examples only.

4021339 Rev B 135

 7 Chapter 7
User Management
Introduction
This chapter explains the procedures for adding and removing ICIM2-
XD users and for changing user access and authorization levels.

In This Chapter
ƒ Introduction ......................................................................................... 138
ƒ Replacing the Default Admin Account............................................ 141
ƒ Working With User Accounts ........................................................... 144
ƒ User Lockout ....................................................................................... 151

4021339 Rev B 137

Chapter 7 User Management

Introduction
The ICIM2 and ICIM2-XD support up to 16 user accounts. This chapter describes
user accounts in detail and explains how the system administrator (a user with
Admin level security access) can set up and edit user accounts through the CLI or
ICIM Web Interface. Additionally, this chapter includes a table of access levels and
corresponding resources, which identifies activities available to users with specific
privileges.

User Accounts
Each user account is set up with a username and password. To initiate an account,
the system administrator first chooses the access level and the status. Accounts to be
activated immediately are given the status enable, while those whose activation
should be delayed are given the status disable. The system administrator may also
adjust the inactivity timeout as well as the limit of failed log-in attempts for the
ICIM2 or ICIM2-XD.
When a user logs onto the ICIM2 or ICIM2-XD via the CLI or ICIM Web Interface,
the username and password are checked for authentication. A check is also
performed to ensure that the user account is enabled. Users with disabled accounts
are not permitted access to the ICIM2 or ICIM2-XD.
Additionally, security levels are compared to ensure that the user is authorized to
access only the options appropriate to their access level. Another check verifies that
the user has not reached the login failure limit as defined by the system
administrator and saved in the ICIM2 or ICIM2-XD. A trap is sent if a user reaches
the failed login attempts limit, and the user is prevented from making further login
attempts for a designated lockout time period.

Usernames
Usernames, also known as login IDs, can be formed from the alphanumeric
characters A through Z (uppercase), a through z (lowercase), and the numbers 0
through 9. Usernames cannot contain special characters (such as @, %, and &) or
control characters (characters generated by holding down the Ctrl key). Usernames
must have at least 6 characters, cannot exceed 14 characters, and must contain at
least one alphabetic character and at least one numeric character.
The username cannot be changed once it is created. If entered incorrectly, the system
administrator must delete the user account and create a new account using the
correct username, password, status, and access level.

138 4021339 Rev B

 Introduction

Passwords
Passwords can be formed from the alphanumeric characters A through Z
(uppercase), a through z (lowercase), the numbers 0 through 9, and special
characters (such as @, %, and &). Passwords cannot contain control characters
(characters generated by holding down the Ctrl key). Passwords must have at least 6
characters, cannot exceed 14 characters, and must contain at least one alphabetic
character and at least one numeric character. Additionally, the password may not
include or consist solely of the username (login ID).
For security reasons, passwords are not echoed when adding, changing, or entering
them at login. If you forget your password, contact the system administrator, as only
he or she is able to change it. Users with Admin level privileges can change the
password for any user.

Security Levels
User account security levels define the privileges available to users at that level.
Choices are Read-Only, Read-Write, and Admin. The system administrator must
have Admin privileges in order to add, change, or delete user accounts, or to modify
system settings for the ICIM2 or IC IM2-XD and the modules in its domain.
Users who do not need to modify module alarm thresholds or controls should be
assigned Read-Only privileges. Users who need to regulate module information or
change CLLI codes need Read-Write privileges.
See Features Available via Remote User Interface (on page 319) for details regarding
features available through the remote interface and user access levels required to
view or edit data elements.

Account Enable or Disable

Each account is assigned a status of enable or disable. If an account is enabled, it may
be used right away. If disabled, the account may not be accessed until the system
administrator has activated it. The disabled account status is useful for employees
who are temporarily unavailable because they have not started work yet or are on
vacation.
Each time someone attempts to log into a disabled account, a trap is sent alerting
management to the event. The attempt is also logged in the event log.
Note: If you discover that your account is disabled, contact your system
administrator.

4021339 Rev B 139

Chapter 7 User Management

Login Thresholds
The login threshold defines the number of failed login attempts that must occur
before a maximum threshold trap is sent. Admin level users may adjust the login
threshold for the ICIM2 or ICIM2-XD. This threshold is the same for all users on a
particular ICIM2 or ICIM2-XD. The default is 5 times, and the range is from 0 to 15.
Login failure threshold checking may be disabled by setting the threshold to 0. A
failed login attempt trap is sent for every failed login attempt.

User Lockout
Beginning with System Release 2.01, User Lockout may be enabled to prevent users
who exceed the maximum failed login attempts threshold from logging in for a
designated lockout interval (60 minutes by default). Locked-out users may try to log
in again after the user lockout period expires or after an administrator removes the
lockout. For further details, see User Lockout (on page 151).

Inactivity Timeout
The inactivity timeout is the number of minutes that a user account must be idle
following login before it is automatically logged out by the ICIM2 or ICIM2-XD. The
timeout value is the same number of minutes for all users on a particular ICIM2 or
ICIM2-XD. The default is 10 minutes, but this value may be set anywhere from 1 to
60 minutes by a user with Admin privileges. The inactivity timeout cannot be
disabled.

140 4021339 Rev B

 Replacing the Default Admin Account

Replacing the Default Admin Account

The ICIM2 and ICIM2-XD ship from the factory with a single default Admin level
account. This account is assigned the username Administrat0r and the password
AdminPassw0rd (in both, zero replaces the letter o).
For security reasons, it is strongly recommended that the system administrator add a
new Admin user level as the first step after starting up the ICIM2 or ICIM2-XD.
After this new Admin level user is added, the default Admin user account may be
deleted.
Important: Before deleting the default Admin user account, be sure that you have
created a new Admin account and noted its login defaults for future reference.
Failure to remember the new username and password may result in being locked
out of the ICIM2 or ICIM2-XD permanently. You cannot revert to the default Admin
username and password once they are deleted.

To Replace the Default Admin Account

Complete the following steps to replace the default Admin account.

From the CLI

1 Log on to the ICIM2 using the default username and password.
The sample dialog below shows the addition of a new user account newAdmin1
with password enterpassword1.
CLI> icim
ICIM> user add newAdmin1 admin enable
Please enter the password: enterpassword1
Please reenter the password: enterpassword1
Note: Passwords are not echoed to the terminal as they are entered.
2 Type show user, and then confirm that the new user appears in the resulting list
of user names.
3 Log off of the ICIM2 or ICIM2-XD.
4 Log back on to the ICIM2 or ICIM2-XD using the new Admin account username
and password.
5 At the ICIM prompt, type user delete Administrat0r. The following message
appears:
You are about to delete user ‘Administrat0r’ from the authorization table.
6 To confirm, type yes, and then press Enter.
7 Type show user, and then confirm that the user Administrat0r no longer appears
in the resulting list of user names.

4021339 Rev B 141

Chapter 7 User Management

From the Web Interface

1 Log onto the ICIM2 or ICIM2-XD using the default username and password.

2 Click User Mgmt in the menu in the left pane. The User Management table
appears as shown below.

3 Click the New User button beneath the User Management table. The New User
Information screen appears as shown below.

142 4021339 Rev B

 Replacing the Default Admin Account

4 Enter the User ID and Password in the fields provided, and then enter the
password again in the Confirm Password field.
Note: The password information you enter is not displayed.
5 Select the appropriate Security Level and Status from the drop-down menus.
6 Click the Save button to save your settings.
7 Log out of the ICIM2 or ICIM2-XD.
8 Log back onto the ICIM2 or ICIM2-XD using the new Admin account name and
password. For example:
newAdmin1
enterpassword1
9 Click User Mgmt in the menu in the left pane.
10 When the User Management Table appears, move the mouse to the delete button
next to the row with the default Admin account username Administrat0r.

11 Click the delete button to remove the default Admin account.

Important:
  Keep track of the Administrator username and password. There is no way to
retrieve the default username and password once they are deleted.
  Use the new Administrator account whenever performing system administrator
tasks.

4021339 Rev B 143

Chapter 7 User Management

Working With User Accounts

The system administrator may perform any of these functions related to user
accounts:
  Add new user accounts to give new users access to the ICIM2 or ICIM2-XD via
the CLI and Web Interface.
  Change the password, security access level, or status (enabled or disabled) for a
user account.
  Unlock user accounts that have become locked due to excessive failed login
attempts.
  Delete user accounts that were entered in error or are no longer needed.
  View a list of currently logged in users.
This section describes the steps for each of these procedures.

To Add a New User

When setting up a new account, the system administrator first determines the
appropriate user access level for the account. The administrator then determines
whether the account will come up in a disabled or enabled state.
Complete the following steps to add a new user.

From the CLI

1 Log on to the ICIM2 or ICIM2-XD using an account with Admin privileges.
2 Enter ICIM mode.
3 Add the user at the ICIM prompt. For example:
ICIM> user add newUser1 read enable
Please enter the password: userpassword1
Please reenter the password: userpassword1
Note: Passwords are not echoed to the terminal as they are entered.
4 Type show user, and then confirm that the new user appears in the resulting list
of usernames.
ICIM> show user
LOGIN IDENTIFIER ACCESS LEVEL STATUS LAST LOGIN FAILED LOCKED
sysAdmin ADMIN Enabled 11/21/06 15:02:47 0 No
icim22 ADMIN Enabled 11/07/06 10:05:46 0 No
newAdmin1 ADMIN Enabled 11/21/06 15:06:11 0 No
newUser1 READ Enabled 00/00/00 00:00:00 0 No

From the Web Interface

1 Log on to the ICIM2 or ICIM2-XD using an account with Admin privileges.

144 4021339 Rev B

 Working With User Accounts

2 Click User Mgmt in the menu in the left pane.

3 When the User Management table appears, click the New User button beneath
the table. A New User Information form appears.

4 Enter the required user account information in the form:

ƒ username (e.g., newUser1)
ƒ password (e.g., userpassword1)
ƒ confirm password (e.g., userpassword1)
Note: Usernames and passwords must contain 6 to 14 characters and include at
least 1 alphabetic character and at least 1 number.
5 Choose the appropriate access level (Read-Only, Read-Write, or Admin) from the
drop-down menu.
6 Choose the appropriate account status (enable or disable) from the drop-down
menu.
7 Click the Save button to keep the changes, and then click OK on the
confirmation dialog to confirm the change.
8 Verify that the new account appears on the User Management table with the
correct information.

To Change a User Password

Complete the following steps to change a user password.

From the CLI

1 Log on to the ICIM2 or ICIM2-XD using an account with Admin privileges.
2 Enter ICIM mode.
3 Add the user at the ICIM prompt. For example:
ICIM> user change password newUser1
Please enter the password: changepassword2
Please reenter the password: changepassword2
Note: Passwords are not echoed to the terminal as they are entered.

4021339 Rev B 145

Chapter 7 User Management

From the Web Interface

1 Log on to the ICIM2 or ICIM2-XD using an account with Admin privileges.
2 Click User Mgmt in the menu in the left pane.
3 When the User Management table appears, click the Edit button on the row next
to the account with the password to be changed.
4 When the edit window appears, verify that you are changing the correct account.

5 Type the new password in the password box (e.g., changepassword2).

6 Confirm the password in the confirmation box (e.g., changepassword2).
Note: Passwords are not echoed to the terminal as they are entered.
7 Click the Save button near the Confirm Password field.
8 When the OK to Save dialog box appears, choose Save.
9 Confirm that the user appears on the User Management table.

To Change a User Security Level

Complete the following steps to change a user security level.

From the CLI

1 Log on to the ICIM2 or ICIM2-XD using an account with Admin privileges.
2 Enter ICIM mode.
3 Edit the user information at the ICIM prompt. For example:
ICIM> user change access_rights newUser1 readwrite
4 Type show user, and then confirm that the change appears in the Access Level
column of the User Management table.
ICIM> show user
LOGIN IDENTIFIER ACCESS LEVEL STATUS LAST LOGIN FAILED LOCKED
sysAdmin ADMIN Enabled 11/21/06 15:02:47 0 No

146 4021339 Rev B

 Working With User Accounts
icim22 ADMIN Enabled 11/07/06 10:05:46 0 No
newAdmin1 ADMIN Enabled 11/21/06 15:06:11 0 No
newUser1 READWRITE Enabled 00/00/00 00:00:00 0 No

From the Web Interface

1 Log on to the ICIM2 or ICIM2-XD using an account with Admin privileges.
2 Click User Mgmt in the menu in the left pane. The User Management table
appears.
3 Click the Edit link on the row next to the account with the Security Level to be
changed.
4 In the edit window, verify that you are changing the correct account.

5 Choose the appropriate Security Level from the drop-down menu.

6 Click the Save button on the Security Level row.
7 When the OK to Save dialog box appears, choose Save.
8 Confirm that the User Management table reflects the new security level.

To Change User Account Status

Complete the following steps to change (enable or disable) user account status.

From the CLI

1 Log on to the ICIM2 or ICIM2-XD using an account with Admin privileges.
2 Enter ICIM mode.
3 Edit the user information at the ICIM prompt. For example:
ICIM> user change account_status newUser1 disable
4 Type show user, and then confirm that the change appears in the Status column
of the User Management table.
ICIM> show user

4021339 Rev B 147

Chapter 7 User Management
LOGIN IDENTIFIER ACCESS LEVEL STATUS LAST LOGIN FAILED LOCKED
sysAdmin ADMIN Enabled 11/21/06 15:02:47 0 No
icim22 ADMIN Enabled 11/07/06 10:05:46 0 No
newAdmin1 ADMIN Enabled 11/21/06 15:06:11 0 No
newUser1 READ Disabled <None> 0 No

From the Web Interface

1 Log on to the ICIM2 or ICIM2-XD using an account with Admin privileges.
2 Click User Mgmt in the menu in the left pane. The User Management table
appears.
3 Click the Edit link on the row next to the account with the status to be changed.
4 In the edit window, verify that you are changing the correct account.

5 Choose the appropriate Status from the drop-down menu.

6 Click the Save button on the Status row.
7 When the OK to Save dialog box appears, choose Save.
8 Confirm that the User Management table reflects the new status.

To Unlock User Accounts

Users who reach a specified maximum number of failed ICIM2 or ICIM2-XD login
attempts may have their user accounts locked. These users will be unable to log in
until a predetermined lockout interval expires, or until a system administrator
unlocks the account. For complete instructions on working with the User Lockout
feature and unlocking user accounts, see User Lockout (on page 151).

To Delete a User Account

Complete the following steps to delete a user account.

148 4021339 Rev B

 Working With User Accounts

From the CLI

1 Log on to the ICIM2 or ICIM2-XD using an account with Admin privileges.
2 Enter ICIM mode.
3 Add the user at the ICIM prompt. For example:
ICIM> user delete newUser1
4 Type show user, and then confirm that the account is no longer listed in the
resulting User Management table.
ICIM> show user
LOGIN IDENTIFIER ACCESS LEVEL STATUS LAST LOGIN FAILED LOCKED
sysAdmin ADMIN Enabled 11/21/06 15:02:47 0 No
icim22 ADMIN Enabled 11/07/06 10:05:46 0 No
newAdmin1 ADMIN Enabled 11/21/06 15:06:11 0 No

From the Web Interface

1 Log on to the ICIM2 or ICIM2-XD using an account with Admin privileges.
2 Click User Mgmt in the menu in the left pane. The User Management table
appears.

3 Click the Delete button next to the row with the username for the account to
remove.
4 In the confirmation box, verify that you are deleting the account that you intend
to remove.
5 Verify that the account is not listed on the User Management Table.
Note: After an account is deleted, there is no more information concerning it except
what has already been logged in the event log file.

To List All Currently Logged In Users

Complete the following steps to list all current ICIM2 or ICIM2-XD users.

From the CLI

1 Navigate to the ICIM prompt.
2 Type who, and then press Enter to display a list of current users.

4021339 Rev B 149

Chapter 7 User Management
ICIM> who
LOGIN IDENTIFIER IP ADDRESS TYPE LOGIN TIME
icim22 172.9.9.12 CLI 11/21/06 15:08:10
newAdmin1 172.8.8.12 WEB 11/21/06 14:18:34

From the Web Interface

1 Click the User Mgmt menu option on the left pane.
2 View the Currently Logged In table in the lower section of the page.

150 4021339 Rev B

 User Lockout

User Lockout
The User Lockout feature imposes a temporary lockout on ICIM2 or ICIM2-XD users
who reach the maximum number of failed login attempts. Users who are locked out
will not be able to log in to the ICIM2 or ICIM2-XD until the lockout interval expires,
even if they try to log in using the correct login information.
By default, User Lockout is enabled with a lockout interval of 60 minutes. Admin
users can select any lockout interval from 1 to 60 minutes, or can set the interval to 0
to disable User Lockout. All changes made to the lockout interval are recorded in the
event log.
Admin users have commands available for checking the lockout time remaining by
user and for unlocking a locked user account before the lockout interval expires.
Admin users and users with unknown user names are not subject to lockouts.
Lockout data is stored in volatile memory, so if the ICIM2 or ICIM2-XD reboots, this
data is lost and all users are unlocked.
This section describes the following User Lockout actions available to Admin users:
  View the current lockout interval
  Specify a new lockout interval
  View locked-out users
  View lockout time remaining by user
  Unlock a locked-out user
Admin users can perform all of these actions through CLI commands, and can view
the current lockout interval, specify a new interval, and view locked-out users
through the ICIM Web Interface.

To View the Current Lockout Interval

Complete the following steps to view the current status of the User Lockout feature.

From the CLI

1 Log on to the ICIM2 or ICIM2-XD using an account with Admin privileges.
2 Enter ICIM command mode.
3 Type show lockout, and then press Enter. The system displays the current user
lockout interval, as shown in the example below.
ICIM> show lockout
LOCKOUT
60
SUCCESS!
ICIM>

4021339 Rev B 151

Chapter 7 User Management

The number following LOCKOUT is the current length of the lockout interval in
minutes. An interval of 0 means that user lockout is disabled.
Note: You can use info lockout instead of show lockout; the two commands
have identical functions.

From the Web Interface

1 Log on to the ICIM2-XD using an account with Admin privileges.
2 Click System Settings in the menu in the left pane. The System Settings table
appears as shown in the example below.

3 Note the value in the Lockout Interval field. This number indicates the current
length of the lockout interval in minutes. A value of 0 means that User Lockout is
disabled.

To Specify a New Lockout Interval

Complete the following steps to either disable User Lockout or to enable this feature
and specify a new lockout interval.

From the CLI

1 Log on to the ICIM2 or ICIM2-XD using an account with Admin privileges.
2 Enter ICIM mode.
3 Type set lockout x, where x is a whole number from 0 to 60, and then press
Enter. The system acknowledges your entry, as shown in the example below.
ICIM> set lockout 30
SUCCESS!
ICIM>
Note:
ƒ Setting the lockout interval to 0 disables user lockout.
ƒ Never change the User Lockout interval while a user is locked, as this may
result in an unexpected actual lockout interval for the user.

From the Web Interface

1 Log on to the ICIM2-XD using an account with Admin privileges.
2 Click System Settings in the menu in the left pane.

152 4021339 Rev B

 User Lockout

3 When the System Settings table appears, click in the Lockout Interval field and
type the desired lockout value in the space provided.

4 Click Apply to save your changes, or click Cancel to abort.

To View Locked-Out Users

Complete the following steps to view a list of all users and their current lockout
status.

From the CLI

1 Log on to the ICIM2 or ICIM2-XD using an account with Admin privileges.
2 Enter ICIM mode.
3 Type show user, and then press Enter. The system displays a list of all users, as
shown in the example below.
ICIM> show user
LOGIN IDENTIFIER ACCESS LEVEL STATUS LAST LOGIN FAILED LOCKED
Administrat0r ADMIN Enabled 03/08/07 11:11:32 0 No
document2 READ Enabled <None> 0 Yes
icim22 READ Enabled <None> 0 No
newUser5 READ Enabled <None> 0 No
4 Check the values in the LOCKED column. Any users with YES in this column,
such as document2 in the example above, are currently locked out.
Note: When a user account becomes locked, the Failed count (number of failed
login attempts) is returned to zero.

From the Web Interface

1 Log on to the ICIM2 or ICIM2-XD using an account with Admin privileges.

4021339 Rev B 153

Chapter 7 User Management

2 Click User Mgmt in the menu in the left pane. The User Management table
appears as shown in the example below.

3 Note the value in the LOCKED column. Any users with YES in this column, such
as firstUser2 in the example above, are currently locked out.

To View Lockout Time Remaining by User

Note: This feature is available only to Admin users and is accessible only through
CLI.
Complete the following steps to view the lockout time remaining for all currently
locked out users.

From the CLI

1 Log on to the ICIM2 or ICIM2-XD using an account with Admin privileges.
2 Enter ICIM mode.
3 At the ICIM prompt, type show lockedusers, and then press Enter. A listing of
all currently locked out users and their remaining lockout time appears, as
shown in the example below.
ICIM> show lockedusers
LOCKED USER MINUTES UNTIL UNLOCK
firstUser2 12
SUCCESS!
ICIM>

Note: If no users are currently locked out, the word (none) will appear in the list.

To Unlock a Locked-Out User

Note: This feature is available only to Admin users and is accessible only through
the CLI.
Complete the following steps to unlock a user account that has been locked due to
excessive incorrect login attempts.

From the CLI

1 Log on to the ICIM2 or ICIM2-XD using an account with Admin privileges.

154 4021339 Rev B

 User Lockout

2 Navigate to the ICIM prompt.

3 Type user unlock <username>, where <username> is the name of the user to be
unlocked, and then press Enter.
ICIM> user unlock firstUser2
SUCCESS!
ICIM>

The user account is now unlocked, and the user will be able to attempt to log in
again.

Alternative Methods
There are two other ways to unlock a user account that has been locked out:
  Cycle power to the ICIM2 or ICIM2-XD off and then on again. Because lockout
information is stored in volatile memory, cycling power to the ICIM2 or ICIM2-
XD returns all users to default unlocked status.
  In the Web Interface, use the Unlock User feature in the Edit User window under
User Management. For details, see To Change User Account Status in Working
with User Accounts (on page 144).
Note: Never change the User Lockout interval while a user is locked, as this may
result in an unexpected actual lockout interval for the user.

4021339 Rev B 155

 8 Chapter 8
Event Log
The ICIM2 and ICIM2-XD use an event log to record certain events in
Prisma II systems. This chapter describes the structure of the event log
and identifies actions that it can record. Instructions are provided for
viewing the event through the CLI or ICIM Web Interface, and for
maintaining the event log via CLI commands.

In This Chapter
ƒ Introduction ......................................................................................... 158
ƒ Viewing the Event Log....................................................................... 161
ƒ Clearing the Event Log ...................................................................... 163
ƒ Setting Event Log Filter Parameters................................................. 164
ƒ Event Log-Related Traps ................................................................... 166
ƒ Downloading and Viewing the Event Log Remotely.................... 168

4021339 Rev B 157

Chapter 8 Event Log

Introduction
The ICIM2 and ICIM2-XD maintain a log of significant events that occur in the
Prisma II system due to non-EMS user activity. The log can be viewed by Admin
level users through the CLI or ICIM Web Interface. It can also be downloaded to an
FTP server for offline viewing.
Certain types of events can be selected for exclusion from the log. Additionally,
changes made through the MIB, usually by the EMS, are not part of the event log.
The event log holds up to 5,000 events. If a new event is logged when the log is
already full, the oldest event is removed and the new event is added. To minimize
log wrapping, several traps are sent to indicate that the log is nearing capacity, and
one trap is sent to indicate that the log is full.
The EMS user or administrator must empty the log each time it nears capacity. To
empty the event log, the EMS user or administrator will typically first upload the log
file from the ICIM2 or ICIM2-XD to an FTP server, and then clear the log file for new
events.

Event Log Fields

Each event in the event log contains the following fields.

Date and Time (Timestamp)

This field records the date and time that the event was logged.

User Name (User ID)

This field records the name of the user whose actions caused the event. Some events,
such as inserting or removing a module, will not contain a user name.

User Access Rights (Security Level)

This field records the access rights of the user whose actions caused the event.
Possible values of this field will be:
  Admin
  Read-Only
  ReadWrite
  Unknown (e.g., if there is no user name)

Event Category
This field records the category of the event. Possible values of this field will be:
  Security

158 4021339 Rev B

 Introduction

  Administration
  System
  Hardware
  Provision

Event Action ID
This field records the action ID of the event. Possible values are detailed later.

Event Description
This field contains text describing the event in more detail. For example, if a module
is inserted, the description would list the chassis and slot numbers for the insertion.

Event Action IDs

Each event that can appear in the event log is identified by a unique character string
called an action ID. The table below lists the action IDs for these events and
identifies their respective event categories.
Note: Action IDs may appear differently depending on whether the log is viewed
through the CLI or ICIM Web Interface.

Event Action ID Event Category

LOGIN_SUCCESS SECURITY
LOGIN_FAILED SECURITY
LOG_OFF SECURITY
SESSION_TIMEOUT SECURITY
LOGIN_THRSHLD_RCHD SECURITY
USER_ACCT_LOCKOUT SECURITY
CHG_LOGIN_THRESHOLD ADMINISTRATION
CHG_TRAP_DESTINATION ADMINISTRATION
CHG_INACTIVITY_TIMER ADMINISTRATION
CHG_USER ADMINISTRATION
GET_USER ADMINISTRATION
CHG_LOG_OPTION ADMINISTRATION
SET_CLOCK ADMINISTRATION
CHG_LOCKOUT_INTERVAL ADMINISTRATION
LOG_NEAR_FULL SYSTEM
LOG_FULL SYSTEM

4021339 Rev B 159

Chapter 8 Event Log

Event Action ID Event Category

DOWNLOAD_START SYSTEM
DOWNLOAD_COMPLETE SYSTEM
REBOOT SYSTEM
SYSTEM_ERROR SYSTEM
WATCHDOG_CPU_OVERLOAD SYSTEM
WATCHDOG_REBOOT SYSTEM
EVENTLOG_FORMAT SYSTEM
SELFTEST_FAILED SYSTEM
SNTP_FAILED SYSTEM
MODULE_INSERT HARDWARE
MODULE_REMOVE HARDWARE
CHG_SERVICE_MODE PROVISION
SET_CLLI PROVISION
SET_COMMREAD PROVISION
SET_COMMWRITE PROVISION
SET_COMMTRAP PROVISION
SET_GATEWAY PROVISION
SET_IP PROVISION
SET_SUBNET PROVISION
SET_UPDATEID PROVISION
SET_MODULE_CTRL PROVISION
SET_ALARM_PARAM PROVISION
ADD_ROUTE PROVISION
DELETE_ROUTE PROVISION

160 4021339 Rev B

 Viewing the Event Log

Viewing the Event Log

As an Admin user, you can view the event log through the CLI or ICIM Web
Interface. This section describes both viewing methods.

To View the Event Log through the CLI

Two CLI commands are available for viewing the event log.
  The icim show eventlog displays an abbreviated version of the event log. Only
the Date and Time, User Name, and Description fields are included, so most log
entries will fit on a single line on the terminal screen.
  The icim show eventlogall command displays all log fields: Date and Time, User
Name, User Access Rights, Event Category, Action ID, and Description. Some
fields use abbreviations to maintain a display that is readable on a terminal.
Examples of each command are shown below.

Abbreviated Event Log

To view an abbreviated version of the event log, use the icim show eventlog
command as shown in the following example.
CLI> icim show eventlog
11/17/06 09:24:17 Administrat0r Set ICIM CLLI to ICIM2_CLLI
11/17/06 09:23:33 Administrat0r Log Off
11/17/06 09:22:57 Module inserted (1/12)
11/17/06 09:22:55 Module inserted (1/9)
11/17/06 09:22:32 Administrat0r Login successful
5 log messages displayed
SUCCESS!
CLI>

Note: As indicated in the example above, no user name is shown for module
insertion events.

Full Event Log

To view a full version of the event log that includes all fields, use the icim show
eventlogall command as shown in the following example.
CLI> icim show eventlogall
11/17/06 09:24:17 Administrat0r AD PR SET_CLLI Set ICIM CLLI t
o ICIM2_CLLI
11/17/06 09:23:33 Administrat0r AD SE LOG_OFF Log Off
11/17/06 09:22:57 HW MODULE_INSERT Module inserted
(1/12)
11/17/06 09:22:55 HW MODULE_INSERT Module inserted
(1/9)
11/17/06 09:22:32 Administrat0r AD SE LOGIN_SUCCESS Login successfu
l
5 log messages displayed
SUCCESS!
CLI>

4021339 Rev B 161

Chapter 8 Event Log

As this example shows, the full view of the event log provides more detail, but may
be more difficult to read because the log entries typically do not fit on a single line.
To shorten the entries and help improve readability, abbreviated values are used in
the User Access Rights and Event Category columns. The User Access Rights column
will contain one of the following abbreviated values:
  AD (Admin)
  RW (ReadWrite)
  RO (Read-Only)
Note: If the user name is blank (as in the Module Insert event), the User Access
Rights field will also be blank.
Similarly, the Event Category column will contain one of the following values:
  SE (Security)
  AD (Administration)
  SY (System)
  HW (Hardware)
  PR (Provisioning)

To View the Event Log through the ICIM Web Interface

After logging in, select Event Log from the menu in the left column. The Event Log
table appears, resembling the example below.

The event log is displayed one page at a time, with up to 25 logs per page. To scroll
through any additional pages, use the Previous and Next links located above the
Event Log table.

162 4021339 Rev B

 Clearing the Event Log

Clearing the Event Log

The event log must be periodically cleared of events to prevent event wrapping
when the log gets full. Typically, the log is first downloaded to an FTP server and
then cleared from the ICIM2 or ICIM2-XD memory.
As an Admin user, you can clear the event log through the CLI or ICIM Web
Interface. This section describes both methods.

To Clear the Event Log through the CLI

To clear the log, use the icim eventlogclear command. This will clear the entire log.
You will be prompted for confirmation before the log is cleared, as shown in the
example below.
CLI> icim eventlogclear
You are about to remove 6 entries from the system log.
Are you sure you want to proceed (Yes/No)? yes
SUCCESS!
CLI>

To Clear the Event Log through the Web

With the event log displayed in the ICIM Web Interface, click the Clear Event Log
button. You will be asked to confirm the operation.

Click OK to continue.

4021339 Rev B 163

Chapter 8 Event Log

Setting Event Log Filter Parameters

Associated with the event log are filter parameters that determine whether certain
types of events are included in or excluded from the log.
Events are included or excluded according to event category. Each event belongs to
one of the following event categories:
  Administration
  Hardware
  Provisioning
  Security
  System
Administration and Security events are always included in the event log. System,
Hardware, and Provisioning events may be included or excluded by changing filter
parameters. Changes to event log filter parameters only affect the logging of future
events. Events that are already part of the log file will remain in the log file,
regardless of subsequent filter parameter changes.
As an Admin user, you can view and set event log filter parameters through the CLI
or ICIM Web Interface. This section describes both methods.

To View Filter Parameters through the CLI

To view the current filter parameter settings, use the icim show eventlogfilter
command as shown in the following example.
CLI> icim show eventlogfilter
Event Log Settings:
Provisioning Events: on
Hardware Events: on
System Events: on
(a value of "on" means to log events of that category)
SUCCESS!
CLI>

To Set Filter Parameters through the CLI

To change filter parameters through the CLI, use the following command:
icim eventlogfilter [category] [setting]
The possible values for [category] and [setting] are listed below along with their
resulting effects on the filter settings.

164 4021339 Rev B

 Setting Event Log Filter Parameters

[category] [setting] Result

hardware on Includes hardware events in the event log.
hardware off Excludes hardware events from the event log.
provisioning on Includes provisioning events in the event log.
provisioning off Excludes provisioning events from the event log.
system on Includes system events in the event log.
system off Excludes system events from the event log.

The example below turns off logging of hardware events, and then shows the filter
parameters settings.
CLI> icim eventlogfilter hardware off
SUCCESS!
CLI> icim show eventlogfilter
Event Log Settings:
Provisioning Events: on
Hardware Events: off
System Events: on
(a value of "on" means to log events of that category)
SUCCESS!
CLI>

To View Filter Parameters through the Web

To view the current filter parameter settings, log in to the ICIM Web Interface and
then select the System Settings page from the left menu. The second group of items
on this page shows the event log settings.

To Set Filter Parameters through the Web

To change the current filter parameter settings, use the check boxes in the Event Log
Settings group on the System Settings page.

Check the box beside each event category to be included in the log, and clear the box
beside each category to be excluded. When finished, click the Apply button to save
your changes, or click Cancel to abort.

4021339 Rev B 165

Chapter 8 Event Log

Event Log-Related Traps

To alert the EMS of possible lost event log entries due to wrapping, the ICIM2 or
ICIM2-XD sends several traps as the log nears capacity. A trap is sent when the log is
80%, 85%, 90%, 95%, and 100% full. Thus, five traps are sent if the EMS takes no
action to clear the log. Once the log reaches 100% full and begins wrapping, no more
"log full" traps are sent.
The traps contain all the varbinds defined as part of that trap type. All traps except
the 100% full trap specify LogMemHalfFull as the p2TrapLogLabel varbind,
although the p2TrapLogDescr varbind specifies the percentage. The 100% full trap
specifies LogMemoryFull as the p2TrapLogLabel varbind.
Examples of the 80% full trap and the 100% full trap are shown below.

Example: 80% Full Trap

Specific: 9
Message reception date: 9/13/2006
Message reception time: 2:27:25.066 PM
Time stamp: 0 days 00h:11m:20s.13th
Message type: Trap (v1)
Protocol version: SNMPv1
Transport: IP/UDP
Agent
Address: 172.24.28.193
Port: 1035
Manager
Address: 172.18.9.66
Port: 162
Community: prismatrap
SNMPv1 agent address: 172.24.28.193
Enterprise: p2trapEvents
Bindings (15)
Binding #1: p2TrapLogSequence *** (int32) 12
Binding #2: p2TrapLogSeverity *** (int32) warning(3)
Binding #3: p2TrapLogState *** (int32) event(3)
Binding #4: p2TrapLogLabel *** (octets) LogMemHalfFull
Binding #5: p2icimStatusMsg.0 *** (int32) 0
Binding #6: p2TrapLogText *** (octets) ICIM2
Binding #7: p2chassisID.2.15 *** (int32) 2
Binding #8: p2slotID.2.15 *** (int32) 15
Binding #9: p2moduleCLLIcode.2.15 *** (octets) 1.2.243
Binding #10: p2moduleCLEIcode.2.15 *** (octets) (zero-length)
Binding #11: p2TrapLogTime *** (octets) 2006-9-13,1:51:39.42
Binding #12: p2TrapLogDateTime *** (octets) Wed, 13 Sep 2006 01:51:39 EST
Binding #13: p2TrapLogValue *** (octets) N/A
Binding #14: p2TrapLogUnit *** (octets) N/A
Binding #15: p2TrapLogDescr *** (octets) Log memory is %80 full

166 4021339 Rev B

 Event Log-Related Traps

Example: 100% Full Trap

Specific: 9
Message reception date: 9/13/2006
Message reception time: 2:44:27.081 PM
Time stamp: 0 days 00h:28m:22s.13th
Message type: Trap (v1)
Protocol version: SNMPv1
Transport: IP/UDP
Agent
Address: 172.24.28.193
Port: 1039
Manager
Address: 172.18.9.66
Port: 162
Community: prismatrap
SNMPv1 agent address: 172.24.28.193
Enterprise: p2trapEvents
Bindings (15)
Binding #1: p2TrapLogSequence *** (int32) 16
Binding #2: p2TrapLogSeverity *** (int32) warning(3)
Binding #3: p2TrapLogState *** (int32) event(3)
Binding #4: p2TrapLogLabel *** (octets) LogMemoryFull
Binding #5: p2icimStatusMsg.0 *** (int32) 0
Binding #6: p2TrapLogText *** (octets) ICIM2
Binding #7: p2chassisID.2.15 *** (int32) 2
Binding #8: p2slotID.2.15 *** (int32) 15
Binding #9: p2moduleCLLIcode.2.15 *** (octets) 1.2.243
Binding #10: p2moduleCLEIcode.2.15 *** (octets) (zero-length)
Binding #11: p2TrapLogTime *** (octets) 2006-9-13,2:8:41.45
Binding #12: p2TrapLogDateTime *** (octets) Wed, 13 Sep 2006 02:08:41 EST
Binding #13: p2TrapLogValue *** (octets) N/A
Binding #14: p2TrapLogUnit *** (octets) N/A
Binding #15: p2TrapLogDescr *** (octets) Log memory is %100 full

4021339 Rev B 167

Chapter 8 Event Log

Downloading and Viewing the Event Log Remotely

You can download the event log from the ICIM2 or ICIM2-XD to an FTP server at
any time. It is recommended that you download the file before it reaches capacity in
order to avoid losing the oldest log events as new events are added.
You use the prismaIIFileMgmtGroup MIB in SNMP to initiate transfer of the event
log file. For additional information, see Event Log File Management (on page 184).

To Download the Event Log File

Complete the following steps in SNMP to initiate the event log file download.
1 Set p2icimFileMgmtUsername to the FTP user name.
2 Set p2icimFileMgmtPassword to the FTP password.
3 Set p2icimFileMgmtIpAdress to the IP address of the FTP server.
4 Set p2icimFileMgmtFilePath to the path of the destination file on the FTP server.
5 Set p2icimFileMgmtFileName to the destination file name on the FTP server.
6 Set p2icimFileMgmtCmd to upload(1).
7 Set p2icimFileMgmtAction to execute(2).
In response to these commands, the ICIM2 or ICIM2-XD logs in to the FTP server
and transfers the event log file.
The event log file itself is a text file with space-separated columns. It is formatted
almost identically to the response to the icim show eventlogall command from the
CLI. Most recent events appear at the bottom of the file, and there is no file header.

168 4021339 Rev B

 Downloading and Viewing the Event Log Remotely

A sample portion of the event log file as downloaded from the ICIM2 or ICIM2-XD
to an FTP server is shown below.

In this example:
  The date-time format is yyyy/mm/dd hh:mm:ss, and seconds are shown
without leading zeros.
  Event categories are abbreviated, with Security shown as SE and Provisioning
shown as P.

4021339 Rev B 169

 9 Chapter 9
SNMP Management
Introduction
This chapter provides information about using Simple Network
Management Protocol (SNMP) commands for remote system
monitoring and control. The ICIM2 and ICIM2-XD recognize SNMP v1
and v2c commands, but to ensure backward compatibility, only send
SNMP v1 traps.
See Module Parameter Descriptions (on page 331) for parameter
descriptions.

In This Chapter
ƒ Introduction ......................................................................................... 172
ƒ ICIM MIB ............................................................................................. 173
ƒ Module MIB......................................................................................... 198
ƒ Remote Reboot of ICIM and Modules ............................................. 225
ƒ Prisma II Traps .................................................................................... 226
ƒ Delay in the Discovery Process......................................................... 263
ƒ Alarm Threshold Modification ......................................................... 264
ƒ System Behavior.................................................................................. 266
ƒ Frequently Asked Questions............................................................. 267

4021339 Rev B 171

Chapter 9 SNMP Management

Introduction
Simple network management protocol (SNMP) is an ISO standard communication
protocol commonly used by network and element management systems to monitor
network devices for alarms and other significant conditions.
SNMP accesses information about network devices through management
information base (MIB) objects. MIBs are hierarchical tree-structured descriptions
used to define database elements. SNMP is used to manage individual data elements
and the values assigned to MIB objects.
SNMP addresses a single MIB object using a numeric string called an object
identifier (OID). The OID defines a branching path through the hierarchy to the
location of the object. In addition to the OID, a MIB object is known by its object
descriptor, a text string intended to be more meaningful to a human operator. The
OID and object descriptor are unique to each MIB object.
Also defined for each MIB object is the access that SNMP can afford to the object
data value. For example, if a MIB object has read-write access, SNMP can be used to
both get (retrieve) and set (define or change) the value of the object. If an object is
read-only, SNMP can be used to get the object value, but not to change it.

Prisma II Enterprise MIBs

The Prisma II Enterprise management information bases (MIBs) allow easy access to
ICIM2 or ICIM2-XD, trap, and module information via SNMP. There are two
proprietary MIBs for management and event notification:
  SCIATL-PRISMAII-ICIM-MIB contains a scalar list of values used to control
Prisma II ICIM2 or ICIM2-XD management functions. Included are two trap
tables, one for trap configuration and the other for trap logging.
Current version: 200702222200Z
  SCIATL-PRISMAII-MODULE-MIB contains a series of tables for managing
Prisma II application modules.
Current version: 200702062209Z
These MIBs are based on the original ICIM MIBs, PRISMAII-ICIMR13-MIB and
PRISMAII-MODULER13-MIB, which are now considered obsolete.
Details of the elements of the ICIM MIB and MODULE MIB are provided in the
sections below.

172 4021339 Rev B

 ICIM MIB

ICIM MIB
MIB objects for the ICIM2 or ICIM2-XD fall into several categories. Information
includes the state of the ICIM in reference to network settings, FTP, download
control, and manufacturing data. Each of the ICIM2 or ICIM2-XD object identifiers
appears below with a description and other pertinent information concerning the
element.

To View the ICIM MIB

To view the Prisma II ICIM MIB, be sure to compile and load both proprietary MIBs,
SCIATL-PRISMAII-ICIM-MIB and SCIATL-PRISMAII-MODULE-MIB, in your MIB
browser.
The ICIM2 or ICIM2-XD object identifier (OID) is 1.3.6.1.4.1.1429.1.6.2.2.13.100. This
is the dot version of the full path that expands to:
iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).scientificatlanta(1429).saTerr(
1).saTerrOptical(6).saTerrOpticalPrismaII(2).saPrismaIIrev2(2).saPrismaIIicim(13).pr
ismaIIicim(100).

ICIM MIB Elements

The ICIM MIB contains the following elements, which are discussed in detail in this
section.

ICIM MIB Element Example Value

p2icimChassisID 6
p2icimSlotID 17
p2icimSMCAddress 615
p2icimType 5011
p2icimManufactureData ICIM2
p2icimSerialNumber AADORSF
p2icimHardwareRevision BdRev87A
p2icimSoftwareRevision 2.02.10
p2icimSoftwareDate 11032006
p2icimTimeOfService 219
p2icimMACAddr 00:14:FF:FF:FF:61
p2icimIPAddr 172.24.24.24
p2icimSubnetMask 255.255.255.0

4021339 Rev B 173

Chapter 9 SNMP Management

ICIM MIB Element Example Value

p2icimGatewayAddr 172.24.24.254
p2PreviousIP 174.24.24.23
p2icimUpdateChassisIDs 0
p2icimAttnStatus High (1)
p2icimDomainSize 6
p2icimNextImage currentActive (1)
p2icimActiveCodeRevision 2.00.08
p2icimInactiveCodeRevision * N/A
p2icimBootCodeRevision 2.02.03
p2icimFtpServerAddr * 172.24.13.12
p2icimFtpUsername * Set
p2icimFtpPassword * Set
p2icimDownLdDir * (zero-length)
p2icimDownLdFilename * ICIM2_2_00_08_app.BIN
p2icimDownLdCmd * Cancel (4)
p2icimDownLdState * Idle (1)
p2icimDownLdTarget * 100
p2icimDownLdResult * No-result-available (9999)
p2icimDownLdSignature * 1146728270
p2icimDownLdSemaphore * 1146720732
p2icimDownLdUser * 0
p2icimCLLIcode * SCIATL01
p2icimCLEIcode * VLLUAA4DAA
p2icimSelfTest ICIM Self-Test Passed
p2icimStatusMsg 6 Nov 03 2006 05:50:03 AM Broadcast reboot command
successful
p2icimDownLdProg * 0
p2icimClock 2006-12-15 11:38:57
p2icimTimeZone EDT
p2icimDateTime Fri, 15 Dec 2006 11:32:57 EST
p2icimNotify 0
p2icimStatusMsgClearKey 2
* Reserved for future use.

174 4021339 Rev B

 ICIM MIB

p2icimChassisID
The number that appears in the chassis ID switch on the front panel of the chassis in
which the ICIM2 or ICIM2-XD is installed indicates the value for the chassis ID (see
figure below). Valid chassis ID values are 00 to 99 inclusive. However, the use of 00
as the chassis ID value is not recommended in some circumstances, as the following
caution explains.
CAUTION:
Setting the chassis ID to 00 is not recommended as it causes the entity MIB to violate
RFC-2737 by creating an invalid object identifier. This may affect operation with some
management systems that use the entity MIB. In particular, attempts to access the fans
(in virtual slot 0) in chassis 00 will fail if made via serial TNCS (or ROSA-EM) or LCI.

Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.100.1

p2icimSlotID
The value in this object identifies the slot number in which the ICIM2 or ICIM2-XD is
installed, and is always 17.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.100.2

p2icimSMCAddress
The value in this object is the chassis number times 100 plus the ICIM2 or ICIM2-XD
slot number. Leading zeros may be cropped. Thus, for chassis 20, the
p2icimSMCAddress will be 2017.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.100.3

p2icimType
The value in this object is used to uniquely identify the ICIM2 or ICIM2-XD model.
In other contexts, this may be referred to as the devtype.
Access: read-only

4021339 Rev B 175

Chapter 9 SNMP Management

OID: 1.3.6.1.4.1.1429.1.6.2.2.13.100.4

p2icimManufactureData
This object holds a string of up to 30 characters that describes the ICIM2 or ICIM2-
XD in words. For this ICIM, the string is P2-ICIM2-XD.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.100.5

p2icimSerialNumber
This object holds the serial number assigned to this unit during the manufacturing
process.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.100.6

p2icimHardwareRevision
The value in this object is the hardware revision of the ICIM2 or ICIM2-XD, e.g.,
BdRev87A.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.100.7

p2icimSoftwareRevision
This object is no longer used, but is kept in place for backward compatibility. Active,
inactive, and boot code revisions display through p2icimActiveCodeRevision,
p2icimInactiveCodeRevision, and p2icimBootCodeRevision (described below).
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.100.8

p2icimSoftwareDate
The value in this object represents the date that the firmware was built, e.g.,
01202007 (Jan. 20, 2007).
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.100.9

p2icimTimeOfService
This object shows the number of hours that the ICIM2 or ICIM2-XD has been in
service, which may be any number of hours starting from 0.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.100.10

176 4021339 Rev B

 ICIM MIB

p2icimMACAddr
This object holds the physical MAC address assigned to the ICIM2 or ICIM2-XD, in
the form 00:11:22:33:44:55.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.100.12

p2icimIPAddr
This object holds the network IP address assigned to the ICIM2 or ICIM2-XD.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.100.13

p2icimSubnetMask
This object holds the network subnet mask used to reach the ICIM2 or ICIM2-XD.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.100.14

p2icimGatewayAddr
This object represents the network gateway address used by the ICIM2 or ICIM2-
XD.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.100.15

p2PreviousIP
This object returns the value 0.0.0.0 until the IP address of the ICIM2 or ICIM2-XD is
changed for the first time. After that, it holds the previous IP address.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.100.16

p2icimUpdateChassisIDs
Setting the value of this object to 1 updates every module in the ICIM2 or ICIM2-XD
domain with its chassis ID and slot number. As a result, each module sends all of its
information to the ICIM. It takes time for the ICIM2 or ICIM2-XD to update the
database with the new data. A get on this object always returns the value 0.
Access: read-write
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.100.19

4021339 Rev B 177

Chapter 9 SNMP Management

p2icimAttnStatus
This object will normally display high (1) unless one of the modules pulls the
attention line low (2). In that case, the ICIM2 or ICIM2-XD will service the request
from the module, and when complete, will return the attention line to high (1).
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.100.20

p2icimDomainSize
This object shows the number of modules managed by the ICIM2 or ICIM2-XD.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.100.21

p2icimNextImage
The value in this object indicates which image will be active following the next
ICIM2 or ICIM2-XD reboot. Values may be current active image (1) or current
inactive image (2).
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.100.22

p2icimActiveCodeRevision
This object displays the active firmware image revision for the ICIM2 or ICIM2-XD.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.100.23
This object is used to determine the active software version. The ICIM2 or ICIM2-XD
can store two flash images, one in the Active area and the other in the Inactive area.

p2icimInactiveCodeRevision
This object is reserved for future use.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.100.24

p2icimBootCodeRevision
This object displays the current boot image revision for the ICIM2 or ICIM2-XD.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.100.25

178 4021339 Rev B

 ICIM MIB

p2icimFtpServerAddr
WARNING:
This object is reserved for future use, and is not intended for use by system
operators.

Access: read-write
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.100.26

p2icimFtpUsername
WARNING:
This object is reserved for future use, and is not intended for use by system
operators.

Access: read-write
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.100.27

p2icimFtpPassword
WARNING:
This object is reserved for future use, and is not intended for use by system
operators.

Access: read-write
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.100.28

p2icimDownLdDir
WARNING:
This object is reserved for future use, and is not intended for use by system
operators.

Access: read-write
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.100.29

p2icimDownLdFilename
WARNING:
This object is reserved for future use, and is not intended for use by system
operators.

Access: read-write
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.100.30

p2icimDownLdCmd
WARNING:
This object is reserved for future use, and is not intended for use by system
operators.

4021339 Rev B 179

Chapter 9 SNMP Management

Access: read-write
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.100.31

p2icimDownLdState
This object is reserved for future use.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.100.32

p2icimDownLdTarget
This object is reserved for future use.
Access: read-write
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.100.33

p2icimDownLdResult
This object is reserved for future use.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.100.34

p2icimDownLdSignature
WARNING:
This object is reserved for future use, and is not intended for use by system
operators.

Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.100.35

p2icimDownLdSemaphore
WARNING:
This object is reserved for future use, and is not intended for use by system
operators.

Access: read-write
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.100.36

p2icimDownLdUser
WARNING:
This object is reserved for future use, and is not intended for use by system
operators.

Access: read-write

180 4021339 Rev B

 ICIM MIB

OID: 1.3.6.1.4.1.1429.1.6.2.2.13.100.37

p2icimCLLIcode
This object is reserved for future use.
Access: read-write
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.100.38

p2icimCLEIcode
This object is reserved for future use.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.100.39

p2icimSelfTest
Use this object to display the results of the basic functional self-test that the ICIM2 or
ICIM2-XD performs at boot-up. If the self-test runs with no failures, performing a
get on this object returns the message “ICIM Self-Test Passed.” If any failures occur,
a get on this object returns the message "ICIM Self-Test failed - Error Code” followed
by a decimal representation of the hexadecimal code of the failure(s).

ICIM Test Failed Hexadecimal Decimal

Code Value
SDRAM 0x01000001 16777217
Boot Flash 0x01000002 16777218
Application Flash 0x01000004 16777220
EEPROM 0x01000008 16777224
Real Time Clock 0x01000010 16777232
Real Time Clock Battery 0x01000020 16777248

If the ICIM2 or ICIM2-XD encounters more than one failure, the error code returned
is the sum of the individual error codes. For example:
  If the Real Time Clock Battery failed the self-test, the error code would be
16777248 decimal or 1000020 hex.
  If the Real Time Clock Battery and the Real Time Clock both failed the self-test,
the error code would be ((16 + 32) + 16777216 =) 16777264 decimal or ((10 + 20) +
1000000 =) 1000030 hex.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.100.40

4021339 Rev B 181

Chapter 9 SNMP Management

p2icimStatusMsg
Use this object to display the most recent status or error message saved in the ICIM2
or ICIM2-XD. An example of an informational message is:
6 Jan 18 2006 01:12:35 PM Broadcast reboot command successful

In this message:
  6 is the level, meaning notice.
  Jan. 18 2006 is the date.
  01:12:35 PM is the time.
  “Broadcast reboot command successful” is the message text.
The importance level of a message may be one of the following: emergency (1), alert
(2), critical (3), error (4), warning (5), notice (6), or general system (7).
Note: To clear p2icimStatusMsg, set p2icimStatusMsgClearKey to 1. Otherwise, the
current status message will persist until replaced by a message having an equal or
greater urgency level.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.100.41

p2icimDownLdProg
WARNING:
This object is reserved for future use, and is not intended for use by system
operators.

Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.100.42

p2icimClock
Perform a get on this object to return the ICIM2 or ICIM2-XD date and time in the
format: 2006-1-18,9:14:8. To change the clock, set this object in the format
MM/DD/YY HH:MM:SS, for example: 03/02/07 08:01:01. Note that leading zeros
are important.
Access: read-write
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.100.43

p2icimTimeZone
To add the time zone to the ICIM2 or ICIM2-XD, set p2icimTimeZone to one of the
valid USA time zones using the following abbreviations:

182 4021339 Rev B

 ICIM MIB

Abbreviation Time Zone

EST Eastern Standard Time
EDT Eastern Daylight Time
CST Central Standard Time
CDT Central Daylight Time
MST Mountain Standard Time
MDT Mountain Daylight Time
PST Pacific Standard Time
PDT Pacific Daylight Time
AST Alaska Standard Time
ADT Alaska Daylight Time
HST Hawaii-Aleutian Standard Time
HDT Hawaii-Aleutian Daylight Time

Note: If a time zone is not entered, the default time zone "EST" appears.
Access: read-write
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.100.44

p2icimDateTime
This object displays the day of the week, date, time, and time zone in the format
"Thu, 04 May 2006 22:43:11 EDT."
Note: If a time zone is not entered in p2icimTimeZone, the default time zone EST
(Eastern Standard Time) appears.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.100.45

p2icimNotify
This object tracks the number of times that an ICIM or module MIB object is set
through the CLI or ICIM Web Interface. The value in this object is an integer that
starts at 1 when the ICIM2 or ICIM2-XD boots up, and increments each time an ICIM
or module MIB object is set through the CLI or ICIM Web Interface.
If p2icimNotify reaches its maximum value of 2,147,483,647 (hexadecimal
7FFFFFFF), any further changes cause the value to return to 1 and increment again
from that point. Thus, once incremented, the value of p2icimNotify only returns to 0
if the ICIM2 or ICIM2-XD is reset.
Access: read-only

4021339 Rev B 183

Chapter 9 SNMP Management

OID: 1.3.6.1.4.1.1429.1.6.2.2.13.100.46

p2icimStatusMsgClearKey
This object lets you control whether status messages are cleared or kept by assigning
one of two possible values:

Value Function
1 Clear status messages
2 Keep status messages

Setting the value of this object to 2 lets the user exit the object gracefully, without
error messages or other impact. This setting also allows the status message to persist
unless replaced by a message of the same or greater urgency level. A get on this
object always returns the value 2.
Access: read-write
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.100.47

Event Log File Management

The Prisma II File Management Group (prismaIIFileMgmtGroup) is a subset of ICIM
MIB objects that lets you transfer an event log file from the ICIM2 or ICIM2-XD to a
remote computer or workstation. These objects also let you evaluate the progress of
the file transfer, as well as to clear the event log, which is recommended following an
event log file transfer.
The prismaIIFileMgmtGroup object identifier (OID) is 1.3.6.1.4.1.1429.1.6.2.2.13.101.
This is the dot version of the full path that expands to:
iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).scientificatlanta(1429).saTerr(
1).saTerrOptical(6).saTerrOpticalPrismaII(2).saPrismaIIrev2(2).saPrismaIIicim(13).pr
ismaIIFileMgmtGroup(101).
Step-by-step procedures for transferring and clearing the event log are provided
below following individual prismaIIFileMgmtGroup object descriptions.

p2icimFileMgmtCmd
This object selects the type of activity to perform: uploadLog (1) or clearLog (2). To
transfer the event log to a remote PC or workstation, set p2icimFileMgmtCmd to 1.
To clear all entries from the event log on the ICIM2 or ICIM2-XD and reformat it to
restart logging, set p2icimFileMgmtCmd to 2.
Note: p2icimFileMgmtCmd must be set before p2icimFileMgmtAction is set (see
below) in order to perform a successful event log transfer or clear action.
Access: read-write
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.101.1

184 4021339 Rev B

 ICIM MIB

p2icimFileMgmtAction
This object executes the event log transfer or clear action as defined by
p2icimFileMgmtCmd. When p2icimFileMgmtAction is set to execute (2), the file
transfer begins or the event log is cleared. Other valid values for
p2icimFileMgmtAction are idle (1) and abort (3).
Note: For a successful transfer or clear action to occur, p2icimFileMgmtCmd and all
other related prismaIIFileMgmtGroup MIB objects must be set before setting
p2icimFileMgmtAction to execute (2). To abort an upload, set
p2icimFileMgmtAction to abort (3).
Access: read-write
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.101.2

p2icimFileMgmtIpAdress
This object holds the destination FTP server IP address, in the format 172.240.250.1,
of the remote PC or workstation to which the event log will be transferred. For file
transfers, this object must be set before the command is executed.
Access: read-write
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.101.3

p2icimFileMgmtUsername
This object holds the FTP username for the file transfer process. The username may
be up to 31 characters. Before a username is entered, a get on
p2icimFileMgmtUsername returns "Not set." After a username is entered, a get on
this object returns "Set." The object does not return the username itself for security
reasons. For file transfers, this object must be set before the command is executed.
Access: read-write
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.101.4

p2icimFileMgmtPassword
This object holds the FTP password for the file transfer process. The password may
be up to 31 characters in length. Before a password is entered, a get on
p2icimFileMgmtPassword returns "Not set." After a password is entered, a get on
this object returns "Set." The object does not return the password itself for security
reasons. For file transfers, this object must be set before the command is executed.
Access: read-write
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.101.5

4021339 Rev B 185

Chapter 9 SNMP Management

p2icimFileMgmtFilePath
This object holds the full path (excluding the filename) where the event log should
be stored on the remote PC or workstation. The path may be up to 127 characters,
and may be of zero length. For file transfers, this object must be set before the
command is executed. A path of zero length implies the FTP server directory on the
remote machine.
Access: read-write
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.101.6

p2icimFileMgmtFileName
This object holds the name of the event log file following upload to the remote
system. The filename may be up to 31 characters in length, including an optional file
extension; for example, event1024.log. For file transfers, this object must be set before
the command is executed.
Access: read-write
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.101.7

p2icimFileMgmtXferSize
This object holds the size in bytes of the file to be transferred from the ICIM2 or
ICIM2-XD. This information is supplied by the underlying file transfer program, and
may be used together with p2icimFileMgmtXferBytes to calculate the progress of the
file transfer process (see below).
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.101.8

p2icimFileMgmtXferBytes
This object holds the number of bytes of the file that have been transferred so far.
This information is supplied by the underlying file transfer program, and may be
used together with p2icimFileMgmtXferSize to calculate the progress of the file
transfer process (see below).
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.101.9

p2icimFileMgmtResult
This object holds a value representing the progress or result of the file transfer,
which is provided by the underlying file transfer program. The possible values for
p2icimFileMgmtResult are listed below.
  unknown (1)
  idle (2)

186 4021339 Rev B

 ICIM MIB

  active (3)
  complete (4)
  failed (5)
  aborting (6)
  aborted (7)
Note: If no files have been transferred, the value displays as idle (2).
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.101.10

To Transfer an Event Log File

Complete the following steps to execute an event log file transfer.
1 Set the following MIB objects in the file management group:
ƒ p2icimFileMgmtUsername - file transfer FTP username
ƒ p2icimFileMgmtPassword - file transfer FTP password
ƒ p2icimFileMgmtIpAdress - destination IP address
ƒ p2icimFileMgmtFilePath - destination path omitting file name
ƒ p2icimFileMgmtFileName - destination file name only
2 Set p2icimFileMgmtCmd to upload (1).
3 Set p2icimFileMgmtAction to execute (2).
The event log file immediately starts to transfer via FTP (File Transfer Protocol) to
the designated remote IP address. This implies that an active FTP server is running
on the remote machine.

To Calculate File Transfer Progress

Complete the following steps to calculate progress at any point during the file
transfer process.
1 Get the current values of p2icimFileMgmtXferSize and
p2icimFileMgmtXferBytes.
2 Divide the value of p2icimFileMgmtXferBytes by the value of
p2icimFileMgmtXferSize.
3 Multiply by 100. The result is the percentage of the file size transferred so far.

To Clear the Event Log File

Complete the following steps to clear the event log.
1 Set p2icimFileMgmtCmd to clearEventlog (2).
2 Set p2icimFileMgmtAction to execute (2).

4021339 Rev B 187

Chapter 9 SNMP Management

After clearing the event log, logging will restart with the formatting of a new event
log and a single entry in the log noting the clear action.

Trap Handling
The Prisma II Trap Handling Group (prismaIItrap) is a subset of ICIM MIB objects
that allows users to configure trap receiver properties. These objects also let users
review the history of traps generated by the ICIM2 or ICIM2-XD.
The prismaIItrap object identifier (OID) is 1.3.6.1.4.1.1429.1.6.2.2.13.200. This is the
dot version of the full path that expands to:
iso(1).org(3).dod(6).internet(1).private(4).enterprise(1).scientificatlanta(1429).saTerr(1
).saTerrOptical(6).saTerrOpticalPrismaII(2).saPrismaIIrev2(2).saPrismaIIicim(13).Pris
maIItrap(200).

Trap Recv Table

Through setting the objects in the Trap Recv table, you enable traps to be sent to the
IP addresses of up to 10 different receivers or targets. The index into the table
represents one of 10 rows, designated 0 to 9.

To Receive Traps
Complete the following steps to receive traps.
1 Set p2TrapRecvEnable to enabled (2).
2 Set the IP address, in the format 172.18.2.24, of the remote entity to receive traps.
3 Set p2TrapRecvTelcoAlarm to enabled (2).

Note: All trap settings are documented for completeness. Information contained in
this trap is expanded upon in the Enhanced trap. Where practical, we recommend
using the Enhanced trap as it is more useful. Enabling this trap and the Enhanced
trap together will cause two traps to be sent for each triggering event. For more
information, see Prisma II Traps (on page 226).
Specific OIDs for the Trap Recv Table (1.3.6.1.4.1.1429.1.6.2.2.13.200.8) follow.

188 4021339 Rev B

 ICIM MIB

p2TrapRecvIndex
This object holds the index into a row of the p2TrapRecvEntry table. It has an integer
value from 0 to 9.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.200.8.1.1

p2TrapRecvEnable
The value in this object enables or disables the complete row. If disabled (1), even
though there may be a valid remote IP address saved in the row and traps may be
enabled (2) in the row, traps will not be sent to this IP address. To enable the row, set
p2TrapRecvEnable to enabled (2).
Access: read-write
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.200.8.1.2

p2TrapRecvAddr
To change this object from its initialized state, enter a valid IP address in the format
172.24.18.2, indicating the PC or workstation to which traps will be sent.
Access: read-write
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.200.8.1.3

p2TrapRecvIPChange
To receive a trap when the IP address of the ICIM2 or ICIM2-XD is changed, set
p2TrapRecvIpChange to enabled (2). Disabled (1) is the default.
Note: All trap settings are documented for completeness. Information contained in
this trap is expanded upon in the Enhanced trap. Where practical, we recommend
using the Enhanced trap as it is more useful. Enabling this trap and the Enhanced
trap together will cause two traps to be sent for each triggering event. For more
information, see Prisma II Traps (on page 226).
Access: read-write
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.200.8.1.4

p2TrapRecvModuleInsert
To receive a trap when a module is inserted into any chassis managed by this ICIM2
or ICIM2-XD, set p2TrapRecvModuleInsert to enabled (2). Disabled (1) is the default.
Note: All trap settings are documented for completeness. Information contained in
this trap is expanded upon in the Enhanced trap. Where practical, we recommend
using the Enhanced trap as it is more useful. Enabling this trap and the Enhanced
trap together will cause two traps to be sent for each triggering event. For more
information, see Prisma II Traps (on page 226).

4021339 Rev B 189

Chapter 9 SNMP Management

Access: read-write
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.200.8.1.5

p2TrapRecvModuleRemove
To receive a trap when a module is removed from any chassis managed by this
ICIM2 or ICIM2-XD, set p2TrapRecvModuleRemove to enabled (2). Disabled (1) is
the default.
Note: All trap settings are documented for completeness. Information contained in
this trap is expanded upon in the Enhanced trap. Where practical, we recommend
using the Enhanced trap as it is more useful. Enabling this trap and the Enhanced
trap together will cause two traps to be sent for each triggering event. For more
information, see Prisma II Traps (on page 226).
Access: read-write
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.200.8.1.6

p2TrapRecvMinorAlarm
Set this object to enable or disable sending traps to the SNMP manager when a
minor alarm in a module changes state. The user may choose to receive minor alarm
traps never (1), only when cleared (2), only when set (3), or "always," i.e., when set or
cleared (4).
This trap is edge triggered, meaning that it is sent if there is a change in a monitored
value that causes it to go into or out of a state of minor alarm. If p2TrapRecvEnable
is set to disabled (1), traps will not be sent.
Note: All trap settings are documented for completeness. Information contained in
this trap is expanded upon in the Enhanced trap. Where practical, we recommend
using the Enhanced trap as it is more useful. Enabling this trap and the Enhanced
trap together will cause two traps to be sent for each triggering event. For more
information, see Prisma II Traps (on page 226).
Access: read-write
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.200.8.1.7

p2TrapRecvMajorAlarm
Set this object to enable or disable sending traps to the SNMP manager when a major
alarm in a module changes state. The user may choose to receive minor alarm traps
never (1), only when cleared (2), only when set (3), or "always," i.e., when set or
cleared (4).
This trap is edge triggered, meaning that it is sent if there is a change in a monitored
value that causes it to go into or out of a state of major alarm. If p2TrapRecvEnable is
set to disabled (1), traps will not be sent.

190 4021339 Rev B

 ICIM MIB

Note: All trap settings are documented for completeness. Information contained in
this trap is expanded upon in the Enhanced trap. Where practical, we recommend
using the Enhanced trap as it is more useful. Enabling this trap and the Enhanced
trap together will cause two traps to be sent for each triggering event. For more
information, see Prisma II Traps (on page 226).
Access: read-write
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.200.8.1.8

p2TrapRecvDwnLdComplete
Set this object to enable (2) or disable (1) sending traps following a download to the
ICIM2 or ICIM2-XD or any application module. Disabled (1) is the default.
Note: All trap settings are documented for completeness. Information contained in
this trap is expanded upon in the Enhanced trap. Where practical, we recommend
using the Enhanced trap as it is more useful. Enabling this trap and the Enhanced
trap together will cause two traps to be sent for each triggering event. For more
information, see Prisma II Traps (on page 226).
Access: read-write
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.200.8.1.9

p2TrapRecvRebootCommand
Set this object to enable (2) or disable (1) sending traps following a reboot command
to the ICIM2 or ICIM2-XD or any application module. Disabled (1) is the default.
If the reboot command is broadcast to all modules and the ICIM2 or ICIM2-XD, only
one broadcast reboot trap will be generated.
Note: All trap settings are documented for completeness. Information contained in
this trap is expanded upon in the Enhanced trap. Where practical, we recommend
using the Enhanced trap as it is more useful. Enabling this trap and the Enhanced
trap together will cause two traps to be sent for each triggering event. For more
information, see Prisma II Traps (on page 226).
Access: read-write
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.200.8.1.10

p2TrapRecvSelfTest
Set this object to enable (2) or disable (1) sending traps following a module or ICIM2
or ICIM2-XD self-test failure. Disabled (1) is the default.
Specific self-test error code values are enumerated under p2icimSelfTest and
p2moduleSelfTest.

4021339 Rev B 191

Chapter 9 SNMP Management

Note: All trap settings are documented for completeness. Information contained in
this trap is expanded upon in the Enhanced trap. Where practical, we recommend
using the Enhanced trap as it is more useful. Enabling this trap and the Enhanced
trap together will cause two traps to be sent for each triggering event. For more
information, see Prisma II Traps (on page 226).
Access: read-write
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.200.8.1.11

p2TrapRecvTelcoAlarm
Set this object to enable (2) or disable (1) sending traps following an ICIM2, ICIM2-
XD, or application module alarm or event. Disabled (1) is the default, but enabled (2)
is the normal operating setting to receive traps.
The Enhanced traps generate the most information concerning the condition causing
the alarm or event. Bindings for the Enhanced traps are detailed in Enhanced Trap
Binding Information (on page 239).
Access: read-write
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.200.8.1.12
Note: All trap settings are documented for completeness. Information contained in
this trap is expanded upon in the Enhanced trap. Where practical, we recommend
using the Enhanced trap as it is more useful. Enabling this trap and the Enhanced
trap together will cause two traps to be sent for each triggering event. For more
information, see Prisma II Traps (on page 226).

Trap Logging Auxiliaries

p2TrapLastSequenceNumber
To observe the most current sequence number used by the Enhanced traps, perform
a get operation on this object. If no traps have been sent, the
p2TrapLastSequenceNumber is 0. Valid sequence numbers are 1 through
2,147,483,647. The sequence number resets to 0 at startup, at ICIM2 or ICIM2-XD
reboot, or if the p2TrapLogEntry table is cleared with the p2TrapLogClearKey. The
first trap sent after the sequence number resets will have the sequence number 1. If
incremented past 2,147,483,647, the sequence number wraps to 1 again.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.200.1

192 4021339 Rev B

 ICIM MIB

p2TrapLogClearKey
To clear the p2TrapLogEntry table, set p2TrapLogClearKey to clear (1). The next
Enhanced trap generated will start with sequence number 1, and be copied to the
Trap Log table to start populating it again. To continue to send traps without
restarting the sequencing, and continue to save them in the trap log table without
first clearing it, set p2TrapLogClearKey to keep (2). This OID will return Keep
Logging (2) when a get operation is performed.
Access: read-write
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.200.2

Trap Logging Table

The Trap Logging table serves as an aid to tracking by keeping a copy of up to 1,000
traps. When this table becomes full, it makes space for new trap records by deleting
the oldest trap records from the table.
To activate trap logging, you configure and enable at least one row in
p2TrapRecvTable. If p2TrapRecvTelcoAlarm is also enabled (2), traps are logged
automatically. The trap sequence number serves as the index into the Trap Logging
table.
A disruption in the network connectivity of the ICIM2 or ICIM2-XD does not mean
that a trap is lost. A copy of each Enhanced trap generated is saved in the Trap
Logging table, and can be retrieved using the trap sequence number.
Elements of the Trap Logging table line up with trap bindings. For more information
regarding the bindings, see Enhanced Trap Binding Information (on page 239).
The figure below shows how the Trap Logging table might appear when displayed
in a MIB browser.

The table below shows sample entries for each element of the Trap Logging table.
The elements themselves are described in this section.

4021339 Rev B 193

Chapter 9 SNMP Management

Trap Log Element Entry 10 Entry 14

p2TrapLogSequence 10 14
p2TrapLogSeverity minor (2) major (1)
p2TrapLogState alarm (1) alarm (1)
p2TrapLogLabel InRF InPwr
p2TrapLogOID p2almIndex.1.12.3 p2almIndex.2.1.1
p2TrapLogText Module=HDTx, Module=P2-HD-RXF,
Model=1032 Model= 2015
p2TrapLogChassisID 1 2
p2TrapLogSlotID 12 1
p2TrapLogCLLIcode N/A N/A
p2TrapLogCLEIcode N/A N/A
p2TrapLogTime 2007-11-27, 10:8:56.33 2007-11-27, 10:9:4.75
p2TrapLogDateTime Tue, 27 Nov 2007 10:08:56 EST Tue, 27 Nov 2007 10:09:04 EST
p2TrapLogValue -50 -21.2668
p2TrapLogUnit dB dBm
p2TrapLogDescr RF input exceeds minor InPwr exceeds major threshold
threshold

Specific OIDs for the Trap Log Table (1.3.6.1.4.1.1429.1.6.2.2.13.200.20) follow.

p2TrapLogSequence
This object holds a unique number assigned to each trap as it is generated. This
serves as an index into the Trap Logging table.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.200.20.1.1

p2TrapLogSeverity
This object holds the severity value, which assists in assigning priority to trap
generating conditions. Severity may be major (1), minor (2), or warning (3).
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.200.20.1.2

p2TrapLogState
This object holds the state value which, together with severity, quickly gives a view
into the current condition of the ICIM2, ICIM2-XD, or application module. State may
be alarm (1), clear (2), or event (3).

194 4021339 Rev B

 ICIM MIB

Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.200.20.1.3

p2TrapLogLabel
This object holds the trap log label. For an alarm or clear trap, the label must be the
same as the p2almLabel assigned to the condition which caused the trap; for
example, ChasTemp. For events, the value of this object indicates the type of event
that occurred and caused the trap to be sent, and may be one of the following:
  DownloadComplete (reserved for future use)
  RebootCommand
  SelfTest
  AuthentictnFailed
  AdminChange
  LogMemHalfFull
  LogMemoryFull
  LoginThreshold
  SNTP (reserved for future use)
  UpdateChassisID
  UserLockout
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.200.20.1.4

p2TrapLogOID
This object holds details regarding the condition that generated the trap. For an
alarm or clear trap, this may be the third index into the Module Alarm table. For the
download or reboot, this may be the p2icimStatusMessage. However, only the most
recent status message is retained by the ICIM2 or ICIM2-XD. If a message from
another event overwrites the status message, additional information may no longer
be available at the OID specified for the particular trap. If an event is logged, details
about the event may be saved in the event log.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.200.20.1.5

p2TrapLogText
This object holds a string that further describes the entity or condition responsible
for trap generation. This usually is a concatenation of the module name and model
number, although it may include the self-test failure code.

4021339 Rev B 195

Chapter 9 SNMP Management

Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.200.20.1.6

p2TrapLogChassisID
The value in this object identifies the chassis in which the ICIM2, ICIM2-XD, or
application module resides at the time of trap generation.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.200.20.1.7

p2TrapLogSlotID
This object holds the slot number in which the ICIM2, ICIM2-XD, or application
module resides at the time of trap generation.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.200.20.1.8

p2TrapLogCLLIcode
This object is reserved for future use.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.200.20.1.9

p2TrapLogCLEIcode
This object is reserved for future use.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.200.20.1.10

p2TrapLogTime
This object holds a date and time stamp indicating when the trap was generated.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.200.20.1.11

p2TrapLogDateTime
This object displays the full local time in the format: Tue, 27 Nov 2007 10:08:56 EST.
The local time zone must be entered in p2icimTimeZone or the default time zone,
EST, will always show.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.200.20.1.12

196 4021339 Rev B

 ICIM MIB

p2TrapLogValue
This object holds the most recent monitored value associated with the object in alarm
or clear state.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.200.20.1.13

p2TrapLogUnit
The value in this object indicates the unit of measure for the value in
p2TrapLogValue.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.200.20.1.14

p2TrapLogDescr
This object holds a verbose description of the alarm.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.200.20.1.15

4021339 Rev B 197

Chapter 9 SNMP Management

Module MIB
The module MIB consists of several tables indexed by the chassis and slot numbers
of the modules managed by the ICIM2 or ICIM2-XD. A third index into a table may
be necessary at times to create a unique instance, as further explained in Module
Alarm Table (on page 207).

Module MIB Tables

The module MIB includes the following tables:
  p2moduleTable
  p2moduleAlarmTable
  p2moduleCurrentAlarmTable
  p2moduleMonitorTable
  p2moduleControlTable
  p2InsertModuleTable
  p2RemoveModuleTable
The contents of each module MIB table are described below.

Table Name Table Contents

Module Table Basic manufacturing features and firmware download data for
each module.
Module Alarm Table Status of each module with regard to alarm thresholds and
nominal values. See Module Alarm Table (on page 207) for
further information.
Module Current Alarm Records the module elements in major or minor alarm at a
Table given time.
Module Monitor Table Contains monitored module values.
Module Control Table Contains module controls that may be adjusted.
Insert Module Table Chassis and slot number of each module inserted after the
ICIM2 or ICIM2-XD initially polls the chassis.
Remove Module Table Chassis number, slot number, and other information on each
module removed from a chassis controlled by this ICIM2 or
ICIM2-XD.

p2moduleNumber
This object shows the total number of active modules that have data in the Module
table.

198 4021339 Rev B

 Module MIB

Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.1

Module Table
The Module table contains information regarding each of the modules managed by
the ICIM2 or ICIM2-XD. It is indexed by the chassis and slot number where the
module currently resides.
The p2moduleTable OID is: 1.3.6.1.4.1.1429.1.6.2.2.13.300.2.
Rows in the table are accessed via p2moduleEntry.
The p2moduleEntry OID is: 1.3.6.1.4.1.1429.1.6.2.2.13.300.2.1.
The figure below shows how the Module table might appear when displayed in a
MIB browser.

The table below shows sample entries for each element of the Module table. The
elements themselves are described in this section.

Module Table First Module Entry Second Module Entry

p2chassisID 1 1
p2slotID 0 1
p2smcAddress 100 101
p2moduleType 5020 1020
p2moduleName XD-Chassis HDTx
p2manufactureData 3dBm TxTS 1310 nm
p2dateCode M07 H07
p2serialNumber ^ABCDEFG ^MMAAFEFJ
p2coreCodeRevision CF_CCB3 155
p2scriptRevision N/A 1

4021339 Rev B 199

Chapter 9 SNMP Management

Module Table First Module Entry Second Module Entry

p2timeOfService 744 1633
p2numOfMonitoredVars 14 7
p2numOfAnalogControls 0 1
p2numOfDigitalControls 2 5
p2numOfControls 2 6
p2numOfAlarms 12 7
p2NextImage currentActive (1) not-applicable (3)
p2activeCodeRevision 1.01.04 N/A
p2inactiveCodeRevision 91.01.04 N/A
p2bootCodeRevision 0.00.03 N/A
p2moduleCLLIcode N/A N/A
p2moduleCLEIcode N/A N/A
p2moduleDownloadable yes (1) no (0)
p2moduleSelfTest Passed N/A
p2FantrayPSsplit no (2) not-applicable (3)

p2chassisID
This object identifies the chassis number in which the module is installed. The value
in this object provides one index into the Module table.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.2.1.1

p2slotID
This object identifies the slot number in which the module is currently installed. The
value in this object provides one index into the Module table.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.2.1.2

p2smcAddress
This object reports the module status monitoring and control (SMC) address, which
is the chassis number times 100, plus the slot number of this module. For example, a
module in chassis 1 slot 1 would have a p2smcAddress of 101.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.2.1.3

200 4021339 Rev B

 Module MIB

p2moduleType
This object holds a number assigned during the manufacturing process to uniquely
identify this type of module. This is also referred to as the devtype or TNCS type
number.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.2.1.4

p2moduleName
This object holds the name assigned to modules of this particular type.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.2.1.5

p2manufactureData
This object holds a string of manufacturing data, which can be up to 30 characters in
length.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.2.1.6

p2dateCode
This object holds the date code, which is a string consisting of three characters. A
letter specifies the month, and a two-digit number specifies the year this module was
manufactured and tested. The following letters are used to specify the month:

Letter Month
A January
B February
C March
D April
E May
F June
G July
H August
J September
K October
L November
M December

Example: M07 = December 2007

4021339 Rev B 201

Chapter 9 SNMP Management

Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.2.1.7

p2serialNumber
The value in this object designates the module serial number.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.2.1.8

p2coreCodeRevision
The value in this object is CF_CCB3 for downloadable CCBs designed to interface
with the ICIM2 or ICIM2-XD.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.2.1.9

p2scriptRevision
This object is deprecated in the downloadable modules, which do not use scripts. It
is retained for compatibility with previous versions of the modules, which still use
scripts.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.2.1.10

p2timeOfService
This object reports the number of hours this module has been in service. The value is
updated every hour for the first 120 hours, and every 12 hours up to 120,000.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.2.1.11

p2numOfMonitoredVars
The value in this object represents the total number of monitored variables for this
module.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.2.1.12

p2numOfAnalogControls
The value in this object represents the total number of analog variables for this
module.
Access: read-only

202 4021339 Rev B

 Module MIB

OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.2.1.13

p2numOfDigitalControls
The value in this object represents the total number of digital and state controls for
this module.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.2.1.14

p2numOfControls
The value in this object represents the total number of control variables for this
module.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.2.1.15

p2numOfAlarms
The value in this object represents the total number of alarm variables for this
module.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.2.1.16

p2NextImage
The value in this object represents the firmware image to be active following the
module reboot. Options are currentActive (1), currentInactive (2), or not applicable
(3).
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.2.1.17

p2activeCodeRevision
The value in this object represents the version of the firmware active for this module.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.2.1.18

p2inactiveCodeRevision
This object is reserved for future use.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.2.1.19

4021339 Rev B 203

Chapter 9 SNMP Management

p2bootCodeRevision
The value in this object represents the current boot image revision for the module.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.2.1.20

p2moduleCLLIcode
This object is reserved for future use.
Access: read-write
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.2.1.21

p2moduleCLEIcode
This object is reserved for future use.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.2.1.22

p2moduleDownloadable
The value in this object indicates whether the module supports firmware downloads.
The value may be either yes (1) or no (2).
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.2.1.23

p2moduleSelfTest
This object displays the results of the basic functional self-test that the module
performs at boot-up or when inserted into a chassis slot. If the module passed the
self-test, performing a get on this object returns the message “Self-Test Passed.” If
the module encounters one or more problems, the message "Self-Test failed - Error
Code” is returned followed by a decimal representation of the hexadecimal code of
the failure(s).

Self-Test Error Codes: Prisma II Platform

The following error codes are used for the Prisma II Fan Tray, Pre-Amplifier, Post-
Amplifier, and Optical Switch modules.

Modules Test Failed Hexadecimal Decimal

Code Value
Flash bank 1 CRC 0x2000001 33554433
Flash bank 2 CRC 0x2000002 33554434
ColdFire RAM 0x2000004 33554436

204 4021339 Rev B

 Module MIB

Flash bank 0 CRC 0x2000008 33554440

EEPROM read 0x2000010 33554448
EEPROM write 0x2000020 33554464
EEPROM write-protect 0x2000040 33554496
SPI BUS 0x2000080 33554560
Local Craft Interface port 0x2000100 33554688
ICIM 485 port 0x2000200 33554944
Local Debug port 0x2000400 33555456
CAN BUS 0x2000800 33556480
Analog to Digital 0x2001000 33558528
Digital to Analog 0x2002000 33562624
IO 0x2004000 33570816
Power Supply 0x2008000 33587200

Self-Test Error Codes: Prisma II XD Platform

The following error codes are used for the Prisma II XD client control board, fan
assembly, AC-to-DC bulk power supplies, DC-to-DC converters, ICIM2 or ICIM2-
XD, and installed application modules.

Modules Test Failed Hexadecimal Decimal

Code Value
Flash bank 1 CRC 0x2000001 33554433
Flash bank 2 CRC 0x2000002 33554434
ColdFire RAM 0x2000004 33554436
Flash bank 0 CRC 0x2000008 33554440
EEPROM read 0x2000010 33554448
EEPROM write 0x2000020 33554464
EEPROM write-protect 0x2000040 33554496
SPI BUS 0x2000080 33554560
Local Craft Interface port 0x2000100 33554688
ICIM2 485 port 0x2000200 33554944
Local Debug port 0x2000400 33555456
CAN BUS 0x2000800 33556480
Analog to Digital 0x2001000 33558528
Digital to Analog 0x2002000 33562624
IO 0x2004000 33570816

4021339 Rev B 205

Chapter 9 SNMP Management

Power Supply 0x2008000 33587200

If self-test discovers more than one problem, the error code returned is the sum of the
individual error codes. For example:
  If the power supply on a pre-amplifier failed, the error code displayed would be
33587200 in decimal (2008000 hex).
  If the power supply and the write to the EEPROM failed on a post-amplifier
module self-test, the error code would be ((32768 + 32) + 33554432 =) 33587232
decimal or ((8000 + 20) + 2000000 =) 2008020 hex.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.2.1.24

p2FantrayPSsplit
Note: This object pertains to the Prisma II Platform chassis only.
The value in this object tells the NMS how to interpret alarms that originate from a
fan tray, power supply, or application module. This information is important in
establishing the actual origin of fan tray and power supply alarms for
troubleshooting purposes.
The fan tray manages alarms for the fan tray as well as for the power supply
modules in slot 1 and slot 3. The ICIM2 with Release 1.00 firmware associates fan
tray, power supply 1, and power supply 3 alarms with a single logical chassis slot
location (slot 3). The NMS must then remap the alarms to physical chassis slot
locations in order to indicate the actual origin of the alarm.
In a chassis with an ICIM2 at Release 2.00 or later and a fan tray at Release 1.01 or
later firmware, these alarms are reported as originating from their respective
physical chassis slot locations. This makes it unnecessary for the NMS to remap fan
tray and power supply alarms to chassis slot locations.
However, due to the potential mix of 1.00 and 1.01 fan trays in the field, the NMS
must be told when to remap alarms to physical slot locations for a particular chassis.
The p2FantrayPSsplit element performs this function. It has three possible values:

Value Meaning
Yes (1) This module is a newer fan tray (devtype 5012) or power supply
(devtype 5013) with split data. Therefore, the data is only for the
particular module (fan tray or power supply) you are viewing. The
NMS does not need to perform slot remapping.
No (2) This module is an older fan tray-power supply combination
(devtype 5010) with unsplit data. Therefore, the data needs to be
separated into fan tray, power supply 1, and power supply 3. The
NMS needs to perform slot remapping.
Not Applicable (3) This module is neither a power supply nor a fan tray module.

206 4021339 Rev B

 Module MIB

The default value of 3 (not applicable) tells the NMS that the module in alarm is
neither the fan tray nor a power supply, making the issue moot. A value of 1 (Yes)
means that the alarms are split by module, so alarm remapping is not needed. A
value of 2 (No) means that the alarms are not split, so remapping is required.
Access: read-write
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.2.1.25

Module Alarm Table

Currently, the alarms in the Module Alarm table and the corresponding traps
generated by the alarm (or clear) condition are reported as Major or Minor with
respect to severity level. See Alarm Severity (on page 213) for details concerning the
alarm severity mappings.
The p2moduleAlarmTable OID is: 1.3.6.1.4.1.1429.1.6.2.2.13.300.5.
Note:
  Alarm thresholds can only be adjusted for type 1, 2 and 7 alarms. (See the
p2almType below.) The type of alarm is shown in the p2almType field. The
p2almLimitAdjust field will be set to "enabled" if the limits can be adjusted, or to
"disabled" if they cannot be adjusted.
  The ICIM2 or ICIM2-XD shows the alarm thresholds for all alarm types as read-
writable, whether they can be adjusted or not. However, an error will result if the
user attempts to change an alarm threshold with non-adjustable limits.
The figure below shows how the Module Alarm table might appear when displayed
in a MIB browser.

The table below shows sample entries for each element of the Module Alarm table.
The elements themselves are described in this section.

4021339 Rev B 207

Chapter 9 SNMP Management

p2module Alarm Entry 1 Entry 2 Entry 3 Entry 4 Entry 5

Table
Instance 1.0.1 1.0.2 1.0.3 1.0.4 1.0.5
index * 1 2 3 4 5
label Fan1_Ok Fan 2_Ok Fan 3_Ok Chastemp ConvAIn
Value 0 (ok) 0 (ok) 0 (ok) 2 (ok) 2 (ok)
Type 6 6 6 2 5
Nominal 1 1 1 25 1
Hysteresis N/A N/A N/A 1 N/A
Major Low N/A N/A N/A -40 N/A
Minor Low N/A N/A N/A -35 N/A
Minor High N/A N/A N/A 60 N/A
Major High N/A N/A N/A 65 N/A
Limit Adjust disabled (2) disabled (2) disabled (2) enabled (1) disabled (2)
Limit Range Lo N/A N/A N/A -32768 N/A
Limit Range Hi N/A N/A N/A 32767 N/A
* The index value for the alarm is actually the third digit of the instance value. The alarm
label will always have the same index value for that module. The index value is not a
running index for the entire Module Alarm table.

p2almIndex
This object holds one of the indices into the alarm table. Indices include chassis and
slot, as well as p2almIndex per alarm type for the module, which form the unique
instance into the Module Alarm table.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.5.1.1

p2almLabel
This object holds a string of eight characters or less that describes an alarm
characteristic of a module type.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.5.1.2

208 4021339 Rev B

 Module MIB

p2almValue
This object holds the alarm value, which may be a Boolean or Non-Boolean value as
appropriate to the alarm type. The table below shows how the meanings of different
alarm values vary depending on their class or enumeration (Non-Boolean vs.
Boolean).

Class/Enumeration 0 1 2 3 4
Non-Boolean (p2almType 1, 2, 3, 4, 7, 8 - see Major Minor OK Minor Major
table under palmType) low low high high
Boolean (p2almType 5 or 6) OK Fault na na na

Important: Certain alarm values can have very different meanings depending on the
type of alarm. For example, for Boolean alarm types (p2almType = 5 or 6),
p2almValue = 0 indicates that there is no fault (OK). However, for Non-Boolean
alarm types (p2almType = 1, 2, 3, 4, 7, or 8), p2almValue = 0 indicates a major low
alarm. See also p2almType below for more on alarm types.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.5.1.3

p2almType
This object holds the alarm type. The alarm type is a number from 1 to 8 that
identifies three key characteristics of the alarm:
  Class - whether the alarm value is Boolean or Non-Boolean. This affects the way
that the alarm values are interpreted.
  Impact - whether the alarm thresholds are fixed by the module or can be
changed by the user. A module alarm is controlled by the module. If a monitored
value violates an alarm threshold set by a module, the module may shut down.
User alarm thresholds may be configured by the user. However, these alarms
will not cause modules to shut down.
  Threshold Implementation - whether the threshold for the alarm is an absolute
value, or is relative to one or more other control parameters.
The table below identifies the class, impact, and threshold implementation for each
possible value of p2almType. Alarm types with user-adjustable thresholds are
indicated with an asterisk (*) in the table and paragraphs below.

p2almType Class Impact Threshold

Implementation
1* Non-Boolean User Relative
2* Non-Boolean User Absolute
3 Non-Boolean Module Relative
4 Non-Boolean Module Absolute

4021339 Rev B 209

Chapter 9 SNMP Management

p2almType Class Impact Threshold

Implementation
5 Boolean User na
6 Boolean Module na
7* Non-Boolean User Absolute
8 Non-Boolean Module Absolute
* Only these alarm thresholds may be changed by a user.

More on Alarm Types

A Major alarm for module alarm types 3, 4, and 6 below may shut down the module
or an important feature of it, such as the laser, if a major threshold is violated. User
alarms of type 1, 2, 5, and 7 will not shut down the module if a Major threshold (low
or high) is exceeded.
1 The relative user alarm. The alarm thresholds are interpreted as a positive or
negative value relative to the nominal value of the alarmed variable. The alarm
thresholds can be adjusted by the operator, but this will not shut down the
module.
2 The absolute user alarm. The alarm thresholds are interpreted as absolute values
of the alarmed variable. The alarm thresholds can be adjusted by the operator,
but this will not shut down the module.
3 The relative module alarm. The interpretation of thresholds is like type 1, but a
Major alarm will set the module in the safe state. The alarm thresholds are not
user-adjustable.
4 The absolute module alarm. The interpretation of thresholds is like type 2, but a
Major alarm will set the module in the safe state. The alarm thresholds are not
user-adjustable.
5 User Boolean alarm. The state 0 means no alarm (OK). The nominal set to 1 (see
p2almNominal below) means that input signal of 1 causes an alarm. If nominal
is 0, input value of 0 causes alarm. This alarm does not set the unit to the safe
state. The alarm thresholds are not user-adjustable.
6 Module Boolean alarm. The state 0 means no alarm (OK). The nominal set to 1
(see p2almNominal below) means that input signal of 1 causes an alarm. If
nominal is 0, input value of 0 causes alarm. This alarm will set the unit to the safe
state. The alarm thresholds are not user-adjustable.
7 The user alarm with complete inhibit. Same as type 2 except that inhibiting this
alarm will always put it in the no alarm state. It will not set anything to the safe
state, set the alarm LED or relay or pull the attention line low. The alarm
thresholds can be adjusted by the operator, but this will not shut down the
module.

210 4021339 Rev B

 Module MIB

8 The Module alarm with complete inhibit. Same as type 7 except that the limits
are not user-adjustable. Unlike other module alarms it will not set anything to
the safe set when an alarm is triggered. The alarm thresholds are not user-
adjustable.
Important: The alarm type and alarm value are inseparably linked, in that the value
may only be understood with respect to the type of alarm. (See also p2almValue
above.)
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.5.1.4

p2almNominal
This object holds the alarm nominal value. To view the current value for a particular
module and element, see the Module Monitor table.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.5.1.5

p2almHysteresis
This object defines the hysteresis value for the alarm. The hysteresis value
determines how far from the alarm threshold a parameter must change before an
alarm condition will clear. The purpose of hysteresis is to prevent the rapid setting
and clearing of alarms that otherwise would occur when a parameter makes small
fluctuations about the alarm threshold value.
For example, assume that the Minor High limit for chassis temperature is set to 45°C,
and the hysteresis value for this alarm parameter is 1°C. When the chassis
temperature rises above 45°C, the Minor High alarm occurs. In order for the alarm to
clear, the temperature must fall below 44°C, which is the alarm threshold value of 45
minus the hysteresis value of 1.
Likewise, if the chassis temperature had a Minor Low alarm threshold of -20°C and a
hysteresis value of 1°C, a Minor Low alarm would occur if the temperature fell
below -20°C, but would not clear until the temperature rose above -19°C.
See Note at the end of this section for additional information.
Access: read-write
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.5.1.8

p2almMajorLowLimit
This object holds the Major Low alarm threshold value. See Note at the end of this
section for additional information.
Access: read-write
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.5.1.9

4021339 Rev B 211

Chapter 9 SNMP Management

p2almMinorLowLimit
This object holds the Minor Low alarm threshold value. See Note at the end of this
section for additional information.
Access: read-write
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.5.1.10

p2almMinorHighLimit
This object holds the Minor High alarm threshold value. See Note at the end of this
section for additional information.
Access: read-write
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.5.1.11

p2almMajorHighLimit
This object holds the Major High alarm threshold value. See Note at the end of this
section for additional information.
Access: read-write
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.5.1.12

p2almLimitAdjust
The value in this object indicates whether an alarm has adjustable threshold values.
It will be set to enabled (1) if adjustable, disabled (2) if non-adjustable. See Note at
the end of this section for additional information.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.5.1.13

p2almLimitRangeLo
The value in this object is the lower limit for an adjustable alarm threshold.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.5.1.14

p2almLimitRangeHi
The value in this object is the upper limit for an adjustable alarm threshold.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.5.1.15
Note: Alarm thresholds can only be adjusted for type 1, 2 and 7 alarms. The type of
alarm is shown in the p2almType field. The p2almLimitAdjust field will be set to
"enabled" if the limits can be adjusted, or to "disabled" if they cannot be adjusted.

212 4021339 Rev B

 Module MIB

The ICIM2 or ICIM2-XD treats all modules the same in that the alarm thresholds will
be shown as read-writable for all alarm types, whether they can be adjusted or not.
An error will result if the user attempts to change an alarm threshold with non-
adjustable limits.

Alarm Severity
All Prisma II XD Chassis alarms presently report to Major or Minor severity levels.
Note: For additional information on alarms, alarm types and alarm values, see
Module Alarm Table (on page 207).

XD Chassis (Fan Assembly and Power Supplies)

Alarm Type Severity Level

Fan 1_Ok Major
Fan 2_Ok Major
Fan 3_Ok Major
ChasTemp Major/Minor per threshold settings
ConvAIn Major
ConvA+24 Major/Minor per threshold settings
ConvA+5 Major/Minor per threshold settings
ConvA-5 Major/Minor per threshold settings
ConvBIn Major
ConvB+24 Major/Minor per threshold settings
ConvB+5 Major/Minor per threshold settings
ConvB-5 Major/Minor per threshold settings

Current Alarm Table

The Current Alarm table displays the module elements currently in alarm. This table
is highly dynamic, and updates with each poll of a module, if needed.
When a module element first goes into alarm, an entry is made in the Current Alarm
table and the date and time are recorded. If the alarm changes from Major to Minor
or vice versa, the change is acknowledged and the time stamp is adjusted.
If an alarm clears, the entry is removed from the Current Alarm table. If a module is
removed from the ICIM2 or ICIM2-XD domain, all of its corresponding alarms are
removed from the table.
The indices are chassis, slot, and index, the same as the index into the
p2moduleAlarm table associated with this alarmed item.

4021339 Rev B 213

Chapter 9 SNMP Management

p2moduleCurrentAlarmTable OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.8

p2moduleCurrentAlarmEntry OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.8.1
The figure below shows how the Current Alarm table might appear when displayed
in a MIB browser.

The table below shows sample entries for each element of the Current Alarm table.
The elements themselves are described in this section.
Instance p2curAlm p2curAlm p2curAlm p2curAlmDescr p2curAlmTime
Index * Severity Label
1.2.3 3 minor (2) InRF Module=HDTx, Wed, 02 Nov 2005 11:55:39 EST
Model=1032
1.3.3 3 minor (2) InRF Module=HDTx, Wed, 02 Nov 2005 11:55:40 EST
Model=1032
1.4.3 3 minor (2) InRF Module=HDTx, Wed, 02 Nov 2005 11:55:42 EST
Model=1032
1.5.3 3 major (1) InRF Module=HDTx, Wed, 02 Nov 2005 11:55:43 EST
Model=1032
1.7.3 3 minor (2) InRF Module=HDTx, Wed, 02 Nov 2005 11:55:46 EST
Model=1032
1.8.3 3 minor (2) InRF Module=HDTx, Wed, 02 Nov 2005 11:55:47 EST
Model=1032
1.9.3 3 minor (2) InRF Module=HDTx, Wed, 02 Nov 2005 11:55:48 EST
Model=1032
1.10.3 3 minor (2) InRF Module=HDTx, Wed, 02 Nov 2005 11:55:50 EST
Model=1032
1.11.3 3 minor (2) InRF Module=HDTx, Wed, 02 Nov 2005 11:55:51 EST
Model=1032
1.12.3 3 minor (2) InRF Module=HDTx, Wed, 02 Nov 2005 11:55:52 EST
Model=1032

214 4021339 Rev B

 Module MIB

Instance p2curAlm p2curAlm p2curAlm p2curAlmDescr p2curAlmTime

Index * Severity Label
1.13.3 3 minor (2) InRF Module=HDTx, Wed, 02 Nov 2005 11:55:53 EST
Model=1032
1.14.3 3 minor (2) InRF Module=HDTx, Wed, 02 Nov 2005 11:55:55 EST
Model=1032
1.16.3 3 minor (2) InRF Module=HDTx, Wed, 02 Nov 2005 11:56:57 EST
Model=1032
2.1.1 1 minor (2) InPwr Module=P2-HD-RXF, Wed, 02 Nov 2005 11:56:01 EST
Model=2015
* The index value for the alarm is actually the third digit of the instance value. The alarm
label will always have the same index value for that module. The index value is not a
running index for the entire Current Alarm table.

p2curAlmIndex
The value in this object is the index into the p2moduleAlarm table for this object in
alarm. It is one of three indices into the Current Alarm table, along with p2chassisID
and p2slotID.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.8.1.1

p2curAlmSeverity
The value in this object represents the current level of severity for the alarm shows
here. The alarm may be Major (1) or Minor (2).
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.8.1.2

p2curAlmLabel
The value in this object represents the label assigned to the alarm, which
corresponds to the p2almLabel.
Example: Fan1_Ok
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.8.1.3

p2curAlmDescr
This object holds the alarm description, which is a concatenation of the module
name and the model number in text form. It is exactly the same as p2TrapLogText,
sent by the Enhanced traps and logged in the Trap Logging table.
Example: Module=HDTx, Model=1032
Access: read-only

4021339 Rev B 215

Chapter 9 SNMP Management

OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.8.1.4

p2curAlmTime
This object shows the time that the alarm was first recorded in the Current Alarm
table, or the time that the severity level last changed from Major to Minor or vice
versa.
Format Example: Wed, 02 Nov 2005 11:56:50 EST
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.8.1.5

Module Monitor Table

The Module Monitor table shows the actual values of module elements. Values may
only be updated via a module in response to requests from the ICIM2 or ICIM2-XD.
As with the Module Control table and the Module Alarm table, the Module Monitor
table is indexed by the chassis and slot number of a particular module. The third
index into the table is represented by the p2monitor Index value.
The OID of p2moduleMonitorTable is: 1.3.6.1.4.1.1429.1.6.2.2.13.300.7.
Rows may be accessed via p2moduleMonitorEntry OID:
1.3.6.1.4.1.1429.1.6.2.2.13.300.7.1.
The figure below shows how the Current Monitor table might appear when
displayed in a MIB browser.

The table below shows sample entries for each element of the Current Alarm table.
The elements themselves are described in this section.

216 4021339 Rev B

 Module MIB

Instance Index * Label Value Unit Type StateName

1.0.1 1 Conv+24 24.1499 V F N/A
1.0.2 2 ConvA+5 5.28269 V F N/A
1.0.3 3 ConvA-5 -5.26423 V F N/A
1.0.4 4 ConvB+24 24.0095 V F N/A
1.0.5 5 ConvB+5 5.27484 V F N/A
1.0.6 6 ConvB-5 -5.2905 N/A F N/A
1.0.7 7 PSA_Inst 1 N/A S (0) No, (1) Yes
1.0.8 8 PSB_Inst 1 N/A S (0) No, (1) Yes
1.0.9 9 ConvAIns 1 N/A S (0) No, (1) Yes
1.0.10 10 ConvBIns 1 N/A S (0) No, (1) Yes
1.0.11 11 Chas+24V 24.1177 V F N/A
1.0.12 12 Chas+5V 5.0277 V F N/A
1.0.13 13 Chas-5V -4.93157 V F N/A
1.0.14 14 ChasTemp 26.75 degC F N/A
1.1.1 1 OutPwr 2.97 dBm F N/A
1.1.2 2 LasBias 72 mA F N/A
* The index value for the alarm is actually the third digit of the instance value. The monitor
label will always have the same index value for that module. The index value is not a
running index for the entire Module Monitor table.

p2monitorIndex
The value in this object is the third index into the Module Monitor table.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.7.1.1

p2monitorLabel
This object holds a short description, eight characters or less, of the monitored
variable found in the string associated with p2monitorLabel.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.7.1.2

p2monitorValue
This object holds the monitor value, which is the actual value given by a module for
the monitored variable.
Access: read-only

4021339 Rev B 217

Chapter 9 SNMP Management

OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.7.1.3

p2monitorUnit
This object indicates the units assigned to the value appearing in p2monitorValue.
The table below summarizes the common units used by monitored values and
controls.

Unit Meaning
A amperes
dB decibels (10log10)
dBm decibels relative to 1 mW (0.0 dBm is 1.0 mW)
degC degrees in Centigrade
hrs hours
Inst installed
mA milliamperes
% percentage
sec seconds

Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.7.1.4

p2monitorType
This object indicates the monitor data type, represented with one of the following
letters:

Unit Meaning
F floating point value
D digital, integer value
B Boolean, 0 or 1
L long, a floating point value converted to 8 ASCII
Hex digits
S state with enumerated list of state names (up to 8
characters each)

Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.7.1.5

p2monitorStateNames
If the element is a state variable, this object lists all the state names for the element.
Access: read-only

218 4021339 Rev B

 Module MIB

OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.7.1.6

Module Control Table

The Module Control table contains control information for every module in the
ICIM2 or ICIM2-XD domain that has control variables.
Like the Alarm table and Monitor table, the Control table has three indices:
  Chassis number
  Slot number
  Individual index, which varies per module by control type
Collectively, these indices make up the instance into the table.
p2ModuleControlTable OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.6
p2ModuleControlEntry OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.6.1
The figure below shows how the Module Control table might appear when
displayed in a MIB browser.

The table below shows sample entries for each element of the Module Control table.
The elements themselves are described in this section.
Instance Index * Label Value Unit Type Range Range Range StateNames
Low 1High Step
1.0.1 1 AlmMuteA 0 N/A S 0 1 1 (0) Off, (1) On
1.0.2 2 AlmMuteB 0 N/A S 0 1 1 (0) Off, (1) On
1.1.1 1 Enable 1 N/A B 0 1 1 N/A
1.1.2 2 CwMode 0 N/A B 0 1 1 N/A
1.1.3 3 LoRFInh 0 N/A B 0 1 1 N/A
1.1.4 4 Master 1 N/A S 0 1 1 (0) Slave, (1) Master

4021339 Rev B 219

Chapter 9 SNMP Management

Instance Index * Label Value Unit Type Range Range Range StateNames
Low 1High Step
1.1.5 5 RFDrive 0 dB F -1.5 1.5 0.5 N/A
1.1.6 6 AGC 0 N/A B 0 1 1 N/A
1.2.1 1 Enable 1 N/A B 0 1 1 N/A
1.2.2 2 CwMode 0 N/A B 0 1 1 N/A
* The index value for the alarm is actually the third digit of the instance value. The alarm
label will always have the same index value for that module. The index value is not a
running index for the entire Module Control table.

p2cntrlIndex
The value in this object is one index into the Module Control table is the
p2cntrlIndex. It is the third index; chassis and slot are the first and second indices to
this table.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.6.1.1

p2cntrlLabel
This object holds a short description of the control, represented as a string of not
more than eight characters. The description varies by module and its controls.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.6.1.2

p2cntrlValue
The value in this object may be changed by the user to control an aspect of the
module.
Access: read-write
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.6.1.3

p2cntrlUnit
This object indicates the units assigned to the values appearing in p2cntrlValue. The
table below summarizes the common units used by monitored values and controls.

Unit Meaning
A amperes
dB decibels (10log10)
dBm decibels relative to 1 mW (0.0 dBm is 1.0 mW)
degC degrees in Centigrade
hrs hours

220 4021339 Rev B

 Module MIB

Unit Meaning
Inst installed
mA milliamperes
% percentage
sec seconds

Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.6.1.4

p2cntrlType
The value in this object represents the data type of the control variable:

Unit Meaning
F floating point value
D digital, integer value
B Boolean, 0 or 1
S state with enumerated list of state names (up to
8 characters each)

Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.6.1.5

p2cntrlRangeLo
The value in this object is the lower limit for the control.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.6.1.6

p2cntrlRangeHi
The value in this object is the upper limit for the control.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.6.1.7

p2cntrlRangeStep
The value in this object is the range step (smallest allowable increment) for the
control.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.6.1.8

4021339 Rev B 221

Chapter 9 SNMP Management

p2cntrlStateNames
If the control is a state variable, this object will list the state names for the control.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.6.1.9

Insert Module Table

If a module is inserted into the chassis following the initial polling of the ICIM2 or
ICIM2-XD, the module chassis and slot appear in the Insert Module table. The table
is indexed sequentially by occurrence.
p2InsertModuleTable OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.3
p2InsertModuleEntry OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.3.1

p2InsertModuleIndex
The value in this object is the index into the Insert Module table, which is sequential
with respect to time.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.3.1.1

p2InsertModuleChassisID
The value in this object represents the number of the chassis in which the module is
installed.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.3.1.2

p2InsertModuleSlotID
The value in this object represents the number of the slot in which the module is
installed.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.3.1.3

Remove Module Table

If a module is removed from a slot, some data concerning the module appears in the
Remove Module table. Information captured in this table allows managers to
determine if the removed module was replaced by a module of the same type. This
table is indexed sequentially based on occurrence.

222 4021339 Rev B

 Module MIB

As with other tables for the module, the rows in this table may be accessed via the
p2RemoveModuleEntry.
p2RemoveModuleTable OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.4
p2IRemoveModuleEntry OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.4.1

p2RemoveModuleIndex
The value in this object represents the index into the Remove Module table, which is
sequential with respect to time.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.4.1.1

p2RemoveModuleChassisID
The value in this object represents the number of the chassis in which the module
had been installed.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.4.1.2

p2RemoveModuleSlotID
The value in this object represents the number of the slot in which the module had
been installed.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.4.1.3

p2RemoveModuleName
The value in this object represents the name assigned to this module type during the
manufacturing process.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.4.1.4

p2RemoveModuleType
The value in this object represents the number assigned during the manufacturing
process to uniquely identify this type of module. This is also referred to as the
devtype or TNCS type number.
Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.4.1.5

p2RemoveModuleSerialNum
The value in this object designates the serial number of the removed module.

4021339 Rev B 223

Chapter 9 SNMP Management

Access: read-only
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.300.4.1.6

224 4021339 Rev B

 Remote Reboot of ICIM and Modules

Remote Reboot of ICIM and Modules

The ICIM2, ICIM2-XD, and application modules can be rebooted remotely using a
series of SNMP commands. The modules may be rebooted using a hard reboot
(service interrupting) or a soft reboot (non-service interrupting). The ICIM2 or
ICIM2-XD always performs a hard reboot (non-service interrupting) in response to
either a soft reboot or hard reboot command.

To Reboot the ICIM via SNMP

Complete the following steps to reboot the ICIM2 or ICIM2-XD via SNMP.
1 Set p2icimDownLdTgt to "ccss," where cc is the chassis number and ss is the slot
number.
2 Set p2icimDownLdCmd to "9" (reboot enable).
3 Set p2icimDownLdCmd to "7" or "8" (7 for soft reboot, 8 for hard reboot).
Note:
  For the ICIM2 or ICIM2-XD, the soft reboot and the hard reboot is the same.
  Because a reboot clears its module database, the ICIM2 or ICIM2-XD must
rediscover its domain before updating module status. Discovery times may be as
long as five minutes, depending on the system size and configuration.

To Reboot a Module via SNMP

Complete the following steps to reboot an application module via SNMP.
1 Set p2icimDownLdTgt to "ccss," where cc is the chassis number and ss is the slot
number.
2 Set p2icimDownLdCmd to "9" (reboot enable).
3 Set p2icimDownLdCmd to "7" or "8" (7 for soft reboot, 8 for hard reboot).
Note: A module soft reboot will not interrupt service to the end customer, but a hard
reboot may cause a brief disruption of service.

4021339 Rev B 225

Chapter 9 SNMP Management

Prisma II Traps
This section describes trap destination configuration and provides details on trap
types, conditions causing traps, and trap logging.

About Traps
The Prisma II system can be configured to provide various alarm and warning
conditions, called traps, to an element management system or system monitor
application. Up to eight different traps can be enabled independently to provide
information on events occurring in a system:
  IP Change
  Module Insertion
  Module Removal
  Alarm Event
  Download Complete
  Self-Test
  Reboot
  Enhanced Alarm
These traps can be sent to up to ten different IP addresses, or "users." Trap filtering
can be configured independently for each user.
Each trap is accompanied by one or more bindings, which are parameters
representing the physical or logical objects associated with the trap.
The following table briefly describes each of the traps listed above and identifies its
associated bindings.

Trap Description Binding

IP Change Trap An informational event indicating when the 1. Previous IP address
ICIM2 or ICIM2-XD IP address has been
changed.
Module Insertion Trap An informational event indicating that a 1. Chassis ID
module has been inserted into a chassis. 2. Slot ID
Module Removal Trap An informational event indicating that a 1. Chassis ID
module has been removed from a chassis. 2. Slot ID

226 4021339 Rev B

 Prisma II Traps

Trap Description Binding

Alarm Event Trap An informational event indicating that an alarm 1. Chassis ID
has changed state on a module. 2. Slot ID
3. Alarm Table Index
4. Alarm Label
(Description)
Download Complete An informational event indicating that new 1. Chassis ID
Trap application software has been downloaded to a 2. Slot ID
module.
Reboot Command An informational event indicating that a 1. Chassis ID
Trap module has been commanded to reboot (hard 2. Slot ID
or soft).
Self-Test Trap An alarm indicating that a module has failed its 1. Chassis ID
power-on self test. 2. Slot ID
Enhanced Alarm Trap An event indicating that an alarm has changed 1. Trap Sequence
state or an event has occurred with a module. Number
This trap includes additional bindings to 2. Severity
indicate CLLI and CLEI codes for
telecommunications equipment. 3. State
4. Description
5. OID
6. Module Name and
type
7. Chassis ID
8. Slot ID
9. CLLI code
10. CLEI code
11. TimeStamp
12. Date Time Zone
13. Value
14. Unit
15. Description

Note: All trap types (module insertion, alarm events, etc.) are reported through the
Enhanced Alarm trap. By default, only the Enhanced Alarm traps are enabled.

Standard and Enhanced Traps

The traps listed above are known as the Standard traps, also called MSO traps
because of their use by multiple service operators (MSOs). An alternative to the
Standard traps is the Enhanced trap, also called the Telco trap because it was
originally developed for telecommunications customers. The Enhanced trap includes
the same information as the Standard traps, and provides additional data that makes
it potentially more useful than the Standard traps.

4021339 Rev B 227

Chapter 9 SNMP Management

Both the Standard traps and the Enhanced trap are disabled by default. You enable
and configure the desired trap(s) using SNMP commands, as described in the
following sections. You can also enable and configure these traps using the ICIM
Web Interface, as described in the Prisma II Platform Remote User Interface Guide, part
number 4012441.
Note: Enable either the Standard traps or the Enhanced trap, but not both. Enabling
both traps will result in duplicate traps being sent for each triggering event.

Trap Receiving Configuration

Trap receiving is configured in the p2TrapRecvTable.
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.200.8
A sample view of this table is provided below.

Object RX Trap RX Trap RX Trap RX Trap Example (same

as RX Trap #3)
p2TrapRecvIndex 0 1 2 3 4 5 6 7 8 9
p2TrapRecvEnable enabled (2) disabled (1) disabled (1) disabled (1) 1 1 1 1 1 1
p2TrapRecvAddr 172.24.28.66 172.24.28.94 0.0.0.0 0.0.0.0 0 0 0 0 0 0
p2TrapRecvIPChange disabled (1) disabled (1) disabled (1) disabled (1) 1 1 1 1 1 1
p2TrapRecvModuleInsert disabled (1) disabled (1) disabled (1) disabled (1) 1 1 1 1 1 1
p2TrapRecvModuleRemove disabled (1) disabled (1) disabled (1) disabled (1) 1 1 1 1 1 1
p2TrapRecvMinorAlarm never (1) never (1) never (1) never (1) 1 1 1 1 1 1
p2TrapRecvMajorAlarm never (1) never (1) never (1) never (1) 1 1 1 1 1 1
p2TrapRecvDwnLdComplete disabled (1) disabled (1) disabled (1) disabled (1) 1 1 1 1 1 1
p2TrapRecvRebootCommand disabled (1) disabled (1) disabled (1) disabled (1) 1 1 1 1 1 1
p2TrapRecvSelfTest disabled (1) disabled (1) disabled (1) disabled (1) 1 1 1 1 1 1
p2TrapRecvTelcoAlarm enabled (2) enabled (2) enabled (2) enabled (2) 2 2 2 2 2 2

As shown in the table, the traps can be filtered for each of the 10 trap receiving
addresses. It is important to note that if p2TrapRecvEnable is set to "disabled," no
enterprise specific traps will be sent to that IP address even if the individual filters
are enabled.
The recommended (and default) trap configuration is to only enable
p2TrapRecvTelcoAlarm traps. The other traps are also reported through this trap
type. Enabling p2TrapRecvTelcoAlarms along with other trap types will result in
duplicate traps for a single alarm event. The trap type filtering remains in place in
order to support legacy systems.

228 4021339 Rev B

 Prisma II Traps

To Configure Trap Destination

By setting the objects in the Trap Recv table, you can enable traps to be sent to up to
10 different IP addresses. The index into the table represents one of 10 rows,
designated 0 to 9.
Complete the following steps to receive traps.
1 Set p2TrapRecvEnable to enabled (2), which allows traps to be sent to the IP
address on the same row.
2 Set the IP address of the remote entity to receive traps. Use the format
172.18.2.24.
3 Set p2TrapRecvTelcoAlarm to enabled (2).
The table below shows how these settings might appear in a MIB browser after
enabling IP address 192.0.2.102 to receive Enhanced traps only.

Note: All trap settings are documented for completeness only. Information
contained in other proprietary traps is expanded upon in the Enhanced traps. We do
not recommend using the older (legacy) traps, as the new Enhanced Trap is more
useful. Enabling other traps together with the Enhanced Trap will cause two traps to
be sent for each event. For more information, see Trap Recv Table (on page 188).

Trap Types
As indicated in the p2TrapRecvTable, there are several types of proprietary traps.
All proprietary traps are documented for completeness only. Information contained
in other traps is expanded upon in the Enhanced trap. We do not recommend using
older traps as the new Enhanced trap is more useful. Enabling other traps together
with the Enhanced trap will cause two traps to be sent for each of these events. For
more information, see Trap Recv Table (on page 188).
In general, traps have two sections: the header and the bindings. The headers are
essentially the same from one trap to another. The table shown below describes each
data element contained in the trap header. The first field, indicated by the label
“Specific:” is important as it identifies which trap has been received.

4021339 Rev B 229

Chapter 9 SNMP Management

Trap Header
The table below explains and provides an example of each trap header label.

Label Example Description

Specific 8 Type of trap sent (8 = SelfTest).
Message reception date 1/18/2006 Date trap received remotely.
Message reception time 11:31:24.550 AM Time trap received remotely.
Time stamp 3 days 00h:02m:04s.00th ICIM2 or ICIM2-XD up time since
last reboot.
Message type Trap (v1) Trap via SNMP version 1.
Protocol version SNMPv1 SNMP version 1.
Transport IP/UDP Transport protocol used.
Agent
Address 172.24.28.168 ICIM2 or ICIM2-XD IP address.
Port 162 ICIM2 or ICIM2-XD port.
Manager
Address 172.18.43.3 Remote IP address.
Port 162 Remote port.
Community prismatrap SNMP trap community.
SNMPv1 agent address 172.24.28.168 ICIM2 or ICIM2-XD IP address.
Enterprise p2trapEvents MIB associated with overall trap
generation.
Bindings (2) 2 Number of bindings to follow.

The number following the word Specific indicates the type of trap sent. The possible
values and meanings of this number are as follows:

Unit Meaning
2 Insert Module
3 Remove Module
4 Alarm (Major or Minor, Alarm or Clear)
5 IP Change Event
6 Download Complete
7 Reboot Command
8 SelfTest Failure
9 Telco Alarm

230 4021339 Rev B

 Prisma II Traps

At least one binding follows the header. The Telco traps include 15 bindings carrying
information regarding the entity that caused the trap to be sent. For more
information on Enhanced traps, see Enhanced Trap Binding Information (on page
239).
Other proprietary traps send very basic data, such as the chassis and slot number of
an ICIM2, ICIM2-XD, or application module.

Trap Binding Example

The table below explains and provides an example of trap bindings.

Binding MIB Name (Examples) Explanation

1: ChassisID p2chassisID Chassis where the ICIM2, ICIM2-XD, or
module is installed.
2: SlotID p2slotID Slot where the ICIM2, ICIM2-XD, or
module is installed.
3: Self-Test data p2moduleSelfTest SelfTest Failed - Error code value.

IP Change Trap (Specific: 5)

This trap is sent when an IP address of an ICIM2 or ICIM2-XD is changed through
the CLI. If p2TrapRecvIPChange is set to enabled (2), a trap containing the previous
IP will be sent. The new IP address will take affect on the next ICIM2 or ICIM2-XD
reboot.
Note: Documentation on this trap is included for completeness. All information in
this trap is contained in and expanded upon in the Enhanced trap. We recommend
using the Enhanced trap instead of this trap, as the Enhanced trap is more useful.
Enabling this trap together with the Enhanced trap will cause two traps to be sent for
each triggering event.
Specific: 5 appears in the heading to indicate that this is a IP Change trap. The table
below describes the binding.

Binding MIB Name (Examples) Explanation

1: PreviousIP p2PreviousIP The IP address previously given to the
ICIM2 or ICIM2-XD before a new IP
address was assigned. The new IP
address takes effect upon the next
ICIM2 or ICIM2-XD reboot.

4021339 Rev B 231

Chapter 9 SNMP Management

IP Change Trap Example

Specific: 5
Message reception date: 1/31/2006
Message reception time: 1:19:58.793 PM
Time stamp: 3 days 00h:25m:57s.00th
Message type: Trap (v1)
Protocol version: SNMPv1
Transport: IP/UDP
Agent
Address: 172.24.28.168
Port: 1051
Manager
Address: 172.18.4.23
Port: 162
Community: prismatrap
SNMPv1 agent address: 172.24.28.168
Enterprise: p2trapEvents
Bindings (1)
Binding #1: p2PreviousIP.0 (ipaddr) 172.24.28.168

Module Insert Trap (Specific: 2)

This trap is sent as soon as the ICIM2 or ICIM2-XD discovers that a module has been
inserted. If p2TrapRecvModuleInsert is enabled (2), a trap containing the chassis and
slot of the new module is sent. A number appears in the heading indicating that this
is a module insert trap.
Note: Documentation on this trap is included for completeness. All information in
this trap is contained in and expanded upon in the Enhanced trap. We recommend
using the Enhanced trap instead of this trap, as the Enhanced trap is more useful.
Enabling this trap together with the Enhanced trap will cause two traps to be sent for
each triggering event.
Specific: 2 appears in the heading to indicate that this is a InsertRemove trap. The
table below describes the bindings.

Binding MIB Name (Examples) Explanation

1: ChassisID p2InsertModuleChassisID Chassis where the module is installed.
2: SlotID p2InsertModuleSlotID Slot where the module is installed.

Module Insert Trap Example

Specific: 2
Message reception date: 1/31/2006
Message reception time: 1:24:47.626 PM
Time stamp: 3 days 00h:30m:46s.00th
Message type: Trap (v1)
Protocol version: SNMPv1
Transport: IP/UDP
Agent
Address: 172.24.28.168
Port: 1055
Manager
Address: 172.18.4.28
Port: 162
Community: prismatrap
SNMPv1 agent address: 172.24.28.168
Enterprise: p2trapEvents
Bindings (2)
Binding #1: p2InsertModuleChassisID.1 (int32) 2
Binding #2: p2InsertModuleSlotID.1 (int32) 13

232 4021339 Rev B

 Prisma II Traps

Module Remove Trap (Specific: 3)

This trap is sent when the ICIM2 or ICIM2-XD discovers that a module has been
removed from the chassis. If p2TrapReceiveModuleRemove is enabled (2), a trap
with the chassis and slot where the removed module had been installed will be sent.
Note: Documentation on this trap is included for completeness. All information in
this trap is contained in and expanded upon in the Enhanced trap. We recommend
using the Enhanced trap instead of this trap, as the Enhanced trap is more useful.
Enabling this trap together with the Enhanced trap will cause two traps to be sent for
each triggering event.
Specific: 3 appears in the heading to indicate that this is a ModuleRemove trap. The
table below describes the bindings.

Binding MIB Name (Examples) Explanation

1: ChassisID p2RemoveModuleChassisID Chassis where the module was formerly
installed.
2: SlotID p2RemoveModuleSlotID Slot where the module was formerly
installed.

Module Remove Trap Example

Specific: 3
Message reception date: 1/31/2006
Message reception time: 1:27:35.778 PM
Time stamp: 3 days 00h:33m:35s.00th
Message type: Trap (v1)
Protocol version: SNMPv1
Transport: IP/UDP
Agent
Address: 172.24.28.168
Port: 1060
Manager
Address: 172.18.4.23
Port: 162
Community: prismatrap
SNMPv1 agent address: 172.24.28.168
Enterprise: p2trapEvents
Bindings (2)
Binding #1: p2RemoveModuleChassisID.1 (int32) 2
Binding #2: p2RemoveModuleSlotID.1 (int32) 11

Alarm Traps (Specific: 4)

Alarm traps are edge triggered, meaning that a trap is sent when an alarm changes
state. An alarm changes state when a monitored value exceeds a limit set by an
alarm threshold, or when a monitored Boolean parameter value changes from OK to
Fault. Both cases will generate alarms.
Alarms may trigger Major or Minor alarm traps, depending on the type of alarm
limit that was exceeded. A Major alarm trap is sent when the monitored value
exceeds the Major High or a Major Low alarm threshold. A Minor alarm trap is sent
when the monitored value exceeds the Minor High or Minor Low alarm threshold.
Major and Minor alarm traps affect the ICIM2 or ICIM2-XD polling cycle in different
ways, as follows:

4021339 Rev B 233

Chapter 9 SNMP Management

  If an alarm is Minor, the module in alarm sends a trap to the ICIM2 or ICIM2-XD
after the next polling interval. Minor alarm handling is integral to the polling
process, and does not disrupt the normal polling cycle.
  If an alarm is Major, the module in alarm brings the ICIM2 or ICIM2-XD
Attention line low to request immediate service. In response, the ICIM2 or
ICIM2-XD first identifies the module requesting attention, and then polls the
module to obtain the alarm information. After handling the Major alarm, the
ICIM2 or ICIM2-XD resets the polling process, so that it resumes at the beginning
of the cycle, rather than at the point in the cycle at which it was interrupted.
To configure alarm traps in the p2TrapRecvTable, select values for
p2TrapRecvMajorAlarm or p2TrapRecvMinorAlarm. If traps are to be sent when
monitored values exceed their Major Low or Major High threshold values, configure
p2TrapRecvMajorAlarm. If traps are to be sent when monitored values exceed their
Minor Low or Minor High threshold values, set values in p2TrapRecvMinorAlarm.
Note: A monitor value stated in a trap binding is a snapshot in time, and may not
indicate a value consistent with an alarm condition. If in doubt, verify the actual
monitor value using the appropriate equipment interfaces.
The user may configure alarm trap behavior by selecting one of four options:
  Never (1), meaning that traps of this type should never be sent
  Clear (2), meaning that traps should be sent only when alarms are cleared
  Set (3), meaning that traps should be sent only when alarms are set
  Always (4), meaning that traps should be sent when alarms are set or cleared
Note: Documentation on this trap is included for completeness. All information in
this trap is contained in and expanded upon in the Enhanced trap. We recommend
using the Enhanced trap instead of this trap, as the Enhanced trap is more useful.
Enabling this trap together with the Enhanced trap will cause two traps to be sent for
each triggering event.
Specific: 4 appears in the heading to indicate an Alarm trap. (Specific: 4 as a value
indicates a major alarm or clear, or a minor alarm or clear condition.) The table
below describes the bindings.

Binding MIB Name (Examples) Explanation

1: ChassisID p2chassisID Chassis where the module is installed.
2: SlotID p2slotID Slot where the module is installed.
3: Index p2almIndex The index into the alarm table where
more information may be found.
4: Label p2almLabel Label for the element that is in the state
of alarm, e.g., Ps1+24.

234 4021339 Rev B

 Prisma II Traps

Alarm Trap Example

Specific: 4
Message reception date: 1/31/2006
Message reception time: 1:31:58.829 PM
Time stamp: 3 days 00h:37m:58s.00th
Message type: Trap (v1)
Protocol version: SNMPv1
Transport: IP/UDP
Agent
Address: 172.24.28.168
Port: 1074
Manager
Address: 172.18.4.23
Port: 162
Community: prismatrap
SNMPv1 agent address: 172.24.28.168
Enterprise: p2trapEvents
Bindings (4)
Binding #1: p2chassisID.2.3 (int32) 2
Binding #2: p2slotID.2.3 (int32) 3
Binding #3: p2almIndex.2.3.4 (int32) 4
Binding #4: p2almLabel.2.3.4 (octets) Ps1+24

Download Complete Trap (Specific: 6)

This trap is reserved for future use.

Reboot Command Trap (Specific: 7)

When an ICIM2, ICIM2-XD, or application module receives the command to reboot,
a trap is generated. If this reboot command is generated via the SOUP application, a
broadcast reboot is sent out. In this case, only one trap may be generated for the
ICIM2 or ICIM2-XD and all modules under its management. To configure the reboot
command trap to be sent, set p2TrapRecvRebootCommand to enabled (2).
Note: Documentation on this trap is included for completeness. All information in
this trap is contained in and expanded upon in the Enhanced trap. We recommend
using the Enhanced trap instead of this trap, as the Enhanced trap is more useful.
Enabling this trap together with the Enhanced trap will cause two traps to be sent for
each triggering event.
Specific: 7 appears in the heading to indicate a RebootCommand trap. The table
below describes the bindings.

Binding MIB Name (Examples) Explanation

1: ChassisID p2chassisID Chassis where the ICIM2, ICIM2-XD, or
module is installed.
2: SlotID p2slotID Slot where the ICIM2, ICIM2-XD, or
module is installed.

The example below shows the bindings for a broadcast RebootCommand Trap.
Chassis 99 and slot 99 indicate that the reboot command was broadcast to all
modules.

4021339 Rev B 235

Chapter 9 SNMP Management

Reboot Command Trap Example

Specific: 7
Message reception date: 1/31/2006
Message reception time: 1:47:14.920 PM
Time stamp: 3 days 00h:53m:16s.00th
Message type: Trap (v1)
Protocol version: SNMPv1
Transport: IP/UDP
Agent
Address: 172.24.28.168
Port: 1145
Manager
Address: 172.18.4.23
Port: 162
Community: prismatrap
SNMPv1 agent address: 172.24.28.168
Enterprise: p2trapEvents
Bindings (2)
Binding #1: p2chassisID.99 (int32) 99
Binding #2: p2slotID.99 (int32) 99

Self-Test Trap (Specific: 8)

This trap is sent if the ICIM2, ICIM2-XD, or an application module fails the self-test.
The trap contains an error code, which is module-specific. See the sections on
p2icimSelfTest in ICIM MIB (on page 173) and p2moduleSelfTest in Module MIB (on
page 198) for further discussion of the error codes. To receive the SelfTest traps, set
p2TrapRecvSelfTest to enabled (2).
Note: Documentation on this trap is included for completeness. All information in
this trap is contained in and expanded upon in the Enhanced trap. We recommend
using the Enhanced trap instead of this trap, as the Enhanced trap is more useful.
Enabling this trap together with the Enhanced trap will cause two traps to be sent for
each triggering event.
Specific: 8 appears in the heading to indicate a SelfTest trap. The table below
describes the bindings.

Binding MIB Name (Examples) Explanation

1: ChassisID p2chassisID Chassis where the ICIM2, ICIM2-XD, or
module is installed.
2: SlotID p2slotID Slot where the ICIM2, ICIM2-XD, or
module is installed.
3: Self-Test data p2moduleSelfTest SelfTest Failed - Error Code value.

236 4021339 Rev B

 Prisma II Traps

Self-Test Trap Example

Specific: 8
Message reception date: 1/31/2006
Message reception time: 2:22:20.190 PM
Time stamp: 3 days 00h:00m:20s.00th
Message type: Trap (v1)
Protocol version: SNMPv1
Transport: IP/UDP
Agent
Address: 172.24.28.168
Port: 1025
Manager
Address: 172.18.4.23
Port: 162
Community: prismatrap
SNMPv1 agent address: 172.24.28.168
Enterprise: p2trapEvents
Bindings (3)
Binding #1: p2chassisID.2 (int32) 2
Binding #2: p2slotID.2 (int32) 15
Binding #3: p2moduleSelfTest.2.15 (octets) SelfTest Failed - Error Code 32.

Telco Traps (Specific: 9)

The Enhanced traps summarize information for all trap types, with additional data,
exclusive of all other traps. Also, if an alarm exists upon startup or module insertion,
Enhanced traps will be sent. To configure the Enhanced traps, set
p2TrapRecvTelcoAlarm to enabled (2).
Specific: 9 appears in the heading to indicate an Enhanced trap. The table below
describes the bindings.

Example of Bindings

Trap Binding MIB Name (Examples) Explanation

1 Sequence p2TrapLogSequence Tracking number from 1 to 2,147,483,647.
2 Severity p2TrapLogSeverity Trap severity level - major (1), minor (2),
warning (3).
3 State p2TrapLogState State - alarm (1), clear (2), event (3).
4 Label p2TrapLogLabel or Event Name or
p2almLabel.1.3.4 Alarm Label.
5 OID p2almIndex.1.3 or More data regarding the alarm or event is
found at this OID.
p2icimStatusMsg
6 Text p2TrapLogText Module name and model number or
ICIM2.
7 ChassisID p2icimChassisID Chassis where the ICIM2, ICIM2-XD, or
module is installed.
8 SlotID p2icimSlotID Slot where the ICIM2, ICIM2-XD, or
module is installed.
9 CLLIcode p2icimCLLIcode Reserved for future use.
10 CLEIcode p2icimCLEIcode Reserved for future use.

4021339 Rev B 237

Chapter 9 SNMP Management

Trap Binding MIB Name (Examples) Explanation

11 Time p2TrapLogTime Time trap generated in the format:
YYYY-MM-DD, HH:MM:SS.ss
12 DateTime p2TrapLogDateTime Date and time generated in the format:
DOW, DD MMM YYYY HH:MM:SS ZZZ
13 Value p2TrapLogValue Monitored value of the object in alarm.
14 Units p2TrapLogUnit Monitored units of the value in alarm.
15 Description p2TrapLogDesc Verbose description of the alarm or event.

Example
Binding #1: p2TrapLogSequence *** (int32) 6
Binding #2: p2TrapLogSeverity *** (int32) major(1)
Binding #3: p2TrapLogState *** (int32) alarm(1)
Binding #4: p2almLabel.0.11.2 *** (octets) OutPwrA
Binding #5: p2almIndex.0.11 *** (int32) 2
Binding #6: p2TrapLogText *** (octets)
Module=1550nm Post-Amp FTTP,Model=3031
Binding #7: p2chassisID.0.11 *** (int32) 0
Binding #8: p2slotID.0.11 *** (int32) 11
Binding #9: p2moduleCLLIcode.0.11 *** (octets)SCIATL01
Binding #10: p2moduleCLEIcode.0.11 *** (octets) PostAmpCLEI
Binding #11: p2TrapLogTime *** (octets) 2006-8-22,15:45:38.11
Binding #12: p2TrapLogDateTime *** (octets) Tue, 22 Aug 2006 15:45:38 EST
Binding #13: p2TrapLogValue *** (octets) -50
Binding #14: p2TrapLogUnit *** (octets) dBm
Binding #15: p2TrapLogDescr *** (octets)
Optical output power of bank A exceeds major threshold (1550nm)

Trap Generation
Proprietary traps are generated as described above for edge triggered alarms or clear
alarms (meaning a change in state of an alarm), as well as for any of the following
events:
  Changing the IP address of an ICIM2 or ICIM2-XD
  Inserting or removing a module
  Successful completion of a download
  Reboot of an ICIM2, ICIM2-XD, or module
  Failure of an ICIM2, ICIM2-XD, or module self-test
Additionally, the Enhanced traps are generated if an alarm condition exists in one of
the modules upon startup or module insertion.

238 4021339 Rev B

 Prisma II Traps

Trap Logging
When an Enhanced trap is sent, a copy is also kept in the Trap Logging table of the
ICIM2 or ICIM2-XD. Each trap has a unique sequence number which may be used as
the index into the Trap Logging table. All bindings captured in the Enhanced traps
are also logged, and may be accessed in the event of network failures between the
SNMP manager and the ICIM2 or ICIM2-XD. The log retains up to 1,000 most recent
Enhanced traps.
The figure below shows how the Trap Logging table might appear when displayed
in a MIB browser.

Note: At least one row in the p2TrapRecvTable needs to be configured and enabled,
with p2TrapRecvTelcoAlarm enabled (2) for logging of traps will occur
automatically. For details, see To Configure Trap Destination (on page 229).

Enhanced Trap Binding Information

The Enhanced trap type was originally added to support the Telco requirement to
include a trap sequence number (p2TrapLogSequence) binding. In addition, the
Enhanced trap type includes other bindings to convey complete alarm information.
Important: The default and recommended configuration is to enable only the
Enhanced trap type. Enabling Enhanced alarm traps and other trap types at the same
time may result in duplicate traps being sent to the element management system.
These other trap types remain to allow backward compatibility with previously
deployed systems.
The table below provides a descriptive listing of the Enhanced trap bindings.

Trap Binding Description

1 p2TrapLogSequence A unique number assigned to each trap as it is generated.
Serves as an index into the Trap Logging table.

4021339 Rev B 239

Chapter 9 SNMP Management

Trap Binding Description

2 p2TrapLogSeverity The number assigned as a guide to prioritizing trap
generating conditions. Severity may be major (1), minor (2),
or warning (3).
3 p2TrapLogState State, along with severity, quickly gives a view into the
current state of an entity. State may be alarm (1), clear (2),
or event (3).
4 p2almLabel For an alarm or clear trap, the label is the same as the
p2almLabel assigned to the condition that caused the trap,
p2TrapLogLabel
e.g. ChasTemp. For events, the type of event that sent the
trap is identified as DownloadComplete, RebootCommand,
SelfTest, AuthentictnFailed, AdminChange,
LogMenuHalfFull, LogMenuFull, LoginThreshold, SNTP,
UpdateChassisIDs, or UserLockout.
5 p2almIndex More information regarding the trap may be found at the
OID specified in this element. For an alarm or clear trap,
p2InsertModuleEntry
this may be the third index into the Module Alarm table.
p2icimStatusMsg For the download, reboot, or self-test event, this may be the
p2icimStatusMessage. However, only the most recent
p2RemoveModuleEntry
status message is retained by the ICIM2 or ICIM2-XD. If a
p2ModuleSelfTest message generated by another even overwrites the status
message, additional information may no longer be
p2icimSelfTest
available at the OID specified for the particular trap. If an
p2icimIPAddr event is logged, event details may be saved in the event
log.
6 p2TrapLogText Display string which further describes the entity or
condition responsible for trap generation. This usually is a
concatenation of the module name and module number,
although it may include the self-test failure code.
7 p2icimChassisID Chassis in which the ICIM2, ICIM2-XD, or application
module resides at the time of trap generation.
p2chassis
8 p2icimSlotID Slot number in which the ICIM2, ICIM2-XD, or application
module resides at the time of trap generation.
p2slotID
9 p2icimCLLIcode Reserved for future use.
10 p2icimCLEIcode Reserved for future use.
11 p2TrapLogTime Date and time stamp indicating when the trap was
generated.
12 p2TrapLogDateTime Full local time displayed in the format:
DOW, DD MMM YYYY HH:MM:SS ZZZ
Note: The local time zone must be entered in
p2icimTimeZone or the default time zone, EST, will show.
13 p2TrapLogValue Monitored value of the object in alarm.

240 4021339 Rev B

 Prisma II Traps

Trap Binding Description

14 p2TrapLogUnit Monitored units of the value in alarm.
15 p2TrapLogDescr Verbose description of the alarm or event.

Trap Sequence Numbering

To observe the most current sequence number used by the Enhanced traps, perform
a get operation on this OID. If no traps have been sent, the
p2TrapLastSequenceNumber is 0. Valid sequence numbers are 1 through
2,147,483,647. The sequence number resets to 1 with the first trap sent after the
ICIM2 or ICIM2-XD boots up, or the p2TrapLogEntry table is cleared with the
p2TrapLogClearKey, or with the trap following sequence number 2,147,483,647.
OID: 1.3.6.1.4.1.1429.1.6.2.2.13.200.1

Enhanced Trap Binding Categories

Each trap has a heading and bindings. Generally, Enhanced trap bindings fall into
the categories below. However, examples of specific traps follow this general
explanation.

Enhanced Trap Header Example

Labels Example Explanation

Specific 9 Type of trap sent (9 = Enhanced).
Message reception 1/18/2006 Date trap was received remotely.
date
Message reception 11:31:24.550 AM Time trap was received remotely.
time
Time stamp 3 days 00h:02m:04s.00th ICIM2 or ICIM2-XD up time since last
reboot.
Message type Trap (v1) Trap via SNMP version 1.
Protocol version SNMPv1 SNMP version 1.
Transport IP/UDP Transport protocol used.
Agent
Address 172.1.1.2 ICIM2 or ICIM2-XD IP address.
Port 1037 ICIM2 or ICIM2-XD port.
Manager
Address 172.2.2.3 Remote IP address.
Port 162 Remote port.
Community prismatrap SNMP trap community.

4021339 Rev B 241

Chapter 9 SNMP Management

Labels Example Explanation

SNMPv1 agent 172.1.1.2 ICIM2 or ICIM2-XD IP address.
address
Enterprise p2trapEvents MIB associated with overall trap
generation.
Bindings (15) 15 Number of bindings to follow.

In the heading of a trap, the type of trap is indicated after the first word Specific.
Values following the Specific stand for:
  2 Insert Module
  3 Remove Module
  4 Alarm (Major or Minor, Alarm or Clear)
  5 Ip Change Event
  6 Download Complete (reserved for future use)
  7 Reboot Command
  8 SelfTest Failure
  9 Enhanced Alarm
Important: The default and recommended configuration is to enable only the
Enhanced trap type. Enabling Enhanced alarm traps and other trap types at the same
time may result in duplicate traps being sent to the element management system.
These other trap types remain to allow backward compatibility with previously
deployed systems.

Enhanced Trap Bindings Example

Trap Binding MIB Name (Examples) Explanation

1 Sequence p2TrapLogSequence Tracking number from 1 to 2,147,483,647.
2 Severity p2TrapLogSeverity Trap severity level - major (1), minor (2),
warning (3).
3 State p2TrapLogState State - alarm (1), clear (2), event (3).
4 Label p2TrapLogLabel or Event Name or
p2almLabel.1.3.4 Alarm Label.
5 OID p2almIndex.1.3 or More data regarding the alarm or event is
found at this OID.
p2icimStatusMsg
6 Text p2TrapLogText Module name and model number of ICIM2
or ICIM2-XD.

242 4021339 Rev B

 Prisma II Traps

Trap Binding MIB Name (Examples) Explanation

7 ChassisID p2icimChassisID Chassis where the ICIM2, ICIM2-XD, or
application module is installed.
8 SlotID p2icimSlotID Slot where the ICIM2, ICIM2-XD, or
application module is installed.
9 CLLIcode p2icimCLLIcode Reserved for future use.
10 CLEIcode p2icimCLEIcode Reserved for future use.
11 Time p2TrapLogTime Time trap generated in the format:
YYYY-MM-DD,HH:MM:SS.ss
12 DateTime p2TrapLogDateTime Date and Time generated in the format:
DOW, DD MMM YYYY HH:MM:SS ZZZ
13 Value p2TrapLogValue Value of the element in alarm.
14 Units p2TrapLogUnit Units in which the value is described.
15 Description p2TrapLogDescr Verbose description of the alarm or event.

Enhanced Trap Alarms

The current system release supports Enhanced trap alarms that alert the element
management system to the following alarm types:
  Alarm Major
  Alarm Major Clear
  Alarm Minor
  Alarm Minor Clear
This section provides examples of each of these alarm types.

4021339 Rev B 243

Chapter 9 SNMP Management

Alarm Major
Specific: 9
Message reception date: 12/17/2007
Message reception time: 5:36:49 PM
Time stamp: 4 days 02h:04m:34s.68th
Message type: Trap (v1)
Protocol version: SNMPv1
Transport: IP/UDP
Agent
Address: 192.168.1.149
Port: 1182
Manager
Address: 192.168.1.7
Port: 162
Community: prismatrap
SNMPv1 agent address: 192.168.1.149
Enterprise: p2trapEvents
Bindings (15)
Binding #1: p2TrapLogSequence *** (int32) 81
Binding #2: p2TrapLogSeverity *** (int32) major(1)
Binding #3: p2TrapLogState *** (int32) alarm(1)
Binding #4: p2almLabel.99.0.2 *** (octets) Fan2_Ok
Binding #5: p2almIndex.99.0 *** (int32) 2
Binding #6: p2TrapLogText *** (octets) Module=XD-Chassis, Model=5020
Binding #7: p2chassisID.99.0 *** (int32) 99
Binding #8: p2slotID.99.0 *** (int32) 0
Binding #9: p2moduleCLLIcode.99.0 *** (octets) Grayson
Binding #10: p2moduleCLEIcode.99.0 *** (octets)N/A
Binding #11: p2TrapLogTime *** (octets) 2007-12-17,17:36:55.80
Binding #12: p2TrapLogDateTime *** (octets) Mon, 17 Dec 2007 17:36:55 EST
Binding #13: p2TrapLogValue *** (octets) N/A
Binding #14: p2TrapLogUnit *** (octets) N/A
Binding #15: p2TrapLogDescr *** (octets) Fan2_Ok exceeded major threshold

Alarm Major Clear

Specific: 9
Message reception date: 12/17/2007
Message reception time: 5:37:46 PM
Time stamp: 4 days 02h:05m:31s.68th
Message type: Trap (v1)
Protocol version: SNMPv1
Transport: IP/UDP
Agent
Address: 192.168.1.149
Port: 1184
Manager
Address: 192.168.1.7
Port: 162
Community: prismatrap
SNMPv1 agent address: 192.168.1.149
Enterprise: p2trapEvents
Bindings (15)
Binding #1: p2TrapLogSequence *** (int32) 82
Binding #2: p2TrapLogSeverity *** (int32) major(1)
Binding #3: p2TrapLogState *** (int32) clear(2)
Binding #4: p2almLabel.99.0.2 *** (octets) Fan2_Ok
Binding #5: p2almIndex.99.0 *** (int32) 2
Binding #6: p2TrapLogText *** (octets) Module=XD-Chassis, Model=5020
Binding #7: p2chassisID.99.0 *** (int32) 99
Binding #8: p2slotID.99.0 *** (int32) 0
Binding #9: p2moduleCLLIcode.99.0 *** (octets) Grayson
Binding #10: p2moduleCLEIcode.99.0 *** (octets) N/A
Binding #11: p2TrapLogTime *** (octets) 2007-12-17,17:37:52.80
Binding #12: p2TrapLogDateTime *** (octets) Mon, 17 Dec 2007 17.37.52 EST
Binding #13: p2TrapLogValue *** (octets) N/A
Binding #14: p2TrapLogUnit *** (octets) N/A
Binding #15: p2TrapLogDescr *** (octets) Fan2_Ok within major threshold

244 4021339 Rev B

 Prisma II Traps

Alarm Minor
Specific: 9
Message reception date: 12/17/2007
Message reception time: 5:34:38 PM
Time stamp: 4 days 02h:02m:23s.50th
Message type: Trap (v1)
Protocol version: SNMPv1
Transport: IP/UDP
Agent
Address: 192.168.1.149
Port: 1178
Manager
Address: 192.168.1.7
Port: 162
Community: prismatrap
SNMPv1 agent address: 192.168.1.149
Enterprise: p2trapEvents
Bindings (15)
Binding #1: p2TrapLogSequence *** (int32) 79
Binding #2: p2TrapLogSeverity *** (int32) minor(2)
Binding #3: p2TrapLogState *** (int32) alarm(1)
Binding #4: p2almLabel.99.0.4 *** (octets) ChasTemp
Binding #5: p2almIndex.99.0 *** (int32) 4
Binding #6: p2TrapLogText *** (octets) Module=XD-Chassis, Model=5020
Binding #7: p2chassisID.99.0 *** (int32) 99
Binding #8: p2slotID.99.0 *** (int32) 0
Binding #9: p2moduleCLLIcode.0.0 *** (octets) Grayson
Binding #10: p2moduleCLEIcode.0.0 *** (octets) N/A
Binding #11: p2TrapLogTime *** (octets) 2007-12-17,17:34:44.62
Binding #12: p2TrapLogDateTime *** (octets) Mon, 17 Dec 2007 17:34:44 EST
Binding #13: p2TrapLogValue *** (octets) 28.75
Binding #14: p2TrapLogUnit *** (octets) degC
Binding #15: p2TrapLogDescr *** (octets) ChasTemp exceeded minor threshold

Alarm Minor Clear

Specific: 9
Message reception date: 12/17/2007
Message reception time: 5:35:46 PM
Time stamp: 4 days 02h:03m:31s.50th
Message type: Trap (v1)
Protocol version: SNMPv1
Transport: IP/UDP
Agent
Address: 192.168.1.149
Port: 1180
Manager
Address: 192.168.1.7
Port: 162
Community: prismatrap
SNMPv1 agent address: 192.168.1.149
Enterprise: p2trapEvents
Bindings (15)
Binding #1: p2TrapLogSequence *** (int32) 80
Binding #2: p2TrapLogSeverity *** (int32) minor(2)
Binding #3: p2TrapLogState *** (int32) clear(2)
Binding #4: p2almLabel.99.0.4 *** (octets) ChasTemp
Binding #5: p2almIndex.99.0 *** (int32) 4
Binding #6: p2TrapLogText *** (octets) Module=XD-Chassis, Model=5020
Binding #7: p2chassisID.99.0 *** (int32) 99
Binding #8: p2slotID.99.0 *** (int32) 0
Binding #9: p2moduleCLLIcode.99.0 *** (octets) Grayson
Binding #10: p2moduleCLEIcode.99.0 *** (octets) N/A
Binding #11: p2TrapLogTime *** (octets) 2007-12-17,17:35:52.62
Binding #12: p2TrapLogDateTime *** (octets) Mon, 17 Dec 2007 17:35:52 EST
Binding #13: p2TrapLogValue *** (octets) 25.75
Binding #14: p2TrapLogUnit *** (octets) degC
Binding #15: p2TrapLogDescr *** (octets) ChasTemp within minor threshold

4021339 Rev B 245

Chapter 9 SNMP Management

Enhanced Trap Events

The current system release supports Enhanced traps that alert management to
certain events related to user login, changes to system settings, event log memory
usage, SNTP failures, and user lockout activity.
All event traps display binding 2 (severity) as warning (3) and binding 3 (state) as
event (3).
Binding 4 (label) may be an alarm label, or may include any of the following event
types:
  Admin Change
  Authentication Failed
  Download Complete (reserved for future use)
  IP Change
  Login Threshold
  Log (Event Log)
  Module Insert
  Module Remove
  Reboot
  SelfTest
  SNTP (reserved for future use)
  Update Chassis IDs
  User Lockout
For example:
Binding #2: p2TrapLogSeverity *** (int32) warning(3)
Binding #3: p2TrapLogState *** (int32) event(3)
Binding #4: p2TrapLogLabel *** (octets) AdminChange

This section describes the events that cause each of these traps to be sent and gives
examples of each trap where appropriate.

AdminChange
An AdminChange trap is sent when an Admin user performs one of the following
actions.
  Add a user
  Change a password
  Change access level

246 4021339 Rev B

 Prisma II Traps

  Enable or disable the status of a user

  Delete a user
  Fail to add a user because the list of users is full (16)
  Change the inactivity timeout
  Change the login thresholds
  Change the User Lockout interval setting

4021339 Rev B 247

Chapter 9 SNMP Management

Admin Change Example - Add New User

Specific: 9
Message reception date: 10/30/2006
Message reception time: 1:46:53.476 PM
Time stamp: 2 days 22h:12m:43s.91th
Message type: Trap (v1)
Protocol version: SNMPv1
Transport: IP/UDP
Agent
Address: 172.24.25.175
Port: 1055
Manager
Address: 172.18.10.23
Port: 162
Community: prismatrap
SNMPv1 agent address: 172.24.25.175
Enterprise: p2trapEvents
Bindings (15)
Binding #1: p2TrapLogSequence *** (int32) 22
Binding #2: p2TrapLogSeverity *** (int32) warning(3)
Binding #3: p2TrapLogState *** (int32) event(3)
Binding #4: p2TrapLogLabel *** (octets) AdminChange
Binding #5: p2icimStatusMsg.0 *** (int32) 0
Binding #6: p2TrapLogText *** (octets) ICIM2
Binding #7: p2chassisID.1.15 *** (int32) 1
Binding #8: p2slotID.1.15 *** (int32) 15
Binding #9: p2moduleCLLIcode.1.15 *** (octets) Engineering Lab
Binding #10: p2moduleCLEIcode.1.15 *** (octets) ICIMCLEI75
Binding #11: p2TrapLogTime *** (octets) 2006-10-30,13:46:35.19
Binding #12: p2TrapLogDateTime *** (octets) Mon, 30 Oct 2006 13:46:35 EST
Binding #13: p2TrapLogValue *** (octets) N/A
Binding #14: p2TrapLogUnit *** (octets) N/A
Binding #15: p2TrapLogDescr *** (octets) Add user ReadWrite3

Admin Change Example - Change ICIM Setting (Inactivity Timer)

Specific: 9
Message reception date: 10/30/2006
Message reception time: 1:25:26.078 PM
Time stamp: 2 days 21h:51m:16s.53th
Message type: Trap (v1)
Protocol version: SNMPv1
Transport: IP/UDP
Agent
Address: 172.24.25.175
Port: 1054
Manager
Address: 172.18.10.23
Port: 162
Community: prismatrap
SNMPv1 agent address: 172.24.25.175
Enterprise: p2trapEvents
Bindings (15)
Binding #1: p2TrapLogSequence *** (int32) 21
Binding #2: p2TrapLogSeverity *** (int32) warning(3)
Binding #3: p2TrapLogState *** (int32) event(3)
Binding #4: p2TrapLogLabel *** (octets) AdminChange
Binding #5: p2icimStatusMsg.0 *** (int32) 0
Binding #6: p2TrapLogText *** (octets) ICIM2
Binding #7: p2chassisID.1.15 *** (int32) 1
Binding #8: p2slotID.1.15 *** (int32) 15
Binding #9: p2moduleCLLIcode.1.15 *** (octets) Engineering Lab
Binding #10: p2moduleCLEIcode.1.15 *** (octets) ICIMCLEI75
Binding #11: p2TrapLogTime *** (octets) 2006-10-30,13:25:7.77
Binding #12: p2TrapLogDateTime *** (octets) Mon, 30 Oct 2006 13:25:07 EST
Binding #13: p2TrapLogValue *** (octets) N/A
Binding #14: p2TrapLogUnit *** (octets) N/A
Binding #15: p2TrapLogDescr *** (octets) Change inactivity timer setting
to: 10 minutes

248 4021339 Rev B

 Prisma II Traps

Admin Change Example - Change ICIM Setting (Login Threshold)

Specific: 9
Message reception date: 10/30/2006
Message reception time: 1:19:04.310 PM
Time stamp: 2 days 21h:44m:54s.78th
Message type: Trap (v1)
Protocol version: SNMPv1
Transport: IP/UDP
Agent
Address: 172.24.25.175
Port: 1049
Manager
Address: 172.18.10.23
Port: 162
Community: prismatrap
SNMPv1 agent address: 172.24.25.175
Enterprise: p2trapEvents
Bindings (15)
Binding #1: p2TrapLogSequence *** (int32) 16
Binding #2: p2TrapLogSeverity *** (int32) warning(3)
Binding #3: p2TrapLogState *** (int32) event(3)
Binding #4: p2TrapLogLabel *** (octets) AdminChange
Binding #5: p2icimStatusMsg.0 *** (int32) 0
Binding #6: p2TrapLogText *** (octets) ICIM2
Binding #7: p2chassisID.1.15 *** (int32) 1
Binding #8: p2slotID.1.15 *** (int32) 15
Binding #9: p2moduleCLLIcode.1.15 *** (octets) Engineering Lab
Binding #10: p2moduleCLEIcode.1.15 *** (octets) ICIMCLEI75
Binding #11: p2TrapLogTime *** (octets) 2006-10-30,13:18:46.0
Binding #12: p2TrapLogDateTime *** (octets) Mon, 30 Oct 2006 13:18:46 EST
Binding #13: p2TrapLogValue *** (octets) N/A
Binding #14: p2TrapLogUnit *** (octets) N/A
Binding #15: p2TrapLogDescr *** (octets) Change login threshold setting
to: 5 minutes

Admin Change Example - Change User Password

Specific: 9
Message reception date: 10/30/2006
Message reception time: 1:48:37.618 PM
Time stamp: 2 days 22h:14m:28s.06th
Message type: Trap (v1)
Protocol version: SNMPv1
Transport: IP/UDP
Agent
Address: 172.24.25.175
Port: 1056
Manager
Address: 172.18.10.23
Port: 162
Community: prismatrap
SNMPv1 agent address: 172.24.25.175
Enterprise: p2trapEvents
Bindings (15)
Binding #1: p2TrapLogSequence *** (int32) 23
Binding #2: p2TrapLogSeverity *** (int32) warning(3)
Binding #3: p2TrapLogState *** (int32) event(3)
Binding #4: p2TrapLogLabel *** (octets) AdminChange
Binding #5: p2icimStatusMsg.0 *** (int32) 0
Binding #6: p2TrapLogText *** (octets) ICIM2
Binding #7: p2chassisID.1.15 *** (int32) 1
Binding #8: p2slotID.1.15 *** (int32) 15
Binding #9: p2moduleCLLIcode.1.15 *** (octets) Engineering Lab
Binding #10: p2moduleCLEIcode.1.15 *** (octets) ICIMCLEI75
Binding #11: p2TrapLogTime *** (octets) 2006-10-30,13:48:19.34
Binding #12: p2TrapLogDateTime *** (octets) Mon, 30 Oct 2006 13:48:19 EST
Binding #13: p2TrapLogValue *** (octets) N/A
Binding #14: p2TrapLogUnit *** (octets) N/A
Binding #15: p2TrapLogDescr *** (octets) Changed user password for
ReadWrite3

4021339 Rev B 249

Chapter 9 SNMP Management

Admin Change Example - Delete User

Specific: 9
Message reception date: 10/30/2006
Message reception time: 1:50:06.243 PM
Time stamp: 2 days 22h:15m:56s.68th
Message type: Trap (v1)
Protocol version: SNMPv1
Transport: IP/UDP
Agent
Address: 172.24.25.175
Port: 1057
Manager
Address: 172.18.10.23
Port: 162
Community: prismatrap
SNMPv1 agent address: 172.24.25.175
Enterprise: p2trapEvents
Bindings (15)
Binding #1: p2TrapLogSequence *** (int32) 24
Binding #2: p2TrapLogSeverity *** (int32) warning(3)
Binding #3: p2TrapLogState *** (int32) event(3)
Binding #4: p2TrapLogLabel *** (octets) AdminChange
Binding #5: p2icimStatusMsg.0 *** (int32) 0
Binding #6: p2TrapLogText *** (octets) ICIM2
Binding #7: p2chassisID.1.15 *** (int32) 1
Binding #8: p2slotID.1.15 *** (int32) 15
Binding #9: p2moduleCLLIcode.1.15 *** (octets) Engineering Lab
Binding #10: p2moduleCLEIcode.1.15 *** (octets) ICIMCLEI75
Binding #11: p2TrapLogTime *** (octets) 2006-10-30,13:49:47.97
Binding #12: p2TrapLogDateTime *** (octets) Mon, 30 Oct 2006 13:49:47 EST
Binding #13: p2TrapLogValue *** (octets) N/A
Binding #14: p2TrapLogUnit *** (octets) N/A
Binding #15: p2TrapLogDescr *** (octets) Delete user ReadWrite3

AuthentictnFailed
An AuthentictnFailed trap is sent when a user login (authentication) fails due to one
of the following causes:
  The user ID is disabled.
  The password is not correct.
  The user ID is not correct or is not found.
  There are too many users logged into the ICIM2 or ICIM2-XD at the current time.
  The list of valid users could not be retrieved from the EEPROM.

250 4021339 Rev B

 Prisma II Traps

Authentication Failed - Password incorrect

Specific: 9
Message reception date: 10/30/2006
Message reception time: 1:15:21.261 PM
Time stamp: 2 days 21h:41m:11s.73th
Message type: Trap (v1)
Protocol version: SNMPv1
Transport: IP/UDP
Agent
Address: 172.24.25.175
Port: 1048
Manager
Address: 172.18.10.23
Port: 162
Community: prismatrap
SNMPv1 agent address: 172.24.25.175
Enterprise: p2trapEvents
Bindings (15)
Binding #1: p2TrapLogSequence *** (int32) 15
Binding #2: p2TrapLogSeverity *** (int32) warning(3)
Binding #3: p2TrapLogState *** (int32) event(3)
Binding #4: p2TrapLogLabel *** (octets) AuthentictnFailed
Binding #5: p2icimStatusMsg.0 *** (int32) 0
Binding #6: p2TrapLogText *** (octets) ICIM2
Binding #7: p2chassisID.1.15 *** (int32) 1
Binding #8: p2slotID.1.15 *** (int32) 15
Binding #9: p2moduleCLLIcode.1.15 *** (octets) Engineering Lab
Binding #10: p2moduleCLEIcode.1.15 *** (octets) ICIMCLEI75
Binding #11: p2TrapLogTime *** (octets) 2006-10-30,13:15:2.94
Binding #12: p2TrapLogDateTime *** (octets) Mon, 30 Oct 2006 13:15:02 EST
Binding #13: p2TrapLogValue *** (octets) N/A
Binding #14: p2TrapLogUnit *** (octets) N/A
Binding #15: p2TrapLogDescr *** (octets) Password failed: Administrat0r

Authentication Failed - User ID Disabled

Specific: 9
Message reception date: 10/30/2006
Message reception time: 4:31:48.399 PM
Time stamp: 0 days 00h:06m:26s.51th
Message type: Trap (v1)
Protocol version: SNMPv1
Transport: IP/UDP
Agent
Address: 172.24.28.151
Port: 1047
Manager
Address: 172.18.10.23
Port: 162
Community: prismatrap
SNMPv1 agent address: 172.24.28.151
Enterprise: p2trapEvents
Bindings (15)
Binding #1: p2TrapLogSequence *** (int32) 24
Binding #2: p2TrapLogSeverity *** (int32) warning(3)
Binding #3: p2TrapLogState *** (int32) event(3)
Binding #4: p2TrapLogLabel *** (octets) AuthentictnFailed
Binding #5: p2icimStatusMsg.0 *** (int32) 0
Binding #6: p2TrapLogText *** (octets) ICIM2
Binding #7: p2chassisID.3.15 *** (int32) 3
Binding #8: p2slotID.3.15 *** (int32) 15
Binding #9: p2moduleCLLIcode.3.15 *** (octets) icimCLLIcode7
Binding #10: p2moduleCLEIcode.3.15 *** (octets) (zero-length)
Binding #11: p2TrapLogTime *** (octets) 2006-10-30,16:33:14.89
Binding #12: p2TrapLogDateTime *** (octets) Mon, 30 Oct 2006 16:33:14 EST
Binding #13: p2TrapLogValue *** (octets) N/A
Binding #14: p2TrapLogUnit *** (octets) N/A
Binding #15: p2TrapLogDescr *** (octets) Try to login to a disabled account:
bogusUser2

4021339 Rev B 251

Chapter 9 SNMP Management

Download Complete
This trap is reserved for future use.

IP Change
An IPChange trap is sent as notification that the IP address of the ICIM2 or ICIM2-
XD has been changed.

IP Change Example - ICIM IP Change

Specific: 9
Message reception date: 8/25/2006
Message reception time: 10:03:30.896 AM
Time stamp: 0 days 00h:15m:19s.00th
Message type: Trap (v1)
Protocol version: SNMPv1
Transport: IP/UDP
Agent
Address: 172.2.5.168
Port: 1030
Manager
Address: 172.24.3.151
Port: 162
Community: prismatrap
SNMPv1 agent address: 172.2.5.168
Enterprise: p2trapEvents
Bindings (15)
Binding #1: p2TrapLogSequence *** (int32) 7
Binding #2: p2TrapLogSeverity *** (int32) warning(3)
Binding #3: p2TrapLogState *** (int32) event(3)
Binding #4: p2TrapLogLabel *** (octets) IPchange
Binding #5: p2icimIPAddr *** (int32) 0
Binding #6: p2TrapLogText *** (octets) ICIM IP address changed --
172.24.28.151.
Binding #7: p2icimChassisID *** (int32) 0
Binding #8: p2icimSlotID *** (int32) 15
Binding #9: p2icimCLLIcode *** (octets) SCIATL01
Binding #10: p2icimCLEIcode *** (octets) VLLUAA4DAA
Binding #11: p2TrapLogTime *** (octets) 2006-8-25,10:5:8.42
Binding #12: p2TrapLogDateTime *** (octets) Fri, 25 Aug 2006 10:05:08 EDT
Binding #13: p2TrapLogValue *** (octets) N/A
Binding #14: p2TrapLogUnit *** (octets) N/A
Binding #15: p2TrapLogDescr *** (octets) ICIM IP Address has been changed

LoginThreshold
The LoginThreshold trap is sent when a user reaches the number of failed login
attempts via the CLI or ICIM Web Interface as allowed by the login threshold.

252 4021339 Rev B

 Prisma II Traps

Login Threshold Example - Too Many Failed Login Attempts

Specific: 9
Message reception date: 10/30/2006
Message reception time: 1:19:29.216 PM
Time stamp: 2 days 21h:45m:19s.70th
Message type: Trap (v1)
Protocol version: SNMPv1
Transport: IP/UDP
Agent
Address: 172.24.25.175
Port: 1052
Manager
Address: 172.18.10.23
Port: 162
Community: prismatrap
SNMPv1 agent address: 172.24.25.175
Enterprise: p2trapEvents
Bindings (15)
Binding #1: p2TrapLogSequence *** (int32) 19
Binding #2: p2TrapLogSeverity *** (int32) warning(3)
Binding #3: p2TrapLogState *** (int32) event(3)
Binding #4: p2TrapLogLabel *** (octets) LoginThreshold
Binding #5: p2icimStatusMsg.0 *** (int32) 0
Binding #6: p2TrapLogText *** (octets) ICIM2
Binding #7: p2chassisID.1.15 *** (int32) 1
Binding #8: p2slotID.1.15 *** (int32) 15
Binding #9: p2moduleCLLIcode.1.15 *** (octets) Engineering Lab
Binding #10: p2moduleCLEIcode.1.15 *** (octets) ICIMCLEI75
Binding #11: p2TrapLogTime *** (octets) 2006-10-30,13:19:10.91
Binding #12: p2TrapLogDateTime *** (octets) Mon, 30 Oct 2006 13:19:10 EST
Binding #13: p2TrapLogValue *** (octets) N/A
Binding #14: p2TrapLogUnit *** (octets) N/A
Binding #15: p2TrapLogDescr *** (octets) Maximum failed session login
attempts reached

Log Memory Traps

The event log traps LogMemHalfFull or LogMemoryFull are sent when the event log
is nearing capacity. Traps are sent at each of the following intervals.
  80% full
  85% full
  90% full
  95% full
  100% full
When all 5,000 entries in the event log table are filled, the LogMemoryFull trap is
sent. New entries then replace the oldest entries as the information wraps. No
additional LogMemoryFull traps are sent.

4021339 Rev B 253

Chapter 9 SNMP Management

LogMemHalfFull Example
Specific: 9
Message reception date: 9/13/2006
Message reception time: 2:27:25.066 PM
Time stamp: 0 days 00h:11m:20s.13th
Message type: Trap (v1)
Protocol version: SNMPv1
Transport: IP/UDP
Agent
Address: 172.24.28.193
Port: 1035
Manager
Address: 172.18.9.66
Port: 162
Community: prismatrap
SNMPv1 agent address: 172.24.28.193
Enterprise: p2trapEvents
Bindings (15)
Binding #1: p2TrapLogSequence *** (int32) 12
Binding #2: p2TrapLogSeverity *** (int32) warning(3)
Binding #3: p2TrapLogState *** (int32) event(3)
Binding #4: p2TrapLogLabel *** (octets) LogMemHalfFull
Binding #5: p2icimStatusMsg.0 *** (int32) 0
Binding #6: p2TrapLogText *** (octets) ICIM2
Binding #7: p2chassisID.2.15 *** (int32) 2
Binding #8: p2slotID.2.15 *** (int32) 15
Binding #9: p2moduleCLLIcode.2.15 *** (octets) 1.2.243
Binding #10: p2moduleCLEIcode.2.15 *** (octets) (zero-length)
Binding #11: p2TrapLogTime *** (octets) 2006-9-13,1:51:39.42
Binding #12: p2TrapLogDateTime *** (octets) Wed, 13 Sep 2006 01:51:39 EST
Binding #13: p2TrapLogValue *** (octets) N/A
Binding #14: p2TrapLogUnit *** (octets) N/A
Binding #15: p2TrapLogDescr *** (octets) Log memory is %80 full

LogMemoryFull Example
Specific: 9
Message reception date: 9/13/2006
Message reception time: 2:44:27.081 PM
Time stamp: 0 days 00h:28m:22s.13th
Message type: Trap (v1)
Protocol version: SNMPv1
Transport: IP/UDP
Agent
Address: 172.24.28.193
Port: 1039
Manager
Address: 172.18.9.66
Port: 162
Community: prismatrap
SNMPv1 agent address: 172.24.28.193
Enterprise: p2trapEvents
Bindings (15)
Binding #1: p2TrapLogSequence *** (int32) 16
Binding #2: p2TrapLogSeverity *** (int32) warning(3)
Binding #3: p2TrapLogState *** (int32) event(3)
Binding #4: p2TrapLogLabel *** (octets) LogMemoryFull
Binding #5: p2icimStatusMsg.0 *** (int32) 0
Binding #6: p2TrapLogText *** (octets) ICIM2
Binding #7: p2chassisID.2.15 *** (int32) 2
Binding #8: p2slotID.2.15 *** (int32) 15
Binding #9: p2moduleCLLIcode.2.15 *** (octets) 1.2.243
Binding #10: p2moduleCLEIcode.2.15 *** (octets) (zero-length)
Binding #11: p2TrapLogTime *** (octets) 2006-9-13,2:8:41.45
Binding #12: p2TrapLogDateTime *** (octets) Wed, 13 Sep 2006 02:08:41 EST
Binding #13: p2TrapLogValue *** (octets) N/A
Binding #14: p2TrapLogUnit *** (octets) N/A
Binding #15: p2TrapLogDescr *** (octets) Log memory is %100 full

254 4021339 Rev B

 Prisma II Traps

LogWriteError
An Event trap is sent when an attempt to write to the event log fails. This serves as a
backup to alert the management system to a problem writing to the event log.

LogWriteError Example
Specific: 9
Message reception date: 9/13/2006
Message reception time: 2:44:27.081 PM
Time stamp: 0 days 00h:28m:22s.13th
Message type: Trap (v1)
Protocol version: SNMPv1
Transport: IP/UDP
Agent
Address: 172.24.28.193
Port: 1039
Manager
Address: 172.18.9.66
Port: 162
Community: prismatrap
SNMPv1 agent address: 172.24.28.193
Enterprise: p2trapEvents
Bindings (15)
Binding #1: p2TrapLogSequence *** (int32) 16
Binding #2: p2TrapLogSeverity *** (int32) warning(3)
Binding #3: p2TrapLogState *** (int32) event(3)
Binding #4: p2TrapLogLabel *** (octets) LogWriteError
Binding #5: p2icimStatusMsg.0 *** (int32) 0
Binding #6: p2TrapLogText *** (octets) ICIM2
Binding #7: p2chassisID.2.15 *** (int32) 2
Binding #8: p2slotID.2.15 *** (int32) 15
Binding #9: p2moduleCLLIcode.2.15 *** (octets) 1.2.243
Binding #10: p2moduleCLEIcode.2.15 *** (octets) (zero-length)
Binding #11: p2TrapLogTime *** (octets) 2006-9-13,2:8:41.45
Binding #12: p2TrapLogDateTime *** (octets) Wed, 13 Sep 2006 02:08:41 EST
Binding #13: p2TrapLogValue *** (octets) N/A
Binding #14: p2TrapLogUnit *** (octets) N/A
Binding #15: p2TrapLogDescr *** (octets) Log error, can't log message:
Password failed: UserName14

Module Insert
A ModuleInsert trap is sent when an application module is inserted into a chassis in
the ICIM2 or ICM2-XD domain.

4021339 Rev B 255

Chapter 9 SNMP Management

Module Insert Example

Specific: 9
Message reception date: 8/22/2006
Message reception time: 4:54:36.478 PM
Time stamp: 0 days 01h:09m:16s.00th
Message type: Trap (v1)
Protocol version: SNMPv1
Transport: IP/UDP
Agent
Address: 172.2.5.168
Port: 1034
Manager
Address: 172.24.3.151
Port: 162
Community: prismatrap
SNMPv1 agent address: 172.2.5.168
Enterprise: p2trapEvents
Bindings (15)
Binding #1: p2TrapLogSequence *** (int32) 11
Binding #2: p2TrapLogSeverity *** (int32) warning(3)
Binding #3: p2TrapLogState *** (int32) event(3)
Binding #4: p2TrapLogLabel *** (octets) ModuleInsert
Binding #5: p2InsertModuleEntry *** (int32) 0
Binding #6: p2TrapLogText *** (octets) Not available
Binding #7: p2chassisID.0.11 *** (int32) 0
Binding #8: p2slotID.0.11 *** (int32) 11
Binding #9: p2moduleCLLIcode.0.11 *** (octets) SCIATL01
Binding #10: p2moduleCLEIcode.0.11 *** (octets) CLEIcode
Binding #11: p2TrapLogTime *** (octets) 2006-8-22,16:54:36.45
Binding #12: p2TrapLogDateTime *** (octets) Tue, 22 Aug 2006 16:54:36 EST
Binding #13: p2TrapLogValue *** (octets) N/A
Binding #14: p2TrapLogUnit *** (octets) N/A
Binding #15: p2TrapLogDescr *** (octets) A module has been inserted into a
chassis

ModuleRemove
A ModuleRemove trap is sent when an application module is removed from a
chassis in the ICIM2 or ICIM2-XD domain.

256 4021339 Rev B

 Prisma II Traps

Module Remove Example

Specific: 9
Message reception date: 8/22/2006
Message reception time: 4:34:08.853 PM
Time stamp: 0 days 00h:48m:48s.00th
Message type: Trap (v1)
Protocol version: SNMPv1
Transport: IP/UDP
Agent
Address: 172.2.5.168
Port: 1033
Manager
Address: 172.24.3.151
Port: 162
Community: prismatrap
SNMPv1 agent address: 172.2.5.168
Enterprise: p2trapEvents
Bindings (15)
Binding #1: p2TrapLogSequence *** (int32) 10
Binding #2: p2TrapLogSeverity *** (int32) warning(3)
Binding #3: p2TrapLogState *** (int32) event(3)
Binding #4: p2TrapLogLabel *** (octets) ModuleRemove
Binding #5: p2RemoveModuleEntry *** (int32) 0
Binding #6: p2TrapLogText *** (octets) Not available
Binding #7: p2chassisID.0.11 *** (int32) 0
Binding #8: p2slotID.0.11 *** (int32) 11
Binding #9: p2moduleCLLIcode.0.11 *** (octets) SCIATL01
Binding #10: p2moduleCLEIcode.0.11 *** (octets) CLEIcode
Binding #11: p2TrapLogTime *** (octets) 2006-8-22,16:34:8.84
Binding #12: p2TrapLogDateTime *** (octets) Tue, 22 Aug 2006 16:34:08 EST
Binding #13: p2TrapLogValue *** (octets) N/A
Binding #14: p2TrapLogUnit *** (octets) N/A
Binding #15: p2TrapLogDescr *** (octets) A module has been removed from a
chassis

Reboot
The Reboot trap is sent when an ICIM2, ICIM2-XD, or application module has been
commanded to reboot, either individually or as a result of a broadcast reboot
command.

4021339 Rev B 257

Chapter 9 SNMP Management

Reboot Example - Broadcast Reboot Command

Specific: 9
Message reception date: 8/28/2006
Message reception time: 2:20:20.014 PM
Time stamp: 0 days 00h:03m:34s.00th
Message type: Trap (v1)
Protocol version: SNMPv1
Transport: IP/UDP
Agent
Address: 172.2.5.168
Port: 1032
Manager
Address: 172.24.3.151
Port: 162
Community: prismatrap
SNMPv1 agent address: 172.2.5.168
Enterprise: p2trapEvents
Bindings (15)
Binding #1: p2TrapLogSequence *** (int32) 9
Binding #2: p2TrapLogSeverity *** (int32) warning(3)
Binding #3: p2TrapLogState *** (int32) event(3)
Binding #4: p2TrapLogLabel *** (octets) RebootCommand
Binding #5: p2icimStatusMsg *** (int32) 0
Binding #6: p2TrapLogText *** (octets) Broadcast
Binding #7: p2chassisID.99.99 *** (int32) 99
Binding #8: p2slotID.99.99 *** (int32) 99
Binding #9: p2moduleCLLIcode.99.99 *** (octets) N/A
Binding #10: p2moduleCLEIcode.99.99 *** (octets) N/A
Binding #11: p2TrapLogTime *** (octets) 2006-8-28,14:20:20.43
Binding #12: p2TrapLogDateTime *** (octets) Mon, 28 Aug 2006 14:20:20 EST
Binding #13: p2TrapLogValue *** (octets) N/A
Binding #14: p2TrapLogUnit *** (octets) N/A
Binding #15: p2TrapLogDescr *** (octets) An ICIM/module has been commanded
to reboot (CH 99 SL 99 indicates a broadcast reboot)

Reboot Example - Reboot ICIM Command

Specific: 9
Message reception date: 8/22/2006
Message reception time: 3:44:20.455 PM
Time stamp: 0 days 00h:10m:17s.00th
Message type: Trap (v1)
Protocol version: SNMPv1
Transport: IP/UDP
Agent
Address: 172.2.5.168
Port: 1034
Manager
Address: 172.24.3.151
Port: 162
Community: prismatrap
SNMPv1 agent address: 172.2.5.168
Enterprise: p2trapEvents
Bindings (15)
Binding #1: p2TrapLogSequence *** (int32) 11
Binding #2: p2TrapLogSeverity *** (int32) warning(3)
Binding #3: p2TrapLogState *** (int32) event(3)
Binding #4: p2TrapLogLabel *** (octets) RebootCommand
Binding #5: p2icimStatusMsg *** (int32) 0
Binding #6: p2TrapLogText *** (octets) Broadcast
Binding #7: p2chassisID.99.99 *** (int32) 99
Binding #8: p2slotID.99.99 *** (int32) 99
Binding #9: p2moduleCLLIcode.99.99 *** (octets) SCIATL01
Binding #10: p2moduleCLEIcode.99.99 *** (octets) CLEIcode
Binding #11: p2TrapLogTime *** (octets) 2006-8-22,15:44:21.0
Binding #12: p2TrapLogDateTime *** (octets) Tue, 22 Aug 2006 15:44:21 EST
Binding #13: p2TrapLogValue *** (octets) N/A
Binding #14: p2TrapLogUnit *** (octets) N/A
Binding #15: p2TrapLogDescr *** (octets) An ICIM/module has been commanded
to reboot (CH 99 SL 99 indicates a broadcast reboot)

258 4021339 Rev B

 Prisma II Traps

SelfTest
A SelfTest trap is sent when an ICIM2, ICIM2-XD, or application module fails its
power-on self test.

SelfTest Example - ICIM Failure

Specific: 9
Message reception date: 8/25/2006
Message reception time: 9:43:26.623 AM
Time stamp: 0 days 00h:00m:57s.00th
Message type: Trap (v1)
Protocol version: SNMPv1
Transport: IP/UDP
Agent
Address: 172.2.5.168
Port: 1024
Manager
Address: 172.24.3.151
Port: 162
Community: prismatrap
SNMPv1 agent address: 172.2.5.168
Enterprise: p2trapEvents
Bindings (15)
Binding #1: p2TrapLogSequence *** (int32) 1
Binding #2: p2TrapLogSeverity *** (int32) warning(3)
Binding #3: p2TrapLogState *** (int32) event(3)
Binding #4: p2TrapLogLabel *** (octets) SelfTest
Binding #5: p2icimSelfTest *** (int32) 0
Binding #6: p2TrapLogText *** (octets) SelfTest Failed - Error Code 16777232
Binding #7: p2icimChassisID *** (int32) 0
Binding #8: p2icimSlotID *** (int32) 15
Binding #9: p2icimCLLIcode *** (octets) SCIATL01
Binding #10: p2icimCLEIcode *** (octets) VLLUAA4DAA
Binding #11: p2TrapLogTime *** (octets) 2006-8-25,9:45:1.76
Binding #12: p2TrapLogDateTime *** (octets) Fri, 25 Aug 2006 09:45:01 EDT
Binding #13: p2TrapLogValue *** (octets) N/A
Binding #14: p2TrapLogUnit *** (octets) N/A
Binding #15: p2TrapLogDescr *** (octets) An ICIM/module has failed its
power-on self test

4021339 Rev B 259

Chapter 9 SNMP Management

SelfTest Example - Module Failure

Specific: 9
Message reception date: 8/25/2006
Message reception time: 9:49:50.657 AM
Time stamp: 0 days 00h:01m:39s.00th
Message type: Trap (v1)
Protocol version: SNMPv1
Transport: IP/UDP
Agent
Address: 172.2.5.168
Port: 1024
Manager
Address: 172.24.3.151
Port: 162
Community: prismatrap
SNMPv1 agent address: 172.2.5.168
Enterprise: p2trapEvents
Bindings (15)
Binding #1: p2TrapLogSequence *** (int32) 1
Binding #2: p2TrapLogSeverity *** (int32) warning(3)
Binding #3: p2TrapLogState *** (int32) event(3)
Binding #4: p2TrapLogLabel *** (octets) SelfTest
Binding #5: p2moduleSelfTest.0.0 *** (int32) 0
Binding #6: p2TrapLogText *** (octets) SelfTest Failed - Error Code 33558528
Binding #7: p2chassisID.0.0 *** (int32) 0
Binding #8: p2slotID.0.0 *** (int32) 0
Binding #9: p2moduleCLLIcode.0.0 *** (octets) SCIATL01
Binding #10: p2moduleCLEIcode.0.0 *** (octets)CLEIcode
Binding #11: p2TrapLogTime *** (octets) 2006-8-25,9:51:28.17
Binding #12: p2TrapLogDateTime *** (octets) Fri, 25 Aug 2006 09:51:28 EDT
Binding #13: p2TrapLogValue *** (octets) N/A
Binding #14: p2TrapLogUnit *** (octets) N/A
Binding #15: p2TrapLogDescr *** (octets) An ICIM/module has failed its
power-on self test

SNTP
This trap is reserved for future use.

UpdateChassisID
The UpdateChassisID trap is sent to indicate that the ICIM2 or ICIM2-XD is
rediscovering the domain as a result of one of the following actions.
  The p2icimUpdateChassisID is set to 1 via SNMP.
  The CLI command set updateid 1 is issued from the ICIM> command
prompt.

260 4021339 Rev B

 Prisma II Traps

UpdateChassisID Example
Specific: 9
Message reception date: 10/30/2006
Message reception time: 12:39:26.263 PM
Time stamp: 0 days 00h:04m:32s.51th
Message type: Trap (v1)
Protocol version: SNMPv1
Transport: IP/UDP
Agent
Address: 172.24.28.151
Port: 1037
Manager
Address: 172.18.10.23
Port: 162
Community: prismatrap
SNMPv1 agent address: 172.24.28.151
Enterprise: p2trapEvents
Bindings (15)
Binding #1: p2TrapLogSequence *** (int32) 14
Binding #2: p2TrapLogSeverity *** (int32) warning(3)
Binding #3: p2TrapLogState *** (int32) event(3)
Binding #4: p2TrapLogLabel *** (octets) UpdateChassisIDs
Binding #5: p2icimUpdateChassisIDs *** (int32) 0
Binding #6: p2TrapLogText *** (octets) ICIM2
Binding #7: p2chassisID.4.15 *** (int32) 4
Binding #8: p2slotID.4.15 *** (int32) 15
Binding #9: p2moduleCLLIcode.4.15 *** (octets) icimCLLIcode7
Binding #10: p2moduleCLEIcode.4.15 *** (octets) (zero-length)
Binding #11: p2TrapLogTime *** (octets) 2006-10-30,12:40:9.94
Binding #12: p2TrapLogDateTime *** (octets) Mon, 30 Oct 2006 12:40:09 EST
Binding #13: p2TrapLogValue *** (octets) N/A
Binding #14: p2TrapLogUnit *** (octets) N/A
Binding #15: p2TrapLogDescr *** (octets) A user requested update for all
chassis IDs has occurred

UserLockout
The UserLockout trap is sent whenever a user is locked out as a result of reaching
the failed login attempts threshold. The UserLockout event may result in the
following message:
  User <user_name> has reached maximum failed login attempts and been locked
out.

4021339 Rev B 261

Chapter 9 SNMP Management

UserLockout Example
Specific: 9
Message reception date: 3/15/2007
Message reception time: 2:15:02.352 PM
Time stamp: 0 days 00h:21m:11s.61th
Message type: Trap (v1)
Protocol version: SNMPv1
Transport: IP/UDP
Agent
Address: 190.2.0.110
Port: 1056
Manager
Address: 190.2.0.108
Port: 162
Community: prismatrap
SNMPv1 agent address: 190.2.0.114
Enterprise: p2trapEvents
Bindings (15)
Binding #1: p2TrapLogSequence *** (int32) 32
Binding #2: p2TrapLogSeverity *** (int32) warning(3)
Binding #3: p2TrapLogState *** (int32) event(3)
Binding #4: p2TrapLogLabel *** (octets) UserLockout
Binding #5: p2icimStatusMsg *** (int32) 0
Binding #6: p2TrapLogText *** (octets) ICIM2
Binding #7: p2chassisID.3.15 *** (int32) 3
Binding #8: p2slotID.3.15 *** (int32) 15
Binding #9: p2moduleCLLIcode.3.15 *** (octets) ICIMCLLI
Binding #10: p2moduleCLEIcode.3.15 *** (octets) VLLUAA4DAA
Binding #11: p2TrapLogTime *** (octets) 2007-3-15,14:15:1.84
Binding #12: p2TrapLogDateTime *** (octets) Thu, 15 Mar 2007 14:15:01 EDT
Binding #13: p2TrapLogValue *** (octets) N/A
Binding #14: p2TrapLogUnit *** (octets) N/A
Binding #15: p2TrapLogDescr *** (octets) User ferret3 has reached maximum
failed login attempts and been locked out.

262 4021339 Rev B

 Delay in the Discovery Process

Delay in the Discovery Process

Depending on when an event occurs in relation to the ICIM2 or ICIM2-XD polling
cycle, a user may notice delays in the discovery process. Such delays may be
experienced when inserting or removing a module.
For example, if a module is removed immediately after being polled, it may be
several seconds before the ICIM2 or ICIM2-XD detects the empty chassis slot. After
detecting it, and assuming that a trap destination is configured, the ICIM2 or ICIM2-
XD will send a trap indicating module removal.
On the other hand, if the ICIM2 or ICIM2-XD is managing a large number of
modules, the polling cycle could be long enough that a module could be removed
and reinserted without being missed. In this case, the ICIM2 or ICIM2-XD would not
send traps indicating module removal and reinsertion.

4021339 Rev B 263

Chapter 9 SNMP Management

Alarm Threshold Modification

The meaning of an alarm value depends on the type of alarm. For example, a
p2almValue of 0 (zero) indicates OK for a Boolean alarm type (p2almType = 5 or 6),
but signals a Major Low alarm for a Non-Boolean alarm type (p2almType = 1, 2, 3, 4,
7 or 8). For more information, see Module Alarm Table (on page 207).
The following example illustrates how an alarm threshold may be set, and the
subsequent behavior that results from violating the alarm threshold. This behavior
includes a module going into an alarm state and a trap being sent.
1 First, observe that the actual value of the +24 V rail voltage from DC-to-DC
converter B is 24.0095 V, as found in the p2moduleMonitorTable shown below.

2 Next, moving to the Module Alarm table, we change the minor low limit from
18.4 to 24.9, as shown below.

264 4021339 Rev B

 Alarm Threshold Modification

3 Because the actual value (24.0095) of the +24 V rail converter B is less than the
Minor Low limit of 24.9, an Enhanced trap for a Minor alarm is sent. A copy of
the trap is kept in the Trap Logging table, as shown below.

4 Now, we change the minor low limit back to 18.4 in the Module Alarm table, as
shown below.

When we do this, an Enhanced trap for a Minor clear is generated, and a copy of
the trap is kept in the Trap Logging table.

5 Finally, returning to the Module Alarm table, we note that the alarm value has
changed from 1 (Minor Low) to 2 (OK).

4021339 Rev B 265

Chapter 9 SNMP Management

System Behavior
ICIM as Proxy for Module Information
The user gains access to information about modules in the ICIM2 or ICIM2-XD
domain through the ICIM via SNMP and the MIBs. A virtual database in the ICIM2
or ICIM2-XD keeps track of data supplied by each module. The ICIM periodically
refreshes this database to ensure that the information it provides is up-to-date.
In this way, all module information obtained via SNMP is proxied through the
ICIM2 or ICIM2-XD. Because the modules never interface directly with SNMP, this
proxy behavior differs from that of SNMP Proxy Agents, and the two methods
should not be confused with each other.

Module Removal and Enhanced Traps

If a module is removed, an Enhanced trap is sent. No other traps indicating alarms
or clearings are sent for that module. Once again, because of the delay in the
discovery process, it may be possible to remove and reinsert a module without traps
being sent.

266 4021339 Rev B

 Frequently Asked Questions

Frequently Asked Questions

How do I configure trap destination?
Trap destination is set up via an entry into the p2TrapRecvTable. Select an index
(choices are 0 through 9) that is not currently used for trap destination.
Note: Some element management systems access and populate the first two entries
(0 and 1), making them unavailable for user configuration.
1 Set p2TrapRecvEnable to enabled (2).
2 Set p2TrapRecvAddr to the IP address of the remote entity, in the format
172.0.0.1.
3 Set p2TrapRecvTelcoAlarm to enabled (2).

Note: Enable the row, or traps will not be sent.

For additional information, see To Configure Trap Destination (on page 229), Trap
Types (on page 229), and Trap Recv Table (on page 188).

Why do the same alarm values represent different conditions?

For example, why does an alarm value of zero sometimes mean "OK," and other
times indicate a state of alarm? The answer is that the alarm value and the alarm
type are inseparably linked, with the meaning of the alarm value inherently
connected with the type of alarm.
For example:
  A zero in p2almValue indicates that all is fine for a Boolean (p2almType 5 or 6).
  A zero in p2almValue indicates a major low alarm for a Non-Boolean
(p2almType 1, 2, 3, 4, 7 or 8).
For additional information, see the sections on alarms in Module Alarm Table (on
page 207).

4021339 Rev B 267

Chapter 9 SNMP Management

How do Enhanced Traps differ from other trap types?

The Enhanced traps contain additional information in the bindings that is not
included in the original proprietary traps.
All proprietary traps are represented with the Enhanced traps. If Enhanced traps are
enabled and if the row in the p2TrapRecvTable is enabled, all traps will be sent to
the IP address set in that particular row.
All trap settings are documented for completeness only. Information contained in
other proprietary traps is expanded upon in the Enhanced traps. Use of the older
traps is not recommended, as the new Enhanced trap is more useful. Enabling other
traps together with the Enhanced trap will cause two traps to be sent for each event.
For more information, see Prisma II Traps (on page 226), Trap Types (on page 229),
and Enhanced Trap Binding Information (on page 239).

When do traps associated with module insertion, removal, and alarms occur?
If modules are in a state of alarm, traps are generated at module insertion, module
startup, chassis startup, or ICIM2 or ICIM2-XD startup. If p2TrapRecvTable is not
configured with IP addresses, rows enabled, and Enhanced traps enabled, no traps
are sent for alarms detected at startup.
If a module is inserted after a steady-state condition is reached, a trap is generated
when the ICIM2 or ICIM2-XD recognizes the insertion event. This fact is recorded in
p2InsertModuleTable. Also, if the module is in a state of alarm, this will be indicated
with startup traps. For additional information, see System Behavior (on page 266).
Upon removal of a module, and once the ICIM2 or ICIM2-XD detects the change, a
trap is generated. Module removal is detected by continued lack of response to
internal ICIM2 or ICIM2-XD polling of the module, so it may take several polling
cycles to discover that the module was removed. However, no traps will be sent to
clear the alarms.
After a module is removed, the ICIM2 or ICIM2-XD keeps no further information on
the module except what appears in p2RemoveModuleTable.
After the modules are discovered by the ICIM2 or ICIM2-XD and initial alarms are
acknowledged by traps, subsequent alarm traps are edge-triggered. Thus, alarm
traps are generated upon module startup, and if there is a change in the state of an
alarm following initial discovery.
Tip: Enable the row, set the IP address, and enable Enhanced traps, or startup alarm
traps will not be sent or logged.

268 4021339 Rev B

 Frequently Asked Questions

Where can I find trap definitions?

Because trap bindings are defined in the code, we have added comments describing
Enhanced traps in the SCIATL-PRISMAII-ICIM-MIB. The current document also
describes the behavior of all proprietary traps and the bindings associated with each
trap.

What is the Trap Logging Table?

If trap destination is configured and enabled for Enhanced traps, the Trap Logging
table maintains a listing of Enhanced traps sent. Each entry in the table contains all
of the bindings of the original trap. The table serves as a backup in the event of
network connectivity failure.
The Trap Logging table holds up to 1,000 entries. When the table gets full, each new
entry causes the oldest one to age out of the listing, leaving the most recent 1,000
entries.
The figure below illustrates the Trap Logging table with several entries.

For additional information, see Prisma II Traps (on page 226), Trap Logging Table
(on page 193), and Enhanced Trap Binding Information (on page 239).

4021339 Rev B 269

 10 Chapter
10
Maintenance and
Troubleshooting
Introduction
This chapter provides information to assist you in maintaining and
troubleshooting the platform.

Qualified Personnel
Only appropriately qualified and skilled personnel should attempt to
maintain or troubleshoot chassis faults.
WARNING:
Allow only qualified and skilled personnel to install, operate,
maintain, and service these products. Otherwise, personal injury or
equipment damage may occur.

4021339 Rev B 271

Chapter 10 Maintenance and Troubleshooting

In This Chapter
ƒ Maintenance ........................................................................................ 273
ƒ Troubleshooting .................................................................................. 274
ƒ Fan Ok Alarms .................................................................................... 276
ƒ ChasTemp Alarm................................................................................ 277
ƒ ConvAIn Alarm................................................................................... 278
ƒ ConvA+24 Alarm................................................................................ 279
ƒ ConvA+5 Alarm.................................................................................. 281
ƒ ConvA-5 Alarm................................................................................... 283
ƒ ConvBIn Alarm ................................................................................... 285
ƒ ConvB+24 Alarm ................................................................................ 286
ƒ ConvB+5 Alarm .................................................................................. 288
ƒ ConvB-5 Alarm.................................................................................... 290
ƒ Cleaning Optical Connectors ............................................................ 292
ƒ Connecting Optical Cables ................................................................ 296

272 4021339 Rev B

 Maintenance

Maintenance
The following maintenance is recommended to ensure optimal performance.

Frequency Maintenance Required

Yearly ƒ Check all parameters and test points.

ƒ Record data.

ƒ Make adjustments as needed.

ƒ Make sure all cables are mated properly.

ƒ Inspect cables for stress and chafing.

ƒ Make sure all retaining screws are tight.

ƒ Replace chassis air filter. Depending on office environment

cleanliness/filtration, the chassis air filter may require more
frequent servicing.
When needed Carefully clean the module with a soft cloth that is dampened with
mild detergent.

Maintenance Record
It may be helpful to establish a maintenance record or log for this equipment. You
may want to record laser power level, laser temperature readings, laser bias current,
or power supply voltages, as well as the filter change dates.
Large variations in any of the parameters above should be investigated prior to
failure.

4021339 Rev B 273

Chapter 10 Maintenance and Troubleshooting

Troubleshooting
This section provides general information on servicing and troubleshooting this
equipment. The troubleshooting information describes the most common alarms and
gives typical symptoms, causes, and items to check before contacting Customer
Service.

Chassis Troubleshooting
The main function of the chassis is to distribute power and establish communication
links for the application modules installed in the chassis. Most troubleshooting
involves the modules installed in the chassis, but in some instances, you will need to
troubleshoot the chassis itself.
The table below describes the most common problems and gives typical symptoms,
possible causes, and items to check before contacting Customer Service.
WARNING:
Avoid electric shock and damage to this product! Do not open the enclosure of
this product. There are no user-serviceable parts inside. Refer servicing to
qualified service personnel.

Symptom Possible Causes Solutions

ON indicator is not Power supply connection loose Check that all power supply
illuminated connections are secure.
Loss of system power Check that power is present
at receptacle.
Power failure; backup in use Check other displays and
indicators for power
indication.
Module indicator burned out Contact Customer Service for
an indicator replacement.
ALARM indicator is on or Application module in alarm Consult EMS for module
flashing alarms (see module
documentation for details).
Chassis failed power-up self- Check that all power supply
test connections are secure.
Check AC OK and DC OK
LED indicators on power
supplies.

274 4021339 Rev B

 Troubleshooting

ICIM indicator is off ICIM not installed or not fully Confirm that chassis is part of
seated an ICIM daisy chain (no need
for separate ICIM).
If not, check that the ICIM is
fully seated in back of chassis.

Alarm Troubleshooting
The Prisma II XD Platform generates certain alarms that are specific to the chassis, its
fan assembly, and its power supply components.

Parameter Function
Fan 1_Ok Fan 1 operating status
Fan 2_Ok Fan 2 operating status
Fan 3_Ok Fan 3 operating status
ChasTemp Chassis internal temperature
ConvAIn DC-to-DC converter A -48 VDC input
ConvA+24 DC-to-DC converter A +24 VDC output
ConvA+5 DC-to-DC converter A +5 VDC output
ConvA-5 DC-to-DC converter A -5 VDC output
ConvBIn DC-to-DC converter B-48 VDC input
ConvB+24 DC-to-DC converter B +24 VDC output
ConvB+5 DC-to-DC converter B +5 VDC output
ConvB-5 DC-to-DC converter B -5 VDC output

Troubleshooting information for each of these alarms is provided in the following

sections of this chapter.
Other alarms may occur as a result of fault conditions in specific application
modules. For information on troubleshooting alarms for specific application
modules, see the appropriate module documentation. For a list of these documents
and their part numbers, see Related Publications (on page 33).

Additional Assistance
If you need additional assistance, telephone one of our Technical Service Centers or
your local sales subsidiary. The chapter Customer Support Information (on page
297) contains a list of telephone numbers.

4021339 Rev B 275

Chapter 10 Maintenance and Troubleshooting

Fan Ok Alarms
The Fan Ok alarms (Fan 1_Ok, Fan 2_Ok, Fan 3_Ok) indicate a problem with the
function of the three fans in the fan assembly. Each alarm triggers when its
corresponding fan is inoperative, whether due to failure of the fan itself or to a
disconnected or broken wiring harness.

Fan Alarm Parameters

Alarm Function Major Minor Minor Major Hysteresis Typical
Low Low High High Range/
Threshold Threshold Threshold Threshold Nom.
Value
Fan 1_Ok Fan 1 status na na na na na OK or
Fault
Fan 2_Ok Fan 2 status na na na na na OK or
Fault
Fan 3_Ok Fan 3 status na na na na na OK or
Fault

Suggested Actions
1 Check for obstruction causing lack of rotation on fan in alarm. If present, rectify
condition.
2 If no obstruction, remove fan assembly and check for breaks in fan wiring or
loose connectors.
3 If all fan wiring is intact and one or more fans do not rotate, replace fan
assembly.

CAUTION:
For a chassis under power, field replacement of the fans, AC-to-DC bulk
power supply modules, or DC-to-DC converter assemblies must be completed
in two minutes or less to prevent possible chassis overheating due to
temporary removal of the fan assembly.

4 If these steps do not clear the alarm, contact Customer Service for assistance.

276 4021339 Rev B

 ChasTemp Alarm

ChasTemp Alarm
This alarm indicates a problem with fan temperature. It triggers when the chassis
internal temperature is outside the threshold levels.

ChasTemp Alarm Parameters

Alarm Function Major Minor Minor Major Hysteresis Typical
Low Low High High Range/
Threshold Threshold Threshold Threshold Nom.
Value
ChasTemp chassis -40°C -35°C 60°C 65°C 1°C -40°C to
internal 65°C
temperature

The factory default range for ChasTemp is -40°C to 65°C. While these values can be
user-adjustable, they must be left at the default values. Failure to do so may result in
improper operation or alarming, or may lead to equipment damage.

Suggested Actions
1 Verify that the conditioned ambient airflow is within chassis temperature alarm
threshold set-points. If not, rectify the condition.
2 Look for and remove any air flow obstructions at the chassis air intake and
exhaust areas. Momentary fan assembly removal may be needed for this
inspection.

CAUTION:
For a chassis under power, field replacement of the fans, AC-to-DC bulk
power supply modules, or DC-to-DC converter assemblies must be completed
in two minutes or less to prevent possible chassis overheating due to
temporary removal of the fan assembly.

3 If these steps do not clear the alarm, contact Customer Service for assistance.

4021339 Rev B 277

Chapter 10 Maintenance and Troubleshooting

ConvAIn Alarm
This alarm indicates one or more of the following conditions:
  Absence of AC input power to the AC-to-DC bulk power supply module in slot
A, if present
  Absence of DC input power to the DC-to-DC converter module for power supply
slot A
  Absence of DC-to-DC converter module for power supply slot A
Note: This alarm can be temporarily disabled for servicing by setting the AlmMuteA
control parameter to 1 (ON) via the CLI or ICIM Web Interface. See the Prisma II
Platform Remote User Interface Guide, part number 4012441 for details.

ConvAIn Alarm Parameters

Alarm Function Major Minor Minor Major Hysteresis Typical
Low Low High High Range/
Threshold Threshold Threshold Threshold Nom.
Value
ConvAIn Slot A na na na na na OK or
power Fault
status

Suggested Actions
1 Check the chassis power cord and confirm that the alarming AC-to-DC bulk
power supply module is fully seated.
2 If the line voltage is feeding only the alarming power supply, check the line for
both proper voltage and polarity. If the line voltage and polarity are acceptable,
replace the power supply module.
3 If the line voltage is feeding more than one chassis with no indication of alarm on
any other power supply, replace the alarming power supply module.
4 If these steps do not clear the alarm, contact Customer Service for assistance.

278 4021339 Rev B

 ConvA+24 Alarm

ConvA+24 Alarm
This alarm indicates the status of the +24 VDC output voltage from the DC-to-DC
converter in slot A of the chassis. It triggers when this output voltage is outside the
threshold levels.

ConvA+24 Alarm Parameters

Alarm Function Major Minor Minor Major Hysteresis Typical
Low Low High High Range/
Threshold Threshold Threshold Threshold Nom.
Value
ConvA+24 DC-to-DC 18.0 V DC 18.4 V DC 25.9 V DC 26.1 V DC 0.1 V DC 23.8 to
Converter 25.6 V
Slot A DC
+24 VDC
output
voltage

While the threshold values can be user-adjustable, they must be left at the default
values. Failure to do so may result in improper operation or alarming, or may lead to
equipment damage.

Suggested Actions
1 Access the DC-to-DC converter in alarm as described below, and confirm that it
is fully seated. If necessary, reseat the converter.
2 Check that the status LED of the converter in alarm is unlit. If the LED is lit,
replace the converter.
3 Confirm that the alarm is caused by the voltage exceeding or falling below
factory-set threshold values. If so, replace the converter.
4 If these steps do not clear the alarm, contact Customer Service for assistance.

To Access the DC-to-DC Converter

Complete the following steps to access the DC-to-DC converter for inspection or
replacement.

4021339 Rev B 279

Chapter 10 Maintenance and Troubleshooting

CAUTION:

ƒ Before removing an AC-to-DC bulk power supply module from the chassis, disable
AC input power to the module by disconnecting the associated AC power cord.

ƒ Before removing a DC-to-DC converter assembly from the chassis, disable DC input
power to the converter assembly by disconnecting the associated AC power cord (if
AC operated) or DC power-passing cable (if DC operated).

ƒ Do not disable power to both sides of the chassis at the same time when such action
may cause a loss of service.

CAUTION:
For a chassis under power, field replacement of the fans, AC-to-DC bulk
power supply modules, or DC-to-DC converter assemblies must be completed
in two minutes or less to prevent possible chassis overheating due to
temporary removal of the fan assembly.
1 Using the CLI or ICIM Web Interface, temporarily set AlmMuteA or AlmMuteB
to 1 (ON) to mute any alarms from the power supply section to be serviced. See
the Prisma II Platform Remote User Interface Guide, part number 4012441 for details.
2 Temporarily disconnect AC or DC power from the power supply section being
serviced.
3 Remove the fan assembly from the chassis and set it aside.
4 Locate the DC-to-DC converter assemblies mounted horizontally on a ledge
inside the fan assembly opening. The converter on the left side is for power
supply section A, while the converter on the right is for power supply section B.
5 To remove a DC-to-DC converter, grasp both edges and pull gently until the
converter board disengages from the midplane bus. Then slide the converter
board out of the chassis.
6 To reinsert a DC-to-DC converter, slide the converter board into the chassis until
it rests against with the connector on the midplane bus. Then push the converter
firmly into the midplane connector.
7 Reinstall the fan assembly.
8 Reconnect AC or DC power to the power supply section being serviced.
9 Set AlmMuteA or AlmMuteB to 0 (OFF) to enable alarms from the power supply
section.

280 4021339 Rev B

 ConvA+5 Alarm

ConvA+5 Alarm
This alarm indicates the status of the +5 VDC output voltage from the DC-to-DC
converter in slot A of the chassis. It triggers when this output voltage is outside the
threshold levels.

ConvA+5 Alarm Parameters

Alarm Function Major Minor Minor Major Hysteresis Typical
Low Low High High Range/
Threshold Threshold Threshold Threshold Nom.
Value
ConvA+5 DC-to-DC 3.6 V DC 3.7 V DC 5.9 V DC 6.1 V DC 0.1 V DC 4.9 to
Converter 5.3 V
Slot A DC
+5 VDC
output
voltage

While the threshold values can be user-adjustable, they must be left at the default
values. Failure to do so may result in improper operation or alarming, or may lead to
equipment damage.

Suggested Actions
1 Access the DC-to-DC converter in alarm as described below, and confirm that it
is fully seated. If necessary, reseat the converter.
2 Check that the status LED of the converter in alarm is unlit. If the LED is lit,
replace the converter.
3 Confirm that the alarm is caused by the voltage exceeding or falling below
factory-set threshold values. If so, replace the converter.
4 If these steps do not clear the alarm, contact Customer Service for assistance.

To Access the DC-to-DC Converter

Complete the following steps to access the DC-to-DC converter for inspection or
replacement.

4021339 Rev B 281

Chapter 10 Maintenance and Troubleshooting

CAUTION:

ƒ Before removing an AC-to-DC bulk power supply module from the chassis, disable
AC input power to the module by disconnecting the associated AC power cord.

ƒ Before removing a DC-to-DC converter assembly from the chassis, disable DC input
power to the converter assembly by disconnecting the associated AC power cord (if
AC operated) or DC power-passing cable (if DC operated).

ƒ Do not disable power to both sides of the chassis at the same time when such action
may cause a loss of service.

CAUTION:
For a chassis under power, field replacement of the fans, AC-to-DC bulk
power supply modules, or DC-to-DC converter assemblies must be completed
in two minutes or less to prevent possible chassis overheating due to
temporary removal of the fan assembly.
1 Using the CLI or ICIM Web Interface, temporarily set AlmMuteA or AlmMuteB
to 1 (ON) to mute any alarms from the power supply section to be serviced. See
the Prisma II Platform Remote User Interface Guide, part number 4012441 for details.
2 Temporarily disconnect AC or DC power from the power supply section being
serviced.
3 Remove the fan assembly from the chassis and set it aside.
4 Locate the DC-to-DC converter assemblies mounted horizontally on a ledge
inside the fan assembly opening. The converter on the left side is for power
supply section A, while the converter on the right is for power supply section B.
5 To remove a DC-to-DC converter, grasp both edges and pull gently until the
converter board disengages from the midplane bus. Then slide the converter
board out of the chassis.
6 To reinsert a DC-to-DC converter, slide the converter board into the chassis until
it rests against with the connector on the midplane bus. Then push the converter
firmly into the midplane connector.
7 Reinstall the fan assembly.
8 Reconnect AC or DC power to the power supply section being serviced.
9 Set AlmMuteA or AlmMuteB to 0 (OFF) to enable alarms from the power supply
section.

282 4021339 Rev B

 ConvA-5 Alarm

ConvA-5 Alarm
This alarm indicates the status of the -5 VDC output voltage from the DC-to-DC
converter in slot A of the chassis. It triggers when this output voltage is outside the
threshold levels.

ConvA-5 Alarm Parameters

Alarm Function Major Minor Minor Major Hysteresis Typical
Low Low High High Range/
Threshold Threshold Threshold Threshold Nom.
Value
ConvA-5 DC-to-DC -5.6 V DC -5.5 V DC -4.6 V DC -4.5 V DC 0.1 V DC -5.3 to
Converter -4.9 V
Slot A DC
-5 VDC
output
voltage

While the threshold values can be user-adjustable, they must be left at the default
values. Failure to do so may result in improper operation or alarming, or may lead to
equipment damage.

Suggested Actions
1 Access the DC-to-DC converter in alarm as described below, and confirm that it
is fully seated. If necessary, reseat the converter.
2 Check that the status LED of the converter in alarm is unlit. If the LED is lit,
replace the converter.
3 Confirm that the alarm is caused by the voltage exceeding or falling below
factory-set threshold values. If so, replace the converter.
4 If these steps do not clear the alarm, contact Customer Service for assistance.

To Access the DC-to-DC Converter

Complete the following steps to access the DC-to-DC converter for inspection or
replacement.

4021339 Rev B 283

Chapter 10 Maintenance and Troubleshooting

CAUTION:

ƒ Before removing an AC-to-DC bulk power supply module from the chassis, disable
AC input power to the module by disconnecting the associated AC power cord.

ƒ Before removing a DC-to-DC converter assembly from the chassis, disable DC input
power to the converter assembly by disconnecting the associated AC power cord (if
AC operated) or DC power-passing cable (if DC operated).

ƒ Do not disable power to both sides of the chassis at the same time when such action
may cause a loss of service.

CAUTION:
For a chassis under power, field replacement of the fans, AC-to-DC bulk
power supply modules, or DC-to-DC converter assemblies must be completed
in two minutes or less to prevent possible chassis overheating due to
temporary removal of the fan assembly.
1 Using the CLI or ICIM Web Interface, temporarily set AlmMuteA or AlmMuteB
to 1 (ON) to mute any alarms from the power supply section to be serviced. See
the Prisma II Platform Remote User Interface Guide, part number 4012441 for details.
2 Temporarily disconnect AC or DC power from the power supply section being
serviced.
3 Remove the fan assembly from the chassis and set it aside.
4 Locate the DC-to-DC converter assemblies mounted horizontally on a ledge
inside the fan assembly opening. The converter on the left side is for power
supply section A, while the converter on the right is for power supply section B.
5 To remove a DC-to-DC converter, grasp both edges and pull gently until the
converter board disengages from the midplane bus. Then slide the converter
board out of the chassis.
6 To reinsert a DC-to-DC converter, slide the converter board into the chassis until
it rests against with the connector on the midplane bus. Then push the converter
firmly into the midplane connector.
7 Reinstall the fan assembly.
8 Reconnect AC or DC power to the power supply section being serviced.
9 Set AlmMuteA or AlmMuteB to 0 (OFF) to enable alarms from the power supply
section.

284 4021339 Rev B

 ConvBIn Alarm

ConvBIn Alarm
This alarm indicates one or more of the following conditions:
  Absence of AC input power to the AC-to-DC bulk power supply module in slot
B, if present
  Absence of DC input power to the DC-to-DC converter module for power supply
slot B
  Absence of DC-to-DC converter module for power supply slot B
Note: This alarm can be temporarily disabled for servicing by setting the AlmMuteB
control parameter to 1 (ON) via the CLI or ICIM Web Interface. See the Prisma II
Platform Remote User Interface Guide, part number 4012441 for details.

ConvBIn Alarm Parameters

Alarm Function Major Minor Minor Major Hysteresis Typical
Low Low High High Range/
Threshold Threshold Threshold Threshold Nom.
Value
ConvBIn Slot B na na na na na OK or
power Fault
status

Suggested Actions
1 Check the chassis power cord and confirm that the alarming AC-to-DC bulk
power supply module is fully seated.
2 If the line voltage is feeding only the alarming power supply, check the line for
both proper voltage and polarity. If the line voltage and polarity are acceptable,
replace the power supply module.
3 If the line voltage is feeding more than one chassis with no indication of alarm on
any other power supply, replace the alarming power supply module.
4 If these steps do not clear the alarm, contact Customer Service for assistance.

4021339 Rev B 285

Chapter 10 Maintenance and Troubleshooting

ConvB+24 Alarm
This alarm indicates the status of the +24 VDC output voltage from the DC-to-DC
converter in slot B of the chassis. It triggers when this output voltage is outside the
threshold levels.

ConvB+24 Alarm Parameters

Alarm Function Major Minor Minor Major Hysteresis Typical
Low Low High High Range/
Threshold Threshold Threshold Threshold Nom.
Value
ConvB+24 DC-to-DC 18.0 V DC 18.4 V DC 25.9 V DC 26.1 V DC 0.1 V DC 23.8 to
Converter 25.6 V
Slot B DC
+24 VDC
output
voltage

While the threshold values can be user-adjustable, they must be left at the default
values. Failure to do so may result in improper operation or alarming, or may lead to
equipment damage.

Suggested Actions
1 Access the DC-to-DC converter in alarm as described below, and confirm that it
is fully seated. If necessary, reseat the converter.
2 Check that the status LED of the converter in alarm is unlit. If the LED is lit,
replace the converter.
3 Confirm that the alarm is caused by the voltage exceeding or falling below
factory-set threshold values. If so, replace the converter.
4 If these steps do not clear the alarm, contact Customer Service for assistance.

To Access the DC-to-DC Converter

Complete the following steps to access the DC-to-DC converter for inspection or
replacement.

286 4021339 Rev B

 ConvB+24 Alarm

CAUTION:

ƒ Before removing an AC-to-DC bulk power supply module from the chassis, disable
AC input power to the module by disconnecting the associated AC power cord.

ƒ Before removing a DC-to-DC converter assembly from the chassis, disable DC input
power to the converter assembly by disconnecting the associated AC power cord (if
AC operated) or DC power-passing cable (if DC operated).

ƒ Do not disable power to both sides of the chassis at the same time when such action
may cause a loss of service.

CAUTION:
For a chassis under power, field replacement of the fans, AC-to-DC bulk
power supply modules, or DC-to-DC converter assemblies must be completed
in two minutes or less to prevent possible chassis overheating due to
temporary removal of the fan assembly.
1 Using the CLI or ICIM Web Interface, temporarily set AlmMuteA or AlmMuteB
to 1 (ON) to mute any alarms from the power supply section to be serviced. See
the Prisma II Platform Remote User Interface Guide, part number 4012441 for details.
2 Temporarily disconnect AC or DC power from the power supply section being
serviced.
3 Remove the fan assembly from the chassis and set it aside.
4 Locate the DC-to-DC converter assemblies mounted horizontally on a ledge
inside the fan assembly opening. The converter on the left side is for power
supply section A, while the converter on the right is for power supply section B.
5 To remove a DC-to-DC converter, grasp both edges and pull gently until the
converter board disengages from the midplane bus. Then slide the converter
board out of the chassis.
6 To reinsert a DC-to-DC converter, slide the converter board into the chassis until
it rests against with the connector on the midplane bus. Then push the converter
firmly into the midplane connector.
7 Reinstall the fan assembly.
8 Reconnect AC or DC power to the power supply section being serviced.
9 Set AlmMuteA or AlmMuteB to 0 (OFF) to enable alarms from the power supply
section.

4021339 Rev B 287

Chapter 10 Maintenance and Troubleshooting

ConvB+5 Alarm
This alarm indicates the status of the +5 VDC output voltage from the DC-to-DC
converter in slot B of the chassis. It triggers when this output voltage is outside the
threshold levels.

ConvB+5 Alarm Parameters

Alarm Function Major Minor Minor Major Hysteresis Typical
Low Low High High Range/
Threshold Threshold Threshold Threshold Nom.
Value
ConvB+5 DC-to-DC 3.6 V DC 3.7 V DC 5.9 V DC 6.1 V DC 0.1 V DC 4.9 to
Converter 5.3 V
Slot B DC
+5 VDC
output
voltage

While the threshold values can be user-adjustable, they must be left at the default
values. Failure to do so may result in improper operation or alarming, or may lead to
equipment damage.

Suggested Actions
1 Access the DC-to-DC converter in alarm as described below, and confirm that it
is fully seated. If necessary, reseat the converter.
2 Check that the status LED of the converter in alarm is unlit. If the LED is lit,
replace the converter.
3 Confirm that the alarm is caused by the voltage exceeding or falling below
factory-set threshold values. If so, replace the converter.
4 If these steps do not clear the alarm, contact Customer Service for assistance.

To Access the DC-to-DC Converter

Complete the following steps to access the DC-to-DC converter for inspection or
replacement.

288 4021339 Rev B

 ConvB+5 Alarm

CAUTION:

ƒ Before removing an AC-to-DC bulk power supply module from the chassis, disable
AC input power to the module by disconnecting the associated AC power cord.

ƒ Before removing a DC-to-DC converter assembly from the chassis, disable DC input
power to the converter assembly by disconnecting the associated AC power cord (if
AC operated) or DC power-passing cable (if DC operated).

ƒ Do not disable power to both sides of the chassis at the same time when such action
may cause a loss of service.

CAUTION:
For a chassis under power, field replacement of the fans, AC-to-DC bulk
power supply modules, or DC-to-DC converter assemblies must be completed
in two minutes or less to prevent possible chassis overheating due to
temporary removal of the fan assembly.
1 Using the CLI or ICIM Web Interface, temporarily set AlmMuteA or AlmMuteB
to 1 (ON) to mute any alarms from the power supply section to be serviced. See
the Prisma II Platform Remote User Interface Guide, part number 4012441 for details.
2 Temporarily disconnect AC or DC power from the power supply section being
serviced.
3 Remove the fan assembly from the chassis and set it aside.
4 Locate the DC-to-DC converter assemblies mounted horizontally on a ledge
inside the fan assembly opening. The converter on the left side is for power
supply section A, while the converter on the right is for power supply section B.
5 To remove a DC-to-DC converter, grasp both edges and pull gently until the
converter board disengages from the midplane bus. Then slide the converter
board out of the chassis.
6 To reinsert a DC-to-DC converter, slide the converter board into the chassis until
it rests against with the connector on the midplane bus. Then push the converter
firmly into the midplane connector.
7 Reinstall the fan assembly.
8 Reconnect AC or DC power to the power supply section being serviced.
9 Set AlmMuteA or AlmMuteB to 0 (OFF) to enable alarms from the power supply
section.

4021339 Rev B 289

Chapter 10 Maintenance and Troubleshooting

ConvB-5 Alarm
This alarm indicates the status of the -5 VDC output voltage from the DC-to-DC
converter in slot B of the chassis. It triggers when this output voltage is outside the
threshold levels.

ConvB-5 Alarm Parameters

Alarm Function Major Minor Minor Major Hysteresis Typical
Low Low High High Range/
Threshold Threshold Threshold Threshold Nom.
Value
ConvB-5 DC-to-DC -5.6 V DC -5.5 V DC -4.6 V DC -4.5 V DC 0.1 V DC -5.3 to
Converter -4.9 V
Slot B DC
-5 VDC
output
voltage

While the threshold values can be user-adjustable, they must be left at the default
values. Failure to do so may result in improper operation or alarming, or may lead to
equipment damage.

Suggested Actions
1 Access the DC-to-DC converter in alarm as described below, and confirm that it
is fully seated. If necessary, reseat the converter.
2 Check that the status LED of the converter in alarm is unlit. If the LED is lit,
replace the converter.
3 Confirm that the alarm is caused by the voltage exceeding or falling below
factory-set threshold values. If so, replace the converter.
4 If these steps do not clear the alarm, contact Customer Service for assistance.

To Access the DC-to-DC Converter

Complete the following steps to access the DC-to-DC converter for inspection or
replacement.

290 4021339 Rev B

 ConvB-5 Alarm

CAUTION:

ƒ Before removing an AC-to-DC bulk power supply module from the chassis, disable
AC input power to the module by disconnecting the associated AC power cord.

ƒ Before removing a DC-to-DC converter assembly from the chassis, disable DC input
power to the converter assembly by disconnecting the associated AC power cord (if
AC operated) or DC power-passing cable (if DC operated).

ƒ Do not disable power to both sides of the chassis at the same time when such action
may cause a loss of service.

CAUTION:
For a chassis under power, field replacement of the fans, AC-to-DC bulk
power supply modules, or DC-to-DC converter assemblies must be completed
in two minutes or less to prevent possible chassis overheating due to
temporary removal of the fan assembly.
1 Using the CLI or ICIM Web Interface, temporarily set AlmMuteA or AlmMuteB
to 1 (ON) to mute any alarms from the power supply section to be serviced. See
the Prisma II Platform Remote User Interface Guide, part number 4012441 for details.
2 Temporarily disconnect AC or DC power from the power supply section being
serviced.
3 Remove the fan assembly from the chassis and set it aside.
4 Locate the DC-to-DC converter assemblies mounted horizontally on a ledge
inside the fan assembly opening. The converter on the left side is for power
supply section A, while the converter on the right is for power supply section B.
5 To remove a DC-to-DC converter, grasp both edges and pull gently until the
converter board disengages from the midplane bus. Then slide the converter
board out of the chassis.
6 To reinsert a DC-to-DC converter, slide the converter board into the chassis until
it rests against with the connector on the midplane bus. Then push the converter
firmly into the midplane connector.
7 Reinstall the fan assembly.
8 Reconnect AC or DC power to the power supply section being serviced.
9 Set AlmMuteA or AlmMuteB to 0 (OFF) to enable alarms from the power supply
section.

4021339 Rev B 291

Chapter 10 Maintenance and Troubleshooting

Cleaning Optical Connectors

Note: The proper procedure for cleaning optical connectors depends on the
connector type. The following describes general instructions for cleaning optical
connectors. Many companies have established procedures for cleaning conductors
which should be followed. If your company has established procedures, the
following instructions should be considered along with your procedures.
Cleaning fiber-optic connectors can help prevent interconnect problems and aid
system performance. When optical connectors are disconnected or reconnected, the
fiber surface can become dirty or scratched. If not addressed, this dirt or damage
may lead to interconnect problems and reduced system performance.
Fiber-optic connectors should be inspected prior to mating and cleaned as needed to
remove all dust and contaminants without leaving any residue. Connectors should
be visually inspected after cleaning to confirm that they are clean and undamaged.

Recommended Equipment
The following equipment is recommended to clean the ends of fiber-optic
connectors.
  CLETOP or OPTIPOP ferrule cleaner (CLETOP Type A for SC, Type B for LC)
  Compressed air (also called “canned air”)
  Lint-free wipes moistened with optical-grade (99%) isopropyl alcohol
  Bulkhead swabs for LC or SC type connectors (choose appropriate type)
  Optical connector scope

Tips for Optimal Fiber-Optic Connector Performance

Follow these guidelines to ensure optimal connector performance.
  Do not connect or disconnect optical connectors while optical power is present.
  Always use compressed air before cleaning the fiber-optic connectors.
  Always use end caps on connectors when they are not in use.
  Always use compressed air to clean the end caps.
  If you have any degraded signal problems, clean the fiber-optic connector.
  Advance a clean portion of the ferrule cleaner reel for each cleaning.
  Turn off optical power before making or breaking optical connections in order to
avoid microscopic damage to fiber mating surfaces.

292 4021339 Rev B

 Cleaning Optical Connectors

To Clean Optical Connectors

Note: The proper procedure for cleaning optical connectors depends on the
connector type. The following describes general instructions for cleaning optical
connectors. Many companies have established procedures for cleaning conductors
which should be followed. If your company has established procedures, the
following instructions should be considered along with your procedures.
WARNING:

ƒ Avoid personal injury! Use of controls, adjustments, or performance of

procedures other than those specified herein may result in hazardous
radiation exposure.

ƒ Avoid personal injury! The laser light source on this equipment emits
invisible laser radiation. Avoid direct exposure to the laser light source.

ƒ Avoid personal injury! Viewing the laser output with optical instruments
(such as eye loupes, magnifiers, or microscopes) may pose an eye hazard.

  Connect or disconnect fiber only when equipment is OFF or in Service mode.

  Do not apply power to this equipment if the fiber is unmated or unterminated.
  Do not look into an unmated fiber or at any mirror-like surface that could reflect
light that is emitted from an unterminated fiber.
  Do not view an activated fiber with optical instruments such as eye loupes,
magnifiers, or microscopes.
  Use safety-approved optical fiber cable to maintain compliance with applicable
laser safety requirements.

Fiber Optic Connector Cleaning Instructions

Connector cleanliness is crucially important for optimum results in fiber-optic
communications links. Even the smallest amount of foreign material can make it
impossible to obtain the expected insertion and return losses. This can reduce the
range of the equipment, shorten its expected service life, and possibly prevent the
link from initializing at all.
New equipment is supplied with clean optical connectors and bulkheads. All optical
connectors (bulkheads and jumpers) should be inspected using an appropriate
optical scope prior to connector mating. If endface contamination is observed, the
connector should be cleaned and then re-inspected to verify cleaning.

Connectors and Bulkheads

Most fiber-optic connectors are of the physical contact (PC) type. PC type connectors
are designed to touch their mating connectors, thereby preventing air gaps which
cause reflections. For optimum performance, all dirt must be removed.
Bulkheads can also become dirty enough to affect performance, either from airborne
dust or from contamination introduced by connectors.

4021339 Rev B 293

Chapter 10 Maintenance and Troubleshooting

WARNING:
Avoid damage to your eyes! Do not look into any optical connector while the
system is active. Even if the unit is off, there may still be hazardous optical
levels present.

Important: Read the above warning before performing cleaning procedures.

Cleaning Connectors
Important:
  All external jumper connectors must be cleaned before inserting them into the
optical module.
  Before you begin, remove optical power from the module or ensure that optical
power has been removed.
Complete the following steps to clean fiber-optic connectors that will be connected to
the optical module.
1 Inspect the connector through an optical connector scope. If the connector is
damaged, e.g., scratched, burned, etc., replace the jumper.
2 If the connector is dirty but otherwise undamaged, clean the connector as
follows:
a Make several swipes across the face of the connector with the appropriate
ferrule cleaner. This will remove dust and some films.
b Listen for a slight "squeak" typically generated during this process, indicating
a clean connector.
c Inspect the connector again through the scope to confirm that it is clean.
3 If a second inspection indicates that further cleaning is needed:
a Use 99% isopropyl alcohol and a lint-free wipe to clean the connector.
b Use the appropriate ferrule cleaner again to remove any film left over from
the alcohol.
c Inspect the connector again through the scope and confirm that it is clean.
4 If necessary, repeat steps 3a-3c until the connector is clean.

Cleaning Bulkheads
Important:
  Do not detach the bulkhead from the module front panel for cleaning under any
circumstances. There is little or no slack in the fiber attached to the bulkhead,
and any attempt to remove the bulkhead will risk damage to the fiber.
  It is generally more difficult to clean bulkhead connectors and verify their
condition due to the inaccessibility of the fiber end face. For this reason, you
should only attempt to clean a bulkhead connector when a dirty connector is
indicated.

294 4021339 Rev B

 Cleaning Optical Connectors

Complete the following steps to clean the bulkhead.

WARNING:

ƒ Avoid personal injury! Use of controls, adjustments, or performance of

procedures other than those specified herein may result in hazardous
radiation exposure.

ƒ Avoid personal injury! The laser light source on this equipment emits
invisible laser radiation. Avoid direct exposure to the laser light source.

ƒ Avoid personal injury! Viewing the laser output with optical instruments
(such as eye loupes, magnifiers, or microscopes) may pose an eye hazard.
1 Insert a dry bulkhead swab into the bulkhead and rotate the swab several times.
2 Remove the swab and discard.
Important: Swabs may be used only once.
3 Check the bulkhead optical surface with a fiber connector scope to confirm that it
is clean. If further cleaning is needed:
a Moisten a new bulkhead swab using a lint-free wipe moistened with optical-
grade (99%) isopropyl alcohol.
b With the connector removed, fully insert the bulkhead swab into the
bulkhead and rotate the swab several times.
c Remove the swab and discard. Swabs may be used only once.
d Repeat steps 1 and 2 with a new dry bulkhead swab to remove any excess
alcohol or residue.
e Check with a fiber connector scope again to confirm that there is no dirt or
alcohol residue on the optical surface.
f If any alcohol residue remains, repeat steps 3d-3f.
4 Mate all connectors to bulkheads and proceed to Verifying Equipment
Operation below.
5 It is also recommended that all connectors be visually inspected after cleaning to
verify the connector is clean and undamaged.

Verifying Equipment Operation

Perform circuit turn-up. If the equipment does not come up, i.e., fails verification or
indicates a reflection problem, clean the connectors and bulkheads again.

For Further Assistance

If you have any questions or concerns about cleaning fiber-optic connectors, contact
Customer Service using the contact information provided in Customer Support
Information (on page 297).

4021339 Rev B 295

Chapter 10 Maintenance and Troubleshooting

Connecting Optical Cables

Important: It is recommended that all connections be made with the optical power
off. This will reduce the risk of damage to fiber-optic connectors.
Note: Observe laser safety precautions. Refer to Laser Safety (on page xxv) for
further information.

To Connect Optical Cables

CAUTION:
High power density exists on fiber when optical power is present. To avoid
microscopic damage to fiber mating surfaces, turn off optical power or reduce
power below 15 dBm before making or breaking optical connections.

Complete the following steps for each optical cable connection to be made and on
every module to be installed.
1 Clean the end of the fiber to be connected as described in Cleaning Optical
Connectors (on page 292).
2 Connect the optical cable to the module connector.
3 Route the cable to the appropriate destination.
4 Clean the remaining cable end, and then connect the cable to the mating module
connector.
Note: Remember to observe minimum bend radius and other accepted handling
practices when working with fiber-optic cables.
5 After cable installation is complete, return the module control settings to their
original states.

296 4021339 Rev B

 11 Chapter
11
Customer Support Information

Introduction
This chapter contains information on obtaining product support and
returning products to Scientific Atlanta.

In This Chapter
ƒ Obtaining Product Support ............................................................... 298
ƒ Return Product for Repair ................................................................. 300

4021339 Rev B 297

Chapter 11 Customer Support Information

Obtaining Product Support

IF… THEN…
you have general questions about this product contact your distributor or sales agent for
product information or refer to product data
sheets on www.cisco.com.
you have technical questions about this call the nearest Technical Service center or
product Scientific Atlanta office.
you have customer service questions or need call the nearest Customer Service center or
a return material authorization (RMA) Scientific Atlanta office.
number

Support Telephone Numbers

This table lists the Technical Support and Customer Service numbers for your area.
Region Centers Telephone and Fax Numbers
North America SciCare™ For Technical Support, call:
Services ƒ Toll-free: 1-800-722-2009
Atlanta, Georgia ƒ Local: 678-277-1120 (Press 2 at the prompt)
United States For Customer Service or to request an RMA number, call:
ƒ Toll-free: 1-800-722-2009
ƒ Local: 678-277-1120 (Press 3 at the prompt)
ƒ Fax: 770-236-5477
ƒ E-mail: [email protected]
Europe, Belgium For Technical Support, call:
Middle East, ƒ Telephone: 32-56-445-197 or 32-56-445-155
Africa ƒ Fax: 32-56-445-053
For Customer Service or to request an RMA number, call:
ƒ Telephone: 32-56-445-133 or 32-56-445-118
ƒ Fax: 32-56-445-051
ƒ E-mail: [email protected]
Japan Japan ƒ Telephone: 81-3-5908-2153 or +81-3-5908-2154
ƒ Fax: 81-3-5908-2155
ƒ E-mail: [email protected]
Korea Korea ƒ Telephone: 82-2-3429-8800
ƒ Fax: 82-2-3452-9748
ƒ E-mail: [email protected]
China China ƒ Telephone: 86-21-6485-3205
(mainland) ƒ Fax: 86-21-6485-3205
ƒ E-mail: [email protected]
All other Hong Kong ƒ Telephone: 852-2588-4746
Asia-Pacific ƒ Fax: 852-2588-3139
countries & ƒ E-mail: [email protected]
Australia

298 4021339 Rev B

 Obtaining Product Support

Region Centers Telephone and Fax Numbers

Brazil Brazil For Technical Support, call:
ƒ Telephone: 55-11-3845-9154 ext 230
ƒ Fax: 55-11-3845-2514
For Customer Service or to request an RMA number, call:
ƒ Telephone: 55-11-3845-9154, ext 109
ƒ Fax: 55-11-3845-2514
ƒ E-mail: [email protected]
Mexico, Mexico For Technical Support, call:
Central ƒ Telephone: 52-3515152599
America, ƒ Fax: 52-3515152599
Caribbean
For Customer Service or to request an RMA number, call:
ƒ Telephone: 52-55-50-81-8425
ƒ Fax: 52-55-52-61-0893
ƒ E-mail: [email protected]
All other Argentina For Technical Support, call:
Latin America ƒ Telephone: 54-23-20-403340 ext 109
countries ƒ Fax: 54-23-20-403340 ext 103
For Customer Service or to request an RMA number, call:
ƒ Telephone: 770-236-5662
ƒ Fax: 770-236-5888
ƒ E-mail: [email protected]

4021339 Rev B 299

Chapter 11 Customer Support Information

Return Product for Repair

You must have a return material authorization (RMA) number to return a product.
Contact the nearest customer service center and follow their instructions.
Returning a product to Scientific Atlanta for repair includes the following steps:
  Obtaining an RMA Number and Shipping Address (on page 300)
  Completing the Scientific Atlanta Transmission Networks Repair Tag (on page
301)
  Packing and Shipping the Product (on page 304)

Obtaining an RMA Number and Shipping Address

You must have an RMA number to return products.
RMA numbers are only valid for 60 days. RMA numbers older than 60 days must be
revalidated by calling a customer service representative before the product is
returned. You can return the product after the RMA number is revalidated. Failure
to comply with the above may delay the processing of your RMA request.
Complete the following steps to obtain an RMA number and shipping address.
1 Contact a customer service representative to request a new RMA number or
revalidate an existing one.
Refer to Support Telephone Numbers (on page 298) to find a customer service
telephone number for your area.
2 Provide the following information to the customer service representative:
ƒ Your company name, contact, telephone number, email address, and fax
number
ƒ Product name, model number, part number, serial number (if applicable)
ƒ Quantity of products to return
ƒ A reason for returning the product and repair disposition authority
ƒ Any service contract details
3 A purchase order number or advance payment to cover estimated charges will
be requested at the time a customer service representative issues an RMA
number.
Notes:
ƒ For credit card or cash in advance customers, a proforma invoice will be sent
to you upon completion of product repair listing all charges incurred.
ƒ Customer service must receive a purchase order number within 15 days after
you receive the proforma invoice.

300 4021339 Rev B

 Return Product for Repair

ƒ In-warranty products can accrue costs through damage, misuse, cosmetics, or

if no problem is found. Products incurring costs will not be returned to you
without a valid purchase order number.
4 Once an RMA number has been issued, a confirmation e-mail or fax will be sent
to you detailing the RMA number, product and product quantities authorized
for return, together with shipping address details and RMA terms and
conditions.
Note: Alternatively, you may obtain an RMA fax request form, complete and fax
it to a customer service representative, or e-mail your completed request form to:
[email protected].
5 Go to Completing the Scientific Atlanta Transmission Networks Repair Tag (on
page 301).

Completing the Scientific Atlanta Transmission Networks Repair Tag

Product returned for repair, both in-warranty and out-of-warranty, should have a
repair tag attached to the product detailing the failure mode. A supply of tags can
be obtained free of charge by calling a customer service representative.
The Scientific Atlanta Transmission Networks repair tag provides important failure
information to the Scientific Atlanta repair department. This information will reduce
the amount of time needed to repair the unit and return it to you. This information
can also reduce the cost of out-of-warranty repairs.
It is best to have the Scientific Atlanta Transmission Networks repair tag completed
by a person knowledgeable about the failure symptoms of the unit to be returned for
repair. The tag should be securely attached to the failed unit with the elastic string,
tape, or another method and returned to Scientific Atlanta.

4021339 Rev B 301

Chapter 11 Customer Support Information

Complete the following steps to fill out the Scientific Atlanta Transmission Networks
repair tag.
1 Complete header information.

ƒ RMA Number: Enter the RMA number provided by the Scientific Atlanta
customer service representative. All RMA numbers start with “3” and are
followed by 7 additional digits. An RMA number is required to return
products to Scientific Atlanta.
ƒ If you are the technician who is filling out this tag, you may not have the
RMA number. Leave it blank for now. Someone else in your organization,
who has the number, can fill it in later.
ƒ Date: Enter the date the unit was removed from service. If this date is
unknown, enter the date you are completing the repair tag.

302 4021339 Rev B

 Return Product for Repair

ƒ Company and City: Enter the company name and city of the customer who
owns the unit to be returned for repair.
ƒ SA Part # and Serial #: Enter the part number and serial number of the unit
you are returning for repair. The part number and serial number can usually
be found on a bar code label on the outside of the unit. If this information
can’t be found leave this blank.
ƒ Product: Enter the model description of the unit you are returning for repair.
For example, Model 6940/44 Node, Multimedia Tap, RF Signal Manager, etc.
2 Complete time of failure information.

This information will help the repair technician understand the failure mode. If
the time to failure is unknown, leave this information blank.
3 Complete the failure description and technician information:

ƒ Failure Description: Include as much information as possible. For example:

– Which feature is not working or which specification is not being met? For
example, does the problem affect audio, video, status monitoring and
control, forward path, reverse path, cosmetics, all functions, etc.
– If it is a multi-port product, which port is not working or if all ports are
not working?
– If the unit has degraded performance or is completely failed.

4021339 Rev B 303

Chapter 11 Customer Support Information

– If the failure happens only at specific environmental conditions (i.e., at

hot temperature).
– If the failure is intermittent or constant.
– How you were powering the unit when it failed? (DC vs. AC, voltage
levels, etc.)
Important: Descriptions like “bad unit,” “failed,” or “no HBO” are not specific
enough to be helpful.
ƒ Technician and Phone Number: Enter the name and phone number of the
technician completing the failure description information. A Scientific
Atlanta representative may want to call this person to better understand the
problem.
4 Attach the repair tag to the unit you are returning for repair. Use the elastic
string provided, tape, or another method to securely attach the tag.
5 Go to Packing and Shipping the Product (on page 304).

Packing and Shipping the Product

Complete the following steps to pack the product and ship it to Scientific Atlanta.
1 Are the product’s original container and packing material available?
ƒ If yes, pack the product in the original container using the original packing
material.
ƒ If no, pack the product in a sturdy corrugated box, that is suitable to the
method of shipment, and cushion it with packing material.
Important: You are responsible for delivering the returned product to Scientific
Atlanta safely and undamaged. Shipments damaged due to improper packaging
may be refused and returned to you at your expense.
Note: PLEASE DO NOT RETURN ANY POWER CORDS, ACCESSORY
CABLES, OR OTHER ACCESSORY PRODUCTS. Instructions for ordering
replacement power cords, accessory cables, or other accessories can be provided
by a customer service representative.
2 Write the following information on the outside of the shipping container:
ƒ RMA number
ƒ Your name
ƒ Your complete address
ƒ Your telephone number
ƒ "Attention: Factory Service"
Important: The RMA number should be clearly marked on all returned product,
boxes, packages, and accompanying paperwork. RMAs received by the factory
service receiving department that are not clearly marked may experience delays
in the processing of RMA requests. All returned product should be marked to
the attention of Factory Service.

304 4021339 Rev B

 Return Product for Repair

3 Ship the product to the address provided by the customer service representative
in the confirmation e-mail or fax.
Note: Scientific Atlanta does not accept freight collect. Be sure to prepay and
insure all shipments. For both in-warranty and out-of-warranty repairs, you are
responsible for paying your outbound freight expense, any applicable import
and/or export duties and taxes. Scientific Atlanta will pay the return freight
expense for in-warranty repairs.
International Shipments: International shipments should be consigned to
Scientific Atlanta with the notified party on the Airway Bill stated as "Expeditors
International for Customs Clearance".
4 On receipt of product returned under an RMA number, a receipt notification e-
mail or fax will be sent to you by Repair Receiving confirming receipt of product
and quantities received. Please check the receipt notification to assure the
product and quantity of product received by Scientific Atlanta matches what you
shipped.

4021339 Rev B 305

 A
Appendix A
Appx auto letter

Prisma II Permitted CLI

Commands
Introduction
The following tables summarize the available CLI commands for the
Prisma II Platform. Each table lists the commands available for one of
the four major CLI prompts: CLI, */* MODULE, TERMINAL, and
ICIM.
Entries shown in parenthesis () are module-specific and must be typed
in full. Hints are given to display available entries for those cases. All
other entries may be abbreviated to the shortest unambiguous form, as
explained in the CLI online help screens.
Note: Some commands are limited to Admin level users only.
For further information and assistance when working with CLI, type
help at the appropriate CLI prompt, and then press Enter to display
the corresponding help screens.

In This Appendix
ƒ From CLI .............................................................................................. 308
ƒ From ICIM ........................................................................................... 309
ƒ From */* MODULE ............................................................................ 315
ƒ From TERMINAL ............................................................................... 318

4021339 Rev B 307

Appendix A
Prisma II Permitted CLI Commands

From CLI
ALARM
CLEAR
DATE
EXIT
HELP ALARM
CLEAR
COMMANDS
DATE
EDIT
EXIT
ICIM
LOGOUT
MANUAL
MODULE
TERMINAL
WHO
WHOAMI
ICIM
LOGOUT
MANUAL
MODULE
TERMINAL
WHO
WHOAMI
'?'

308 4021339 Rev B

 From ICIM

From ICIM
ALARM
EVENTLOGCLEAR
EVENTLOGFILTER HARDWARE ON/OFF
PROVISIONING ON/OFF
SYSTEM ON/OFF
EXIT
FILE IP (IP_ADDRESS)
NAME (FILENAME)
PASSWORD (PASSWORD)
PATH (PATH)
USER (USERNAME)
HELP
IKE * ADD (IP_ADDRESS)
DELETE (IP_ADDRESS)
INFO ACTIVEREV
ATTNSTATUS
BOOTREV
CHASSIS
CLEI *
CLLI *
COMMREAD
COMMTRAP
COMMWRITE
DEVTYPE
DOWNLDCMD *
DOWNLDDIR *
DOWNLDFILE *
DOWNLDRESULT *
DOWNLDSEM *
DOWNLDSIG *
DOWNLDSTATE *

4021339 Rev B 309

Appendix A
Prisma II Permitted CLI Commands

DOWNLDTGT *
DOWNLDUSER *
FTPSERVER *
FTPUSER *
GATEWAY
HWREV
INACTIVEREV *
IP
IPSEC *
LOCKOUT
MAC
MANDATA
NEXTIMAGE
PREVIOUSIP
SELFTEST
SERIAL
SIZE
SLOT
SMC
STATUSMSG
SUBNET
SWDATE
SWREV
THRESHOLD
TIMEOUT
TOS
TZONE
UPDATEID
IPROUTE ADD (DESTINATION)
(GATEWAY)
DELETE (DESTINATION)
(GATEWAY)
IPSEC * DISABLE

310 4021339 Rev B

 From ICIM

ENABLE
LOGOUT
MANUAL
REBOOT
SET CLLI * (CLLI)
CLOCK (DATE_TIME)
COMMREAD (READ_STRING)
COMMTRAP (TRAP_STRING)
COMMWRITE (WRITE_STRING)
GATEWAY (GATEWAY)
IP (IP_ADDRESS)
LOCKOUT (INTERVAL)
STATUSMSG- (1)
CLEARKEY
SUBNET (SUBNET_MASK)
THRESHOLD (THRESHOLD)
TIMEOUT (TIMEOUT)
TZONE (TIMEZONE)
UPDATEID (1)
SHOW ACTIVEREV
ATTNSTATUS
BOOTREV
CHASSIS
CLEI *
CLLI *
CLOCK
COMMREAD
COMMTRAP
COMMWRITE
DEVTYPE
DOMAIN
DOWNLDCMD *
DOWNLDDIR *
DOWNLDFILE *

4021339 Rev B 311

Appendix A
Prisma II Permitted CLI Commands

DOWNLDRESULT *
DOWNLDSEM *
DOWNLDSIG *
DOWNLDSTATE *
DOWNLDTGT *
DOWNLDUSER *
EVENTLOG
EVENTLOGALL
EVENTLOGFILTER
FILE
FTPSERVER *
FTPUSER *
GATEWAY
HWREV
IKE *
INACTIVEREV *
IP
IPROUTE
IPSEC *
LOCKOUT
LOCKEDUSERS
MAC
MANDATA
NEXTIMAGE
PREVIOUSIP
PROVISIONING
SELFTEST
SERIAL
SIZE
SLOT
SMC
SNTP *
STATUSMSG

312 4021339 Rev B

 From ICIM

SUBNET
SWDATE
SWREV
THRESHOLD
TIMEOUT
TOS
TRAPS
TZONE
UPDATEID
USER
SNTP * INTERVAL
IP
MODE
STATE
TIMEOUT
TRAPS DISABLE (INDEX)
(IP_ADDRESS)
ENABLE (INDEX)
(IP_ADDRESS)

USER ADD (USER_ID) ADMIN DISABLE

ENABLE
READ DISABLE
ENABLE
READWRITE DISABLE
ENABLE
CHANGE ACCESS_RIGHTS (USER_ID) ADMIN
READ
READWRITE
ACCOUNT_STATUS (USER_ID) DISABLE
ENABLE
PASSWORD (USER_ID) (PASSWORD)
DELETE (USER_ID)
UNLOCK (USER_ID)

4021339 Rev B 313

Appendix A
Prisma II Permitted CLI Commands

'?'
* Reserved for future use.

314 4021339 Rev B

 From */* MODULE

From */* MODULE

ALARM DOMAIN
MODULE
CHASSIS (digits)
*
[range]
EXIT
HELP
INFO ALARM (ALARMNAME) HYSTERESIS
use show alarms * INDEX
LABEL
LIMITADJUST
MAJORHIGH
MAJORLOW
MINORHIGH
MINORLOW
NOMINAL
RANGEHI
RANGELO
TYPE
VALUE
CONTROL (CONTROLNAME) INDEX
use show control * LABEL
RANGEHI
RANGELO
RANGESTEP
STATENAMES
TYPE
UNITS
VALUE
MODULE ACTIVEREV
BOOTREV
CLEI 1

4021339 Rev B 315

Appendix A
Prisma II Permitted CLI Commands

CLLI 1
CODEREV
DATECODE
DEVTYPE
DOWNLOADABLE 1
INACTIVEREV 1
MANDATA
MODTYPE
NAME
NEXTIMAGE
NUMANALOGCONTROLS
NUMCONTROLS
NUMDIGITALCONTROLS
NUMMONITS
NUMOFALARMS
SCRIPTREV
SELFTEST
SERIAL
TOS
MONITOR (MONITORNAME) INDEX
use show mon * LABEL
STATENAMES
TYPE
UNITS
VALUE
LOGOUT
MANUAL
MODID digits
*
[range]
RESET
SET ALARMPARAM (ALARMNAME) HYSTERESIS
MAJORHIGH

316 4021339 Rev B

 From */* MODULE

MAJORLOW
MINORHIGH
MINORLOW
CONTROL (CONTROLNAME) (VALUE)
MODULE CLLI 1 (CLLI)
SHOW ALARMPARAM (ALARMNAME) HYSTERESIS
use show alarms * MAJORHIGH
MAJORLOW
MINORHIGH
MINORLOW
ALARMSTATE (ALARMNAME)
CONTROL (CONTROLNAME)
MODULE
MONITOR (MONITORNAME)
SLOT digits
*
[range]
'?'
1 Reserved for future use.

4021339 Rev B 317

Appendix A
Prisma II Permitted CLI Commands

From TERMINAL
ALARM
COLSEP (string)
EXIT
HEADERS (digits)
HELP
LOGOUT
MANUAL
PAGING (digits)
PATTERN REGEX
WILDCARD
SHOW
'?'

318 4021339 Rev B

 B
Appendix B
Appx auto letter

Features Available via Remote

User Interface
Introduction
This appendix lists the features of the remote user interface and
identifies the availability (CLI, Web Interface, or both) and required
user access level (Read-Only, Read-Write, or Admin) for each feature.
For additional information on these features, see the Prisma II Platform
Remote User Interface Guide, part number 4012441.

In This Appendix
ƒ Overview.............................................................................................. 320
ƒ ICIM Data............................................................................................. 321
ƒ Module Data ........................................................................................ 324
ƒ Current Alarms ................................................................................... 325
ƒ Module Alarms ................................................................................... 326
ƒ Module Controls ................................................................................. 327
ƒ Module Monitors ................................................................................ 328
ƒ System Information ............................................................................ 329
ƒ User Management............................................................................... 330

4021339 Rev B 319

Appendix B
Features Available via Remote User Interface

Overview
The tables below list the features available via either the CLI or the Web Interface.
Symbols appearing in the cells of these tables have the meanings described below.
  In the CLI or Web column:
- An asterisk (*) indicates that the corresponding interface (CLI or Web)
supports this feature.
- A dash (-) indicates that the corresponding interface (CLI or Web) does not
support this feature.
  In the Read-Only User, Read-Write User, or Admin User security column:
- A dash (-) indicates that this feature is not available to the corresponding
access level.
- The letter R indicates that the corresponding access level has Read-Only
access to this feature.
- The letter RW indicates that the corresponding access level has Read-Write
access to this feature.
Note: The hierarchy of access goes from Read-Only to Read-Write to Admin. So, if a
Read-Only user has the privilege to view a particular data element, a Read-Write
user would be able to view the same data element. Similarly, if a Read-Write user is
able to view or edit a data element, an Admin level user would be able to do the
same.

320 4021339 Rev B

 ICIM Data

ICIM Data
Feature CLI Web Read-Only Read-Write Admin
User User User
Privilege Privilege Privilege
IP address *1 * R R RW
Active rev * * R R R
Attnstatus * - R R R
Boot rev * - R R R
Chassis * * R R R
CLEI 2 * * R R R
CLLI 2 * * R RW RW
Clock *1 * R R RW
Commread * - - - RW
Commwrite * - - - RW
Commtrap * - - - RW
DevType * - R R R
Domain * * R R R
Downldcmd 2 * - R R R
Downlddir 2 * - R R R
Downldfile 2 * - R R R
Downldresult 2 * - R R R
Downldsem 2 * - R R R
Downldsig 2 * - R R R
Downldstate 2 * * R R R
Downldtgt 2 * - R R R
Downlduser 2 * - R R R
Eventlog * - - - R
Eventlogall * * - - R
File * - - R RW
Ftpserver 2 * - R R R
Ftpuser 2 * - - - R
Gateway *1 * R R RW

4021339 Rev B 321

Appendix B
Features Available via Remote User Interface

Feature CLI Web Read-Only Read-Write Admin

User User User
Privilege Privilege Privilege
Hwrev * * R R R
Inactiverev 2 * * R R R
IKE 2 * - - - RW
IProute * - R R RW
IPSec 2 * - R R RW
LockedUsers * * - - R
LockoutInterval * * R R RW
MAC * * R R R
Mandata * * R R R
Nextimage * - R R R
Previousip * - R R R
Provisioning * - R R R
Reboot * - - - W
Selftest * * R R R
Serial * * R R R
Size * * R R R
Slot * * R R R
Smc * * R R R
SNTPInterval 2 * - - - RW
SNTPIPAddress 2 * - - - RW
SNTPLastUpdate 2 * - - - R
SNTPMode 2 * - - - RW
SNTPState 2 * - - - RW
SNTPTimeout 2 * - - - RW
Statusmsg * - R R R
Statusmsgclearkey * - - - W
Subnet *1 * R R RW
Swdate * - R R R
Swrev * - R R R
sysDescr - * R R R

322 4021339 Rev B

 ICIM Data

Feature CLI Web Read-Only Read-Write Admin

User User User
Privilege Privilege Privilege
sysLocation - * R R R
sysUptime - * R R R
Threshold *3 * R R RW
Timeout *3 * R R RW
TOS * * R R R
Traps *3 * R R RW
Timezone *1 * R R RW
Updateid * - R R RW
User * * - - RW
1 May be modified through the CLI but not through the Web Interface.
2 Reserved for future use.
3 May be read through the CLI but not through the Web Interface.

4021339 Rev B 323

Appendix B
Features Available via Remote User Interface

Module Data
Feature CLI Web Read-Only Read-Write Admin
User User User
Privilege Privilege Privilege
Active rev * * R R R
Boot rev * - R R R
Chassis * * R R R
CLEI 1 * * R R R
CLLI 1 * * R RW RW
Device Type * * R R R
Downloadable 1 * * R R R
Inactive Rev 1 * * R R R
Module Name * * R R R
Module Type * * R R R
Reset * - - - W
Selftest * * R R R
Serial * * R R R
Slot * * R R R
Time of Service * * R R R
1 Reserved for future use.

324 4021339 Rev B

 Current Alarms

Current Alarms
Feature CLI Web Read-Only Read-Write Admin
User User User
Privilege Privilege Privilege
Current Alarms * * R R R

4021339 Rev B 325

Appendix B
Features Available via Remote User Interface

Module Alarms
Feature CLI Web Read-Only Read-Write Admin
User User User
Privilege Privilege Privilege
Hysteresis * * R RW RW
Label * * R R R
MajorHigh * * R RW RW
MajorLow * * R RW RW
MinorHigh * * R RW RW
MinorLow * * R RW RW
RangeHigh * * R R R
RangeLow * * R R R
Type * * R R R
Value * * R R R

326 4021339 Rev B

 Module Controls

Module Controls
Feature CLI Web Read-Only Read-Write Admin
User User User
Privilege Privilege Privilege
High * * R R R
Label * * R R R
Low * * R R R
Step * * R R R
Units * * R R R
Value * * R RW RW

4021339 Rev B 327

Appendix B
Features Available via Remote User Interface

Module Monitors
Feature CLI Web Read-Only Read-Write Admin
User User User
Privilege Privilege Privilege
Label * * R R R
Units * * R R R
Value * * R R R

328 4021339 Rev B

 System Information

System Information
Feature CLI Web Read-Only Read-Write Admin
User User User
Privilege Privilege Privilege
Event Log Filter *4 * R R RW
Event Log Clear * * - - R/Clear
Max Login Attempts *4 * R R RW
Inactivity Timeout *4 * R R RW
Lockout Interval * * R R RW
Trap Receive Table *4 * R R RW

4 May be read through the CLI but not through the Web Interface.

4021339 Rev B 329

Appendix B
Features Available via Remote User Interface

User Management
Feature CLI Web Read-Only Read-Write Admin
User User User
Privilege Privilege Privilege
Add user * * - - RW
Change user * * - - RW
Current users * * - - R
Delete user * * - - RW
Unlock user * -1 - - RW

1A user account may be unlocked through the Web Interface by enabling the
account.

330 4021339 Rev B

 C
Appendix C
Appx auto letter

Module Parameter
Descriptions
Introduction
This appendix provides manufacturing data, monitored parameters,
configurable parameters, and alarms for the Prisma II XD Platform.
The examples shown in the tables are for guidance only.
CAUTION:
The warranty may be voided and the equipment damaged if you operate
the equipment above the specified temperature limits (0 to 50°C).
Specification temperature limits are measured in the air stream at the fan
inlet and may be higher than room ambient temperature.

In This Appendix
ƒ XD Chassis Parameters ...................................................................... 332

4021339 Rev B 331

Appendix C
Module Parameter Descriptions

XD Chassis Parameters
XD Chassis Control Parameters
Control Function Value Default
AlmMuteA Alarm muting for power section A 0 (OFF) 0 (OFF)
1 (ON)
AlmMuteB Alarm muting for power section B 0 (OFF) 0 (OFF)
1 (ON)

XD Chassis Alarm Data Parameters

User Alarm Data Parameters

Alarm Function Major Minor Minor Major Hysteresis Typical

Low Low High High Range/
Threshold Threshold Threshold Threshold Nom.
Value
ChasTemp Fan tray -40°C -35°C 60°C 65°C 1°C -40°C to
temperature 65°C /
25°C
ConvA+24 +24 V alarm 18.0 VDC 18.4 VDC 25.9 VDC 26.1 VDC 0.1 VDC 23.8 to
for supply A 25.6
VDC /
24.7 V
ConvA+5 +5 V alarm 3.6 VDC 3.7 VDC 5.9 VDC 6.1 VDC 0.1 VDC 4.9 to
for supply A 5.3 VDC
/ 5.4 V
ConvA-5 -5 V alarm -5.6 VDC -5.5 VDC -4.6 VDC -4.5 VDC 0.1 VDC -5.3 to
for supply A -4.9
VDC / -
5.4 V
ConvB+24 +24 V alarm 18.0 VDC 18.4 VDC 25.9 VDC 26.1 VDC 0.1 VDC 23.8 to
for supply B 25.6
VDC /
24.7 V
ConvB+5 +5 V alarm 3.6 VDC 3.7 VDC 5.9 VDC 6.1 VDC 0.1 VDC 4.9 to
for supply B 5.3 VDC
/
5.4 V
ConvB-5 -5 V alarm -5.6 VDC -5.5 VDC -4.6 VDC -4.5 VDC 0.1 VDC -5.3 to
for supply B -4.9
VDC / -
5.4 V

332 4021339 Rev B

 XD Chassis Parameters

Module Alarm Data Parameters

Alarm Function Major Minor Minor Major Hysteresis Typical

Low Low High High Range/
Threshold Threshold Threshold Threshold Nom.
Value
Fan 1_Ok Fan 1 status na na na na na OK or
Fault
Fan 2_Ok Fan 2 status na na na na na OK or
Fault
Fan 3_Ok Fan 3 status na na na na na OK or
Fault
ConvAIn Converter A na na na na na OK or
power status Fault
ConvBIn Converter B na na na na na OK or
power status Fault

XD Chassis Monitor Parameter Examples

Parameter Function Initial Operating
Value Value (typ)
PSA Inst 1 if power supply A is installed and 1 (Installed 1 (Installed
powered, 0 if not and and
powered) powered)
ConvAIns 1 if converter A is installed, 0 if not 1 (Installed) 1 (Installed)
ConvA+24 Measured +24 V DC of slot A 24.1148 V 24.1148 V
ConvA+5 Measured +5 V DC of slot A 5.29054 V 5.29054 V
ConvA-5V Measured -5 V DC of slot A -5.29926 V -5.29926 V
PSB Inst 1 if power supply B is installed and 0 (Not 1 (Installed)
powered, 0 if not installed)
ConvBIns 1 if converter B is installed, 0 if not 1 (Installed) 1 (Installed)
ConvB+24 Measured +24 V DC of slot B 24.1481 V 24.1481 V
ConvB+5 Measured +5 V DC of slot B 5.0949 V 5.0949 V
ConvB-5V Measured -5 V DC of slot B -5.02933 V -5.02933 V
Chas+24 Chassis +24 V bus 24.14 V 24.14 V
Chas+5 Chassis +5 V bus 5.08 V 5.08 V
Chas-5 Chassis -5 V bus -5.05 V -5.05 V
ChasTemp Chassis internal temperature 26.5°C 26.5°C

Note: All monitored values may vary from module to module. The values shown
above are examples only.

4021339 Rev B 333

Appendix C
Module Parameter Descriptions

XD Chassis Manufacturing Data Parameter Examples

XD Chassis

Manufacturing Data Typical Values

Module Name P2-XD-CHASSIS
Module Type 5020
Manufacturing Data <NULL>
Serial # [1] AAFHJJT
Date Code [1] K06
Module ID <NULL>
CLLI Code [1] <NULL>
CLEI Code [1] <NULL>
Sw Ver (Software Version) [1] 1.01.00
In Service Hours [1] 372

ICIM2-XD

Manufacturing Data Typical Values

Module Name P2-ICIM2-XD
Module Type 5011
Manufacturing Data ICIM2
Serial # [1] ~AAVGTHZ
Date Code [1] C07
Module ID <NULL>
CLLI Code [1] <NULL>
CLEI Code [1] <NULL>
Hardware Revision BdRev87A
Sw Ver (Software Version) [1] 2.02.10
In Service Hours [1] 372

Note: [1] These values may vary from module to module. The values shown above
are examples only.

334 4021339 Rev B

Glossary
A

A
ampere. A unit of measure for electrical current.

ac, AC
alternating current. An electric current that reverses its direction at regularly recurring
intervals.

AD
administration.

Admin
administrator.

AGC
automatic gain control. A process or means by which gain is automatically adjusted in a
specified manner as a function of input level or other specified parameters.

AWG
American Wire Gauge. A U.S. standard for wire conductor sizes.
B

binding
A parameter representing the physical or logical objects associated with a trap.
C

CAT5
category 5 Ethernet cable.

CBN
common bonding network.

CCB
client controller board or chassis control board.

4021339 Rev B 335

 Glossary

CENELEC
Comité Européen de Normalisation ELECtrotechnique. The European Committee for electro-
technical standardization.

CLEI
common language equipment identifier. CLEI code is globally unique ten-character
intelligent code, assigned by Telcordia, that identifies communications equipment in a
concise, uniform feature-oriented language, which describes product type, features, source
document and associated drawings and vintages.

CLI
command line interface. A command reference software that allows the user to interact with
the operating system by entering commands and optional arguments.

CLLI
common language location identification. A CLLI code is typically an 11-character
alphanumeric descriptor used to identify network elements and their locations.

COM
communication.

CSV
comma-separated values. A data file format supported by many spreadsheet programs, in
which fields are separated by commas. Also referred to as comma delimited.
D

dc, DC
direct current. An electric current flowing in one direction only and substantially constant in
value.
E

EEPROM
electrically erasable programmable read-only memory.

EIA
Electronic Industries Association. A United States association that provides standards for use
between manufacturers and purchasers of electronic products.

EMC
electromagnetic compatibility. A measure of equipment tolerance to external electromagnetic
fields.

336 4021339 Rev B

 Glossary

EMS
Element Management System. A system that controls a single element, or many elements of a
single type. Usually works up into a full network management system (NMS).

ESD
electrostatic discharge. Discharge of stored static electricity that can damage electronic
equipment and impair electrical circuitry, resulting in complete or intermittent failures.
F

FCC
Federal Communications Commission. Federal organization set up by the Communications
Act of 1934 which has authority to regulate all inter-state (but not intra-state) communications
originating in the United States (radio, television, wire, satellite, and cable).

FTP
file transfer protocol. Allows users to transfer text and binary files to and from a personal
computer, list directories on the foreign host, delete and rename files on the foreign host, and
perform wildcard transfers between hosts.

FTTP
fiber-to-the-premises. Fiber optic service to the subscriber's premises.
H

HDRx
high density receiver.

HDTx
high density transmitter.

HTTP
hypertext transport protocol. A communication protocol used to request and transmit files
over the Internet and other networks.

HW
hardware.

Hz
hertz. A unit of frequency equal to one cycle per second.
I

I/O
input/output.

4021339 Rev B 337

 Glossary

ICIM
intelligent communications interface module.

ID
identifier.

IEC
International Electro-technical Commission.

in-lb
inch-pound. A measure of torque defined by the application of one pound of force on a lever
at a point on the lever that is one inch from the pivot point.

IP
Internet protocol. A standard that was originally developed by the United States Department
of Defense to support the internetworking of dissimilar computers across a network. IP is
perhaps the most important of the protocols on which the Internet is based. It is the standard
that describes software that keeps track of the internetwork addresses for different nodes,
routes, and outgoing/incoming messages on a network. Some examples of IP applications
include email, chat, and Web browsers.
L

LCD
liquid crystal display. A display medium made of liquid crystal. Liquid crystal's reflectance
changes when an electric field is applied. Commonly used in monitors, televisions, cell
phones, digital watches, etc.

LCI
local craft interface.

LED
light-emitting diode. An electronic device that lights up when electricity passes through it.
M

MIB
management information base. SNMP collects management information from devices on the
network and records the information in a management information base. The MIB
information includes device features, data throughput statistics, traffic overloads, and errors.

MSO
multiple system operator. A cable company that operates more than one cable system.

338 4021339 Rev B

 Glossary

nm
nanometer. One billionth of a meter.

Nm
Newton meter. A measure of torque defined by the application of one Newton of force on a
lever at a point on the lever that is one meter from the pivot point. (1 Nm = 0.737561 ft-lb)

NMS
network management system. A software system designed specifically to monitor a network
and to facilitate troubleshooting.

NTP
network time protocol.
O

OID
object identifier.

OMI
optical modulation index.
P

PR
provisioning.

PWR
power.
Q

QAM
quadrature amplitude modulation. A phase modulation technique for representing digital
information and transmitting that data with minimal bandwidth. Both phase and amplitude
of carrier waves are altered to represent the binary code. By manipulating two factors, more
discrete digital states are possible and therefore larger binary schemes can be represented.
R

RF
radio frequency. The frequency in the portion of the electromagnetic spectrum that is above
the audio frequencies and below the infrared frequencies, used in radio transmission systems.

RMA
return material authorization. A form used to return products.

4021339 Rev B 339

 Glossary

RO
read-only.

RTC
real time clock.

RW
read-write.

RX
receive or receiver.
S

SE
security.

semaphore
In programming, a control token (variable or abstract data type) used to restrict access to a
resource. The Scientific Atlanta SOUP program uses a semaphore to prevent multiple
instances of the SOUP from running and trying to change Prisma II EMS chassis parameters
at the same time.

SMC
status monitoring and control. The process by which the operation, configuration, and
performance of individual elements in a network or system are monitored and controlled
from a central location.

SNMP
simple network management protocol. A protocol that governs network management and the
monitoring of network devices and their functions.

SOUP
software upgrade program. A utility used to update firmware in Prisma II EMS application
modules.

SY
system.
T

TNCS
Transmission Network Control System. A Scientific Atlanta application that allows status

340 4021339 Rev B

 Glossary

monitoring and control of all transmission equipment located in headends and hubs plus
optical nodes, power supplies, and amplifiers in the outside plant. TNCS provides access to
and information on the entire network in an easy to understand, topology driven, graphical
user display.

trap
An unsolicited message sent by a network device to notify a network or element management
system of an alarm or other condition that requires administrative attention.

TX
transmit or transmitter.
V

V AC
volts alternating current.

V DC
volts direct current.
X

XD
extreme density.

4021339 Rev B 341

Index
Chassis Midplane • 44
A Chassis Power Supply Architecture • 35
A • 335 Chassis Troubleshooting • 274
About Traps • 226 Chassis Wiring and Fusing • 6, 57, 74
ac, AC • 335 Chassis-to-Chassis ICIM Activation • 66
Accessing the Module Detail Information • 118 Chassis-to-Chassis ICIM Connections • 3
AC-to-DC Bulk Power Supply Features • 51 ChasTemp Alarm • 277
AC-to-DC Bulk Power Supply Illustration • 51 ChasTemp Alarm Parameters • 277
AC-to-DC Bulk Power Supply Modules • 48 Checking Manufacturing Data using LCI • 134
AD • 335 Checking the Module Alarms using LCI • 128
Additional Assistance • 275 Checking the Operating Status • 124
Admin • 335 Cleaning Optical Connectors • 292
AGC • 335 Clearing the Event Log • 163
Alarm Data Parameters • 129 CLEI • 336
ALARM IN and OUT Connections • 70 CLI • 336
ALARM IN and OUT Terminal Blocks • 71 CLI Parameters • 93
Alarm Limit Parameters • 132 CLLI • 336
Alarm Severity • 213 COM • 336
Alarm Threshold Modification • 264 Completing the Scientific Atlanta Transmission
Alarm Troubleshooting • 275 Networks Repair Tag • 301
AWG • 335 Computer Requirements • 111
Configuring the Module using LCI • 126
B Connecting a Chassis to the TNCS Server • 68
Basic SNMP Setup • 106 Connecting Optical Cables • 87, 296
Before You Begin • 56 Connecting RF Cables • 88
binding • 335 Connecting the ICIM to Additional Chassis • 64
Connecting Your Computer to the Chassis • 115
C Connector Interface Panel • 63
Cable Kits for Connecting a Chassis to the ConvA+24 Alarm • 279
TNCS Server • 68 ConvA+24 Alarm Parameters • 279
Cable Requirements • 111 ConvA+5 Alarm • 281
CAT5 • 335 ConvA+5 Alarm Parameters • 281
CBN • 335 ConvA-5 Alarm • 283
CCB • 335 ConvA-5 Alarm Parameters • 283
CENELEC • 336 ConvAIn Alarm • 278
Chassis and Slot Numbering • 41 ConvAIn Alarm Parameters • 278
Chassis Back Panel Features • 43 ConvB+24 Alarm • 286
Chassis Configuration • 40 ConvB+24 Alarm Parameters • 286
Chassis Dimensions • 62 ConvB+5 Alarm • 288
Chassis Features • 39 ConvB+5 Alarm Parameters • 288
Chassis Front Panel Features • 42 ConvB-5 Alarm • 290
Chassis Illustrations • 42 ConvB-5 Alarm Parameters • 290

4021339 Rev B 343

Index

ConvBIn Alarm • 285

ConvBIn Alarm Parameters • 285
H
CSV • 336 Hardware Installation • 55
Current Alarm Table • 213 HDRx • 337
Current Alarms • 325 HDTx • 337
Customer Support Information • 297 How do Enhanced Traps differ from other trap
types? • 268
D
How do I configure trap destination? • 267
DC Power Connectors • 76 HTTP • 337
dc, DC • 336 HW • 337
DC-to-DC Converter Illustration • 52 HyperTerminal Session Setup • 90
DC-to-DC Converters • 52 Hz • 337
Default Community Strings • 107
Delay in the Discovery Process • 263
I
Downloading and Viewing the Event Log I/O • 337
Remotely • 168 ICIM • 338
ICIM as Proxy for Module Information • 266
E
ICIM Data • 321
EEPROM • 336 ICIM Front Panel • 102
EIA • 336 ICIM IN and ICIM OUT Cables • 5, 66
Electrical Input Voltages • 50 ICIM IN and ICIM OUT Connectors • 3
Electrical Power Connections • 6, 74 ICIM Introduction • 100
EMC • 336 ICIM MIB • 173
EMS • 337 ICIM2-XD • 37
Enhanced Trap Alarms • 243 ICIM2-XD Block Diagram • 53, 101
Enhanced Trap Binding Information • 239 ICIM2-XD Front Panel Features • 54, 102
Enhanced Trap Events • 246 ICIM2-XD Illustration (Front Panel) • 54, 102
Equipment Configuration • 89 ID • 338
ESD • 337 IEC • 338
Event Action IDs • 159 in-lb • 338
Event Log • 157 Insert Module Table • 222
Event Log Fields • 158 Installing Application Modules • 84
Event Log File Management • 184 Installing LCI • 112
Event Log-Related Traps • 166 Installing the ICIM • 83
External Alarms Connections • 70 Installing the Power Supply • 73
Introduction • 31, 138, 158, 172
F IP • 338
Fan Alarm Parameters • 276
L
Fan Assembly • 44, 72
Fan Assembly Illustration • 47 Laser Warning • 100
Fan Ok Alarms • 276 LCD • 338
Fan Operation • 47 LCI • 338
FCC • 337 LCI Function • 110
Frequently Asked Questions • 267 LCI Introduction • 110
From */* MODULE • 315 LCI Module Tree • 117
From CLI • 308 LED • 338
From ICIM • 309 Login • 93
From TERMINAL • 318
FTP • 337
M
FTTP • 337 Maintenance • 273

344 4021339 Rev B

 Index

Maintenance and Troubleshooting • 271 Power Supply Requirements • 73

Maintenance Record • 273 PR • 339
Manufacturing Data Parameters • 105, 134 Prisma II Enterprise MIBs • 172
Master-Slave Illustration • 71 Prisma II ICIM2-XD • 53
Master-Slave Operation • 70 Prisma II Traps • 226
MIB • 338 Prisma II XD Chassis • 39
Midplane Bus Connectors • 45 Prisma II XD Platform • 34
Modifying Module Alarm Limits using LCI • PWR • 339
131
Module Alarm Data Parameters • 104
Q
Module Alarm Table • 207 QAM • 339
Module Alarms • 326 Quick Start Guide • 1
Module Control Table • 219
Module Controls • 327 R
Module Data • 324 Rack Location Requirements • 59
Module Details Window • 118 Recommended Equipment • 292
Module MIB • 198 Related Publications • 33
Module Monitor Table • 216 Remote Reboot of ICIM and Modules • 225
Module Monitors • 328 Remove Module Table • 222
Module Removal and Enhanced Traps • 266 Replacing the Default Admin Account • 141
Module Table • 199 Required Equipment and Tools • 56
Module Tree • 117 Return Product for Repair • 300
Mounting the Chassis in a Rack • 61 RF • 339
MSO • 338 RMA • 339
RO • 340
N
RTC • 340
nm • 339 RW • 340
Nm • 339 RX • 340
NMS • 339
NTP • 339 S
SE • 340
O
semaphore • 340
Obtaining an RMA Number and Shipping Setting Event Log Filter Parameters • 164
Address • 300 Setting Trap Receive Parameters • 108
Obtaining Product Support • 298 Site Requirements • 57
OID • 339 SMC • 340
OMI • 339 SNMP • 340
Operating Environment • 57 SNMP Considerations • 106
Operating Status Parameters • 103, 124 SNMP Management • 171
Operating the ICIM • 103 SNMP Parameters • 98
Operation using ICIM • 99 SOUP • 340
Operation using LCI • 109 Standard and Enhanced Traps • 227
Overview • 100, 320 Starting LCI Software • 116
Step 1
P
Install the Chassis in a Rack • 2
Packing and Shipping the Product • 304 Step 10
Power Inlet Illustration • 9, 77 Perform Chassis-to-Chassis ICIM Activation
Power Inlets • 50 (Optional) • 25
Power Supply Configurations • 48 Step 11
Power Supply Cooling Fans • 79

4021339 Rev B 345

Index

Make Changes to Traps and Enterprise MIBs To Change the Chassis ID Number • 4, 65
• 26 To Check Alarms using LCI • 128
Step 12 To Check Manufacturing Data using LCI • 134
Make Physical Connections to Modules • 27 To Check the Operating Status using LCI • 124
Step 13 To Clean Optical Connectors • 293
Verify System Release and Module Firmware To Configure Trap Destination • 229
Versions • 29 To Connect a Computer to the Chassis • 115
Step 2 To Connect Optical Cables • 87, 296
Make Chassis-to-Chassis ICIM Connections • To Connect RF Cables • 88
3 To Connect TNCS to the Chassis EM IN Port •
Step 3 68
Make Electrical Power Connections • 6 To Enable Power Passing • 81
Step 4 To Install the Chassis in a Rack • 2, 61
Install the ICIM2 • 14 To Install the DC-to-DC Converter • 79
Step 5 To Install the ICIM2-XD • 14, 83
Set Network Parameters from the Command To Install the LCI Software • 112
Line Interface (CLI) • 15 To Install the Module • 20, 84
Step 6 To Install the Power Cord • 9, 77
Connect the ICIM to the Network • 19 To Install the Power Supply in the Chassis • 10,
Step 7 78
Install Modules in the Chassis • 20 To Make ICIM IN and ICIM OUT Cable
Step 8 Connections • 3, 64
Set Additional Parameters via CLI (Optional) To Modify Alarm Limits using LCI • 131
• 22 To Monitor the Power Supply • 81
Step 9 To Remove the Fan Assembly • 72
Set and Verify SNMP Community Strings • To Remove the Module • 85
23 To Set Additional Users for Telnet or CLI
Suggested Actions • 276, 277, 278, 279, 281, Access • 22, 94
283, 285, 286, 288, 290 To Set and Verify SNMP Community Strings •
Support Telephone Numbers • 298 94
SY • 340 To Set Control Parameters using LCI • 126
System Behavior • 266 To Set Up a HyperTerminal Serial Port Session •
System Information • 329 90
System Requirements • 111 To Set Up a Telnet CLI Session • 19, 96
To Share Power Between Two Chassis • 11
T To Start LCI Software • 116
Telnet Session • 96 trap • 341
Tips for Optimal Fiber-Optic Connector Trap Handling • 188
Performance • 292 Trap Logging Auxiliaries • 192
TNCS • 340 Trap Logging Table • 193
To Access the DC-to-DC Converter • 279, 281, Trap Receiving Configuration • 228
283, 286, 288, 290 Trap Recv Table • 188
To Access the Module Details, Double-Click the Trap Types • 229
Chassis • 119 Troubleshooting • 274
To Access the Module Details, Double-Click the TX • 341
Module • 121 Typical Chassis Block Diagram • 41
To Access the Module Details, Right-Click the
U
Chassis • 120
To Access the Module Details, Right-Click the Unpacking and Inspecting the Chassis • 56
Module • 122 Unused Slots • 60

346 4021339 Rev B

 Index

User Alarm Data Parameters • 104

User Lockout • 151
User Management • 137, 330
Using TNCS with Multiple Chassis • 69
V
V AC • 341
V DC • 341
Viewing the Event Log • 161
W
Warning Labels • xxvii
What is the Trap Logging Table? • 269
When do traps associated with module insertion,
removal, and alarms occur? • 268
Where can I find trap definitions? • 269
Why do the same alarm values represent
different conditions? • 267
Working With User Accounts • 144
X
XD • 341
XD Application Modules • 38
XD Chassis • 35
XD Chassis Alarm Data Parameters • 332
XD Chassis Control Board • 45
XD Chassis Control Parameters • 127, 332
XD Chassis Fan Assembly • 35, 47
XD Chassis Manufacturing Data Parameter
Examples • 334
XD Chassis Monitor Parameter Examples • 333
XD Chassis Parameters • 332
XD Platform Components • 34

4021339 Rev B 347

Scientific Atlanta, A Cisco Company 678.277.1000
5030 Sugarloaf Parkway, Box 465447 www.scientificatlanta.com
Lawrenceville, GA 30042
This document includes various trademarks of Cisco Systems, Inc. Please see the Notices
section of this document for a list of Cisco Systems, Inc., trademarks used in this document.
Product and service availability are subject to change without notice.
© 2008 Cisco Systems, Inc. All rights reserved.
September 2008 Printed in United States of America Part Number 4021339 Rev B