Motorola UBR Issue

[Ignitionnet]

Originally Posted by III

That's not for me to find out or even care about, it's for you to get the correct reference so you may chase the progress.

It would seem the fault and fault reference you have been chasing for months has been resolved since there have been 5 code updates to the Moto kit

At least two of those were security patches, another one fixed cosmetic issues amongst other things. Another added additional line card support. Unsure about number 5 but given the T3/T4 issue is still under investigation it would appear Motorola can't replicate.

[III]

I'm not willing to post what the 5th is on a forum. You are correct on all counts you have posted sir.

[Welshchris]

all im saying is that why would Virgin give the same reference number to so many people if they wernt putting the issues under the same number? I could understand them making a mistake an issuing it to one or maybe two people but not so many.

---------- Post added at 21:57 ---------- Previous post was at 21:56 ----------

Originally Posted by Ignitionnet

At least two of those were security patches, another one fixed cosmetic issues amongst other things. Another added additional line card support. Unsure about number 5 but given the T3/T4 issue is still under investigation it would appear Motorola can't replicate.

tell em to go and sit in someones house and watch would be the easiest way LOL.

[III]

With all due respect Chris the amount of people who queried this fault on the groups, I could count on one hand. ( I lurk on the groups you see )

Its very possible that the reference and 'fault' is still open for investigation, that investigation would include as I said local networks; from BSR right down to drop cable.

Non of this changes the fact that what you are referencing is for just two instances in Scotland.

[Ignitionnet]

Originally Posted by Welshchris

tell em to go and sit in someones house and watch would be the easiest way LOL.

Sadly that would just be 'observation' not 'replication'. Replication has to be done in controlled environments to eliminate things such as local network fluctuations, CPE issues, etc. Basically a known good modem plugged into a splitter which then goes straight to a BSR via a lot of attenuators.

[Welshchris]

Originally Posted by III

With all due respect Chris the amount of people who queried this fault on the groups, I could count on one hand. ( I lurk on the groups you see )

Its very possible that the reference and 'fault' is still open for investigation, that investigation would include as I said local networks; from BSR right down to drop cable.

Non of this changes the fact that what you are referencing is for just two instances in Scotland.

Well it doesnt change the fact either that people from Preston, Lancs and Belfast aswell as myself in Swansea were given the same reference number for the same fault either.

---------- Post added at 23:01 ---------- Previous post was at 23:00 ----------

Originally Posted by Ignitionnet

Sadly that would just be 'observation' not 'replication'. Replication has to be done in controlled environments to eliminate things such as local network fluctuations, CPE issues, etc. Basically a known good modem plugged into a splitter which then goes straight to a BSR via a lot of attenuators.

Whats the point of testing a good modem when they should be testing one with a fault, kind of defeats the object lol

[Peter_]

Originally Posted by Welshchris

Well it doesnt change the fact either that people from Preston, Lancs and Belfast aswell as myself in Swansea were given the same reference number for the same fault either.

Well they were given incorrect information then as they cannot all be connected to the same kit.

Originally Posted by Welshchris

Whats the point of testing a good modem when they should be testing one with a fault, kind of defeats the object lol

Are you for real!

They use a good modem to ensure the accuracy of any test, if they used a duff modem how would they know were the fault was.

[Ignitionnet]

Originally Posted by Welshchris

Whats the point of testing a good modem when they should be testing one with a fault, kind of defeats the object lol

Interests Computer Hardware
Occupation IT Tech

As you're quite nocturnal unsure if you're between jobs at the moment but if you aren't I kinda hope you don't work in a support role as troubleshooting doesn't appear to be your strong suit.

Troubleshooting is a form of problem solving most often applied to repair of failed products or processes. It is a logical, systematic search for the source of a problem so that it can be solved, and so the product or process can be made operational again. Troubleshooting is needed to develop and maintain complex systems where the symptoms of a problem can have many possible causes. Troubleshooting is used in many fields such as engineering, system administration, electronics, automotive repair, and diagnostic medicine. Troubleshooting requires identification of the malfunction(s) or symptoms within a system. Then, experience is commonly used to generate possible causes of the symptoms. Determining which cause is most likely is often a process of elimination - eliminating potential causes of a problem. Finally, troubleshooting requires confirmation that the solution restores the product or process to its working state.

Using a known good modem eliminates the modem as a cause, plugging the modem basically straight into a CMTS eliminates HFC leaving only CMTS and associated software / hardware. If fault cannot be replicated CMTS as a stand-alone root cause eliminated and search for a trigger for the fault from HFC layer begins.

Translating this into your interest of computer hardware if a PC doesn't boot and doesn't give much clue why you either change the components out for known good ones, one at a time, until it does boot or remove unnecessary components one at a time, ensuring that the original components are always replaced before removing the next one.

Same process dealing with faulty RAM when you have multiple sticks, remove one and see if POST still whines, put it back and remove another, etc, until POST is successful. Same story here just different scale, methodical, controlled elimination of potential causes one at a time which requires full control of the test environment.

[Welshchris]

FFS! cant u people take a joke!!!

And as for them giving out wrong info Moldova, it seems weird they have given out wrong info to so many people, so someone somewhere has put that reference number into the systems for the national BSR issues.

[Peter_]

Originally Posted by Welshchris

FFS! cant u people take a joke!!!

And as for them giving out wrong info Moldova, it seems weird they have given out wrong info to so many people, so someone somewhere has put that reference number into the systems for the national BSR issues.

I do know when you are joking Chris hence the the blue smilies.

Those people giving out duff info are the issue as they are taking the easy route just to get you off the phone.

Those people annoy me because they cause you to call back into the centre.

[darwin]

There is apost on the newsgroups suggesting that the fault is being upgraded to a national fault.

[Welshchris]

thats because it is !