Talkiet:jaysin: I was not trying to tell YOU how UFB works. I was trying to explain to the original poster what might be causing the issue. I did not address anyone else to begin with.
I thought the idea of such forums was for people to try to explain / help with other peoples issues. Not to interrupt such conversation to flex the testosterone of your I.T. knowledge.
The fact that I have worked extensively in the LFC space does give me some sort of knowledge about how UFB works.
However, I don't see the need to tell other people about my vast knowledge of UFB, and the details I know, as it won't make me sleep better at night, and I don't see the need in portraying a large ego on a geek forum.
So, if your aim here is to try to put other people, myself in this case, in their place with your protruding extensive phallic like knowledge of I.T. you have failed, sorry.
Wow.
To be fair, you were wrong about our traffic shaping and tried to maintain that position for a while, you are wrong about the 24 way split (at least as far as what's actually deployed), and you are paying WAY too much attention to the DW PON bandwidth for an OLT port.
I'll happily flex appropriate muscles if people come and post wrong information here, more so if they carry on and defend statements I know for a fact are wrong.
You are factually correct about the PON bandwidth split (at least in the DS direction, US is a different bandwidth and a completely different method of BW sharing) but you're wrong to think it would be having a real world impact.
Cheers - N
Taffic shaping, sure, I may have been incorrect. But this isn't specific to UFB.
I did not once state that what I was told, by a Spark rep (you are a Spark rep here right?) were fact, and admitted that I was just relaying what I was told.
And again, this was in Hamilton, which uses a 24 way splitter model (in general) as per the LFC policy.
Spark, or Chorus, is not the LFC in Hamilton, so you do not know for a fact my statements are wrong, and flexing your I.T. muscles, in this case at least, is not required.
Although, if doing so makes you feel better about yourself, then feel free. It is rather amusing to be honest.
I'm quite aware that upstream traffic management is done via PCP tags, but myself and the original query didn't get that far, so there was no reason to go into it.
And now, I am not wrong to think splitters via an OLT port would have a real impact.
This is because I have been in projects which have physically tested OLT capabilities, not on Chorus / Alcatel / Ericsson equipment by the way, which does show that physical capabilty via an OLT and split ratio do indeed impact on services. This would be the reason higher CIR's are more expensive. This statement isn't to try to prove my knowledge or anything, simply backing up the statement of why I know this to be fact.
I think the main point here has been missed. This issue, at least at a layer 1 and layer 2 issue, was in HAMILTON.
As such, Spark has nothing to do with the capability of the layer 1 or layer 2 performance here.
People need to remember that NZ broadband does not solely revolve around Spark or Chorus capability.
There are other I.T. companies in N.Z. that have affect the broadband performance in N.Z.
Trusted
ID Verified
