You can do 32Q plus 2 OFDM blocks as well. But who has that kind of spectrum,
we surely don’t. A 96Mhz block maybe.
But you can’t take the total at 100G and say that’s beyond your scale, you
don’t run at full saturation do you? :)
And in order to run DCAM2s you’ll have to upgrade the RSMs to th
16 connectors per DCAM2 times 6 cards is 96 DS service groups in a
chassis. At ~1.2 Gbps per connector (using 32 SC-QAM DOCSIS 3.0
channels) that's ~ 100gigabits per chassis. Quite a bit above my scale ;- )
The E6k can also do DOCSIS 3.1, which we use today, though I'm not sure
what the capaci
E6K using gen 1 DCAMs can do about 32 service groups give or take, not that
hard to get to a point with splits where you want to go past those numbers. Gen
2 DCAMs double that by going to 16 connectors compared to 8. cBR8 is less than
the E6K.
The point of node splits is to lower customers per
Aaron, I was thinking something similar. I've never once had a node
split require moving a customer to a different CMTS. Even the very old
and (relatively) low capacity 7200 VXR could serve several nodes per
line card and supported several line cards per chassis. Newer cBR8, E6k,
and the like c
@nanog.org
Subject: Re: How to manage Static IPs to customers
*External Email: Use Caution*
I'm curious...
Is it part of the DOCSIS spec that the CMTS terminates L3, or can they bridge
to IEEE 802(.3) and delegate that to some other piece of gear?
I'm unfortunately not familiar with t
The spec allows for bridging or layer 3 but none of the major or certified
manufacturers support bridging on larger platforms. (>1000 modems)
Scott Helms
On Fri, May 8, 2020 at 3:56 PM Brandon Martin
wrote:
> I'm curious...
>
> Is it part of the DOCSIS spec that the CMTS terminates L3, or ca
I'm curious...
Is it part of the DOCSIS spec that the CMTS terminates L3, or can they
bridge to IEEE 802(.3) and delegate that to some other piece of gear?
I'm unfortunately not familiar with the MSO world much at all aside from
a little bit of L1.
--
Brandon Martin
We have a provisioning system (promptlink) that we use to map cable modems
to their static ip addresses. The provisioning system has a gui front end
and it sits on linux and also acts as a dhcp server, etc. This is the same
ip address that we use for cable-helper (like ip-helper on a cmts bundle
On Fri, May 8, 2020 at 8:56 AM Michael Crapse wrote:
>
> On our network(which isn't docsis, granted) we use PPPoE for all static IP
> addresses, because it allows /32 ip address allocations for all home CPE
> routers, upstream, the routers handle routing via ospf to change the path of
> where t
: NANOG list
Subject: Re: How to manage Static IPs to customers
On our network(which isn't docsis, granted) we use PPPoE for all static IP
addresses, because it allows /32 ip address allocations for all home CPE
routers, upstream, the routers handle routing via ospf to change the path of
nting that with DHCP or TR69 usually required other teams'
> involvement and didn't allow portability.
>
> With IPv6 you get PD which helps immensely.
>
> Ed
>
> -Original Message-
> From: NANOG On Behalf Of Javier Gutierrez Guerra
> Sent: Frid
v6 you get PD which helps immensely.
Ed
-Original Message-
From: NANOG On Behalf Of Javier Gutierrez Guerra
Sent: Friday, May 8, 2020 8:57 AM
To: NANOG list
Subject: RE: How to manage Static IPs to customers
That's surprising to me, I have no intentions to do routing with our cable
Hi,
In my previous job, we managed static IPs by implementing L2TP tunnels
between CPEs and central Juniper LNS. It wasn't very elegant (at least for
mtu, MSS clamping), but the design was done around 15 years ago :)
BR
Pierre
Le ven. 8 mai 2020 à 00:58, Bryan Fields a écrit :
> On 5/7/20 5:
On 5/8/20 8:57 AM, Javier Gutierrez Guerra wrote:
> That's surprising to me, I have no intentions to do routing with our cable
> subscribers, that seems like a headache for both sides
Meh, there are BNG solutions out there;
but RIP's not horrible _in_this_context_
> Today we have specific
ANOG On Behalf Of Bryan Fields
> Sent: Thursday, May 7, 2020 5:57 PM
> To: nanog@nanog.org
> Subject: Re: How to manage Static IPs to customers
>
> CAUTION: This email is from an external source. Do not click links or open
> attachments unless you recognize the sender and know the con
customer static IP if their node gets splitter and I have to mode them to a
different CMTS
Thanks,
Javier Gutierrez Guerra
-Original Message-
From: NANOG On Behalf Of Bryan Fields
Sent: Thursday, May 7, 2020 5:57 PM
To: nanog@nanog.org
Subject: Re: How to manage Static IPs to
On 5/7/20 5:54 PM, Brandon Jackson via NANOG wrote:
> I have seen (Charter) and heard quite a few run RIP or some other routing
> protocol on the CPE.
Yep, it's RIP. They don't support IPv6 on this either. I've been asking for
IPv6 since 2006, it's always next year.
--
Bryan Fields
727-409-11
I do not believe it is a GRE tunnel.
I have seen (Charter) and heard quite a few run RIP or some other routing
protocol on the CPE.
Though I have not seen anything specific about Comcast specifically.
Brandon Jackson
On Thu, May 7, 2020, 16:54 Brandon Martin wrote:
> On 5/7/20 4:49 PM, Javie
On 5/7/20 4:49 PM, Javier Gutierrez Guerra wrote:
Just wanted to reach out and get an idea how is people managing customers with
static Ips, more specifically on Docsis networks where the customer could be
moved between cmts's when a node is split
Around here, Comcast seems to provision a GRE
19 matches
Mail list logo
