Alpha OEX-N GS7000 Technical Manual

Brand: Alpha

Model: OEX-N GS7000

Category: Networking

Type: Technical Manual

This manual is also suitable for

GS7000

Optical Ethernet Transponder GS7000

Technical Manual

Effective: June 2017

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:

The following sections contain important safety information that must be followed during the installa-

tion and maintenance of the equipment and batteries. Read all of the instructions before installing or

operating the equipment, and save this manual for future reference.

There may be multiple warnings associated with the call out. Example:

ATTENTION provides specic regulatory/code requirements that may affect the placement of equip-

ment and /or installation procedures.

ATTENTION:

NOTICE provides additional information to help complete a specic task or procedure.

NOTICE:

ELECTRICAL HAZARD WARNING provides electrical safety information to PREVENT

INJURY OR DEATH to the technician or user.

WARNING! ELECTRICAL HAZARD

FUMES HAZARD WARNING provides fumes safety information to PREVENT INJURY OR

DEATH to the technician or user.

WARNING! FUMES HAZARD

FIRE HAZARD WARNING provides ammability safety information to PREVENT INJURY OR

DEATH to the technician or user.

WARNING! FIRE HAZARD

This WARNING provides safety information for both Electrical AND Fire Hazards

WARNING! ELECTRICAL & FIRE HAZARD

CAUTION provides safety information intended to PREVENT DAMAGE to material or

equipment.

CAUTION!

GENERAL HAZARD WARNING provides safety information to PREVENT INJURY OR

DEATH to the technician or user.

WARNING! GENERAL HAZARD

3018-350-B0-001, Rev. A (06/2017)

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. If there are questions regarding the safe operation of this powering system, contact Alpha

Technologies or the nearest Alpha representative.

Alpha shall not be held liable for any damage or injury involving its enclosures, power supplies,

generators, batteries or other hardware if used or operated in any manner or subject to any condition

not consistent with its intended purpose or is installed or operated in an unapproved manner or

improperly maintained.

Contact Information

Sales information and customer service in USA

(7AM to 5PM, Pacic Time):

Complete technical support in USA

(7AM to 5PM, Pacic Time or 24/7 emergency support):

Website:

800 863 3364

www.alpha.com

360 392 2217

4 018-350-B0-001, Rev. A (06/2017)

Table of Contents

1.0 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1.2 Optical Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

1.3 Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

1.4 Technical Support Contact Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2.0 Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

2.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

2.2 Connector Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

2.3 OEX Specications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

3.0 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

3.1 Preparing the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

The OEX Startup Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

The DHCP Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

The Time Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

The TFTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

3.2 The Conguration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

3.3 Installing the OEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

3.4 Checking the LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

3.5 Conguration MIBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

ATI-MGMT-SYS-COMMS-MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

ATI-MGMT-SNMP-MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

SA-HMS-FIBERNODEGS7000-MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

4.0 Provisioning the SNMP Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

4.1 MIB Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

4.2 Acquiring the Transponders by the SNMP Manager . . . . . . . . . . . . . . . . . . . . . 29

5.0 Network Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Optical Network Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Local Ethernet Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Using the Local Ethernet Connector with the Optical Link . . . . . . . . . . . . . . . . . . 31

6.0 Web Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

6.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

6.2 Logging In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

6.3 Web Page Summaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Home Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

System Pages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Hardware Diagram Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

HFC Node Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

System Data Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Communications Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Alarms Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Alarm Log Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

6.4 Conguring the Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

General Node Conguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Node Module Conguration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Other Congurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

6.5 Conguring the Web Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

5018-350-B0-001, Rev. A (06/2017)

Figures

Fig. 1-1, The OEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Fig. 1-2, Typical SFP Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Fig. 2-1, OEX Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Fig. 2-2, OEX Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

Fig. 3-1, A Typical Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Fig. 3-2, Sample Conguration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Fig. 3-3, Fiber Node Interface Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Fig. 3-4, Transponder Slot and Interface Connector . . . . . . . . . . . . . . . . . . . . . . . . . 18

Fig. 3-5, Transponder Mounting Screw Locations . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Fig. 3-6, SFP in Place . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Fig. 3-7, Fibers Plugged Into the SFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Fig. 3-8, OEX LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Fig. 5-1, Network Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Fig. 6-1, GS7000 Home Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Fig. 6-2, Log In Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Fig. 6-3, Log In Prompt. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Fig. 6-4, System Link, Navigation Pane, GS7000 Home Page . . . . . . . . . . . . . . . . . . . 34

Fig. 6-5, Hardware Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Fig. 6-6, HFC Node Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Fig. 6-7, Alarm Settings Popup Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Fig. 6-8, System Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Fig. 6-9, Communications Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Fig. 6-10, Limit Properties, Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Fig. 6-11, Discrete Properties, Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Fig. 6-12, Alarm Log Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Fig. 6-13, GS7000 Hardware Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Fig. 6-14, Conguring Module Slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Fig. 6-15, System Data Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Fig. 8-1, Update Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

7.0 Cable Pinout Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

7.1 Ethernet Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

8.0 Upgrading the OEX Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Table of Contents, continued

6 018-350-B0-001, Rev. A (06/2017)

Tables

Table 1-1, Revision History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Table 1-2, Technical Support Contact Information . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Table 2-1, Connector Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

Table 3-1, OEX Provisioning Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Table 3-2, atiMgmtSysCommsCommon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Table 3-3, atiMgmtSysCommsCongFile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Table 3-4, atiMgmtSysCommsAccessGlobal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Table 3-5, atiMgmtSysCommsAccessTable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Table 3-6, atiMgmtSysCommsOpticalInfoTable . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Table 3-7, atiMgmtSysCommsOpticalStateTable . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Table 3-8, atiMgmtSysCommsOpticalStateTable . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Table 3-9, atiMgmtSnmpTrapTable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Table 3-10, SA-HMS-FIBERNODEGS7000-MIB. . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Table 4-1, Supported HMS MIB Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Table 4-2, Supported Vendor MIB Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Table 4-3, Additional Supported MIB Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Table 4-4, High-resolution optical power in ATI-DEV-HFC-NODES-MIB. . . . . . . . . . . . . . . 29

Table 6-1, Alarm Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Table 6-2, Node Conguration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Table 6-3, OIDs for Usernames and Passwords for Web Interface Access . . . . . . . . . . . . . 47

Table 6-4, ATI-MGMT-SYS-HTTP-LOGINS-MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Table 7-1, Pin Number Conguration Chart for the Ethernet Cable . . . . . . . . . . . . . . . . . 49

7018-350-B0-001, Rev. A (06/2017)

1.0 Introduction

1.1 Overview

The Optical Ethernet Transponder (OEX) provides the ability to manage ber nodes and optical hubs through an existing

ber optic infrastructure. Contact an Alpha Technologies representative for a complete listing of supported ber nodes.

The transponder leverages the operator’s ber optic network infrastructure and communicates with a management

system, using standard Simple Network Management Protocol (SNMP). Status monitoring is compatible with ANSI/SCTE

HMS standards.

Fig. 1-1, The OEX

The OEX:

• Uses ANSI/SCTE HMS standards

• Measures analog values and digital states, and exchanges digital data with optical modules

• Can be network managed through the existing network infrastructure

• Allows remote control and conguration of the node

• Can provide a remote upgrade of node module rmware

• Provides a ber optic based connection for node telemetry

1.0 Introduction, continued

8 018-350-B0-001, Rev. A (06/2017)

1.2 Optical Module

The OEX uses an industry-standard SFP (Small Form-factor Pluggable) optical transceiver, to provide great exibility 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 ber pair just for its communications, a standard data SFP may be chosen. More often,

the OEX communications is sharing bers with other cable plant signals, in which case a CWDM or DWDM SFP module

should be used, to coexist with other trafc using different wavelengths. In all cases, make sure the SFP is rated for

industrial temperatures, and that a compatible SFP is used at the other end of the communications link.

For SFP modules which support DDM (Digital Diagnostics Monitoring), the OEX can report the internal operating status

and alarms for the module.

Contact a Cisco or Alpha sales representative for further guidance in selecting an SFP module appropriate for the

intended application.

1.3 Revision History

This section contains revision tracking information such as document version, release date, and descriptions of changes

and new features.

Revision History - 018-350-B0

Version Date Description of Changes and New Features

PRELIMINARY 04/2017 Preliminary release, not nalized

A 06/2017 Initial release

Table 1-1, Revision History

Fig. 1-2, Typical SFP Module

1.0 Introduction, continued

9018-350-B0-001, Rev. A (06/2017)

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

North America Atlanta, Georgia

Technical Support Customer Service

Toll-Free: 1-800-722-2009

Local: 678-277-1120 (Press 3 at the

prompt)

Local: 678-277-1120

Fax: 770-236-5477

Email: [email protected]

Europe, Middle East,

Africa

Belgium

Technical Support Customer Service

Telephone #1: 32-56-445-197 Telephone: 32-56-445-444

Telephone #2: 32-56-445-155 Fax: 32-56-445-051

Fax: 32-56-445-061 Email: [email protected]

Japan Japan

Telephone #1: 81-3-5908-2153

Telephone #2: +81-3-5908-2154

Fax: 81-3-5908-2155

Korea Korea

Telphone: 82-2-3429-8800

Fax: 82-2-3452-9748

Email: [email protected]

China (mainland) China

Telephone: 82-2-3429-8800

Fax: 82-2-3452-9748

Email: [email protected]

All other Asia Pacic

countries & Australia

Hong Kong

Telephone: 852-2588-4746

Fax: 852-2588-3139

Email: [email protected]

Brazil Brazil

Telephone: 11-55-08-9999

Fax: 11-55-08-9998

Email #1: [email protected]

Email #2: [email protected]

Mexico, Central

America, Carribean

Mexico

Technical Support Customer Service

Telephone: 52-351512599 Telephone: 52-55-50-81-8425

Fax: 52-3515152599

Fax: 52-55-52-61-0893

Email: [email protected]

All other Latin

America countries

Argentina

Technical Support Customer Service

Telephone: 54-23-20-403340

ext: 109

Telephone: 770236-5662

Fax: 770-236-5888

Fax: 54-23-20-403340 ext: 103 Email: [email protected]

Table 1-2, Technical Support Contact Information

10 018-350-B0-001, Rev. A (06/2017)

2.0 Connections

2.1 Overview

The OEX communicates with the ber 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. The locations of these components are shown in Fig. 2-1 and Fig. 2-2.

Fig. 2-1, OEX Connections

LEDs

Tamper Sensor

Local Ethernet Port

Label with Transponder

Serial Number

2.0 Connections, continued

11018-350-B0-001, Rev. A (06/2017)

Connector Summary

Connector Description

SFP Slot

The SFP module is installed into the slot. The SFP must be oriented as indicated on the top of

the transponder.

Ethernet Port

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. See Section 5, “Network

Interfaces,” for details. This connector includes two LEDs, to indicate a link (green LED, closer

to the Tamper sensor) and communications acitivity (yellow LED, closer to the “Ethernet” label).

Interface Connector

The Interface Connector is the physical connection point at which the transponder attaches to

the node or optical hub. The interface connector provides the transponder power and internal

communications.

Tamper Sensor

The Tamper Sensor provides an indication of physical tampering (opening of the node

enclosure).

LED Indicators

The OEX includes two LEDs:

• POWER ON

• OPTICAL LINK

These indicate transponder status. For details on the LEDs and their indication, see Section 3.4

titled “Checking the LEDs” presented in this manual.

Interface Connector

The Interface Connector is fragile and must be handled carefully to avoid damage.

CAUTION!

Table 2-1, Connector Summary

2.2 Connector Summary

Fig. 2-2, OEX Connections

SFP

Slot

2.0 Connections, continued

12 018-350-B0-001, Rev. A (06/2017)

2.3 OEX Specications

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

13018-350-B0-001, Rev. A (06/2017)

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.

• Preparing the network

• Creating an appropriate conguration le

• Installing the OEX

• Powering the OEX and checking the LEDs for status

Please read through this entire section before attempting the rst installation.

After OEX installation, the user will also need to congure each individual node through the web page interface. That

process is described in Section 6.4, “Conguring the Node.”

3.1 Preparing the Network

The OEX interacts with a number of elements within a network system, so it is important to understand the interactions,

particularly during the OEX startup process. The following graphic depicts a summary of the OEX startup process which is

detailed in the subsequent pages.

Optical

Ethernet

Transponder

Web Client

AlphaXD /

SNMP Manager

Fault and

Performance

Management

OSS Integration

IP Network

Time

Server

DHCP

Server

TFTP

Server

Conguration FileAlpha Firmware

Image Upgrade*

Optical Hub

Power Supply

Tap

HFC

Fig. 3-1, A Typical Network

*Optionally, AlphaXD can be congured as the TFTP server for rmware updates. Refer to the AlphaXD

documentation for details.

NOTICE:

3.0 Installation, continued

14 018-350-B0-001, Rev. A (06/2017)

OEX Provisioning Process

Action Result

1 Install OEX in target device

• Prior to attaching the Fiber to SFP connectors, user has ability to

connect to OEX through local Ethernet port using 192.168.100.1 IP

address

2 Connect ber to SFP Connector

• OEX contacts the DHCP server

• Access via 192.168.100.1 is no longer available

3 DHCP returns to the OEX

• IP Address

• Conguration File name

• NTP IP Address

• TFTP IP Address

• Note: At this stage of provisioning, the OEX is still accessible using

Global Get/Set community string

4 OEX requests Time from NTP Server • NTP server returns Time of Day to the OEX

OEX requests Conguration File Data

from TFTP Server

• TFTP server provides conguration le data to OEX including at a

minimum:

• IP SNMP access range allowed

• Community string to contact OEX

• Access level (Read, read-write, none)

• Optional entries in the conguration le include:

• IPv4 setting

• Subnet Mask Prex

OEX is now online with a valid IP

address and contains access data

provided by the conguration le

• Note: Once a correct entry (IP range, community & access level) is

populated in the atiMgmtCommsAccess Table, the Global Get/Set

community access is suspended

Table 3-1, OEX Provisioning Process

The OEX Startup Process

When the OEX rst starts up (after receiving power within the ber node, or following a remote reset), it performs a

number of steps:

1. Check for a valid optical connection. The SFP must be installed and signaling a valid link (usually indicating that

the optical receiver sees a good carrier). Until these are true, the OEX operates in a local access mode (see

section 5 for details) and none of the remaining network steps can yet occur.

2. The OEX attempts to obtain an IP address from a DHCP server. Until this succeeds, the OEX has no address on

the network.

3. If the successful DHCP offer included any time servers, the OEX attempts to obtain the current date and time.

4. If the successful DHCP offer included a TFTP server and a TFTP le, the OEX attempts to load the specied

conguration le from the specied server. This allows the network to specify the operating contions of the OEX.

The last two steps are optional but strongly recommended: the OEX can come online, and be accessed remotely, as long

as it has a network connection and can get an IP address from some DHCP server. However, without access to a time

server, the OEX will report an incorrect time of day (used in a number of the HMS-compatible SNMP objects). Ensure that

the OEX receives a conguration le (described in Section 3.2) to set up specic security restrictions in order to avoid

unauthorized access to the transponder that could affect the operation of the ber node.

3.0 Installation, continued

15018-350-B0-001, Rev. A (06/2017)

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 specic DHCP offer for a particular

device, and providing the options within the DHCP offer to support the time of day and conguration le operations.

The most direct way to tie a particular DHCP offer to a particular device is by the MAC address. The MAC address of the

OEX is indicated on its labels, so that the DHCP server can be set up (prior to the OEX installation) to provide specic

offer details when that OEX comes online.

To support the time server functionality, the DHCP offer should include either option 42, to specify a single NTP server

(RFC 1305), or option 4, to specify one or more TIME servers (RFC 868). NTP is the preferred format; if both options

are present, the OEX tries the NTP server rst before trying the TIME server. Either time server format provides the OEX

with Universal Coordinated Time (UTC), so the DHCP offer usually also includes option 2 to set the local time offset (the

current adjustment from UTC to local time).

To support conguration les for the OEX, the DHCP offer should include a TFTP server and a TFTP lename (or boot

lename). These can be stored in the BOOTP protocol elds for server address and bootle name, or they can be options

66 (server name) and 67 (le name). The OEX considers the options to override the BOOTP elds.

Consult your DHCP server documentation for details of how to manage these options.

The Time Server

The current time of day is provided by any time server with a reasonably accurate clock (or which is in turn synchronized

to a better external time source). This server can be running NTP (RFC 1305), or the much older TIME protocol (RFC

868). (The same server can run multiple protocols.)

If the OEX receives information about an NTP server in its DHCP offer, it will connect using the “SNTP” (Simple Network

Time Protocol) subset of the full NTP specication. NTP is the preferred time protocol for the OEX.

If the OEX receives information about a TIME protocol server in its DHCP offer, it will connect using the UDP version of

the protocol, not the TCP version.

The TFTP Server

The conguration le for an OEX, and also any rmware update le, is stored on a TFTP (Trivial File Transfer Protocol)

server (RFC 1350).

The TFTP protocol allows anyone on the network to download and upload les. As a security precaution, congure the

TFTP server to not allow uploads into the server, to prevent unauthorized alteration of the les. (The OEX will never

attempt a TFTP upload.) Actually editing conguration les or making update les available should be performed using the

normal le access, and access right security, of the server itself.

The Optix or AlphaXD server can be congured as a TFTP server for convenience of performing rmware updates.

3.0 Installation, continued

16 018-350-B0-001, Rev. A (06/2017)

3.2 The Conguration File

The security of the OEX and its control of the ber node depends upon the conguration le settings. Verify that the

transponder conguration le has been successfully tested prior to deploying transponders into the network in quantity.

The OEX manages SNMP remote access and notication/trap destinations according to its internal conguration settings.

These settings and many others may be changed at startup by the conguration le. Almost any setting that can be done

on the OEX through a sufciently privileged SNMP access may also be performed by the conguration le. (The only

exceptions are settings that only become possible after the ber node has fully initialized, because in normal operation the

conguration le is processed sooner than the node initialization completes.)

The conguration le is a simple text le containing a list of settings, where each has an OID (the SNMP address of the

item), the type of the setting, and the setting value. No special tool is needed for editing this le; a text editor such as

Notepad in Windows or gedit in Linux is sufcient. The OEX ignores blank lines and any line that begins with the pound

sign (“#”), allowing the technician to arrange the conguration le and add comments to help with future maintenance of

the settings.

Here is an example of a simple conguration le:

This example sets up a single SNMP access permission, where any IP address in the 172.16.1.x subnet is granted

read/write access using the community string “Secret.” It also sets up the server at 172.16.1.42 as the recipient of trap

messages.

The access information uses atiMgmtSysCommsAccessTable within ATI-MGMT-SYS-COMMS-MIB, while the trap

destination uses atiMgmtSnmpTrapTable within ATI-MGMT-SNMP-MIB. For further details, refer to Section 3.5.

Fig. 3-2, Sample Conguration File

Unless atiMgmtSysCommsAccessTable contains at least one valid entry granting write access to someone, the

OEX allows SNMP access by anyone using the global community strings in atiMgmtSysCommsAccessCmtyGet

and atiMgmtSysCommsAccessCmtySet.

NOTICE:

3.0 Installation, continued

17018-350-B0-001, Rev. A (06/2017)

The supported types for conguration values are:

• int - an integer value

• string - a text string value

• octet - an octet string, expressed as some number of two-digit hexadecimal values

• ip - an IPv4 address

The value is considered to be anything after the type and any following spaces, up to the end of the line.

As the OEX processes the conguration le, it keeps a count of successful entries processed as well as errors (settings it

was unable to perform). Details of the rst error encountered (if any) are also stored: the line number within the le, and

the specic complaint. Lastly, the OEX separately counts potentially valid entries that were skipped because the particular

index wasn’t available (such as a rmware update provisioning entry that doesn’t apply to this particular node). These

results are all visible to a MIB browser; refer to the objects beginning with “atiMgmtSysCfgFile” in section 3.5. These

results are also displayed on the System Data web page. This should help with getting a conguration le properly set up

the rst time.

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. 3-4.

Fig. 3-3, Fiber Node Interface Connector

3.0 Installation, continued

18 018-350-B0-001, Rev. A (06/2017)

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.

Exercise caution when installing the OEX to assure proper alignment between the connectors to

avoid damaging the pins.

CAUTION!

Fig. 3-5, Transponder Mounting Screw Locations

3.0 Installation, continued

19018-350-B0-001, Rev. A (06/2017)

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 rmly.

Fig. 3-6, SFP in Place

Install the ber(s) into the SFP. Route the ber(s) neatly to the ber management tray to avoid loose cabling inside the

node.

Fig. 3-7, Fibers Plugged Into the SFP

3.0 Installation, continued

20 018-350-B0-001, Rev. A (06/2017)

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 briey during startup when the OEX rst gets power, and is solid thereafter. If this LED goes

off or blinks again after having showed a solid “on,” it means the transponder is resetting. Unless this was commanded

remotely, any reset potentially indicates a problem with the transponder itself.

The Optical Link LED should be lit when the OEX is operating with the optical (SFP) link, or off when the OEX is in local

operation mode (this is described in more detail in section 5). This LED blinks whenever the OEX is transitioning into

either optical operation or local operation. (For example, this will blink while the OEX is waiting for a DHCP address over

the optical link.)

During normal network operation, both LEDs will be on and steady.

Page is loading ...

Alpha OEX-N GS7000 Technical Manual

Brand: Alpha

Model: OEX-N GS7000

Category: Networking

Type: Technical Manual

This manual is also suitable for

GS7000

Download PDF

report

Alpha OEX-N GS7000 Technical Manual

This manual is also suitable for

Alpha OEX-N GS7000 Technical Manual

Related papers

Other documents