Menu
Reply
  • 24
  • 1
  • 1
lmacilroy
On our wavelength
303 Views
Message 1 of 17
Flag for a moderator

Problems with Connection/SH2

Lately I have been having some big problems regarding my SH2 and connection. I also have another issue with my service. Please bare in mind that I do have someone on the case regarding my SH2 but need additional help to resolve ALL matters regarding my service. To begin with several weeks ago I had an engineer come out and repair the line coming into my home as it had been snipped. All went well the engineer arrived and repaired this issue. Upon doing his final checks he noticed that the power on the line coming into my property was below a satisfactory level. He tested the connection from in my house then tested the cable outside and at the cabinet. It was determined that the cabling coming to my house from the cabinet was defective and in his opinion needed to be replaced. He said he would discuss this with his supervisor regarding this. I left it a couple of days and rang them up regarding this. After talking to several helpdesk operators, I was asked to ring another number as I needed a "field engineer" to attend and replace the cabling. I rang the number (0800 073 1132 Option 1) and talked to someone regarding this. After several days I rang back up and was told someone would be out that day. No engineer turned up and that particular problem STILL exists - ie the cable STILL needs to be investigated AND replaced as necessary.

 

Onto my current problem. Ive noticed in the last week, and has happened a couple of times - once late last week and again as I type this post. I noticed that I was suffering with some small latency problems when connected to the web or gaming (high pings/slow loading web pages). As would be the usual route to resolve issues of this kind, I reset my SH2 (which is setup in router mode). Upon doing this the SH then goes into intermittent connectivity whereby it connects/disconnects over and over at random interval - for several hours upon end. Upon the first instance of this happening I did ring up VM and a helpdesk op made some checks on my equipment and determined there was a problem with the SH itself. I DO have an engineer coming out tomorrow (ie 7/9/16) between 9am and 12pm but I am annoyed as it felt like the op who answered my call did not care for my issue. To say the least being left for nearly 6 days with this issue with my SH2 potentially happening several times (albeit its only happened twice that is besides the issue). I rang back up that same evening saying that the appt I was given was NOT acceptable and proceeded to attempt to get an earlier appt ie within 24-48 hours of which the next operator roadblocked me and said nothing was absolutely available. I then proceeded to request to make this into an official complaint - guess what - I was roadblocked again. I asked to speak to a supervisor/manager _ was told no one was available. I eventually got the operator to arrange a call back from a supervisor/manager within an hour. That callback was NEVER made. Obviously you can check logs regarding this and confirm.

 

I want to know what is going to be done regarding this. The service I have received just lately is beyond ALL belief and has left me to believe no one at VM gives a damn about the service they provide.

 

Anyway heres my netork log - I seem to be getting a ranging response error with my SH2.

 

06/09/2016 05:09:43 GMT06/09/2016 05:09:43 GMTWarning (5)66050310Auth Success - Web login successful.
06/09/2016 05:09:35 GMT06/09/2016 05:09:35 GMTError (4)68000407TOD established
Time Not EstablishedTime Not EstablishedNotice (6)84000510Downstream Locked Successfully
06/09/2016 04:54:12 GMT06/09/2016 04:54:12 GMTCritical (3)82000600Unicast Maintenance Ranging attempted - No response - Retries exhausted
06/09/2016 04:54:12 GMT06/09/2016 04:54:12 GMTCritical (3)82000300Ranging Request Retries exhausted
06/09/2016 04:54:11 GMT06/09/2016 04:54:11 GMTCritical (3)82000200No Ranging Response received - T3 time-out
06/09/2016 04:54:11 GMT06/09/2016 04:54:11 GMTCritical (3)82000200No Ranging Response received - T3 time-out
06/09/2016 04:54:11 GMT06/09/2016 04:54:11 GMTCritical (3)82000200No Ranging Response received - T3 time-out
06/09/2016 04:54:10 GMT06/09/2016 04:54:10 GMTCritical (3)82000200No Ranging Response received - T3 time-out
06/09/2016 04:54:10 GMT06/09/2016 04:54:10 GMTCritical (3)82000200No Ranging Response received - T3 time-out
06/09/2016 04:54:10 GMT06/09/2016 04:54:10 GMTCritical (3)82000200No Ranging Response received - T3 time-out
06/09/2016 04:54:09 GMT06/09/2016 04:54:09 GMTCritical (3)82000200No Ranging Response received - T3 time-out
06/09/2016 04:54:09 GMT06/09/2016 04:54:09 GMTCritical (3)82000200No Ranging Response received - T3 time-out
06/09/2016 04:54:09 GMT06/09/2016 04:54:09 GMTCritical (3)82000200No Ranging Response received - T3 time-out
06/09/2016 04:54:09 GMT06/09/2016 04:54:09 GMTCritical (3)82000200No Ranging Response received - T3 time-out
06/09/2016 04:54:08 GMT06/09/2016 04:54:08 GMTCritical (3)82000200No Ranging Response received - T3 time-out
06/09/2016 04:54:08 GMT06/09/2016 04:54:08 GMTCritical (3)82000200No Ranging Response received - T3 time-out
06/09/2016 04:54:08 GMT06/09/2016 04:54:08 GMTCritical (3)82000200No Ranging Response received - T3 time-out
06/09/2016 04:54:08 GMT06/09/2016 04:54:08 GMTCritical (3)82000200No Ranging Response received - T3 time-out
06/09/2016 04:54:07 GMT06/09/2016 04:54:07 GMTCritical (3)82000200No Ranging Response received - T3 time-out
0 Kudos
Reply
  • 3.88K
  • 120
  • 203
Forum Team (Retired) Adam_L
Forum Team (Retired)
245 Views
Message 2 of 17
Flag for a moderator

Re: Problems with Connection/SH2

Hi Imacilroy, 

 

Thanks for posting! I am sorry to hear about your issues with your broadband connection and needing to reboot the router in order to resolve the issues. I offer my apologies for any bother.

 

I've tested things from here and I noticed that all of your downstream power levels are too low and there's a large number of T3 and T4 time outs inside the Hubs logs. 

 

An engineer will be required to attend in order to resolve this for you, I will send you a PM (Purple envelope at the top) detailing what's required to proceed with making the booking.

 

Please respond to me there and I'll get this all sorted for you.

 

Take care, 

Thanks, 

Adam.


Tech fan? Have you read our Digital life blog yet? Check it out


0 Kudos
Reply
  • 24
  • 1
  • 1
lmacilroy
On our wavelength
226 Views
Message 3 of 17
Flag for a moderator

Re: Problems with Connection/SH2

Had the guys out today to resolve my issue. Wednesday had ground work team laying in new conduit and cable from cabinet to premises. VM engineer arrived earlier this morning and swapped the cable lines over. Things seem to be working fairly well and checked my router status. Below you can see the results of my down channel stats. With the old cable my Power level was regularly hitting -6.0 dBmV which I know is way way down below par.

The power levels are now up to an average of between -2 and -3 dBmV. My question for this now is are these acceptible levels or should be they be higher. I really dont want to go through more of the issues that I have experienced over the last 3 months or so.

Just one last note...I am still getting T3 ranging response errors in my sh2 network log.

Frequency (Hz)507000000515000000523000000531000000539000000547000000555000000563000000
Lock Status(QAM Lock/FEC Sync/MPEG Lock)LockedLockedLockedLockedLockedLockedLockedLocked
Channel ID1314151617181920
Modulation256QAM256QAM256QAM256QAM256QAM256QAM256QAM256QAM
Symbol Rate (Msym/sec)6.9520006.9520006.9520006.9520006.9520006.9520006.9520006.952000
Interleave DepthI=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
Power Level (dBmV)-1.99-2.23-2.45-2.52-2.62-2.65-2.79-2.93
RxMER (dB)37.0937.3637.0937.0937.6437.3637.3637.09
Pre RS Errors
10941204125412461351537414011490
Post RS Errors
894967983944998924979981
0 Kudos
Reply
  • 24
  • 1
  • 1
lmacilroy
On our wavelength
211 Views
Message 4 of 17
Flag for a moderator

Re: Problems with Connection/SH2

Im wondering if someone can attend to this issue for me please. yesterday had engineer round to connect new cable to house replacing the old one that was causing major issues. Noticed some errors on my network log and even more today.

Im still suffering with T3 Time outs/ranging response received errors. Today Ive also had quite a few T4 time out errors too. I would have thought these issues would have now been resolved with the cable replacement but they have not. Id like VM to attend to this post and help with next stage of resolution.

0 Kudos
Reply
  • 24
  • 1
  • 1
lmacilroy
On our wavelength
187 Views
Message 5 of 17
Flag for a moderator

Re: Problems with Connection/SH2

"Knock Knock"...Is anyone home? Hello? is anyone there?...i seem to still be having a slight problem...Can you help me please....drowning...drowning...eyes getting heavy....shallow breathing..."BEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEP". Oh damn my life support seems to have died on me....just like VM's customer service has itself...indeed drawn its last breath!

 

Do I really have to resort to this sort of sarcastic humour to try and get a response....

0 Kudos
Reply
  • 24
  • 1
  • 1
lmacilroy
On our wavelength
164 Views
Message 6 of 17
Flag for a moderator

Re: Problems with Connection/SH2

VM...I really AM disappointed that my post is not getting ANY response at all. **bleep** poor customer service....Im now considering switching to BT or SKY as you obviously have NO intention of helping with this issue or even replying to this message.

I so want to cuss and curse right now but I wont let your ignorance goad me into that sort of response.

I will be considering placing a complaint in with you. As none of you really should be doing this job if you cannot reply to a post that has been sitting here for well over a week!

0 Kudos
Reply
  • 24
  • 1
  • 1
lmacilroy
On our wavelength
144 Views
Message 7 of 17
Flag for a moderator

Re: Problems with Connection/SH2

JUST TO LET THE NON-EXISTENT VM FORUM STAFF....IM STILL HAVING TROUBLE WITH MY CONNECTION. I RANG UP A FEW DAYS AGO COMPLAINING REGARDS MY CONNECTION...WAS TOLD BY PERSON THEY WERE GONNA RESET SOMETHING THEIR END AND ALL WOULD BE GOOD. WELL IT ISNT. IM STILL GETTING A LOT OF T3 RANGING RESPONSE TIMEOUTS AND T4 TIMEOUTS (Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received ).

Are you guys actually gonna give me some HELP or not? This is what I want to know. If i was to go by the law this could be classed as a "fit for Purpose" issue. As my broadband and VM's customer service are NOT fit for its intended purpose.

Now Im going to ask once more...GET THIS CRAP SORTED; And if your just delaying ANY response or resolution of my problem because Im getting irate and annoyed and hence cussing in my post then I suggest you think about this...WHY am i getting like this? That would be down to the poor CS im getting prior to my anger and irratation at how you take such a long time to respond. Its qiuite obvious the forum staff cannot cope here - maybe its time you moved on and let someone who KNOWS how to deal with issues take over!

0 Kudos
Reply
  • 24
  • 1
  • 1
lmacilroy
On our wavelength
129 Views
Message 8 of 17
Flag for a moderator

Re: Problems with Connection/SH2

19/10/2016 00:43:02 GMT19/10/2016 00:43:02 GMTCritical (3)82000500Started Unicast Maintenance Ranging - No Response received - T3 time-out
19/10/2016 00:43:02 GMT19/10/2016 00:43:02 GMTCritical (3)82000500Started Unicast Maintenance Ranging - No Response received - T3 time-out
19/10/2016 00:43:02 GMT19/10/2016 00:43:02 GMTCritical (3)82000500Started Unicast Maintenance Ranging - No Response received - T3 time-out
19/10/2016 00:43:02 GMT19/10/2016 00:43:02 GMTCritical (3)82000500Started Unicast Maintenance Ranging - No Response received - T3 time-out
19/10/2016 00:43:02 GMT19/10/2016 00:43:02 GMTCritical (3)82000500Started Unicast Maintenance Ranging - No Response received - T3 time-out
19/10/2016 00:43:02 GMT19/10/2016 00:43:02 GMTCritical (3)82000500Started Unicast Maintenance Ranging - No Response received - T3 time-out
19/10/2016 00:43:02 GMT19/10/2016 00:43:02 GMTCritical (3)82000500Started Unicast Maintenance Ranging - No Response received - T3 time-out
19/10/2016 00:43:02 GMT19/10/2016 00:43:02 GMTCritical (3)82000500Started Unicast Maintenance Ranging - No Response received - T3 time-out
19/10/2016 00:43:02 GMT19/10/2016 00:43:02 GMTCritical (3)82000500Started Unicast Maintenance Ranging - No Response received - T3 time-out
19/10/2016 00:43:02 GMT19/10/2016 00:43:02 GMTCritical (3)82000500Started Unicast Maintenance Ranging - No Response received - T3 time-out
19/10/2016 00:43:02 GMT19/10/2016 00:43:02 GMTCritical (3)82000500Started Unicast Maintenance Ranging - No Response received - T3 time-out
19/10/2016 00:43:02 GMT19/10/2016 00:43:02 GMTCritical (3)82000500Started Unicast Maintenance Ranging - No Response received - T3 time-out
19/10/2016 00:43:02 GMT19/10/2016 00:43:02 GMTCritical (3)82000500Started Unicast Maintenance Ranging - No Response received - T3 time-out
19/10/2016 00:43:02 GMT19/10/2016 00:43:02 GMTCritical (3)82000500Started Unicast Maintenance Ranging - No Response received - T3 time-out
19/10/2016 00:43:02 GMT19/10/2016 00:43:02 GMTCritical (3)82000500Started Unicast Maintenance Ranging - No Response received - T3 time-out
19/10/2016 00:43:02 GMT19/10/2016 00:43:02 GMTCritical (3)82000500Started Unicast Maintenance Ranging - No Response received - T3 time-out
19/10/2016 00:43:02 GMT19/10/2016 00:43:02 GMTCritical (3)82000500Started Unicast Maintenance Ranging - No Response received - T3 time-out
19/10/2016 00:43:02 GMT19/10/2016 00:43:02 GMTCritical (3)82000500Started Unicast Maintenance Ranging - No Response received - T3 time-out
19/10/2016 00:43:02 GMT19/10/2016 00:43:02 GMTCritical (3)82000500Started Unicast Maintenance Ranging - No Response received - T3 time-out
19/10/2016 00:43:02 GMT19/10/2016 00:43:02 GMTCritical (3)82000500Started Unicast Maintenance Ranging - No Response received - T3 time-out
19/10/2016 00:43:02 GMT19/10/2016 00:43:02 GMTCritical (3)82000500Started Unicast Maintenance Ranging - No Response received - T3 time-out
19/10/2016 00:43:02 GMT19/10/2016 00:43:02 GMTCritical (3)82000500Started Unicast Maintenance Ranging - No Response received - T3 time-out
19/10/2016 00:43:02 GMT19/10/2016 00:43:02 GMTCritical (3)82000500Started Unicast Maintenance Ranging - No Response received - T3 time-out
19/10/2016 00:43:02 GMT19/10/2016 00:43:02 GMTCritical (3)82000500Started Unicast Maintenance Ranging - No Response received - T3 time-out
19/10/2016 00:43:02 GMT19/10/2016 00:43:02 GMTCritical (3)82000500Started Unicast Maintenance Ranging - No Response received - T3 time-out
19/10/2016 00:43:02 GMT19/10/2016 00:43:02 GMTCritical (3)82000500Started Unicast Maintenance Ranging - No Response received - T3 time-out
19/10/2016 00:43:02 GMT19/10/2016 00:43:02 GMTCritical (3)82000500Started Unicast Maintenance Ranging - No Response received - T3 time-out
19/10/2016 00:43:02 GMT19/10/2016 00:43:02 GMTCritical (3)82000500Started Unicast Maintenance Ranging - No Response received - T3 time-out
19/10/2016 00:43:02 GMT19/10/2016 00:43:02 GMTCritical (3)82000500Started Unicast Maintenance Ranging - No Response received - T3 time-out
19/10/2016 00:43:02 GMT19/10/2016 00:43:02 GMTCritical (3)82000500Started Unicast Maintenance Ranging - No Response received - T3 time-out
19/10/2016 00:43:02 GMT19/10/2016 00:43:02 GMTCritical (3)82000500

Started Unicast Maintenance Ranging - No Response received - T3 time-out

 

Frequency (Hz)547000000507000000515000000523000000531000000539000000555000000563000000
Lock Status(QAM Lock/FEC Sync/MPEG Lock)LockedLockedLockedLockedLockedLockedLockedLocked
Channel ID1813141516171920
Modulation256QAM256QAM256QAM256QAM256QAM256QAM256QAM256QAM
Symbol Rate (Msym/sec)6.9520006.9520006.9520006.9520006.9520006.9520006.9520006.952000
Interleave DepthI=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
Power Level (dBmV)-2.15-1.52-1.72-1.84-1.91-2.01-2.29-2.43
RxMER (dB)36.8436.8437.0936.6136.8436.3935.4235.78
Pre RS Errors
11901201108011091066124711591243
Post RS Errors
9849709699599401070920

999

0 Kudos
Reply
  • 4.95K
  • 146
  • 282
Forum Team (Retired) BenD_H
Forum Team (Retired)
113 Views
Message 9 of 17
Flag for a moderator

Re: Problems with Connection/SH2

Hi lmacilroy,

 

Many thanks for posting your message, I'm so very sorry that I wasn't here to answer you sooner, you slipped through our fingers. 

 

I have been back into the account and from what I can see confirms what you mentioned about the T3 timeouts and T4 on the hub. 

 

This is something that would certainly need an engineer to help resolve and bring the Hub back to normal working levels again. If you can have a little look inside your 'Inbox', you'll see I've sent you a 'Private Message'. You can find this at the top right of the page, purple envelope Smiley Happy

 

Keep in touch.

Ben


Who's who? Find out more about our community members. Good folk to know


0 Kudos
Reply
  • 24
  • 1
  • 1
lmacilroy
On our wavelength
92 Views
Message 10 of 17
Flag for a moderator

Re: Problems with Connection/SH2

Just an update and to document whats been happening with my service.

This last saturday (29th Oct 2016) had an engineer come out to check what was happening with our broadband. He noted that the physical connections to the cabinet were all loose and therefore tightened them up. The cabinet door itself as he quoted was "missing" so dont know whats going on there!

Anyway prior to him tightening the connections in the cabinet he noted that our SNR ratio's were quite poor and would, realistically, be the cause of our T3/T4 timeouts. Upon tightening the connections he checked our SNR and it had gone up quite substantially so that was sorted out (hopefully). Once he had completed checks he asked us to keep an eye on our connection to see any other issues occur.

Now on to today. Seeing as I had not restarted the router since the visit I decided to do this. I did a soft reset by restarting the router from in the router login page. Before I did this I did check the network log and noticed that there were a bucket load of T4 timeouts. This is where my current problem begins. I am now getting the drop in's/drop out's on my connection. I restarted approximately 11.45am and the connection is disconnecting/connecting continually. From past experience I notice this will go on for a good hour or two before settling down and finally keeping a constant connection. Anyway at 12PM i decided to do a full reboot by disconnecting power to my SH2 waiting 30 seconds or so and then reconnecting. Unfortunately no resolution as while I am writing this I have had another disconnection. The disconnections last anything between 2 mins to around 5 or 6 mins before finally connecting back up. That connection will then last anything up to 10 mins before disconnecting again. At present I notice there are a (and i quote again) "bucket" load of T3 timeouts this time. So there is still something wrong with both downstream (please note earlier in post regarding T4 timeouts) and upstream channels even though it may not seem like that at present. Before I forget prior to soft resetting I noticed that there was a "TCS Fail" whatever the heck that means! I still feel this issue is to do jointly with both the cabling and my SH2 although the engineer said it was most likely nothing to do with my SH2 with the problems I am experiencing.

With the total length of time that has been spent on this since my first post over a month ago and my still having problems. I wonder if the need for a tier 3 engineer to attend and diagnose the problem and come up with a relevant fix is on the cards as I feel there is a need for this.

Please take a look at the pretty tables I have created below for you to illustrate my downstream/upstream channels and network log.

Love and Kisses

A disgruntled customer. :/

  DS-1 DS-2 DS-3 DS-4 DS-5 DS-6 DS-7 DS-8

Frequency (Hz)539000000507000000515000000523000000531000000547000000555000000563000000
Lock Status(QAM Lock/FEC Sync/MPEG Lock)LockedLockedLockedLockedLockedLockedLockedLocked
Channel ID1713141516181920
Modulation256QAM256QAM256QAM256QAM256QAM256QAM256QAM256QAM
Symbol Rate (Msym/sec)6.9520006.9520006.9520006.9520006.9520006.9520006.9520006.952000
Interleave DepthI=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
Power Level (dBmV)-2.61-1.99-2.22-2.45-2.57-2.70-2.76-2.85
RxMER (dB)36.8436.6136.8436.3937.0935.4236.8436.39
Pre RS Errors
41622570210333773290827048464654
Post RS Errors
971950289897966952960339

 

  US-1 US-2 US-3 US-4

Channel Type2.02.02.02.0
Channel ID8765
Frequency (Hz)25800000326000003940000046200000
Ranging StatusTimeout T4Timeout T4Timeout T4Success
Modulation16QAM16QAM16QAM16QAM
Symbol Rate (Sym/sec)5120000512000051200005120000
Mini-Slot Size4444
Power Level (dBmV)40.2540.2540.2542.75
T1 Timeouts0000
T2 Timeouts0000
T3 Timeouts4041410
T4 Timeouts4847470

 

First TimeLast TimePriorityError NumberDescription
01/11/2016 12:43:48 GMT01/11/2016 12:43:48 GMTCritical (3)82000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
01/11/2016 12:43:48 GMT01/11/2016 12:43:48 GMTCritical (3)82000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
01/11/2016 12:43:48 GMT01/11/2016 12:43:48 GMTCritical (3)82000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
01/11/2016 12:43:48 GMT01/11/2016 12:43:48 GMTCritical (3)82000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
01/11/2016 12:43:48 GMT01/11/2016 12:43:48 GMTCritical (3)82000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
01/11/2016 12:43:48 GMT01/11/2016 12:43:48 GMTCritical (3)82000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
01/11/2016 12:43:48 GMT01/11/2016 12:43:48 GMTCritical (3)82000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
01/11/2016 12:43:48 GMT01/11/2016 12:43:48 GMTCritical (3)82000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
01/11/2016 12:43:48 GMT01/11/2016 12:43:48 GMTCritical (3)82000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
01/11/2016 12:43:48 GMT01/11/2016 12:43:48 GMTCritical (3)82000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
01/11/2016 12:43:48 GMT01/11/2016 12:43:48 GMTCritical (3)82000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
01/11/2016 12:43:48 GMT01/11/2016 12:43:48 GMTCritical (3)82000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
01/11/2016 12:43:48 GMT01/11/2016 12:43:48 GMTCritical (3)82000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
01/11/2016 12:43:48 GMT01/11/2016 12:43:48 GMTCritical (3)82000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
01/11/2016 12:43:48 GMT01/11/2016 12:43:48 GMTCritical (3)82000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
01/11/2016 12:43:48 GMT01/11/2016 12:43:48 GMTCritical (3)82000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
01/11/2016 12:43:48 GMT01/11/2016 12:43:48 GMTCritical (3)82000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
01/11/2016 12:43:48 GMT01/11/2016 12:43:48 GMTCritical (3)82000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
01/11/2016 12:43:48 GMT01/11/2016 12:43:48 GMTCritical (3)82000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
01/11/2016 12:43:48 GMT01/11/2016 12:43:48 GMTCritical (3)82000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
01/11/2016 12:43:48 GMT01/11/2016 12:43:48 GMTCritical (3)82000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
01/11/2016 12:43:48 GMT01/11/2016 12:43:48 GMTCritical (3)82000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
01/11/2016 12:43:48 GMT01/11/2016 12:43:48 GMTCritical (3)82000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
01/11/2016 12:43:48 GMT01/11/2016 12:43:48 GMTCritical (3)82000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
01/11/2016 12:43:48 GMT01/11/2016 12:43:48 GMTCritical (3)82000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
01/11/2016 12:43:48 GMT01/11/2016 12:43:48 GMTCritical (3)82000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
01/11/2016 12:43:48 GMT01/11/2016 12:43:48 GMTCritical (3)82000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
01/11/2016 12:43:48 GMT01/11/2016 12:43:48 GMTCritical (3)82000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
01/11/2016 12:43:48 GMT01/11/2016 12:43:48 GMTCritical (3)82000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
01/11/2016 12:43:48 GMT01/11/2016 12:43:48 GMTCritical (3)82000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
01/11/2016 12:43:48 GMT01/11/2016 12:43:48 GMTCritical (3)82000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
0 Kudos
Reply