Technical data

TraverseEdge 2020 Applications and Engineering Guide, Chapter 11: Interoperability
Page 11-4 Turin Networks Release 5.0.x
• Xmt of OC-3/12 PLM in lower TE-2020 CCT connects to OAU A Rcv on OSIRIS
Figure 11-4 OSIRIS to TE-2020 Fiber Connectivity
11.1.4 OSIRIS DCC IP Addressing
The Operations Support System (OSS) is connected to the OSIRIS ring via an OSIRIS “gateway node”
using IP addressing, therefore each OSIRIS Ring to be managed must be on a different IP subnets.
TE-
2020/OSIRIS can support any valid IP sub-net scheme. Using the “255.255.255.x” subnet range substan-
tially reduces IP address requirements in a Central Office (CO). A full list of 255.255.255.x subnets can be
found at “http://support.whiterock.com/subnet”.
NOTE: OSIRIS does not support 255.255.255.255 (host subnets)
Use of
TE-2020 “Proxy ARP” feature allows the OSIRIS Gateway NE to appear to be on the same subnet
as the CO LAN.
• Appears as if all OSIRIS NE’s are on the CO LAN
• No impact on existing OSS routing tables
• Simplifies installation
An IP address is required for the TE-2020 DCC port and a single OSIRIS “gateway” node on the
ring. A minimum of 4 contiguous IP addresses must be allocated for each OSIRIS ring
(255.255.255.252 subnet), however any subnet addressing scheme is supported. The remainder of
OSIRIS nodes do not require IP addresses. Refer to Figure 11-5 for a typical IP addressing struc-