Hola ChicosApenas despertándome lue

Hola Chicos

Apenas despertándome luego del troubleshooting, que explico a continuación:

Resumen:
1.-La Falla en este WBTS inicio en Domingo 30. Luego de un cambio de EDCH Y DSCH.
2.-El cliente realizo pruebas de ping con una PC desde todos los salta en la transmision, aunque tiene mucha perdida de paquetes . ver log anexo con pruebas hacia la IP LOCAL 172.25.168.63.
3.-Hoy el cliente piensa reemplazar todo el HW indiqueme si es recomendable dada la situación de afectación del sitio.
4.- El grupo local detecto mal commissioning. EL M-PLANE no estaba configurado en el WBTS. Por dicha razon al principio no había ping desde la RNC y OMS.
5.- Ya tenemos ping hacia las IP del nodo con perdida de paquetes mayores a 1200 bits. Adjunto datafill.
6.- Finalmente el WBTS sube pero queda con intermitencias en el o&m y los WCELL.
7..-El nodo tiene conexión remota para su revisión.

Resultados (Inglês) 1:

Hi guysJust waking me up after the troubleshooting, which I explain below:Summary:1.-the failure in this WBTS home on Sunday 30. After a change of EDCH and DSCH. 2.-the client conducted tests of ping with a PC from all them jumps in the transmission, although has much loss of packages. see annex log evidence towards the LOCAL IP 172.25.168.63.3.-today the customer intends to replace all the HW show me if it is recommended given the State of affectation of the site.4. the local group detected bad commissioning. THE M-PLANE not was configured in the WBTS. For this reason at the beginning there was no ping from the NCR and WHO.5 we have ping to the IP of the node with loss of greater than 1200 bit packages. Deputy datafill.6.-Finally the WBTS rises but remains with intermittently in the or & m and those WCELL. 7.-the node has remote connection for your review.

Resultados (Inglês) 2:

Hi Guys

Just after waking of troubleshooting, I explain below:

Summary:
. 1.-The failure in this WBTS start on Sunday 30. After a change of EDCH And DSCH
2. The client ping tests conducted with a PC all jumps in the transmission, but has a lot of packet loss. see Annex log evidence to the LOCAL IP 172.25.168.63.
3. Today the customer thinks replace the entire HW please show whether it is advisable given the situation affecting the site.
4. The local group detected bad commissioning. THE M-PLANE was not configured in the WBTS. For this reason at first there was no ping from the RNC and WHO.
5. We have ping to the IP node with packet loss higher to 1200 bits. Deputy datafill.
6. Finally WBTS up but remains intermittently in the o & m and WCell.
7 ..- The node has remote connection for review.

Resultados (Inglês) 3:

Hey guysJust waking up after troubleshooting, as follows:Abstract:The flaw in this WBTs home on Sunday. After a change of EDCH and dsch.2. - the client Ping tests with a PC from all the Jumps in the transmission, but has a lot of Packet Loss. See annex with log evidence towards the local IP 172.25.168.63.3. - Today the customer plans to replace all HW lead if advisable given the situation of use of the site.The Local Group detected Bad Commissioning. The M - plane was not configured in the WBTs. For this reason the principle had not Ping from the RNC and who.5. - We already have to ping the IP node with Packet Loss greater than 1200 bits. Deputy DataFill.6. - Finally the WBTs is up but with intermittency in the o & M and the WCell.7. - the Remote Connection node has for its revision.