I am trying to formulate our corporate policy on allocation of IP Multicast addresses. I have read RFC2365 and the Cisco "Guidelines for Enterprise IP Multicast Address Allocation" but am still a bit confused.
I understand that the "Site-Local" scope (188.8.131.52/16) is the smallest scope, must be equal to or wholely contained within another scope boundary and is not sub divisible.
I also understand that the "Organization-Local" scope (184.108.40.206/14) is divisible.
I am assuming that if you divide the "Org-Local" scope, the lowest level you can go to is to a /16 prefix so that it can encompass the "Site-Local" scope which is the smallest scope and must be encompassed within a boundary..
So say I choose to subdivide the "Org-Local" scope into 3:
Enterprise Scope - 220.127.116.11/16
Region Scope - 18.104.22.168/16
Campus Scope - 22.214.171.124/16
I also decide to reuse the 126.96.36.199/16 scope at each campus site as non of these groups should "leak" from that site and so address reuse is possible.
Now obviously both the "Site-Local" and "Org-Local" (Campus Scope) addresses fall on a /16 boundary and meet the RFC2365 guidlines.
The confusion now arises:
When or why would I allocate an address from the "Org-Local" (Campus Scope) 188.8.131.52/16 range as opposed to using the "Site-Local" 184.108.40.206/16 range as they would both seem to be covered by the same administrative boundary. I am struggling to see the difference between the "Site-Local" and "Org-Local" ranges and when you use one over the other.
Also if I subdivide the "Org-Local" block into 4 /16 blocks do I end up with 4 separate "Scope Relative Address" [SRA] ranges below or do I still only have the one "Org-Local" SRA space of 220.127.116.11/24:
For Enterprise Scope 239.195..0.0/16 the SRA space is 18.104.22.168/24
For the Region Scope 22.214.171.124/16 the SRA space is 126.96.36.199/24
For the Campus Scope 188.8.131.52/16 the SRA space is 184.108.40.206/24
For the Unused Scope 220.127.116.11/16 the SRA space is 18.104.22.168/24
The Site-Local Scope should be assigned to address range 22.214.171.124/16 and should not be used by any other operational scopes.The address range for operational scopes (except for SSM) should be allocated from the Organization-Local group range 126.96.36.199/14 or its expansion space.
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...