OlenCom MG-iP Series Reference Manual

October 2006 Copyright © 2006 OlenCom Electronics ltd.. All rights reserved. Specifications and information are subject to change without notice.

MG-IP Reference Manual Notice Page Release Information Date Rev. Change Level Comments Catalog No. June 2006 3.3.0 Firmware version 3.3.0 Revised with additional information on CLI, RCP, and other subjects DC-RM-MG-IP- 1/MG-IP-4 October 2006 3.4.0 Firmware version 3.4.0 Revised with additional information on Clock Recovery, Download Files, Corrections to a number of incorrect CLI examples DC-RM-MG-IP- 1/MG-IP-4 Proprietary Notice No part of this publication may be copied in any form, by photocopy, microfilm, retrieval system, or by any means now known or hereafter invented without the prior written permission of Olencom Inc. Olencom Inc. and the Olencom logo are trademarks of Olencom Inc. All other trademarks used in this document are the property of their respective owners. Olencom Inc. reserves the right to make changes to the product(s) or information contained herein without notice. No liability is assumed as a result of their use or application. No rights under any patent accompany the sale of any such product(s) or information. Contact Information Technical Support e-Mail: [email protected] OlenCom ltd. Web Site www.olencom.com

About this Document The MG-IP-1 and MG-IP-4 units are fully integrated TDM over Packet (TDMoP) gateways that multiplex T1/E1 circuits and 100 Mbps user Ethernet data ports onto any standard Ethernet/IP network or link. The units support rapid design of standards-compliant TDM over packet circuit emulation equipment. They can be used in standalone applications or in hosted environments. The MG-IP-1, which supports a single E1/T1 port only, is targted as a CPE device and is limited to a single pseudowire session, while the MG-IP-4 provides support for 4 E1/T1 ports and may be configured as an aggregator, aggregating multiple pseudowires opposite multiple MG-IP-1 devices. This document describes the functionality, pinout, power requirements, and management of the MG-IP-1 and the MG- IP-4. Loopback mechanisms and troubleshooting suggestions are also provided. The MG-IP-1 and MG-IP-4 feature identical software and board layouts. All CLIs and management options are exactly the same on both modules. While many of the examples in this manual focus on the MG-IP-1, they are equally applicable to the MG-IP-4. Further Reading If you would like further information about the MG-IP-1 and MG-IP-4, or if you have questions not answered by these documents, please contact [email protected] or visit our web site at http://www.olencom.com. Feedback We welcome feedback on our products and our documentation. If you have any comments or suggestions about this product, contact your supplier and give them the product name and a concise explanation. Alternatively, you can send your feedback directly to us at [email protected] with the following information: ƒ The document title ƒ The document’s catalog number ƒ The page number(s) to which your comments refer ƒ Your comments

1 Functional Description.....................................................................................11 Overview......................................................................................................................... 11 Circuit Emulation Service (CES)..................................................................................... 11 MG-IP CES Operation...................................................................................................12 MG-IP in CES Topology................................................................................................12 Fractional Operation ....................................................................................................... 12 CAS Signaling.................................................................................................................12 Grooming.........................................................................................................................12 CCS Signaling.................................................................................................................12 Header Options...............................................................................................................12 Timing Modes ................................................................................................................. 13 Classic TDM Timing.......................................................................................................14 Loopback Timing ............................................................................................................14 Internal Timing ................................................................................................................14 External Timing...............................................................................................................15 Line Timing......................................................................................................................15 Differential Timing ..........................................................................................................16 Recovered Clock Mode.................................................................................................17 Adaptive Timing..............................................................................................................17 Cascading Two Modules...............................................................................................21 Recovered Timing Holdover .........................................................................................22 Packet Delay Variation (Jitter) Buffer ..........................................................................22 Packet Reordering .........................................................................................................22 Interfaces ........................................................................................................................ 22 IP Address Configuration ..............................................................................................23 WAN IP Configuration Limitations ...............................................................................24 DHCP Option Support ...................................................................................................24 Functional Block Diagram............................................................................................... 26 T1/E1 to Packet ..............................................................................................................26 Packet to T1/E1 ..............................................................................................................26 LAN to WAN....................................................................................................................26 WAN to LAN....................................................................................................................27 Ethernet Configuration...................................................................................................27 Control Processor...........................................................................................................27 UART .............................................................................................................................. 27 LED Interface.................................................................................................................. 28 MG-IP Configuration ....................................................................................................... 28

Contents ii Pseudowire Sessions...................................................................................................... 28 Configuration Database .................................................................................................. 28 WAN.................................................................................................................................28 LAN/Management (rear panel).....................................................................................29 T1/E1 Interface ...............................................................................................................29 TDM over Packet Application ......................................................................................... 30 Packet Headers .............................................................................................................. 30 CAS Signaling with CESoPSN and CESoEth Headers.................................................. 31 Jitter Buffer/Underrun/Overrun ....................................................................................... 32 Replacement Frames and Packet Reordering...........................................................33 Jitter Buffer Operation....................................................................................................33 End-To-End Delay Calculation.....................................................................................34 Bandwidth per Pseudowire ...........................................................................................34 Framing and Signaling Options ...................................................................................... 35 Clocks ............................................................................................................................. 35 LED Interface.................................................................................................................. 36 LEDs ............................................................................................................................... 37 TDM and Pseudowire Error Handling............................................................................. 38 System Overview............................................................................................................38 TDM Defects and Failures ............................................................................................38 Status Indications...........................................................................................................43 Error Handling.................................................................................................................46 Application Signaling......................................................................................................52 Errored Second Counters .............................................................................................53 CES Configuration Parameters....................................................................................53 References......................................................................................................................53 2 Management Options .......................................................................................55 The Command Line Interface (CLI) ................................................................................ 55 CLI Script Files................................................................................................................ 55 Script File Format...........................................................................................................55 TLV Files......................................................................................................................... 57 TLV Structure..................................................................................................................57 Rules of Construction ....................................................................................................58 SNMP.............................................................................................................................. 60 Automatic Management and Provisioning ...................................................................... 60 Safe Download (UDL) Mode.........................................................................................60 File Download via TFTP Client.....................................................................................60 Dynamic Downloading/Processing of CLI Script-based Configuration ..................61 Dynamic Firmware Download through a TFTP/DHCP Client..................................61 Syslog Error Reporting ..................................................................................................61

Configuring the Management PC ................................................................................... 66 TELNET Using LAN........................................................................................................ 68 Managing Users.............................................................................................................. 68 User Management Tasks..............................................................................................69 Manage User Accounts Example ................................................................................... 70 Managing the CONSOLE Interface ................................................................................ 74 CONSOLE Management Tasks...................................................................................75 CONSOLE Management Example ..............................................................................75 Managing Basic Functionality......................................................................................... 75 Basic Board Management Tasks.................................................................................76 Global Configuration Status............................................................................................ 81 Managing LAN and WAN Interfaces............................................................................... 83 LAN/WAN Management Tasks ....................................................................................83 Ethernet Interface Information......................................................................................84 Sample Ethernet Configuration....................................................................................89 Managing the T1/E1 Interface ........................................................................................ 91 T1/E1 Management Tasks............................................................................................92 T1/E1 Interface Information ..........................................................................................93 T1/E1 Example Configuration......................................................................................... 99 Managing the MG-IP unit.............................................................................................. 103 Sessions and Pseudowires.........................................................................................103 Out of Stream Signaling ..............................................................................................103 Default Configuration...................................................................................................105 Getting Started..............................................................................................................106 Session Management Tasks in Unstructured Mode ...............................................116 Session Management Tasks in Structured Mode....................................................118 Structured Mode Example 1 – CESoPSN ................................................................121 Structured Mode Example 2 – MEF-8 (CESoEth)...................................................123 Managing SNMP........................................................................................................... 125 SNMP Management Tasks.........................................................................................125 Request Managers.......................................................................................................127 Trap Managers .............................................................................................................128 4 SNMP Support.................................................................................................131 The Management Model............................................................................................... 131 SNMP Management Information Base (MIB) ............................................................... 132 MG-IP SNMP Support................................................................................................... 133 MIB Support.................................................................................................................. 133 Standard MIBs ..............................................................................................................133 Draft MIBs......................................................................................................................135

Contents iv Private MIBs..................................................................................................................137 Irregular Functionality ..................................................................................................138 Private MIB - General Definitions ................................................................................. 141 MIB Relations................................................................................................................ 141 SNMP Request Manager Configuration ....................................................................... 142 Configuration Sequence ............................................................................................... 142 Pseudowire Creation with Assigned DS-1 Port .......................................................142 Pseudowire Creation with Assigned Timeslots........................................................142 Updating DS1 Parameters..........................................................................................143 Updating the Pseudowire’s Attached Timeslots ......................................................144 Setting SNMP Trap Destination .................................................................................144 Upgrading the Software Image...................................................................................145 Traps............................................................................................................................. 145 Default SNMP Settings ................................................................................................. 145 Complete Configuration Examples ............................................................................... 145 Unframed Pseudowire.................................................................................................146 Framed Pseudowire.....................................................................................................147 5 Command Line Interface................................................................................149 How to Access the CLI.................................................................................................. 151 Connecting via the CONSOLE Port...........................................................................151 Connecting via Telnet and a Network Interface.......................................................151 CLI Command Description Conventions....................................................................... 152 CLI Command Hierarchy .............................................................................................. 153 Summary of CLI Commands ........................................................................................ 155 Configuration Commands ...........................................................................................155 Clock configurathion ....................................................................................................155 Ethernet Configuration Commands (LAN & WAN)..................................................156 T1/E1 Configuration Commands................................................................................156 Port Configuration Commands...................................................................................156 Profile Definition Commands......................................................................................157 CONSOLE Configuration Commands.......................................................................157 SNMP Configuration Commands...............................................................................157 TDM over Packet Configuration Commands............................................................157 TDM Error Reporting Commands ..............................................................................158 Session Configuration Commands ............................................................................159 General Configuration Commands ............................................................................159 Monitoring Commands ................................................................................................159 Ethernet Monitoring Commands (LAN and WAN)...................................................160 T1/E1 Monitoring Commands.....................................................................................160 Port Monitoring Commands........................................................................................160

CONSOLE Monitoring Commands............................................................................161 SNMP Monitoring Commands....................................................................................161 TDM over Packet Monitoring Commands.................................................................161 Session Configuration..................................................................................................161 General Monitoring Commands .................................................................................162 Diagnostics Commands ..............................................................................................162 Admin Commands........................................................................................................163 User Commands...........................................................................................................163 CLI Command Descriptions.......................................................................................... 163 6 Testing the MG-IP ...........................................................................................165 Loopback Options......................................................................................................... 165 Using the Get Status Command to Evaluate Performance .......................................... 168 Troubleshooting Guide.................................................................................................. 169 Appendix A CLI Commands ...........................................................................A-1 CLI Command Lookup Matrix........................................................................................A-1 CLI Command Descriptions...........................................................................................A-5 AddNewSession ...........................................................................................................A-5 AddRequestManager...................................................................................................A-6 AddTrapManager .........................................................................................................A-7 AddUser.........................................................................................................................A-8 ApplyChanges...............................................................................................................A-9 Bert...............................................................................................................................A-10 CalibrateJitter..............................................................................................................A-11 ChangePassword.......................................................................................................A-12 ConfigHeaderCESoETH............................................................................................A-13 ConfigHeaderSAT/CESoP........................................................................................A-14 ConfigSesTargetIP.....................................................................................................A-15 ConnectClockToSession...........................................................................................A-16 DeleteUser...................................................................................................................A-17 DownLoadFile.............................................................................................................A-18 ForceUserLogout........................................................................................................A-19 FunctionalTest ............................................................................................................A-20 GetActiveUsers...........................................................................................................A-21 GetBertStatus .............................................................................................................A-22 GetBoardData.............................................................................................................A-23 GetCLIPrompt.............................................................................................................A-24 GetClockStatus...........................................................................................................A-25 GetConfig.....................................................................................................................A-26 GetConfigDBStatus....................................................................................................A-31

Contents vi GetConfigIfs ................................................................................................................A-32 GetConfigUarts...........................................................................................................A-33 GetDateTime...............................................................................................................A-34 GetDefGateway ..........................................................................................................A-35 GetFirmwareStatus ....................................................................................................A-36 GetGlobalConfig.........................................................................................................A-37 GetGlobalStatus .........................................................................................................A-38 GetInitDnldStatus .......................................................................................................A-41 GetMacAddress..........................................................................................................A-42 GetModifiedConfigPorts ............................................................................................A-43 GetRequestManagers................................................................................................A-44 GetRequestTrapPorts................................................................................................A-45 GetRunningConfigPorts ............................................................................................A-46 GetSessionTimeSlots ................................................................................................A-47 GetSnmpStatistics......................................................................................................A-48 GetStatistics................................................................................................................A-52 GetStatus.....................................................................................................................A-55 GetStatusBoard..........................................................................................................A-58 GetStatusIfs.................................................................................................................A-59 GetSystemDesc..........................................................................................................A-61 GetTimeSlotMap.........................................................................................................A-62 GetTrapManagers ......................................................................................................A-63 GetUsers......................................................................................................................A-64 GetVersion...................................................................................................................A-65 ListClocks ....................................................................................................................A-66 ListOfSessions............................................................................................................A-67 PwTDMCfgRtpHdrUsed ............................................................................................A-68 Reload..........................................................................................................................A-69 RemoveRequestManager .........................................................................................A-70 RemoveSession .........................................................................................................A-71 RemoveSyslogServer................................................................................................A-72 RemoveTrapManager................................................................................................A-73 RenameSession .........................................................................................................A-74 Replace........................................................................................................................A-75 ReplaceReload ...........................................................................................................A-76 SatopSendLBitOnAIS ................................................................................................A-77 SetActiveClock............................................................................................................A-78 SetCESappTestMode................................................................................................A-79 SetChannelBandwidth...............................................................................................A-80 SetCLIPrompt .............................................................................................................A-81

Contents vii SetConfigBitStreamClockingMode ..........................................................................A-82 SetConfigCESClock...................................................................................................A-83 SetConfigCESEmulationType ..................................................................................A-84 SetConfigCESIP.........................................................................................................A-85 SetConfigCESPaylength ...........................................................................................A-86 SetConfigCESVlan.....................................................................................................A-87 SetConfigEth...............................................................................................................A-88 SetConfigEthFlowControl..........................................................................................A-89 SetConfigEthLimit.......................................................................................................A-90 SetConfigLIUlineBuildout ..........................................................................................A-91 SetConfigLIULineCode..............................................................................................A-92 SetConfigLIURxTerm.................................................................................................A-93 SetConfigMPLS ..........................................................................................................A-94 SetConfigUART ..........................................................................................................A-95 SetDateTime ...............................................................................................................A-96 SetDefaultDB ..............................................................................................................A-97 SetDefGateway...........................................................................................................A-98 SetDynamicMACLpbk................................................................................................A-99 SetEmulationCircuitID..............................................................................................A-100 SetExternalClockDirection ......................................................................................A-101 SetExternalClockFreq..............................................................................................A-102 SetFramedParams...................................................................................................A-103 SetIdlePattern ...........................................................................................................A-104 SetIPConfig ...............................................................................................................A-105 SetLayer2App ...........................................................................................................A-106 SetLFlagPolicy..........................................................................................................A-107 SetLIUDynamicLpbk ................................................................................................A-108 SetLIULpbk................................................................................................................A-109 SetLOPSPolicy .........................................................................................................A-110 SetPayloadSuppression..........................................................................................A-111 SetPingEnable..........................................................................................................A-112 SetPortsDisable........................................................................................................A-113 SetPortsEnable.........................................................................................................A-114 SetPortState..............................................................................................................A-115 SetRDPolicy..............................................................................................................A-116 SetRequestPort ........................................................................................................A-117 SetRFlagPolicy .........................................................................................................A-118 SetRxEqualizerGainLimit ........................................................................................A-119 SetSessionPorts.......................................................................................................A-120 SetSessionTimeSlots...............................................................................................A-121

Contents viii SetSigIdle ..................................................................................................................A-122 SetSyslogDisable .....................................................................................................A-123 SetSyslogEnable ......................................................................................................A-124 SetSyslogServer.......................................................................................................A-125 SetTDMoPSessionDisable......................................................................................A-126 SetTDMoPSessionEnable ......................................................................................A-127 SetTrapPort...............................................................................................................A-128 SetUserTimeout........................................................................................................A-129 List of Figures Figure 1: MG-IP-1/MG-IP-4 Application Example .................................................... 11 Figure 2: CES Packet Format ................................................................................... 13 Figure 3: Classic TDM Clocking................................................................................ 14 Figure 4: Loopback Timing Mode.............................................................................. 14 Figure 5: Internal Timing Mode ................................................................................. 15 Figure 6: External Timing Mode................................................................................ 15 Figure 7: Line Timing ................................................................................................ 16 Figure 8: Differential Timing...................................................................................... 16 Figure 9: Recovered Clock Mode.............................................................................. 17 Figure 10: Adaptive Loopback Timing....................................................................... 18 Figure 11: Adaptive Line Timing ............................................................................... 18 Figure 12: Adaptive Internal Timing .......................................................................... 19 Figure 13: Adaptive External Timing......................................................................... 19 Figure 14: Global External Timing............................................................................. 20 Figure 15: Network Timing Mode.............................................................................. 20 Figure 16: Cascading Two MG-IP unitss .................................................................. 21 Figure 17: MG-IP-1 Interfaces................................................................................... 23 Figure 18: MG-IP-4 Interfaces................................................................................... 23 Figure 19: MG-IP-1 Functional Block Diagram ......................................................... 26 Figure 20: MG-IP-4 Functional Block Diagram ......................................................... 26 Figure 21: SATOP Header........................................................................................ 30 Figure 22: CESoPSN Header ................................................................................... 30 Figure 23: CESoEth Header ..................................................................................... 31 Figure 24: Signaling Packet Format.......................................................................... 31 Figure 25: Jitter Buffer Operation.............................................................................. 33 Figure 26: External Clock Jumpers........................................................................... 35

Figure 28: MG-IP – Front Pannel.............................................................................. 36 Figure 29: Point-to-multipoint TDM over Ethernet Pseudowire................................. 38 Figure 30: TDM Performance Monitoring.................................................................. 45 Figure 31: CES Gateway .......................................................................................... 46 Figure 32: Loss of Signal Trace Example ................................................................. 48 Figure 33: RAI Transfer............................................................................................. 51 Figure 34: Loss of Packets........................................................................................ 51 Figure 35: Standalone Application ............................................................................ 55 Figure 36: T1 Framing, 56K Data Channel ............................................................. 104 Figure 37: E1 pcm30 Format .................................................................................. 104 Figure 38: Network Management Model................................................................. 131 Figure 39: MIB Relations......................................................................................... 141 Figure 40: Command Directory Hierarchy............................................................... 154 Figure 41: Loopback Test Setup-Single Port .......................................................... 166 Figure 42: Loopback of the WAN Interface............................................................. 166 List of Tables Table 1: Supported DHCP Options........................................................................... 24 Table 2: Frames Per Packet vs. Jitter Buffer Size .................................................... 33 Table 3: Bandwidth Requirements (SATOP Header)................................................ 34 Table 4: LED Description .......................................................................................... 37 Table 5: Failure Integration/deintegration Times (Sec)............................................. 42 Table 6: PDH Near-End Failure Hierarchy................................................................ 42 Table 7: PDH Far-End Failure Hierarchy .................................................................. 43 Table 8: Relations between PDH Near-End and Far-End Failures........................... 43 Table 9: Status Bit Settings....................................................................................... 43 Table 10: Incoming Packet Flow-based Indications.................................................. 45 Table 11: Structure-agnostic Event Handling............................................................ 47 Table 12: Structure-aware Event Handling ............................................................... 49 Table 13: TLV Structure Specification....................................................................... 58 Table 14: Syslog Messages...................................................................................... 62 Table 15: User Groups.............................................................................................. 68 Table 16: User Management..................................................................................... 69 Table 17: CONSOLE Management........................................................................... 75 Table 18: Basic Board Management......................................................................... 76

Contents x Table 19: LAN/WAN Management............................................................................ 83 Table 20: Ethernet Configuration Commands........................................................... 85 Table 21: T1/E1 Management CLI Commands......................................................... 92 Table 22: T1/E1 Configuration .................................................................................. 94 Table 23: Port Configuration ..................................................................................... 95 Table 24: Profile Configuration.................................................................................. 95 Table 25: T1/E1 LIU loopback................................................................................... 96 Table 26: PortLIU loopback....................................................................................... 97 Table 27: Session01 Default Parameters ............................................................... 105 Table 28: Global Configuration Parameters............................................................ 107 Table 29: List Session Parameters ......................................................................... 109 Table 30: Unstructured Session Parameters .......................................................... 111 Table 31: Unstructured Mode Session Management Commands .......................... 116 Table 32: Unstructured Session Parameters .......................................................... 116 Table 33: Structured Mode Session Management Commands .............................. 118 Table 34: Structured Session Parameters .............................................................. 119 Table 35: SNMP Management................................................................................ 125 Table 36:Correlation between dsx1LineType and Framing Mode .......................... 139 Table 37: dsx1SignalMode Functionality ................................................................ 139 Table 38: Pseudowire PSN Type............................................................................ 140 Table 39: Pseudowire Creation with Assigned DS-1 Port....................................... 142 Table 40: Pseudowire Creation with Assigned Timeslots ....................................... 143 Table 41: Updating DS1 Parameters ...................................................................... 143 Table 42: Updating the Pseudowire’s Attached Timeslots...................................... 144 Table 43: Setting SNMP Trap Destination .............................................................. 144 Table 44: Upgrading the Software Image ............................................................... 145 Table 45: Description of Loopback Modes.............................................................. 165 Table 46: Reported Jitter Parameters..................................................................... 169 Table 47: Observations and Corrections................................................................. 171

11 1 Functional Description Overview The MG-IP-1 and MG-IP-4 are DTM Over IP gateway units for Ethernet/IP networks. They perform point-to-point (MG-IP-1) or point-to-multipoint (MG-IP-4) emulation of T1 or E1 synchronous circuits by incorporating TDM bitstreams into packets and transmitting them over packet-switched networks as streams of packets. These streams are referred to as pseudowires (PW). A pseudowire can transport a full TDM circuit or a bundle of time slots from a TDM circuit. A MG-IP unit at the opposite side of the network converts the pseudowires back into a TDM circuit. The TDM over-packet circuit emulation service (CES) that transforms the TDM circuit to a pseudowire and vice versa uses a dynamic jitter buffer and clock recovery to deliver consistent performance even over the variable timing of the packet network. See Figure 1 for a graphical view of a mixed MG-IP-1 and MG-IP-4 application. In this example, point-to-multipoint topology is used where the MG-IP-1 is the CPE device and the MG-IP-4 is configured as an aggregator, aggregating multiple pseudowire sessions opposite multiple MG-IP-1 modules. In the example, fractional T1 circuits, supporting six PBXs at different locations, are aggregated at a central location. Each pseudowire only uses the bandwidth necessary to support the needs of an individual customer, instead of a full T1. Adaptive timing is used, with clocking of the aggregator units based on the accurate timing of the Central Office. Each Slave MG-IP-1 unit performs adaptive clock recovery from the stream of packets in the pseudowire. Circuit Emulation Service (CES) CES refers to the process of creating pseudowires that transport TDM circuits across a packet network. Since a TDM circuit is bi-directional, the pseudowire CES process is also bi-directional. For example, at one end of the pseudowire the TDM circuit is broken down into fixed size packets; a header is added to each packet and the packet is transmitted. At the other end of the packet network, the header is removed from the packet, and a TDM circuit is re-constructed. Central Office Switch 4xE1 MG-iP Slave MG-iP Slave MG-iP Slave MG-iP Slave MG-iP Slave MG-iP Slave Fractional E1 PBX Fractional E1 PBX Fractional E1 PBX Fractional E1 PBX Fractional E1 PBX Fractional E1 PBX PacketSwithed Network MG-iP Master

12 MG-IP CES Operation The circuit emulation can be in either unstructured or structured mode. In unstructured mode, the entire T1/E1 circuit is transferred regardless of the structure of frame and time slot boundaries. This is called “structure agnostic”. In structured mode, full or fractional frames can be packetized and transferred between MG-IP units. E1 and T1 data is structured as frames based on an 8 KHz frame sync. Each frame is divided into 8-bit time slots (32 slots for E1, 24 slots for T1). The traffic is depacketized on the other side of the packet network to recreate frames with the selected time slots in their corresponding time slot positions. MG-IP in CES Topology The MG-IP-1 can be configured to operate in point-to-point topologyopposite another MG-IP-1. It is limited to support a single pseudowire. The MG-IP-1 can also operate as a CPE device in point-to- multi point topology opposite a MG-IP-4 aggregator. The MG-IP-4 can be configured to operate in point-to-point topology opposite another MG-IP-4, with support for four pseudowire sessions. It can also operate as an aggregator device in point-to-multipoint topology opposite MG-IP-4 or MG-IP-1 CPEs. The MG-IP-4 is capable of aggregating up to ten pseudowire sessions. Fractional Operation When a fractional TDM circuit is transported on a pseudowire only the selected time slots are sent. Even if all the voice channel time slots on a port are sent, frame synchronization is not transmitted with the voice channel data. E1 time slot 0 (zero) and the T1 F bit are not transmitted. Rather, frame synchronization is recreated at the receiving end of the pseudowire. CAS Signaling In structured mode, TDM circuits that use channel associated signaling (CAS) carry this information within the TDM stream. Circuits in E1 format carry this information in time slot 16. Circuits in T1 format carry channel signaling in one bit of each channel in one out of every six frames in a super frame. Signaling information can optionally be sent either through a separate pseudowire or within the same pseudowire in a separate stream so that the signaling can be inserted in the recreated TDM frame in the appropriate place according to the signal type. When fractional TDM is transported on a pseudowire, the MG-IP units utilize the minimal Ethernet WAN bandwidth required for transmitted time slots by transmitting only the selected time slots and by sending signaling out-of-stream. Grooming A single TDM circuit can be divided up into multiple pseudowires. A group of time slots can be sent to a port on one target MG-IP unit and another group of time slots from the same circuit can be sent to a port on the same or on a different MG-IP units. This functionality is only applicable to the MG-IP-4 and grooming is supported only when the MG-IP- 4 is configured as an aggregator. CCS Signaling Common Channel Signaling and other signaling methods that use a dedicated channel, such as PRI and BRI, are supported transparently by the MG-IP-1 and MG-IP-4. The dedicated channel is included in the list of time slots assigned to the pseudowire and is transmitted at all times with the voice channels. This approach assumes that each group of voice channels has its own signaling channel. Header Options Pseudowire packets have headers that are used to define the connection between a pair of MG-IP units. The MG-IP units support standard header encapsulation as specified in IETF-PWE3 SAToP/CESoP

13 and MEF-8. Three packet header formats are supported: the SAToP (structureagnostic TDM over packet) header for unstructured data, the CESoPSN (circuit emulation service over packet switched network) header for structured data and the CESoEth (circuit emulation service over ethernet) header as defined by the Metro Ethernet Forum (MEF-8) format. The CESoEth header can be used for either structured or unstructured circuits. See Packet Headers section. All standard protocol headers include control information to be exchanged between the pseudowire peer, and provide status information such as alarms and defects occurring on the TDM interface. Figure 2: CES Packet Format Timing Modes The Circuit Emulation Service enables convergence and transport of TDM circuits (E1/T1) over packet-switched networks. To do so, it must feature a mechanism capable of maintaining and keeping the TDM clock synchronized between peers of a pseudowire, in order to maintain E1/T1 circuit clock continuity across the packet network, and to meet the standards of ITU G.823 and G.824. To achieve this requirement, Olencoms’ products have been designed to support a variety of timing modes, including: ƒ Loopback timing ƒ Internal timing ƒ External timing ƒ Line timing ƒ Recovered timing (adaptive/differential timing) ƒ Differential timing Changing the timing mode will require to reset the MG-IP unit. MG-IP units only support a Single Clock Domain. It is the customer’s responsibility to feed the CES device with TDM ports, all of which are timed by the same clock source (this applies to the MG-IP-4 only).

14 Classic TDM Timing As shown in Figure 3, in classic TDM clocking, the TDM clock is contained in and recovered by the TDM data bit in the received bit. Figure 3: Classic TDM Clocking Loopback Timing In loopback timing mode (see Figure 4), TDM ports on the MG-IP (CES device) use the clock received from the TDM equipment as a transmit clock to the TDM equipment. In a multipe E1/T1 module (i.e. the MG-IP-4), it is the customer’s responsibility to feed the MG-IP device with TDM ports, all of which are timed by the same clock source. Figure 4: Loopback Timing Mode Internal Timing In internal timing mode (see Figure 5), TDM ports on the MG-IP (CES device) use the on-board internal clock (Stratum-4 compatible local oscillator OCXO or TCXO) as a transmit clock to the TDM equipment.

15 Figure 5: Internal Timing Mode External Timing In external timing mode (see Figure 6), TDM ports on the MG-IP (CES device) use the external clock (received through the external clock pin) as a transmit clock to the TDM equipment. The frequency of the external clock may differ from that of the T1/E1 clock, in which case the units translates and derives the TDM clock from the external clock frequency received. If the external clock is disconnected, the MG-IP automatically switches to the onboard TCXO/OCXO. Figure 6: External Timing Mode The folowing clock ferquencies are supported: External clock frequency Derived TDM port frequency T1 T1 E1 E1 10.24MHz T1 10.24MHz E1 16.384MHz T1 16.384MHz E1 Line Timing In line timing mode (see Figure 7), TDM ports on the MG-IP (CES device) use the clock received on port 1 as a transmit clock for all ports. The clock is also exported to the external clock pin (if so configured). Should the clock on port 1 fail or the port be disabled, automatic switchover to the Free Running clock 1ppm (TCXO/OCXO) occurs. As soon as the failure condition ends, the MG-IP device

16 will revert to the original clock source (line timing mode is not applicable to the MG-IP-1 as it features only a single E1/T1 port). Figure 7: Line Timing Differential Timing Differential timing (see Figure 8) is designed to deliver the phase variations of the service clock relative to a common reference clock, so that the receiver can reconstruct the service clock by replicating these variations. This scheme assumes the availability of stratum-1 traceable common reference clock on both ends. The sender generates an RTP timestamp based on a common reference clock, and sampled every fixed number of service clock cycles (normally equivalent to one packet size). The RTP timestamp delivers the phase information about the TDM service clock, compared to the common reference clock. The receiver captures and analyzes the RTP timestamp, and detects the sender’s frequency and phase shift. Figure 8: Differential Timing Receiver Sender Timestamp Generator Differential Clock Recovery Common Clock Common Clock Local Clock TDM Clock Recovered TDM Clock RTP timestamp In differential timing mode, there are no logical master and slave entities. Each side of the pseudowire is a sender of a pseudowire packet carrying the RTP timestamp and performing diferrential timing clock recovery (DCR) on the pseudowire received with the RTP time stamp. As such, the limitation of a single session per port (on the “slave”) is no longer valid. The following common clock/RTP time stamp frequencies are supported: TDM Clock EXT Clock RTP Time stamp TDM Clock EXT Clock RTP Time stamp T1 1544MHz 25M E1 2048MHz 25M

17 10.24MHz 10.24M 10.24MHz 10.24M 16.384MHz 16.384M 16.384MHz 16.384M Recovered Clock Mode In recovered clock mode (see Figure 9), the clock is recovered from the CES packet stream received from the packet-switched network using two mechansims: adaptive timing algorithm or differential timing algorithm. The mechanisms differ as follows: in adaptive timing, the recovery mechanism is based on the rate of the packets received from the PSN, while in differential timing, it is based on the RTP time stamp included within the packet and the existance of a reference clock on both sides of the pesudowire. All ports are clocked according to the recovered clock of one of the sessions (PWS). It is possible to configure a primary/secondary pesudowire. The clock recovery mechanism uses the primary pseudowire for the clock recovery algorithm and may manually be switched to the secondary pseudowire either if the primary one fails or autmatically, when the primary pseudowire is manually disabled. The defaults primary and secondary pseudowires are the first and second created sessions, respectively. A configuration option enables switching from the primary to the secondary and vice versa. It is possible to change the configuration of either the primary or secondary pseudowire when it is the currently active clock recovery channel. Clock recovery first switches to the backup pseudowire and, once the active pseudowire becomes the new backup pseudowire, it can be modified. If the active pseudowire is manually disabled, clock recovery automatically switches to the alternate pseudowire, if configured and enabled (if the active pseudowire is the primary one, it will attempt to move to the secondary pseudowire, while if the active pseudowire is the secondary one, it will attempt to switch to the primary pseudowire). If no alternate pseudowire is enabled, it will switch to the internal clock. Figure 9: Recovered Clock Mode Figure 9 presents an example of a clock recovered through adaptive timing. Adaptive Timing Adaptive timing is applicable to point-to-point and to point-to- multipoint (aggregation) topologies. This mode defines two logical CES device configurations, as follows: ƒ Master – can be configured to line, external and internal timing ƒ Slave – is always configured to “recovered timing”

18 In PTMP topology, the aggregator is always the master, while in PTP topology, one MG-IP unit is the master and the other is a slave (this is arbitrarily selected). Adaptive Timing Applicaton Configuration The folowing sections describes possible MG-IP adaptive timing application configurations (adaptive timing is always set on the slave). Adaptive Loopback Timing Application Configuration In adaptive loopback timing mode (see Figure 10), the master is configured to loopback timing only if all ports are locked to the same source clock (this is the customer’s responsibility and is only applicable to the MG-IP-4). The slave is configured to recovered timing. Figure 10: Adaptive Loopback Timing Adaptive Line Timing Application Configuration In adaptive line timing mode (see Figure 11), the master is configured to line timing, while the slave is configured to recovered timing. Figure 11: Adaptive Line Timing

19 Adaptive Internal Timing Application Configuration In adaptive internal timing mode (see Figure 12), the master is configured to internal timing, while the slave is configured to recovered timing. Figure 12: Adaptive Internal Timing Adaptive External Timing Application Configuration In adaptive external timing mode (see Figure 13), the master is configured to external timing, while the slave is configured to recovered timing. Figure 13: Adaptive External Timing

20 Global External Timing (Also Called Direct Timing) Application Configuration In global external timing mode (see Figure 14), both sides acquire an accurate external clock and the TDM equipment needs be locked to this timing mode (i.e. work in loopback timing mode). Figure 14: Global External Timing Network Timing Application Configuration In network timing mode (see Figure 15), it is assumed that both sides of the TDM equipment are synchronized through an accurate external clock. Both sides are configured to loopback timing. Figure 15: Network Timing Mode

21 Cascading Two Modules The MG-IP units supports "external clock in" and "external clock out" via its dedicated mini-BNC connector. Therefore, it can be configured as a TDM clock source (External Clock In). It may be used as the TDM Tx clock for all connected TDM circuits. However, it may also be configured to export the unit’s clock (Clock Out). This could be used to cascade two units in a system (see Figure 16) when, for example, line timings are used. Figure 16: Cascading Two MG-IP unitss Output Clock Options The external clock connnector may be configured to output theMG-IP’s clock. For example, this may be used when cascading two units. The exported clock depends on the mode of operation as follows:

22 ƒ In case of internal timing - the onboard TCXO/OCXO clock is exported ƒ In case of external timing – clock export is not possible, as the same connector is used for external input ƒ In case of line timing – the Port 1 clock is exported ƒ In case of loopback timing – the Port 1 clock is exported ƒ In case of adaptive recovered timing – the recovered clock is exported Recovered Timing Holdover The holdover mechanism provides the following: ƒ Rapid recovery after a short service interruption/impairment (i.e. the clock is maintained until service is resumed) ƒ Compliance under traffic modulation (this will be supported in future releases of the product) The following are examples of possible triggers to adaptive timing holdover: ƒ Link disconnects ƒ Remote TDM disconnects ƒ Protection switching on TDM ƒ Protection switching on PSN ƒ PSN network route change: (delay changes) ƒ Adding switch/router to the network ƒ Remove switch/router from the network ƒ Dynamic flow route change (i.e. bandwidth-related) This holdover is only applicable on recovered mode. Packet Delay Variation (Jitter) Buffer As pseudowire packets traverse the packet network, the delay varies from packet to packet. This is especially evident in wireless networks that may forward packets in bursts. To compensate for this packet delay variation (PDV), the MG-IP uses a jitter buffer, which can be sized according to the maximum PDV of the network in order to avoid underrun and overrun conditions. A high network PDV requires a long jitter buffer, which translates to delay of the T1/E1 stream. The module status displays the current jitter buffer length as well as its maximum and minimum values. Packet Reordering A pseudowire packet sent over a complex network with different routes to the destination may arrive ahead of a previous packet. The MG-IP-1 and MG-IP-4 reorder the received pseudowire packets automatically, based on a sequence number in the received packets. If a packet arrives so late that it misses its transmission time to the TDM circuit, a filler packet will be sent to the T1/E1 circuit and the late packet will be dropped. Module status reports the number of filler packets and dropped packets. Interfaces The MG-IP-1and MG-IP-4 has the following interfaces: • Two network interfaces, WAN and LAN, located on the front panel.

23 • LAN/Management Port – for out-of-band management, and bandwidth control LAN interface. • One or Four T1/E1 interface. • One console interface. • One External Clock interface. • One power jack, either AC (external power adapter) or DC single/redundant (Block Terminal) The MG-IP has a built-in T1/E1 framer/LIU. The T1/E1 interface can be connected to standard T1/E1 equipment via the external connectors. The MG-IP multiplexes the LAN Ethernet traffic and the pseudowire for transmission to the WAN. The traffic is transmitted so that the pseudowire has priority over forwarded LAN traffic (default priority is 0x5). The maximum bandwidth of the LAN and the WAN interfaces are configurable to support limited bandwidth applications. Pseudowire and other traffic received on the WAN interface is demultiplexed and output through the LAN interface and the T1/E1 interface. Certain data packets, such as management packets, are processed locally on the MG-IP, and therefore are not forwarded to other interfaces. Figure 17: MG-IP-1 Interfaces Figure 18: MG-IP-4 Interfaces MG-iP IP Address Configuration MG-IP units offer three options for configuring IP addresses for the two Ethernet ports (WAN, LAN/Management (located on the rear side): ƒ Static IP address: (This is the factory default setting) the user defines the IP address for each port. The IP address can be ƒ The same value for both ports ƒ Different values if the ports are on different sub-nets, and for out of band management ƒ TCP/IP Disabled: The port does not support IP traffic at all. This will be the case, for example, when using CESoETH headers on pseudowire streams. ƒ IP configured Dynamically: The IP address for a port is configured dynamically at power up using a DHCP client. At power on, the embedded DHCP client sends a request for an IP address and default gateway for each dynamically configured port. TDM traffic will not start to flow until IP addresses are received for the dynamically configured ports. The user must ensure that there is a DHCP server available to respond to the DHCP client request for an IP address. Each Ethernet port can be configured independently, using the sic command line interface (CLI) command. This command selects the option and sets the IP address and sub-net mask if the static IP option was chosen. The “set default gateway” CLI command is effective only if the static option was chosen.

24 The LAN and WAN GetConfiguration (gc) CLI command shows the selected mode. When the dynamic configuration option is selected, the LAN and WAN GetStatus Command shows whether the product is waiting on receipt of an IP address from a DHCP server before starting operations Note that the MG-IP units perform neither routing, VLAN switching of traffic. Traffic received on the rear LAN port not addressed to the MG-IP is forwarded to the WAN. Similarly, traffic received on the WAN is forwarded without change to the rear LAN port WAN IP Configuration Limitations When DHCP is active on the WAN port, LAN port and WAN port IP addresses must belong to different subnets. However, a configuration option is provided that allows both IP addresses to be identical (shared IP). When attempting to configure a LAN port IP address after DHCP is answered, the LAN IP address configuration will be checked against the DHCP IP address. If they belong to the same subnet and are not identical, a warning is printed yet the command will succeed. If the LAN IP address is already configured on boot, when the DHCP answer is received, it will be checked against the LAN IP address. If they are not identical and reside on the same subnet, the system will reboot. DHCP Option Support The DHCP protocol allows the DHCP client running on MG-IP units to request additional information beyond the IP address. MG-IP units utilize numerous DHCP options to automatically acquire CLI script configuration files or new firmware. Table 1 describes the DHCP options supported and system behavior in case of missing/illegal options or failures during the use of these options. Table 1: Supported DHCP Options DHCP Field/Option Behavior if Missing/Incorrect DHCP Option Comments IP address Return to DHCP discovery This attribute is expected to be received in the “yiaddr” DHCP field If the LAN is configured with static IP and the DHCP IP address received is on the same subnet but not identical, the system will send swerr + unsolicited and return to DHCP discovery. If the lease time expires, the system will send Syslog and reboot Default gateway Return to DHCP discovery Router (option 3) Subnet mask Return to DHCP discovery Subnet mask (option 1)

25 DHCP Field/Option Behavior if Missing/Incorrect DHCP Option Comments TFTP server IP This field is optional TFTP server name - (option 66). This attribute is expected to be received in the “siaddr” DHCP field If the configuration file name was received, the TFTP server IP should be received as well, otherwise the system will send swerr + unsolicited messages (no Syslog) and return to DHCP discovery Config file path This field is optional Bootfile name (option 67). This attribute is epxected to be received in the “file” DHCP field The file name must end with a TXT extension for CLI scripts or TLV files. If the file extension is not supported, or if the TFTP download of the file fails, the system will send a Syslog message and reboot. In case of an error in file processing, provisioning will end with an error indication (but with no reboot) Syslog server This field is optional Log server option (option 7) If this field is set, Syslog messages indicating errors or success will be sent to it during the provisioning process. Server identifier This field is optional Server identifier (option 54) Reboot due to problems associated with DHCP or DHCP option processing will occur after a delay of a few seconds, and a periodic error message (unsolicited) will be displayed with a description of the error and the time left until the imminent reset. Configuring the DHCP Server To support the above options, the DHCP server should be configured as follows: ƒ Router Option - specifies default gateway IP address (option 3) ƒ Log Server Option - specifies Syslog server ip address (option 7) ƒ Server Identifier - specifies DHCP server IP address (option 54) ƒ Subnet Mask - specifies host’s subnet mask (option 1) ƒ Bootfile name (option 67) ƒ TFTP server name - specifies the TFTP IP address (option 66)

26 Functional Block Diagram The following figures present functional block diagrams of the MG-IP-1 and of the MG-IP-4. Figure 19: MG-IP-1 Functional Block Diagram Figure 20: MG-IP-4 Functional Block Diagram T1/E1 to Packet The T1 or E1 circuit is detected by the LIU and converted from an analog to a digital bitstream. The framer detects frame boundaries and passes complete frames to the packetizer. The packetizer accumulates bytes until the defined pseudowire packet size is reached. The packet is then queued for transmission. When the packet is ready for transmission, a special header is added and the packet is transmitted via the WAN interface. Packet to T1/E1 Packets received on the WAN interface with special headers are placed on a queue, where the de- packetizer/reorderer extracts T1/E1 frames from the packets in the order they were sent. The queue serves as a jitter buffer to adjust for varying arrival times of the incoming pseudowire packets. Frames are sent to the framer for transmission under control of a transmission clock either derived from the local Rx clock (Master) or recovered from the received packetized data (Slave). LAN to WAN Packets received from the rear LAN/Managemet interface are queued for transmission and sent with a lower priority than pseudowire data. The bandwidth of LAN traffic transmitted via the WAN interface can be limited by setting a limit on the LAN traffic bandwidth transmitted through the WAN port.

27 LAN Bandwith Management Guidelines Given the network bandwidth limit of the PSN (packet-switched network) connected to the WAN port, LAN port bandwidth should be calculated and limited (using the cel CLI command) so as not to affect CES flow. For example, if the PSN bandwidth is assumed to be 10 Mbps and the MG-IP-4 uses four full E1/T1 connections (which add up to 9 Mbps required for CES flow), the LAN port bandwidth limit should be set to 1 Mbps. To calculate the exact bandwidth required for the TDM CES flow (after the port and sessions have been configured), use the Config\TDM_Over_Packet>ggc CLI command and observe the “Enable session BW” and the “Disable session Bandwidth” fields. Add 1.8 Mbps overhead to their values. LAN limitation is available only on the REAR LAN interface which marked as "LAN/Management". In case you need to limit the front LAN interface it can be done only via the EEPROM. The flow of pseudowire packets between two MG-IP units requires a dedicated bandwidth guarantee to maintain an error-free circuit emulation service. MG-IP units provide several methods of prioritizing pseudowire traffic: ƒ The bandwidth limitation of LAN traffic through the WAN as described above ƒ Assignment of VLAN 802.1p and VLAN priority to the traffic transmitted through the WAN, which can be used by the PSN network to provide a higher priority to the pseudowire However, it is the network manager’s responsibility to configure the network in such way that each pseudowire has the necessary bandwidth and priority to ensure timely arrival of CES packets. WAN to LAN Packets without special headers received on the WAN interface are queued for transmission on the LAN/Management interface. In case you don't need any bandwidth limitation, use the front LAN interface which is not passed via the main proccessor, and transferred via internal switch directly to the LAN interface. Ethernet Configuration The MG-IP Ethernet ports may be configured as specified by the 802.3xx standard. However, although WAN configuration can be performed in various modes, the user should always configure the WAN port with 100Mbps Full duplex and not any other configuration, as these options conflict with internal switch requirements and may couse performance degradation. Also WAN port PHY mode should be OFF. LAN port configuration can be changed, but must have PHY address set to 5 at all time. Control Processor The control processor detects activity on the UART and processes CLI commands received from the UART. Telnet sessions addressed to the module IP address are also processed by the control processor. The control processor reports status via the LED interfaces. It also sends unsolicited messages to report alarms or changes in interface status and manages SNMP communications. UART The UART is used for management and control information. The application firmware can be reprogrammed and the configuration database can be modified through the UART.

28 LED Interface Interface activity and system status can be monitored using the LED interfaces. MG-IP Configuration The following section provides an overview of MG-IP configuration. There are a number of ways to define or modify the unit configuration: ƒ The Command Line Interface (CLI) is accessible using the UARTs or via Telnet over either the LAN or WAN interface. The CLI can modify the parameters in the module configuration database. ƒ CLI script files – CLI commands grouped into a CLI script file, a text file edited and located offline on the user’s PC. The script file is aumatically copied and processed via TFTP (see CLI Script Files section) ƒ SNMP – standard SNMP V2 is used for Get/Set and Trap operations (see SNMP Support section) ƒ TLV files – TLV files comply with the CableLabs standard and are binary files (type, length, value) containing SNMP commands. TLV files are located remotely, copied via the TFTP protocol and activated on MG-IP startup (see TLV Files section). Pseudowire Sessions The pseudowire between two MG-IP units is defined with a TDM over packet session. A session defines the source TDM port, the format of the pseudowire packet, the maximum jitter, the header format, and the address of the target MG-IP. The target MG-IP requires a corresponding session definition. Configuration Database MG-IP units are configured using a configuration database that is stored in on-board Flash memory. Many database parameter changes take effect only when a modified database is saved as the new startup database and the module is restarted. Session definitions are an exception to this. After changing the parameters of a session and saving them, the session can be disabled and then re-enabled. The session will resume using the new parameters. Many port configuration parameters can also be changed without requiring a module reset. The following is a list of the configurable parameters contained in the configuration database: WAN ƒ Interface IP mode (Static, DHCP or none) ƒ Interface IP and subnet mask ƒ Auto-negotiation enable/disable ƒ Auto-negotiation advertising values ƒ MII Clock source (DTE, DCE) ƒ Flow control on/off ƒ Bandwidth limit (0 to 100 Mbps or unlimited)

29 LAN/Management (rear panel) ƒ Interface IP mode (Static, DHCP or none) ƒ Interface IP and subnet mask ƒ Auto-negotiation enable/disable ƒ Auto-negotiation advertising values ƒ MII Clock source (DTE, DCE) ƒ Flow control on/off ƒ Bandwidth limit (0 to 100 Mbps or unlimited) T1/E1 Interface ƒ Line format: T1/E1 ƒ Clock selection (Loopback/Recovery/Internal/External) ƒ Transmit clock polarity ƒ Receive clock polarity ƒ LIU Line code ƒ LIU Line buildout ƒ LIU Receive equalizer gain limit ƒ LIU Internal receive termination ƒ Signaling mode ƒ Per-interface SNMP enable/disable line status trap ƒ Target IP address ƒ Maximum jitter ƒ Payload length ƒ Clock accuracy ƒ Clock locking range ƒ Selected time slots for n x 64 operation ƒ Header format - SAToP/CESoPSN, or CESoEth ƒ Header port numbers, Ethertype, IP TOS ƒ VLAN ID ƒ Target MAC address ƒ ECID ƒ MPLS labels Serial Connection (UART) ƒ Baud rate ƒ Mode of operation SNMP ƒ Request manager port number. ƒ Request managers ƒ Trap destination port number

30 ƒ Trap manageres ƒ MIB2 system object parameters: name, description, contact, and location TDM over Packet Application The TDM over Packet CES application takes the E1 or T1 circuit received on the T1/E1 port, packages it into pseudowire packets, adds a special header, and transmits the packets via the WAN, according to the session definition. The application also receives the pseudowire packets, unpacks the data and transmits it to the E1 or T1 circuit via the T1/E1 ports. Packet Headers There are three packet header formats: the SATOP (structure-agnostic TDM over packet) header for unstructured data, the CESoPSN (circuit emulation service over packet switched network) header for structured data, and the CESoEth (circuit emulation service over Ethernet) header as defined by the Metro Ethernet Forum (MEF-8). ƒ SATOP The header format complies with the IETF PWE3 SAToP standard for unstructured TDM over packet switched networks (Figure 21). The protocol is routable and can be configured to use a VLAN to improve priority of the tunnelled traffic. The figure shows only the RTP portion of the header plus the SATOP control word. The header requires 62 bytes per packet, Ethernet, IP, UDP and RTP headers and the SAToP control word. Figure 21: SATOP Header ƒ CESoPSN The header format complies with the IETF PWE3 CESoPSN standard for structured TDM over packet switched networks (Figure 22). The protocol is routable and can be configured to use a VLAN to improve priority of the tunnelled traffic. The figure shows only the RTP portion of the header plus the CESOP control word. The header requires 62 bytes per packet, including Ethernet, IP, UDP and RTP headers and the CESoPSN control word. Figure 22: CESoPSN Header ƒ CESoEth The header complies with MEF-8: “Implementation Agreement for the Emulation of PDH Circuits over Metro Ethernet Networks” (Figure 23). It supports both unstructured and

31 structured pseudowires. The header consists of an Ethernet header, an emulated circuit identification (ECID), and a CESoEth control word, for a total of 22 bytes. A VLAN or an MPLS label can be added in front of the header. Since MEF communications assumes only layer 2 operations, an ARP (address resolution protocol) message cannot be used to locate peer MG-IP units based on their IP address. Therefore, sessions defining pseudowires using the CESoEth need to have the destination MAC address defined explicitly using the appropriate CLI or RCP command. Similarly, ECIDs and MPLS labels are user-provided. The product does not communicate directly with an MPLS label server. Figure 23: CESoEth Header ƒ The RTP header is optional in all encapsulations ƒ Backwards compatibility issues: ƒ The behavior of RTP header existence differs from that of former versions ƒ In previous versions, RTP was always on (CESoP/SAToP), while in this release, it is disabled by default. As such, when working with this release opposite earlier releases, the RTP header must be enabled ƒ In differential timing mode, the default is “enabled" CAS Signaling with CESoPSN and CESoEth Headers CAS signaling is performed out-of-stream from the remainder of the data. It may be sent via a separate pseudowire or within the same pesudowire, but in a separate stream. MG-IP units implement the IETF PW3 draft standard for out of stream CAS signaling. When MG-IP units detect a signaling change in time slot 16 (E1) or in the robbed bit of a time slot (T1), they send an additional packet to peer MG-IP units receiving the pseudowire containing that time slot. The message contains the current state of the signaling bits for each time slot included in the pseudowire. The signaling message is sent three times on approximately 5 msec intervals. If another signaling change is detected for one of the timeslots included in a particular pseudowire before three messages were sent, additional messages are sent until three identical messages in a row have been sent. A signaling packet is sent every five seconds when no signaling changes are detected. When sent in a separate stream, the signaling message has the same header as packets containing TDM data, except that both M bits are set, indicating that it is a signaling packet. The payload of a signaling packet is four bytes for each time slot included in the pseudowire. The first byte of the four contains a hex 9 followed by the ABCD bits for the corresponding timeslot. The rest of the bytes have a value of zero. See Figure 24. The packet is padded out to the minimum packet length of 64 bytes if necessary. Figure 24: Signaling Packet Format

32 MG-IP configuration supports one protocol at a time and mixing of PSN headers is not allowed. In other words, CES sessions may be either SAToP, CESoPSN or CESoETH sessions, with no mixing allowed Jitter Buffer/Underrun/Overrun As packets traverse the packet network, the arrival delay varies from packet to packet. To accommodate this packet delay variation (PDV), the MG-IP uses a jitter buffer, whose main purpose is to smooth out variation in CES frame arrival time. Data is played out of the jitter buffer onto the TDM service at constant rate. The delay through this buffer needs to be as short as possible, in order to reduce TDM service latency, but long enough to absorb known variation in the network packet delay (PDV). The MG-IP supports a jitter buffer that can be sized according to the maximum PDV expected for the specific network in order to avoid under run and overrun conditions. ƒ An “overrun” condition occurs when the jitter buffer cannot accommodate the newly arrived packet due to insufficient storage space. Packets are then discarded and counted as overrun packets. ƒ An “underrun” condition occurs when there is no correctly received CES payload ready to be played out on the TDM interface, and filler packets are played out instead. This may occur due to a frame getting lost on the Ethernet network, or discarded due to error conditions. Typically, in order to minimize end-to-end delay, the maximum jitter is set to the lowest value possible, given the conditions of the network. Based on this value, a number of packets received over the network are buffered before bitstream transmission begins. The number of packets in the jitter buffer is calculated based on the maximum jitter in milliseconds and the packet payload length. For example, with a packet payload of three frames on an E1 circuit, one packet is transmitted every 375 microseconds. If the maximum jitter setting is 10 milliseconds, the MG-IP will create an initial 27-packet backlog (10 msec/.375 msec = 26.6). While setting the jitter buffer size, the user configures the normal jitter buffer operating point. This configuration should correspond to the previously measured PDV of the network. The entire size of the jitter buffer will actually be larger than that, to accommodate larger latencies that occur from time to time. However, this situation is not recommended as, should the delay last longer than the total size of the buffer, it will eventually lead to discarded packets that will overflow this size. In a low-PDV environment, the jitter buffer will vary in length by only one or two packets. If the maximum jitter setting matches the network PDV, the maximum and minimum jitter may vary by a larger span. Underrun and overrun occurrences indicate that the MG-IP parameters should be adjusted. See Using the Get Status Command to Evaluate Performance on page 168.

33 To support the clock recovery calculation, the application buffers a minimum of 1.5 packets. With the three-frame-per-packet example above, this represents less than 1 millisecond of delay, which falls within the minimum jitter setting. It is possible to configure the Jitter Buffer to a minimum of 1 * packet_length. However, to guarantee error-fee flow, we recommend a minimum settingg of 1.5 * packet_length. Table 2 shows the relationship between frames per packet and the valid jitter buffer size. Table 2: Frames Per Packet vs. Jitter Buffer Size No. of Frames in Payload Max. Jitter Range (msec) 2 to 5 1 to 200 6 to 10 2 to 200 11 to 16 3 to 200 17 to 21 4 to 200 22 to 26 5 to 200 28 to 32 6 to 200 34 to 36 7 to 200 38 to 42 8 to 200 44 to 46 9 to 200 Replacement Frames and Packet Reordering Another cause for “underrun” is due to a packet getting delayed or lost in the packet network. This condition is detected based on sequence numbers in the packet headers. If a packet with the right sequence number is not available at the right time, a packet’s worth of TDM frames made up of a filler pattern is sent in its place. If the packet eventually arrives late, it will be discarded. “Late” in this context means later than twice the maximum jitter setting. MG-IP units perform packet reordering automatically. Jitter Buffer Operation Figure 25 describes jitter buffer operation. Figure 25: Jitter Buffer Operation ƒ Late Ethernet packets: the number of packets that arrived after their scheduled playout time, although the jitter buffer may not necessary be full. By the time they arrived, a filler packet was already delivered instead. These packets are effectively discarded. See MEF-8 Section 6.6.3.

34 ƒ Underrun Ethernet packets: the jitter buffer underrun condition occurs when there is no correctly received ToP payload ready to be played out on the TDM interface, and filler packets are played out instead. This may occur due to frames getting lost on the Ethernet network, or discarded due to error conditions. ƒ Overrun Ethernet packets: the jitter buffer overrun condition occurs when the jitter buffer cannot accommodate the newly arrived packet in its entirely (e.g. due to insufficient storage space). ƒ Invalid Sequence Ethernet Packets: packets with sequence numbers completely outside the expected range. These packets are automatically discarded. End-To-End Delay Calculation The end-to-end delay of a CES frame can be calculated as follows: End-to-End delay = (Packetization Delay + Tx Processing Delay) + Constant Network Delay + (Maximum Jitter Buffer Delay + Rx Processing Delay) ƒ Packetization Delay - 0.125 milisecond * number of frames configured (payload size) ƒ Tx Processing Delay - depends on the configuration and will always be shorter than 1 ms. ƒ Constant Network Delay - Constant delay of the network. Varying delay (or delay variation) will be absorbed by the jitter buffer. ƒ Maximum Jitter Buffer Delay - The size of the preset maximum jitter buffer ƒ Rx Processing Delay - depends on the configuration and will always be shorter than 1 ms. Bandwidth per Pseudowire The amount of bandwidth required by a pseudowire drops as a function of the number of frames encapsulated in each packet. More frames per packet payload means fewer packets per second, and therefore fewer packet headers. Table 3 lists sample network bandwidth requirements for different packet payload sizes when the data is unstructured. Table 3: Bandwidth Requirements (SATOP Header) Line Format No. of Frames Per Packet Packets/Sec. Bandwidth Required (Mbps) 2 4000 4.032 4 2000 3.040 8 1000 2.544 16 500 2.296 E1 32 250 2.172 2 4000 3.538 4 2000 2.541 8 1000 2.042 16 500 1.793 T1 32 250 1.668

35 Framing and Signaling Options MG-IP units support two framing options each for E1 and T1 ports: ƒ E1: PCM30 or PCM31 ƒ T1: D4 or ESF E1 frames are transmitted from a MG-IP to its peer without time slot 0. Time slot 16 can be assigned to a session unless the TDM port is defined as PCM30. In that case, time slot 16 is used for CAS signaling and cannot be assigned to a specific session. A T1 frame consists of 193 bits: 8 x 24 time slots plus the F-bit. The F-bit is not sent in a pseudowire. When the MG-IP is configured for T1 and the channel bandwidth is 64Kbps, all eight bits of a time slot are used for data. If the channel bandwidth is configured for 56Kbps, the robbed bit is used for channel associated signaling and is transmitted out-of-stream. Clocks External Clock: Input: 1.544 MHz or 2.048 MHz clock (LVTTL ONLY for BNC connector). The device uses this as the TDM Tx clock (configured as input using CLI). Used either via the BNC connector, or via one of the E1/T1 interfaces. When using the BNC connector, a jumper on the internal board is used to select this external clock input. Jumper No J30 must be shorted. Output: 1.544 MHz or 2.048 MHz TDM Tx clock used by the device loopback, or internal clock on the Master, or the recovered clock on the Slave (configured as output using CLI). Used either via the BNC connector, or via on of the E1/T1 interfaces. When using the BNC connector, a jumper on the internal board is used to select this external clock output. Jumper No J31 must be shorted. Figure 26: External Clock Jumpers Internal Clock: System Clock Reference: 1ppm system clock provided by the device temperature- compensated crystal oscillator (TCXO). The TCXO is sufficiently accurate to meet the ITU standards for jitter and wander. If a more stringent standard is required, a more accurate and stable clock source can be provided by the user application. This could be an oven-controlled crystal oscillator (OCXO) with 0.05ppm (25MHz) precision or better installed on the internal board for use in systems requiring extra precision clock recovery. A jumper on the internal pigitailed board is used to select this internal clock source. See the bellow picture for PIN settings. J30 J31

36 Figure 27: OCXO Jumper Location LED Interface Led indicators are according to the following table: Figure 28: MG-IP – Front Pannel MG-iP Full Duplex / Collision LED Link / Activitiy LED

37 LEDs The MG-IP comes with the following LEDs that provide status information about traffic activity and performance of the unit. The bellow tables describes the functionality of the LEDs Table 4: LED Description LED Name Description of Function WAN/LAN Link LEDs Lit when port is connected to network. WAN/LAN Activity LEDs Commanded to light when a frame is transmitted from or received on the port. Status Link LED (Green) Alarm LED (Yellow/Red) Port not configured or commanded down. Off Off Normal-link is up. Green Off Red alarm: framing error. Green Red Red alarm: loss of carrier. Off Red Yellow alarm. Off Yellow Blue alarm. Green Flashing Yellow T1/E1 Link and Alarm LEDs One pair per port; only the first port is in use when the MG-IP-1 is used; the MG-IP-4 uses all four ports Port in loopback. Flashing green Yellow System Status LED Red/Green LED. Green: System is operating correctly: TDM transmit and receive is operating with both the T1/E1 interface and with the peer unit. Flashing green: T1/E1 send or receive or communications with the peer unit is not operating correctly. Alternating red/green: Functional test in progress, with no failure. Flashing red: Failure during functional test. Red: Power on test failed. Power On LED Green LED. Lit when power is on.

38 TDM and Pseudowire Error Handling This section describes the implementation of error handling in Olencom products’ TDM and pseudowire interfaces. The document summarizes the requirements of relevant T1 and E1 standards, as well as the Circuit Emulation IETF CESOP/SATOP drafts, the Docsis BSoD and the MEF-8 PDH Implementation Agreement. This section covers: TDM defects and failures Pseudowire defects Failure reporting and transfer across the network System Overview A simplified system diagram is shown in Figure 29 below. A pseudowire is depicted as it heads towards the TSP (TDM Service Processor) and is converted into a packet flow by the IWF (Interworking Function). At the peer device, packets are received by the IWF and converted back to the TDM interface at the TSP. A TSP may support one or more TDM interface ports (e.g. 4 x E1/T1 are supported by the MG-IP-4). Similarly, an IWF may support one or more pseudowires. A description of the mapping of TDM interfaces and pseudowires is beyond the scope of this document. Defects and failures are detected on the TSP and IWF RX interfaces. Error conditions are signaled to the peer TDM device on the TDM TX interface by transmission of AIS, RAI or idle signaling patterns. Error conditions are signaled to the peer IWF across the PSN (Packet Switched Network) via the L, R and M bits of the pseudowire packet flow’s Control word. Figure 29: Point-to-multipoint TDM over Ethernet Pseudowire RX IWF RX TSP Not all of the functionality described in this section will initially be implemented in Olencom products. Some may be implemented gradually. TDM Defects and Failures The following defect definitions are specified in RFC3895, based on corresponding standard documents. TDM Defects AIS Defect AIS defect- for D4 and ESF links, the “all ones” condition is detected at a DS1 line interface upon an unframed signal with a “ones” density of at least 99.9% being observed for a time equal to or greater than T, where 3 ms <= T <= 75 ms (in the Dallas framer, this is set to 3 ms and is not configurable) The AIS is terminated upon observation of a signal not meeting the configured “ones” density or the unframed signal criteria for a period equal to or greater than T. For E1 links, the “all ones” condition is detected at the line interface as a string of 512 bits containing fewer than three zero bits. TDM Terminal Equipment TX IWF TX TSP TDM Terminal/ Switching Equipment

39 OOF (Out-Of-Frame) Defect This defect occurs whenever errors in the incoming framing pattern are discovered. This can occur when 2 of 4, 2 of 5, or 3 of 5 framing bits are in error. A reframe clears the OOF defect. OOF is not declared when AIS is present. For T1 links, an Out of Frame defect is declared when the receiver detects two or more framing errors within a 3 ms period for ESF signals and within a 0.75 ms period for D4 signals, or two or more errors out of five or fewer consecutive framing-bits. For E1 links, an Out Of Frame defect is declared when three consecutive frame alignment signals have been received with an error. Once an Out Of Frame Defect is declared, the framer starts searching for a correct framing pattern. The Out of Frame defect ends when the signal is in frame. In-frame occurs when there are fewer than two frame bit errors within a 3 ms period for ESF signals and within a 0.75 ms period for D4 signals. For E1 links, the Out of Frame defect is cleared when: ƒ In frame N, the frame alignment signal is correct, and ƒ in frame N+1, the frame alignment signal is absent (i.e., bit 2 in TS0 is a one), and ƒ in frame N+2, the frame alignment signal is present and correct LOS Defect (Line Defect) A LOS (Loss Of Signal) defect is declared when no pulses have been detected during a defined period of time, as follows: ƒ For DS1, the Loss Of Signal defect is declared upon observation of 175 +/- 75 contiguous pulse positions with no pulses of either positive or negative polarity. The LOS failure is cleared upon observation of an average pulse density of at least 12.5% over a period of 175 +/- 75 contiguous pulse positions, starting with the receipt of a pulse. ƒ For E1 links, the Loss Of Signal failure is declared when 255 consecutive zeroes are detected (E1RCR2.RCLA= 0) RDI Defect While ANSI T1.231.02-2003 does not define the RDI defect and defines only the RAI failure, ITU-T G.0775 and G.0705 distinguish between the RDI defect and RAI failure. RAI definitions will be made using the ITU-T terminology so that the final behavior of the system will comply with both ANSI T1.231.02-2003 and G.0705/G.0775. ƒ RDI defect for T1 lines - RDI definitions for DS1 lines are adopted from ANSI T1.231.02- 2003, 9.1. For DS1 links, RDI defect is declared as soon as a DS1 terminal determines that it is receiving an RAI signal from the Far-End. The RDI defect is cleared as soon as the DS1 terminal determines that it is no longer receiving an RAI signal from the Far-End ƒ For T1 SF (D4) links, the RAI signal is sent by setting bit 2 of all DS0 channels to "0" for the entire duration (and at least for 1 second) of an LOS, LOF or AIS failure ƒ For T1 ESF links, the RAI signal is sent by a repeating 16-bit pattern consisting of eight "ones" followed by eight "zeroes" for the entire duration (and at least for 1 second) of an LOS, LOF or AIS failure ƒ RDI defect for E1 lines - RDI definitions for E1 lines are taken from G.0775, 6.1 and 6.2 ƒ For E1 links carrying basic frame structures, a Remote Defect Indication (RDI) defect at 2048 kbit/s path termination functions is detected when the incoming signal has the "Remote alarm indication" bit set to binary ONE ("1") for z consecutive double frame periods, where z = 2 .. 5 and is not provisionable

40 ƒ The RDI defect is cleared when the incoming signal has the "Remote alarm indication" bit set to binary ZERO ("0") for z consecutive double frame periods The “Remote alarm indication” bit is the "A bit" in the 2048 kbit/s frame defined in 2.3.2/G.704. TDM Failures The following line failure definitions are specified in RFC3895, based on T.231, T.403 and G.775. LOS Failure An LOS failure is declared when an LOS defect persists for 2.5 (for T1) or 0 (for E1) +/- 0.5 seconds. The LOS failure is cleared when the LOS defect is absent for 10 +/- 0.5 seconds (see 4.3.1.1.1/ANSI T1.231-2003). AIS Failure An AIS Failure is present when an AIS defect is detected at the input for 2.5 +/- 0.5 seconds and the AIS defect still exists. The AIS failure is cleared when there have been no LOS, AIS or OOF defects for 10 seconds. LOF Failure A Loss of Frame Failure is present when an OOF defect is detected at the input for 2.5 +/- 0.5 seconds. The LOF failure is cleared when OOF defects are absent for 10 seconds. RAI Failure Remote Alarm Indication is also known as a Yellow Alarm, a Far End Alarm and a Distant Alarm. When detected, it indicates that a Red Alarm is present at the opposite link. For T1 D4 links, the RAI failure is declared when an RDI defect is present for at least 335 ms and is cleared when bit 6 of at least one channel is not set to zero for a period of T, where T is typically less than one second and always less than 5 seconds. This rule is adopted for all other T1/E1 modes as follows: the RAI failure is present when an RDI defect is detected at the input for 0.5 +/- 0.1 seconds. The RAI failure is cleared when there have been no RDI defects for 0.5+/-0.1 seconds. For ESF links, the Yellow Alarm failure is declared if the Yellow Alarm signal pattern occurs in at least seven out of ten contiguous 16-bit pattern intervals and is cleared if the Yellow Alarm signal pattern does not occur in ten contiguous 16-bit signal pattern intervals. For E1 links, the Far End Alarm failure is declared when bit 3 of time slot zero is received set to one on two consecutive occasions. The Far End Alarm failure is cleared when bit 3 of time slot zero is received set to zero. Multi-Frame Failures For E1, multi-frame failures are detected when operating with CAS. Note that while ITU-T standards define the faults listed below as failures only, this document follows standard defect/failure terminology. This allows introduciton of integration/deintegration logic without changing the default behavior of default actions (Multiframe Remote Alarm Indication, etc.). These failures are reported in the appropriate dsx1 MIB. Loss Of Multi-frame Failure The Loss Of Multi-frame (LOM) defect is declared when two consecutive multi-frame alignment signals (bits 4 through 7 of TS16 of frame 0) have been received with an error. It is cleared when the first correct multi-frame alignment signal is received. The failure is also declared when CRC is enabled and the framer has lost CRC alignment.

41 Immediately upon detection of the LOM defect, the system should send the MRAI bit in the outgoing (to the TDM) direction to indicate that it has lost multi-frame synchronization. The MRAI bit is cleared immediately after the LOM defect is cleared. The Loss Of Multi-Frame (LOM) failure is present when a LOM defect passes the stabilization filter of 0 seconds. The LOM failure is cleared when there have been no LOM defects for 10 seconds. This failure is reported in the dsx1 MIB as object dsx1LineStatus bit dsx1XmtFarEndLOMF. Far End Loss of Multi-frame Failure The Far End Loss of Multi-frame (RLOM) defect is declared when bit 2 of TS16 of frame 0 is received set to one on two consecutive occasions. It is cleared when bit 2 of TS16 of frame 0 is received set to zero. The Far End Loss Of Multi-Frame (RLOM) failure is present when an RLOM defect passes the stabilization filter of 0.5 +/- 0.1 seconds. The RLOM failure is cleared when there have been no RLOM defects for 0.5 +/- 0.1 seconds. This failure is reported in the dsx1 MIB as object dsx1LineStatus bit dsx1RcvFarEndLOMF. TS16 Alarm Indication Signal Failure (Currently Not Supported) The TS16 Alarm Indication Signal defect (AIS-TS16) is declared when time slot 16 is received as “all ones” for all frames of two consecutive multi-frames (see G.732 Section 4.2.6). This condition only applies to E1 operating in CAS (TS16) multi-frame framing. The AIS-TS16 failure is present when an AIS-TS16 defect passes the stabilization filter of 0.5 +/- 0.1 seconds. The AIS-TS16 failure is cleared when there have been no AIS-TS16 defects for 0.5 +/- 0.1 seconds. The failure is reported in the dsx1 MIB as object dsx1LineStatus bit dsx1T16AIS. No other actions are taken as a result of this event.

42 Failure Integration/Deintegration Time Table 5 specifies integration/deintegration time in seconds for failure declaration and clearance. Table 5: Failure Integration/deintegration Times (Sec) Defect Failures Integration Time (Sec) Deintegration Time (Sec) Loss of Signal (LOS) LOS (red) 2.5 10 Out of Frame (OOF) LOF (red) 2.5 10 Remote Alarm Indication (RAI) RAI (yellow) 0.5 0.5 Alarm Indication Signal (AIS) AIS (blue) 2.5 10 Loss of Multi-frame (LOM) LOMF (red) 0.0 10 Remote Alarm Indication (MRAI) RLOMF (yellow) 0.5 0.5 TS 16 Alarm Indication Signal (AIS) AIS (blue) 2.5 10 PDH Fault Correlation According to Bellcore/ITU-T requirements, any single failure (or root cause of incoming signal problems) must result in a single alarm output message only. Non-traffic-related failures may be exceptions to the "single failure/single message" criteria. Fault correlation logic is a software filter that filters out all "non-root-causing problem" alarms and relies on the fact that most alarms are related to each other and are organized hierarchicaly. For the purpose of alarms reporting, traffic-related failures can be divided into Near-End (i.e. LOS, LOF, AIS, etc.) and Far-End failures (i.e. RAI, RLOMF). In general, the following rules need be applied: ƒ Declaration of a failure will immediately clear any existing failure from a lower level. It should also disable further declaration of any lower-level failure ƒ Clearing of a failure will allow declaration of lower-level failures, if conditions warrant such declaration Table 6 defines the hierarchy of Near-End failures, while Table 7 defines the hierarchy of Far-End failuresTable 8 defines the relations and hierarchy of both Near-End and Far-End failures. To avoid reporting of multiple traps for a single event (as a result of numerous "correlation" actions), simple stabilization logic can be implemented (for example, a trap sending routine can be scheduled to accumulate alarms for periods of 100 milliseconds). This will avoid a typical scenario of a single LOS clearance resulting in declaration and clearing of the LOF trap (inhibited by LOS). Table 6: PDH Near-End Failure Hierarchy Failure Fault Correlation Action LOS “Declared” state will clear and inhibit declaration of all failures listed below. “Cleared” state will enable declaration and declare all relevant failures listed below. AIS “Declared” state will clear and inhibit declaration of all failures listed below. “Cleared” state will enable declaration and declare all relevant failures listed below. LOF “Declared” state will clear and inhibit declaration of all failures listed below. “Cleared” state will enable declaration and declare all relevant failures listed below.

43 Failure Fault Correlation Action AIS-TS16 “Declared” state will clear and inhibit declaration of all failures listed below. “Cleared” state will enable declaration and declare all relevant failures listed below. LOM None Table 7: PDH Far-End Failure Hierarchy Failure Fault Correlation Action RAI “Declared” state will clear and inhibit declaration of all failures listed below. “Cleared” state will enable declaration and declare all relevant failures listed below. RLOM None Table 8: Relations between PDH Near-End and Far-End Failures Near-End Failure Far-End Failure Fault Correlation Relation LOF RAI All Near-End failures including LOF and above will be assigned a higher priority than that of RAI. LOM RLOM All Near-End failures including LOM and above will be assigned a higher priority than that of RLOM. Status Indications This section describes interface line and CES status reporting. TDM Status Reporting The status of the TDM interfaces is reported via the DS1 MIB line status object. The dsx1LineStatus object reports the status of the line. Changes in line status result in SNMP traps. This variable indicates the line status of the interface. It contains loopback, failure, received alarm and transmitted alarm information. The dsx1LineStatus is a bit map represented as a sum. It can therefore simultaneously represent multiple failures (alarms) and a LoopbackState. dsx1NoAlarm must be set if and only if no other flag is set. If the dsx1loopbackState bit is set, the loopback in effect can be determined from the dsx1loopbackConfig object. The various bit positions are presented in Table 9. Table 9: Status Bit Settings Bit Setting Item Description 1 dsx1NoAlarm No alarm present 2 dsx1RcvFarEndLOF Far end LOF (a.k.a., Yellow Alarm) 4 dsx1XmtFarEndLOF Near end sending LOF Indication 8 dsx1RcvAIS Far end sending AIS 16 dsx1XmtAIS Near end sending AIS 32 dsx1LossOfFrame Near end LOF (a.k.a., Red Alarm) 64 dsx1LossOfSignal Near end Loss Of Signal 128 dsx1LoopbackState Near end is looped 256 dsx1T16AIS E1 TS16 AIS (currently not supported)

44 Bit Setting Item Description 512 dsx1RcvFarEndLOMF Far End Sending TS16 LOMF 1024 dsx1XmtFarEndLOMF Near End Sending TS16 LOMF 2048 dsx1RcvTestCode Near End detects a test code 4096 dsx1OtherFailure any line status not defined here 8192 dsx1UnavailSigState Near End in Unavailable Signal State The following events are not supported: ƒ dsx1NetEquipOOS ƒ dsx1RcvPayloadAIS ƒ dsx1Ds2PerfThreshold TDM Performance Monitoring Performance parameters are raw counts derived by the processing of performance primitives within 1- second time intervals. The following are examples of counters: ƒ Errored Seconds (ESs) - count of seconds containing one or more anomalies and/or defects (for lines and paths) ƒ Severely Errored Seconds (SESs) - count of seconds containing more than a particular quantity of anomalies and/or defects (for lines and paths) Generally, PM parameters are normally accumulated at quarter-hourly intervals (i.e., every 15 minutes) and are maintained in designated storage registers. There are 96 storage registers termed: ƒ Current 15-minute ƒ 96 previous 15-minute storage registers At the end of every accumulation interval, the current value of the performance parameter register is saved in its corresponding “previous period” register, and the current register is reset to zero. If the time of day setting in the NE is changed, the collection of parameter counts in each of the current 15-minute interval registers continues uninterrupted, and the time associated with the current 15-minute register is changed to the new time. If this change of time lengthens or shortens the current 15-minute or current day register by more than 10 seconds, the invalid flag is set. All counts saved in the previous and recent 15-minute or daily registers are not affected by the changing of the time of day. Previous (15-minute or day) registers, together with the corresponding recent history registers, if any, form a data structure/buffer. That is, when a new value is stored at the most recent position in the storage structure, every existing value is shifted down to the next most recent position, and the least recent (oldest) value in the structure is discarded. Each entity has an invalid data flag for each current and stored interval, both for 15-minute and daily intervals for each direction of transmission. A flag is set to indicate that the data stored in the associated group of registers is incomplete or invalid (for that interval). When any register capacity is exceeded, the register should not roll over but should be pegged at the maximum value and reinitialized after the data is saved in the appropriate storage register, or upon receipt of an explicit instruction from the OS or operations staff.

45 Figure 30: TDM Performance Monitoring CES Status Reporting The IWF (circuit emulation Interworking Function) detects several conditions based on arriving pseudowire packet flows. These indications are reported in the pseudowire TDM MIB as PwTDMCurrentIndications. They may lead to defects, may be counted in statistic counters and may lead to alarms. The only currently defined CES defect failure is LOPS (Loss Of Packet Synchronization) state. When in LOPS state, the pseudowire’s state is considered to be “down”. When it acquires packet synchronization, the pseudowire’s state is considered to be “up”. Table 10 below describes the indications (specified in the pseudowire MIB) detected by the IWF for each pseudowire based on the incoming packet flow. Table 10: Incoming Packet Flow-based Indications Indication Description strayPacket Stray packets may be detected by the PSN and multiplexing layers. Stray packets must be discarded by the IWF and their detection must not affect packet loss detection mechanisms. malformedPacket Malformed packets are detected by a mismatch between the expected packet size (taking the value of the L bit into account) and the actual packet size inferred from the PSN and multiplexing layers. Malformed in-order packets MUST be discarded by the IWF and replacement data must be generated as for lost packets. excessivePktLossRate Excessive packet loss rate is detected by computing the average packet loss rate over the value of pwVcTDMAvePktLossTimeWindow and comparing it with a preconfigured threshold. bufferOverrun Buffer overrun is detected when the jitter buffer cannot accommodate newly arrived packets. bufferUnderrun Buffer underrun is detected when no packets are present in the jitter buffer.

46 Indication Description remotePktLoss Remote packet loss is indicated by reception of packets with their R bit set. pktMisOrder Packet misorder is detected by examining the sequence number provided by the control word. A packet is considered misordered when: ƒ The sequence number of the new packet is less than the highest sequence number of a packet successfully stored in the jitter buffer ƒ The sequence number of the new packet is not the next consecutive number packetLoss Packet loss is detected if a packet was not received before it needed to be played out. tdmFault If L bit in the control word is set, TDM fault, indicates that TDM data carried in the payload is invalid due to an attachment circuit fault. When the L bit is set, the payload may be omitted in order to conserve bandwidth. In any event, replacement data is generated when the L bit is set. LOPS The loss of packet synchronization (LOPS) state is entered when either: ƒ A preconfigured number of consecutive packets are missing as determined by the play out of these packets or ƒ the excessive packet loss threshold is reached The LOPS state is terminated when: ƒ A preconfigured number of consecutive packets are available for play out with no error and ƒ the excessive packet loss rate falls below the excessive packet threshold value for a complete window time (AvePktLossTimeWindow) Error Handling This section describes how defects and failures are handled for structure-agnostic and structure-aware transport on the TDM-bound and PSN-bound (packet) interfaces. Each CES gateway contains a defined mapping between TDM circuits and pseudowires (see Figure 31). Events detected in the TSP RX affect the IWF TX and perhaps the TSP TX. Similarly, events detected in the IWF RX affect what is transmitted by the TSP to the TDM circuits. The data and signaling transmitted during error conditions is governed by a set of configuration settings and policies. The configuration options for both the TSP and IWF are described in detail in CES Configuration Parameters on page 53. Figure 31: CES Gateway

47 Until a pseudowire is started, the IdlePattern pattern is sent by the TSP on the TDM circuits. Once a pseudowire is operational, TDM data is regenerated based on the incoming pseudowire packet flow and is transmitted on the associated TDM circuit. Error handling is based on standard specifications of the Circuit Emulation IETF CESOP/SATOP drafts, the Docsis BSoD and the MEF-8 PDH Implementation Agreement. Structure-agnostic Mode Table 11 below describes the events and actions taken when operating in structure-agnostic mode. Table 11: Structure-agnostic Event Handling Event Actions TSP RX: LOS defect or TSP RX: AIS defect (optional) IWF TX: Sends the packet with the L bit set to 1 The packet payload may be omitted according to PaySupPolicy in order to conserve bandwidth If there are no defects, the L bit must be cleared, and the proper payload sent TSP TX: “All ones” pattern will be inserted into received E1/T1 payload on LOS detection TSP IWF

48 Event Actions IWF RX: Packet received with L flag set TSP TX: If payload is suppressed, plays out AIS pattern (“all ones” for T1/E1) with appropriate amount of data on TDM circuit If payload is not suppressed, behaves according to LflagPayloadPolicy. The default is to ignore the payload and to play out the AIS pattern. Optionally, the payload is maintained and no further alarm processing is performed. IWF RX: Packet received with R flag set Report RemotePktLoss to PW TDM MIB IWF RX: Missing packet detected TSP TX: Plays out an appropriate amount of data on TDM circuit according to the PktReplacePolicy IWF RX: PW enters LOPS state TSP TX: Plays out AIS pattern (“all ones” for T1/E1) with an appropriate amount of data on TDM circuit IWF TX: Sends packets for this pseudowire with the R bit set IWF RX: PW exits LOPS state TSP TX: Plays out data from jitter buffer IWF TX: Sends packets for this pseudowire with the R bit cleared Figure 32 below illustrates a sample LOS defect case. Figure 32: Loss of Signal Trace Example Description of events: LOS L bit set According to LFLAG Policy (none, ldle, AIS)

49 1. An LOS defect is detected at the TSP RX, causing a packet with the L bit set to be generated. This is received by the IWF RX, which in turn, causes the TSP TX to generate a packet according to the L flag policy. 2. At the IWF TX, it is possible to have both the L and R bits set simultaneously. This represents no conflicts. 3. At the TSP TX, the AIS pattern is played out. 4. The R flag does not affect the data to be played out. Structure-aware Mode Table 12 describes the events and actions taken when operating in the structure-aware mode. Table 12: Structure-aware Event Handling Event Actions TSP RX: LOS defect or TSP RX: AIS defect or TSP RX: OOF defect IWF TX: ƒ Sends the packet with the L bit set to 1 (if there are no defects, the L bit must be cleared and the proper payload sent) ƒ The packet payload may be omitted according to PaySupPolicy, in order to conserve bandwidth TSP TX: ƒ Sends RAI, if configured for E1 operation ƒ “All ones” pattern will be inserted into the E1/T1 payload received on LOS detection. No insertions are required on OOF or AIS defects T1 only: TSP RX: LOS failure or TSP RX: AIS failure or TSP RX: OOF failure TSP TX: ƒ Sends RAI on attached T1 interface, if configured for T1 operation ƒ RAI is sent for the duration of the failure, and for at least 1 second (see t1.231.02-2003 section 4.5.1). In T1 D4 operation, RAI for T1 should be sent by setting the S bit of frame 12 of the multi-frame to 1 TSP RX: RAI defect IWF TX: ƒ Sends packets with the M bits set to b10 (bit 6, bit 7) and the L bit set to 0 TSP RX: LOMF defect (E1 only) TSP TX: ƒ The distant multi-frame alarm is transmitted to the far end by setting the bit in position 2 of time slot 16 in frame 0 to 1. This is often referred to as the Y bit (E1 in CAS framing only)

50 Event Actions IWF RX: Packet Received with L Flag set TSP TX: ƒ If packet arrived with no payload or if LbitPayloadPolicy is set to ignore payload (default), uses FrameLbitPolicy to determine the payload and signaling performed on the payload and entire trunk ƒ Default is to play out the idle pattern instead of the payload ƒ Optionally, an “all ones” pattern is played out on the entire T1/E1 trunk ƒ Optionally, the idle pattern is played out and idle signaling is performed for the relevant time slots IWF RX: Packet Received with R Flag set TSP TX: ƒ Plays out data data amd signaling on TDM circuit according to the FramedRflagPolicy ƒ Default is to do nothing different and only report this to management. If the RflagPolicy is set to RAI, sends out RAI on the associated T1/E1 interface (independent of TDM equipment configuration, and even if other pseudowires associated with this TDM interface have a different configuration) ƒ If the FramedRflagPolicy is set to “channel idle”, plays out the IdlePattern byte and signal “channel idle” for the specific DS0s on trunk IWF RX: Packet Received with M Flags set to 10 and L bit is 0 TSP TX: ƒ Plays out data on TDM circuit according to the FramedRDPolicy. Default is to do nothing different and to report this to management ƒ If RDPolicy is set to RAI, sends out RAI on the associated T1/E1 interface (independent of TDM equipment configuration, and even if other pseudowires associated with this TDM interface have a different configuration) ƒ If the FramedRDflagPolicy is set to “channel idle”, plays out the IdlePattern byte and signal “channel idle” for the specific DS0s on trunk IWF RX: Missing packet detected TSP TX: ƒ Plays out an appropriate amount of data on TDM circuit according to the PktReplacePolicy. Default is to generate Idle for relevant time slots. If pktReplacePolicy is set to AIS, plays out the idlepattern on these slots

51 Event Actions IWF RX: PW enters LOPS state TSP TX: Uses FrameLOPSPolicy to determine the payload and signaling performed on the payload and on the entire trunk Default is to play out the idle pattern instead of the payload Optionally, an “all ones” pattern is played out on the entire T1/E1 trunk Optionally, the idle pattern is played out and idle signaling is performed for the relevant time slots IWF TX: Generates packets with the R bit set IWF RX: PW exits LOPS state TSP TX: Plays out data from jitter buffer IWF TX: Generates packets with the R bit cleared The following figures present examples of transferring events across the network. Figure 33 shows the transfer of the RAI failure across the network, while Figure 34 demonstrates a case of loss of packets. Figure 33: RAI Transfer Figure 34: Loss of Packets At the IWF TX, it is possible to have the R flag set to 01, together with either the L flag or the M flag. If for some reason, the TSP RX detects L flag setting defects simultaneously with M flag setting defects, priority is given to the L flag defects, the L flag is set to 1, and M is sent as 00. RAI M bit set According to RD Policy (none, ldle, RAI) According to R Flag Policy (none, ldle, RAI) According to Packet Replace Policy (none, ldle, AIS)

52 At the TSP TX, several conflicting framed policy instructions may occur. For example, a packet received with the L bit set while in LOPS state, packets can be received with the L and R bits set, etc. Operation hierarchy is determined in the following order: 1. FramedLOPSpolicy 2. FramedLbitPolicy 3. FramedRbitPolicy 4. FramedRDbitPolicy This hierarchy is set to make sure that operations on the TSP TX will be consistent and will not fluctuate. In particular, while in the LOPS state, occasional receipt of a packet with the L bit or the R bit set should not change the indication on the wire. Conflicts between AIS and RAI IWF indications and RAI detected by the framer due to an incoming defect on the T1/E1 are determined according to the standard TDM (framer) behavior, as per the following priority: 1. AIS 2. RAI 3. Idle pattern This hierarchy is also applicable when two or more sessions introduce conflicting policies on the outgoing T1/E1 circuit. In particular, configuration of AIS on the entire T1/E1 should not be set as a policy when more than one CESoPSN pseudowire is aggregated to the same trunk. Application Signaling When Out of Stream CAS signaling is used with structure-aware emulation, care must be taken in handling application signaling during error conditions as shown below: ƒ Application signaling must be frozen to the peer IWF once the local TDM interface indicates any of the following defects: ƒ LOS ƒ OOF ƒ AIS The idle signaling pattern should be sent to the peer IWF when any of the following failures persist: ƒ LOS ƒ LOF ƒ AIS ƒ LOMF The idle signaling pattern should also be sent locally to the TSP TX when the IWF RX detects that packets for a particular pseudowire are received with the L, R or M bits set and the corresponding policy is set to “channel idle”. The idle signaling pattern should also be sent locally to the TSP TX when the IWF RX has entered the LOPS state for a particular pseudowire and the LOPS policy is set to “channel idle”. The idle signaling pattern is defined in the parameter SigIdle.

53 As soon as new packets are received and the defect(s) that caused the idle pattern to be sent is (are) cleared: ƒ Signaling sent on the TSP TX should be updated ƒ Signaling packets should be sent three times to update the peer’s TSP TX Errored Second Counters For each TDM interface and for each pseudowire, the TSP must detect and count: ƒ Errored seconds ƒ Severely errored seconds ƒ Unavailable seconds The IWF must detect an error defect whenever filler data is played out of the jitter buffer. For structure- agnostic operation, a filler packet is considered a single error defect. The IWF must count: ƒ An errored second as any second in which one or more error defects are detected ƒ A severely errored second as a second in which the number of error defects is equal to or greater than the configurable severely errored second threshold ƒ An unavailable second when ten consecutive seconds qualify as severely errored seconds. This condition will last until ten consecutive seconds occur that do not qualify as severely errored seconds CES Configuration Parameters See TDM Error Reporting Command on page 158. References Supported standards include: ƒ ANSI: T1.231, T1.403 ƒ ITU: G.706, G.732 (E1) G.733 (T1), G.775 Unsupported standards: ƒ ETSI 300 233 - this standard defines how ISDN primary rate works

55 2 Management Options MG-IP units feature multiple management options that support unit use in a range of applications. In a standalone application, the TDM over packet functionality of the MG-IP is the primary application. The processor on the MG-IP is the only processor, so there is no other processor to manage the MG-IP. Management will need to be performed from an external processor such as a PC or a craft terminal. See Figure 35. Figure 35: Standalone Application The Command Line Interface (CLI) The Command Line Interface (CLI) provides access to all of the user modifiable parameters of the module. There are commands for displaying configuration and status information as well as performance statistics. The CLI can be run from a serial terminal or a PC via a serial interface or via a network connection by using Telnet application. See Appendix A for CLI command descriptions. CLI Script Files Users may create textual configuration files comprising text lists representing CLI commands. CLI script files may prove useful for customers using the product in standalone mode under the following scenarios: ƒ Statically - as input to the CLI command ("dlf" – download file) ƒ Dynamically - as input to a DHCP option for customers using a DHCP client to configure their IP addresses Script File Format The script file contains CLI commands, with each command listed on an individual line separated by \r\n (cr/lf) characters. Blank lines and spaces are allowed. ƒ The ";" character represents the start of a comment, which is terminated by an EOL (end-of- line) character ƒ The file must start with a username and password, as follows: ƒ admin ƒ admin (the "admin" string must not be followed by spaces, or it will be treated as an invalid login/password)

56 ƒ \a\dlf cfg - (download CLI script). This CLI is forbidden in the script. It is treated as an error command (failure is returned). ƒ \a\dlf img (download software image).This CLI command with an "img" parameter is relevant only in “safe” download mode (also referred to as UDL mode), the only mode in which a software image can be downloaded. In non-UDL mode, this parameter is treated as invalid. In “safe” download (UDL) mode, when the command appears in a CLI script, a download request is sent to the TFTP server and the remaining commands in the script are ignored. However, if a software image with this filename has already been downloaded, no download request is sent and the script continues to run. Image files are customer specific and are included in a dedicated ZIP file provided by Olencom. This ZIP file’s name must not be changed. ƒ Progress messages following success/failure: unsolicited messages are sent to all CLI users (connected through UART/Telnet) ƒ If a command succeeds: Command completed. Line: , Command: ƒ If the command fails: CLI script file processing failed.. Line: , Command: Description: The script stops and the system restarts. An identical failure message is sent to the Syslog server. Guidelines to Writing CLI Script File CLI scripts used in DHCP mode have a very specific format and comply with specific guidelines, as follows: ƒ Boot with the default configuration, which has NO associated sessions The CLI script should be composed in the following format: ƒ User name and password ƒ dlf command for image file (if required) ƒ Disable TDM ports ƒ Configure TDM ports and, if required, TDM hardware profiles ƒ Enable TDM ports ƒ Add all sessions ƒ Configure all sessions ƒ Enable all sessions The order of the commands bears significance. Olencom recommends it not be changed.

57 If you use the \c\rr and \c\rp commands in the CLI script file, the configuration contained in the script file will be saved to the database statically. A Sample Script File admin admin \a\dlf 169.254.1.1 img MG-IP-1-R03.04.00_D001.zip \c\top\spod all \c\top\cet struct p1 \c\t1\p1\sfp d4 \c\top\spoe all \c\top\adds s01 s01 \c\top\ccpl s01 8 5 \c\top\scfg\ccip s01 169.254.1.119 \c\top\sse all TLV Files This section describes TLV11 rules of construction. TLV11 is an object used to set arbitrary SNMP objects it contains within an SNMP Varbind. TLV is a binary file format. A TLV file consists of type, length and value elements. They appear as a stream of octets (with no delimiters between them). ƒ Length is a single octet containing the length of the value field in octets (not including type and length fields) ƒ The type is a single octet ƒ Value ranges from one to 255 octets. The value is treated according to its type The value may contain additional TLV elements. Several containment levels are supported. An element whose value contains additional elements is referred to as a “container” in this section and the elements contained in its value are referred to as “nested elements”. An element whose value does not contain additional TLV elements is referred to as a “single element”. The nested element type depends on the container TLV type. For example, a nested TLV of type 1 contained within a TLV of type 2 is treated differently than a TLV of type 1 contained within a TLV of type 3. In the first case, the type of the nested TLV is treated as 2.1 and in the second case, it is treated as 3.1. The TLV file ends with type 0xFF, without length and value elements. TLV Structure TLV11 is a container of the following structure (its specification is listed in Table 13). ƒ TLV11 ƒ TLV48 (Varbind TLV) ƒ TLV6 (OID TLV)

58 ƒ Value TLV Table 13: TLV Structure Specification Type Container Length (bytes) Value 11 Yes Variable SNMP MIB object 11.48 Yes Variable Varbind 11.48.2 No 4 Integer value (signed) 11.48.4 No Variable Octets 11.48.6 No Variable OID (e.g. 1.3.6) 11.48.64 No 4 IP address 11.48.65 No 4 Counter (unsigned integer) 11.48.70 No 8 64 Counter (unsigned integer) Rules of Construction Maximum Length Constraint The maximum length of the VarBind TLV value is limited to 249. 249 = 255-6. 255 is the maximal length of the TLV11 value and 6 is the sum of the VarBind TLV type and length fields (2 bytes), OID type and length fields (2 bytes) and value TLV type and length (2 bytes). SNMP allows values longer than 255 bytes (for example, strings). However, they cannot be represented in TLV format due to length limitation. TLV6 (OID) TLV6 may be used in the two following cases: ƒ The OID representing the relevant MIB variable + index (the 1st part of the Varbind pair) ƒ A value (the 2nd part of the Varbind pair) Encoding Rules TLV6 (OID) encoding rules are not defined in standards. However, there a de-facto standard is in common use, as follows: ƒ Every OID starts with 1.3. In order to conserve space, this prefix is presented in a single byte instead of two. The prefix is presented as X*40+Y, where X=1, Y=3 and the result is 43 (=0x2B). Similarly, the TLV of OID=1.3.6.1 will look like the following: 6 3 43 6 1 Type Length Value

59 ƒ When a sub-identifier of OID is greater than or equal to 128 (for example 1.3.6…. 24222 – the Olencom assigned number), it is divided into numerous octets as follows: ƒ Only seven bits in each octet are used to represent the value ƒ The most significant bit (MSB) of the last octet is 0 ƒ The most significant bit of other octets is 1 ƒ Example1: sub-identifier 128 = 0x80 = 10000000 ƒ Last (least significant) 7 bits form the last octet with MSB = 0: 00000000 ƒ The first octet is 10000001 – MSB = 1 and LSB is the remaining bit from the original sub-identifier ƒ Result: 10000001 00000000 = 0x8100. This sub-identifier takes up 2 bytes in the TLV file ƒ Example2: sub-identifier 24222 = 0x5E9E = 101 1110 1001 1110 ƒ Last 7 bits from the last octet. The MSB of the octet is 0: 00011110 ƒ Next 7 bits from the next octet with 1 in MSB: 10111101 ƒ The remaining bit forms the first octet. The MSB of the octet is 1, the rest of the bits are zeros: 10000001. ƒ Result: 10000001 10111101 00011110 = 0x81BD1E. This sub-identifier takes up 3 bytes in the TLV file ƒ Example3: for additional clarification, sub-identifier 127 = 01111111 ƒ This sub-identifier is not encoded, as its MSB is 0 ƒ Result: 01111111 = 0x7F. This sub-identifier takes up 1 byte in the TLV file ƒ When an octet with 1 as its MSB is encountered while parsing OID in a TLV file, it means that this is a first octet of an encoded sub-identifier. This encoded sub-identifier ends with an octet that has 0 in its MSB. TLV Examples The following TLV contains the Varbind of dsx1LineCoding (OID = 1.3.6.1.2.1.10.18.6.1.6), index 1 and value AMI = 5 (integer type). 11 21 48 19 6 11 43 6 1 2 1 10 18 6 1 6 1 2 4 0 0 0 5 type length type length type length type length TLV 11 Varbind OID Integer TLV The following TLV contains the Varbind of OlencomPwAdminStatus (OID = 1.3.6.1.4.1.24222.3.3.1.2.1.37), index 1 and value UP = 1 (integer type). The sub-identifier 24222 is encoded to 3 bytes (129, 189, 30 = 0x81BD1E).

60 11 25 48 23 6 15 43 6 1 4 1 129 189 30 3 3 1 2 1 37 1 2 4 0 0 0 1 T L T L T L T L TLV11 Varbind OID Integer SNMP Please refer to SNMP Support on page 131. Automatic Management and Provisioning Safe Download (UDL) Mode The MG-IP supports a “safe” remote image download mode (this mode is also referred to as UDL mode), in which a new image is copied to the MG-IP (for example, when a remote software upgrade is required). The MG-IP will switch to the new copied image only if the download process was completed successfully. Note that the MG-IP can be produced either with or without this mode. Availability of this mode is set during MG-IP production and may not be configured online. File Download via TFTP Client This mechanism allows firmware/configuration data to be downloaded to the target using a new CLI. This mechanism is applicable mainly to customers using the module in standalone mode, or when using the module on an evaluation platform. A CLI command has been developed for file downloads. This command can be used to download: ƒ Configuration/CLI script files ƒ Image files. This is only applicable when the “safe dowload” (UDL) option is used (note that all standalone-purpose modules are produced and released with the UDL option) The CLI command is \admin\dlf ƒ Mandatory parameters: ƒ TFTP server IP address ƒ Downloaded file type – image/configuration file ƒ File path – a string no longer than 70 characters. The file path includes the file name, which must have a TXT extension for CLI script files. ƒ Optional parameter: ƒ Force – indicates whether the given filename should be compared to the saved filename of the image, and can determine whether a download is performed in any case or only if they differ (this only applicable to software image file)

61 Dynamic Downloading/Processing of CLI Script-based Configuration In DHCP mode, the system has the option to acquire a TFTP server IP address and configuration file path using DHCP options. After setting the WAN IP address, if the TFTP option exists in the DHCP response, a TFTP process is initiated to download the configuration file. If the download fails, the system will restart itself. In case of successful file download, the CLI script configuration file received is processed and used to configure the system. A success/fail message is sent to the Syslog server (if it exists in the DHCP option) following the configuration file process. Dynamic Firmware Download through a TFTP/DHCP Client This process is identical to dynamically downloading CLI-script based configuration files. If the CLI script configuration file includes the "dlf img " command, a download request is sent to the TFTP server and the remaining commands in the script are ignored. However, if a software image with this filename already exists on the target, no download request is sent and the script continues to run. Note that image upgrade using a TFTP client is supported in “safe download” (UDL) mode only. System behavior following the image download is based on UDL implementation. Image files are customer specific and are included in a dedicated ZIP file provided by Olencom. This ZIP file’s name must not be changed. Syslog Error Reporting The device supports Syslog error reporting (see Table 14). This is currently limited to the startup session, when dynamic provisioning is used. See Syslog CLI commands in Appendix A for further information on Syslog configuration.

62 Table 14: Syslog Messages Scenario Facility Severity Mnemonic Text Init related messages Success messages Init successful Init Info InitSuccess Init completed successfully Failure messages Init failed - unsupported file type Init Critical FailedFile Failed: Unsupported file type Init failed - Problem with CLI script processing Init Critical CLIscriptFail Failed: CLI script file processing failed. Line: Command: , Description: Init failed - Missing TFTP IP option in DHCP offer Init Critical DHCPMissTFTPOpt Failed: Missing TFTP server IP in DHCP offer TFTP server returned an undefined error Init Critical TFTPUndeErr Failed: TFTP server returned undefined error TFTP server file not found Init Critical TFTPFileNotFound Failed: TFTP server returned error - file not found Failed to access TFTP server Init Critical TFTPAccessViol Failed: TFTP server returned error - access violation Illegal operation on TFTP server Init Critical TFTPIllegalOper Failed: TFTP server returned error - illegal operation Unknown TFTP transport ID Init Critical TFTPUnknownID Failed: TFTP server returned error - unknown transfer ID Invalid TFTP user Init Critical TFTPInvalidUser Failed: TFTP server returned error - no such user Illegal TFTP option Init Critical TFTPIllegalOpt Failed: TFTP server returned error - illegal option General TFTP failures without specific message Init Critical TFTPFailure Failed: TFTP error Received IP is on subnet of other interface(s) Init Critical IPOnSameSubnet Failed: Received IP address is on subnet of other interface(s). TFTP connection timeout expired during connection Init Critical TFTPConTimeoutExp Failed: TFTP server couldn't be reached, connection timeout expired Size of file to be downloaded is too big Init Critical DnldFileTooBig Failed: Size of file to be downloaded is too big

63 Scenario Facility Severity Mnemonic Text Configuration download related messages Failure messages Unsupported file type CfgDnld Warning FailedFile Failed: Unsupported file type Problem with CLI script processing CfgDnld Warning CLIscriptFail Failed: CLI script file processing failed. Line: Command: , Description: Missing TFTP IP option in DHCP offer CfgDnld Warning DHCPMissTFTPOpt Failed: Missing TFTP server IP in DHCP offer TFTP server returned an undefined error CfgDnld Warning TFTPUndeErr Failed: TFTP server returned undefined error TFTP server file not found CfgDnld Warning TFTPFileNotFound Failed: TFTP server returned error - file not found Failed to access TFTP server CfgDnld Warning TFTPAccessViol Failed: TFTP server returned error - access violation Illegal operation on TFTP server CfgDnld Warning TFTPIllegalOper Failed: TFTP server returned error - illegal operation Unknown TFTP transport ID CfgDnld Warning TFTPUnknownID Failed: TFTP server returned error - unknown transfer ID Invalid TFTP user CfgDnld Warning TFTPInvalidUser Failed: TFTP server returned error - no such user Illegal TFTP option CfgDnld Warning TFTPIllegalOpt Failed: TFTP server returned error - illegal option General TFTP failures without specific message CfgDnld Warning TFTPFailure Failed: TFTP error Received IP is on subnet of other interface(s) CfgDnld Warning IPOnSameSubnet Failed: Received IP address is on subnet of other interface(s). TFTP connection timeout expired during connection CfgDnld Warning TFTPConTimeoutExp Failed: TFTP server couldn't be reached, connection timeout expired Size of file to be downloaded is too big CfgDnld Warning DnldFileTooBig Failed: Size of file to be downloaded is too big

64 Scenario Facility Severity Mnemonic Text Image download related messages Failure messages Unsupported file type ImgDnld Warning FailedFile Failed: Unsupported file type Problem with CLI script processing ImgDnld Warning CLIscriptFail Failed: CLI script file processing failed. Line: Command: , Description: Missing TFTP IP option in DHCP offer ImgDnld Warning DHCPMissTFTPOpt Failed: Missing TFTP server IP in DHCP offer TFTP server returned an undefined error ImgDnld Warning TFTPUndeErr Failed: TFTP server returned undefined error TFTP server file not found ImgDnld Warning TFTPFileNotFound Failed: TFTP server returned error - file not found Failed to access TFTP server ImgDnld Warning TFTPAccessViol Failed: TFTP server returned error - access violation Illegal operation on TFTP server ImgDnld Warning TFTPIllegalOper Failed: TFTP server returned error - illegal operation Unknown TFTP transport ID ImgDnld Warning TFTPUnknownID Failed: TFTP server returned error - unknown transfer ID Invalid TFTP user ImgDnld Warning TFTPInvalidUser Failed: TFTP server returned error - no such user Illegal TFTP option ImgDnld Warning TFTPIllegalOpt Failed: TFTP server returned error - illegal option General TFTP failures without specific message ImgDnld Warning TFTPFailure Failed: TFTP error Received IP is on subnet of other interface(s) ImgDnld Warning IPOnSameSubnet Failed: Received IP address is on subnet of other interface(s). TFTP connection timeout expired during connection ImgDnld Warning TFTPConTimeoutExp Failed: TFTP server couldn't be reached, connection timeout expired Size of file to be downloaded is too big ImgDnld Warning DnldFileTooBig Failed: Size of file to be downloaded is too big DHCP messages DHCP IP lease expired on interface = the expired address = WAN/LAN Dhcp Critical DhcpIpExpired DHCP IP lease has expired on interface TLV messages Problem with TLV script processing parsing problem or wrong OID. CfgDnld Warning TLVFail Failed: TLV file processing failed. {Problems in parsing.} | {OID: .}

65 3 Configuring The MG-IP via CLI This chapter describes the tasks that need be performed to configure MG-IP units. Each section builds upon the previous section: the console must be configured before operating the CLI interface; the WAN and the T1/E1 circuit must be configured before managing the module; the module management must be understood before using SNMP to gather MIB information and other status. Each section gives an overview of how to configure the module using the CLI interface and demonstrates simple configurations. The section Ошибка! Источник ссылки не найден. on page Ошибка! Закладка не определена. contains an explanation about how traffic moves from the T1/E1 circuit through the system to the WAN, the special configuration of the T1/E1 circuit to reflect structured or unstructured mode, and how the information stream is packetized using headers and then moved out of the system to the Packet Switched Network (PSN). The section Session Management Tasks in Structured Mode on page 118 discusses the concept of a session and Out-of-Stream Signaling (OOS). For maximum use of this chapter, first set up the hardware and all required network connections, and turn the power on. For an introduction to the CLI, refer to the chapter Command Line Interface on page 149. The configuration tasks are described in the following sections: ƒ Configuring the Management PC on page 66 ƒ Managing Users on page 68 ƒ Managing the CONSOLE Interface on page 74 ƒ Managing Basic Functionality on page 75 ƒ Global Configuration Status on page 81 It is possible to set all Ethernet and MAC layer configuration options dynamically using the ac (ApplyChanges) CLI command, without the need to perform Replace & Reload (\c\rr). However, one must make sure that no pesudowire sessions are active when using this command. ƒ Managing the T1/E1 Interface on page 91. ƒ Ошибка! Источник ссылки не найден. on page Ошибка! Закладка не определена.. ƒ Managing SNMP on page 125. The MG-IP-1 and MG-IP-4 feature identical software and board layouts. All CLIs and management options are exactly the same on both units. While this section focuses on the MG-IP-1, it is equally applicable to the MG-IP-4.

66 Configuring the Management PC Connect an RS-232 null modem cable to the unit and to a COM port of the management PC. Open HyperTerminal (found on Programs/Accessories/ Communications menu on Windows 2000 or Windows XP). The opening screen allows the user to define a connection. Select an icon and enter a name for the connection. On the “Connect to” panel in the “Connect using” drop-down selection, pick the COM port you are using.

67 On the COM properties pane, set the following: ƒ 115200 bps ƒ 8 bits ƒ no parity ƒ 1 stop bit ƒ no flow control The Hyper terminal now opens. Press “Enter” to get the CLI login prompt. At the login prompt type “admin”. At the password prompt type “admin”, and you will get the loging prompt.

68 TELNET Using LAN To establish a Telnet connection with the MG-IP, connect to one of the Ethernet ports with a PC. The factory default IP address of a master unit is 169.254.1.100 (the slave is 169.254.1.101) . The default subnet mask is 255.255.255.0. If you need to change the IP address in the module before connecting to them via a LAN, see Managing LAN and WAN Interfaces on page 83. Select Windows Start button, then “Run...” then type “telnet nn.nn.nn.nn”, where the n's are the module lan IP address. The MG-IP’s product prompt will be displayed. Note that if a reset command such as \c\rr is used, the Telnet session will need to be reestablished to reconnect to the CLI. Managing Users MG-IP units allow for creation of additional users beyond the default admin user. Additional users may have full administrator privileges like admin or may be assigned to a user group with limited administrative privileges. The different user groups to which to assign users are as follows: Table 15: User Groups User Group Description Viewer Users assigned to the Viewer user group may only run monitoring commands in the \Config and \Monitor directories, as well as the cp (change password) command in the \Admin\Users directory. Oper Users assigned to the Oper user group may run all commands in the \Monitor and \Config directories, as well as the cp (change password) command in the \Admin\Users directory.

69 Admin Users assigned to the Admin user group may run all commands in any directory. Users can be configured to have access only from the CONSOLE, or also from the LAN interface using Telnet. User Management Tasks The user management commands are executed from the \Admin\Users directory, unless noted otherwise. The following user management tasks are available: Table 16: User Management Action Command Add a user au (see page A-8 in Appendix A) Delete a user du (see page A-17 in Appendix A) Display active users gau (see page A-21 in Appendix A) Display all users gu (see page A-64 in Appendix A) Set a user’s password cp (see page A-12 in Appendix A) Set an inactivity timeout for the user sut (see page A-129 in Appendix A) End a user’s login session. ful (see page A-19 in Appendix A) Log out at any time from any directory Lo

70 Manage User Accounts Example Change directory to the Admin directory from the root: MG-IP-1:\>a\u MG-IP-1:\Admin\Users> Display all users in the system: MG-IP-1:\Admin\Users>gu Username Group Timeout CommApp Current Users: view Viewer -1 All logger Viewer -1 All oper Oper 60 All admin Admin 60 All bdadmin Admin 30 UART Modified Users view Viewer -1 All logger Viewer -1 All oper Oper 60 All admin Admin 30 All bdadmin Admin 60 UART Find out how which users are currently active: MG-IP-1:\Admin\Users>gau Username Comm Id Group Timeout Timeleft Active Users: admin * 11 Admin 30 30 Add several users to the system: MG-IP-1:\Admin\Users>au user1 viewer 10 all The command completed successfully. Use \c\rp to save the modified running_config MG-IP-1:\Admin\Users>au user2 oper -1 all The command completed successfully. Use \c\rp to save the modified running_config MG-IP-1:\Admin\Users>au user3 admin 100 uart The command completed successfully. Use \c\rp to save the modified running_config

71 MG-IP-1:\Admin\Users>au user4 viewer 5 all The command completed successfully. Use \c\rp to save the modified running_config MG-IP-1:\Admin\Users>gu Current Users: view Viewer -1 All logger Viewer -1 All oper Oper 60 All admin Admin 30 All bdadmin Admin 60 UART user1 Viewer 10 All user2 Oper -1 All user3 Admin 100 UART user4 Viewer 5 All Modified Users view Viewer -1 All logger Viewer -1 All oper Oper 60 All admin Admin 30 All bdadmin Admin 60 UART user1 Viewer 10 All user2 Oper -1 All user3 Admin 100 UART user4 Viewer 5 All Set each user’s password MG-IP-1:\Admin\Users>cp user1 Administrator password:admin New Password:xxxx Confirm New Password:xxxx(the typed password is not echoed) Only a user with Admin privileges may change all passwords. One may typically only change one’s own password.

72 Set the inactivity timeout for each new user A value was set on creation of the user. This task is only repeated if the timeout is no longer relevant. Set user1 to a 10 minute timeout. MG-IP-1:\Admin\Users>sut user1 10 The command completed successfully. Use \c\rp to save the modified running_config Set user2 to an unlimited timeout. MG-IP-1:\Admin\Users>sut user2 -1 The command completed successfully. Use \c\rp to save the modified running_config Set user3 to a two minute timeout. MG-IP-1:\Admin\Users>sut user3 2 The command completed successfully. Use \c\rp to save the modified running_config Set user4 to a five minute timeout. MG-IP-1:\Admin\Users>sut user4 5 The command completed successfully. Use \c\rp to save the modified running_config View the changes by issuing a gu command. MG-IP-1:\Admin\Users>gu Current Users: Current Users: view Viewer -1 All logger Viewer -1 All oper Oper 60 All admin Admin 30 All bdadmin Admin 60 UART user1 Viewer 10 All user2 Oper -1 All user3 Admin 2 UART user4 Viewer 5 All Modified Users view Viewer -1 All logger Viewer -1 All

73 oper Oper 60 All admin Admin 30 All bdadmin Admin 60 UART user1 Viewer 10 All user2 Oper -1 All user3 Admin 2 UART user4 Viewer 5 All Log out using the lo command. Then log back in as user1. MG-IP-1:\Admin\Users>lo MG-IP-1 R03.01.01_D001-202 Login: user1 Password: MG-IP-1 R03.01.01_D001-202 MG-IP-1:\> User1 has view only privileges. Traverse the directories and notice that the only available commands are those to display information. This user is not privileged to set any parameters. Log out and log back in as user2. This time the directories will display more functionality available to the operator, but certain functions, such as setting user characteristics, will be restricted. Display active user Change directory to the Admin\Users directory. Type in gau to display the list of active users. MG-IP-1:\Admin\Users>gau Username Comm Id Group Timeout Timeleft Active users user2 * 12 Oper -1 -1 Log out from user2 and log back in as admin. MG-IP-1:\Admin\Users>lo Login: admin Password: MG-IP-1 R03.01.01_D001-202 MG-IP-1:\>

74 Delete a user from the system Change directory to \Admin\Users. Delete user4 from the system. MG-IP-1:\Admin\Users>du user4 The command completed successfully. Use \c\rp to save the modified running_config Verify that user4 is removed from the system with the gu command. MG-IP-1:\Admin\Users>gu Current Users: view Viewer -1 All logger Viewer -1 All oper Oper 60 All admin Admin 30 All bdadmin Admin 60 UART user1 Viewer 10 All user2 Oper -1 All user3 Admin 100 UART Modified Users view Viewer -1 All logger Viewer -1 All oper Oper 60 All admin Admin 30 All bdadmin Admin 60 UART user1 Viewer 10 All user2 Oper -1 All user3 Admin 100 UART Managing the CONSOLE Interface MG-IP units can be exclusively managed using the CONSOLE interface, or configured for access through the LAN interface via Telnet.

75 CONSOLE Management Tasks Perform the following tasks to configure the CONSOLE. The CONSOLE management commands are run from the \Config\CONSOLE directory, unless noted otherwise. Table 17: CONSOLE Management Action Command Configure the CONSOLE interface baud rate scu (see page A-95 in Appendix A) Display CONSOLE interface information gc (see page A-26 in Appendix A) \Config\gcu (see page A-33 in Appendix A) CONSOLE Management Example Change directory to config\console: MG-IP-1:\>config\cons MG-IP-1:\Config\CONSOLE> Get the current console configuration: MG-IP-1:\Config\CONSOLE>gc Running_config Modified Running_config Baud rate............... : 115200 115200 Stop bit.................. : 1 1 Protocol................. : Term Term Mode..................... : Enabled Enabled Reconfigure the baud rate: MG-IP-1:\Config\CONSOLE>scu 57600 The request was updated successfully in modified running_config. The configuration change will be activated after the next Replace&Reload (\c\rr) If you change the baud rate for the module, make sure it reflects the configuration of the management PC COM port before saving the changes. Change the baud rate back to the desired baud rate if you don’t want to make any changes at this time. To permanently change the configuration, issue the replace and reload command. The MG-IP restarts. MG-IP-1:\Config\CONSOLE>\c\rr MG-IP-1 R03.01.01_D001-202 Login: Managing Basic Functionality This section describes the tasks associated with viewing or configuring basic MG-IP functionality. The tasks include displaying basic status and statistics about the board, changing the CLI prompt, and saving configuration changes and restarting the board.

76 Basic Board Management Tasks Table 18: Basic Board Management Action Directory Command Run an internal self-test \Diagnostics fts (see page A-20 in Appendix A) Display status about the board, including links, type, version, memory, and checksum information \Config, \Monitor, \Diagnostics \Admin gsb (see page A-58 in Appendix A) gbd (see page A-23 in Appendix A) Display information about the configuration database \Admin gcds (see page A-31 in Appendix A) Display the firmware version and status \Admin \Config gfs (see page A-36 in Appendix A) gv (see page A-65 in Appendix A) Set or display the current and modified CLI prompt \Config \General scp (see page A-81 in Appendix A) gcp (see page A-24 in Appendix A) Set or display the date and time as set on the MG-IP \Admin sdt (see page A-96 in Appendix A) gdt (see page A-34 in Appendix A) Replace the startup configuration with modified configuration. The rr command also restarts the MG-IP \Config rp (see page A-75 in Appendix A) rr (see page A-76 in Appendix A) Reload the startup configuration, discarding any changes. The rp command also restarts the MG-IP \Config rl (see page A-69 in Appendix A) Reset the database to a default configuration \Admin sddb (see page A-97 in Appendix A) Autmatic download configuration file (CLI script file or TLV file). Autmatic download Image file (safe dowanload (UDL) mode only) \Admin dlf (see page A-18 in Appendix A) Initialize the System In order to re-initialize the system back to the default configuration, run the sddb command to reset the database. sddb requires the line format, whether E1 or T1 (J1 is for future use), and the clock source. The optional model template defaults to the predefined Olencom model or to the customer specification model. After issuing the sddb command the system restarts. Change directory to \Admin. MG-IP-1:\Admin>sddb t1 internal The request was updated successfully in startup-config. MG-IP-1 R03.01.01_D001-202

77 After the Restart follow the bellow command line: MG-IP:\c\top\ssd all (Disable all running sessions) MG-IP:\c\wan\sce 100 full (Set internal WAN interface to work 100 FDX) MG-IP:\d\d\scep wan off (Disable the PHY on WAN port) MG-IP:\d\d\scep lan on 5 (Set PHY address to 5 on the LAN port) MG-IP:\c\g\scp MG-IP-1 (Optional, Change your CLI Prompt to your Prompt) MG-IP:\c\top\scfg\ccip all 169.254.1.100 0x5 – (Set all sessions to Priority 5, to get highest priority on the internal switch, and best QoS settings for E1/T1 ports. IP address is changed according to your settings.) MG-IP:\c\top\sse all (Set all sessions to enable mode) MG-IP:\c\rr (Replace Reload)

78 Internal Testing The diagnostics directory contains the fts command to run the internal test. This test exercises the MG- IP by routing traffic through all the device interfaces and checking for correct performance. The command performs a device reset, both before and after the test. The following setup must be done for the function to operate successfully: ƒ Connect the LAN/Management (rear) interface to the WAN interface using an Ethernet cross- cable. ƒ Connect an external loopback connector to all four T1/E1 connectors. While the command is running, the MG-IP’s SYS OK LED displays the status: ƒ Alternating red/green indicates the test is proceeding without error. ƒ Flashing red indicates the test has detected a failure. If the test was set to run continuously or for a long interval, the user can cycle the power to stop the test. When the test completes, the device is reset and the version string is sent to the CONSOLE. MG-IP-1:\Diagnostics>fts 2 Self test will start for 2 seconds. Board Test: successful iteration: 0 Board Test: successful iteration: 1 Board Test: ENDED SUCCESSFULLY MG-IP-1 R03.01.01_D001-202 The second example below was run with no loopback set. MG-IP-1:\Diagnostics>fts 2 Board Test: successful iteration: 0 Failed interface: 2, in-frames=0, frames-discards=0, bytesdiscards=0 **** SELF TEST FAILED **** (continue scan) : 1 Board Test: TEST FAILED!!!!!!!: MG-IP-1 R03.01.01_D001-202 After the test completes the system resets. Hardware Status Various hardware features report status back to the console. As noted in Table 18, the commands are spread throughout the directory structure for the convenience of the user. gsb may be run from the \config, \monitor, and \diagnostics directories. gbd may only be executed from the \admin directory. MG-IP-1:\Config>gsb Power up test succeeded Interface LAN link......: DOWN Interface WAN link......: DOWN

79 Port1 Port2 Port3 Port4 Interface T1 link.......: DOWN DOWN DOWN DOWN MG-IP-1:\Config>..\a MG-IP-1:\Admin>gbd Board information Card type.......................... : 0x5-0 (CMX ppm+) CPLD version................... : 0 FLASH data ..................... : FUJITSU 4 Meg DRAM size....................... : 64 MB SW checksum................... : 0x1aeed028 FPGA id ........................... : 0x6 FPGA version................... : 0x6 Shift register value ........... : 0xf Firmware Status The firmware information may be displayed only from the \admin directory using gfs, Get Firmware Status. MG-IP-1:\Admin>gfs Current version....................: R03.01.00_D012 Internal version....................: AeGf1g6h1i4j SW Checksum.....................: 0x1AEED028 The firmware version may be displayed from the \config or \monitor directories: MG-IP-1:\Config>gv MG-IP-1 R03.01.01_D001-202 “R” is for “Release”. The first two digits after “R” represent the major portion of the release number. The next two digits represent the minor release number. The remaining numbers are restricted use only. Database Configuration gcds is only run from the \admin directory. It displays the current database name and version number, sizing information, and the model template. MG-IP-1:\Admin>gcds Internal DB name.................: Aarb0c1d6e0f Customer DB name..............: MG-IP-1 CLI prompt ..........................: MG-IP-1 (Original version) ................: 3.0.0*

80 Current version.....................: 3.0.0* Customer serial num ............: - Validity ................................: Yes Max available size................: 65536 Current size..........................: 4366 Model template ....................: R1601ETEA0000 Master model template.: R1601ETEA0000 To reload the database and discard all changes made to the modified running configuration, change directory to the \config directory. Then run rl. rl returns the system to the state since the previous restart or replace. MG-IP-1:\Config>rl MG-IP-1 R03.01.01_D001-202 In order to replace the startup configuration with the modified running configuration issue an rp, Replace, command. MG-IP-1:\Config>rp The command completed successfully. The rl and rp commands are conveniently grouped together in the rr command, Replace and Reload, which performs them both in a single step. MG-IP-1:\Config>rr MG-IP-1 R03.01.01_D001-202 Login: Date and Time Time is set on the MG-IP from the \Admin directory. Note that the date is day, then month, then year. The default date is January 1, 1970. MG-IP-1:\Admin>gdt Current date: 1 Jan 1970 Current time: 00:07:00 System uptime: 0 days, 00:07:00 (930 ms) Set the date using the sdt command. Again, note that the format is days first (dd), followed by the month (mmm) in character format, followed by a four digit year (yyyy). The time fields are optional and take the form of hours (hh):minutes (mm):seconds (ss). MG-IP-1:\Admin>sdt 19/Jul/2006 03:28 Date and time set successfully. Current date: 19 Jul 2006 Current time: 03:28:00 System uptime: 0 days, 00:11:03 (970 ms)

81 Current CLI Prompt The CLI prompt may be customized using the scp, Set CLI Prompt, command from the \Config\General directory. To see the current prompt use the gcp, Get CLI Prompt, command. MG-IP-1:\Config\General>gcp Running_config Modified Running_con CLI prompt.........: MG-IP-1 Test1 Go back to the \Config directory and run rr to replace and reload. Upon log-in the new prompt is evident. MG-IP-1:\Config>rr MG-IP-1 R03.01.00_D012-202 Login: admin Password: MG-IP-1 R03.01.00_D012-202 Test1:\> Global Configuration Status Two commands show the configuration and status of the Ethernet (LAN and WAN) and the T1/E1 interfaces: gci, and gsi. gci and gsi both run from the \Config or \Monitor directories, display a quick glance subset of the configuration and status of the interfaces. Refer to Managing LAN and WAN Interfaces on page 83, Managing the T1/E1 Interface on page 91 and Ошибка! Источник ссылки не найден. on page Ошибка! Закладка не определена. for configuration and more defined status of each interface and the module application. MG-IP-1:\Config>gci LAN interface configuration LAN interface configuration Running_config Modified Running_config Working mode.................... : ETH ETH AutoNeg ............................. : On On Speed (Mb/s) ..................... : - - Duplex mode ...................... : - - Interface BW (kb/s) ........... : Unlimited Unlimited MAC address...................... : 00-50-C2-15-15-7B 00-50-C2-15-15-7B IP config mode ................... : Static IP Static IP IP address ........................... : 169.254.1.100 169.254.1.100 Subnet mask ....................... : 255.255.255.0 255.255.255.0 T1 interface configuration Running_config Modified Running_config Working mode.................... : Bitstream Bitstream

82 LIU line format................... : T1 T1 Clocking mode ................... : Internal-master Internal-master Port 1 state.......................... : Enabled Enabled Active Profile ..................... : Profile_1 Profile_1 WAN interface configuration Running_config Modified Running_config Working mode.................... : ETH ETH AutoNeg ............................. : - - Speed (Mb/s) ..................... : - - Duplex mode ...................... : - - Interface BW (kb/s) ........... : Unlimited Unlimited MAC address...................... : 00-50-C2-15-15-7A 00-50-C2-15-15-7A IP config mode ................... : Static IP Static IP IP address ........................... : 169.254.1.100 169.254.1.100 Subnet mask ....................... : 255.255.255.0 255.255.255.0 MG-IP-1:\Config>gsi LAN interface configuration Link..................................... : DOWN PHY status .......................... : Working AutoNeg.............................. : - Peer advertisement value .... : - Speed (Mb/s) ...................... : - Duplex mode....................... : - Flow control........................ : - MAC loopback.................... : Disabled DHCP client state................ : DHCP server ip................... : Request sent T1 interface configuration link status............................ : Port1 ---------------------: ----- Link..................................... : DOWN LIU loopback ...................... : Disable LIU database loopback ....... : Disable Alarm Status ....................... : los WAN interface configuration Link..................................... : DOWN

83 Link..................................... : Working AutoNeg - Peer advertisement value .... : - Speed (Mb/s) ...................... : - Duplex mode....................... : - Flow control........................ : - MAC loopback.................... : Disabled Managing LAN and WAN Interfaces This section covers configuring the WAN interface and the LAN/Management (rear) interface. The MG-IP is designed to stream data from the T1/E1 circuit to the WAN interface, which in turn connects over a network to other receiving devices. Data traffic from the LAN interface can be multiplexed with the packetized TDM data and sent to the packet network via the WAN. This section describes how to configure the LAN/Management and WAN interfaces. For information on configuring the T1/E1 port, refer to Managing the T1/E1 Interface on page 91 and Ошибка! Источник ссылки не найден. on page Ошибка! Закладка не определена.. The same configuration commands are used to configure the LAN and the WAN, although the directory is different. While this discussion focuses on the LAN, the system administrator can apply the same actions in the WAN directory. The first connection to the MG-IP is through the CONSOLE. Upon configuration of the LAN it is then possible to perform all management monitoring and configuration tasks using the LAN. LAN/WAN Management Tasks The LAN/Management (rear) interface commands are found in the \Config\LAN directory, and the WAN interface commands are found in the \Config\WAN directory, unless otherwise noted. Refer to Appendix A for an alphabetical list of commands (page A-1). Table 19: LAN/WAN Management Action Comand Display configuration information about the interface gc (see page A-26 in Appendix A) or WAN \Config\gci (see page A-32 in Appendix A) \Config\gsi (see page A-59 in Appendix A) Display and/or reset the status and statistics for the interface gs (see page A-55 in Appendix A) gst (see page A-52 in Appendix A) gss (see page A-48 in Appendix A) Configure the Ethernet settings sce (see page A-88 in Appendix A) scef (see page A-89 in Appendix A) cel (see page A-90 in Appendix A)

84 Action Comand Set or display the Gateway IP address \Config\General\sdg (see page A-98 in Appendix A) \Config\General\gdg (see page A-35 in Appendix A) Set IP and subnet address for the interface sic (see page A-105 in Appendix A) Display the MAC address for the link \Config\General\gma (see page A-42 in Appendix A) Enable or disable MAC loopback sdml (see page A-99 in Appendix A) Apply changes ac (see page A-9 in Appendix A) Ethernet Interface Information The \Config\LAN directory, and the identical \Monitor directory, contains the gc, gs, gss and gst commands. Both gc and gs give more detailed information about the particular interface than gci and gsi. gss and gst provide statistical information regarding the interface. gc Command The GetConfiguration command in the \Config\LAN directory shows five parameters not displayed with gci: Interface type, MAC loopback, PHY configured, PHY number and advertisement. The parameters highlighted in this list are configurable. Each configurable parameter is further discussed below this list. MG-IP-1:\Config\LAN>gc Running_config Modified Running_config Working mode ..................: ETH ETH Interface type ....................: MII MII AutoNeg............................: On On Speed (Mb/s) ....................: - - Duplex mode.....................: - - Flow control......................: Disabled Disabled Interface BW (kb/s) ..........: Unlimited Unlimited MAC address ....................: 00-50-C2-15-15-7B 00-50-C2-15-15-7B MAC loopback..................: Disabled Disabled PHY configured ................: Yes Yes PHY number .....................: 5 5 Advertisement...................: 10F 100H 100F 10F 100H 100F IP config mode..................: Static IP Static IP IP address..........................: 169.254.1.100 169.254.1.100 Subnet mask......................: 255.255.255.0 255.255.255.0

85 Table 20: Ethernet Configuration Commands Parameter CLI CLI Name CLI Page AutoNeg sce SetConfigEth page A-88 in Appendix A Speed sce SetConfigEth page A-88 in Appendix A Duplex Mode sce SetConfigEth page A-88 in Appendix A Flow Control scef SetConfigEthFlowControl page 0A-89 in Appendix A Interface BW cel SetConfigEthLimit page A-90 in Appendix A IP address sic SetIPConfig page A-105 in Appendix A MAC loopback sdml SetDynamicMACLpbk page A-99 in Appendix A gs Command The Get Status command in the \Config\LAN displays the same information as the gsi command run from the \Config directory. See Global Configuration Status on page 81. gss Command Another status command is the GetMibStatistics command. The four possible status reports are for the IP statistics, TCP statistics, UDP statistics and the ICMP statistics. Display Mib statistics for IP: MG-IP-1:\Config\LAN>gss i Ip data mib2 statistics Num of IP forwarding.................................................: 2 Num of IP time to live ................................................: 64 Num of IP in received.................................................: 5 Num of IP in header errors .........................................: 0 Num of IP in address errors........................................: 0 Num of IP frward datagrams ......................................: 0 Num of IP in unknown protocols................................: 0 Num of IP in discards .................................................: 0 Num of IP in delivers..................................................: 5 Num of IP out requests ...............................................: 1108 Num of IP out discards ...............................................: 0 Num of IP out discards do routes................................: 0 Num of IP out discards do routes................................: 0 Num of IP reassembly Timeout..................................: 60 Num of IP reassembly Required.................................: 0 Num of IP reassembly Required.................................: 0 Num of IP reassembly OKs........................................: 0 Num of IP reassembly fails.........................................: 0

86 Num of IP fragment OKs............................................: 0 Num of IP fragment Fails ...........................................: 0 Num of IP fragment creates........................................: 0 Num of IP routing discards.........................................: 0 Display Mib statistics for TCP: MG-IP-1:\Config\LAN>gss t Tcp data mib2 statistics Tcp retransmitting algorithm................................. : Unknown type Num of TCP retransmitting min timeout .............. : 0 Num of TCP retransmitting max timeout.............. : 0 Num of TCP max tcp connection.......................... : 0 Num of TCP active open connections................... : 2 Num of TCP passive open connections................. : 1 Num of TCP attempt failes ................................... : 1 Num of TCP closed state from establised ............. : 0 Num of TCP current extablish or close w............. : 0 Num of TCP In segments received ....................... : 5 Num of TCP Out segments received..................... : 7 Num of TCP segment retransmitted...................... : 0 Num of Tcp received in error................................ : 0 Num of Tcp sent contain RST flag........................ : 1 Tcp data mib2 connections Tcp connection state.............................................. : established Tcp Local ip addr connection................................ : 0x7f000001 Tcp Local port connection .................................... : 0x60b Tcp Remote ip addr connection ............................ : 0x7f000001 Tcp Remote tcp connection................................... : 0x2b29 Tcp connection state.............................................. : established Tcp Local ip addr connection................................ : 0x7f000001 Tcp Local port connection .................................... : 0x2b29 Tcp Remote ip addr connection ............................ : 0x7f000001 Tcp Remote tcp connection................................... : 0x60b Display Mib statistics for UDP: MG-IP-1:\Config\LAN>gss u

87 Udp data mib2 statistics Num of in Udp datagram....................................... : 0 Num of in Udp datagram no port .......................... : 0 Num of in Udp datagram not delivered................. : 0 Num of out Udp datagram not delivered............... : 2 Udp data mib2 connections Udp Local ip addr connection............................... : 0x0 Udp Local port connection.................................... : 0xa1 Udp Local ip addr connection............................... : 0x0 Udp Local port connection.................................... : 0x835 Udp Local ip addr connection............................... : 0x7f000001 Udp Local port connection.................................... : 0x2b29 Udp Local ip addr connection............................... : 0xa9fe0164 Udp Local port connection.................................... : 0x7d0 Display Mib statistics for ICMP: MG-IP-1:\Config\LAN>gss c Icmp data mib2 statistics Num of ICMP in messages ................................... : 0 Num of ICMP in Errors ........................................ : 0 Num of ICMP in Dest unreachables ..................... : 0 Num of ICMP in time exceeded............................ : 0 Num of ICMP in parameter problem .................... : 0 Num of ICMP in source quench............................ : 0 Num of ICMP in redirect ...................................... : 0 Num of ICMP in echo request .............................. : 0 Num of ICMP in echo reply.................................. : 0 Num of ICMP in timestamp request ..................... : 0 Num of ICMP in timestamp replay....................... : 0 Num of ICMP in addr mask request...................... : 0 Num of ICMP in addr mask replay....................... : 0 Num of ICMP out message................................... : 0 Num of ICMP out errors ....................................... : 0 Num of ICMP out dest unreachable...................... : 0

88 Num of ICMP out time exceeded.......................... : 0 Num of ICMP out parameter problem .................. : 0 Num of ICMP out source quench.......................... : 0 Num of ICMP out redirect .................................... : 0 Num of ICMP out echo request ............................ : 1107 Num of ICMP out echo replay.............................. : 0 Num of ICMP out timestamp request ................... : 0 Num of ICMP out timestamp replay..................... : 0 Num of ICMP out addr mask request.................... : 0 Num of ICMP out addr mask replay..................... : 0 gst Command gst displays the ethernet statistics for the LAN interface. MG-IP-1:\Config\LAN>gst In octets ............................... : 0 Out octets............................. : 126848 Frames received................... : 0 Frames transmitted .............. : 1982 In Frames multicast ............. : 0 Out frames multicast............ : 0 In Frames broadcast............. : 0 Out frames broadcast........... : 1982 Alignment errors.................. : 0 CRC errors........................... : 0 Long frames......................... : 0 Short frames ........................ : 0 MG-IP units support limited RMON statictics that may be displayed using this cli command. The folowing RMON counters are supported: ƒ etherStatsTable ƒ etherStatsDropEvents ƒ etherStatsOctets ƒ etherStatsPkts ƒ etherStatsCRCAlignErrors ƒ etherStatsUndersizePkts ƒ etherStatsOversizePkts ƒ etherStatsFragments ƒ etherStatsCollisions

89 cel command This CLI is used to set the bandwith of the LAN/Management (rear interface) tarfic . Given the network bandwidth limit of the PSN (packet-switched network) connected to the WAN port, LAN port bandwidth should be calculated and limited (using cel CLI command) so as not to affect CES flow. For example, if the PSN bandwidth is assumed to be 10 Mbps and the MG-IP-4 uses four full E1/T1 connections (which add up to 9 Mbps required for CES flow), the LAN port bandwidth limit should be set to 1 Mbps. To calculate the exact bandwidth required for the TDM CES flow (after the port and sessions have been configured), use the Config\TDM_Over_Packet>ggc CLI command and observe the “Enable session BW” and the “Disable session Bandwidth” fields. Add 1.8 Mbps overhead to their values. The cel command is available only at the WAN directory. MG-IP-1:\Config\WAN>cel 4000 The request was updated successfully in modified running_config. Use \c\rr to restart the system. Sample Ethernet Configuration This is an example of setting the parameters for the LAN interface. Change directory to \Config\LAN. Execute the gc command to see the current status. Then change parameters using the commands listed in Table 20. After making the desired changes in the modified configuration database run gc again. The changes will be listed under the righthand header, “Modified Running Configuration.” If these changes are correct, run rr to replace the startup configuration and the restart the device. MG-IP-1:\Config\LAN>gc Running_config Modified Running_config Working mode ..................: ETH ETH Interface type ....................: MII MII AutoNeg............................: On On Speed (Mb/s) ....................: - - Duplex mode.....................: - - Flow control......................: Disabled Disabled Interface BW (kb/s) ..........: Unlimited Unlimited MAC address ....................: 00-50-C2-15-15-7B 00-50-C2-15-15-7B MAC loopback..................: Disabled Disabled PHY configured ................: Yes Yes PHY number .....................: 5 5 Advertisement...................: 10F 100H 100F 10F 100H 100F IP config mode..................: Static IP Static IP IP address..........................: 169.254.1.100 169.254.1.100 Subnet mask......................: 255.255.255 255.255.255 Set the interface speed and enable full duplex mode: MG-IP-1:\Config\LAN>sce 100 full

90 The request was updated successfully in modified running_config. Use ac to apply changes Enable the flow control: MG-IP-1:\Config\LAN>scef on The request was updated successfully in modified running_config. Use ac to apply changes Enter a new IP address and sub-net mask: MG-IP-1:\Config\LAN>sic static 10.100.1.5 255.255.255.128 The request was updated successfully in modified running_config. The configuration change will be activated after the next Replace & Reload (\c\rr) Display the configuration changes. Notice that only the modified configuration database contains the changes. MG-IP-1:\Config\LAN>gc Running_config Modified Running_config Working mode ..................: ETH ETH Interface type ....................: MII MII AutoNeg............................: On Off Speed (Mb/s) ....................: - 100 Duplex mode................... :l - Full Flow control......................: Disabled Enabled MAC address ....................: 00-50-C2-15-15-7B 00-50-C2-15-15-7B MAC loopback..................: Disabled Disabled PHY configured ................: Yes Yes PHY number .....................: 5 5 Advertisement...................: 10F 100H 100F - IP config mode..................: Static IP Static IP IP address..........................: 169.254.1.100 10.100.1.5 Subnet mask......................: 255.255.255.0 255.255.255.0 Change directory to \Config and run rr to replace the startup configuration and restart the MG-IP: MG-IP-1:\Config>rr MG-IP-1 R03.01.01_D001-202 Login: admin

91 Password: MG-IP-1 R03.01.01_D001-202 Change directory to \Config\LAN and run gc. The new values are now part of the running configuration database. MG-IP-1:\Config\LAN>gc Running_config Modified Running_config Working mode ..................: ETH ETH Interface type ....................: MII MII AutoNeg............................: Off Off Speed (Mb/s) ....................: 100 100 Duplex mode.....................: Full Full Flow control......................: Enabled Enabled Interface BW (kb/s) ..........: 2000 2000 MAC address ....................: 00-50-C2-15-15-7B 00-50-C2-15-15-7B MAC loopback..................: Disabled Disabled PHY configured ................: Yes Yes PHY number .....................: 5 5 Advertisement...................: - - IP config mode..................: Static IP Static IP IP address..........................: 10.100.1.5 10.100.1.5 Subnet mask......................: 255.255.255.128 255.255.255.128 It is possible to set all Ethernet and MAC layer configuration options dynamically using the ac (ApplyChanges) CLI command, without the need to perform Replace & Reload (\c\rr). However, one must make sure that no pesudowire sessions are active when using this command. Managing the T1/E1 Interface This section describes how to manage the T1/E1 port on the MG-IP. This section describes only the configuration performed prior to, and in preparation for, running the TDM over Packet application on the port. For more information about TDM over Packet and Sessions, refer to Ошибка! Источник ссылки не найден. on page Ошибка! Закладка не определена.. The port is primarily configured by setting the parameters in Profile_1. The Profile configuration can be viewed from the \Config\T1\Profile_1 directory. The port configuration is available through the gc command in the \Config\T1\Port_1 directory. The configuration information may also be obtained from the corresponding \Monitor directories. Due to the nature of the port-session relationship, and in order not to disrupt port traffic intentionally, any changes made to the port, such as a change in session management, require disabling and enabling of the session and/or disabling and enabling the port.

92 T1/E1 Management Tasks The following commands to manage the T1/E1 interface are found in the \Config\T1 (or \Config\E1) directory, or in a subdirectory of this directory (profile definition or port definition), unless otherwise noted. Commands are listed alphabetically in Appendix A. Table 21: T1/E1 Management CLI Commands Action \Config\T1 ..\Port_1 ..\Profile_1 Display configuration information about the interface. gc (see page A-26 in Appendix A) gmcp (see page A-43 in Appendix A) grcp (see page A-46 in Appendix A) gc (see page A-26 in Appendix A) gc (see page A-26 in Appendix A) Display status information. gs (see page A-55 in Appendix A) gs (see page A-55 in Appendix A) Display the SNMP statistics gss (see page A-48 in Appendix A) Display and/or reset statistics about the interface gst (see page A-52 in Appendix A) gst (see page A-52 in Appendix A) Enable/disable the interface spoe (see page A-114 in Appendix A) spod (see page A-113 in Appendix A) Configure the state of a port spos (see page A- 115 in Appendix A) Configure the channel bandwidth scb (see page A-80 in Appendix A) Configure framing parameters sfp (see page A-103 in Appendix A) Configure LIU line build out sfp (see page A-103 in Appendix A) sltt (see page A-91 in Appendix A) Configure LIU line coding sllc (see page A-92 in Appendix A) Configure LIU line Rx termination slrt (see page A-93 in Appendix A) Configure LIU loopback sll (see page A-109 in Appendix A) sldl (see page A-108 in Appendix A) sll (see page A-109 in Appendix A) sldl (see page A-108 in Appendix A) slrt (see page A-93 in Appendix A) Configure LIU Rx equalizer gain limit. sll (see page A-109 in Appendix A) sldl (see page A-108 in Appendix A) sll (see page A-109 in Appendix A) sldl (see page A-108 in Appendix A) sreg (see page A- 119 in Appendix A) Clocking Mode Configuration The folowing CLIs are located in the \Config\clk directory and are used to configure and monitor the clocking mode on the system.

93 Action CLI Comments Configure mode sccm (see page A-82 in Appendix A) Set external clock frequency secf (see page A-102 in Appendix A) direct/differential timing Connect clock to session ccts (see page A-16 in Appendix A) adaptive/differential timing Set active clock sac (see page A-78 in Appendix A) adaptive/differential timing Get config gc (see page A-26 in Appendix A) Set external clock direction secd (see page A-101 in Appendix A) Get clock status gcs (see page A-25 in Appendix A) List clocks lc (see page A-66 in Appendix A) To configure differential timing: ƒ Use the sccm CLI to set the mode to differential ƒ Use the secf command to set external clock frequency ƒ Use the ccts command to select primary/secondary sessions as the source for the differential clock recovery algorithm To configure adaptive timing: ƒ Use the sccm CLI to set the mode to adaptive ƒ Use the ccts command to select primary/secondary sessions as the source for the differential clock recovery algorithm To configure external timing: ƒ Use the sccm CLI to set the mode to external ƒ Use the secf command to set the external clock frequency T1/E1 Interface Information Information about the T1/E1 circuits is made available through five “get” information commands. Two commands, gc, and gs, show the configuration and status of the T1/ E1 interface. Both execute from the \Config\T1 (or E1) or \Monitor\T1 (or E1) directories. In addition gst, Get Statistics, displays statistical information about the port. grcp and gmcp, Get Running Config Ports and Get Modified Running Config Ports, display the current running configuration and the modified configuration for all ports. An additional status command, gss, Get SNMP Statistics, is only valid in the port directories. For clarity the following sections are divided by major “get” information commands. Each section is further divided between the T1/E1 level, the port level and the profile level. Even though there are parameters listed within a configuration report that are configurable, only those that are configurable at the current level are discussed within the section. For example, LIU line format is a configurable

94 parameter from the \Admin directory using the sddb command. However, it is not highlighted in the T1/E1 level because it cannot be configured from the T1/E1 level. gc Command From the \Config\T1 directory the gc command displays high level port and profile information. \Config\T1 Directory MG-IP-1:\Config\T1>gc Running_config Modified Running_config Working mode ................. : Bitstream Bitstream LIU line format................ : T1 T1 Frame size (bytes) ........... : 100 100 Underrun value ................ : 0xFE 0xFE Clocking mode................. : Line 1 Line 1 Tx clock polarity.............. : Rising Rising Rx clock polarity.............. : Falling Falling Port 1 state ....................... : Enabled Enabled Active Profile................... : Profile_1 Profile_1 Table 22: T1/E1 Configuration Parameter CLI CLI Name Reference Frame size Clocking mode sccm Set Config Bitstream Clocking Mode page A-82 in Appendix A Dis/Enabled spod, spoe Set Ports Enable, Set Ports Disable page A-114 in Appendix A, page A-113 in Appendix A \Config\T1\Port_1 Directory Transitioning to the Port_1 directory, the gc command displays the current port configuration. In the following example, please note the difference between the running config and the modified running config regarding the parameter “Framed mode”. “Framed mode” is set from the TDM over Packet directories and will be further discussed in the emulation context. The “Channel bandwidth” parameter depends on a structured mode setting in “Framed mode”. Therefore, the example shows the modified running config “Framed mode” parameter as structured. MG-IP-1:\Config\T1\Port_1>gc Running_config Mod. Running_config Port 1 state.......................................: Enabled Enabled Active Profile..................................: Profile_1 Profile_1 LIU line format ...............................: T1 T1 LIU type..........................................: DS21458 DS21458 LIU line code ..................................: B8ZS B8ZS LIU line build out............................: T1_133 T1_133 LIU Rx term....................................: 100ohm 100ohm

95 LIU monitor gain ............................: Norm Norm LIU Rx equalizer gain limit ............: Short Short LIU jitter attenuation.......................: Rx-path Rx-path LIU loopback ..................................: Disabled Disabled Framed mode ..................................: Unframed ESF Channel bandwidth .........................: - 56K TDM signaling type ........................: OOSF+CAS Table 23: Port Configuration Parameter CLI CLI Name Reference Port_1 state spos Set Port State page A-115 in Appendix A LIU loopback sll sldl Set LIU Loopback, Set dynamic LIU loopback page A-109 in Appendix A, page A-108 in Appendix A Framed mode sfp Set the framing mode page A-103 in Appendix A Channel Bandwidth scb Set Channel Bandwidth page A-80 in Appendix A \Config\T1\Profile_1 Directory Transitioning to the Profile_1 directory, the gc command displays the current profile configuration. MG-IP-1:\Config\T1\Profile_1>gc Running_config Mod. Running_config LIU type ........................................... : DS21458 DS21458 LIU line code.................................... : B8ZS B8ZS LIU line build out............................. : T1_133 T1_133 LIU Rx term ..................................... : 100ohm 100ohm LIU monitor gain.............................. : Norm Norm LIU Rx equalizer gain limit.............. : Short Short LIU jitter attenuation ........................ : Rx-path Rx-path Table 24: Profile Configuration Parameter CLI CLI Name Reference LIU line code..................................: sllc SetConfigLIULineCode page A-92 in Appendix A LIU line build out...........................: sltt SetConfigLIULineBuildout page A-91 in Appendix A LIU Rx term...................................: slrt SetConfigLIURxTerm page A-93 in Appendix A LIU Rx equalizer gain limit............: sreg SetRxEqualizerGainLimit page A-119 in Appendix A gs Command \Config\T1 Directory From the \Config\T1 directory the gs command displays port information for each port.

96 MG-IP-1:\Config\T1>gs Status of interface link status ......................... : Port1 ---------------------- ----- Link.................................. : DOWN LIU loopback ................... : Disable LIU database loopback..... : Disable TDM Tx Clock Source.....: LoopBack dsx1NoAlarm.............: - dsx1RcvFarEndLOF........: - dsx1RcvAIS..............: - dsx1XmtAIS..............: - dsx1LossOfFrame.........: los dsx1LossOfSignal........: - dsx1LoopbackState.......: - dsx1RcvFarEndLOMF.......: - dsx1XmtFarEndLOMF.......: - Table 25: T1/E1 LIU loopback Parameter CLI CLI Name CLI Page LIU database loopback sll, sldl SetLIULpbk SetLIUDynamicLpbk page A-109 in Appendix A, page A-108 in Appendix A Config\T1\Port_1 Directory From the \Config\T1\Port_1 directory the gs command displays status about the specific port. MG-IP-1:\Config\T1\Port_1>gs Link.............................................: DOWN LIU loopback......................: Disable LIU database loopback.............: Disable dsx1NoAlarm.......................: - dsx1RcvFarEndLOF..................: - dsx1RcvAIS........................: - dsx1LossOfFrame...................: - dsx1LossOfSignal..................: los

97 dsx1LoopbackState.................: - dsx1RcvFarEndLOMF.................: - dsx1XmtFarEndLOMF.................: - Table 26: PortLIU loopback Parameter CLI CLI Name CLI Page LIU database loopback sll, sldl SetLIULpbk SetLIUDynamicLpbk page A-109 in Appendix A, page A-108 in Appendix A gst Command The gst command shows transmission information for the T1/E1 circuit. At the port level the only statistics available are Mib statistics. See Ошибка! Источник ссылки не найден. on page Ошибка! Закладка не определена. for more information. \Config\T1 MG-IP-1:\Config\T1>gst Bitstream statistics on T1 interface Port1 ----- In octets ..............: 2192909092 Out octets............: 2192909092 Frames received.........: 10492388 Frames transmitted......: 10492388 TDM Tx Clock Source.....: LoopBack \Config\T1\Port_1 Directory MG-IP-1:\Config\T1\Port_1>gst m Interface name.................................. : Port_1 Interface type ................................... : T1 device Largest datagram.............................. : 100 Interface speed ................................. : 1544000 Admin link status ............................. : Link-up Oper link status ................................ : Link-down Oper link last changed...................... : 0 days 0h:0m:1s In octets............................................ : 550025091 Out octets ......................................... : 550025091

98 grcp Command This command is only valid in the \Config\T1(E1) or \Monitor\T1(E1) directories. his command shows all the running configuration database information for the T1/ 1 circuit. All the configurable parameters have been discussed in the sections above. MG-IP-1:\Config\T1>grcp Running_config.............................. : Port1 ------------------- ----- port state......................................... : Enabled Active Profile ................................. : Profile_1 LIU line format............................... : T1 LIU type ......................................... : DS21458 LIU line code.................................. : B8ZS LIU line build out........................... : T1_133 LIU Rx term ................................... : 100ohm LIU monitor gain............................ : Norm LIU Rx equalizer gain limit............ : Short LIU jitter attenuation...................... : Rx-path LIU loopback.................................. : Disabled LIU database loopback................... : Disabled Framed mode.................................. : Unframed gmcp Command This command is only valid in the \Config\T1(E1) or \Monitor\T1(E1) directories. his command shows all the modified running configuration database information egarding the T1/E1 circuit. All the configurable parameters have been discussed in the ections above. MG-IP-1:\Config\T1>gmcp Modified Running_config ...............................: Port1 ------------------- ----- port state...........................................: Enabled Active Profile...................................: Profile_1 LIU line format ................................: T1 LIU type...........................................: DS21458 LIU line code ...................................: B8ZS LIU line build out.............................: T1_133 LIU Rx term.....................................: 100ohm LIU monitor gain .............................: Norm LIU Rx equalizer gain limit .............: Short LIU jitter attenuation........................: Rx-path