Avaya BCM 2.0 Programming Betriebsanweisung PDF herunterladen (Seite 278)

278 Maintenance

Enterprise Edge 2.0 Programming Operations Guide P0911588 Issue 01

2. Total Queue XX Packets: Total number of packets carried at specified queue's

priority.

3. Total Queue XX Packets Dropped: Total number of packets dropped at

specified queue - probably due to insufficient buffer space.

Maintenance programming for telephony resources

When you perform maintenance on your Enterprise Edge system, you must know

the system version and the status of each of your Media Bay Modules. For

procedures on how to access this information, refer to the following:

• System version on page 278

• Media Bay Module status on page 279

For information on the logs generated by your Enterprise Edge system, refer to:

• System test log on page 282

• System administration log on page 283

• Network event log on page 284

For information on alarm codes and event messages, refer to Alarm codes on page

285 and Event messages on page 285.

If you want to run a line loopback, payload loopback, card loopback or continuity

loopback test, refer to Tests on page 294.

For information on system statistics and metrics, refer to:

• CSU statistics on page 297

• Link Status on page 301

• Metrics on page 301

For information on physically moving an existing telephone, refer to Moving

telephones on page 302.

System version

System version allows you to check the version number of the System Processor

(SP) software, that resides on the Media Services Card (MSC).

1. Choose Resources andclickontheMedia Services Card heading.

The version number of the software appears in the Version box.

2. Write the version number on the appropriate Maintenance record.

Note: You can use the version number to determine the software release and

it may be required by support staff if a software fault occurs.

1 2 ... 273 274 275 276 277 278 279 280 281 282 283 ... 445 446

Keine Kommentare

Avaya BCM 2.0 Programming Betriebsanweisung Seite 278