Colocated Hub » History » Revision 4
Revision 3 (laforge, 04/21/2022 06:22 PM) → Revision 4/27 (laforge, 08/29/2022 04:17 PM)
{{>toc}} h1. Colocated Hub This page exists to collect some planning about the future colocated OCTOI hub, see #5542 h2. Rackmount units Physical Setup h3. Central Office server (2U / 67cm) Server (specs) This is a High level: * Some 2U rack-mount server running all the relevant software. See [[AVSt_Server]] for more details of the server h4. Connections This is a 2U rack-mount server machine with the following connections: capacity to host preferably >=2 full-height PCIe cards (TE820). * Power SRV-IO to map TE820 into a VM for easier debugging of potential DAHDI kernel crashes ** 2x AC power connections (Redundand PSU) * Ethernet amount of RAM is not very important, the use case has no high RAM requirements ** 1x RJ45 100-Base-TX BMC ** 2x RJ45 1000-Base-TX * E1 ** 8x E1 CPU is more critical given all of the the byte-shifting and lots of copying / context switches we have to a co-located Cisco AS5400 (see below) do for each trunk in the current software architecture ** 1x E1 to a co-located Livingston PM3 (see below) ** 1x E1 to icE1usb/clock-source h3. icE1usb * storage is also not very critical, other than for log files / E1 clock source (1U / 31cm) monitoring This is a 1U rack mount system containing: Candidates: * a PC-Engines APU3 embedded x86_64 @laforge has experience with Dell PowerEdge R740 (up to 3 full-height slots) * an [[e1-t1-adapter:ICE40_E1_USB_interface|icE1usb]] with a custom RS422 interface board @gruetzkopf has suggested HP DL830p G8 (up to 6 full-height slots) * a custom rs422 over voltage protection + 12V injection board @laforge is checking SuperMicro options with riser cards for PCIe h3. DAHDI cards This @laforge has at least two TE820 that can be used for this purpose h3. icE1usb acts We need at leaset one icE1usb as a GPS-disciplined clock master. However, as no acutal RF GPS signal is available We can also use that one to compare physical (icE1usb+TE820) setups against DAHDI-trunkdev. We could deploy 1-2 more, just in the data centre, we are using an Ericsson [[ericsson-rbs-6xxx:GPS_02]] attached via ~100m of RS-422. h4. Connections * Power ** 2x AC power connections (1x APU, 1x RS422/GPS) * Ethernet * RS422 ** 1x RJ45 towards GPS02 on the roof case. h3. Cisco AS5400 RAS Server (2U / 49cm) dial-up server h4. Connections * Power ** 2x AC power connection (redundant PSU) * Ethernet ** 1x RJ45 Ethernet (100-Base-TX) We should install at least one RAS server next to internal VLAN * E1 ** 8x E1 (via break-out cable) to AVSt-Server h3. Livingstion Portmaster 3 (2U it, for dial-up modem / 31cm) isdn termination h4. Connections * Power ** 1x AC power connection * Ethernet ** 1x RJ45 Ethernet (10-Base-TX) [yes, 10MBps] * E1 ** 1x E1 Definitely the Livingston Pormaster3 currently next to AVSt-Server h2. Roof installation On the roof of hub. Needs 1xE1 on the data centre, the CAT5 cable with RS422 for the GPS03 arrives. It will be passed through several DIN rail mounted OVP (Over Voltage Protection) circuits before connecting to the actual DIN-rail mounted Ericsson GPS03 The Ericsson GPS03 Server * Likely also a Cisco ASR5400 @laforge has a SMA connector, to which a SMA-male to N-Male coaxial cable is attached. A Times Microwave LP-GTR-NFF lightning protector (N-female to N-femaile) is used to pass the coaxial cable through the enclosure An external GPS antenna with N connector is plugged into the LP-GTR-NFF acquired (much higher capacity, likely more featurs) h2. Software * Like in the current hub at @laforge's basement, we should run the entire yate / osmo-e1d / dahdi-trunkdev inside a KVM with SRV-IO mapping the PCI devices h2. Misc / TODO h3. local verification with modem/ISDN-TA It would be great if we could somehow verify local calls via the yate / hub excluding the complexity of the TDMoIP to compare calls without TDMoIP to calls with TDMoIP. Unfortuantely I'm not aware of any really small PBX that would terminate the E1/S2M and offer S0/POTS ports. Adding antoher 3U for a PBX seems excessive. Doing calls between PM3 and ASR5400 is of course an option, but ideally we'd have a real physical modem attached via a serial port, and a real HFC-S-USB for test purpose.