Table of Contents
Advertisement
Quick Links
Advertisement
Table of Contents
Summary of Contents for Alpha Technologies GS7000
- Page 1 Optical Ethernet Transponder GS7000 Technical Manual Effective: June 2017...
- Page 2 Safety Notes Alpha considers customer safety and satisfaction its most important priority. To reduce the risk of injury or death and to ensure continual safe operation of this product, certain information is presented differently in this manual. Alpha tries to adhere to ANSI Z535 and encourages special attention and care to information presented in the following manner: WARNING! GENERAL HAZARD GENERAL HAZARD WARNING provides safety information to PREVENT INJURY OR...
- Page 3 Optical Ethernet Transponder GS7000 Technical Manual 018-350-B0-001 Effective Date: June 2017 © 2017 by Alpha Technologies, Inc. Disclaimer Images contained in this manual are for illustrative purposes only. These images may not match every installation. Operator is cautioned to review the drawings and illustrations contained in this manual before proceeding.
-
Page 4: Table Of Contents
Table of Contents 1.0 Introduction..........7 1.1 Overview . - Page 5 Fig. 6-1, GS7000 Home Page ........
- Page 6 Tables Table 1-1, Revision History........8 Table 1-2, Technical Support Contact Information .
-
Page 7: Introduction
The Optical Ethernet Transponder (OEX) provides the ability to manage fiber nodes and optical hubs through an existing fiber optic infrastructure. Contact an Alpha Technologies representative for a complete listing of supported fiber nodes. The transponder leverages the operator’s fiber optic network infrastructure and communicates with a management system, using standard Simple Network Management Protocol (SNMP). -
Page 8: Optical Module
1.0 Introduction, continued 1.2 Optical Module The OEX uses an industry-standard SFP (Small Form-factor Pluggable) optical transceiver, to provide great flexibility in optical connection options. Any SFP module rated for at least 1Gb/s (gigabit) data rate will work in the OEX. (However, SFP+ modules (typically rated for 10Gb/s or faster) are not compatible with the OEX.) If the OEX is using a dedicated fiber pair just for its communications, a standard data SFP may be chosen. -
Page 9: Technical Support Contact Information
1.0 Introduction, continued 1.4 Technical Support Contact Information For technical issues, Cisco customers should call the following Cisco Technical Support and Customer Service Numbers. Technical Support Contact Information Region Centers Telephone and Fax Numbers Technical Support Customer Service Toll-Free: 1-800-722-2009 Toll-Free: 1-800-722-2009 Local: 678-277-1120 (Press 3 at the North America... -
Page 10: Connections
2.0 Connections 2.1 Overview The OEX communicates with the fiber optic network through the SFP (Small Form-factor Pluggable) transceiver module. The OEX includes two status LEDs, a local Ethernet port (a standard RJ-45 Ethernet connector), an optical tamper sensor, and a node interface connector. The transponder receives its power and performs communications with the node all via the node interface connector. -
Page 11: Connector Summary
2.0 Connections, continued Slot Interface Connector Fig. 2-2, OEX Connections 2.2 Connector Summary Connector Summary Connector Description The SFP module is installed into the slot. The SFP must be oriented as indicated on the top of SFP Slot the transponder. The Ethernet port is a local interface into the OEX when the SFP is not connected, or a local interface into the optical network when the SFP is connected. -
Page 12: Oex Specifications
2.0 Connections, continued 2.3 OEX Specifications General HMS Monitoring Protocol: SNMP v1, SNMP v2c SFP Interface: SFF Committee INF-8074i; SFF-8472 Ethernet Interface: 1000BASE-T (IEEE 802.3ab), 100BASE-TX (IEEE 802.3u), 10BASE-T (IEEE 802.3i) Operating Temperature: –40°C to +75°C Humidity: 10% to 90% (non-condensing) EMI/EMC: FCC Part 15 Class A, EN50022 Class A 018-350-B0-001, Rev. -
Page 13: Installation
3.0 Installation Network infrastructures each have unique characteristics; therefore, Alpha Technologies strongly recommends completely installing one transponder and making it operational before deploying the entire system throughout the network. Installing the transponders and making them operational consists of the following steps, which are explained in detail in this section. -
Page 14: The Oex Startup Process
3.0 Installation, continued OEX Provisioning Process Action Result • Prior to attaching the Fiber to SFP connectors, user has ability to Install OEX in target device connect to OEX through local Ethernet port using 192.168.100.1 IP address • OEX contacts the DHCP server Connect fiber to SFP Connector •... -
Page 15: The Dhcp Server
3.0 Installation, continued The DHCP Server The address for the OEX can be offered up by any DHCP server (following RFC 2131). The details of managing any particular DHCP server vary, but there are two basic areas of interest: setting up a specific DHCP offer for a particular device, and providing the options within the DHCP offer to support the time of day and configuration file operations. -
Page 16: The Configuration File
3.0 Installation, continued 3.2 The Configuration File The security of the OEX and its control of the fiber node depends upon the configuration file settings. Verify that the transponder configuration file has been successfully tested prior to deploying transponders into the network in quantity. The OEX manages SNMP remote access and notification/trap destinations according to its internal configuration settings. -
Page 17: Installing The Oex
3.3 Installing the OEX This section provides the steps for installing the OEX into a GS7000 optical hub or node. Remove the OEX from the shipping package. Do not install the SFP yet. Position the transponder so the interface connector shown in Fig. 3-3 aligns with the node’s interface connector shown in Fig. -
Page 18: Fig. 3-4, Transponder Slot And Interface Connector
3.0 Installation, continued Fig. 3-4, Transponder Slot and Interface Connector Firmly push the OEX down onto the node’s mother board until the transponder seats into position. Use the captive screws in the transponder to secure it to the mother board. The screw locations are shown in Fig. 3-5. CAUTION! Exercise caution when installing the OEX to assure proper alignment between the connectors to avoid damaging the pins. -
Page 19: Fig. 3-6, Sfp In Place
3.0 Installation, continued Install the SFP into the slot in the OEX, oriented as indicated on the top of the enclosure. Slide the SFP into place so that it seats firmly. Fig. 3-6, SFP in Place Install the fiber(s) into the SFP. Route the fiber(s) neatly to the fiber management tray to avoid loose cabling inside the node. -
Page 20: Checking The Leds
3.0 Installation, continued 3.4 Checking the LEDs The OEX has two green LEDs for indicating operational status. Fig. 3-8, OEX LEDs The Power On LED blinks briefly during startup when the OEX first gets power, and is solid thereafter. If this LED goes off or blinks again after having showed a solid “on,”... -
Page 21: Configuration Mibs
3.0 Installation, continued 3.5 Configuration MIBs The OEX supports a number of SNMP objects for its operational configuration. ATI-MGMT-SYS-COMMS-MIB The Alpha ATI-MGMT-SYS-COMMS-MIB objects deal with both the management of a transponder with an optical link, and the management of SNMP access rights. atiMgmtSysCommsCommon Component Type... -
Page 22: Table 3-3, Atimgmtsyscommsconfigfile
3.0 Installation, continued atiMgmtSysCommsConfigFile Component Type Description This optional object provides the name of the most recently loaded configuration atiMgmtSysCfgFileName Read file. An empty string is returned if a configuration file is supported by the network (OID 1.3.6.1.4.1.926.1.3.2.11.1.3.1) String element, but no such file has been successfully loaded since startup. atiMgmtSysCfgFileSuccessful Read This optional object provides the count of successfully loaded lines or entries... -
Page 23: Table 3-5, Atimgmtsyscommsaccesstable
3.0 Installation, continued atiMgmtSysCommsAccessTable Component Type Description A table that contains access settings for a particular communications atiMgmtSysCommsAccessTable link. These settings are established at runtime, typically through a (OID 1.3.6.1.4.1.926.1.3.2.11.2.2) startup configuration mechanism, and are not retained for any future startup. -
Page 24: Table 3-7, Atimgmtsyscommsopticalstatetable
3.0 Installation, continued atiMgmtSysCommsOpticalStateTable Component Type Description atiMgmtSysCommsOpticalStateTable A table that contains status information about the optical link. (OID 1.3.6.1.4.1.926.1.3.2.11.3.2) This optional object represents the optical power measured by the receiver, atiMgmtSysCommsOptStRxPwr Read expressed in units of 1 microwatt. (OID 1.3.6.1.4.1.926.1.3.2.11.3.2.1.1) This object has an entry in the limit properties table. -
Page 25: Table 3-8, Atimgmtsyscommsopticalstatetable
3.0 Installation, continued atiMgmtSysCommsOpticalStateTable, Continued Component Type Description This optional object represents the transmitter bias current, expressed in units atiMgmtSysCommsOptStTxBias Read of 0.01 mA. (OID 1.3.6.1.4.1.926.1.3.2.11.3.2.1.9) This object has an entry in the limit properties table. This optional object represents the alarm state of the transmitter bias current. The alarm state is determined on the basis of device-specific criteria, NOT by atiMgmtSysCommsOptStTxBiasAlm Read... -
Page 26: Ati-Mgmt-Snmp-Mib
3.0 Installation, continued ATI-MGMT-SNMP-MIB The OEX supports some of the Alpha ATI-MGMT-SNMP-MIB objects, including the trap destination table. atiMgmtSnmpTrapTable Component Type Description atiMgmtSnmpTrapTable Table of SNMP Trap Addresses (OID 1.3.6.1.4.1.926.1.3.1.1) atiMgmtSnmpTrapAddress ipaddr Address for this entry (OID 1.3.6.1.4.1.926.1.3.1.1.1.2) atiMgmtSnmpTrapServerAddressType InetAddressType Address mode of atiMgmtSnmpTrapServerAddress. Use 1 for IPv4. (OID 1.3.6.1.4.1.926.1.3.1.1.1.3) Address of trap server. -
Page 27: Sa-Hms-Fibernodegs7000-Mib
3.0 Installation, continued SA-HMS-FIBERNODEGS7000-MIB The OEX supports the Cisco fiber node management MIB. NOTICE: Most of the objects in the Cisco MIB are intended for use with a fiber node, and don’t directly apply to an optical hub configuration. SA-HMS-FIBERNODEGS7000-MIB Component Type Description... -
Page 28: Provisioning The Snmp Manager
The files in Table 4-1 can be found on the Society of Cable Telecommunications (SCTE) Web site, www.scte.org. The files in Table 4-2 and Table 4-3 are provided by Alpha Technologies or Cisco. There are dependencies between MIB files, so compile them in the order shown in the following tables. -
Page 29: Acquiring The Transponders By The Snmp Manager
4.0 Provisioning the SNMP Manager, continued NOTICE: In the OEX, hfcnReturnLaserOpticalPower (OID 1.3.6.1.4.1.926.1.5.4.3.1.11) and hfcnOpticalReceiverOpticalPower (OID 1.3.6.1.4.1.926.1.5.4.4.1.5) have a higher resolution (.001 milliWatts) than the fnReturnLaserOpticalPower and fnOpticalReceiverPower. These new components are located in ATI-DEV-HFC-NODES-MIB. The fnReturnLaserOpticalPower and fnOpticalReceiverPower components are still supported, but have a lower resolution. -
Page 30: Network Interfaces
5.0 Network Interfaces The OEX possesses two network interfaces (Fig. 5-1). The optical link, through the SFP slot, is the primary communications link back to the network and any management systems. There is also an Ethernet port on the OEX, for local access by an installer or a technician. -
Page 31: Using The Local Ethernet Connector With The Optical Link
5.0 Network Interfaces, continued Fig. 5-1, Network Interfaces The local port may also support SNMP access; however, SNMP access is still subject to the same access rights whether the OEX is using the optical network link or local link. So, it’s up to the configuration of the OEX (including access setup from the configuration file described in section 3) whether local SNMP access is possible. -
Page 32: Web Interface
Web pages displays a “tool tip” of the corresponding SNMP objects. By default, Web access to the transponder is fully supported. To change the configuration of this access, refer to “6.5 Configuring the Web Access.” Fig. 6-1, GS7000 Home Page 018-350-B0-001, Rev. A (06/2017) -
Page 33: Logging In
6.3 Web Page Summaries Home Page The Home Page displays when the GS7000 Web page is loaded, as shown on the previous page. This page displays summaries for the Alarm, Hardware, System, and Communications pages. Follow the link below each summary to view the corresponding page for further detail. -
Page 34: System Pages
• System Data Page - View and edit system data for the transponder. • Communications Page - View details about the optical communications link. • Alarms Page - View the current alarms, and view and edit alarm settings. Fig. 6-4, System Link, Navigation Pane, GS7000 Home Page 018-350-B0-001, Rev. A (06/2017) -
Page 35: Hardware Diagram Page
Open the Hardware Diagram page by selecting System -> Hardware Diagram on the main menu. Fig. 6-5, Hardware Diagram The GS7000 Hardware Diagram Page displays some basic configuration information for the specific node type. Below the configuration, an interactive diagram is also displayed (see Fig. 6-5). -
Page 36: Hfc Node Page
6.0 Web Interface, continued HFC Node Page Open the HFC Node Page by selecting System -> HFC Node on the main menu. The HFC Node Page displays all the details of the fiber node and its various modules, organized by category. This is similar to the information in the pop-ups on the Hardware Diagram Page, but presented all in a single view. -
Page 37: Fig. 6-7, Alarm Settings Popup Window
6.0 Web Interface, continued Many of the features on the HFC Node Page are editable or selectable when logged in. Before leaving a page, click the Save Changes button at the bottom of the page to apply and save new settings. Other items in this display are “alarmable,”... -
Page 38: System Data Page
6.0 Web Interface, continued System Data Page Open the System Data Page by selecting System -> System Data on the main menu. The System Data Page displays a variety of status and configuration information about the transponder (this is separate from information about the node). -
Page 39: Communications Page
6.0 Web Interface, continued Communications Page Open the Communications Page by selecting System -> Communications on the main menu. The Communications Page displays detailed information about the optical communications link, including a network communications summary, the optical module data, and the configuration file results. If accessing the Communications Page locally (using IP address 192.168.100.1), the “IP Address from DHCP”... -
Page 40: Alarms Page
6.0 Web Interface, continued Alarms Page Open the Alarms page by selecting System -> Alarms on the main menu. The Alarms Page consists of three main sections: • Alarms - Any items currently in alarm, first listed as a summary and then by category. •... -
Page 41: Fig. 6-11, Discrete Properties, Alarms
6.0 Web Interface, continued Each type of alarm setting is displayed with its current state, current value, and five settings: Major High, Minor High, Minor Low, Major Low, and Dead Band. The checkboxes next to each setting indicate whether the setting generates an alarm or not. Checked boxes generate an alarm. -
Page 42: Alarm Log Page
6.0 Web Interface, continued NOTICE: Any changes to parameters in the field that are deemed necessary should be recorded and conveyed to the EMS operations group for application to this device’s profile; otherwise the next download from the EMS can overwrite the field set values. -
Page 43: Configuring The Node
1. Navigate to the main Web page by entering the IP address of the transponder into the Web browser’s URL bar. 2. Log In. 3. On the main menu, click System -> Hardware Diagram. This opens the GS7000 Hardware Diagram Page as shown below. -
Page 44: General Node Configuration
The Hardware Diagram Page shows a “Configuration” table above the diagram for general node settings. See Table 6-2 for descriptions of the node configuration options. Forward Configuration, Forward Redundancy and Restore Time settings do not apply to optical hubs, and are not displayed when the Node Type is GS7000 Optical Hub. Node Configuration Options... -
Page 45: Node Module Configuration
6.0 Web Interface, continued Node Module Configuration 1. Click on the gray slot for the module to be configured, or a colored slot for the module to be reconfigured. 2. On the popup window, select the module that is installed in that slot (see Fig. 6-14). 3. -
Page 46: Other Configurations
6.0 Web Interface, continued Other Configurations Configuration choices specific to the transponder, rather than to the fiber node, can be found by selecting System -> System Data. From this page, the operator can configure the values reported by several SNMP OIDs: •... -
Page 47: Configuring The Web Access
6.0 Web Interface, continued 6.5 Configuring the Web Access A number of SNMP objects configure the behavior of the Web page. These settings can be viewed and set through a MIB browser, or configured at startup using the configuration file. There are both basic and administrative usernames and passwords. -
Page 48: Table 6-4, Ati-Mgmt-Sys-Http-Logins-Mib
6.0 Web Interface, continued Configuration and information for the transponder’s login ability can be accessed using the ATI-MGMT-SYS-HTTP- LOGINS-MIB. See the following table for the MIB file details: ATI-MGMT-SYS-HTTP-LOGINS-MIB Component Description Values This controls whether the device will accept Web interface logins from the local (Ethernet) port. -
Page 49: Cable Pinout Details
7.0 Cable Pinout Details 7.1 Ethernet Cable The following table is the pin number configuration chart for the Ethernet cable. Pin Number Configuration Chart for the Ethernet Cable Name TRP1+ TRP1- TRP2+ TRP3+ TRP3- TRP2- TRP4+ TRP4- Table 7-1, Pin Number Configuration Chart for the Ethernet Cable 018-350-B0-001, Rev. -
Page 50: Upgrading The Oex Firmware
8.0 Upgrading the OEX Firmware The OEX has the ability to download firmware to Optical Amps, Optical Switches, and the Transponder by using the CHEETAH-MGMT-UPDATE-MIB (OID 1.3.6.1.4.1.33872.2.4). NOTICE: While downloading firmware to the Optical Amps and Optical Switches there will be no communications between the transponder and any Optical Amps or Optical Switches in the Hub or Node throughout the entire firmware download process, although they will continue to function correctly. - Page 51 8.0 Upgrading the OEX Firmware, continued To start a management initiated download, set the updateServerAddress, and updateFilename to the correct values. Then set the updateControl to either startDownload(1) or forceDownload(2). The following OIDs are used for the Module Download Feature: •...
- Page 52 Fax: +561 792.7157 Fax: +852 2199.7988 Alpha reserves the right to change specifications without notice. Alpha Technologies © 2017 Alpha Technologies Inc. All Rights Reserved. Alpha is a registered trademark of Alpha Technologies. 018-350-B0-001, Rev. A (06/2017) For more information visit www.alpha.com...
Need help?
Do you have a question about the GS7000 and is the answer not in the manual?
Questions and answers