You in the wrong directory. Those are SQL database files.
Check hamody's post on 6680 paths.
Sent from my ADR6300
Bam_log.LDF
Alarm.mdf
Alarm_log.LDF
Bam.mdf
Perf_log.LDF
Perf.mdf
You in the wrong directory. Those are SQL database files.
Check hamody's post on 6680 paths.
Sent from my ADR6300
Edify...
I did some EVDO access failure analysis. The highest release cause is
55c.jpg
There's no details of the release codes in the online help manual. Can anyone say what would be the reason for this release cause?
RelCause: 55c
Macro name:
RRM_FAIL_PILOT_NOT_SUPPORT_SVR_TYPE
Detail Explain:
Pilot not supporting call service type
Edify...
Another one is for EVDO call drop analysis:
272f.jpg
Can anyone identify this timer? May be hamody??? BTW there are no alarms in the BSC for this.
RelCause: 272f
Macro name:
CCB_FAIL_DO_DATA_FWD_REQ_TIMEOUT
Detail Explain:
Waiting for SDU_CCM_DO_DATA_FWD_REQ timed out
Cause:
The timer is not configured properly, or the internal message interaction fails. Perform analysis based on alarms and assertions.
Edify...
I've found out that all the sites having problems in this analysis have been EVDO rev. 0 sites. So what's happening is that every time a rev. A modem or phone makes a connection request, the system denies it service and makes it fallback to rev. 0. That's why it says in cause that pilot does not support this service. So this one is figured out.
Upgrading this sites to rev. A would solve this issue since we have more rev. A modems than rev. 0.
I'll find out on the one below following week.
Sent from my ADR6300
Edify...
Finally understood this one too. 272f.
Sent from my ADR6300
Last edited by T_ADD; 2013-03-21 at 05:26 PM
Edify...
hi,carver!the med file of sendspace is invalid now!could you send me a copy to my email herdkid@gmail.com,thanks!
Bookmarks