[evla-sw-discuss] Fwd: MIB Multicast address document
Pete Whiteis
pwhiteis at aoc.nrao.edu
Thu Apr 28 15:04:48 EDT 2005
It does exist as a document titled MIB_multicast_addresses.txt. This is
kept on the NRAO CVS repository and can be found under NRAO/EVLA/MIB/docs.
Cheers,
-Pete-
James Robnett wrote:
>
> The following is a copy of an email that Frank sent around (and
> has been reforwarded at
> times).
>
> Does anyone know whether
>
> o this email exists as an 'official' document somewhere (I couldn't
> find the MIB/docs CVS area he mentioned).
> o this information is still accurate
> o or whether there's a new 'official' document that re-addresses this
> issue?
>
> At some point there should be some sort of official document, if
> there isn't one I'd recommend
> using this as a starting point.
>
> James
>
> Begin forwarded message:
>
>> From: Clayton Frank Helvey <chelvey at nrao.edu>
>> Date: December 3, 2004 2:38:25 PM MST
>> To: Pete Whiteis <pwhiteis at nrao.edu>, Hichem Ben Frej
>> <hbenfrej at aoc.nrao.edu>, Rich Moeser <rmoeser at nrao.edu>
>> Cc: James Robnett <jrobnett at nrao.edu>, Bill Sahr <bsahr at nrao.edu>
>> Subject: MIB Multicast address document
>>
>> The attached is a writeup on the multicast addresses and port numbers
>> being used and the methods that are or can be used to derive those
>> addresses.
>>
>> This is also in the MIB/docs CVS area.
>>
>> -- Frank
>>
>> --
>> -----------------------------------------------------------------------
>> Clayton Frank Helvey Contracted to NRAO/AUI, Inc.
>> President Socorro, NM 87801
>> Montvale Software Services, PC email: chelvey at nrao.edu
>> phone: 540.947.5364 cell: 540.529.3740
>> email: cfhelvey at yahoo.com
>>
>>
>> MIB Multicast Address Usage
>> 02-DEC-2004
>> C. Frank Helvey
>>
>> Description
>> =============
>> This file lists all multicast addresses in use on the MIB in
>> Framework code revision 0.19.
>>
>> The addresses are broken up by Receiver (RX) and Transmitter (TX).
>> There are
>> currently no multicast addresses which are both.
>>
>>
>> Port Number Assignments
>> =======================
>>
>> Here are the port numbers being used for each type of output,
>> regardless of the address
>> used for that type of output.
>>
>> Output Type Port
>> ------------- -----
>> archive data 20010
>> alert data 20011
>> screen data 2004
>> logger output 20000
>>
>>
>> Multicast Addresses Definition
>> ==============================
>>
>> RX Multicast Addresses
>> ======================
>>
>> 224.000.000.001 All-hosts group
>> 224.000.001.001 NTP group (uses NTP_PORT)
>>
>>
>> TX Multicast Addresses
>> ======================
>>
>> TX Address Formation
>> ====================
>> Three methods are available in the MIB to form the data
>> addresses, and
>> two are available to form the logger address in 0.19 and later
>> MIB code.
>>
>> Data addresses (archive, alert, and screen) can be formed by one
>> of the
>> following methods:
>> 1) in the configuration XML file in the device "ipsetup".
>> 2) by turning off the code that uses site and antenna ID to
>> form defaults
>> 3) by turning on that code.
>>
>> The code that uses site and antenna ID to form the addresses is
>> currently turned off
>> in the MIB code via a compiler symbol; with it turned off the
>> default addresses shown
>> below are created. With it turned on, the addresses listed under
>> "Site and Antenna
>> ID Based TX Multicast Addresses" are used.
>>
>> Current Default TX Multicast Addresses:
>> =======================================
>> 239.192.000.001 - archive data
>> 239.192.000.002 - alert data
>> 239.192.000.003 - screen data
>> 239.192.002.001 - logger output
>>
>>
>> Site and Antenna ID Based TX Multicast Addresses:
>> =================================================
>>
>> These have the form 239.192.SSS.XXX, where:
>>
>> SSS is the site location field as follows:
>> Base address value is 0 for the AOC and 1 for the VLA;
>> 0 is the
>> default if the code can't determine the site location.
>>
>> To that base value, add one of the following offsets:
>> data address + 0 offset
>> logger address + 2 offset
>>
>> So AOC data address value for SSS is 0, and logger
>> address is 2
>> So VLA data address value for SSS is 1, and logger address
>> is 3
>>
>> XXX is the antenna ID field as follows:
>> The base address value is derived from the Antenna ID.
>> The Antenna ID is normalized to fall in the range 0 to 49.
>> If the ID is > 100, subtract 100; otherwise, subtract 50.
>>
>> To that base value, add the following offsets for each type
>> of address:
>> archive or logger address offset is +0
>> alert address offset is +50
>> screen address offset is +100
>> So for Antenna ID 0 (the Control Building), the result
>> would be 0
>> for archive and logger, 50 for alert, and 100 for screen.
>>
>>
>> Examples of addresses formed when using site location and antenna
>> ID:
>> =====================================================================
>>
>> Antenna 13 at the site:
>>
>> Address Function
>> --------------- ---------------
>> 239.192.001.013 archive data
>> 239.192.001.063 alert data
>> 239.192.001.113 screen data
>> 239.192.003.013 logger output
>>
>> Bench/office systems (Antenna 98) at the AOC:
>>
>> Address Function
>> --------------- ---------------
>> 239.192.000.048 archive data
>> 239.192.000.098 alert data
>> 239.192.000.148 screen data
>> 239.192.002.048 logger output
>>
>> Test Rack (Antenna 99) at the AOC:
>>
>> Address Function
>> --------------- ---------------
>> 239.192.000.049 archive data
>> 239.192.000.099 alert data
>> 239.192.000.149 screen data
>> 239.192.002.049 logger output
>>
>
> _______________________________________________
> evla-sw-discuss mailing list
> evla-sw-discuss at listmgr.cv.nrao.edu
> http://listmgr.cv.nrao.edu/mailman/listinfo/evla-sw-discuss
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pwhiteis.vcf
Type: text/x-vcard
Size: 144 bytes
Desc: not available
URL: <http://listmgr.nrao.edu/pipermail/evla-sw-discuss/attachments/20050428/0fdc7914/attachment.vcf>
More information about the evla-sw-discuss
mailing list