| Doc ID | SOLN260820 | |
| Version: | 13.0 | |
| Status: | Published | |
| Published date: | 11 Feb 2021 | |
| Created Date: | 12 Dec 2014 |
Details
VAL-PT (Voice Announcements over LAN Packet/Port)
Alarm
VAL-PT y MIN
test board 29b03 long Page 1
TEST RESULTS
Port Mtce Name Alt. Name Test No. Result Error Code
29B03 VAL-BD 52 PASS
29B03 VAL-BD 597 PASS
29B03 VAL-BD 595 PASS
29B03 VAL-BD 596 PASS
29B03 VAL-BD 598 PASS
29B03 VAL-BD 600 PASS
29B03 VAL-BD 601 PASS
29B03 VAL-BD 1680 ABORT 0
29B0301 VAL-PT 1285 FAIL
29B0301 VAL-PT 1275 PASS
29B0302 VAL-PT 1285 FAIL
29B0302 VAL-PT 1275 PASS
29B0303 VAL-PT 1285 FAIL
29B0303 VAL-PT 1275 PASS
29B0304 VAL-PT 1285 FAIL
29B0304 VAL-PT 1275 PASS
29B0305 VAL-PT 1285 FAIL
29B0305 VAL-PT 1275 PASS
29B0306 VAL-PT 1285 FAIL
29B0306 VAL-PT 1275 PASS
29B0307 VAL-PT 1285 FAIL
29B0307 VAL-PT 1275 PASS
29B0308 VAL-PT 1285 FAIL
29B0308 VAL-PT 1275 PASS
29B0309 VAL-PT 1285 FAIL
29B0309 VAL-PT 1275 PASS
29B0310 VAL-PT 1285 FAIL
29B0310 VAL-PT 1275 PASS
29B0311 VAL-PT 1285 FAIL
Problem Clarification
VAL-PT alarms for Announcement Board Reporting Alarms
Cause
Hardware
display errors
HARDWARE ERROR REPORT — ACTIVE ALARMS
Port Mtce Alt Err Aux First/Last Err Err Rt/ Al Ac
Name Name Type Data Occurrence Cnt Rt Hr St
VAL-PT 3585
VAL-PT 3585
VAL-PT 3585
Solution
Received tones do not match transmitted tones.
1. Make sure that you have a recent backup of the announcements stored
2. Busy the circuit pack
3. Reset the circuit pack
4. Release the circuit pack
5. Repeat the test “test board 29b03 long”
6. Check to see if alarms are cleared, and no test 1285 fail
7. If the problem persists, we’ll need to replace the circuit pack
VAL-BD 1680 ABORT 0 = there is no short test sequence for this MO
ETH-PT IPv4 1278 ABORT 1000 = The port is in use. 1. Determine status of port using status clan-port location. 2. Retry the command when the port is idle. You can force the port to the idle state by executing busyout port location. Note: The busyout port command is destructive, causing every call and link associated with the port to be torn down.
The alarms have cleared and the board is passing and that ETH-PT IPv4 1278 ABORT 1000 port is in use by Equipment Type: Clan Ethernet Link
If ETH-PT IPv4 1278 FAIL Data received did not match the data transmitted and we would end up replacing the circuit pack.
Additional Relevant Phrases
SOLN260820
VAL-PT
SOLN131953
FALLA MedPro solicita revision y en su caso reemplazo de la tarjeta
*Tarjeta TN2501AP se encuentra defectuaza u se necesita reemplazo*
TN2501 fails Tests 52 and 1285.
olicita apoyo para apertura caso con Intersel,
Constant disruption of service
Presentamos problemas con nuestra tarjeta principal de anuncio VALTN2501, por lo anterior no esta permitiendo la reproducción de los audios.
busyout | extract | reinsert > board VAL[tn2501]
Avaya — Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS
Contact US
Thanks. We have received your request and will respond promptly.
Log In
Come Join Us!
Are you a
Computer / IT professional?
Join Tek-Tips Forums!
- Talk With Other Members
- Be Notified Of Responses
To Your Posts - Keyword Search
- One-Click Access To Your
Favorite Forums - Automated Signatures
On Your Posts - Best Of All, It’s Free!
*Tek-Tips’s functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.
Posting Guidelines
Promoting, selling, recruiting, coursework and thesis posting is forbidden.
Students Click Here
ETH-PT Error 3585 Aux Data 1ETH-PT Error 3585 Aux Data 1(OP) 3 Nov 06 11:40 Can anyone explain this error to me? I went through Avaya’s maintanence pdf and cannot find anything on thie error. The eth-pt is on the 17th port of my clan. I am using it for a CDR connection between my SQL Server and the switch. I am also getting errors on the clan card (error 3846)which are telling me that the connection is causing a high cpu occupancy. The error itself is not destructive but I am afraid that since I am starting to see this other error on the same card that eventually it is going to cause a problem. Any help would be appreciated! Thanks Rob Red Flag SubmittedThank you for helping keep Tek-Tips Forums free from inappropriate posts. |
Join Tek-Tips® Today!
Join your peers on the Internet’s largest technical computer professional community.
It’s easy to join and it’s free.
Here’s Why Members Love Tek-Tips Forums:
Talk To Other Members- Notification Of Responses To Questions
- Favorite Forums One Click Access
- Keyword Search Of All Posts, And More…
Talk To Other MembersRegister now while it’s still free!
Already a member? Close this window and log in.
Join Us Close
Модератор: Administrator
-
steysha
- Постоянный участник форума
- Сообщения: 152
- Зарегистрирован: Пн 02 фев 2009, 19:29
Ошибки DS1
Добрый день. С некоторого времени каждую ночь появляются и сами собой пропадают проблеммы с карточкой. Почти как по расписанию она уходит в аут оф сервис после ошибки на сигнальном порту — Error Type 3585: transmit FIFO Overflow error. The circuit pack is having problems
transmitting data to the packet bus, thus affecting the conveyance of signaling information
over the D channel. Specifically, this error occurs when the packet-bus transmit buffers
overflow. This condition probably indicates a hardware problem.
и возвращается в норму после: Error Type 1793: UDS1 Interface circuit pack or DS1 Interface Media Modulekm is out of
service. Look for and resolve UDS1-BD or MG-DS1 errors in the Hardware Error Log.
Моглабы заподозрить железо, но настораживает зависимость от времени.
Что может быть еще причиной и как бы это протестировать.
Заранее спасибо.
-
guest_avaya
- Постоянный участник форума
- Сообщения: 170
- Зарегистрирован: Ср 27 янв 2010, 10:40
Re: Ошибки DS1
Сообщение
guest_avaya » Пт 10 дек 2010, 14:48
Если этот ds1 смотрит в сторону провайдера «блаблателеком», то имеет смысл сначала поговорить с ними, что происходит у них каждую ночь 
Странно что они вам не говорят когда проблеммы на потоке, мне обычно звонят даже вне рабочее время если ошибки на потоке!
-
steysha
- Постоянный участник форума
- Сообщения: 152
- Зарегистрирован: Пн 02 фев 2009, 19:29
Сообщение
steysha » Пт 10 дек 2010, 15:29
Провайдеры то говорят, но очень размыто (что-то типа у вас связь пропадает +) ) и никак не хотят мне давать ошибки приходящие на их сторону..
-
Pterodahtil
- Постоянный участник форума
- Сообщения: 2803
- Зарегистрирован: Пн 07 июл 2008, 16:51
- Откуда: Москва
- Контактная информация:
Сообщение
Pterodahtil » Пт 10 дек 2010, 16:40
может промежуточное железо сбоит?
Настрою IP Office и классическую Avaya
-
guest_avaya
- Постоянный участник форума
- Сообщения: 170
- Зарегистрирован: Ср 27 янв 2010, 10:40
Сообщение
guest_avaya » Пн 13 дек 2010, 07:08
Можно тесты погонять test board, mst повесить на транк, если нету mst то list trace tac на ночь вдруг, что еще всплывет.
(k) Error Type 3585 appears when the switch receives an ISDN RESTART message for an
●
ISDN trunk. Calls are cleared with the RESTART message. Therefore, this Error Type may
be associated with a dropped call report from a user.
The following Aux Data values for Error Type 3585 represent the trunk’s ISDN call state at
the time the unexpected request to restart the channel was received from the remote
switch. This information can be useful if dropped calls (cutoffs) are reported by users of the
ISDN-PRI trunks.
The meanings of Aux Data values are shown below; ignore any others.
Table 88: Aux Data Values
Aux Data
Cause
0
A idle trunk received a restart.
10
A call in a stable, talking state was cleared unexpectedly by the
far-end with an ISDN RESTART message. This state is called the
«active» state.
4
A call that has not reached the active state, but has at least
7
reached a ringing state, was cleared unexpectedly by the far-end
8
with an ISDN RESTART message.
260
263
1
A call that has not yet reached a ringing state was cleared
3
unexpectedly by the far-end with an ISDN RESTART message.
6
9
265
11
A call that was in the process of clearing anyway has been
12
cleared by the far-end with an ISDN RESTART message. If this
19
condition occurs frequently, it may mean that the far-end is
531
attempting to clear trunks that it thinks are in a «hung» state. The
RESTART message brings the trunk to an idle condition.
267
268
(l) An ISDN trunk selected by the near-end has been rejected 10 times by the far-end
●
without a successful call. This may indicate a service state mismatch between the
near-end and far-end for this trunk that is effecting the end user (that is, customer receives
unexpected intercept tones when accessing ISDN trunks). This may indicate that the ISDN
trunk is not administered on the far-end.
The Aux field contains the physical name of the ISDN trunk in decimal. Then, verify that the
far-end has this trunk administered.
The Warning alarm will be retired automatically whenever an outgoing or incoming call that
uses this trunk is answered by the called endpoint. If problems persist, then busy-out the
ISDN trunk to take it out of the hunt group.
ISDN-TRK (DS1 ISDN Trunk)
Issue 1.1 June 2005
191
Communication Manager Maintenance-Object Repair Procedures
542 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
t. Error Type 3329: The on-board LANHO chip is insane, possibly due to a problem in
packet-bus arbitration, the transmission line frame, or the circuit pack itself. The circuit pack
cannot talk to the packet bus.
If the packet bus is alarmed:
1. Resolve any PKT-BUS errors. The probability of this error being related to a packet-bus
problem increases with the number of other circuit packs using the bus that are also
showing this error.
If the packet bus is not alarmed:
2. Reset the circuit pack (reset board location).
3. If the problem persists, replace the ATM-EI circuit pack.
If the system has a duplicated PNC, and the in-line error received is from an active ATM-EI,
the system switches to the standby PNC.
!
CAUTION:
CAUTION:
If the system does not have duplicated PNC, services to the PN could be
disrupted.
u. Error Types 3585 and 3586: (Major board alarm) A failure of critical components involved
in the operation of the circuit pack, and the switch can no longer recognize the circuit pack.
If the system has a duplicated PNC and the in-line error received is from an active ATM-EI,
the system switches to standby PNC.
!
CAUTION:
CAUTION:
If the system does not have duplicated PNC, services to the PN could be
disrupted.
Error Type 3585
Aux Data (Error Type 3585 only):
Aux
Data
Description
1
ATM framer failure
2
NCE failed (only from ATM-EIs in PN)
4
TDM_PLD_FAILED
5
DSP_ALL FAILED
6
Receive Network Processor (RNP) failure
7
Transmit Network Processor (TNP) failure
8
MEMORY read/write failure