7

junglemux sonet multiplexer manual

LINK 1 ENTER SITE >>> Download PDF
LINK 2 ENTER SITE >>> Download PDF

File Name:junglemux sonet multiplexer manual.pdf
Size: 3256 KB
Type: PDF, ePub, eBook

Category: Book
Uploaded: 8 May 2019, 20:39 PM
Rating: 4.6/5 from 667 votes.

Status: AVAILABLE

Last checked: 13 Minutes ago!

In order to read or download junglemux sonet multiplexer manual ebook, you need to create a FREE account.

Download Now!

eBook includes PDF, ePub and Kindle version

✔ Register a free 1 month Trial Account.

✔ Download as many books as you like (Personal use)

✔ Cancel the membership at any time if not satisfied.

✔ Join Over 80000 Happy Readers

junglemux sonet multiplexer manualYou may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. Discover everything Scribd has to offer, including books and audiobooks from major publishers. Start Free Trial Cancel anytime. Report this Document Download Now Save Save JMUX Reference Manual Issue 4.0 For Later 100 (1) 100 found this document useful (1 vote) 208 views 99 pages JMUX Reference Manual Issue 4.0 Uploaded by gradeli Description: multiplexor optico general electric Full description Save Save JMUX Reference Manual Issue 4.0 For Later 100 100 found this document useful, Mark this document as useful 0 0 found this document not useful, Mark this document as not useful Embed Share Print Download Now Jump to Page You are on page 1 of 99 Search inside document Browse Books Site Directory Site Language: English Change Language English Change Language Quick navigation Home Books Audiobooks Documents, active. Technical Practice and Installation Manual This document must not be copied, reprinted or reproduced in any material form, either wholly or in part, without the written consent of GE Multilin Inc. GE Multilin Inc. reserves the right to make changes and modifications to any part of this document without notice. How the ETHER-1000 units maps IP frames to priority queues. This manual explains how to operate, install and maintain the ETHER unit. The unit description and block diagram are included as well as detailed description of the unit s operation. Engineering documentation includes EAS schematics for all unit circuitry. Related Publication and Documentation Support Additional information is provided in the JungleMUX Technical Overview and Reference Manual for system planning and engineering. The user may also find useful information in Technical Practice and Installation Manuals (TPIMs) for other JungleMUX units.http://enter.in.ua/admin/fckeditor/editor/filemanager/connectors/php/userfiles/an-prm-10-manual.xml

Tags:
• junglemux sonet multiplexer manual, junglemux sonet multiplexer manual download, junglemux sonet multiplexer manual pdf, junglemux sonet multiplexer manual transfer switch, junglemux sonet multiplexer manual transmission, ge junglemux sonet multiplexer manual pdf.

Customer inquiries for information contained in this manual should be directed to JungleMUX Product Line Management. GE Multilin appreciates notification of any possible errors or omissions contained herein. Shipped with all purchased JungleMUX nodes is a Node Assignment Drawing (NAD), which provides necessary configuration details for the units and shelf location. Product Color and Nomenclature The product line has undergone a transition to a new colored package. Note that there is no difference in the internal electronics and therefore the functioning of this equipment, whether it be gray or black. Gray-colored modules were discontinued in June The modules added to the product portfolio after November 2007 have been available in black only. To simplify the information within this TPIM, all unit code numbers will be stated without any color prefix. The ordering information (Section 8), however, does include the available color options. 10 Page 10 Handling and Packing Equipment with Electrostatic Discharge Sensitive (ESDS) devices or components must be shipped in protective containers and necessary handling precautions observed; otherwise, all warranties, expressed or implied, will be considered null and void. The following Electronic Industries Association (EIA) attention label appears on all GE Multilin EAS schematics and should be attached on all containers used for ESDS items to alert personnel that the contents requires special handling. Issue Date Details of Change Draft 1 April 2010 Preliminary draft document originated. Draft 2 May 2010 General update. Draft 3 June 2010 General update. Draft 4 Dec 2010 Added spec for electrical isolation. General update. Draft 5 Mar 2011 Updated to reflect unit Version 2 features and operation. Issue 1 June 2011 Updated to reflect unit Version 3 features and operation. Issue 1.1 June 2011 Observed errors corrected. Table 3 amended. Observed errors corrected.http://blentech.ru/pic/an-psq-18-technical-manual.xml 11 Page UNIT OVERVIEW A JungleMUX SONET system provides a mechanism to transport various forms of electronic data over an optical fiber. The unit acts as an intelligent learning bridge, forwarding to other units only those frames that are not locally addressed. Bandwidth partitioning into multiple (up to 4) independent TDM streams (TDM pipes) where individual stream s bandwidth can range from 1 to 24 STS- 1 SPEs. Supports point-to-point, linear and ring network topologies. Traffic can be passed between contiguous networks (at collocated nodes). Figure 1: ETHER-1000 Unit Provides rapid path switching after a fiber or JMUX unit failure in ring applications (typically within 5 ms). 1 For ETHER-1000 firmware versions 12 Page 12 Supports VLANs o Ability to share the allocated STS-1 SPE(s) between multiple sets of bridged LANs. Privacy is maintained between the different sets.D-PVLANs are pre-assigned to the four TDM pipes in sets of 15. Each provisioned Ethernet access port requires a D-PVLAN assignment (1-60).On a D-PVLAN trunk, all frames are 802.1Q tagged to distinguish between different D-PVLANs.Applied to both ingress (input) and egress (output) frames. Configurable per-qvlan output tagging (available when QVLAN filtering is enabled). Powerful MAC address management o A 32,768-entry MAC address table in the ETHER-1000 unit ( WAN switch).The inner tag is the one closest to the payload portion of the frame. 3 Some limitations apply. See MAC Address Management section. 13 Page 13 o Static and pseudo-static MAC addresses stored in flash for guaranteed resumption of operation upon reboot.Enhanced port security features including blocking of unknown MAC addresses, intrusion detection and automatic port disabling on cable disconnect. Configurable Unit Security mode. High security mode (default) ensures that none of the unit parameters except those related to SONET-path provisioning can be modified by non-administrators.https://www.informaquiz.it/petrgenis1604790/status/flotaganis22052022-0226 Only VistaNET administrators can change the unit security from High to Low. Guaranteed delivery of mission critical traffic o Mission-critical traffic can be detected on ingress using the frame s EtherType value. The top priority queues in both LAN and WAN switches are reserved for selected EtherType traffic. All other traffic will use lower priority queues.Backwards compatible with ETHER-100 unit. Per-port ingress and egress rate limiting. Port mirroring Firmware upgrades through CI. Connectivity The unit performs a bridging function between the GMII port (interface to the paddleboard) and its two (left and right) Line ports. The number (N) of STS-1 SPEs used per CBW port is user-configurable. For more information the user is referred to the respective JMUX unit Technical Practice and Installation Manual and JungleMUX Technical Overview and Reference Manual. 9 The ETHER-1000 unit and paddleboard can also be installed in Expansion Shelf slots 2 to 14 if the shelf spacer unit PB or PL with removable front panel is used immediately above it. Customer access ports are provided using either one or two quad-port plug-in modules installed on the paddleboard. These modules have dedicated locations (Banks A and B) on the paddleboard. Cascading ETHER-1000 Units A maximum of two ETHER-1000 units can be cascaded and connected to the same CBW port on the JMUX units (Figure 3). An ETHER-1000 unit is connected with one or more other ETHER-1000 units in the same JungleMUX network to form a point-to-point, linear or ring ETHER network topology. Ethernet ports of all ETHER-1000 units that make up such a topology create an Ethernet switch with geographically spread access ports (a distributed Ethernet switch ). An example of ETHER-1000 ring network topology is shown in Figure 4. The devices on the LAN segments connected to ETHER-1000 unit paddleboards at all six sites can exchange traffic through common bandwidth (N x STS-1 SPE).https://hardwareusato.com/images/802d-manual.pdf 10 A point-to-point topology may be considered a special case of a linear network. Two-node ring topologies are sometimes confused with point-to-point networks. The unit can partition this bandwidth into as many as four TDM pipes. The ETHER-1000 unit has independent traffic forwarding queues for each TDM pipe, which ensures that traffic carried in different TDM pipes will be independently queued within the WAN switch. In the example in Figure 6, each of the four TDM pipes is accessed at all sites. Since all four pipes have been configured as rings, protection switching is independently carried out for each TDM pipe. Along each TDM pipe, an independent ETHER network topology, which may include a mixture of ETHER-1000 and ETHER-100 units, can be created. ETHER-100 unit does NOT support automatic segregation of selected EtherType traffic and its placement into top priority queues. If a failure occurs in a JMUX unit, or a fiber is damaged, affected traffic will be automatically rerouted to the other way around the ring typically within 5 ms. Note: Path protection is carried out independently for each TDM pipe configured and provisioned as a ring. Physical ETHER-1000 unit redundancy can be achieved by equipping an ETHER-1000 drop site with two ETHER-1000 units installed on separate paddleboards. These units can either be installed on separate CBW ports (this would assume establishing completely independent ETHER-1000 systems using separate STS-1 channels), or on the same CBW ports (using two cascaded ETHER-1000 units). An example of a fully redundant ETHER-1000 application at an OC-48 JungleMUX node is shown in Figure 10. CAUTION When redundant ETHER-1000 units are simultaneously bridging the same traffic, an Ethernet loop is created which can cripple the network if not properly handled. Using VistaNET, the user can assign membership in any one D-PVLAN to each of the 8 ports on the paddleboard. Ports provisioned as D-PVLAN trunks can have multiple D-PVLAN memberships (explained later). The D-PVLAN information is encoded in a proprietary secure tag called Envelope Header attached to each frame at its source ETHER-1000 unit and removed at the destination one, so the frames leave the ETHER-1000 system unchanged. As a result, any ingressing broadcast and multicast traffic will be delivered only to those ports that are members of the same D-PVLAN and QVLAN. A maximum of 50 QVLAN memberships in the range from 1 to 4000 per can be assigned to a port. If QVLAN filtering for a port is enabled, it is applied to both ingressing and egressing frames. All ports on the same D-PVLAN must be set for the same QVLAN filtering mode (either enabled or disabled). Note: QVLAN filtering for the port is enabled or disabled by means of selecting the proper Port Type option. Ports provisioned as P-Access or P-Trunk ports do not support QVLAN filtering, while the ports provisioned as Q-Access or Q-Trunk ports do. Note: For ports with QVLAN filtering enabled (Q-Access and Q-Trunk ports), any ingressing untagged (native) frames and 802.1p frames are either discarded or assigned the port s Default QVLAN ID value, depending on the port setting. At the far end, these frames may be outputted either unchanged or with an added tag with the source port s Default QVLAN ID value. (See Output Tagging feature below.) Output Tagging The output tagging feature allows for adding or removing the (outer) 802.1Q tags of the frames egressing the local access port. This feature, in its generic form, is available only to ports with QVLAN filtering enabled. The frames that were tagged at the far-end source port can be outputted either unchanged or with the (outer) tag removed. The frames that were untagged at the far-end source port can be outputted unchanged, or with an added tag carrying the source port s Default QVLAN ID and Default Priority. The default is no change. Output Tagging mode is configured on per-qvlan basis. 11 For more information on VLANs the user is referred to Appendix B. 27 Page 27 Note: All ports on the same D-PVLAN must be set for the same QVLAN filtering mode (either enabled or disabled), while their individual output tagging settings (if applicable) may vary. Port Types Port Type selection is made at the beginning of the provisioning process for a paddleboard port. Otherwise, No Change, Untag or Tag. Each (outer) QVLAN ID corresponds to a specific D-PVLAN. Ingress: - Untagged frames. Default QVLAN ID is applied. - Tagged frames (if enabled) with QVLAN ID matching Default QVLAN ID. 50 (configurable in range) Yes (configurable) (Applied to untagged frames at ingress, if any.) No (can be enabled) No Change, Tag (per QVLAN). Untag is allowed for Default QVLAN only. Ingress: Tagged frames with various QVLAN IDs (from external switch). All QVLANs remain on same D-PVLAN and are distributed using QVLAN filtering. Table 2: Port Type Options Note: The Port Type parameter is not available on unit versions 28 Page 28 CAUTION The user must ensure that only the compatible port types are residing on the same D-PVLAN. Otherwise, traffic misrouting may occur. Port Type Application Examples Below are some application examples for various port type options. To simplify the figures, all ETHER-1000 units whose one or more TDM pipes are interconnected through common SONET bandwidth are shown as a single ETHER-1000 switch with geographically distributed ports. The Port Type setting is denoted for each port. P-Access Ports P-Access (PA) is the default port type. Each PA port has only one D-PVLAN assignment and no QVLAN filtering capabilities. These ports can exchange traffic only with remote PA and PT ports (with matching D-PVLAN memberships). Application examples for PA ports are shown in Figures 12 to PA PA PA Distributed ETHER-1000 Switch JungleMUX JMUX Ring Ring Ethernet Port D-PVLAN membership PA PA PA Figure 12: PA ports in a single ring (and same ETHER-1000 WAN) 13 These applications are also supported by ETHER-1000 firmware Versions 1 and 2. 29 Page 29 PA PA PA PA PA PA JungleMUX Ring 1 JungleMUX Ring 2 CBW Ties PA PA PA PA PA PA Figure 13: PA ports in multiple physical rings (but same ETHER-1000 WAN) PA PA PA PA PA PA JungleMUX JMUX Ring Ring PA PA PA PA 1 2 JungleMUX JMUX Ring Ring PA PA PA Ethernet Port D-PVLAN membership Figure 14: PA ports in multiple rings (and different ETHER-1000 WANs) P-Trunk Ports P-Trunk (PT) ports can have multiple D-PVLAN memberships. The PT ports can exchange traffic only with remote PA and PT ports (with matching D-PVLAN memberships). Each frame egressing a PT port has an added 802.1Q tag with the VID corresponding to its originating D-PVLAN. The ingressing tagged frames are placed into respective D-PVLANs based on the VID carried in their (outer) tag. The (outer) tag is removed on ingress. Any untagged frames are blocked. Also, any tagged frames whose (outer) VID does not match any of the VIDs associated with selected D-PVLANs are blocked. All frames egressing the router port typically have the same source MAC. D-PVLAN membership Figure 17: Distributing traffic from a router s trunk port to D-PVLANs 15 PT port functionality is not supported by ETHER-1000 Versions 1 and 2. 31 Page 31 Q-Access Ports Each Q-Access (QA) port has a single D-PVLAN membership and a single QVLAN membership (the Default QVLAN ID, which is user-configurable). These ports can exchange traffic only with remote QA and QT ports (with matching D- PVLAN and QVLAN memberships). Ingress of untagged frames can be enabled (default) or disabled. If enabled, the port s Default QVLAN ID (configurable for a value between 1 (default) and 4000) is assigned to these frames. Ingress of tagged frames is normally disabled (default), but if enabled, only those ingressing frames tagged with the VID matching the Default QVLAN ID will be processed. Only the frames matching the port s D-PVLAN and QVLAN membership are allowed to egress. The port can be set to remove the (outer) tag of all egressing tagged frames (the Untag option), to add a tag with respective remote Default QVLAN ID to all egressing untagged frames (the Tag option), or to keep the egressing frames unchanged with respect to their far-end ingress (the No Change option). NOTE: If Q-trunking is used somewhere within the same D-PVLAN (see next slide), No Change can be used as an alternative to 'Tag' if only tagged frames appear on all ports. D-PVLAN membership QVLAN membership Figure 18: Multiple VLANs within a single D-PVLAN (one VLAN per port) 16 If duplicate MACs are not used anywhere in the network, this application is supported by ETHER-1000 V2. It is also supported by ETHER-1000 V1 if only tagged frames appear on all ports (assuming use of non-default QVLAN ID). 32 Page 32 Q-Trunk Ports Each Q-Trunk (QT) port has a single D-PVLAN membership and (usually) multiple QVLAN memberships (the Default QVLAN ID plus up to 49 other ones, all user configurable). These ports can exchange traffic only with remote QA and QT ports (with matching D-PVLAN and QVLAN memberships). Ingress of untagged frames is normally disabled, but can be enabled by the user. If enabled, the port s Default QVLAN ID (configurable for a value between 1 (default) and 4000) is assigned to ingressing untagged frames. Ingress of tagged frames is always enabled (cannot be disabled). Only those ingressing tagged frames whose (outer) VID is matching the Default QVLAN ID or any of the entered QVLAN memberships will be processed. Only the frames matching the port s D-PVLAN and any of the QVLAN memberships are allowed to egress. For each QVLAN membership independently, the port can be set to either add a tag with respective remote Default QVLAN ID to all egressing untagged frames (the Tag option) or to keep the egressing frames unchanged with respect to their far-end ingress (the No Change option). For Default QVLAN only, the port can be alternatively set to remove the (outer) tag of all egressing tagged frames (the Untag option). Examples of applications that can be addressed with QT (and QA) ports are shown in Figures 19 to The actual field implementation may be a combination of these examples. The only difference is that QT cannot be set to block tagged frames. 34 Page 34 QA QA QA QT JungleMUX JMUX Ring Ring 1 1 Router All frames are tagged. 101 Frames egressing router typically have the same source MAC address. The mapping priority is carried in the secure tag attached to each frame for transmission between ETHER-1000 units. This tag is removed at the far-end unit's drop port. Optionally, the user can force the mapping priority of all frames ingressing the given access port to a specific priority. Each paddleboard port is capable of detecting ingressing mission critical frames based on the frame s embedded EtherType code (e.g. 88b8 for GOOSE messages). All frames whose EtherType code is matching the port s EtherType setting will be treated as super-priority frames and they will be switched through the highest priority queues in both LAN and WAN switches. The unit also has 8 priority queues for the drop traffic passed to the GMII port (the port facing paddleboard). 19 The highest priority queue (within each set of 8) is reserved for EtherType traffic 20, while the 7 lower priority queues are used for all other traffic. 18 When ETHER-100 units are used in the same ETHER system, special caution shall be exercised as these units do not support this feature. The frames being forwarded from the WAN to the LAN switch are competing for the GMII port s drop bandwidth (1 Gbps) based on their mapping priority designation. Figure 24 shows the priority queues. Note that, for the Line ports, only the queues for one of the four TDM pipes are shown. No priority ( native frame), in which case the user-configurable port's Default Priority is assumed. Which of the 8 available queues a frame is placed into depends on its mapping priority (designated at its source ETHER-1000 paddleboard port). The frames from higher 37 Page 37 priority queues are outputted first i.e. no frame from a given priority queue is outputted before all the frames from higher priority queues have been outputted. There are also 8 priority queues for the Drop port (for the frames dropped from the Line ports). Use of TDM Pipes and Traffic Prioritization for Providing Guaranteed SONET Bandwidth for Important VLANs Figure 25 pictorially shows the four TDM pipes and their bandwidth utilization in two different moments in time (t 1 and t 2 ). Each TDM pipe can carry traffic at different (up to 8) priority levels. Traffic at each priority level is depicted with uniquely colored pie slice whose size is proportional to the current amount of traffic at that priority level with respect to the TDM pipe s capacity. This problem can be partially addressed by forcing each VLAN s traffic to a priority that properly reflects its importance to the network operator. It is individually configurable for each access port, and for each direction (input and output). Each set of criteria includes the specific frame type(s) (unicast, multicast, broadcast) and source priorities. The frames that do not meet any of the configured (up to three) sets of criteria are not rate limited. Output rate limiting, if enabled, applies to all frames being outputted through the given port regardless of their type (broadcast, multicast or unicast) and priority. When the device does not support auto-negotiation and the ETHER-1000 unit s auto-negotiation for the port is enabled, the unit uses the incoming signal's speed and half-duplex mode. With auto-negotiation disabled, the user can configure the mode and speed as desired. Ethernet frames are discarded if too short ( 1632 bytes), or if the CRC error-check fails. Ethernet errors are monitored and reported through VistaNET software. In half-duplex mode, collisions between Ethernet frames are expected to occur. RJ-45 ports are available on and quad-port modules, equipped with four and two RJ-45 ports, respectively. The type of transceiver used (1000Base-SX, 1000Base-LX, or 1000Base-LH) is determined by the type of fiber used (mmf or smf) and required reach. The type of transceiver used (100Base-SX, 100Base-FX, or 100Base-LH) is determined by the type of fiber used (mmf or smf) and required reach. The SFP transceiver format is a standard supported by many optical transceiver vendors. 21 The ETHER-1000 unit accepts only transceivers equipped with DMI (Diagnostic Monitoring Interface) to allow for in-depth transceiver monitoring. The SFP transceivers available through GE Multilin are equipped with dual LC connectors (separate fiber strands for transmit and receive traffic). Note: SFP transceivers with RJ-45 copper port are also available on the market; however, they are not supported by ETHER-1000 because they are not SWC compliant. The unit operates as a learning bridge, implying that the locations of source MAC addresses (SA) are learned from normal Ethernet traffic. Typically, dual-fiber transceivers are equipped with LC connectors while the single-fiber ones are equipped with an SC connector. 41 Page 41 The received 802.1Q VLAN ID 22 The Distributed Port-based VLAN value used when setting up physical port security The Destination Port Vector (DPV) defining: - the frame s source port, for frames received through a local port 23, or - the location of the ETHER-1000 unit at the frame s source, for frames received through a Line port The aging value for each entry A Unicast or Multicast flag As Ethernet frames arrive into the ETHER-1000 unit, a lookup of the SA in the MAC address table is performed. If the same entry already exists on the same D-PVLAN, its age field is re-initialized and the DPV field is updated (if changed). Otherwise, the MAC address and frame ingress port will be added (assuming there is less than 32,768 MAC entries already in the table). A MAC address entry can only age out of the table. If required, the table can be cleared by the user, using VistaNET software. The WAN MAC address table is kept sorted to facilitate the fast retrieval of table entries and to allow the use of all the entries (many switches typically store less than 10 of their advertised capacity). All entries in the WAN MAC address are subject to aging, i.e. an entry will be removed after a period of inactivity. A MAC address is considered inactive if it has not been received at any of the ETHER-1000 unit ports (GMII port and two Line ports) within a specified time interval called Aging Time (defined in each unit). Aging time is user-configurable (ranging from 30 seconds to 1 hour, or never). It learns the MAC addresses of the devices connected to local drop ports as well as the MAC addresses of the devices connected to remote drop ports that are exchanging traffic with the local ones. Any unicast frames between local ports are not forwarded to the ETHER unit as long as their destination addresses have not aged out. Any new entries will be added to the table even if the respective bin is full because in such case the oldest entry in the bin will be removed. Each LAN switch port exposed on the paddleboard (i.e. customer access port) has a configurable learning mode. A port in No Blocking mode will learn the MACs of all connected devices (up to an optional user-configurable limit). A port in Secured mode has the MAC learning disabled. It will let communicate only those local devices whose MACs either appear in the user-defined list of the port s static MACs or had been learned before the port got secured (pseudostatic MACs). Both static and pseudo-static MACs are stored in flash to allow for restoring normal operation after unit reboot. The user can have as many as 20 static MAC entries defined per port. Note: The LAN MAC Address Table s static and pseudo-static entries do not age out. All entries in the WAN MAC Address table are subject to aging. Note: The same MAC address can have multiple instances in the MAC address table as long as it appears on different D-PVLANs (or different QVLANs, if QVLAN filtering is enabled). CAUTION If QVLAN filtering is used and there is a need to use the same MAC address in two different D-PVLANs, these MAC addresses must be on different QVLANs. Otherwise, traffic misrouting may appear. Note: If a device is moved from one ETHER-1000 site to another and stays on the same D-PVLAN (and same QVLAN, if QVLAN filtering is enabled), its MAC address entry will be updated with the new site information in the WAN MAC Address Tables across the ETHER-1000 system as soon as the device becomes active (regardless of the Aging Time settings). Through the VistaNET software, the user can determine the MAC addresses stored in the LAN MAC address table on per D-PVLAN basis. For any selected D-PVLAN, a maximum of 138 MAC entries can be displayed. For each entry, it is indicated whether it is a dynamic, static or pseudo-static entry and whether it has been learned from a local port (in which case the port number is displayed) or from a remote port. The entries are sorted in the ascending MAC address order. 43 Page 43 Unit Security The unit security mode can be set to High (default) or Low. They will not be allowed to change any other configurable parameters. The user enables only the used ports. The Off On Disconnect feature, ensures that the port will be disabled automatically as soon as cable disconnect (loss of input signal) is detected. An alarm will be reported to the NMS (if Enable Alert feature for the port is on). The alarm will remain latched until either the cable is re-connected and the port is reenabled or the Off On Disconnect feature for the port is disabled. Ports in the Secure mode are blocking all unknown ingressing MAC addresses. The Secure mode operation is explained in the MAC Address Management section. If an unknown ingressing MAC address is detected on a secured port with intrusion detection feature enabled, the MAC address will be treated as an intruder MAC and an alarm will be reported to the NMS (if Enable Alert feature for the port is on). The alarm will remain latched until acknowledged by the user. In general, at a site with collocated nodes, Ethernet traffic can be passed across using: 44 Page 44 a) CBW tie connections, or b) Ethernet port tie connections (directly between paddleboards or through external Ethernet devices). Each of the above solutions has advantages and disadvantages. The user is referred to Tying Ethernet Traffic in Section 4 for more information. Note: When Ethernet traffic is to be passed between networks, caution must be exercised to ensure that no Ethernet loops are created. The SONET path BER rate and CV errors are determined using the Path Overhead's B3 bytes of individual STS-1 paths. An STS-1 Path-AIS pattern (all ones), which usually appears due to a fiber failure, is also detected and reported through the VistaNET software.