IPmux-24 3.5 MN

INSTALLATION AND OPERATION MANUAL
IPmux-24
TDM Pseudowire Access Gateway
Version 3.5
The Access Company
IPmux-24
TDM Pseudowire Access Gateway
Version 3.5B
Installation and Operation Manual Notice

This manual contains information that is proprietary to RAD Data Communications Ltd. ("RAD"). No part of this publication may be reproduced in any form whatsoever without prior written approval by RAD Data Communications. Right, title and interest, all information, copyrights, patents, know-how, trade secrets and other intellectual property or other proprietary rights relating to this manual and to the IPmux-24 and any software components contained therein are proprietary products of RAD protected under international copyright law and shall be and remain solely with RAD. IPmux-24 is a registered trademark of RAD. No right, license, or interest to such trademark is granted hereunder, and you agree that no such right, license, or interest shall be asserted by you with respect to such trademark. The RAD name, logo, logotype, and the terms EtherAccess, TDMoIP and TDMoIP Driven, and the product names Optimux and IPmux, are registered trademarks of RAD Data Communications Ltd. All other trademarks are the property of their respective holders. You shall not copy, reverse compile or reverse assemble all or any portion of the Manual or the IPmux-24. You are prohibited from, and shall not, directly or indirectly, develop, market, distribute, license, or sell any product that supports substantially similar functionality as the IPmux-24, based on or derived in any way from the IPmux-24. Your undertaking in this paragraph shall survive the termination of this Agreement. This Agreement is effective upon your opening of the IPmux-24 package and shall continue until terminated. RAD may terminate this Agreement upon the breach by you of any term hereof. Upon such termination by RAD, you agree to return to RAD the IPmux-24 and all copies and portions thereof. For further information contact RAD at the address below or contact your local distributor.
International Headquarters RAD Data Communications Ltd. 24 Raoul Wallenberg Street Tel Aviv 69719, Israel Tel: 972-3-6458181 Fax: 972-3-6498250, 6474436 E-mail: market@rad.com
North America Headquarters RAD Data Communications Inc. 900 Corporate Drive Mahwah, NJ 07430, USA Tel: (201) 5291100, Toll free: 1-800-4447234 Fax: (201) 5295777 E-mail: market@rad.com
19992010 RAD Data Communications Ltd.
Publication No. 488-200-07/10
Limited Warranty
RAD warrants to DISTRIBUTOR that the hardware in the IPmux-24 to be delivered hereunder shall be free of defects in material and workmanship under normal use and service for a period of twelve (12) months following the date of shipment to DISTRIBUTOR. If, during the warranty period, any component part of the equipment becomes defective by reason of material or workmanship, and DISTRIBUTOR immediately notifies RAD of such defect, RAD shall have the option to choose the appropriate corrective action: a) supply a replacement part, or b) request return of equipment to its plant for repair, or c) perform necessary repair at the equipment's location. In the event that RAD requests the return of equipment, each party shall pay one-way shipping costs. RAD shall be released from all obligations under its warranty in the event that the equipment has been subjected to misuse, neglect, accident or improper installation, or if repairs or modifications were made by persons other than RAD's own authorized service personnel, unless such repairs by others were made with the written consent of RAD. The above warranty is in lieu of all other warranties, expressed or implied. There are no warranties which extend beyond the face hereof, including, but not limited to, warranties of merchantability and fitness for a particular purpose, and in no event shall RAD be liable for consequential damages. RAD shall not be liable to any person for any special or indirect damages, including, but not limited to, lost profits from any cause whatsoever arising from or in any way connected with the manufacture, sale, handling, repair, maintenance or use of the IPmux-24, and in no event shall RAD's liability exceed the purchase price of the IPmux-24. DISTRIBUTOR shall be responsible to its customers for any and all warranties which it makes relating to IPmux-24 and for ensuring that replacements and other adjustments required in connection with the said warranties are satisfactory. Software components in the IPmux-24 are provided "as is" and without warranty of any kind. RAD disclaims all warranties including the implied warranties of merchantability and fitness for a particular purpose. RAD shall not be liable for any loss of use, interruption of business or indirect, special, incidental or consequential damages of any kind. In spite of the above RAD shall do its best to provide error-free software products and shall offer free Software updates during the warranty period under this Agreement. RAD's cumulative liability to you or any other party for any loss or damages resulting from any claims, demands, or actions arising out of or relating to this Agreement and the IPmux-24 shall not exceed the sum paid to RAD for the purchase of the IPmux-24. In no event shall RAD be liable for any indirect, incidental, consequential, special, or exemplary damages or lost profits, even if RAD has been advised of the possibility of such damages. This Agreement shall be construed and governed in accordance with the laws of the State of Israel.
Product Disposal
To facilitate the reuse, recycling and other forms of recovery of waste equipment in protecting the environment, the owner of this RAD product is required to refrain from disposing of this product as unsorted municipal waste at the end of its life cycle. Upon termination of the units use, customers should provide for its collection for reuse, recycling or other form of environmentally conscientious disposal.
General Safety Instructions

The following instructions serve as a general guide for the safe installation and operation of telecommunications products. Additional instructions, if applicable, are included inside the manual.
Safety Symbols
This symbol may appear on the equipment or in the text. It indicates potential safety hazards regarding product operation or maintenance to operator or service personnel.
Warning
Danger of electric shock! Avoid any contact with the marked surface while the product is energized or connected to outdoor telecommunication lines.
Protective ground: the marked lug or terminal should be connected to the building protective ground bus.
Warning
Some products may be equipped with a laser diode. In such cases, a label with the laser class and other warnings as applicable will be attached near the optical transmitter. The laser warning symbol may be also attached. Please observe the following precautions: Before turning on the equipment, make sure that the fiber optic cable is intact and is connected to the transmitter. Do not attempt to adjust the laser drive current. Do not use broken or unterminated fiber-optic cables/connectors or look straight at the laser beam. The use of optical devices with the equipment will increase eye hazard.
Use of controls, adjustments or performing procedures other than those specified herein, may result in hazardous radiation exposure. ATTENTION: The laser beam may be invisible! In some cases, the users may insert their own SFP laser transceivers into the product. Users are alerted that RAD cannot be held responsible for any damage that may result if non-compliant transceivers are used. In particular, users are warned to use only agency approved products that comply with the local laser safety regulations for Class 1 laser products. Always observe standard safety precautions during installation, operation and maintenance of this product. Only qualified and authorized service personnel should carry out adjustment, maintenance or repairs to this product. No installation, adjustment, maintenance or repairs should be performed by either the operator or the user.
Handling Energized Products

General Safety Practices
Do not touch or tamper with the power supply when the power cord is connected. Line voltages may be present inside certain products even when the power switch (if installed) is in the OFF position or a fuse is blown. For DC-powered products, although the voltages levels are usually not hazardous, energy hazards may still exist. Before working on equipment connected to power lines or telecommunication lines, remove jewelry or any other metallic object that may come into contact with energized parts. Unless otherwise specified, all products are intended to be grounded during normal use. Grounding is provided by connecting the mains plug to a wall socket with a protective ground terminal. If a ground lug is provided on the product, it should be connected to the protective ground at all times, by a wire with a diameter of 18 AWG or wider. Rack-mounted equipment should be mounted only in grounded racks and cabinets. Always make the ground connection first and disconnect it last. Do not connect telecommunication cables to ungrounded equipment. Make sure that all other cables are disconnected before disconnecting the ground. Some products may have panels secured by thumbscrews with a slotted head. These panels may cover hazardous circuits or parts, such as power supplies. These thumbscrews should therefore always be tightened securely with a screwdriver after both initial installation and subsequent access to the panels.
Connecting AC Mains
Make sure that the electrical installation complies with local codes. Always connect the AC plug to a wall socket with a protective ground. The maximum permissible current capability of the branch distribution circuit that supplies power to the product is 16A (20A for USA and Canada). The circuit breaker in the building installation should have high breaking capacity and must operate at short-circuit current exceeding 35A (40A for USA and Canada). Always connect the power cord first to the equipment and then to the wall socket. If a power switch is provided in the equipment, set it to the OFF position. If the power cord cannot be readily disconnected in case of emergency, make sure that a readily accessible circuit breaker or emergency switch is installed in the building installation. In cases when the power distribution system is IT type, the switch must disconnect both poles simultaneously.
Connecting DC Power
Unless otherwise specified in the manual, the DC input to the equipment is floating in reference to the ground. Any single pole can be externally grounded. Due to the high current capability of DC power systems, care should be taken when connecting the DC supply to avoid short-circuits and fire hazards. Make sure that the DC power supply is electrically isolated from any AC source and that the installation complies with the local codes.
The maximum permissible current capability of the branch distribution circuit that supplies power to the product is 16A (20A for USA and Canada). The circuit breaker in the building installation should have high breaking capacity and must operate at short-circuit current exceeding 35A (40A for USA and Canada). Before connecting the DC supply wires, ensure that power is removed from the DC circuit. Locate the circuit breaker of the panel board that services the equipment and switch it to the OFF position. When connecting the DC supply wires, first connect the ground wire to the corresponding terminal, then the positive pole and last the negative pole. Switch the circuit breaker back to the ON position. A readily accessible disconnect device that is suitably rated and approved should be incorporated in the building installation. If the DC power supply is floating, the switch must disconnect both poles simultaneously.
Connecting Data and Telecommunications Cables

Data and telecommunication interfaces are classified according to their safety status. The following table lists the status of several standard interfaces. If the status of a given port differs from the standard one, a notice will be given in the manual.
Ports V.11, V.28, V.35, V.36, RS-530, X.21, 10 BaseT, 100 BaseT, Unbalanced E1, E2, E3, STM, DS-2, DS-3, S-Interface ISDN, Analog voice E&M xDSL (without feeding voltage), Balanced E1, T1, Sub E1/T1
Safety Status SELV Safety Extra Low Voltage: Ports which do not present a safety hazard. Usually up to 30 VAC or 60 VDC.
TNV-1 Telecommunication Network Voltage-1: Ports whose normal operating voltage is within the limits of SELV, on which overvoltages from telecommunications networks are possible. TNV-2 Telecommunication Network Voltage-2: Ports whose normal operating voltage exceeds the limits of SELV (usually up to 120 VDC or telephone ringing voltages), on which overvoltages from telecommunication networks are not possible. These ports are not permitted to be directly connected to external telephone and data lines. TNV-3 Telecommunication Network Voltage-3: Ports whose normal operating voltage exceeds the limits of SELV (usually up to 120 VDC or telephone ringing voltages), on which overvoltages from telecommunication networks are possible.
FXS (Foreign Exchange Subscriber)
FXO (Foreign Exchange Office), xDSL (with feeding voltage), U-Interface ISDN
Always connect a given port to a port of the same safety status. If in doubt, seek the assistance of a qualified safety engineer. Always make sure that the equipment is grounded before connecting telecommunication cables. Do not disconnect the ground connection before disconnecting all telecommunications cables. Some SELV and non-SELV circuits use the same connectors. Use caution when connecting cables. Extra caution should be exercised during thunderstorms.
When using shielded or coaxial cables, verify that there is a good ground connection at both ends. The grounding and bonding of the ground connections should comply with the local codes. The telecommunication wiring in the building may be damaged or present a fire hazard in case of contact between exposed external wires and the AC power lines. In order to reduce the risk, there are restrictions on the diameter of wires in the telecom cables, between the equipment and the mating connectors.
Caution
To reduce the risk of fire, use only No. 26 AWG or larger telecommunication line cords.
Attention
Pour rduire les risques sincendie, utiliser seulement des conducteurs de tlcommunications 26 AWG ou de section suprieure.
Some ports are suitable for connection to intra-building or non-exposed wiring or cabling only. In such cases, a notice will be given in the installation instructions. Do not attempt to tamper with any carrier-provided equipment or connection hardware.
Electromagnetic Compatibility (EMC)

The equipment is designed and approved to comply with the electromagnetic regulations of major regulatory bodies. The following instructions may enhance the performance of the equipment and will provide better protection against excessive emission and better immunity against disturbances. A good ground connection is essential. When installing the equipment in a rack, make sure to remove all traces of paint from the mounting points. Use suitable lock-washers and torque. If an external grounding lug is provided, connect it to the ground bus using braided wire as short as possible. The equipment is designed to comply with EMC requirements when connecting it with unshielded twisted pair (UTP) cables. However, the use of shielded wires is always recommended, especially for high-rate data. In some cases, when unshielded wires are used, ferrite cores should be installed on certain cables. In such cases, special instructions are provided in the manual. Disconnect all wires which are not in permanent use, such as cables used for one-time configuration. The compliance of the equipment with the regulations for conducted emission on the data lines is dependent on the cable quality. The emission is tested for UTP with 80 dB longitudinal conversion loss (LCL). Unless otherwise specified or described in the manual, TNV-1 and TNV-3 ports provide secondary protection against surges on the data lines. Primary protectors should be provided in the building installation. The equipment is designed to provide adequate protection against electro-static discharge (ESD). However, it is good working practice to use caution when connecting cables terminated with plastic connectors (without a grounded metal hood, such as flat cables) to sensitive data lines. Before connecting such cables, discharge yourself by touching ground or wear an ESD preventive wrist strap.
FCC-15 User Information

This equipment has been tested and found to comply with the limits of the Class A digital device, pursuant to Part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the Installation and Operation manual, may cause harmful interference to the radio communications. Operation of this equipment in a residential area is likely to cause harmful interference in which case the user will be required to correct the interference at his own expense.
Canadian Emission Requirements

This Class A digital apparatus meets all the requirements of the Canadian Interference-Causing Equipment Regulation. Cet appareil numrique de la classe A respecte toutes les exigences du Rglement sur le matriel brouilleur du Canada.
Warning per EN 55022 (CISPR-22)

Warning
This is a class A product. In a domestic environment, this product may cause radio interference, in which case the user will be required to take adequate measures. Cet appareil est un appareil de Classe A. Dans un environnement rsidentiel, cet appareil peut provoquer des brouillages radiolectriques. Dans ces cas, il peut tre demand lutilisateur de prendre les mesures appropries. Das vorliegende Gert fllt unter die Funkstrgrenzwertklasse A. In Wohngebieten knnen beim Betrieb dieses Gertes Rundfunkstrrungen auftreten, fr deren Behebung der Benutzer verantwortlich ist.
Avertissement
Achtung
Mise au rebut du produit

Afin de faciliter la rutilisation, le recyclage ainsi que d'autres formes de rcupration d'quipement mis au rebut dans le cadre de la protection de l'environnement, il est demand au propritaire de ce produit RAD de ne pas mettre ce dernier au rebut en tant que dchet municipal non tri, une fois que le produit est arriv en fin de cycle de vie. Le client devrait proposer des solutions de rutilisation, de recyclage ou toute autre forme de mise au rebut de cette unit dans un esprit de protection de l'environnement, lorsqu'il aura fini de l'utiliser.
Franais
Avertissement
Instructions gnrales de scurit

Les instructions suivantes servent de guide gnral d'installation et d'opration scurises des produits de tlcommunications. Des instructions supplmentaires sont ventuellement indiques dans le manuel.
Symboles de scurit
Ce symbole peut apparaitre sur l'quipement ou dans le texte. Il indique des risques potentiels de scurit pour l'oprateur ou le personnel de service, quant l'opration du produit ou sa maintenance.
Danger de choc lectrique ! Evitez tout contact avec la surface marque tant que le produit est sous tension ou connect des lignes externes de tlcommunications.
Mise la terre de protection : la cosse ou la borne marque devrait tre connecte la prise de terre de protection du btiment.
Avant la mise en marche de l'quipement, assurez-vous que le cble de fibre optique est intact et qu'il est connect au transmetteur. Ne tentez pas d'ajuster le courant de la commande laser. N'utilisez pas des cbles ou connecteurs de fibre optique casss ou sans terminaison et n'observez pas directement un rayon laser. L'usage de priphriques optiques avec l'quipement augmentera le risque pour les yeux.
L'usage de contrles, ajustages ou procdures autres que celles spcifies ici pourrait rsulter en une dangereuse exposition aux radiations. ATTENTION : Le rayon laser peut tre invisible !
Les utilisateurs pourront, dans certains cas, insrer leurs propres metteurs-rcepteurs Laser SFP dans le produit. Les utilisateurs sont avertis que RAD ne pourra pas tre tenue responsable de tout dommage pouvant rsulter de l'utilisation d'metteurs-rcepteurs non conformes. Plus particulirement, les utilisateurs sont avertis de n'utiliser que des produits approuvs par l'agence et conformes la rglementation locale de scurit laser pour les produits laser de classe 1. Respectez toujours les prcautions standards de scurit durant l'installation, l'opration et la maintenance de ce produit. Seul le personnel de service qualifi et autoris devrait effectuer l'ajustage, la maintenance ou les rparations de ce produit. Aucune opration d'installation, d'ajustage, de maintenance ou de rparation ne devrait tre effectue par l'oprateur ou l'utilisateur.
Manipuler des produits sous tension

Rgles gnrales de scurit
Ne pas toucher ou altrer l'alimentation en courant lorsque le cble d'alimentation est branch. Des tensions de lignes peuvent tre prsentes dans certains produits, mme lorsque le commutateur (s'il est install) est en position OFF ou si le fusible est rompu. Pour les produits aliments par CC, les niveaux de tension ne sont gnralement pas dangereux mais des risques de courant peuvent toujours exister. Avant de travailler sur un quipement connect aux lignes de tension ou de tlcommunications, retirez vos bijoux ou tout autre objet mtallique pouvant venir en contact avec les pices sous tension. Sauf s'il en est autrement indiqu, tous les produits sont destins tre mis la terre durant l'usage normal. La mise la terre est fournie par la connexion de la fiche principale une prise murale quipe d'une borne protectrice de mise la terre. Si une cosse de mise la terre est fournie avec le produit, elle devrait tre connecte tout moment une mise la terre de protection par un conducteur de diamtre 18 AWG ou plus. L'quipement mont en chssis ne devrait tre mont que sur des chssis et dans des armoires mises la terre. Branchez toujours la mise la terre en premier et dbranchez-la en dernier. Ne branchez pas des cbles de tlcommunications un quipement qui n'est pas mis la terre. Assurez-vous que tous les autres cbles sont dbranchs avant de dconnecter la mise la terre.
Franais
Certains produits peuvent tre quips d'une diode laser. Dans de tels cas, une tiquette indiquant la classe laser ainsi que d'autres avertissements, le cas chant, sera jointe prs du transmetteur optique. Le symbole d'avertissement laser peut aussi tre joint. Avertissement Veuillez observer les prcautions suivantes :
Connexion au courant du secteur

Assurez-vous que l'installation lectrique est conforme la rglementation locale. Branchez toujours la fiche de secteur une prise murale quipe d'une borne protectrice de mise la terre. La capacit maximale permissible en courant du circuit de distribution de la connexion alimentant le produit est de 16A (20A aux Etats-Unis et Canada). Le coupe-circuit dans l'installation du btiment devrait avoir une capacit leve de rupture et devrait fonctionner sur courant de court-circuit dpassant 35A (40A aux Etats-Unis et Canada). Branchez toujours le cble d'alimentation en premier l'quipement puis la prise murale. Si un commutateur est fourni avec l'quipement, fixez-le en position OFF. Si le cble d'alimentation ne peut pas tre facilement dbranch en cas d'urgence, assurez-vous qu'un coupe-circuit ou un disjoncteur d'urgence facilement accessible est install dans l'installation du btiment. Le disjoncteur devrait dconnecter simultanment les deux ples si le systme de distribution de courant est de type IT.
Franais
Connexion d'alimentation CC
Sauf s'il en est autrement spcifi dans le manuel, l'entre CC de l'quipement est flottante par rapport la mise la terre. Tout ple doit tre mis la terre en externe. A cause de la capacit de courant des systmes alimentation CC, des prcautions devraient tre prises lors de la connexion de l'alimentation CC pour viter des courts-circuits et des risques d'incendie. Assurez-vous que l'alimentation CC est isole de toute source de courant CA (secteur) et que l'installation est conforme la rglementation locale. La capacit maximale permissible en courant du circuit de distribution de la connexion alimentant le produit est de 16A (20A aux Etats-Unis et Canada). Le coupe-circuit dans l'installation du btiment devrait avoir une capacit leve de rupture et devrait fonctionner sur courant de court-circuit dpassant 35A (40A aux Etats-Unis et Canada). Avant la connexion des cbles d'alimentation en courant CC, assurez-vous que le circuit CC n'est pas sous tension. Localisez le coupe-circuit dans le tableau desservant l'quipement et fixez-le en position OFF. Lors de la connexion de cbles d'alimentation CC, connectez d'abord le conducteur de mise la terre la borne correspondante, puis le ple positif et en dernier, le ple ngatif. Remettez le coupe-circuit en position ON. Un disjoncteur facilement accessible, adapt et approuv devrait tre intgr l'installation du btiment. Le disjoncteur devrait dconnecter simultanment les deux ples si l'alimentation en courant CC est flottante.
Declaration of Conformity
Manufacturer's Name: Manufacturer's Address: declares that the product: Product Name: IPmux-24 RAD Data Communications Ltd. 24 Raoul Wallenberg St., Tel Aviv 69719, Israel
conforms to the following standard(s) or other normative document(s): EMC: EN 55022:1998 + A1:2000, A2:2003 EN 50024: 1998 A1:2001, A2:2003 EN 61000-3-2:2000 + A2:2005 Information technology equipment Radio disturbance characteristics Limits and methods of measurement. Information technology equipment Immunity characteristics Limits and methods of measurement. Electromagnetic compatibility (EMC) - Part 3-2: Limits - Limits for harmonic current emissions (equipment input current up to and including 16A per phase). Electromagnetic compatibility (EMC) - Part 3-3: Limits - Limitation of voltage changes, voltage fluctuations and flicker in public low voltage supply systems, for equipment with rated current 16A per phase and not subject to conditional connection. Information technology equipment Safety Part 1: General requirements.
EN 61000-3-3:1995 + A1:2001
Safety: Supplementary Information:
EN 60950-1:2001 + A11:2004
The product herewith complies with the requirements of the EMC Directive 2004/108/EC, the Low Voltage Directive 2006/95/EC and the R&TTE Directive 99/5/EC for wired equipment. The product was tested in a typical configuration. Tel Aviv, 22 February, 2008
Haim Karshen VP Quality European Contact: RAD Data Ottobrunn-Riemerling, Germany Communications GmbH, Otto-Hahn-Str. 28-30, 85521
Glossary
Address Attenuation AWG Balanced
A coded representation of the origin or destination of data. Signal power loss through equipment, lines or other transmission devices. Measured in decibels. The American Wire Gauge System, which specifies wire width. A transmission line in which voltages on the two conductors are equal in magnitude, but opposite in polarity, with respect to ground. The range of frequencies passing through a given circuit. The greater the bandwidth, the more information can be sent through the circuit in a given amount of time. Signaling method in E1/T1 representing a binary 1 by alternating positive and negative pulses, and a binary 0 by absence of pulses. The smallest unit of information in a binary system. Represents either a one or zero (1 or 0). A device interconnecting local area networks at the OSI data link layer, filtering and forwarding frames according to media access control (MAC) addresses. A storage device. Commonly used to compensate for differences in data rates or event timing when transmitting from one device to another. Also used to remove jitter. A group of bits (normally 8 bits in length). The 53-byte basic information unit within an ATM network. The user traffic is segmented into cells at the source and reassembled at the destination. An ATM cell consists of a 5-byte ATM header and a 48-byte ATM payload, which contains the user data. Structure-aware TDM Circuit Emulation Service over Packet Switched Network. A method for encapsulating structured (NxDS0) Time Division Multiplexed (TDM) signals as pseudo-wires over packet switched networks (PSN). A path for electrical transmission between two or more points. Also called a link, line, circuit or facility. Technology for offering circuit emulation services over packetswitched networks. The service offers traditional TDM trunking (at n x 64 kbps, fractional E1/T1, E1/T1 or E3/T3) over a range of transport protocols, including Internet Protocol (IP), MPLS and Ethernet. A term for the source(s) of timing signals used in synchronous transmission.
Bandwidth
Bipolar
Bit Bridge
Buffer
Byte Cell
CESoPSN
Channel Circuit Emulation Service
Clock
Data Diagnostics Encapsulation
Information represented in digital form, including voice, text, facsimile and video. The detection and isolation of a malfunction or mistake in a communications device, network or system. Encapsulating data is a technique used by layered protocols in which a low level protocol accepts a message from a higher level protocol, then places it in the data portion of the lower-level frame. The logistics of encapsulation require that packets traveling over a physical network contain a sequence of headers. Ethernet Ring Protection Switching, a sub-50ms protection mechanism for Ethernet traffic in a ring topology. It is defined by ITU-T G.8032 specifications. A local area network (LAN) technology which has extended into the wide area networks. Ethernet operates at many speeds, including data rates of 10 Mbps (Ethernet), 100 Mbps (Fast Ethernet), 1,000 Mbps (Gigabit Ethernet), 10 Gbps, 40 Gbps, and 100 Gbps. A congestion control mechanism that results in an ATM system implementing flow control. A logical grouping of information sent as a link-layer unit over a transmission medium. The terms packet, datagram, segment, and message are also used to describe logical information groupings. At the physical and data link layers of the OSI model, bits are fit into units called frames. Frames contain source and destination information, flags to designate the start and end of the frame, plus information about the integrity of the frame. All other information, such as network protocols and the actual payload of data, is encapsulated in a packet, which is encapsulated in the frame. A circuit or device permitting transmission in two directions (sending and receiving) at the same time. An ITU standard for the physical and electrical characteristics of various digital interfaces, including those at 64 kbps and 2.048 Mbps. Gateways are points of entrance and exit from a communications network. Viewed as a physical entity, a gateway is that node that translates between two otherwise incompatible networks or network segments. Gateways perform code and protocol conversion to facilitate traffic between data highways of differing architecture. The combined effect of resistance, inductance and capacitance on a transmitted signal. Impedance varies at different frequencies. A shared boundary, defined by common physical interconnection characteristics, signal characteristics, and meanings of exchanged signals.
ERPS
Ethernet
Flow Control Frame
Framing
Full Duplex G.703
Gateway
Impedance Interface
IP Address
Also known as an Internet address. A unique string of numbers that identifies a computer or device on a TCP/IP network. The format of an IP address is a 32-bit numeric address written as four numbers from 0 to 255, separated by periods (for example, 1.0.255.123). The deviation of a transmission signal in time or phase. It can introduce errors and loss of synchronization in high speed synchronous communications. The addition of inductance to a line in order to minimize amplitude distortion. Used commonly on public telephone lines to improve voice quality, it can make the lines impassable to high speed data, and baseband modems. A type of diagnostic test in which the transmitted signal is returned to the sending device after passing through all or part of a communications link or network. The Network Time Protocol, a protocol for synchronizing the clocks of computer systems over packet-switched, variable-latency data networks. NTP uses UDP on port 123 as its transport layer. An application that receives Simple Network Management Protocol (SNMP) information from an agent. An agent and manager share a database of information, called the Management Information Base (MIB). An agent can use a message called a traps-PDU to send unsolicited information to the manager. A manager that uses the RADview MIB can query the RAD device, set parameters, sound alarms when certain conditions appear, and perform other administrative tasks. The source of timing signals (or the signals themselves) that all network stations use for synchronization. (1) An interconnected group of nodes. (2) A series of points, nodes, or stations connected by communications channels; the collection of equipment through which connections are made between data stations. An ordered group of data and control signals transmitted through a network, as a subset of a larger message. The 48-byte segment of the ATM cell containing user data. Any adaptation of user data via the AAL will take place within the payload. Layer 1 of the OSI model. The layer concerned with electrical, mechanical, and handshaking procedures over the interface connecting a device to the transmission medium. The physical interface to a computer or multiplexer, for connection of terminals and modems. A formal set of conventions governing the formatting and relative timing of message exchange between two communicating systems.
Jitter
Loading
Loopback
NTP
Manager
Master Clock Network
Packet Payload
Physical Layer
Port Protocol
Pseudowire
Point-to-point connections set up to emulate (typically Layer 2) native services like ATM, Frame Relay, Ethernet, TDM, or SONET/SDH over an underlying common packet-switched network (Ethernet, MPLS or IP) core. Pseudowires are defined by the IETF PWE3 (pseudowire emulation edge-to-edge) working group. Structure-Agnostic Time Division Multiplexing (TDM) over Packet. A method for encapsulating Time Division Multiplexing (TDM) bitstreams (T1, E1, T3, E3) that disregards any structure that may be imposed on these streams, in particular the structure imposed by the standard TDM framing. In telecommunications, the absence of a signal. Equivalent to a binary 0. A digital transmission link with a capacity of 1.544 Mbps used in North America. Typically channelized into 24 DS0s, each capable of carrying a single voice conversation or data stream. Uses two pairs of twisted pair wires. The amount of information transferred through the network between two users in a given period, usually measured in the number of packets per second (pps). TDM over IP is a standards-based pseudowire transport technology that extends voice, video or data circuits across packet-switched networks simply, transparently and economically. TDMoIP supports the multiple signaling standards, OAM mechanisms and clock recovery features demanded by TDM networks for carrying voice-grade telephony.
SAToP
Space T1
Throughput
TDMoIP
Quick Start Guide

Installation of IPmux-24 should be carried out only by an experienced technician. If you are familiar with IPmux-24, use this guide to prepare the unit for operation.
1.
Installing the Unit
Connecting the Interfaces

1. Connect the network interface to the connector designated ETH 1. 2. Connect the user LAN(s) to the connector(s) designated ETH 2 or ETH 3. 3. Connect the E1 or T1 lines to the RJ-45 connectors designated E1 or T1.
Caution
When connecting balanced E1 or T1 equipment, make sure to use only 4-wire RJ-45 connectors with the following pins used for receiving and transmitting data: 1, 2, 4, 5. Do not use 8-pin RJ-45 connectors. 4. Connect the control terminal to the rear panel CONTROL connector. or Connect a Telnet host, or a PC running a Web browsing application to one of the user LAN ports.
Connecting the Power

Connect the power cable to the power connector on the IPmux-24 rear panel. The unit has no power switch. Operation starts when the power is applied to the rear panel power connector.
2.
Configuring the Unit
Configure IPmux-24 to the desired operation mode via an ASCII terminal connected to the rear panel CONTROL port. Alternatively, you can manage IPmux-24 over Telnet, or via a PC running a Web browsing application connected to one of the user LAN ports.
IPmux-24 Ver. 3.5
Quick Start Guide
Installation and Operation Manual
Starting a Terminal Session for the First Time

To start a terminal session: 1. Connect a terminal to the CONTROL connector of IPmux-24. 2. Turn on the control terminal PC and set its port parameters to 115,200 baud, 8 bits/character, 1 stop bit, no parity. Set the terminal emulator to ANSI VT100 emulation (for optimal view of system menus). 3. Power IPmux-24 up and proceed with the management session.
Configuring the IP Management Parameters

The host IP address, subnet mask, and default gateway IP address must be configured via an ASCII terminal. To configure the IP management parameters: From the Host IP menu (Configuration > System > Management > Host IP), select an IP address of the IPmux-24 host.
Configuring the System Clock

IPmux-24 system timing mechanism ensures a single clock source for all TDM links by providing the master and fallback clocks. To configure the system clock: From the System Clock menu (Configuration > System > System clock), select the master and fallback timing reference for IPmux-24.
Configuring E1 and T1 at the Physical Level

E1 and T1 interfaces must be configured at the physical level first. To configure E1 and T1 at the physical level: 1. From the TDM Interface Type menu (Configuration > Physical layer > TDM interface type), select the TDM interface type, E1 or T1. 2. From the TDM Configuration menu (Configuration > Physical layer > TDM configuration), configure the necessary parameters of the E1 or T1 services.
Connecting Bundle
The E1/T1 timeslots must be assigned to a bundle. The bundle must be sent to the remote IP address and be connected to one of the destination bundles. To assign timeslots to a bundle: From the DS0 Bundle Configuration menu (Main > Configuration > Connection > DS0 bundle configuration), assign desired timeslots to a bundle by setting them to 1.
IPmux-24 Ver. 3.5
Quick Start Guide
To configure a PW host: From the PW Host IP menu (Configuration > Connection > PW host IP), define IP parameters of PW host. It is an IP host which receives pseudowire traffic generated by remote device.
To connect a bundle: From the Bundle Connection Configuration menu (Main > Configuration > Connection > Bundle connection configuration), configure the necessary bundle connection parameters.
IPmux-24 Ver. 3.5
Quick Start Guide
IPmux-24 Ver. 3.5
Contents
Chapter 1. Introduction 1.1 Overview.................................................................................................................... 1-1 Product Options...................................................................................................... 1-1 Applications ............................................................................................................ 1-2 Features ................................................................................................................. 1-2 E1 Interface ....................................................................................................... 1-2 T1 Interface ....................................................................................................... 1-2 Timing................................................................................................................ 1-3 Packet Networks ................................................................................................ 1-3 Payload Encapsulation ........................................................................................ 1-4 QoS ................................................................................................................... 1-5 Ring Topology .................................................................................................... 1-5 Ethernet Link Protection ..................................................................................... 1-6 Ethernet OAM .................................................................................................... 1-6 Management ...................................................................................................... 1-6 Environment ...................................................................................................... 1-6 1.2 Physical Description ................................................................................................... 1-7 1.3 Functional Description................................................................................................ 1-7 Service Type ........................................................................................................... 1-8 Unframed........................................................................................................... 1-8 Fractional ........................................................................................................... 1-8 Fractional with CAS ............................................................................................ 1-8 HDLC.................................................................................................................. 1-8 Timeslot Assignment in a Bundle ............................................................................. 1-8 Testing ................................................................................................................... 1-9 Timing Modes ......................................................................................................... 1-9 E1/T1 Timing ...................................................................................................... 1-9 System Timing.................................................................................................... 1-9 Network Timing Schemes ........................................................................................ 1-9 External Network Timing................................................................................... 1-10 Adaptive Timing ............................................................................................... 1-11 Frame Format ....................................................................................................... 1-11 UDP/IP Encapsulation (MPLS and IP Networks) .................................................. 1-11 MPLS Encapsulation (Ethernet and MPLS Networks) .......................................... 1-14 Ethernet (MEF 8) Encapsulation ........................................................................ 1-15 Payload Encapsulation .......................................................................................... 1-15 Packet Delay Variation .......................................................................................... 1-17 PDVT (Jitter) Buffer ............................................................................................... 1-18 Packet Creation Time (PCT) ................................................................................... 1-18 TDMoIP ............................................................................................................ 1-18 CESoPSN .......................................................................................................... 1-19 SAToP .............................................................................................................. 1-19 Round Trip Delay .................................................................................................. 1-19 Ethernet Throughput ............................................................................................ 1-19 Pseudowire OAM .................................................................................................. 1-20 End-to-End Alarm Generation................................................................................ 1-20 Trail-Extended Mode ............................................................................................. 1-21 VLAN Traffic Behavior ........................................................................................... 1-21 Bridge................................................................................................................... 1-22 Multiple Hosts....................................................................................................... 1-22
IPmux-24 Ver. 3.5 i
Table of Contents
Proprietary Ethernet Ring ...................................................................................... 1-22 G.8032 Ethernet Ring Protection (ERP) ................................................................. 1-24 Ethernet Port Protection ....................................................................................... 1-25 Link Aggregation .............................................................................................. 1-25 Dual Homing .................................................................................................... 1-26 Bundle Redundancy .............................................................................................. 1-27 Ethernet Service OAM (IEEE 802.1ag, ITU-T Y.1731) .............................................. 1-28 Maintenance Domains ...................................................................................... 1-28 Maintenance Entities ........................................................................................ 1-28 MEG Endpoints ................................................................................................. 1-28 Connectivity Fault Management Protocols ......................................................... 1-29 Link OAM (IEEE 802.3ah) ....................................................................................... 1-30 Management ........................................................................................................ 1-31 Security ........................................................................................................... 1-31 Syslog .............................................................................................................. 1-31 Simple Network Time Protocol .............................................................................. 1-31 QoS ...................................................................................................................... 1-32 Traffic Classification and Prioritization .............................................................. 1-32 Rate Limitation ................................................................................................ 1-32 L2CP Handling ....................................................................................................... 1-32 1.4 Technical Specifications............................................................................................ 1-32 Chapter 2. Installation and Setup 2.1 2.2 2.3 2.4 Introduction ............................................................................................................... 2-1 Site Requirements and Prerequisites .......................................................................... 2-1 Package Contents ...................................................................................................... 2-1 Required Equipment ................................................................................................... 2-2 Power Cable............................................................................................................ 2-2 Interface Cables ...................................................................................................... 2-2 2.5 Mounting the Unit ...................................................................................................... 2-2 2.6 Installing SFP Modules ................................................................................................ 2-3 2.7 Connecting to Ethernet Equipment ............................................................................. 2-4 2.8 Connecting to E1/T1 Devices ...................................................................................... 2-4 2.9 Connecting to ASCII Terminal ...................................................................................... 2-5 2.10 Connecting to External Clock Source ........................................................................... 2-6 2.11 Connecting to External Alarm Device .......................................................................... 2-6 2.12 Connecting to Power .................................................................................................. 2-6 Connecting to AC Power.......................................................................................... 2-7 Connecting to DC Power ......................................................................................... 2-7 Chapter 3. Operation 3.1 3.2 3.3 3.4 Turning On the Unit ................................................................................................... 3-1 Indicators .................................................................................................................. 3-1 Default Settings ......................................................................................................... 3-3 Configuration and Management Alternatives ............................................................ 3-11 Working with Terminal .......................................................................................... 3-12 Login ............................................................................................................... 3-14 Choosing Options ............................................................................................. 3-15 Ending a Terminal Configuration Session........................................................... 3-16 Verifying the Application Software Version ....................................................... 3-16 Working with Web Terminal................................................................................... 3-16 Web Browser Requirements ............................................................................. 3-16
ii
IPmux-24 Ver. 3.5
Table of Contents
General Web Browsers Operating Procedures ................................................... 3-17 Working with RADview .......................................................................................... 3-17 Working with SNMP............................................................................................... 3-18 Menu Maps ........................................................................................................... 3-18 3.5 Turning IPmux-24 Off ............................................................................................... 3-24 Chapter 4. Configuration 4.1 Configuring for Management ...................................................................................... 4-1 Configuring IP Host Parameters ............................................................................... 4-1 Configuring DHCP Client ..................................................................................... 4-1 Managing IP Parameters of the IPmux-24 Host ................................................... 4-2 Defining Read, Write and Trap Communities ............................................................ 4-3 Configuring the Host Encapsulation ......................................................................... 4-3 Assigning a Name to the Unit and Its Location ........................................................ 4-4 Defining Network Managers .................................................................................... 4-4 Configuring SNMPv3 ................................................................................................ 4-5 Configuring the SNMP Engine ID ......................................................................... 4-6 Enabling SNMPv3 ................................................................................................ 4-6 Adding SNMPv3 Users ........................................................................................ 4-7 Adding Notification Entries ................................................................................. 4-8 Assigning Traps .................................................................................................. 4-8 Configuring Target Parameters ........................................................................... 4-9 Configuring Target Address .............................................................................. 4-10 Mapping SNMPv1 to SNMPv3 ............................................................................ 4-11 Configuring Management Access Permissions and Methods ................................... 4-11 Defining Management Access Permissions ........................................................ 4-11 Controlling Management Access ............................................................................ 4-13 Configuring RADIUS Client ..................................................................................... 4-14 Configuring Control Port Parameters ..................................................................... 4-15 4.2 Configuring for Operation ........................................................................................ 4-16 Setting Device-Level Parameters ........................................................................... 4-16 Configuring the System Clock ........................................................................... 4-16 Selecting the TDM Interface Type ..................................................................... 4-17 Configuring the Resilient Fast Ethernet Ring (RFER) .......................................... 4-18 Configuring the IEEE 8032 Ethernet Ring (ERP) ................................................. 4-19 Configuring the LAG ......................................................................................... 4-22 Configuring Dual Homing .................................................................................. 4-23 Configuring Bundle Protection .......................................................................... 4-25 Configuring the Service OAM ............................................................................ 4-27 Configuring the Link OAM ................................................................................. 4-38 Setting Physical Layer Parameters ......................................................................... 4-40 Configuring the E1 TDM Interface ..................................................................... 4-40 Configuring the E1 External Clock Interface Type ............................................... 4-43 Configuring the T1 TDM Interface ..................................................................... 4-43 Configuring Ethernet Interfaces ........................................................................ 4-46 Configuring Routing Parameters ............................................................................ 4-48 Configuring Bundle Connections ............................................................................ 4-49 Configuring the Ethernet Bridge ............................................................................ 4-61 Configuring MAC Table...................................................................................... 4-62 Configuring the Bridge Ports ............................................................................. 4-64 Configuring L2CP Handling ................................................................................ 4-65 Configuring the VLAN Membership .................................................................... 4-66 Configuring Quality of Service (QoS) ..................................................................... 4-68
IPmux-24 Ver. 3.5 iii
Table of Contents
Configuring the Traffic Priority .......................................................................... 4-68 Configuring Rate Limitation .............................................................................. 4-70 4.3 Performing Additional Tasks ..................................................................................... 4-72 Displaying the Inventory ....................................................................................... 4-72 Setting the Date and Time .................................................................................... 4-73 Editing Banner Information ................................................................................... 4-75 Configuring Syslog Parameters .............................................................................. 4-76 Displaying the Status ............................................................................................ 4-77 Displaying the Physical Layer Information ......................................................... 4-78 Displaying the Bundle Connection Information .................................................. 4-79 Displaying the System Clock Information .......................................................... 4-80 Displaying the MAC Address Table .................................................................... 4-81 Displaying List of Connected Managers ............................................................. 4-82 Displaying the RFER Information ....................................................................... 4-82 Displaying the ERP Status ................................................................................. 4-83 Displaying the LAG Status................................................................................. 4-84 Displaying the Dual Homing Status ................................................................... 4-84 Displaying the Bundle Protection Status ........................................................... 4-85 Displaying Service OAM (802.1ag) Status.......................................................... 4-85 Transferring Software and Configuration Files ....................................................... 4-87 TFTP Application ............................................................................................... 4-87 Setting-up a TFTP Server .................................................................................. 4-88 Checking the Firewall Settings .......................................................................... 4-88 Resetting the Unit ................................................................................................ 4-91 Resetting to the Defaults ................................................................................. 4-91 Performing Overall Reset .................................................................................. 4-92 Chapter 5. Monitoring and Diagnostics 5.1 Monitoring Performance ............................................................................................. 5-1 Displaying E1/T1 Statistics ...................................................................................... 5-1 Displaying Ethernet Statistics .................................................................................. 5-6 Displaying Bundle Connection Statistics................................................................... 5-7 Displaying Service OAM (8021ag) Statistics ........................................................... 5-11 Displaying Link OAM (802.3ah) Statistics ............................................................... 5-14 Displaying the ERP Statistics ................................................................................. 5-14 5.2 Detecting Errors ....................................................................................................... 5-16 Power-Up Self-Test ............................................................................................... 5-16 LEDs ..................................................................................................................... 5-17 Alarms and Traps .................................................................................................. 5-17 Statistic Counters ................................................................................................. 5-17 5.3 Handling Events ....................................................................................................... 5-17 Displaying Events .................................................................................................. 5-17 Clearing Events ..................................................................................................... 5-19 Masking Alarm Traps ............................................................................................. 5-21 5.4 Troubleshooting ....................................................................................................... 5-23 5.5 Testing the Unit ....................................................................................................... 5-23 Running Diagnostic Loopbacks .............................................................................. 5-24 External Loopback ............................................................................................ 5-24 Internal Loopback ............................................................................................ 5-24 Activating T1 Inband Loopbacks........................................................................ 5-25 Pinging IP Hosts .................................................................................................... 5-27 Running a Trace Route .......................................................................................... 5-28 Running 802.1ag Tests ......................................................................................... 5-29
iv IPmux-24 Ver. 3.5
Table of Contents
Performing OAM Loopback ............................................................................... 5-29 Performing OAM Link Trace .............................................................................. 5-31 Setting a Permanently Active Bundle ..................................................................... 5-33 5.6 Frequently Asked Questions ..................................................................................... 5-34 5.7 Technical Support .................................................................................................... 5-36 Chapter 6. Software Upgrade 6.1 6.2 6.3 6.4 Compatibility Requirements ........................................................................................ 6-1 Impact ....................................................................................................................... 6-1 Software Upgrade Options ......................................................................................... 6-1 Prerequisites .............................................................................................................. 6-2 Software Files ......................................................................................................... 6-2 System Requirements ............................................................................................. 6-2 6.5 Upgrading Software via the File Utilities Menu ............................................................ 6-2 Verifying the Host Parameters ................................................................................ 6-3 Pinging the PC ........................................................................................................ 6-4 Activating the TFTP Server ....................................................................................... 6-5 Downloading the New Software Release File to the Unit ......................................... 6-5 6.6 Upgrading Software via the Boot Menu ...................................................................... 6-5 Using the XMODEM Protocol ................................................................................... 6-6 Using the TFTP ........................................................................................................ 6-8 Chapter 7. Application Tutorial 7.1 CESoPSN Application .................................................................................................. 7-1 Equipment List ........................................................................................................ 7-1 Installing the Units .................................................................................................. 7-2 Configuring Gmux-2000 .......................................................................................... 7-3 Loading Hardware Configuration ........................................................................ 7-3 Configuring the Host IP Parameters .................................................................... 7-4 Configuring the Manager List .............................................................................. 7-5 Verifying the Master Clock Source ....................................................................... 7-5 Enabling the GbE Module .................................................................................... 7-6 Configuring the E1 Interface ............................................................................... 7-7 Adding and Connecting a Bundle ........................................................................ 7-8 Assigning Timeslots to the Bundle ...................................................................... 7-9 Configuring IPmux-24 ............................................................................................ 7-10 Resetting IPmux-24 to its Defaults ................................................................... 7-10 Configuring the Host IP Parameters .................................................................. 7-10 Configuring the Manager List ............................................................................ 7-11 Configuring the E1 Interface ............................................................................. 7-11 Assigning Timeslots to the Bundle .................................................................... 7-12 Connecting the Bundle ..................................................................................... 7-13 Verifying the Bundle Connection Status ................................................................. 7-14 Testing the Application ......................................................................................... 7-15 Configuring the E1/T1 Traffic Generator ........................................................... 7-15 7.2 Typical Pseudowire Application with Ring Protection ................................................. 7-20 Equipment List ...................................................................................................... 7-20 Installing the Units ................................................................................................ 7-21 Configuration Sequence ........................................................................................ 7-22 Configuring Gmux-2000 ........................................................................................ 7-23 Configuring IPmux-24 ............................................................................................ 7-23 Configuring the Management Host ................................................................... 7-23
IPmux-24 Ver. 3.5
Table of Contents
Setting the TDM Physical Layer Parameters ....................................................... 7-24 Configuring the Pseudowire Host...................................................................... 7-24 Configuring the Bridge...................................................................................... 7-24 Configuring the VLAN Membership .................................................................... 7-25 Enabling the Ring Functionality ......................................................................... 7-25 Configuring the Priority Classification Method ................................................... 7-26 Mapping the 802.1p Priorities to Traffic Classes ............................................... 7-26 Unmasking Ring Status Traps............................................................................ 7-27 Configuring and Connecting the PW Bundles ..................................................... 7-28 Appendix A. Connection Data
vi
IPmux-24 Ver. 3.5
Chapter 1 Introduction
1.1 Overview
IPmux-24 offers a pseudowire (PW) solution for extending traditional E1/T1 services transparently over packet switched networks (PSNs) such as Ethernet, MPLS and IP networks. The device converts the data stream coming from its TDM ports into configurable-sized packets that are encapsulated using one of the PW methods (TDMoIP, CESoPSN, SAToP, HDLCoPSN) and forwarded over Ethernet, MPLS and IP networks. IPmux-24 offers end-to-end synchronization for voice/leased line applications. IPmux-24 also features two Gigabit or Fast Ethernet user ports for connectivity to packet-switched networks. Management is performed locally by a terminal, or remotely via Web, Telnet, or SNMP.
Product Options
Several versions of the unit are available, offering different of TDM port types, different combinations of Ethernet ports, various clock recovery capabilities, and other special features (external clock, alarm relay etc). TDM ports: 1, 2 or 4 E1 or T1 ports Ethernet ports: One SFP- or UTP-based network port One SFP- or UTP-based network/user port One SFP- or UTP-based user port Clock recovery: standard or advanced clock recovery mechanism Carrier-class option: external clock, alarm relay, real-time clock Environmentally hardened option (IPmux-24/H).
Note
The unit can also be ordered with Fast Ethernet interfaces only (IPmux-24/FE).
IPmux-24 Ver. 3.5
Overview
1-1
Applications
Figure 1-1 illustrates an IPmux-24 application in which it provides a 2G/3G cellular
backhaul over an Ethernet ring.
Figure 1-1. 2G/3G Cellular Backhaul over an Ethernet Ring
Features
E1 Interface
The E1 interfaces comply with G.703, G.704, and G.823 standards. They support unframed, framed transmission with or without CAS/CCS. The E1 interfaces can be monitored for alarms and error statistics.
T1 Interface
The T1 interfaces comply with ANSI T1.403, G.703, and G.704 standards. They support unframed, SF, ESF and Robbed Bit signaling. T1 jitter performance is according to G.824 and TR-62411.The T1 interfaces can be monitored for alarms and error statistics. FDL and transmit performance monitoring for T1/ESF are also supported.
1-2
Overview
IPmux-24 Ver. 3.5
Timing
IPmux-24 maintains synchronization between TDM devices by deploying advanced clock recovery mechanisms. Available timing modes are: Loopback (Rx clock) Adaptive Internal clock External clock.
System clock ensures a single clock source for all TDM links. The system clock uses master and fallback timing sources for clock redundancy. IPmux-24 provides system clock output via the external clock connector. The advanced clock recovery mechanism complies with G.823 (clause 6) requirements, providing frequency accuracy of up to 16 ppb. This makes the unit suitable for timing-sensitive applications, such as cellular backhauling.
Packet Networks
IPmux-24 supports transmission over the following packet networks: Ethernet MPLS IP.
Ethernet
The Ethernet ports can be either UTP (10/100BaseT), SFP-based fiber optic (1000BaseX or 100BaseFx), or SFP-based electrical (100/1000/multirate) interfaces. Bridge Modes The following bridge modes are available: Transparent Filtered (VLAN-aware and VLAN-unaware).
Rate Limiting Traffic rate is limited at the ingress of the network and user ports. Frame type (broadcast, multicast or flooded unicast) is user-selectable.
MPLS
IPmux-24 encapsulates PW payload with MPLS labels for transporting it over MPLS networks (TDMoMPLS, CESoMPLS, SATOPoMPLS, HDLCoMPLS). Saving up to 20 bytes of overhead in comparison to the standard PWoIP encapsulation, TDMoMPLS is ideal for bandwidth-sensitive networks.
IPmux-24 Ver. 3.5
Overview
1-3
IP
The data stream coming from the E1 or T1 port is converted into IP packets that are transported over the Gigabit or Fast Ethernet ports, and vice versa. TDM bytes are encapsulated in a UDP frame that runs over IP and over Ethernet. The number of TDM bytes in an IP frame is configurable for throughput/delay tradeoff. Each device has a two IP address (host IP and PW IP); the user can use the same IP address for host and PW traffic. A configurable destination IP address is assigned to the IP packets. IP ToS field support can be configured for IP Level Priority.
Payload Encapsulation
Payload is encapsulated using the following methods: TDMoIP CESoPSN SAToP HDLCoPSN.
TDMoIP
TDMoIP (TDM over IP) payload encapsulation is implemented according to IETF RFC 5087 and ITU-T Y.1413. It uses AAL1 format for constant rate/static allocation of timeslots. The TDMoIP packet size is a multiple of 48 bytes. TDMoIP encapsulation can be used with framed, multiframed or unframed TDM service. It supports FAC1 inband loopback activation.
CESoPSN
CESoPSN (Circuit Emulation Service over PSN) is a structure-aware format for framed E1/T1 services. It converts structured E1/T1 data flows into IP or MPLS packets and vice versa with static assignment of timeslots inside a bundle according to ITU-T Y.1413 and IETF RFC 5086. The CESoPSN packet size is a multiple of TDM frame size.
SAToP
SAToP (Structure Agnostic TDM over Packet) encapsulation method is used to convert unframed E1/T1 data flows into IP or MPLS packets and vice versa according to ITU-T Y.1413 and IETF RFC 4553. It provides flexible packet size configuration and low end-to-end delay.
HDLCoPSN
IPmux-24 also supports HDLCoPSN (HDLCoMPLS, HDLCoIP and HDLCoETH) transmission. This makes IPmux-24 suitable for the following data transfer applications: Port-mode Frame Relay (FRAD) Transparent X.25 (PAD) Transparent PPP (router).
1-4
Overview
IPmux-24 Ver. 3.5
The HDLCoPSN is implemented in IPmux-24 according to the IETF RFC 4618 (excluding clause 5.3 PPP) and RFC 5087. The HDLC uses bit stuffing to ensure the bits stream continuity. The HDLC frames include the 16-bit FCS for the frame validity check.
QoS
QoS supports: Labeling IP level priority (ToS/Diffserv) for PW packets VLAN tagging and priority labeling according to IEEE 802.1p&Q for PW packets Using EXP bits for QoS marking of the PW traffic in MPLS networks.
The user can configure the ToS (Type of Service) of the outgoing TDMoIP packets. This allows an en-route Layer 3 router or switch, which supports ToS, to give higher priority to IPmux-24 TDMoIP traffic for delay-sensitive and secure applications. IPmux-24 allows you to configure the WHOLE ToS byte field, since different vendors may use different bits to tag packets for traffic prioritization. This also enables operation according to various RFC definitions (for example RFC 2474, RFC 791). The user can also configure VLAN priority bits for Level 2 priority.
Ring Topology
Ethernet ring are used to protect data against link and node failures. IPmux-24 supports two ring mechanisms: Proprietary RFER (Resilient Fast Ethernet Ring) Standard, according to the IEEE 8032 requirements.
Proprietary Ethernet Ring

The proprietary ring is used to protect the transmission path, when data propagates over two alternative paths (clockwise or counterclockwise). To comply with the Ethernet protocol characteristics, an arbitrary pair of adjacent nodes on the ring keep the ring open by disconnecting a ring segment, thereby preventing frames from making a full round trip. If a segment breaks (fails), the redundancy mechanism automatically moves the blocking nodes to the ends of the failed segment and reconnects the previously disconnected segment. Therefore, full connectivity is restored for any single point of failure. For pseudowire traffic and other user-specified traffic, this change takes effect within 50 msec. A single ring may include up to 16 IPmux-24 devices and up to 16 VLAN plus an additional VLAN for management traffic.
G.8032 Ethernet Ring

A G.8032 Layer-2 Ethernet ring is a logical ring, defined as a set of IEEE 802.1 compliant bridges and protect against link and node failures. To achieve this, every node in the ring has two bridge ports connected it to adjacent nodes. The ring itself is constructed independently of the transport technology used at a server layer. Failures in the ring detected by using Ethernet OAM (Y.1731) continuity check (CC) messages between adjacent nodes.
IPmux-24 Ver. 3.5
Overview
1-5
Ethernet Link Protection

The unit supports link aggregation (LAG) based on 802.3ad requirements. Dual homing technology (1:1) allows IPmux-24 to be connected to two different upstream devices.
Ethernet OAM
IPmux-24 provides OAM to monitor and troubleshoot the Ethernet network and quickly detect failures. Two OAM types are provided: OAM Connectivity Fault Management (CFM) based on IEEE 802.1ag and Y.1731 to enable Ethernet service providers to monitor their services proactively, measure end-to-end performance, and guarantee that the customers receive the contracted SLA. Fault monitoring and performance measurement include Frame Delay, Frame Delay Variation, Frame Loss, and Frame Availability Link OAM according to IEEE 802.3ah for fault indication and loopback activation response.
Management
IPmux-24 can be managed locally by connecting an ASCII terminal to the RS-232 port on the rear panel, or via an HTTP connection (Web-based management tool), Telnet or SNMP. The SNMP management capability enables fully graphical, user-friendly management using the RADview Service Center TDMoIP network management stations offered by RAD, as well as management by other SNMP-based management systems.
Web Terminal
A Web-based terminal management system for remote device configuration and maintenance is embedded into IPmux-24 and provided at no extra cost. The application can be run from any standard Web browser.
RADview-SC/TDMoIP
The RADview Service Center and Element Manager packages control and monitor pseudowire devices and circuits. The Service Centers intuitive GUI, point-and-click functionality and easy-to-follow wizards increase the efficiency and accuracy of the service provisioning process.
Environment
IPmux-24/H is an environmentally hardened version intended for street-cabinet and cellular-tower installations.
1-6
Overview
IPmux-24 Ver. 3.5
1.2
Physical Description
IPmux-24 is a compact, easy-to-install standalone unit. Figure 1-2 shows a 3D view of an IPmux-24 unit.
Figure 1-2. IPmux-24 3D View

The front panel includes the LEDs. For the detailed LED description, see Chapter 3. User, network, external clock and management ports, and the power supply connectors are located on the rear panel of the unit. For further details, see Chapter 2.
1.3
Functional Description
IPmux-24 provides TDM connectivity across the Ethernet, MPLS or IP network. A single bundle (group of timeslots) can be transmitted in a TDM pseudowire (PW) to a predefined far-end bundle. IPmux-24 includes one, two or four E1 or T1 ports. Traffic is transmitted over the network as E1/T1 or fractional E1/T1, using the TDMoIP, CESoPSN, SAToP or HDLCoPSN method. IPmux-24 supports two Ethernet user ports for user LAN connectivity. Configuration and management are provided via the IPmux-24 local terminal, Web-based management utility, Telnet or RADview management tool (SNMP).
IPmux-24 Ver. 3.5
1-7
Service Type
This section describes the IPmux-24 operation modes, which are: Unframed E1/T1 Fractional E1/T1 Fractional E1/T1 with CAS HDLC.
Unframed
In the unframed mode, the incoming bit stream from each channel (regardless of framing) is converted into IP over Ethernet frames. This option provides clear channel end-to-end service (unframed).
Fractional
In the fractional mode, the incoming bit stream is regarded as a sequence of n64 kbps timeslots (according to framing). Each predefined group of timeslots is converted into a structure block. The structure block is packetized into IP frames and transmitted. This mode allows transmission of several selected timeslots without the whole E1 or T1 frame, as in transparent mode.
Fractional with CAS

In the fractional-with-CAS mode, the structure block (as described under Fractional Operation Modes, above) also includes Channel Associated Signaling (CAS) from timeslot 16 (E1) or robbed bit (T1). The relevant portion of the signaling channel is packetized and sent to the destination.
HDLC
Handling HDLC in TDMoIP ensures efficient transport of CCS (common channel signaling, such as SS7), embedded in the TDM stream or other HDLC-based traffic, such as Frame Relay.
Timeslot Assignment in a Bundle

A pseudowire (PW) bundle is a group of timeslots associated with a specific E1 or T1 channel. IPmux-24 places individual or multiple TDM timeslots (up to 31 timeslots for E1 or up to 24 for T1) into PWs with a single IP address destination. IPmux-24 supports up to 64 PW bundle connections (16 bundles per TDM link).
1-8
IPmux-24 Ver. 3.5
Testing
Diagnostic capabilities include E1/T1 local and remote loopback tests for rapid localization of faults. The E1/T1 traffic can be looped locally, toward the line, or toward the remote end (see Chapter 5 for more information).
Timing Modes
IPmux-24 supports different timing modes to provide maximum flexibility for connecting the IPmux-24 E1, T1 ports. Each of the clocks must be configured correctly on both the receive and transmit ends to ensure proper operation and prevent pattern slips (see Figure 1-3, Figure 1-4 and Figure 1-5).
E1/T1 Timing
Synchronization between TDM devices is maintained by deploying advanced clock distribution mechanisms. The clocking options are: Loopback timing the E1/T1 Tx clock is derived from the E1/T1 receive (Rx) clock Adaptive timing the E1/T1 Tx clock is regenerated from the network packet flow and calculated according to arrival time of the incoming packets Internal timing the Tx clock is derived from an internal oscillator External timing the Tx clock is derived from the external clock input. The external clock port also outputs the input clock signal to allow connection to other units, if needed.
Note
In adaptive timing, the regenerated clock is subject to network packet delay
variation. That is why the quality of the adaptive clock depends on the quality of the network.
A special option of the device (IPmux-24/A), with an advanced clock recovery
mechanism, can be used in cellular backhaul applications.
System Timing
The IPmux-24 TDM links can be configured to use system clock, synchronized to internal, loopback, external or adaptive timing source. The system clock has master and fallback sources. If a fallback clock source fails, IPmux-24 switches to internal timing.
Network Timing Schemes

The following paragraphs describe typical timing schemes and the correct timing mode settings for achieving end-to-end synchronization.
IPmux-24 Ver. 3.5
1-9
External Network Timing

When the edges of the network are synchronized by an external network clock source, all the IPmux-24 units should be configured to work in loopback timing mode (see Figure 1-3). This topology enables any-to-any connectivity.
Figure 1-3. IPmux-24 in Loopback Timing Mode

External timing from the network can also be issued to IPmux-24 by external clock input.
Figure 1-4. IPmux-24 in External Clock Mode
1-10
IPmux-24 Ver. 3.5
Adaptive Timing
When a common clock is not available on all the ends of the network, one of the IPmux-24 devices is configured to work in loopback timing, while the other IPmux-24 device is configured to work in adaptive timing (see Figure 1-5).
Figure 1-5. IPmux-24 in Adaptive Timing Mode

In leased line applications, the carrier does not know which side provides the source clock. To ensure correct clock distribution, IPmux-24 units working opposite each other can be both configured to adaptive clock.
Note
As the clock is recovered twice, it is more sensitive to interferences introduced by the network.
Figure 1-6. IPmux-24 in Adaptive-Adaptive Timing Mode
Frame Format
Network encapsulation method depends on packet-switched network type (IP, MPLS or Ethernet/MAC) and pseudowire standard (TDMoIP, CESoPSN, SAToP or HDLCoPSN).
UDP/IP Encapsulation (MPLS and IP Networks)

The Ethernet frame sent by IPmux-24 is a UDP datagram that transfers E1/T1 payload bytes over IP over Ethernet (UDP payload + UDP header + IP header + Ethernet header). The UDP payload is equal to TDM bytes per frame (TDM bytes/frame configuration). Table 1-1 specifies the structure of the different headers, special fields, and the payload in the Ethernet packet. MAC ETH Type VLAN ETH Type IP Header UDP Header CW Data CRC
Figure 1-7. UDP/IP Frame Structure
IPmux-24 Ver. 3.5
1-11
Table 1-1. UDP/IP Frame Structure

Field Length (Bytes) 7 Field Preamble SFD Destination MAC Address Source MAC Address Type 0x800 Vers/HLEN Service Type Total Length Identification Flags/Fragment Offset (most) Fragment Offset (least) Time to Live Protocol Header Checksum Source IP Address Destination IP Address UDP Source Port UDP Destination Port UDP Message Length UDP Checksum PW Control Word Data CRC The UDP source port field is used to transfer a destination bundle number. See Note below.
ETH Layer
1 6 6
LLC Layer
2 1 1 2 2 1
Note: IEEE 802.1p&Q VLAN tagging (additional 4 bytes if enabled), 0x8100.
IP Layer
1 1 1 2 4 4 2
UDP Layer
2 2 2 4
Data Layer ETH Layer
... 4
1-12
IPmux-24 Ver. 3.5
Note
The UDP Source Port value calculation depends on the selected TDMoIP version (1 or 2):
TDMoIP version 2: The UDP Source Port value equals 0x2000 + Destination
Bundle Number, it is always greater than 8192.

TDMoIP version 1:
During normal operation the UDP Source Port value equals Destination Bundle Number + 1 (for example, for bundle 1 the UDP Source Port equals 2). The allowed range for the UDP Source Port values in the normal state is from 0 to 8191. If a bundle is in the local fail state, the MSB of the UDP Source Port is set to 1 to indicate the local fail state to the remote equipment. In this case the UDP Source Port value equals 0x8000 + Destination Bundle Number + 1. The UDP Source Port value in the local fail state is always greater than 32768.
VLAN Support
VLAN, according to IEEE 802.1p&Q, adds four bytes to the MAC layer of the Ethernet frame. The user can set the contents of these bytes, MAC layer priority and VLAN ID. In this mode, only VLAN format frames are sent and received by IPmux-24. Figure 1-8 shows the VLAN tag format.
81
00
CFI = 0
user_priority
VID
802.1D Tag Protocol Type
Priority
VLAN ID
Figure 1-8. VLAN Tag Format (802.1p&Q)
UDP Support
Table 1-2. UDP Ports Definition
Field Length (Bits) 2 bytes 2 bytes Field Description UDP Source Port UDP Destination Port Value 2497d* 2142d Function Destination bundle Standard TDMoIP UDP port
* The MSB of this field can be either 1 or 0 for inband end-to-end proprietary signaling.
Note
The UDP Source Port field is used for destination bundle indication.
For more information about VLAN tagging, refer to IEEE standard 802.1p&Q.
IPmux-24 Ver. 3.5
1-13
MPLS Encapsulation (Ethernet and MPLS Networks)

Figure 1-15 and Table 1-3 illustrate MPLS frame structure.
MAC ETH Type VLAN ETH Type MPLS PW Label MPLS Tunnel Label CW Data CRC
Figure 1-9. MPLS Frame Structure Table 1-3. MPLS Frame Structure
Field Length (Bytes) 7 Field Preamble SFD Destination MAC Address Source MAC Address Type 0x8847 MPSL PW label EXP Stacking bit TTL Inner label EXP Stacking bit TTL PW Control Word Data CRC The inner label field is used to transfer a destination bundle number.
ETH Layer
1 6 6
LLC Layer
2 20 3 1
MPLS Layer (Bits)
8 20 3 1 8 4
... 4
1-14
IPmux-24 Ver. 3.5
Ethernet (MEF 8) Encapsulation

Table 1-4. Ethernet Frame Structure
Field Length (Bytes) 7 Field Preamble SFD Destination MAC Address Source MAC Address Type 0x88d8 ECID 0x102 PW Control Word Data CRC
MAC Layer
1 6 6
LLC Layer ECID Layer
2 20 13 4
... 4
MAC
ETH Type
VLAN
ETH Type
ECID
CW
Data
CRC
Figure 1-10. Ethernet Frame Structure
Payload Encapsulation
IPmux-24 supports the following payload encapsulation techniques: AAL1, CESoPSN and SAToP.
IPmux-24 Ver. 3.5
1-15
TDM Payload (Voice/CAS)
SN
CRC
47-Octet Payload
Non P-Format AAL1 Cell
OR
SN
CRC
P E
Pointer
46-Octet Payload
P-Format AAL1 CELL (Structured Bundles only)
L2/L3 Header
Control Word
TDMoIP Payload up to 30 AAL1 Cells
CRC
Ethernet Packet
Figure 1-11. TDMoIP CE Encapsulation
L2/L3 Header
Control Word
FRG bits = 00 (no fragmentation)
TDM Payload
CRC
Ethernet Packet
TDM Bitstream N TDM Bytes

Figure 1-12. SAToP Encapsulation
1-16
IPmux-24 Ver. 3.5
TDM Payload L2/L3 Header Control Word
4 25 4 25
4 25
CRC
Ethernet Packet
FRG bits = 00 (no fragmentation)
Frame 1
Frame 2
Frame N
4 Frame 1
25
4 Frame 2
25
4 Frame N
25
Figure 1-13. CESoPSN Encapsulation (E1, Bundle with Timeslots 4 and 25)
HDLC Frame in TDM
Flags
Data
CRC-16
Flags
Zero Bit Deletion
L2/L3 Header
Control Word
HDLC Type TDMoIP Payload
CRC
Ethernet Packet
Figure 1-14. HDLCoPSN Encapsulation
Packet Delay Variation

TDMoIP packets are transmitted by IPmux-24 at a constant rate towards the PSN (Packet-Switched Network). Packet Delay Variation is the deviation from the nominal time the packets are expected to arrive at the far end device. IPmux-24 has a jitter buffer that compensates for the deviation from the expected packet arrival time to ensure that the TDM traffic is sent to the TDM device at a constant rate. The jitter buffer needs to be configured to compensate for the jitter level introduced by the PSN. If the PSN jitter level exceeds the configured jitter buffer size, underflow/overflow conditions occur, resulting in errors at the TDM side.
Packets Leaving IPmux-24 t
Packets Arriving
PDV
Figure 1-15. Packet Delay Variation
IPmux-24 Ver. 3.5
1-17
PDVT (Jitter) Buffer

IPmux-24 is equipped with a Packet DVT (Delay Variation Tolerance) buffer. The PDVT buffer or jitter buffer is filled by the incoming packets and emptied out to fill the TDM stream. A jitter buffer overrun usually occurs when IPmux-24 loses its clock synchronization A jitter buffer underrun occurs when no packets are received for more than the configured jitter buffer size, or immediately after an overrun.
When the first packet is received, or immediately after an underrun, the buffer is automatically filled with conditioning pattern up to the PDVT level in order to compensate for the underrun. Then, IPmux-24 processes the packet (packetization delay) and starts to empty out the jitter buffer to the TDM side. See Figure 1-16 for the illustration of the PDVT buffer operation. The PDVT (jitter) buffer is designed to compensate for network delay variation of up to 180 msec. Packets arriving from the PSN side are stored in the jitter buffer before being transmitted to the TDM side, adding a delay to the TDM traffic. The delay time equals to the PDVT size configured by the user.
PDVT Buffer + Packet Creation Time Normal Operation (No PDV) PDVT (Jitter) Buffer Depth Maximum Jitter Buffer Size (2 PDVT + 2 PCT + 1 msec)
Figure 1-16. Jitter Buffer Operation

The maximum jitter buffer size is 2 PDVT + PCT + 1 msec.
Packet Creation Time (PCT)

When IPmux-24 builds a frame, a packetization delay is introduced. The packet creation time is different for the different payload encapsulation methods. It is calculated according to the following formulas:
TDMoIP
PCT (ms) = Where: N=
47 N 0.125 TS
TDM bytes/frame 48
TS = number of assigned timeslots (in unframed mode= 32 for E1, 24 for T1)
1-18
IPmux-24 Ver. 3.5
Note
For a bundle that contains a few timeslots (i.e. 1 to 3), the recommended number of TDM bytes/frame is 48 in order to prevent excessive PCT.
CESoPSN
PCT (ms) = N 0.125 Where: N = Number of TDM frames in packet
SAToP
PCT (ms) =
N 0.125 TS
N Number of TDM bytes in packet TS Number of timeslots in one frame (32 for E1 or 24 for T1)
Round Trip Delay

The voice path round-trip delay is a function of all connections and network parameters. (2 msec) RT Delay(msec) = 2 (PCT + Jitter Buffer Level) + network round trip delay
Ethernet Throughput
Increasing payload size reduces the ratio between the TDMoIP/IP/Ethernet header segment in the packet and the payload, thus reducing the total Ethernet throughput. On the other hand, packetization delay is increased; this contributes to a higher end-to-end delay. This effect can be small and negligible when a full E1 (or many timeslots) are transferred, but can be very significant when few timeslots are transferred. Configuring the TDM bytes per frame (TDM bytes/frame) parameter has impact on the Ethernet throughput (bandwidth or traffic traveling through the Ethernet). This parameter controls the number of TDM bytes encapsulated in one frame. The TDM bytes/frame parameter can be configured to N 48 bytes where N is an integer between 1 and 30. To calculate Ethernet throughput as a function of TDM bytes/frame: Ethernet load (bps) = [(frame overhead (bytes) + TDM bytes/frame) 8] frames/second Frame overhead without VLAN (IP) = Ethernet overhead + IP overhead = 46 bytes Frame overhead (MPLS) = Control Word + MPLS overhead + Ethernet overhead = 22 bytes
IPmux-24 Ver. 3.5
1-19
Note
The frame overhead does not include:

Preamble field: 7 bytes SFD field: 1 byte Interframe gap: 12 bytes VLAN field (when used): 4 bytes. Frame/second = Unframed: Framed:
5447/n for a full E1 4107/n for a full T1 8000 k/(46.875 n)
Where k = number of assigned timeslots Where n =
TDM bytes/frame 48
The maximum Ethernet throughput is calculated by:
( VLAN + CW + frame overhead + payload) 8 bits
1444444 24444444 4 3
frame size (in bytes)
1 PCT
Where: VLAN is an optional field: if enabled it adds 4 bytes to the frame overhead CW = control word (4 bytes) payload = number of TDM bytes in frame, (48, 96, 144, 192, 1440) frame overhead = size of 46 bytes, include MAC, LLC, IP and UDP layer
The result is in bits per second (bps).
Pseudowire OAM
OAM connectivity is used to detect a valid connection (the remote IPmux will confirm it recognizes the connection and that it is enabled). It prevents flooding by a handshake. The control packets are run over a unique bundle number that is used for this purpose. The control packets have the same packet overhead as the traffic. The control packet uses the TDMoIP UDP number. OAM connectivity can be enabled or disabled.
Note
For control packets, the UDP checksum is neither calculated nor checked.
End-to-End Alarm Generation

An end-to-end alarm generation mechanism exists in IPmux-24 to facilitate the following alarms: Unframed AIS is transmitted toward the near-end PBX in event of far-end LOS, AIS Framed Timeslot/CAS configurable alarm pattern is transmitted toward the near-end PBX in event of far-end LOS, LOF, AIS.
1-20
IPmux-24 Ver. 3.5
Trail-Extended Mode
To enhance fault condition reporting capabilities, remote IPmux-24 transfers RDI, LOS, LOF and AIS conditions received from the remote E1 device to the local E1 device (see Figure 1-17).
Figure 1-17. Fault Indication Transfer

IPmux-24 transfers fault conditions only if the payload format is configured to V2. The fault conditions are transferred as follows: Framed E1 or T1: RDI as RDI, LOS, LOF and AIS as AIS Unframed E1 or T1: LOS, LOF and AIS as AIS.
Note
The trail extension can be activated only when IPmux-24 has one bundle per port.
VLAN Traffic Behavior

Table 1-5 lists the IP and VLAN validity checks that are performed with each Ethernet packet that is received by IPmux-24. Table 1-5. VLAN Check for Packets that are Received by IPmux-24
Packet Type Management TDM over IP Receiving Ping ARP Source IP Check Performed Performed Not performed Not performed VLAN Check Performed Performed in the VLAN-aware mode Not performed, even if it is one of the IPs that is configured for the manager or for the connection Performed only when Telnet access mark is from manager
Telnet
Performed only when Telnet access mark is from manager
Table 1-6 lists the IP and VLAN validity checks that are performed with each
Ethernet packet that is sent by IPmux-24.
IPmux-24 Ver. 3.5
1-21
Table 1-6. VLAN Check for Packets Sent by IPmux-24

Packet Type Management TDM over IP Answer to Ping VLAN Support As configured for the manager As configured for the connection Packet with VLAN tagging: IPmux-24 replies with the same VLAN ID (even if it is one of IPs configured for the manager or for the connection). Packet without VLAN tagging: if it is one of the IPs configured for the manager or for the connection, the IPmux-24 replies with the VLAN ID that is in the manager or connection configuration. ARP initiated by IPmux-24 Telnet Ping initiated by IPmux-24 No VLAN value unless it is to one of the managers or the connections IP address
Bridge
The bridge operates in the VLAN-aware and VLAN-unaware modes. In the VLAN-aware mode, the bridge supports up to 64 VLANs. Learning and filtering can be enabled or disabled. Static MAC addresses are stored in the MAC table. The size of the MAC table is 8128 addresses. The bridge can handle frames of up to 1632 bytes. The unit can append additional VLAN tag (provider VLAN) at the user port ingress and remove it at the network port ingress. The provider VLAN includes provider VID and priority (VLAN stacking).
Multiple Hosts
IPmux-24 includes three different hosts: Management host for handling the management traffic Two PW hosts for handling the pseudowire traffic. Redundant PW host is used for bundle redundancy.
Each host has a separate MAC address. As the unit provides one default gateway, the user can also specify static routes to enhance the IP routing capabilities of the management and pseudowire traffic.
Proprietary Ethernet Ring

Ring topology, implemented by means of the RAD-proprietary protocol (RFER), provides protection for the Ethernet transmission path, and is especially suited for MAN and dark fiber applications. When the ring is enabled, the data is propagated between the nodes either clockwise or counterclockwise. Because of the Ethernet protocol characteristics, actually the ring cannot be closed: a pair of adjacent nodes on the
1-22
IPmux-24 Ver. 3.5
ring keep the ring open by disconnecting an arbitrary ring segment, thereby preventing frames from making a full round trip.
Figure 1-18 shows a basic ring topology; the arrow shows the path followed by
frames exchanged between ring nodes A and D during normal operation, assuming that the blocked segment is between nodes A and D.
Figure 1-18. Basic Ring Redundancy Topology Data Flow during Normal Operation
If a segment, for example, the segment between nodes B and C, breaks (fails), the ring mechanism automatically moves the blocking nodes to the ends of the failed segment and reconnects the previously disconnected segment. The new path of the frames is shown in Figure 1-19. Therefore, full connectivity is restored for any single point of failure. For PW traffic, the redundancy mechanism ensures that this change takes effect within 50 msec.
Figure 1-19. Basic Ring Redundancy Topology Data Flow after Recovery from Segment Failure
The method used to achieve fast recovery is based on the use of VLAN tagging. This approach enables adjacent nodes on the ring to exchange protocol messages that check the connectivity, and multicast ring open messages to all the nodes in case a fault is detected on a segment. Note however that this means the ring VLAN ID cannot be used for other traffic. Two VLANs are used by the ring mechanism: one for the multicast messages (Ring Reject, Ring Open) and one for unicast messages (Link KeepAlive, Ring Detect, Ring Closed).
Note
VLANs reserved for the ring messages cannot be used for other traffic.
IPmux-24 Ver. 3.5
1-23
The fast redundancy protection available to the PW traffic within the ring can be extended to other equipment: such equipment is connected to the USER port of the IPmux-24 devices, and therefore its traffic is not processed by IPmux-24: it only passes to the network through the IPmux-24 network ports. The protected addresses are destination addresses for traffic connected to IPmux-24 through the user port: this may be traffic from another IPmux-24 device, or from any other type of equipment using IPmux-24 to connect to remote sites.
Note
Ring topology is configured via an ASCII terminal. SNMP management stations display only ring status information.
G.8032 Ethernet Ring Protection (ERP)

G.8032 revertive rings provide sub-50 ms protection for Ethernet traffic and prevent loops at the Ethernet layer. The rings are built around a specific link, referred to as Ring Protection Link (RPL), which is used to protect the whole ring. RPL is controlled by a single node called an RPL Owner. It uses R-APS messages to detect failures in the ring and coordinate the activities of enabling/disabling the RPL link. In addition, the following timers exist: Wait-to-Restore (WTR) Period of time used by RPL Owner to verify that the ring has stabilized before blocking the RPL after signal recovery. Guard Period of time during which all received A-RPS messages are ignored by the ERP mechanism. This prevents the ring nodes from receiving outdated A-RPS messages circulating the network. Hold-off Period of time during which the underlying Ethernet layer attempts to filter out intermittent link faults before reporting them to the ERP mechanism.
Ethernet OAM (Y.1731) Continuity Check (CC) can be used for additional monitoring of the ring links. If no failure is detected, the RPL is blocked. When the ring fails, the RPL owner unblocks traffic over the RPL. When the failure clears, the WTR timer starts running in the RPL owner. When this timer expires, the revertive protection switching of the APS mechanism blocks traffic over the RPL and unblocks traffic on the link on which the failure is cleared. There are up to 16 nodes on the ring. Figure 1-20 illustrates mobile backhaul application, in which Ethernet traffic is protected by the ERP technology.
1-24
IPmux-24 Ver. 3.5
Figure 1-20. G.8032 Ethernet Ring
Ethernet Port Protection

The network and network/user ports can be configured to operate either independently, as two separate Ethernet interfaces, or used as a single Ethernet interface with line redundancy. Link aggregation mode in accordance with IEEE 802.3ad (without LACP). This mode inherently provides redundancy: if one of the Ethernet ports fails, the traffic is transmitted on the other. Dual homing mode. In this mode, at any time only one of the ports is actively carrying traffic. With the dual homing redundancy, the recovery mode (revertive or non-revertive), and the restoration time in the revertive mode, can be selected in accordance with the application requirements.
Link Aggregation
The network and network/user ports can be operated as a single logical interface, using link aggregation in accordance with IEEE 802.3ad without LACP (Link Aggregation Control Protocol). In the virtual link group only one link transmits at a time. If a failure occurs on the transmitting link, IPmux-24 switches to the standby link in the group. The flip is performed by reassigning destination ports. With link aggregation, the two Ethernet ports serve as a single logical interface. The two ports must be connected to the same switch/router, as shown in Figure 1-21.
IPmux-24 Ver. 3.5
1-25
Figure 1-21. Link Aggregation Redundancy Mode

Using link aggregation inherently provides redundancy, because that if one of the ports fails, the other can continue transferring traffic. Therefore, link aggregation per IEEE 802.3ad has inherent APS (Automatic Protection Switching) characteristics. Failure of one the links is detected by sensing the loss of valid signals at a port, in which case the whole traffic is sent through the remaining port. The switching time is less than 50 milliseconds. The Layer-2 equipment connected to the Ethernet ports must use signal loss as switching criteria for redundancy. As the two Ethernet ports serve as a single logical interface, the learning tables do not change as a result of the interface flip.
Dual Homing
As an alternative to link aggregation, the two IPmux-24 Ethernet ports can be configured for dual homing (1:1 redundancy) mode. With this mode, two topologies can be used: Connection of both Ethernet ports to the same switch/router, as shown in Figure 1-21. Connection of the Ethernet ports to different switch/routers, as shown in Figure 1-22. The main advantage of this topology is its higher availability, because each port can be routed along a different path through the network.
Note
In 1:1 redundancy mode IPmux-24 detects failures only between its network port and edge switches.
Figure 1-22. Dual Homing Redundancy Mode

With dual homing mode, at any time only one of the ports is actively carrying traffic, and the other port serves as the backup port. A RAD proprietary redundancy algorithm, based on loss of Ethernet signal, is used to detect line failure. The flipping time depends on the network relearning time or aging. The recovery mode after a protection switching can be selected in accordance with the application requirements:
1-26
IPmux-24 Ver. 3.5
Non-revertive mode IPmux-24 does not automatically flip back after the failed port returns to normal operation, but only when the currently used port fails, or after a manual flip command. Revertive mode IPmux-24 flips back to the original port when it returns to normal operation. Flipping back can be delayed by specifying a restoration time, during which alarms are ignored. As a result, IPmux-24 starts evaluating the criteria for protection switching (flipping) only after the restoration time expires, thereby ensuring that another flip cannot occur before the specified time expires.
When the dual homing is enabled, shutdown duration upon flip parameters defines period of time during which the failed link suspends its transmission in order to inform the remote device of the link failure Also one of the redundant ports can be configured to be permanently active irrespective of the other port status.
Bundle Redundancy
IPmux-24 features a bundle redundancy capability. This feature enables the user to backup the pseudowire traffic in case of fault at the bundle connection level. This feature permits the user to set a different path for the primary bundle and for the secondary bundle (different packet-switched networks, different links, different TDM pseudowire gateways, etc) and thus rely on two routes, which are not influenced by the same faulty PSN conditions. Both bundles can be routed to the same or different destinations, as illustrated below.
Figure 1-23. Bundle Redundancy Application (A)
Figure 1-24. Bundle Redundancy Application (B)

The recovery mode and wait-to-restore time are user-configurable for 1+1 redundancy. There are two modes of bundle redundancy: 1+1 Both the primary and secondary bundles transmit pseudowire traffic, but only the active bundle receives pseudowire traffic, while the redundant bundle ignores the Rx path. This mode results in minimum recovery time between the bundles whenever switch/flip occurs, but on the other hand increases the total throughput. 1:1 Only one bundle transmits and receives pseudowire traffic while the secondary bundle is kept on hold. This mode does not affect the throughput,
IPmux-24 Ver. 3.5
1-27
however, it increases the recovery time of the system in case switch/flip occurs (depends on the network elements involved in the application). In 1:1 mode, the active and redundant paths are monitored continuously to detect failure and initiate the flip/switch using OAM keep-alive messages. In the 1:1 redundancy with two remote devices (Figure 1-24), the bundles in the remote units operate in the mate mode. In this mode each device monitors traffic activity on a mate bundle and transfers data only when the other bundle is inactive.
Ethernet Service OAM (IEEE 802.1ag, ITU-T Y.1731)

Ethernet Service OAM is a set of functions for managing Ethernet services as specified by the IEEE 802.1ag and ITU-T Y.1731 standards. It allows service providers to operate, administer, and maintain Ethernet services. The Connectivity Fault Management (CFM) uses an end-to-end Ethernet layer OAM protocol for proactive connectivity monitoring, fault verification, and fault isolation. These actions are performed using IEEE 802.1ag standard Layer 2 ping, Layer 2 traceroute, and end-to-end connectivity check of Ethernet networks.
Maintenance Domains
Ethernet service OAM defines a hierarchy of up to eight OAM levels or maintenance domains (MDs), allowing users, service providers and operators to run independent OAMs at their own level. By default, users are allocated three levels, service providers two levels, and operators three levels. OAM frames belonging to higher levels are transparently forwarded by lower level devices (e.g. user OAM frames are forwarded by service provider switches). Larger domains are assigned higher levels.
Maintenance Entities
Y.1731 defines a maintenance entity (ME) that requires management. Some examples of these entities are the entire Ethernet network between two customer switches, or the Ethernet network in the administrative domain of a single service provider, or even a single Ethernet link. Thus MEs can be nested, with link MEs internal to service provider, and MEs of successive providers internal to the customer end-to-end ME. In order to capture the multipoint-to-multipoint nature of Ethernet, MEs are grouped into ME groups (MEGs, referred to as Maintenance Associations or MAs in IEEE language). A multipoint-to-multipoint Ethernet network with N end-points has N (N-1)/2 MEs, while a point-to-point connection has only one. In order to enable detection of incorrect connectivity, each MEG is given a unique ID, and OAM messages specify the MEG ID for which the message is intended.
MEG Endpoints
At the ends of managed entities we find MEG End Points (MEPs), which are the functions that generate and process OAM frames to monitor and maintain the ME. There may also be MEG Intermediate Points (MIPs) that can respond to OAM messages, but cannot originate them. For point-to-point MEGs, a MEP has a single peer MEP, but in between there may be many MIPs. Hence a MEP can send
1-28
IPmux-24 Ver. 3.5
CC messages to its peer MEP, or direct non-intrusive LB messages towards the peer MEP or to any MIP. It is the responsibility of the MEP to prevent OAM messages from leaking out of the administrative domain to which they belong, or entering another domain. However, MEPs transparently pass OAM frames from other domains when they belong to a higher OAM level, thus enabling end-to-end management of customer connectivity (see Figure 1-25).
Figure 1-25. Service OAM MEPs and MIPs
Connectivity Fault Management Protocols

Ethernet CFM comprises three protocols that work together to help administrators debug Ethernet networks. These are: continuity check, link trace and loopback protocols. Continuity Check "heartbeat" messages issued periodically by maintenance endpoints. They allow maintenance endpoints to detect loss of service connectivity amongst themselves. They also allow maintenance endpoints to discover other maintenance endpoints within a domain, and allow maintenance intermediate points to discover maintenance endpoints. Once enabled, a MEP sends a CC messages periodically at one of the following transmission periods: 100 msec, 1 sec, 10 sec, 1 min, 10 min.
IPmux-24 Ver. 3.5
1-29
MIPs transfer CC messages transparently. In addition to detecting loss of continuity, CC messages also perform various other defect and performance monitoring activities, such as the discovery of other MEPs (by sending a CC to a multicast address), detection of unwanted connectivity between MEPs, and RDI. Link Trace messages are transmitted by a maintenance endpoint on the request of the administrator to track the path (hop-by-hop) to a destination maintenance endpoint. They allow the transmitting node to discover vital connectivity data about the path. Link trace is similar in concept to UDP traceroute. Loopback Messages are transmitted by an MEP upon demand by the administrator to verify bidirectional connectivity to a particular MIP or MEP. Similar to ping messages, LBs are sent upon demand and thus may be sent once, repetitively, or according to any other scheme dictated by the initiator. LB messages can be unicast to the MAC address of the desired entity, or multicast to all peer MEPs in the MEG. The unicast version infers connectivity by timely receipt of an LB response message, while the multicast version produces a list of MEPs with which connectivity was detected. LB messages may optionally carry test patterns, the length and content of which may be configured according to need.
Link OAM (IEEE 802.3ah)

Link-level Ethernet OAM is specified by IEEE 802.3ah and can be implemented on any full-duplex point-to-point or emulated point-to-point Ethernet link. Link-layer OAM messages are sent in untagged slow protocol frames called OAM Protocol Data Units, or OAMPDUs. They cannot propagate beyond a single hop within an Ethernet network and have modest bandwidth requirements (frame transmission rate is limited to a maximum of 10 frames per second).
Figure 1-26. 802.3ah OAM

IEEE link-layer OAM operates purely at the Ethernet layer, and so (unlike SNMP or ping) does not require an IP address. This means that Ethernet service providers dont need to run IP protocols or manage IP addresses. Furthermore, special Ethernet features may be directly supported, such as Ethernet multicast and slow protocol frames. When an OAM frame is received by an OAM-enabled Ethernet MAC, it is passed to the OAM client for processing; such a frame is simply discarded if received by a MAC that does not support link-layer OAM. In any case, link-layer OAM frames are never forwarded. Since the IEEE link-layer OAM is generally used over a link between a service provider and a customer, it defines two modes for OAM entities: active or passive. The elements of the provider network (e.g. DSLAMs or provider Ethernet switches) operate in active mode, and can exert control over the passive-mode devices (e.g. DSL modems or customer premises switches). Thus, the active-mode entity can send an LB command forcing the passive-mode device into loopback
1-30
IPmux-24 Ver. 3.5
mode, and query the configuration parameters of the passive-mode device. However, the reverse is not possible. The OAMPDUs perform the following functions: Autodiscovery, heartbeat, and fault notification. Discovery is the procedure whereby OAM-enabled entities discover each other and exchange information regarding their OAM capabilities and configuration. The OAM capabilities may be used to determine whether it is worthwhile to run the OAM protocol.
Event notification for reporting various link statistics such as the number of symbol errors that occurred during a specified period, or the running total of frames with errors since the OAM sublayer was last reset.
Loopback control used by an active-mode OAM entity to enable or disable intrusive loopback in the remote passive-mode device.
Management
Setup, monitoring and diagnostics tests can be performed using one of the following methods: Local management via ASCII terminal connected to the V.24/RS-232 DCE control port. Remote management via the network or user ports using Telnet SSH, Web, Secured Web (HTTPS) using Web terminal, or RADview, RADs SNMP-based management system. IPmux-24 supports the SNMP version 3 entity, providing secure access to the device by authenticating and encrypting packets transmitted over the network.
Security
To ensure client-server communication privacy and correct user authentication, IPmux-24 supports the security protocols listed below: RADIUS (client authentication only) SSL for Web-based management application SSH for Secure Shell communication session SNMPv3.
Syslog
The Syslog protocol is used by IPmux-24 to generate and transport event notification messages over IP networks to the central Syslog server. The Syslog operation is compliant with the RFC 3164 requirements.
Simple Network Time Protocol

IPmux-24 supports Simple Network Time Protocol (SNTP) for propagating and receiving time information on a network, according to SNTPv4 (RFC 4330) requirements. SNTP is used to configure data and time by learning the information from a single or multiple NTP servers. The clock can be configured to a local time by defining UTC and DST offsets.
IPmux-24 Ver. 3.5
1-31
QoS
IPmux-24 supports traffic prioritization and rate limitation.
Traffic Classification and Prioritization

IPmux-24 provides four priority queues for each user port. The traffic can be classified and mapped into the priority queues according to the VLAN priority, DSCP, IP Precedence or per port basis. In VLAN-unaware mode TDM traffic receives the highest priority automatically.
Rate Limitation
IPmux-24 supports an egress and ingress rate limitation per network and user ports.
L2CP Handling
Each Ethernet port can be configured to tunnel the Layer-2 control frames across the network, to peer supported protocols (OAM.ah) or to discard the L2CP frames.
1.4
E1 Interface
Technical Specifications
1, 2 or 4 ITU-T Rec. G.703, G.704, G.706, G.732, G.823 2.048 Mbps HDB3 Unframed, framed, multiframe; with or without CRC-4 CAS, CCS (transparent) Balanced: 120; unbalanced: 75 Receive: 0 to -36 dB LTU (long haul) 0 to -10 dB DSU (short haul) Transmit pulse amplitude, balanced: 3V 10% Transmit pulse amplitude, unbalanced: 2.37V 10%
Number of Ports Compliance Data Rate Line Code Framing Signaling Line Impedance Signal Levels
Jitter Performance Connector
As per ITU-T G.823 Balanced: RJ-45 Unbalanced: Two BNC coax (via an adapter cable)
1-32
IPmux-24 Ver. 3.5
T1 Interface
Number of Ports Compliance Data Rate Line Code Framing Signaling Line Impedance Signal Levels
1, 2 or 4 ANSI T1.403, AT&T TR-62411, ITU-T Rec. G.703, G.704, G.824 1.544 Mbps B8ZS, B7ZS, AMI Unframed, SF, ESF CAS (robbed bit), CCS (transparent) Balanced: 100 Receive: 0 to -36 dB Transmit pulse amplitude: 3V 20%; 0 dB, -7.5 dB, -15 dB, -22 dB (CSU), user-selectable 2.7V 10%, 0 to 655 feet, (DSU), user-selectable
Jitter Performance Connector
As per AT&T TR-62411, G.824 (for internal, loopback and external clock modes) RJ-45 IEEE 802.3, 802.3u, 802.1p&Q Any port can be either SFP slot or built-in UTP UTP (10/100BaseT) SFP-based fiber optic (1000BaseX or 100BaseFx) SFP-based electrical (10/100/1000BaseT)
Ethernet Interface
Compliance Port Combinations Interfaces
Frame Size Fiber Optic Specifications
1632 bytes max See the SFP Transceivers data sheet
Timing
Transmit
Internal External input or output via dedicated connector: E1/T1 or 2048/1544 kHz squarewave (RS-422 electrical levels) Loopback Adaptive
IPmux-24/A Frequency Accuracy Adaptive Clock
Better than 16 ppb and G.823 synchronization interface requirements (clause 6), when locked to a PRC (stratum 1) or SSU (stratum 2) clock
IPmux-24 Ver. 3.5
1-33
Frequency Accuracy in Holdover
16 ppb 1 ppb of aging per day
Pseudowire
Number of Bundles Standard Compliance
Up to 64 TDM: IETF: RFC 4553 (SAToP), RFC 5087 (TDMoIP), RFC 5086 (CESoPSN) ITU-T: Y.1413 (TDMoIP) MFA: IA 4.0 MEF: 8, 9, 14 (EPL-certified) HDLC: IETF: IETF RFC 4618 (excluding clause 5.3 PPP) and RFC 5087
Jitter Buffer Size
0.5180 msec (unframed) with 0.1 msec granularity 2.5180 msec (framed) with 0.5 msec granularity
Management
Methods
SNMPv1, SNMPv3 Telnet RADview Service Center TDMoIP (ordered separately) ASCII terminal via V.24 (RS-232) DCE port
Diagnostics
Loopbacks
E1/T1 local loopback E1/T1 remote loopback T1 Facility Type 1 (FAC1) inband loopback
Statistics
E1/T1 Ethernet Receive Buffer Indication
As per G.826 and RFC 2495 As per RFC 2819 Overflow, underflow, sequence error
Alarm Relay Indicators
Dry Contact General
Via pin 6, pin 7 and pin 8 of the EXT CLK connector (RJ-45) PWR (green) Power TST/ALM (red/yellow) Alarm or diagnostic loopback status EXT. CLK (red/green) External clock status
E1
E1 SYNC (red/green) E1 synchronization status
1-34
IPmux-24 Ver. 3.5
T1 Ethernet
T1 SYNC (red/green) T1 synchronization status LINK/ACT (green) Link/activity status 100240 VAC, 50/60 Hz or 48/60 VDC nominal (40 to 72 VDC) 24/48/60 VDC nominal (18 to 72 VDC) 13W max 47 mm (1.8 in) 215 mm (8.4 in) 147 mm (5.8 in) 0.7 kg (1.5 lb) IPmux-24: 0C to 50C (32C to 122F) IPmux-24/H: -30 to 65C (-22 to 149F)
Power
AC/DC Source DC Source Power Consumption
Physical
Height Width Depth Weight
Environment
Temperature
Humidity
Up to 90%, non-condensing
IPmux-24 Ver. 3.5
1-35
1-36
IPmux-24 Ver. 3.5
Chapter 2 Installation and Setup

2.1 Introduction
This chapter describes installation and setup procedures for the IPmux-24 unit. After installing the unit, refer to Chapter 3 for the operating instructions. If a problem is encountered, refer to Chapter 5 for test and diagnostic instructions. Internal settings, adjustment, maintenance, and repairs may be performed only by a skilled technician who is aware of the hazards involved.
Warning
Always observe standard safety precautions during installation, operation, and maintenance of this product.
2.2
Site Requirements and Prerequisites
AC-powered IPmux-24 units should be installed within 1.5m (5 ft) of an easily-accessible grounded AC outlet capable of furnishing the voltage in accordance with IPmux-24 nominal supply voltage. DC-powered IPmux-24 units require a 24 or 48 VDC power source, which must be adequately isolated from the main supply. Allow at least 90 cm (36 in) of frontal clearance for operating and maintenance accessibility. Allow at least 10 cm (4 in) clearance at the rear of the unit for signal lines and interface cables. The ambient operating temperature of IPmux-24 must be 0C to 50C (32C to 122F), at a relative humidity of up to 90%, non-condensing.
2.3

Package Contents
The IPmux-24 package includes the following items: One IPmux-24 unit Matching SFP module (if ordered) AC power cord AC/DC adapter plug CBL-RJ45/2BNC/E1/X adapter cable for unbalanced E1 interface (if ordered)
IPmux-24 Ver. 3.5
Package Contents
2-1
CBL-DB9F-DB9M-STR control port cable (if ordered) RM-35/P1 rack mount kit for mounting one IPmux-24 unit (if ordered) RM-35/P2 rack mount kit for mounting two IPmux-24 units (if ordered).
2.4
Required Equipment
IPmux-24 is a standalone unit, designed for desktop or bench installation and is delivered fully assembled. No provisions are made for bolting the unit to a tabletop. Mounting IPmux-24 in a 19-inch rack, however, requires a 3 mm Phillips screwdriver and an RM-35 kit. For the rack installation instructions, refer to the Rack Mounting Kit for 19-inch Racks guide that comes with the RM kit.
Power Cable
AC-powered IPmux-24 is equipped with an appropriate power cord (country or region dependent) to be connected from the mains to the power socket of the hot-swappable power unit. DC-powered IPmux-24 is equipped with an appropriate DC connection kit, which should be used for preparing the DC cable connection.
Interface Cables
Refer to the following table to determine what cables and connectors are required for installation. Appendix A specifies the wiring of all connector pinouts.
Table 2-1. Required Interface Cables

Interface Control terminal Ethernet Cable Type DB-9 to DB-9, RS-232/V.24 compliant cable for ASCII-based terminal control Electrical: Cat. 5, RJ-45 to RJ-45, IEEE 802.3 compliant cable Fiber optic: Fiber optic cable that matches the ordered interface type. E1/T1 Balanced: Cat. 5, RJ-45 to RJ-45 cable Unbalanced: CBL-RJ45/2BNC/E1/X adapter cable
2.5
Mounting the Unit
IPmux-24 is designed for installation as a desktop unit. It can also be mounted in a 19" rack. For rack mounting instructions, refer to RM-35 installation kit manual Refer to the clearance and temperature requirements in Site Requirements and
Prerequisites.
2-2
Mounting the Unit
IPmux-24 Ver. 3.5
2.6
Installing SFP Modules
IPmux-24 uses SFP modules with LC fiber optic connectors. Third-party SFP optical transceivers must be agency-approved, complying with the local laser safety regulations for Class 1 laser equipment.
Warning
To install the SFP modules: 1. Lock the wire latch of each SFP module by lifting it up until it clicks into place, as illustrated in Figure 2-1.
Note
Some SFP models have a plastic door instead of a wire latch.
Figure 2-1. Locking the SFP Wire Latch

2. Carefully remove the dust covers from the SFP slot. 3. Insert the rear end of SFP into the socket, and push slowly backwards to mate the connectors until the SFP clicks into place. If you feel resistance before the connectors are fully mated, retract the SFP using the latch wire as a pulling handle, and then repeat the procedure. 4. Remove the protective rubber caps from the SFP modules. To remove the SFP module: 1. Disconnect the fiber optic cables from the SFP module. 2. Unlock the wire latch by lowering it downwards (as opposed to locking). 3. Hold the wire latch and pull the SFP module out of the Ethernet port.
IPmux-24 Ver. 3.5
Installing SFP Modules
2-3
2.7
Connecting to Ethernet Equipment
IPmux-24 is connected to the Ethernet equipment via the fiber optic LC or 8-pin RJ-45 electrical ports designated NET 1, NET/USER 2 and USER 3. Refer to Appendix A for the RJ-45 connector pinout. Figure 2-2 illustrates a typical IPmux-24 rear panel with two fiber optic LC and one electrical RJ-45 connectors. To connect to the Ethernet equipment with fiber optic interface: Connect IPmux-24 to the Ethernet equipment using a standard fiber optic cable terminated with an LC connector.
RESTORE DEFAULT
NET 1 CONTROL
NET/USER 2
USER 3
E1/T1
DCE
GbE/100Fx
10/100BASE-T
SYNC
SYNC
SYNC
SYNC
Figure 2-2. NET 1 and NET/USER 2 Fiber Optic Connectors Note The SFP-based ports also accept SFP transceivers with electrical RJ-45 connectors.
To connect to the Ethernet equipment with a copper interface: Connect IPmux-24 to the Ethernet equipment using a standard straight UTP cable terminated with an RJ-45 connector.
Figure 2-3. USER 3 Electric Connector
2.8
Connecting to E1/T1 Devices
E1/T1 devices are connected to IPmux-24 via balanced RJ-45 ports designated E1/T1 14. Unbalanced E1 interface is provided via CBL-RJ45/2BNC/E1/X adapter cable (see Appendix A for the connector pinouts and cable wiring diagram).
Caution When connecting balanced E1 or T1 equipment, make sure to use only 4-wire
RJ-45 connectors with the following pins used for receiving and transmitting data: 1, 2, 4, 5. Do not use 8-pin RJ-45 connectors.
2-4
Connecting to E1/T1 Devices
IPmux-24 Ver. 3.5
RESTORE DEFAULT
NET 1 CONTROL
NET/USER 2
USER 3
E1/T1
DCE
GbE/100Fx
10/100BASE-T
SYNC
SYNC
SYNC
SYNC
Figure 2-4. E1/T1 14 Balanced Connectors

To connect to the E1/T1 devices with balanced interfaces: Connect IPmux-24 to the E1/T1 devices using standard straight E1/T1 cables.
To connect to the E1 devices with unbalanced interfaces: 1. Connect the RJ-45 connectors of the CBL-RJ45/2BNC/E1/X adapter cables to the IPmux-24 balanced RJ-45 ports. 2. Connect the transmit cable to the red coaxial connectors of the adapter cables marked . 3. Connect the receive cable to the green coaxial connectors of the adapter cables marked .
2.9
Connecting to ASCII Terminal
IPmux-24 is connected to an ASCII terminal via a 9-pin D-type female connector designated CONTROL. Refer to Appendix A for the connector pinout.
RESTORE DEFAULT
NET 1 CONTROL
NET/USER 2
USER 3
E1/T1
DCE
GbE/100Fx
10/100BASE-T
SYNC
SYNC
SYNC
SYNC
Figure 2-5. CONTROL Connector

To connect to an ASCII terminal: 1. Connect the male 9-pin D-type connector of CBL-DB9F-DB9M-STR straight cable available from RAD to the CONTROL connector. 2. Connect the other connector of the CBL-DB9F-DB9M-STR cable to an ASCII terminal.
Caution Terminal cables must have a frame ground connection. Use ungrounded cables
when connecting a supervisory terminal to a DC-powered unit with floating ground. Using improper terminal cable may result in damage to supervisory terminal port.
IPmux-24 Ver. 3.5
Connecting to ASCII Terminal
2-5
2.10 Connecting to External Clock Source

If your IPmux-24 features an external clock mechanism, connect the unit to the external clock source via a balanced RJ-45 port designated EXT. CLK. Refer to Appendix A for the connector pinout.
Figure 2-6. EXT. CLK Connector

To connect to the external clock source: Connect IPmux-24 to the external E1 or T1 clock source using an appropriate cable.
2.11 Connecting to External Alarm Device

IPmux-24 is connected to an external alarm device via designated pins the balanced RJ-45 EXT. CLK port (see Figure 2-6). Refer to Appendix A for the connector pinout. To connect to an external alarm source: 1. Prepare a cable in accordance with the alarm connector pinout given in Appendix A. 2. Connect IPmux-24 to an external alarm device, such as a buzzer, using prepared cable.
2.12 Connecting to Power

To connect power to IPmux-24, refer to the appropriate section below, depending on your version of the unit (AC or DC). Interrupting the protective grounding conductor (inside or outside the instrument) or disconnecting the protective earth terminal can make this instrument dangerous. Intentional interruption is prohibited. Before connecting or disconnecting any communication cable, the unit must be ground by connecting its power cord to a power outlet with a ground terminal, and by connecting the ground terminal on the panel (if provided) to a protective ground. Make sure that only fuses with the required rated current and specified type, as marked on the IPmux-24 rear panel, are used for replacement. Whenever it is likely that the protection offered by fuses has been impaired, the instrument must be made inoperative and be secured to prevent any operation.
Warning
2-6
Connecting to Power
IPmux-24 Ver. 3.5
Note
Refer also to the sections describing connections of AC and DC mains at the beginning of the manual.
Connecting to AC Power
AC power is supplied to IPmux-24 through the 1.5m (5 ft) standard power cable terminated by a standard 3-prong plug. The cable is supplied with the unit according to the number of ordered power supplies. To connect AC power: 1. Verify that the AC outlet is grounded properly. Ensure that the supply voltage is in the range 100 VAC to 240 VAC. 2. Connect the power cable to the rear panel connector first and then to the AC mains outlet.
Connecting to DC Power
DC power is supplied via an AC/DC adapter plug provided with the unit. To connect DC power: Refer to the DC power supply connection supplement for instructions how to wire the DC adapters. The DC supplement is provided at the end of the manual.
IPmux-24 Ver. 3.5
Connecting to Power
2-7
2-8
Connecting to Power
IPmux-24 Ver. 3.5
Chapter 3 Operation
This chapter: Provides a detailed description of the front panel controls and indicators and their functions Explains power-on and power-off procedures Provides instructions for configuration using a terminal connected to the IPmux-24 control port Provides instructions for configuration using a Web browser Illustrates the management menus.
For a detailed explanation of parameters on the menus, see Chapter 4.
3.1
Turning On the Unit
To turn on IPmux-24: Connect the power cord to the mains.
Once it is powered up, IPmux-24 operates automatically. IPmux-24 requires no operator attention once installed, with the exception of occasional monitoring of front panel indicators. Intervention is only required when IPmux-24 must be configured to its operational requirements, or diagnostic tests are performed.
3.2
Indicators
The unit's LEDs are located on the front and rear panels (see Figure 3-1 and Figure 3-2). Table 3-1 lists the functions of the IPmux-24 LED indicators.
IPmux-24
RAD
ETH LINK/ACT 1 2 3
PWR TST
Figure 3-1. Front Panel
IPmux-24 Ver. 3.5
Indicators
3-1
Chapter 3 Operation
Figure 3-2. Rear Panel Table 3-1. LEDs and Controls

Name PWR TST/ALM Type Green LED Red/yellow LED Function ON Power is ON ON (red) An active alarm is stored in the log file ON (yellow) Any alarm is stored in the log file OFF No alarms are stored in the log file Blinks (red) Active alarm is stored in the log file and a test is active Blinks (red) An alarm is present in the log file and a test is active or only a test is active E1 SYNC Red/green LED ON (green) E1 link is synchronized ON (red) E1 link has lost synchronization OFF E1 link is disabled T1 SYNC Red/green LED ON (green) T1 link is synchronized ON (red) T1 link has lost synchronization OFF T1 link is disabled ETH LINK/ACT 1 Green LED ON Network Ethernet link is OK Blinks Data is being transmitted or received on the network Ethernet link Green LED ON User Ethernet link 1 is OK Blinks Data is being transmitted or received on the user Ethernet link 1 Green LED ON User Ethernet link 2 is OK Blinks Data is being transmitted or received on the user Ethernet link 2 Red/green LED ON (green) IPmux-24 is configured to external clock and valid clock input is detected ON (red) IPmux-24 is configured to external clock and no valid clock input is detected OFF IPmux-24 is not configured to external clock RESTORE DEFAULT Button Restores default values Rear panel Rear panel Front panel Front panel Front panel Rear panel Rear panel Location Front panel Front panel
ETH LINK/ACT 2
ETH LINK/ACT 3
EXT. CLK
3-2
Indicators
IPmux-24 Ver. 3.5
Chapter 3 Operation
3.3
Default Settings
The following table lists the default settings of the IPmux-24 parameters.
Table 3-2. Default Settings

Parameter Accept Frame Type Access Default Value All All Menu Path Configuration > Bridge > Bridge Port Configuration > System > Management > Management access > User access Configuration > System > Management > Management Access > RADIUS Parameters Configuration > System > OAM > CFM > Maintenance Domains > Maintenance Associations > MEP Configuration > Physical layer > ETH Configuration > Physical layer > TDM Configuration > Bridge Configuration > System > Management > Management Access > RADIUS Parameters Configuration > Physical layer > ETH Manual Section Configuring the Bridge Ports Defining Management Access Permissions
Accounting Port
Configuring RADIUS Client
Admin status
Down
Configuring Maintenance Endpoints
Administrative status Administrative status Aging time Authentication Port
Up Up 300 sec
Configuring Ethernet Interfaces Configuring the E1/T1 TDM Interface Configuring the Ethernet Bridge Configuring RADIUS Client
Auto negotiation
Disable for fiber optic interface Enable for copper interface
Configuring Ethernet Interfaces
Baud rate Broadcast Mode Burst size
115200 bps Disable 12 bytes
Configuration > System > Control port Configuration > System > Date and Time Configuration > QoS > Rate Limitation > Ingress
Configuring Control Port Parameters Setting the Date and Time Configuring Ingress Rate Limitation
IPmux-24 Ver. 3.5
Default Settings
3-3
Chapter 3 Operation Parameter CCI Enabled Default Value True Menu Path
Installation and Operation Manual Manual Section Configuring Maintenance Endpoints
Configuration > System > OAM > CFM > Maintenance Domains > Maintenance Associations > MEP Configuration > Connection > Bundle connection Configuration > System > Management > Device info Configuration > System > OAM > CFM > Maintenance Domains > Maintenance Associations > MEP Configuration > System > OAM > CFM > Maintenance Domains > Maintenance Associations > MEP Configuration > System > Management > Host IP Configuration > Connection > PW host IP Configuration > Bridge > Bridge Port Configuration > Physical layer > Link OAM > Link OAM Descriptors Configuration>Physical layer>Link OAM>Link OAM Parameters Configuration > System > OAM > CFM > Maintenance Domains > Maintenance Associations > MEP Configuration > Connection > Bundle connection
Connection status
Enable
Configuring Bundle Connections Assigning a Name to the Unit and Its Location Configuring Maintenance Endpoints
Contact Person
name of contact person
Continuity Verification Mode
CC Based
Default CCM/LTM Priority
Default gateway
Managing IP Parameters of the Host Configuring Bundle Connections Configuring the Bridge Ports Configuring Link OAM Descriptors Assigning Link OAM Descriptor to an Ethernet Port Configuring Maintenance Endpoints
Default next hop Default Priority Tag Descriptor Number
Descriptor Number
Destination Address Type
Multicast
Destination bundle
Configuring Bundle Connections
3-4
Default Settings
IPmux-24 Ver. 3.5
Installation and Operation Manual Parameter Destination IP address Default Value Menu Path Configuration > Connection > Bundle connection Configuration > System > OAM > CFM > Maintenance Domains > Maintenance Associations > MEP Configuration > System > Syslog Configuration > System > Syslog Configuration > System > Management > Host IP Configuration > Physical layer > TDM Configuration > System > Syslog Configuration > System > System clock Configuration > System > System clock Configuration > Connection > Bundle connection Configuration > Bridge Configuration > System > Management > Host IP > Encapsulation Configuration > Connection > PW host IP > PW encapsulation Configuration > Physical layer > TDM Configuration > Bridge > Bridge Port Configuration > System > Management > Host IP
Chapter 3 Operation Manual Section Configuring Bundle Connections Configuring Maintenance Endpoints
Destination MAC Address
01-80-C2-00-00-33
Device Logging Status Device UDP Port DHCP
Disable 514 Enable
Configuring Syslog Parameters Configuring Syslog Parameters Managing IP Parameters of the Host Configuring the E1/T1 TDM Interface Configuring Syslog Parameters Configuring the System Clock Configuring the System Clock Configuring Bundle Connections Configuring the Ethernet Bridge Configuring the Host Encapsulation Configuring Bundle Connections Configuring the E1/T1 TDM Interface Configuring the Bridge Ports Managing IP Parameters of the Host
Ethernet network type Facility Fall back clock Fall back source Far end type
WAN Local 1 Adaptive Channel 1 E1 or T1 (ESF)
Forwarding Mode Host Tagging
Filter Untagged
Host Tagging
Untagged
Idle code Ingress Filtering IP address
7E Enable
IPmux-24 Ver. 3.5
Default Settings
3-5
Chapter 3 Operation Parameter IP address IP mask Default Value 0.0.0.0 Menu Path
Installation and Operation Manual Manual Section Configuring Bundle Connections Managing IP Parameters of the Host Configuring Bundle Connections Configuring Bundle Connections Configuring Bundle Connections Configuring the Ring Protection Configuring the Ring Protection Configuring the LAG Configuring Ingress Rate Limitation Configuring the T1 TDM Interface Configuring the T1 TDM Interface Configuring the E1/T1 TDM Interface Configuring the T1 TDM Interface Configuring the T1 TDM Interface Configuring the E1 TDM Interface Configuring L2CP Handling Configuring Bundle Connections
Configuration > Connection > PW host IP Configuration > System > Management > Host IP Configuration > Connection > PW host IP Configuration > Connection > Bundle connection Configuration > Connection > Bundle connection Configuration > System > Protection Configuration > System > Protection Configuration > Physical layer > LAG Configuration > QoS > Rate Limitation > Ingress Configuration > Physical layer > TDM (T1) Configuration > Physical layer > TDM (T1) Configuration > Physical layer > TDM Configuration > Physical layer > TDM (T1) Configuration > Physical layer > TDM (T1) Configuration > Physical layer > TDM (E1) Configuration > Bridge > Bridge Port > L2CP Handling Configuration > Connection > Bundle connection
IP mask IP TOS
0.0.0.0 0
Jitter buffer
3.0
Keep Alive Drops To Fall Keep Alive Tx Time LAG Enable Limit Packet Type Line bildout Line code Line interface Line length Line type Line type L2CP Handling
3 13 Disabled All -7.5 B8ZS DSU 0133 feet ESF Framed G.704 Tunnel
MPLS Egress Label
3-6
Default Settings
IPmux-24 Ver. 3.5
Installation and Operation Manual Parameter Number of Retries Default Value 1 Menu Path Configuration > System > Management > Management Access > RADIUS Parameters Configuration > Physical layer > TDM Configuration > System > System clock Configuration > System > System clock Configuration > Physical layer > ETH Configuration > System > Protection Configuration > QoS > Priority > Classification Configuration > QoS > Priority > Classification Configuration > Connection > Bundle connection Configuration > Connection > Bundle connection Configuration > Physical layer > Link OAM > Link OAM Descriptors Configuration > Physical layer > Link OAM > Link OAM Descriptors Configuration>Physical layer>Link OAM>Link OAM Parameters Configuration > Physical layer > TDM Configuration > Connection > Bundle connection Configuration > Physical layer > TDM
Chapter 3 Operation Manual Section Configuring RADIUS Client
Mark signaling code Master clock Master source Max Capability Advertised Mcast VLAN ID Network ETH1 Network/User ETH2 Next hop
D Rx clock Channel 1 100baseT Full Duplex 4002 Port default priority Port default priority
Configuring the E1/T1 TDM Interface Configuring the System Clock Configuring the System Clock Configuring Ethernet Interfaces Configuring the Ring Protection Configuring Quality of Service (QoS) Configuring Quality of Service (QoS) Configuring Bundle Connections Configuring Bundle Connections Configuring Link OAM Descriptors Configuring Link OAM Descriptors Assigning Link OAM Descriptor to an Ethernet Port Configuring the E1/T1 TDM Interface Configuring Bundle Connections Configuring the E1/T1 TDM Interface
OAM connectivity
Enable
OAM Mode
OAM Rate Limit
OAM Status
Disable
OOS code OOS mode
FF Tx OOS
OOS signaling
Space
IPmux-24 Ver. 3.5
Default Settings
3-7
Chapter 3 Operation Parameter Payload format Default Value V2 Menu Path
Installation and Operation Manual Manual Section Configuring Bundle Connections Defining Management Access Permissions
Configuration > Connection > Bundle connection Configuration > System > Management > Management access > User access Configuration > System > Date and Time
Permission
Full control
Poll Interval Port VID Primary Bundle 1 1
Setting the Date and Time Configuring the Bridge Ports Configuring Bundle Protection Configuring Maintenance Endpoints
Configuration > Bridge > Bridge Port Configuration > System > Protection > Bundle Protection Configuration > System > OAM > CFM > Maintenance Domains > Maintenance Associations > MEP Configuration > System > OAM > CFM > Maintenance Domains > Maintenance Associations > MEP Configuration > System > Protection > Dual Homing Configuration > Connection Configuration > System > Protection Configuration > Connection Configuration > System > Management > Management Access Configuration > QoS > Rate Limitation > Egress Configuration > QoS > Rate Limitation > Ingress Configuration > System > Management > Host IP
Primary VID
Primary PORTID
Network-ETH1
Protection mode PSN type PTP VLAN ID PW type RADIUS
Dual Homing UDP/IP 4001 TDMoIP CE Enable Remote
Configuring Dual Homing Configuring Bundle Connections Configuring the Ring Protection Configuring Bundle Connections Controlling Management Access Configuring Egress Rate Limitation Configuring Ingress Rate Limitation Managing IP Parameters of the Host
Rate Limitation Rate Limitation Read Community
No Limit No Limit public
3-8
Default Settings
IPmux-24 Ver. 3.5
Installation and Operation Manual Parameter Recovery Default Value Revertive Menu Path Configuration > System > Protection > Bundle Protection Configuration > System > Protection > Bundle Protection Configuration > Connection Configuration > Physical layer > TDM (T1) Configuration > System > Protection > Dual Homing Configuration > System > Protection Configuration > Physical layer > TDM Configuration > System > Protection > Bundle Protection Configuration > System > Management > Management Access > RADIUS Parameters Configuration > System > Syslog Configuration > System > Syslog Configuration > System > Syslog Configuration > System > Management > Management Access > RADIUS Parameters Configuration > System > Management > Management Access Configuration > System > Management Configuration > Physical layer > TDM Configuration > Connection > Bundle
Chapter 3 Operation Manual Section Configuring Bundle Protection Configuring Bundle Protection Configuring Bundle Connections Configuring the T1 TDM Interface Configuring Dual Homing Configuring the Ring Protection Configuring the E1/T1 TDM Interface Configuring Bundle Protection Configuring RADIUS Client
Redundancy Type
1+1
Redundancy Function Restoration time Revertive mode Ring Administrative Status Rx sensitivity Secondary Bundle
None Fast (1 Second) Not Revertive Down Short haul 1
Server IP Address
0.0.0.0
Server IP Address Server UDP Port Severity Level Shared Secret
0.0.0.0 514 Minor
Configuring Syslog Parameters Configuring Syslog Parameters Configuring Syslog Parameters Configuring RADIUS Client
SNMP access
Enable
Controlling Management Access Enabling SNMPv3 Configuring the E1/T1 TDM Interface Configuring Bundle Connections
SNMPv3 Send upon fail Sensitive
Disable OOS code Data
IPmux-24 Ver. 3.5
Default Settings
3-9
Chapter 3 Operation Parameter Default Value Menu Path connection Set Active Port Shut Down Duration Upon Flip Signaling mode Source clock quality Source IP Address None 0 None Other/unknown PW IP
Installation and Operation Manual Manual Section
Configuration > System > Protection > Dual Homing Configuration > System > Protection > Dual Homing Configuration > Physical layer > TDM (T1) Configuration > Physical layer > TDM Configuration > Connection > Bundle connection Configuration > Physical layer > TDM Configuration > Physical layer > ETH Configuration>System> OAM>CFM Configuration>System> OAM>CFM Configuration > System > Management > Device info Configuration > System > Management > Device info Configuration > Bridge > Bridge Port Configuration > System > Management > Management Access Configuration > Connection > Bundle connection Configuration > QoS > Priority > Classification Configuration > System > Management > Management Access > RADIUS Parameters
Configuring Dual Homing Configuring Dual Homing Configuring the T1 TDM Interface Configuring the E1/T1 TDM Interface Configuring Bundle Connections Configuring the E1/T1 TDM Interface Configuring Ethernet Interfaces Adding and Configuring Maintenance Domains Adding and Configuring Maintenance Domains Assigning a Name to the Unit and Its Location Assigning a Name to the Unit and Its Location Configuring the Bridge Ports Controlling Management Access Configuring Bundle Connections Configuring Quality of Service (QoS) Configuring RADIUS Client
Space signaling code Speed & Duplex Standard OAM EtherType
1 10baseT Half Duplex 8902
Standard OAM MAC Address System Location
01-80-C2-00-00-30
the location of this device
System Name
IPmux-24
Tag Handling Telnet/SSH access
None Enable
TDM bytes in frame
TDM PW Timeout
Port default priority 1
3-10
Default Settings
IPmux-24 Ver. 3.5
Installation and Operation Manual Parameter Trail mode Transmit clock source Trap Community Default Value Termination Adaptive SNMP_trap Menu Path Configuration > Physical layer > TDM Configuration > Physical layer > TDM Configuration > System > Management > Host IP Configuration > QoS > Priority > Classification Configuration > System > Management > Management access > User access Configuration > System > Date and Time Configuration > Bridge Configuration > Connection > Bundle connection Configuration > System > Protection > Dual Homing Configuration > System > Management > Management Access Configuration > System > Management > Host IP Configuration > System > Protection > Bundle Protection
Chapter 3 Operation Manual Section Configuring the E1/T1 TDM Interface Configuring the E1/T1 TDM Interface Managing IP Parameters of the Host Configuring Quality of Service (QoS) Defining Management Access Permissions
User ETH3 User name
Port default priority su
UTC Offset VLAN Mode VLAN tagging
+2 Unaware Disable
Setting the Date and Time Configuring the Ethernet Bridge Configuring Bundle Connections Configuring Dual Homing Controlling Management Access Managing IP Parameters of the Host Configuring Bundle Protection
Wait to Restore Web access
0 Enable
Write Community
private
WTR
10
3.4 Configuration and Management Alternatives

If required, IPmux-24 can be reconfigured. The IPmux-24 configuration and monitoring operations are performed using any of the following tools: ASCII terminal connected to supervisory port Web-based management system, using a Web browser running on a PC connected to the network RADview, RADs SNMP-based management system with a graphical user interface. See RADview SC/TDMoIP User's Manual for details
IPmux-24 Ver. 3.5
Configuration and Management Alternatives
3-11
Chapter 3 Operation
Third-party SNMP-based management systems.
Detailed configuration procedures are given in Chapter 4. The following parameters can be configured only via ASCII or Web terminal: Host IP address and mask Host encapsulation Terminal baud rate (ASCII terminal only) Ethernet ring.
Working with Terminal

IPmux-24 includes a V.24/RS-232 asynchronous DCE port, designated CONTROL and terminated in a 9-pin D-type female connector. The control port continuously monitors the incoming data stream and immediately responds to any input string received through this port. The IPmux-24 control port can be configured to communicate at the following rates: 9.6, 19.2, 38.4, 57.6 or 115.2 kbps. To start a terminal control session: 1. Make sure all IPmux-24 cables and connectors are properly connected. 2. Turn on the control terminal or start the PC terminal emulation (in Windows XP: click Start > All Programs > Accessories > Communications> HyperTerminal to create a new terminal connection. The Connection Description dialog box is displayed.
Figure 3. Windows HyperTerminal, Connection Description Dialog Box

3. Enter description for the terminal connection. 4. Select an icon to represent the terminal connection. The Connect To dialog box is displayed.
3-12
IPmux-24 Ver. 3.5
Chapter 3 Operation
Figure 4. Connect To Dialog Box

5. Select a PC COM port to be used to communicate with IPmux-24. The COM Properties dialog box is displayed.
Figure 5. COM1 Properties Dialog Box

6. Configure the communication port parameters to a baud rate of 115,200 bps, 8 bits/character, 1 stop bit, no parity and no flow control. The main HyperTerminal window is displayed.
IPmux-24 Ver. 3.5
3-13
Chapter 3 Operation
Figure 6. Main HyperTerminal Window

7. Set the terminal emulation to ANSI VT100 (Properties> Settings). 8. Set the terminal mode to the 132-column mode for optimal view of system menus: (Properties > Settings > Terminal Setup > 132 column mode). 9. Power-up the unit.
Login
To prevent unauthorized modification of the operating parameters, IPmux-24 supports three access levels: Superuser can perform all the activities supported by the IPmux-24 management facility. Users have read-only access, they cannot change any settings. Techs (technicians) read-only access, but the technicians are allowed to reset the unit, set its parameters to defaults and use TFTP download/upload.
The su, user and tech are permanent users, they cannot be removed from the authorization database. The su level users can define new dynamic users and assign access levels (su, user or tech) to them. To enter as a superuser: 1. Enter su for user name. 2. Enter 1234 for password. To enter as a user: 1. Enter user for user name. 2. Enter 1234 for password.
3-14
IPmux-24 Ver. 3.5
Chapter 3 Operation
To enter as a technician: 1. Enter tech for user name. 2. Enter 1234 for password.
Choosing Options
How to use the terminal to perform a desired activity: To select a menu item, type the corresponding line number and then press <Enter>. This will either: display a submenu or a parameter selection screen: let you type the (free text) parameter value in the same row toggle the current value of the corresponding parameter (relevant to ENABLE/DISABLE or ON/OFF selections). The type of response to be expected after selecting a menu item is indicated as follows: > Selecting that item will display a submenu or a parameter selection screen. Selecting that item will let you type the desired value in the same line. When neither symbol is displayed, selecting that item will toggle the current selection, now shown in brackets (for example, this will change ENABLE to DISABLE or vice versa).
...
Nothing
When a menu does not fit on one screen (because it includes many lines), it is displayed on two consecutive pages. In this case, you will see (N) after the last line on the first page and (P) after the last line on the second page: While on the first page, press N to display the second page While on the second page, press P to return to the first page.
When a configuration screen is organized as a table, a special set of keys is used for navigation within the table (such screens always have a ? (help) option that displays these keys). The following keys may be used for navigation within tables:
L move to the left ^D scroll down
R move to the right ^U scroll up
In addition, the following shortcuts are also available: Tab select the next cell that may be changed G followed by <row number>,<col number> select a specific cell. For example, type G2,5 to select the fifth cell in the second row. The current value of a parameter is listed within parentheses ( ). To change a parameter value on a parameter selection screen:
IPmux-24 Ver. 3.5
3-15
Chapter 3 Operation
Type the line number corresponding to the desired value, and then press <Enter> To enter a value which requires free text entry, type in the desired string and then press <Enter>. Use backspace to erase the current string. Note that whenever applicable, the allowed range of values of a parameter is listed within square brackets [ ]. The entry is checked after pressing <Enter>, and it is accepted only if it is valid: If you make an error, for example, if you press a key not active on the current screen or select an invalid parameter value, an ERROR indicator appears in the right-hand corner. This indicator disappears as soon as you make a correct operation. If you select a parameter value incompatible with the current operating state or other parameters, you will see a message that explains the error. When done with the current screen, press <Esc> to return to the previous screen, or type ! to return directly to the main menu.
Ending a Terminal Configuration Session

To end the current terminal session: Type &.
After a session is ended, it is necessary to enter again a valid user name and password to start a new session.
Verifying the Application Software Version

Before continuing the management session, verify that the unit is running version 3.5 of the application software. To verify the application software version: 1. From the Main menu, select Inventory. 2. In the Inventory screen, verify that that the Application version field displays 3.5x. 3. If the application software version is 3.5x, proceed to Chapter 4 for further instructions on how to configure the unit for management and operation. 4. If displayed number is below 3.5x, see Chapter 6 for software upgrade instructions.
Working with Web Terminal

Web Browser Requirements
The following Web browsers can be used to access the IPmux-24 supervision utility from any location that enables access to the IPmux-24 using Internet protocols. Internet Explorer 7.0 and up, running on Windows
3-16
IPmux-24 Ver. 3.5
Chapter 3 Operation
Netscape Communicator 8.1 and up, running on Windows, HPOV or Linux Firefox 2.0.0.1 and up, running on Windows Mozilla 1.7.8 and up, running on Linux.
However, before using Web access, it is necessary to perform a preliminary configuration of IPmux-24. When using a Web browser, pay attention to the following points: Enable scripts Configure the firewall that is probably installed on your PC to allow access to the destination IP address Disable pop-up blocking software (such as Google Popup Blocker); you may also have to configure your spyware/adware protection program to accept traffic from/to the destination IP address Browsers store the last viewed pages in a special cache. To prevent configuration errors, it is absolutely necessary to flush the browsers cache whenever you return to the same screen.
General Web Browsers Operating Procedures

To manage IPmux-24 via Web browser: 1. Open the Web browser. 2. Enter the IP address of IPmux-24 in the address field of the browser in the following format: http://IP address (IP address stands for the actual IPmux-24 IP address). 3. After entering the address, press <Enter> to command the browser to connect. 4. After the opening window is displayed, click LOGIN. 5. Perform log-in. You will see the main menu. 6. Use standard browser operating procedures to perform the desired activities. At the left-hand bottom corner, the Web terminal provides some auxiliary management tools: Status shows the number of users currently managing IPmux-24 Trace opens an additional pane for system messages, progress indicators (ping, software and configuration file downloads) and alarms. It is recommended to keep the trace pane open all the time. Refresh All refreshes all display elements.
Working with RADview

RADview-SC/TDMoIP is a user-friendly and powerful SNMP-based application for management and service provisioning. It offers pseudowire service provisioning, as well as embedded element management capabilities.
IPmux-24 Ver. 3.5
3-17
Chapter 3 Operation
RADview-SC/TDMoIP provides a dedicated graphical user interface (GUI) for monitoring RAD products via their SNMP agents. RADview agent for IPmux-24 is bundled in the RADview-SC/TDMoIP package for PC (Windows-based) or Unix. For more details about this network management software, and for detailed instructions on how to install, set-up and use RADview contact your local distributor or refer to the RADview-SC/TDMoIP documentation.
Working with SNMP

IPmux-24 can be managed via a third-party SNMP-based NMS (refer to Chapter 5 for trap list).
Menu Maps
Use these menu trees as a reference aid while performing configuration and control functions. Chapter 4 illustrates menus and explains parameters.
Device Info
System name System location Contact person
Host IP
IP ad dress IP m ask DHCP Read Comm unity Write Comm unity Trap Comm unity Encapsulation
Encapsula tion
Host T agging Host VLAN ID Host VLAN Priority
Target Para ms
Name Message Processing Model Security Model Security Name Security Level
Manager List
IP address Trap mask
Users
Secur ity Name Authentication Proto col Authentication Password Privacy Proto col Privacy Password
Target Address
Name IP Addr ess Params Name Address Mask Tag List
SNMPv3 Settings Management Main Menu

Invento ry Config uration Monito ring Diagnostics Utilities Device info SNMPv3 Host IP Manager list SNMP Engine ID SNMPv3 Settings Management access Alarm trap mask Users Targets & Notify SN MPv1/v3 Mapping SN MPv3 F actory Defaults Su mmary Target Table Su mmary User Table
Targets and Notify

Target Params Target Address Notify Trap
Configuration
System Physica l Layer Connection Bridge QoS Router
System
Managem ent System clock C ontrol p ort Syslog D ate/Tim e Protectio n O AM F actory default
Notify
Name Tag
Management Access
User Access Telnet/SSH Access Web Access SNMP Access RADIUS Authen tication RADIUS Parameters
User Acce ss
User name Per mission Access 'su' passwo rd New passw ord Co nfirmation
Trap
Trap Name Notify N ame
Router
Static Ro ute Table D efault G ateway
Alarm Trap Mask

Alarm ID Trap status
RA DIUS Parameters
Server IP Address Sh ared Secret Nu mber of Retries Timeout Au thentication Po rt Accountin g Port
Figure 3-7. Main Menu > Configuration > System > Management
3-18
IPmux-24 Ver. 3.5

NTP S ervers
NTP Server Admin St atus UDP Port St ratum
Chapter 3 Operation
System Clock
Mase r clock Mast er source Fall b ack clo ck Fall b ack sou rce
Dual Homing
Protection mode Revertive mode Wait to Restore Sh ut Down Duratio n Upon Flip Set Active Port
Main Menu
Invento ry Config uration Monito ring Diagnostics Utilities
Control Port Configuration

System Physica l Layer Connection Bridge QoS Managem ent System clock Control p ort Syslog Date/Tim e Protectio n O AM F actory default
System
Baud Rate
Sysl og
Device Logging Status Device UDP Port Facility Severity Level Server Param eters
Bundle Protection
Primary Bu ndle ID Secondary Bundle ID Redundan cy Type Recovery WT R
Da te/Time
Sys tem Dat e Sys tem Tim e Broadcast Mode Poll Interval UTC Offset NTP Servers
RFER (Proprietary)
Rin g Administrative Statu s Keep Alive Tx Tim e Keep Alive Drops To Fall PT P VLAN ID Mcast VLA N ID
ERP (G.8032)
Rin g Numb er Ad min Status Bridge Nu mber East Port Number West Port Number RPL Port WT R Guard Tim er Ho ldoff Tim er R-APS Vid R-APS Me l Tra ffic VLANs Force SF Comman d Rin g Port Paramet ers
Protection
Dual Homin g Bundle Protection RFER (Prop rietary) ERP (G .8032)
CFM
See Figure 3-9
Ring Port P arameters

Eas t mepid Eas t md Eas t ma West mepid West md West ma
Factory Def ault

Full Except manag ement
Figure 3-8. Configuration > System

Management System clock Control port Date/Tim e Protection CFM CFM Maintenance D omains OAM Maintenance Protoco l Type CF M Maintenance D omains Factory default Associat ions Standard OAM MAC A ddress MD Nam e Form at MD Nam e Standard OAM EtherType MA Name Format MD Level MA Name Mainten ance Associations CCM Interval MEP
System
MEP
Admin Status Primary VID Primary PO RTID Destination Address Type Rem ote MEP IDs Destination MAC Address Default CCM/LTM P riority CCI Enabled Continuity Verification Mode Services
Services
Perfo rmance Monitoring Prior ity Delay Object ive Delay Variation Objective Event Repo rt Fram e Loss Ratio Fram e Above Delay Fram e Above Delay Variation Unavailabilit y Ratio
Figure 3-9. Configuration > System > OAM
IPmux-24 Ver. 3.5
3-19
Chapter 3 Operation
Configuration
System Physical layer Connection Bridge QoS
Physical Layer
TDM interface type TDM ETH LAG Link OAM External clock interface
TDM (E1)
Administrative status Transmit clock source Source clock quality Trail mode Line type Line interface Idle code Send upon fail OOS code OOS signaling Mark signaling code Space signaling code Ethernet network type
TDM (T1)
Administrative status Transmit clock source Source clock quality Rx sensitivity Trail mode Line type Line interface Line length or Line BildOut Restoration time Idle code Send upon fail OOS code Signaling mode OOS signaling Mark signaling code Space signaling code Ethernet network type
Or
ETH Configuration
Administrative status Auto negotiation Max capability advertised Speed & Duplex
LAG
LAG Enable Aggregator
Link OAM
Link OAM Descriptors Link OAM Parameters
Link OAM Descriptors

Descriptor Number OAM Mode OAM Rate Limit
Link OAM Parameters

OAM Status Descriptor Number
Figure 3-10. Configuration > Physical Layer

Configuration
Connection
PW Host IP Bundle ID Connection mode PSN type DS0 bundle Bundle connection
PW Host IP
IP address IP mask PW encapsulation
PW Encapsulation
Host Tagging Host VLAN ID Host VLAN Priority
Figure 3-11. Configuration > Connection > PW Host IP

Bundle Connection
Destination IP Address Bundle Name Next Hop IP TOS Connection Status Destination Bundle Redundancy Function TDM Bytes In Frame Payload Format Far End Type OAM Connectivity Jitter Buffer Sensitive OOS Mode VLAN Tagging Source IP Address
Configuration
Connection
Figure 3-12. Configuration > Connection (TDMoIP CE Connection and UDP/IP PSN)
3-20
IPmux-24 Ver. 3.5
Chapter 3 Operation
Bundle Connection
Destination IP Address Bundle Name MPLS Egress Label Connection Status Destination Bundle Redundancy Function Next Hop Type Next Hop IP Address TDM Bytes In Frame Payload Format Far End Type OAM Connectivity Jitter Buffer Sensitive OOS Mode VLAN Tagging
Configuration
Connection
Figure 3-13. Configuration > Connection (TDMoIP CE Connection and MPLS/ETH PSN)
Bundle Connection
Destination IP Address Bundle Name Connection Status Destination Bundle Redundancy Function Next Hop Type Next Hop MAC Address TDM Bytes In Frame Far End Type Jitter Buffer Sensitive OOS Mode VLAN Tagging Source IP Address
Configuration
Connection
Figure 3-14. Configuration > Connection (TDMoIP CE Connection and MAC/ETH PSN)
Bundle Connection Configuration
Connection
Destination IP Address Bundle Name Next Hop IP TOS Connection Status Destination Bundle Redundancy Function TDM Frames In Packet Payload Format OAM Connectivity Jitter Buffer Sensitive OOS Mode VLAN Tagging Source IP Address
Figure 3-15. Configuration > Connection (CESoPSN Connection and UDP/IP PSN)
Destination IP Address MPLS Egress Label Connection Status Destination Bundle Redundancy Function Next Hop Type Next Hop IP Address TDM Frames In Packet Payload Format OAM Connectivity Jitter Buffer Sensitive OOS Mode VLAN Tagging Source IP Address
Connection
Figure 3-16. Configuration > Connection (CESoPSN Connection and MPLS/ETH PSN)
IPmux-24 Ver. 3.5
3-21
Chapter 3 Operation

Connection
Destination IP Address Bundle Name Connection Status Destination Bundle Redundancy Function Next Hop Type Next Hop MAC Address TDM Frames In Packet Jitter Buffer Sensitive OOS Mode VLAN Tagging Source IP Address
Figure 3-17. Configuration > Connection (CESoPSN Connection and MAC/ETH PSN)
Destination IP Address Bundle Name Next Hop IP TOS Connection Status Destination Bundle TDM Bytes In Packet Payload Format OAM Connectivity Jitter Buffer Sensitive OOS Mode VLAN Tagging Source IP Address
Connection
PWHost IP Bundle ID Connection mode PSN type DS0 bundle Bundle connection
Figure 3-18. Configuration > Connection (SAToP Connection and UDP/IP PSN)
Destination IP Address Bundle Name MPLS Egress Label Connection Status Destination Bundle Redundancy Function Next Hop Type Next Hop IP Address TDM Bytes In Packet Payload Format OAM Connectivity Jitter Buffer Sensitive OOS Mode VLAN Tagging Source IP Address
Connection
Figure 3-19. Configuration > Connection (SAToP Connection and MPLS/ETH PSN)
Destination IP Address Bundle Name Connection Status Destination Bundle Redundancy Function Next Hop Type Next Hop MAC Address TDM Bytes In Packet Jitter Buffer Sensitive OOS Mode VLAN Tagging Source IP Address
Connection
Figure 3-20. Configuration > Connection (SAToP Connection and MAC/ETH PSN)
3-22
IPmux-24 Ver. 3.5
Chapter 3 Operation
Bundle Connection
Destination IP Address Bundle Name Next Hop IP TOS Connection Status Redundancy Function Payload Format OAM Connectivity VLAN Tagging Source IP Address
Configuration
Connection
Figure 3-21. Configuration > Connection (HDLC Connection and UDP/IP PSN)
Connection
Destination IP Address Bundle Name MPLS Egress Label Connection Status Destination Bundle Redundancy Function Next Hop Type Next Hop IP Address Payload Format OAM Connectivity VLAN Tagging Source IP Address
Figure 3-22. Configuration > Connection (HDLC Connection and MPLS/ETH PSN)
Connection
Destination IP Address Bundle Name Connection Status Destination Bundle Redundancy Function Next Hop Type Next Hop MAC Address VLAN Tagging Source IP Address
Figure 3-23. Configuration > Connection (HDLC Connection and MAC/ETH PSN)
Configuration
Bridge
VLAN Mode Forwarding Mode Aging Time Static MAC Table Erase MAC Table Bridge Port VLAN Membership
Bridge Port (User)

Ingress Filtering Accept Frame Type Port VID/Stacking VID Default Priority Tag Tag Handling
Egress Tagged Ports Egress Untagged Ports
Figure 3-24. Configuration > Bridge

Configuration
Classification QoS
Priority Rate Limitation
Priority
Classification Mapping
Network ETH1 Network/User ETH2 User ETH3 TDM PW
Rate Limitation
Egress Ingress
Egress
Rate Limitation
Ingress
Rate Limitation Burst Size Limit Packet Type
Figure 3-25. Configuration > QoS
IPmux-24 Ver. 3.5
3-23
Chapter 3 Operation
Statistics
TDM physical layer Connection Bridge OAM
Monitoring
Statistics Status Event log Managers
OAM
15 Min. Counters 24 Hours Counters Service Counters
Status
Diagnostics loopback Physical ports LAG Connection OAM (802.1ag) System Clock Protection
Physical Ports
ETH physical layer SFP
SFP
Link status
Protection
Ring Dual Homing
Event Log
Read log file Clear log file
Managers
Connected Managers
Figure 3-26. Monitoring

Ping Diagnostics
Ping Trace route Loopback Self test results Interface Destination IP address VLAN tagging VLAN ID VLAN priority Number of frames to send Ping Send
Trace Route
Destination IP address VLAN tagging VLAN ID VLAN priority Trace route send
Loopback
Loopback state Inband loop detection (T1 only)
Self Test Results

Framer test Bridge test
Figure 3-27. Diagnostics

Utilities
File Utilities Reset
File Utilities
Download/upload using FTP
Download/Upload Using FTP

File name Command Server IP Retry timeout Total timeout View transfer status
Figure 3-28. Utilities
3.5
Turning IPmux-24 Off
To power off the unit: Remove the power cord from the power source.
3-24
Turning IPmux-24 Off
IPmux-24 Ver. 3.5
Chapter 4 Configuration
This chapter illustrates the configuration IPmux-24 screens and explains their parameters. Menu trees of the IPmux-24 management software are shown in Chapter 3.
4.1
Configuring for Management
Usually, initial configuration of the management parameters is performed via ASCII terminal. Once the IPmux-24 host IP parameters are set, it is possible to access the unit via Telnet, Web terminal or RADview for operation configuration. Perform the following steps in order to configure IPmux-24 for management: To configure IPmux-24 for management: 1. Connect an ASCII terminal to the RS-232 control port of IPmux-24. 2. Log in as Superuser (su). 3. Enable or disable the IPmux-24 DHCP client. 4. Assign an IP address to IPmux-24. 5. Assign a subnet mask and a default gateway. 6. Configure the SNMP communities. 7. Set a manager IP address.
Note
Make sure that you save your settings at each configuration screen.
Configuring IP Host Parameters

IPmux-24 can be managed by a network management station, which is located on the LAN connected to the one of the units Ethernet ports. In order to establish a proper connection, it is necessary to configure the following: host IP address, subnet mask, default gateway, its trap, read and write communities. In addition, you can enable or disable DHCP client of the device.
Configuring DHCP Client

To facilitate integration of a new device into a DHCP IP network, if no IP address has been manually configured, IPmux-24 automatically requests one from the DHCP server upon booting. IPmux-24 is shipped with the DHCP client set to Enable.
IPmux-24 Ver. 3.5
4-1
Managing IP Parameters of the IPmux-24 Host

IPmux-24 allows entering IP parameters manually or using parameters acquired from the DHCP server. To define the IP parameters manually: 1. Disable DHCP client. IPmux-24 releases the current IP address by sending the release message to the DHCP server, sets all host IP parameters to 0.0.0.0 and reboots itself automatically. 2. From the Host IP menu (Configuration > System > Management > Host IP), perform the following: Select IP Address to define the host IP address Select IP Mask to define the host IP mask. Configuration>System>Management>Host IP 1. IP address 2. IP mask 3. DHCP 4. DHCP Status 5. Read Community 6. Write Community 7. Trap Community 8. Encapsulation > Please select item <1 to 8> ESC-prev.menu; !-main menu; &-exit ... () ... (0.0.0.0) (Enable) > ... (public) ... (private) ... (SNMP_trap) >
1 M/ 1 C
Figure 4-1. Host IP Menu

To acquire a new IP address from the DHCP server: 1. From the Host IP menu, set all host IP parameters (host IP, IP mask and default gateway) to 0.0.0.0 or reset the IPmux-24 configuration to the default settings, including the management parameters. IPmux-24 reboots automatically. After returning on line, IPmux-24 starts broadcasting requests for an IP address. When the DHCP server is found, IPmux-24 receives from it all necessary host IP parameters. 2. From the Host IP menu, select DHCP Status to view the current status of the IPmux-24 DHCP client: Server ID IP address of the DHCP server Lease expiration time Time when the IP address lease expires Current status Current status of the DHCP client (Locating available server, Waiting for confirmation of lease, etc)
Note
When the IP address lease is going to expire, DHCP client automatically requests lease extension.
4-2
IPmux-24 Ver. 3.5
Defining Read, Write and Trap Communities

You have to assign names for the read, write and trap communities. To define read, write and trap communities: From the Host IP menu (Figure 4-1), configure the following: Select Read Community to enter the name of a community with read-only authorization (up to 10 alphanumeric characters, case-sensitive). Select Write Community to enter the name of a community with write authorization (up to 10 alphanumeric characters, case-sensitive). Select Trap Community to enter the name of a community to which IPmux-24 will send traps (up to 10 alphanumeric characters, case-sensitive).
Configuring the Host Encapsulation

IPmux-24 management software allows you to create a dedicated management VLAN in order to separate management traffic from the user data. To configure the host encapsulation: 1. From the Host menu (Figure 4-1), select Encapsulation. The Encapsulation menu is displayed (see Figure 4-2). 2. From the Encapsulation menu, do the following: Select Host tagging, and choose Tagged or Untagged to consider or ignore the VLAN tagging of the management traffic coming from the management station. If the host tagging is enabled, select Host VLAN ID to enter the ID of the host VLAN (14094). If the host tagging is enabled, select Host VLAN priority to specify priority of the host VLAN (07).
Note
If the Host tagging is enabled and the bridge VLAN mode is set to Unaware (see Configuring the Ethernet Bridge, IPmux-24 can be managed only using the host VLAN ID and only via the network port. Management via the user ports is disabled.
Configuration>System>Management>Host IP>Encapsulation 1. Host Tagging 2. Host VLAN ID [1 - 4094] 3. Host VLAN Priority [0 - 7] > ESC-prev.menu; !-main menu; &-exit 1 M/ 1 C (Tagged) ... (300) ... (7)
Figure 4-2. Encapsulation Menu
IPmux-24 Ver. 3.5
4-3
Assigning a Name to the Unit and Its Location

The IPmux-24 management software allows you to assign a name to the unit and its location to distinguish it from the other devices installed in your system. To assign a name to IPmux-24 and its location: 1. From the System menu, select Management. The Management menu is displayed. 2. From the Management menu, select Device Info. The Device Info menu appears (see Figure 4-3). 3. From the Device Info menu, select System Name and enter the desired name for the IPmux-24 device. 4. Select System Location, and enter the desired name for the current IPmux-24 location. 5. Select Contact Person, and enter the desired name for the IPmux-24 contact person. Configuration>System>Management>Device info 1. System Name 2. System Location 3. Contact Person > Please select item <1 to 3> ESC-prev.menu; !-main menu; &-exit ... (IPmux-24) ... (the location of this device) ... (name of contact person)
1 M/ 1 C
Figure 4-3. Device Info Menu
Defining Network Managers

Define or modify the network management stations to which the SNMP agent of IPmux-24 will send traps. Up to 16 managers can be defined. In addition, you can enable or disable manager stations to receive traps. To add a network manager: 1. From the Management menu, select Manager List. The Management List menu appears (see Figure 4-4). 2. From the Management List menu, type a to add a management station. The Management List menu display changes, entering the Add mode (see Figure 4-5). 3. When in Add mode, perform the following: Select IP Address, and enter the IP address of the management station. Select Trap Mask, and select Enable or Disable to mask or unmask traps for the selected management station. Press <Esc> to return to the Edit mode.
4-4
IPmux-24 Ver. 3.5
To edit the manager list: 1. From the Management List menu, move the cursor to the Trap Mask field by pressing arrow buttons. 2. Toggle between Enable and Disable to mask or unmask traps for the selected management station. Refer to trap list in Chapter 5 for the detailed description of the IPmux-24 traps. To remove a network manager: 1. From the Manager List, select a network manager that you intend to remove. 2. Type r to remove the selected network manager from the list. To clear the manager list: From the Manager List, type c to delete all network managers.
Configuration>System>Management>Manager List Manager ID 1 IP Address 172.18.159.35 Trap mask Disable ... (Disable)
1. Change cell
A Add R Remove C Clear ESC-prev.menu; !-main menu; &-exit; ?-help
1 M/ 1 C
Figure 4-4. Manager List Menu

Configuration>System> Management > Manager ID 1. IP Address 2. Trap Mask > ESC-prev.menu; !-main menu; &-exit Manager List (1) ... (0.0.0.0) ... (Disable) 1 M/ 1 C
Figure 4-5. Manager List Menu, Add Mode
Configuring SNMPv3
IPmux-24 supports SNMP version 3 entity, providing secure access to the device by authenticating and encrypting packets transmitted over the network. Follow these steps to configure the SNMPv3 entity: 1. Define SNMP engine ID 2. Enable SNMPv3. 3. Add a new user or use a default user account. 4. Add a new notification entry. 5. Assign traps to notification entries. 6. Configure target (NMS) parameters.
IPmux-24 Ver. 3.5
4-5
7. Specify target address, define its parameter set and assign notification tags. 8. Map SNMPv3 setting to SNMPv1 settings. This is necessary for coexistence of different SNMP versions. For example, when managing an SNMPv3 agent via an SNMPv1 NMS.
Configuring the SNMP Engine ID

Engine ID is an alphanumeric string used for identification of the IPmux-24 agent in the SNMPv3 environment. The engine ID must be unique to allow the user to query the SNMP engine. It must be defined prior to enabling SNMPv3 functionality. The length of the string is up to 27 characters. To define the SNMP engine ID: From the SNMP Engine ID menu (Configuration > System > Management > SNMP Engine ID), select Remaining Bytes and define the value of the engine ID section reserved for user SNMP engine identification. The value is automatically translated in hexadecimal format and displayed in the read-only Engine ID field. Configuration>System> Management>SNMP Engine ID Engine ID ... (800000a40400000000) Engine ID Config Type > (Text) 1. Remaining Bytes ... () > ESC-prev.menu; !-main menu; &-exit
1 M/ 1 C
Figure 4-6. SNMP Engine ID Menu
Enabling SNMPv3
To enable SNMPv3: 1. From the Management menu (Configuration > System > Management), select SNMPv3 to enable the SNMPv3 entity. The SNMPv3 Settings line is added to the Management menu. 2. From the Management menu, select SNMPv3 Settings. The SNMPv3 Settings menu is displayed. The SNMPv3 Settings menu includes the following information: Engine Boots (The number of times that the SNMP engine has reinitialized since its identification was last configured.) Engine Time (The number of seconds since the last SNMP engine boot) SNMP Message Size (The maximum length of an SNMP message (in octets) that the SNMP engine can send or receive and process.)
4-6
IPmux-24 Ver. 3.5
Configuration>System>Management>SNMPv3 Settings Engine Boots (2) Engine Time (276) SNMP Message Size ... (1500) 1. Users > 2. Targets & Notify > 3. SNMPv1/v3 Mapping > 4. SNMPv3 Factory Defaults 5. Summary User Table [] 6. Summary Target Table [] > ESC-prev.menu; !-main menu; &-exit
1 M/ 1 C
Figure 4-7. SNMPv3 Settings Menu
Adding SNMPv3 Users

IPmux-24 supports up to ten SNMPv3 managers with different authorization and privacy attributes.
Note
Access control policy is defined via the vacmSecurityToGroupTable and vacmAccessTable tables, which can be accessed via an SNMP browser only.
To add an SNMPv3 user: 1. From the Users menu (Configuration > System > Management > SNMPv3 Settings > Users), perform the following: Select Security Name and enter security name for a new user (up to 32 alphanumeric characters). Select Authentication Protocol and define the authentication protocol to be used for authenticating the user: usmNoAuthProtocol (No authentication is performed) usmHMACMD5AuthProtocol (MD5 protocol) usmHMACSHAAuthProtocol (SHA protocol) Select Privacy Protocol and define the type of privacy protocol to be used for encryption: usmNoPrivProtocol (Privacy protocol is not used) usmDESPrivProtocol (DES protocol) Select Authentication Password (eight characters) and define the authentication password of the user. This is not available if authentication has been disabled. Select Privacy Password (eight characters) and define the private key used for encryption. This is not available if privacy has been disabled.
IPmux-24 Ver. 3.5
4-7
2. To view the summary of the SNMPv3 user configuration, select Summary User Table from the SNMPv3 Settings (Configuration > System > Management > SNMPv3 Settings) menu. To delete an SNMPv3 user: 1. From the Users menu (Configuration > System > Management > SNMPv3 Settings > Users), type f or b to select an SNMPv3 user. 2. Type r to delete the selected user.
Adding Notification Entries

To add a notification entry: 1. From the Targets & Notify menu (Configuration > System > Management > SNMPv3 Settings > Targets & Notify), select Notify. The Notify menu is displayed (see Figure 4-8). 2. From the Notify menu, perform the following: Name (ASCII string identifying the notification entry) Tag (A tag value to be associated with the current notification entry. This tag will be used to identify the current notification entry when configuring the target address.) Configuration>System>Management> SNMPv3 Settings> Target & Notify > Notify Type > (trap)
1. Name ...(agnCounterChange) 2. Tag ...(unmasked) > ESC-prev.menu; !-main menu; &-exit
1 M/ 1 C
Figure 4-8. Notify Menu
Assigning Traps
One or more traps must be assigned to each notification entry. To assign traps to notification entries: 1. From the Target & Notify menu, select Trap. The Trap menu is displayed. 2. From the Trap menu, configure the following: Trap Name (A trap to be assigned to the selected notification entry). Notify Name (Notification entry name)
4-8
IPmux-24 Ver. 3.5
Configuration>System>Management> SNMPv3 Settings> Target & Notify > Trap 1. Trap Name >( Link Up) 2. Notify Name >( linkUp) > ESC-prev.menu; !-main menu; &-exit
1 M/ 1 C
Figure 4-9. Trap Menu
Configuring Target Parameters

Target is an SNMPv3 network management station to which IPmux-24 is going to send trap notifications. A set of parameters has to be configured and assigned to each target. To configure target parameters: 1. From the Targets & Notify menu (Configuration > System > Management > SNMPv3 Settings > Targets & Notify), select Target Params. The Target Params menu is displayed (see Figure 4-10). 2. From the Target Params menu, configure the following: Name (An ASCII string identifying current set of target parameters) Message Processing Model (The Message Processing Model to be used when generating SNMP messages using this entry): SNMPv1 SNMPv2c SNMPv2u SNMPv3 Security Model (The Security Model to be used when generating SNMP messages using this entry): Any SNMPv1 SNMPv2c User-Based Security Model (USM) Not defined Security Name (Identification of the principal on whose behalf SNMP messages are to be generated using this entry. This can be either SNMPv3 user or SNMPv1/SNMPv2 community string.) Security Level (The level of security to be used when generating SNMP messages using this entry): noAuthNoPriv (Authorization and privacy are disabled) authNoPriv (Authorization is enabled, privacy is disabled) authPriv (Authorization and privacy are enabled)
IPmux-24 Ver. 3.5
4-9
Configuration>System>Management> SNMPv3 Settings> Target & Notify > Target Params
1. 2. 3. 4. 5.
Name Message Processing Model Security Model Security Name Security Level
... > > ... >
() () () () ()
> ESC-prev.menu; !-main menu; &-exit
1 M/ 1 C
Figure 4-10. Target Params Menu
Configuring Target Address

Each target must have a valid IP address. Also, a previously configured parameter set and notification tags must be assigned to the target. To configure the target address: 1. From the Targets & Notify menu (Configuration > System > Management > SNMPv3 Settings > Targets & Notify), select Target Address. The Target Address menu is displayed (see Figure 4-11). 2. From the Target Address menu, configure the following: Name (ASCII string identifying the target) IP Address (Valid IP address of the NMS. The IP address must be in xxx.xxx.xxx.xxx:162 format, where 162 is a standard SNMP port used for sending traps.) Params Name (Name of the previously defined target parameter set to be assigned to this target) Tag List (List of previously defined notification tags). 3. To view the summary of the SNMPv3 target configuration, select Summary Target Table from the SNMPv3 Settings (Configuration > System > Management > SNMPv3 Settings) menu.
Configuration>System>Management> SNMPv3 Settings> Target & Notify > Target Address
1. 2. 3. 4.
Name IP Address Params Name Tag List
... ... ... ...
() () () ()
1 M/ 1 C
Figure 4-11. Target Address Menu
4-10
IPmux-24 Ver. 3.5
Mapping SNMPv1 to SNMPv3

IPmux-24 supports coexistence of different SNMP versions by mapping SNMPv1/SNMPv2 community name to the SNMPv3 security name value. The mapping is performed according to the RFC 3584 requirements. To map SNMPv1 to SNMPv3: 1. From the SNMPv3 Settings menu (Configuration > System > Management > SNMPv3 Settings), select SNMPv1/v3 Mapping. The SNMPv1/v3 Mapping menu is displayed. 2. From the SNMPv1/v3 Mapping menu, select the following: Community Index (SNMP community index) Community Name (SNMPv1/SNMPv2 community name) Security Name (SNMPv3 security name to be mapped to the SNMPv1/SNMPv2c community name) Transport Tag (Specifies a set of transport endpoints which are used in two ways: To specify the transport endpoints from which an SNMP entity accepts management requests To specify the transport endpoints to which a notification may be sent using the community string matching the corresponding instance of community name.) Configuration>System>Management> SNMPv3 Settings> SNMPv1/v3 Mapping 1. 2. 3. 4. Community Index Community Name Security Name Transport Tag ... ... ... ... () () () ()
1 M/ 1 C
Figure 4-12. SNMPv1/v3 Mapping Menu
Configuring Management Access Permissions and Methods

The user access permissions, as well as SNMP, Telnet and Web access authorization are configured via the Management Access menu.
Defining Management Access Permissions

IPmux-24 management software allows you to define new users, their management and access rights. Only superusers (su) can create new users, the regular users are limited to changing their current passwords, even if they were given full management and access rights.
IPmux-24 Ver. 3.5
4-11
To add a new user: 1. Make sure that you logged in as su. 2. From the Management Access menu, select User access. The User Access menu is displayed (see Figure 4-13). 3. From the User Access menu, do the following: Select User name, and enter a name for a new user. Select Permission, and specify the users access rights (full control or read-only). Select Access, and specify the users access methods (ASCII terminal, Telnet, Web browser, Telnet and Web browser, or all of them).
Note
When changing Permission and Access for an existing user, make sure to fill out the SU Password, New Password and Confirm fields (you can enter the current user password for the New Password and Confirm).
Select 'su' Password, and enter your current superuser password. Select New Password, and assign a password to a new user name. Select Confirm and re-enter the new user password to confirm it. Save new settings by typing S, when asked. To delete an existing user: From the User Access menu, do the following: Type F to display a user that you intend to delete. Select 'su' password, and enter your current superuser password. Type D to delete the current user.
Configuration>System>Management>Management access>User access 1. 2. 3. 4. 5. 6. > Please select item <1 to 6> ESC-prev.menu; !-main menu; &-exit User name Permission Access 'su' password New password Confirmation ... > > ... ... ... (su) (Full Control) (All) () () ()
1 M/ 1 C
Figure 4-13. User Access Menu
4-12
IPmux-24 Ver. 3.5
Controlling Management Access

You can enable or disable access to the IPmux-24 management system via an SNMP, Telnet or Web-based application. By disabling SNMP, Telnet or Web, you prevent unauthorized access to the system when security of the IPmux-24 IP address has been compromised. When SNMP, Telnet and Web access is disabled, IPmux-24 can be managed via an ASCII terminal only. In addition, you can limit access to the device to only the stations defined in the manager list. Table 4-1 details management access implementation, depending whether the network managers are defined or not. To define the management access method: 1. From the Management menu, select Management Access. The Management Access menu appears. 2. From the Management Access menu, select Telnet/SSH Access to configure Telnet access, select SNMP Access to configure SNMP access, or select Web Access to configure Web access. 3. Define access mode for each management method: Enable (Telnet, SNMP or Web access is enabled) Disable (Telnet, SNMP or Web access is disabled) Managers Only (Access is allowed only for the stations appearing in the manager list) Enable Secure (Secure access (SSH-enabled for Secure Shell or SSL-enabled for Web) is enabled) Manager Only Secure (Secure access (SSH-enabled for Secure Shell or SSLenabled for Web) is allowed only for the stations appearing in the manager list).
Table 4-1. Management Access Implementation

Access Method Mode Who is Allowed to Access IPmux-24 Network Manager(s) Defined Enable SNMP Access Disable Managers Only Enable/Enable Secure Telnet Access Disable Managers Only/ Managers Only Secure Enable/Enable Secure Web Access Disable Managers Only/ Managers Only Secure Anybody Nobody Only defined network managers Anybody Nobody Only defined network managers Anybody Nobody Only defined network managers Network Manager(s) not Defined Anybody Nobody Nobody Anybody Nobody Nobody Anybody Nobody Anybody
IPmux-24 Ver. 3.5
4-13
Configuration>System>Management>Management Access 1. 2. 3. 4. 5. User Access TELNET/SSH access WEB access SNMP access Access Policy > > > > >
(Enable) (Enable) (Disable)
1 M/ 1 C
Figure 4-14. Management Access Menu
Configuring RADIUS Client

The RADIUS (Remote Authentication Dial-In User Service) is a client/server security protocol. Security information is stored in a central location, known as the RADIUS server. RADIUS clients, such as IPmux-24, communicate with the RADIUS server to authenticate users. To define the access policy: From the Management Access menu (Configuration > System > Management > Management Access), select the following: 1st level authentication method: RADIUS IPmux-24 uses authentication database stored at the RADIUS server to check if the entered user name and password match the data server records. User authentication fails if one the following occurs: No user name record is found Password does not match user name Connection to the RADIUS server is lost. Local IPmux-24 uses its internal authentication database
Note
When RADIUS is selected as the first authentication method, RADIUS Parameters is displayed in the Management Access menu.
2nd level authentication method: Local IPmux-24 uses local authentication database None No authentication is performed To configure RADIUS client: From the Management Access menu, select RADIUS Parameters and configure the following: Server IP Address (IP address of the RADIUS server) Shared Secret (The shared secret is a password used by RADIUS to authenticate the client. IPmux-24 encrypts the user-password, if present; using the secret it shares with the RADIUS server.): Any alphanumeric string up to 16 characters
4-14
IPmux-24 Ver. 3.5
Number of retries (The number of retries to be made when sending request to the RADIUS server): 15 Timeout (The maximum time IPmux-24 waits for a single request response from the RADIUS server (in seconds). After this time the request is retransmitted.): 160 Authentication Port (The UDP port number to be used for the RADIUS authentication application. Make sure to define the same value in the RADIUS server.): any valid UDP port number Accounting Port (The UDP port number to be used for the RADIUS accounting. Make sure to define the same value in the RADIUS server.): any valid UDP port number.
Configuring Control Port Parameters

Configuration parameters of the IPmux-24 control port, except for the baud rate are set at the factory and cannot be changed by the user (see Figure 4-15). These parameters have the following values: Data bits 8 Parity None Stop bits 1 Flow control None.
To select the baud rate: 1. From the System menu, select Control port. The Control Port menu is displayed (see Figure 4-15). 2. From the Control Port menu, select Baud rate, and configure baud rate of the IPmux-24 terminal control port to the desired value (9600, 19200, 38400, 57600 or 11520 bps). Configuration>System>Control port Data bits Parity Stop bits Flow control 1. Baud rate (bps) > ESC-prev.menu; !-main menu; &-exit 1 M/ 1 C (8) (None) (1) (None) (115200)
> > >
Figure 4-15. Control Port Menu
IPmux-24 Ver. 3.5
4-15
4.2
Configuring for Operation
The recommended operation configuration procedure for IPmux-24 includes the following stages: 1. Defining system clock. 2. Configuring IPmux-24 interfaces (Ethernet, E1, T1) at the physical level. 3. Creating bundles by allocating timeslots to them. 4. Connecting bundles by directing them to remote device.
Setting Device-Level Parameters

At the device level, you have to configure the system clock to provide a single clock source for E1/T1 links of the device and a ring application to protect the Ethernet transmission path.
Configuring the System Clock

IPmux-24 system timing mechanism ensures a single clock source for all TDM links by providing the master and fallback clocks. If the system clock is locked to one of the IPmux-24 TDM links, it is necessary to define clock source (adaptive or loopback). See Configuring the E1 TDM Interface for details. To configure the system clock: 1. From the System menu, select System clock. The System clock menu appears (see Figure 4-16). 2. From the System clock menu, configure the required parameters, according to Table 4-2.
Table 4-2. System Clock Parameters

Parameter Master clock Description Master clock type Possible Values Adaptive Clock is regenerated from an E1 or T1 bundle Rx Clock E1/T1 recovered Rx clock is used as the Tx clock Default: Rx Clock Master source Source of the master clock, when the master clock type is adaptive or Rx Channel 1 Channel 4 Master clock is provided via one of the TDM links. E1/T1 links can be locked to adaptive, loopback or external clock. External clock Clock is received from an external clock source clock via the EXT. CLK connector Default: Channel 1
4-16
IPmux-24 Ver. 3.5
Installation and Operation Manual Parameter Fallback clock Description Fallback clock type Possible Values
Adaptive Clock is regenerated from an E1 bundle Rx Clock E1/T1 recovered Rx clock is used as the Tx clock Default: Adaptive
Fallback source
Source of the fallback clock
Channel 1 Channel 4 Master clock is provided via one of the TDM links. E1/T1 links can be locked to adaptive or loopback clock. Default: Channel 1
Note
If the configured fallback clock source fails, the internal timing is used as the fallback clock source instead.
Configuration>System>System clock 1. 2. 3. 4. > Please select item <1 to 4> S - save ESC-prev.menu; !-main menu; &-exit Master clock Master source Fall back clock Fall back source > > > > (Rx Clock) (Channel 1) (Adaptive) (Channel 1)
1 M/ 1 C
Figure 4-16. System Clock Menu
Selecting the TDM Interface Type

Before configuring the IPmux-24 TDM interfaces, it is necessary to select their type (E1 or T1). To select the TDM interface type: 1. From the Configuration menu, select Physical layer. The Physical Layer menu appears (see Figure 4-17). 2. From the Physical Layer menu, select TDM interface type, and choose the type of the IPmux-24 TDM links (E1 or T1).
IPmux-24 Ver. 3.5
4-17
Configuration>Physical layer 1. 2. 3. 4. 5. > Please select item <1 to 4> ESC-prev.menu; !-main menu; &-exit TDM interface type TDM ETH LAG External clock interface > (E1) > > > (Balanced)
1 M/ 1 C
Figure 4-17. Physical Layer Menu
Configuring the Resilient Fast Ethernet Ring (RFER)

Ring redundancy, implemented by means of the RAD-proprietary protocol, provides protection for the Ethernet transmission path, and is especially suited for MAN and dark fiber applications. A single ring may include up to 16 IPmux-24 devices and up to 16 VLAN (including an additional VLAN for management traffic). Two additional VLANs are reserved for the ring controls. All the keep-alive and ring status notifications are delivered using: Point-to-point (PtP) messages, sent between adjacent ring members. Multicast (Mcast) messages, sent to all ring members.
Note
VLANs used for the ring status traffic (4001 and 4002 by default) must be unique within the given network.
Before enabling ring protection, make sure that the following parameters have been configured: Host IP address (see Configuring IP Host Parameters) PW host IP address (see (Configuring Bundle Connections) Bridge set to VLAN-aware mode (see Configuring the Ethernet Bridge) All network ports set to be egress tagged ports in the ring VLAN (see Configuring the VLAN Membership) Priority classification method is set to 802.1p (see Configuring the Traffic Priority) Priority mapping (see Configuring the Traffic Priority): Priority 7 (reserved for the ring status traffic) mapped to traffic class 2 Priority 6 (PW traffic) mapped to traffic class 1. The PW traffic priority should be lower than the ring status traffic priority. Rest of the priorities mapped to traffic class 0.
4-18
IPmux-24 Ver. 3.5
To configure the RFER: From the Protection menu (Configuration > System > Protection > Ring (Proprietary)), configure the necessary parameters and enable the ring redundancy (see Figure 4-18 and Table 4-3).
Chapter 7 details how to configure a typical ring protection application.

Configuration>System>Protection>RFER (Proprietary) Group ID (1) Port Members (1,2) Redundancy Method (Ring) 1. 2. 3. 4. 5. > Ring Administrative Status Keep Alive Tx Time[Msec][2 - 100] Keep Alive Drops To Fall[1 - 10] PTP VLAN ID Mcast VLAN ID (Down) (13) (3) (4001) (4002))
... ... ... ...
Please select item <1 to 5> ESC-prev.menu; !-main menu; &-exit
1 M/ 1 C
Figure 4-18. RFER (Proprietary) Menu Table 4-3. RFER Parameters

Parameter Ring Administrative Status Description Administrative status of the redundancy ring Possible Values Up Protection ring is operational Down Protection ring is not operational Disabled Operation of an active protection ring has been suspended Default: Down Keep Alive Tx Time Period of time between two keep-alive PtP messages 2100 msec Default: 13
Keep Alive Drops To Fall PTP VLAN ID
Number of keep-alive PtP messages not 110 received from adjacent ring member, Default: 3 after which IPmux-24 declares link failure VLAN ID for point-to-point messages. This VLAN ID must not be used by other services in the network. VLAN ID for multicast messages. This VLAN ID must not be used by other services in the network. 14094 Default: 4001 14094 Default: 4002
Mcast VLAN ID
Configuring the IEEE 8032 Ethernet Ring (ERP)

A G.8032 Layer-2 Ethernet ring is a logical ring, defined as a set of IEEE 802.1 compliant bridges and protect against link and node failures. To achieve this,
IPmux-24 Ver. 3.5
4-19
every IPmux-24 in the ring has two network ports (East and West) connected it to adjacent devices. The user Ethernet port serves as an access point to the ring. Before configuring the ERP, perform the following: 1. Define separate two hosts IP addresses with VLAN tagging: Management host IP address for management and ERP traffic PW host IP for pseudowire (user) traffic 2. Set the bridge to operate in VLAN-aware mode. 3. Add dedicated VLANs for ERP traffic (see Configuring the VLAN Membership) 4. Configure OAM (CFM) MEPs for ring ports if you intend to use CC messages for ring failure detection (see Configuring the Service OAM). To configure the ERP 1. From the Protection menu, select ERP (G.8032). The ERP (G.8032) menu is displayed. 2. From the ERP menu, enter a to add a new IEEE 8032 Ethernet ring and configure its parameters according to Configuration>System>Protection>ERP (G.8032) 1. Ring Number 2. Admin Status 3. Bridge Number 4. East Port Number 5. West Port Number 6. RPL Port 7. WTR (min) 8. Guard Timer (msec) 9. Holdoff Timer (msec) 10.R-APS Vid 11.R-APS Mel 12.Traffic VLANs 13.Force SF Command 14.Port Specific Parameters > > (1) (Enabled) (1) (1) (2) (East) (5) (500) (0) (5) (3) (1,3,100,101,4000) (SF East)
Please select item <1 to 14> F- Forward Ring; B-Backward Ring; A-Add Ring; R-Remove Ring ESC-prev.menu; !-main menu; &-exit
1 M/ 1 C
Figure 4-19. ERP (G.8302) Menu Table 4-4. ERP (G.8302) Parameters
Parameter Ring Number Description Administrative status of the redundancy ring Possible Values 1
4-20
IPmux-24 Ver. 3.5
Installation and Operation Manual Parameter Admin Status Description Administrative status of the ring node Possible Values
Enable The node is operational Disable The node is not operational Default: Down
Bridge Number East Port Number West Port Number RPL Port
Number of the node bridge Configures one of the Ethenet ports to be the East port of the node Configures one of the Ethenet ports to be the West port of the node Defines the East or West port of the node to be the RPL Owner Period of time used by RPL Owner to verify that the ring has stabilized before blocking the RPL after signal recovery
1 1, 2 1, 2 East, West, N/A Default: N/A 512 min Default: 5
WTR Timer
Guard Timer
Period of time during which all received 10 msec2 sec R-APS messages are ignored by the ERP Default: 500 msec mechanism. This prevents the ring nodes from receiving outdated R-APS messages circulating the network. Period of time during which the underlying Ethernet layer attempts to filter out intermittent link faults before reporting them to the ERP mechanism VLAN ID fro R-APS messages 010000 msec Default: 0
Holdoff Timer
R-APS VID
04095 Default: 0
R-APS MEL
Maintenance Entity Group Level providing a communication channel for ring automatic protection switching (R-APS) information Protected VLANs for the user management or data traffic. When defining traffic VLANs, administrative mode of the ring node must be set to Disable. Type a to add a traffic VLAN, or d to delete it.
07 Default: 0
Traffic VLANs
04095
IPmux-24 Ver. 3.5
4-21
Chapter 4 Configuration Parameter Force SF Command Description Forces Signal Failure (SF) or clears SF for East and West port. This allows the user to manually block/unblock the ring port, causing unblocking or blocking of the RPL port.
Installation and Operation Manual Possible Values eastOn Forces SF condition on East port westOn Forces SF condition on West port eastClear Clears SF condition on East port westClear Clears SF condition on West port off Disables the Force SF command Default: off
Ring Port Parameters
Defines OAM CFM Continuity Check (CC) attributes for each node port, if you intend to use Y.1731 CCMs for additional monitoring of the ring links. See below.
To configure node ports: 1. From the ERP (G.8302) menu, select Port-Specific Parameters. The Port-Specific Parameters menu is displayed. 2. From the Port-Specific Parameters menu, configure MEP ID, maintenance domain and maintenance association values of the East and West ports of the node according to you network requirements. Configuration>System>Protection>ERP(G.8302)>Port-Specific Parameters Ring Number 1 1. East mepid 2. East md (maintenance domain level) 3. East ma (maintenance association Vlan Id) 4. West mepid 5. West md (maintenance domain level) 6. West ma (maintenance association Vlan Id) > Please select item <1 to 6> F- Forward Ring; B-Backward Ring; ESC-prev.menu; !-main menu; &-exit (1) (2) (3) (3) (4) (5)
1 M/ 1 C
Figure 4-20. Port-Specific Parameters Menu
Configuring the LAG

The network and network/user ports can be operated as a single logical interface (Link Aggregation Group, or LAG), using link aggregation in accordance with IEEE 802.3ad without LACP (Link Aggregation Control Protocol). In the virtual link group only one link transmits at a time. If a failure occurs on the transmitting link, IPmux-24 switches to the standby link in the group. The flip is performed by reassigning destination ports.
4-22
IPmux-24 Ver. 3.5
To configure the LAG: From the LAG menu (Configuration > Physical layer > LAG), select LAG Enable and set it to Enabled. The network and network/user ports are aggregated into a single logical link. Their bridge and VLAN membership parameters become identical. The LAG status can be verified via the LAG Status screen (see the Displaying the LAG Status section below).
Note
In the LAG mode the first link to have its Administrative Status to be set to Up
becomes an active link of the group and starts data transmission. Refer to the Configuring Ethernet Interfaces section below for instructions on how to change the administrative status of the link.
In the LAG mode both Ethernet links receive data, but only one of them
transmits.
Configuration>Physical layer>LAG LAG ID (1) 1. LAG Enable 2. Aggregator > Please select item <1 to 2> ESC-prev.menu; !-main menu; &-exit
... (Enabled) >
1 M/ 1 C
Figure 4-21. LAG Menu, Link Aggregation is Enabled
Configuring Dual Homing

In the dual homing (1:1) mode both network and network/user ports operate independently, one of them is active, the other on standby. The traffic is automatically switched to the standby port in case the active port or its link fails. To configure the dual homing: 1. From the Dual Homing menu (Configuration > System > Protection > Dual Homing), set Protection Mode to Dual Homing. New parameters become available in the menu. 2. Configure the dual parameters as explained in Table 4-5. The dual homing status can be verified via the Dual Homing Status screen (see the Displaying the Dual Homing Status section below).
IPmux-24 Ver. 3.5
4-23
Configuration>System>Protection>Dual Homing Group ID (1) Primary Port > (Network-ETH1) Secondary Port > (Network/User-ETH2) 1. 2. 3. 4. 5. > Protection mode Revertive mode Wait to Restore (sec)[0 - 720] ... Shut Down Duration Upon Flip[0 - 30] ... Set Active Port > (Dual Homing) (Not Revertive) (0) (0) (None)
1 M/ 1 C
Figure 4-22. Dual Homing Menu, Dual Homing is Enabled Table 4-5. Dual Homing Parameters
Name Revertive mode Description Port recovery mode Possible Values Non-revertive Traffic keeps on being sent over the secondary port (network/user port) after the primary port recovery Revertive Traffic is switched back to the primary port (network port) after the primary port recovery Default Non-revertive Wait to Restore Period of time between link 0720 sec restoration and using the link for Default 0 the data transfer Period of time during which the failed link suspends its transmission in order to inform the remote device of the link failure 030 sec Default 0
Shut Down Duration Upon Flip
Note: Shut Down Duration Upon Flip value must be smaller than Wait to Restore value.
Set Active Port Defining permanently active port None None of the ports is configured as permanently active Low (Secondary) Network/user port is configured as permanently active High (Primary) Network port is configured as permanently active Default None
4-24
IPmux-24 Ver. 3.5
Configuring Bundle Protection

Bundle redundancy mechanism protects pseudowire traffic in case of network path failure. The user defines different network paths for the primary and secondary pseudowire bundles. Actual configuration of bundles as members of redundancy mechanism is performed via Bundle Connection menu (see the Configuring Bundle Connections section below). The same bundles must be configured as primary and secondary via the Bundle Protection menu. Configuration order (first bundle connection, then bundle protection, or vice versa) is not relevant. To configure bundle redundancy: 1. From the Bundle Protection menu (Configuration > System > Protection > Bundle Protection), type a to add redundancy bundles (see Figure 4-23). The Bundle Protection menu display changes, entering the Add mode (see Figure 4-24). 2. Add primary and secondary bundles and configure all required parameters, according to Table 4-6.
Note
Primary and secondary bundles must belong to the same TDM link.
Configuration>System>Protection>Bundle Protection Primary Secondary Redundancy Type Recovery WTR
A-Add;R-Remove;C-Clear ESC-prev.menu; !-main menu; &-exit
1 M/ 1 C
Figure 4-23. Bundle Protection Menu, No Redundant Bundles Exist

Configuration>System>Protection>Bundle Protection 1. Primary Bundle ID[1 - 127] 2. Secondary Bundle ID[1 - 127] 3. Redundancy Type 4. Recovery 5. WTR[0 - 99] > ... (1) ... (1) > > (1+1) (Non Revertive)
... (10)
1 M/ 1 C
Figure 4-24. Bundle Protection Menu, Add Mode
IPmux-24 Ver. 3.5
4-25
Table 4-6. Bundle Protection Parameters

Name Primary Bundle Description Active (primary) bundle. Make sure that the same bundle is configured as primary via Bundle Connection menu. Redundant (secondary) bundle. Make sure that the same bundle is configured as secondary via Bundle Connection menu. Bundle protection type Possible Values Whole bundle range supported by IPmux-24 Default 1
Secondary Bundle
Whole bundle range supported by IPmux-24 Default 1
Redundancy Type
1+1 Both the primary and secondary bundles transmit pseudowire traffic, but only the active bundle receives pseudowire traffic, while the redundant bundle ignores the Rx path. 1:1 Only primary bundle transmits and receives pseudowire traffic while the secondary bundle is kept on standby. Default 1+1
Note: If both primary and secondary bundles are routed to the same target device, their destination bundles must be the same. See the Configuring Bundle Connections section below for instructions on how to define destination bundles.
Recovery Recovery mode for the primary bundle in 1:1 redundancy Revertive PW traffic switches back to primary bundle when the primary path is restored Non-revertive PW traffic switches back to primary bundle when the secondary path fails Default Non-revertive WTR Period of time that IPmux-24 waits before trying to recover the primary bundle once conditions causing bundle failure have been cleared. Relevant for 1:1 redundancy only. 099 sec Default 10
Removing Protected Bundles

Protected bundles can be removed via Bundle Protection menu. Before removing protected bundles delete or disable them as explained in the Configuring Bundle
Connections section below.

To remove protected bundles: 1. From the Bundle Protection menu, use arrow keys to select a protected bundle pair. 2. Type r to remove selected bundles.
4-26
IPmux-24 Ver. 3.5
Configuration>System>Protection>Bundle Protection Primary 1 3 Secondary 2 4 Redundancy Type 1:1 1+1 Recovery Revertive WTR 2
A-Add;R-Remove;C-Clear ESC-prev.menu; !-main menu; &-exit
1 M/ 1 C
Figure 4-25. Bundle Protection Menu, 34 Bundle Pair is Selected
Clearing all Protected Bundles

All protected bundles can be cleared via Bundle Protection menu. Before clearing protected bundles, delete or disable them as explained in the Configuring Bundle
Connections section below.

To clear all protected bundles: From the Bundle Protection menu, type c to clear all protected bundles.
Configuring the Service OAM

IPmux-24 supports Ethernet service OAM (Operation, Administration, and Maintenance) to detect network faults and measure network performance. This is performed according to ITU 802.1ag requirements. To configure the service OAM: 1. Add and configure maintenance domain(s) (MD). 2. Configure maintenance associations for the added MDs. 3. Configure MA endpoints, referred as MEPs. 4. Configure MEP services.
Adding and Configuring Maintenance Domains

MDSs are domains for which the connectivity faults are managed. Each MD is assigned a name which must be unique among all those used or available to an operator. The MD name facilitates easy identification of administrative responsibility for the maintenance domain. You can add up to 16 maintenance domains. To add and configure maintenance domains: 1. From the OAM CFM menu (Configuration > System > OAM > CFM), modify the OAM MAC address and/or the Ethertype as needed. See Table 4-7.
IPmux-24 Ver. 3.5
4-27
Configuration>Application>OAM>CFM 1. Maintenance Domains > 2. Standard OAM MAC Address ... 3. Standard OAM EtherType[0 - ffff] > Please select item <1 to 3> ESC-prev.menu; !-main menu; &-exit 1 M/2 C
(01-80-C2-00-00-30) ...(8902)
Figure 4-26. OAM CFM Menu Table 4-7. OAM CFM Parameters
Name Standard OAM MAC Address Description Specifies the MAC Address for OAM CFM messages Possible Values Multicast MAC address Default 01-80-C2-00-00-30 0ffff Default 8902
Standard OAM EtherType
Specifies the EtherType for OAM CFM messages
2. Select Maintenance Domains to continue configuration. The Maintenance Domain (MD) menu appears. If you havent defined any maintenance domains yet, the menu is empty. See Table 4-8 for a description of the maintenance domain parameters. 3. Type a to add a new MD. The maintenance domain parameters appear with default values. Configuration>Applications>OAM>CFM>Maintenance Domains MD ID 1. 2. 3. 4. Protocol Type MD Name Format MD Name MD Level[0-7] ... (1) (Standard) (String) (DEFAULT) (3)
> ... ...
Please select item <1 to 4> S-Save ESC-prev.menu; !-main menu; &-exit
1 M/2 C
Figure 4-27. Maintenance Domain Menu, Adding MD

4. If you wish to modify an existing MD, type f or b to scroll forward or backward respectively to the MD to be modified. 5. Modify the MD parameters as desired.
4-28
IPmux-24 Ver. 3.5
6. Save the maintenance domain. If you added a new maintenance domain, the Maintenance Associations parameter appears in the menu (see Figure 4-28). 7. Refer to Configuring Maintenance Associations for a description of configuring maintenance associations. Configuration>Applications>OAM>CFM>Maintenance Domains MD ID 1. 2. 3. 4. 5. Protocol Type MD Name Format > MD Name ... MD Level ... Maintenance Associations > ... (1) (Standard) (String) (DEFAULT) (3)
Please select item <1 to 5> A-Add New MD; F-Forward; B-Backward; D-Delete ESC-prev.menu; !-main menu; &-exit
1 M/2 C
Figure 4-28. Maintenance Domain Menu Table 4-8. Maintenance Domain Parameters
Name MD ID Protocol Type Description The maintenance domains identification Specifies whether to use the RAD proprietary OAM mechanism or the standard OAM mechanism Possible Values 116 Standard Pre-Standard Default Standard
Note: If Pre-Standard is selected, it imposes the following: MD Format = None, MD Level = 3, MA Format = String, CC Interval = 1sec.
MD Name Format Specifies the format of the maintenance domain name None No name defined String Alphanumeric value DNS DNS format MACAndUINT MAC and UINT format Default String MD Name Specifies the maintenance domain name According to MD Name Format Default DEFAULT (if MD Name Format is String) MD Level Specifies the level of the OAM maintenance domain, used to differentiate between different levels of service providers 07 Default: 3
IPmux-24 Ver. 3.5
4-29
Configuring Maintenance Associations

A maintenance domain contains up to 16 maintenance associations, for each of which you can configure the continuity check interval and up to 8191 maintenance endpoints (MEPs). To configure maintenance associations: 1. In the OAM CFM Maintenance Domain menu, select Maintenance Associations. The Maintenance Associations menu appears. If you havent defined any maintenance associations yet, the menu is empty. See Table 4-9 for a description of the maintenance association parameters. ...OAM>CFM>Maintenance Domains>Maintenance Associations
A-Add New MA ESC-prev.menu; !-main menu; &-exit
1 M/2 C
Figure 4-29. Maintenance Associations Menu, No Maintenance Associations Defined

...OAM>CFM>Maintenance Domains>Maintenance Associations MD ID MA ID 1. 2. 3. 4. MA Name Format MA Name CCM Interval MEP > > > ... (1) ... (1) (String) ... (DEFAULT) (1 Second)
Please select item <1 to 4> A-Add New MA; F-Forward; B-Backward; D-Delete ESC-prev.menu; !-main menu; &-exit
1 M/2 C
Figure 4-30. Maintenance Associations Menu

2. If you wish to add a new maintenance association, type a. The maintenance association parameters appear with default values.
4-30
IPmux-24 Ver. 3.5
...OAM>CFM>Maintenance Domains>Maintenance Associations MD ID MA ID 1. MA Name Format 2. MA Name 3. CCM Interval > > (String) ... (1 Second) ... (1) ... (1)
(DEFAULT)
Please select item <1 to 3> S-Save ESC-prev.menu; !-main menu; &-exit
1 M/2 C
Figure 4-31. Maintenance Associations Menu, Adding MA

3. Modify the maintenance association parameters as desired. 4. Save the maintenance association. If you added a new maintenance association, the MEP parameter appears in the menu (see Figure 4-30). 5. Refer to Configuring Maintenance Endpoints for a description of configuring maintenance endpoints.
Table 4-9. Maintenance Association Parameters

Name MD ID MA ID MA Name Format Description Displays the maintenance domain ID to which the maintenance association belongs The maintenance associations identification Specifies the format of the maintenance association name Possible Values 116 116 String Alphanumeric value PrimaryVid primary VLAN Uint Unsigned 16-bit integer ICC Defined by ITU-T Y.1731 (32) Default String MA Name Specifies the maintenance association name. According to MA Name Format Default DEFAULT (if MA Name Format is String) CCM Interval Specifies the interval between continuity check messages. 100ms 1 sec 10 sec 1 min 10 min Default 1 sec
IPmux-24 Ver. 3.5
4-31

A maintenance association contains up to 8191 maintenance endpoints (MEPs). To add the first maintenance endpoint to a maintenance association: 1. In the OAM CFM Maintenance Association menu, select MEP. The menu for adding a MEP appears. IPmux-24 ...OAM>CFM>Maintenance Domains>Maintenance Associations>MEP MD ID MA ID 1. MEP ID[1 8191] > (0) ... (1) ... (1)
1 M/2 C
Figure 4-32. Menu for Adding MEP

2. Select MEP ID and enter a value from 1 to 8191. The specified MEP ID appears at the top of the menu and the MEP parameters appear in the menu as illustrated in Figure 4-33. ...OAM>CFM>Maintenance Domains>Maintenance Associations>MEP MD ID MA ID MEP ID 1. 2. 3. 4. 5. 6. 7. 8. 9. Admin Status Primary VID[1 - 4094] ... Primary PORTID > Destination Address Type Remote MEP IDs > Destination MAC Address ... Default CCM/LTM Priority[0 - 7] ... CCI Enabled Continuity Verification Mode > Services ... (1) ... (1) ... (1) (Up) (1) (Network-ETH1) (Multicast) (4) (01-80-C2-00-00-33) (0) (True) (CC Based)
Please select item <1 to 9> D-Delete ESC-prev.menu; !-main menu; &-exit
1 M/2 C
Figure 4-33. MEP Menu with MEP Parameters, Adding MEP

3. Configure the MEP parameters as described in Table 4-10.
4-32
IPmux-24 Ver. 3.5
4. Configure the MEP services as described in Configuring Maintenance Endpoint
Services Table 4-10. MEP Parameters

Name MD ID MA ID MEP ID Description Displays the corresponding maintenance domain ID Displays the corresponding maintenance association ID Specifies the MEP identification. Possible Values 116 116 18191 Default 1 Admin Status Specifies whether the MEP is available for operation Down Up Default Down Primary VID Specifies the VLAN ID used for OAM messages for the MEP 14094 Default 1
Note: Service OAM traffic cannot be run over user ports, when its VLAN ID is the same as the management host VLAN ID. You can either run it via a network port or change its VID.
Primary PORTID Specifies the port used for OAM messages for the MEP Network-ETH1 Network/User-ETH2 User-ETH3 Default Network-ETH1 Destination Address Type Specifies the type of MAC address in OAM messages. Multicast addresses are used to send the OAM messages to more than one recipient, while a unicast address is used for just one recipient Multicast RAD proprietary multicast address of Standard multicast address Unicast User-defined unicast address Default Multicast Remote MEP IDs Specifies the remote MEP IDs with which the MEP IDs in incoming OAM messages are compared, therefore every units MEP ID must remain unique. 18191
Note: If protocol type is Standard and destination address type is Multicast, five remote MEP IDs are allowed, otherwise only one remote MEP ID is allowed
Destination MAC Address Specifies the MAC address to which OAM messages are sent. A valid MAC address Default 01-80-C2-00-0033
Note: This parameter is configurable only if the Destination Address Type is set to Unicast, otherwise this parameter is read-only and contains the standard OAM MAC address configured in the OAM CFM menu (see Figure 4-26).
IPmux-24 Ver. 3.5
4-33
Chapter 4 Configuration Name Default CCM/ LTM Priority Description Specifies the priority with which continuity check/ link trace messages are sent if no services are defined for the MEP. If a service is defined for the MEP, the continuity check/ link trace messages are sent with the highest priority defined in the MEP. Specifies whether continuity check messages are sent for this MEP
Installation and Operation Manual Possible Values 07 Default 0
CCI Enabled
True False Default True
Continuity Verification Mode
Specifies whether the continuity check method is based on loopback messages or based on incoming performance monitoring messages
LB Based Continuity check method is based on Loopback messages CC Based Continuity check method is based on incoming performance monitoring messages Default CC Based
Configuring Maintenance Endpoint Services

You can configure up to three services in one MEP. Each service is created with performance monitoring disabled by default. When performance monitoring is disabled, no other MEP service parameters can be configured for that service. To configure the MEP services: 1. In the OAM CFM MEP menu, select Services. The MEP services menu for service 1 appears as illustrated in Figure 4-34 if performance monitoring is disabled, otherwise it appears as illustrated in Figure 4-35. ...Maintenance Domains>Maintenance Associations>MEP>Services Service [1 3] 1. Performance Monitoring ... (1) (Disabled)
Please select item <1 to 1> F-Forward ESC-prev.menu; !-main menu; &-exit
1 M/2 C
Figure 4-34. MEP Services Menu, Performance Monitoring Disabled

2. Type f to advance to the next service if desired. 3. To enable performance monitoring, select Performance Monitoring. The MEP services menu appears as illustrated in Figure 4-35. 4. Configure the MEP services parameters as described in Table 4-11.
4-34
IPmux-24 Ver. 3.5
IPmux-24 ...Maintenance Domains>Maintenance Associations>MEP>Services Service [1 3] 1. 2. 3. 4. Performance Monitoring Priority[0-7] Delay Objective (msec)[1-1000] Delay Variation Objective (msec)[1-1000] ... (1) (Enabled) (0) (1) (1)
... ... ... > > > >
Event Report 5. Frame Loss Ratio 6. Frame Above Delay 7. Frame Above Delay Variation 8. Unavailability Ratio > Please select item <1 to 8> F-Forward; S-Save ESC-prev.menu; !-main menu; &-exit
1 M/2 C
Figure 4-35. MEP Services Menu, Performance Monitoring Enabled Table 4-11. MEP Service Parameters
Name Service Performance Monitoring Description Three services are automatically created for each MEP, for which you can configure event reporting Enables/disables performance monitoring for the service. If performance monitoring is disabled, no event reporting is done. Specifies the priority of OAM messages from this service Possible Values 13 Enabled Disabled Default Disabled 07 Default 0 Delay Objective Specifies the planned delay for the service 11000 Default 1 Delay Variation Objective Specifies the planned delay variation for the service 11000 Default 1
Priority
To configure MEP service event reporting: 1. In the OAM CFM MEP Services menu, navigate to the service for which you wish to configure the event reporting, and verify that performance monitoring is enabled (see Figure 4-35). 2. Select the event counter reporting that you would like to configure (Frame Loss Ratio, Frames Above Delay, Frames Above Delay Variation, Unavailability Ratio).
IPmux-24 Ver. 3.5
4-35
The MEP service event reporting menu appears as illustrated in Figure 4-36 if the event reporting type is None, otherwise it appears as illustrated in Figure 4-37 for event Select Frame Loss Ratio or Unavailability Ratio, or Figure 4-38 for event Frames Above Delay or Frames Above Delay Variation. ... Maintenance Associations>MEP>Services> Frame Loss Ratio 1. Event Reporting Type > > Please select item <1 to 1> ESC-prev.menu; !-main menu; &-exit (None)
1 M/2 C
Figure 4-36. MEP Services Event Reporting Menu, Event Reporting Type None
1. Select Event Reporting Type and set it to the desired value (None, Log, Trap, Log & Trap). Setting it to None disables the reporting of the event. If you set Event Reporting Type to any value except None, the MEP service event reporting menu appears as illustrated in Figure 4-37 for event Select Frame Loss Ratio or Unavailability Ratio, or Figure 4-38 for event Frames Above Delay or Frames Above Delay Variation. 2. Configure the MEP service event reporting parameters as described in Table 4-12. ... Maintenance Associations>MEP>Services> Frame Loss Ratio 1. Event Reporting Type 2. Rising Threshold > 3. Falling Threshold > > Please select item <1 to 3> S-Save ESC-prev.menu; !-main menu; > (1E-10) (1E-10) (Log)
&-exit
1 M/2 C
Figure 4-37. MEP Service Event Reporting Menu for Frame Loss Ratio or Unavailability Ratio
... Maintenance Associations>MEP>Services> Frames Above Delay 1. Event Reporting Type 2. Rising Threshold ... 3. Falling Threshold ... 4. Sampling Interval (Sec) > Please select item <1 to 4> S-Save ESC-prev.menu; !-main menu; ... (1) (1) ... (Log)
(1)
&-exit
1 M/2 C
Figure 4-38. MEP Service Event Reporting Menu for Frames Above Delay or Frames Above Delay Variation
4-36 Configuring for Operation IPmux-24 Ver. 3.5
Table 4-12. MEP Service Event Reporting Parameters

Parameter Event Reporting Type Description Specifies the type of event reporting Possible Values None No event reporting is done Log The event report is written in the event log. Trap An SNMP trap is sent to report the event Log & Trap The event is reported via the event log and an SNMP trap Default None Rising Threshold A value above this threshold within the sampling interval for the particular event is considered as rising event occurred For Frames Above Delay or Frames Above Delay Variation: 14,294,967,296 For Unavailability Ratio or Frame Loss Ratio: 1E-3 1E-4 1E-5 1E-6 1E-7 1E-8 1E-9 1E-10 Default: Falling Threshold A value below this threshold within the sampling interval for the particular event is considered as falling event occurred For Frames Above Delay or Frames Above Delay Variation: 1 For Unavailability Ratio or Frame Loss Ratio: 1E-10
For Frames Above Delay or Frames Above Delay Variation: 14,294,967,296 For Unavailability Ratio or Frame Loss Ratio: 1E-3 1E-4 1E-5 1E-6 1E-7 1E-8 1E-9 1E-10 Default: For Frames Above Delay or Frames Above Delay Variation: 1 For Unavailability Ratio or Frame Loss Ratio: 1E-10
IPmux-24 Ver. 3.5
4-37
Chapter 4 Configuration Parameter Sampling Interval Description Specifies the interval in seconds over which the data is sampled and compared with the rising and falling thresholds
Installation and Operation Manual Possible Values 14,294,967,296
Note: This parameter is available only for events Frames Above Delay and Frames Above Delay Variation.
Configuring the Link OAM

IPmux-24 supports a passive mode of a link-layer OAM (IEEE 802.3ah). The unit responds to loopback requests and queries about its configuration parameters. There is no performance measurement and the information exchanged about the state of the link being monitored is minimal. To configure link OAM for a port: 1. Configure the link OAM descriptors 2. Associate the Ethernet port to the appropriate link OAM descriptor 3. Enable link OAM for the port.
Configuring Link OAM Descriptors

Descriptors are sets of link OAM parameters that are assigned to an Ethernet port. To configure OAM descriptors: 1. From the Link OAM Descriptors menu (Configuration > Physical Layer > Link OAM > Link OAM Descriptors), select Descriptor Number and enter a descriptor number. 2. Configure the link OAM descriptor parameters as described in Table 4-13. To remove an OAM descriptor: From the Link OAM Descriptors menu, select an OAM descriptor and type r to remove it.
Configuration>Physical layer>Ethernet>Link OAM>Link OAM Descriptors 1. Descriptor Number 2. OAM Mode 3. OAM Loopback Rx ... > > (1) (Passive) (Ignore) (60) 1 M/2 C
4. OAM Rate Limit [1 100] ... ESC-prev. menu; !-main menu; &-exit
Figure 4-39. Ethernet Link OAM Descriptors Menu
4-38
IPmux-24 Ver. 3.5
Table 4-13. Link OAM Descriptor Parameters

Parameter Descriptor Number Mode Description Specifies the identification of the OAM descriptor Values 1511
Specifies whether to initiate OAM activities or Passive IPmux-24 does not initiate just respond to OAM activities. Currently OAM activities, but responds to them, IPmux-24 supports passive mode only. with the possible exception of OAM loopback, depending on the setting of OAM Loopback Rx Default Passive
OAM Loopback Rx
Specifies whether to react to or ignore OAM loopbacks
Ignore IPmux-24 ignores OAM loopback messages ProcessIPmux-24 processes OAM loopback messages Default Ignore
OAM Rate Limit
Specifies how many OAM frames can be sent in one second
1100 Default 10
Assigning Link OAM Descriptor to an Ethernet Port

To enable link OAM on an Ethernet port, you must assign a traffic descriptor to it. To assign link OAM descriptor to an Ethernet port: 1. From the link OAM menu (Configuration > Physical Layer > Link OAM > Link OAM Parameters), select one of the Ethernet ports 2. Attach or detach a traffic descriptor to it (see Table 4-14). Configuration>Physical layer>Link OAM>Link OAM Parameters Ethernet Port 1. OAM Status 2. Descriptor Number Please select item <1 to 2> F-Forward; B-Backward; D-Detach ESC-prev. menu; !-main menu; &-exit 1 M/2 C > ... ... (1) (Disable) (-)
Figure 4-40. Ethernet Link OAM Parameters Menu Table 4-14. Link OAM Parameters
Parameter OAM Status Description Values
Specifies if OAM is enabled or disabled for Enable OAM is enabled the port. You must associate a descriptor to Disable OAM is disabled the port before you can enable OAM. Default Disable
IPmux-24 Ver. 3.5
4-39
Chapter 4 Configuration Parameter Descriptor Number Description Specifies the OAM descriptor to use for the port Values
Setting Physical Layer Parameters

Configuring the E1 TDM Interface
The E1 and T1 interfaces of IPmux-24 are configured via the TDM menu. To configure the E1 interface: 1. From the Physical Layer menu, select TDM. The TDM (E1) menu appears (see Figure 4-41). 2. From the TDM (E1) menu, type F to select one of the 4 E1 links that you intend to configure. 3. From the TDM (E1) menu, configure the E1 interface parameters (see Table 4-15).
Table 4-15. E1 Interface Parameters

Name Administrative Status Description Administrative status of E1 interface Possible Values Up Traps and alarms on E1 link are enabled Down Traps and alarms on E1 link are disabled Default Up Transmit clock source Source of the E1 transmit clock Adaptive Clock is regenerated from an E1 bundle Loopback E1 recovered Rx clock is used as the Tx clock Internal Tx clock is received from an internal oscillator System System clock is used as the Tx clock Default Adaptive Source clock quality Quality of the adaptive clock used by the device Stratum 1/PRC G.811 Stratum 2/Type II G.812 Stratum 3/Type IV G.812 Stratum 3E/Type III G.812 Other/Unknown Default Other/Unknown
4-40
IPmux-24 Ver. 3.5
Installation and Operation Manual Name Description Possible Values
Note: The Source Clock Quality parameter is relevant only when the Tx clock source is set to adaptive or loopback. In adaptive clock mode only the Stratum 1/PRC G.811 and Stratum 2/Type II G.812 values are available when the Ethernet network type is set to LAN. In the adaptive clock mode setting the source clock quality parameter to Other/Unknown achieves shorter clock trace time, but may cause occasional clock instability. This means that when the master clock quality is Stratum 3 or better, or a short tracing time is not required, the source clock quality parameter must not be set to Other/Unknown.
Trail Mode Controls the end-to-end transfer of TDM OAM (Operation, Administration, and Maintenance) data in framed mode, when the payload format is set to V2 Termination Trail-extended mode is disabled; the TDM networks function as separate OAM domains Extension Trail-extended mode is enabled; OAM data is passed between the TDM networks Default Termination Line type E1 framing mode Unframed G.703 Framing is not used Framed G.704 G.704 framing, CRC-4 function disabled Framed G.704 CRC4 G.704 framing, CRC-4 function enabled Framed MF CAS enabled, CRC-4 function disabled Framed MF CRC4 CAS enabled, CRC-4 function enabled Default Framed G.704 Line Interface Operating mode of the LIU receive path LTU DSU Default DSU Idle Code Code transmitted to fill unused timeslots in the E1 frames Notification sent to the E1 side if Ethernet link fails 0ff Default 7E OOS Code Out-of-service code AIS Alarm indication signal Default OOS code OOS code Code to be sent to the E1 side if Ethernet link fails 0ff Default FF
Send Upon Fail
IPmux-24 Ver. 3.5
4-41
Chapter 4 Configuration Name OOS signaling Description Out-of-service signaling method for the framed MF or framed MF CRC4 line types only. OOS signal is sent toward the IP path when loss of signal, loss of frame, or AIS is detected at the E1 line. The OOS signal is also sent toward the E1 line when packet receive buffer overrun or underrun occurs.
Installation and Operation Manual Possible Values Space Code specified by the Space Signaling Code parameter is sent Mark Code specified by the Mark Signaling Code parameter is sent Space Mark Space code is sent in the first 2.5 seconds, then mark code is sent Mark Space Mark code is sent in the first 2.5 seconds, then space code is sent Default Space
Mark Signaling Code
OOS signaling code sent when the Mark OOS signaling is selected. Relevant for the framed MF or framed MF CRC4 line types only. OOS signaling code sent when the Space OOS signaling is selected. Relevant for the framed MF or framed MF CRC4 line types only.
0f Default D
Space Signaling Code
0f Default 1
Ethernet Network Type Type of the Ethernet network which is WAN Layer 3 network used for the pseudowire connection. LAN Layer 2 network Different network types are Default WAN characterized by different packet delay variation models. This parameter is relevant only when the adaptive clock mode is selected.
Configuration>Physical layer>TDM (E1) Channel ID (1) Restoration time >(CCITT) Signaling mode (CAS Disabled) 1. Administrative Status 2. Transmit clock source 3. Source clock quality 4. Trail Mode 5. Line type 6. Line interface 7. Idle code[0 - ff] (Up) >(Adaptive) >(Other/unknown) (Termination) >(Framed G.704) (LTU) ... (7E)
8. Send upon fail (OOS Code) 9. OOS Code[0 - ff] ... (FF) 10.Ethernet network type >(WAN) > Please select item <1 to 10> ESC-prev.menu; !-main menu; &-exit
1 M/ 1 C
Figure 4-41. TDM (E1) Menu
4-42
IPmux-24 Ver. 3.5
Configuring the E1 External Clock Interface Type

For the units with the E1 user interface it is necessary to define the external clock interface type: balanced or unbalanced. When it is set to unbalanced, connection to the external clock source must be performed via CBLRJ45/2BNC/E1/X adapter cable. To configure the external clock E1 interface type: From the Physical Layer menu (Configuration > Physical Layer), select External Clock Interface and choose its type: balanced or unbalanced.
Configuring the T1 TDM Interface

The procedure for configuring the T1 port is similar to the procedure described above for configuring the E1 port. To configure T1 interface: 1. From the TDM (T1) menu, type F to select one of the T1 links that you intend to configure. 2. From the TDM (T1) menu, configure the T1 interface parameters (see Table 4-16).
Table 4-16. T1 Interface Parameters

Name Administrative Status Description Administrative status of T1 interface Possible Values Up Traps and alarms on T1 link are enabled Down Traps and alarms on T1 link are disabled Default Up Transmit clock source Source of the T1 transmit clock Adaptive Clock is regenerated from an T1 bundle Loopback T1 recovered Rx clock is used as the Tx clock Internal Tx clock is received from an internal oscillator System System clock is used as the Tx clock Default Adaptive Source clock quality Quality of the adaptive clock used by the device Stratum 1/PRC G.811 Stratum 2/Type II G.812 Stratum 3/Type IV G.812 Stratum 3E/Type III G.812 Other/Unknown Default Other/Unknown
IPmux-24 Ver. 3.5
4-43
Chapter 4 Configuration Name Description
Installation and Operation Manual Possible Values
Note: The Source Clock Quality parameter is relevant only when the Tx clock source is set to adaptive or loopback. In adaptive clock mode only the Stratum 1/PRC G.811 and Stratum 2/Type II G.812 values are available when the Ethernet network type is set to LAN. In the adaptive clock mode setting the source clock quality parameter to Other/Unknown achieves shorter clock trace time, but may cause occasional clock instability. This means that when the master clock quality is Stratum 3 or better, or a short tracing time is not required, the source clock quality parameter must not be set to Other/Unknown.
Rx sensitivity Maximum attenuation of the receive signal that can be compensated for by the interface receive path Controls the end-to-end transfer of TDM OAM (Operation, Administration, and Maintenance) data in framed mode, when the payload format is set to V2 Short haul: -10 dB Long haul: -32 dB Default Short haul Termination Trail-extended mode is disabled; the TDM networks function as separate OAM domains Extension Trail-extended mode is enabled; OAM data is passed between the TDM networks Default Termination Line type T1 framing mode ESF 24 frames per multiframe SF (D4) 12 frames per multiframe Unframed Default ESF Line code Line code and zero suppression method used by the port B7ZS B8ZS AMI Default B8ZS Line Interface Operating mode of the LIU receive path LTU DSU Default DSU Line length Length of a cable in feet between the 0133 ft IPmux-24 T1 port connector and the 133266 ft network access point (DSU mode only) 266399 ft 399533 ft 533655 ft Default: 0133
Trail Mode
4-44
IPmux-24 Ver. 3.5
Installation and Operation Manual Name Line buildOut Description Tx gain level relative to T1 output transmit level (CSU mode only) Possible Values 0 No attenuation
-7.5 Attenuation of 7.5 dB relative to the nominal transmit level -15 Attenuation of 15 dB relative to the nominal transmit level -22 Attenuation of 22 dB relative to the nominal transmit level) Default: -7.5
Restoration time
Time required for the T1 port to return TR-6211 (10 seconds) to normal operation after sync loss Fast (1 second) Default: Fast (1 second)
Idle Code
Code transmitted to fill unused timeslots in the T1 frames Notification sent to the T1 side if Ethernet link fails
0ff Default 7E OOS Code Out-of-service code AIS Alarm indication signal Default OOS code
Send Upon Fail
OOS code
Code to be sent to the T1 side if Ethernet link fails T1 signaling mode
0ff Default FF None Robbed Bit Default None
Signaling mode
OOS signaling
Out-of-service signaling method. OOS signal is sent toward the IP path when loss of signal, loss of frame, or AIS is detected at the T1 line. The OOS signal is also sent toward the T1 line when packet receive buffer overrun or underrun occurs.
Space Code specified by the Space Signaling Code parameter is sent Mark Code specified by the Mark Signaling Code parameter is sent Space Mark Space code is sent in the first 2.5 seconds, then mark code is sent Mark Space Mark code is sent in the first 2.5 seconds, then space code is sent Default Space
Mark Signaling Code
OOS signaling code sent when the Mark OOS signaling is selected
0f (ESF framing) 03 (SF framing) Default 0D (ESF), 01 (SF)
Space Signaling Code
OOS signaling code sent when the Space OOS signaling is selected.
0f (ESF framing) 03 (SF framing) Default 01
IPmux-24 Ver. 3.5
4-45
Chapter 4 Configuration Name Description
Ethernet Network Type Type of the Ethernet network which is WAN Layer 3 network used for the pseudowire connection. LAN Layer 2 network Different network types are Default WAN characterized by different packet delay variation models. This parameter is relevant only when the adaptive clock mode is selected.
Configuration>Physical layer>TDM (T1) Channel ID (1) 1. Administrative status 2. Transmit clock source 3. Source clock quality 4. Rx Sensitivity 5. Trail Mode 6. Line type 7. Line code 8. Line interface 9. Line length (feet) 10. Restoration time 11. Idle Code[0 - ff] 12. Send upon fail 13. OOS code[0 - ff] 14. Signaling mode 15. OOS signaling 16.Mark signaling code[0 - f] 17.Space signaling code[0 - f] 18.Ethernet network type > Please select item <1 to 18> ESC-prev.menu; !-main menu; &-exit (Up) >(Adaptive) >(Other/unknown) (Short haul) (Termination) >(ESF) >(B8ZS) >(DSU) >(0-133) >(TR-621 (10 seconds)) ... (7E) (OOS Code) ... (FF) (Robbed Bit) > (Space) ... (D) ... (1) > (Wan)
1 M/ 1 C
Figure 4-42. TDM (T1) Menu
Configuring Ethernet Interfaces

IPmux-24 includes one network and up to two user Ethernet ports. To configure Ethernet interface: 1. From the Physical Layer menu (Figure 4-17), select ETH. The ETH menu appears (see Figure 4-43). 2. From the ETH menu, type F to select the Ethernet interface that you intend to configure (Network ETH1, Network/User ETH2 or User ETH3). 3. When the required Ethernet interface is displayed, configure the required Ethernet parameters (see Table 4-17).
4-46
IPmux-24 Ver. 3.5
Table 4-17. Ethernet Interface Parameters

Name Administrative Status Description Administrative status of Ethernet interface Possible Values Up Current Ethernet interface is enabled Down Current Ethernet interface is disabled Default Up Auto negotiation Autonegotiation mode Enable Autonegotiation is enabled Disable Autonegotiation is disabled Default Disable (fiber optic interfaces), Enable for (copper interfaces) Max capability advertised Maximum capability to be advertised during the autonegotiation process 10BaseT Half Duplex 10BaseT Full Duplex 100BaseT Half Duplex 100BaseT Full Duplex 1000BaseX Full Duplex Default 100baseT Full Duplex Speed & Duplex Rate and duplex mode, if the autonegotiation is disabled 10BaseT Half Duplex 10BaseT Full Duplex 100BaseT Half Duplex 100BaseT Full Duplex 1000BaseX Full Duplex Default 10baseT Half Duplex
Note: When autonegotiation protocols do not support each other, this degrades the connection to a halfduplex mode. In order to avoid this, disable autonegotiation and configure the ports manually. Halfduplex degradation also occurs when autonegotiation is enabled at one port and disabled at the opposite port. Half-duplex operation in the IPmux-24 network port is not recommended when transmitting small-size packets, because collisions and backoffs cause large delay variation and may exceed the delay variation buffer tolerance at the receiving end, resulting in buffer underflows and errors.
Flow Control Data flow control method based on Ethernet Pause frames. IPmux-24 only responds to the Pause frames sent by the peer device, slowing its transmission rate. Enable Flow control is enabled) Disable Flow control is disabled) Default Disable
Note: Enabling flow control may cause deterioration in the clock and voice traffic quality.
IPmux-24 Ver. 3.5
4-47
Configuration>Physical layer>ETH Channel Speed & Duplex 1. Administrative status 2. Auto negotiation 3. Flow control > > (User ETH3) (1000baseX Full Duplex) (Up) (Disable) (Disable)
> Please select item <1 to 3> F Forward ESC-prev.menu; !-main menu; &-exit
1 M/ 1 C
Figure 4-43. ETH Menu
Configuring Routing Parameters

To control the paths used to reach the pseudowire destinations, the IPmux-24 router enables defining up to 100 static routes, in addition to a default gateway. To configure routing parameters: 1. From the Configuration menu, select Router. The Router menu is displayed. 2. From the Router menu, select Default Gateway and set the default gateway IP address.
Note
The default gateway must be in the same subnet as the originating IP address (management or pseudowire host).
3. From the Router menu, select Static Route. The Static Route menu is displayed (Figure 4-44). 4. From the Static Route menu, type a to add a new static route. 5. Define the following static route attributes: IP Address (IP address of the static route) IP Mask (IP subnet mask of the static route) Next Hop (an IP address to which the packets will be sent, to enable reaching the destination IP address. This is usually the address of an IP router port.)
Note
Next hop IP address cannot be the same as default gateway IP address.
4-48
IPmux-24 Ver. 3.5
To delete a static route: 1. In the Static Route Table, use arrow keys to select a static route. 2. Type r to delete the route. To clear the static route table: In the Static Route Table, type c to clear all static route entries.
Configuration>Router>Static Route Table IP Address 30.30.30.30 30.30.30.34 50.50.50.0 > IP Mask 255.255.255.0 255.255.255.0 255.255.255.0 Next Hop 10.10.10.1 20.20.20.1 10.10.10.1
A-Add; R-Remove; C-Clear F Forward ESC-prev.menu; !-main menu; &-exit
1 M/ 1 C
Figure 4-44. Static Route Menu
Configuring Bundle Connections

IPmux-24 supports up to 64 bundles (16 bundles per E1/T1 link). Each bundle can include up to 31 E1 timeslots or up to 24 T1 timeslots. The bundle identification numbers are assigned to the E1/T1 links as illustrated in Table 4-18.
Table 4-18. Bundle Assignment

TDM Link 1 2 3 4 Bundle ID 131 3363 6595 97127
Any bundle can be connected to any bundle of a pseudowire device that operates opposite IPmux-24. The pseudowire traffic generated by IPmux-24 is forwarded to a PW host IP address of the remote device. To configure bundle connection: 1. From the Configuration menu, select Connection. The Connection menu appears (see Figure 4-45).
IPmux-24 Ver. 3.5
4-49
Configuration>Connection 1. 2. 3. 4. 5. 6. 7. 8. > PW host IP Redundant PW host IP Multiplexing Bundle ID[1 - 511] PW type PSN type DS0 bundle Bundle connection > > (Source Port) ... (1) > (TDMoIP CE) > (UDP/IP) []> >
1 M/ 1 C
Figure 4-45. Connection Menu

2. From the Connection menu, select PW Host IP. The PW Host IP menu is displayed (see Figure 4-46). 3. From the PW Host IP menu, define parameters of the PW host which is going to be used as a destination IP for the incoming pseudowire traffic, see Table 4-19. Configuration>Connection>PW host IP 1. IP address 2. IP mask > Please select item <1 to 2> ESC-prev.menu; !-main menu; &-exit ... (0.0.0.0) ... (0.0.0.0)
1 M/ 1 C
Figure 4-46. PW Host IP Menu Table 4-19. PW Host IP Parameters

Name IP address Description IP address of the PW host, used for the pseudowire traffic. At the remote device, make sure that the Destination IP Address value is the same as the local PW host and vice versa. IP Mask IP mask of the PW host, used for the pseudowire traffic Valid IP mask Possible Values Valid IP address
4. From the Redundant PW Host IP menu, define parameters of the redundant PW host, see Table 4-19. Redundant host IP can be defined only after defining a regular PW host IP. It is used in bundle redundancy applications. 5. Select UDP multiplexing method, which is used by UDP/IP bundles:
4-50
IPmux-24 Ver. 3.5
Source Port: RAD proprietary method. It uses a fixed UDP destination port, and includes the pseudowire label as part of the UDP source port. Select this value for backward compatibility with RAD equipment. Destination Port: Multiplexing method specified by current standards. The UDP destination port includes the destination pseudowire label, and the UDP source port includes the source pseudowire label. Select this value for compatibility with other vendor's equipment. IPmux-24 resets automatically. 6. Select Bundle ID, and select a bundle to which you intend to assign timeslots. Keep in mind that by selecting a bundle number, you specify a TDM link (14), which provides timeslots for the bundle, as illustrated above. 7. Select DS0 bundle. The DS0 Bundle menu appears (see Figure 4-47). Configuration>Connection>DS0 bundle TDM Channel ID: 1 Bundle ID: 1 +1 +2 +3 +4 TS 0 1 0 0 0 0 0 0 0 0 0 0 0 TS 10 TS 20
+5 0 0 0
+6 0 0 0
+7 0 0 0
+8 0 0 0
+9 0 0 0
+10 0 0 0
TS 30 0 1. Change cell [0 - 1] >
... (0)
Please select item <1 to 1> E enable all; L disable all ESC-prev.menu; !-main menu; &-exit; ?-help
1 M/ 1 C
Figure 4-47. DS0 Bundle Menu

8. From the DS0 Bundle, assign timeslots to the current bundle by selecting a timeslot and choosing 1 (active) or 0 (free).
Note
You can assign all timeslots to the current bundle at once by typing E. You can cancel assignment of all timeslots to the current bundle at once by
typing L.
9. From the Connection menu, select the connection mode: TDMoIP CE (TDMoIP circuit emulation) HDLC (HDLC connection mode is not available for the bundles used for carrying adaptive clock) CESoPSN (CESoPSN connection mode is available for E1/T1 links operating in framed mode) SAToP (SAToP connection mode is available for E1/T1 links operating in unframed mode)
IPmux-24 Ver. 3.5
4-51
10. From the Connection menu, configure the packet-switched network type: UDP/IP (Bundle encapsulation is UDP/IP) MPLS/ETH (Bundle encapsulation is MPLS/Ethernet) MAC/ETH (Bundle encapsulation is MAC/ETH).
Note
PSN Type is only available after Bundle ID has been set.

11. From the Connection menu, select Bundle connection. The Bundle Connection menu appears (see Figure 4-48).
Note
IPmux-24 only shows the relevant menu options, depending on the TDM line type, PW type, PSN type, and transmit clock source.
Configuration>Connection>Bundle connection TDM channel ID: 1 Bundle ID: 1 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. 18. > Destination IP Address Bundle Name Next Hop IP TOS[0 - 255] Connection Status Destination Bundle[1 - 8063] Redundancy Function TDM Bytes In Frame(x48 Bytes)[1 - 30] Payload Format Far End Type OAM Connectivity Jitter Buffer [msec][2.5 - 180] Sensitive OOS Mode VLAN Tagging VLAN ID[1 - 4094] VLAN Priority[0 - 7] RTP Header RTP Payload Type[0 - 7f] SSRC Source IP Address ... ... ... ... ... > ... > > ... (2.2.2.10) (Bundle 1) (1.1.1.1) (0) (Enable) (1) (Primary) (1) (V2) (E1) (Disable) (3.0) (Data) (Tx OOS) (Enable) (111) (7) (Enable) (65) (0) (Host IP)
... ... ... ...
Please select item <1 to 18> F - Forward Bundle ID; D - Delete; ? - Help ESC-prev.menu; !-main menu; &-exit
1 M/ 1 C
Figure 4-48. Bundle Connection Menu (Connection Mode=TDMoIP CE, PSN Type=UDP/IP)
4-52
IPmux-24 Ver. 3.5
12. From the Bundle Connection menu, configure the connection values according to Table 4-20, Table 4-21, Table 4-22, Table 4-23, Table 4-24, Table 4-25, Table 4-26, Table 4-27.
Table 4-20. Connection Parameters (TDMoIP CE Connection, UDP/IP PSN)

Name Destination IP Address Description IP address of the destination device Possible Values Valid IP address Default None Bundle Name Name assigned to bundle Alphanumeric string Default None Next Hop Use the next hop parameter when the destination IP address is not in the device subnet. In such cases the Ethernet frame is sent to the next hop IP. If it is not configured, the default gateway is used. When using redundant bundles with Layer 3 networks, make sure that primary and secondary bundles use different next hop addresses to create different networks paths for PW traffic. IP TOS Specifies the Layer 3 priority assigned to 0255 the traffic generated by this bundle. Default 0 For IP networks, this priority is indicated by the IP type-of-service parameter for this bundle. The specified value is inserted in the IP TOS field of the bundle IP packets. When supported by an IP network, the type-of-service parameter is interpreted, in accordance with RFC 791 or RFC 2474, as a set of qualitative parameters for the precedence, delay, throughput and delivery reliability to be provided to the IP traffic generated by this bundle. These qualitative parameters may be used by each network that transfers the bundle IP traffic to select specific values for the actual service parameters of the network, to achieve the desired quality of service You can also specify a Layer 2 priority by means of the VLAN Priority field, provided VLAN Tagging for this bundle is Enable. Valid IP address Default None
IPmux-24 Ver. 3.5
4-53
Chapter 4 Configuration Name Connection Status Description Administrative status of the connection
Installation and Operation Manual Possible Values Enable Connection is active Disable The connective is not active. You can still configure and save the desired parameters, to prepare the bundle for activation when needed. Default Enable
Destination Bundle
Bundle number in the destination device. 18063 IPmux-24 automatically adds the following values to the destination and source bundle number: +15, when the PSN type is set to MPLS +0xc000 when the CESoPSNand SAToP PWs operate over UDP/IP PSN +1 when the TDMoIP is set to the V1 payload format. Default 1
Destination bundle must be the same for both primary and secondary bundles operating in protection mode. Redundancy Function Bundle role in redundancy mechanism. Make sure that the same bundle is configured as primary or secondary via Bundle Protection menu (see the Configuring Bundle Protection section above). For secondary bundles, the following parameters are not available: TDM Bytes In Frame, Payload Format, Far End Type, OAM Connectivity, Jitter Buffer size, Sensitive, OOS Mode. These parameters are automatically copied from the primary bundle settings. Primary Active bundle Secondary Redundant (standby) bundle Mate Bundle is a mate to a bundle in another PW gateway operating in 1:1 redunancy mode. This bundle starts carrying traffic only when its mate is inactive. None Bundle is not part of redundancy mechanism Default None
Note: TDMoIP bundle redundancy is available only when the payload format is set to V2.
TDM Bytes in Frame (x48 bytes) UDP payload length, enabling reduction of Ethernet throughput 130 Default 1
4-54
IPmux-24 Ver. 3.5
Installation and Operation Manual Name Payload Format Description Selects the TDMoIP payload format. The selection must be compatible with the equipment at the far end of the connection. The payload format is valid for TDMoIP CE PWs and UDP/IP PSNs. Possible Values
V1 Old TDMoIP format, defined as experimental in the relevant IETF drafts. Not recommended for use. TDMoIP version V1 requires two UDP sockets per bundle, whereas TDMoIP V2 requires a single UDP socket per bundle. The larger number of UDP sockets per bundle needed by TDMoIP V1 reduces the maximum number of bundles to a given destination supported by IPmux-24. V2 Current TDMoIP format. Requires one UDP socket per bundle. Default V2
Far end type
Specifies the type of framing used by the equipment at the destination endpoint. The selected value also determines the encoding law used on PCM voice channels. Make sure to select the same value at both end points. The selected value must also match the Line Type configured for the physical port of the bundle local endpoint.
E1 E1 stream with G.704 framing. The PCM signals are processed assuming that they are encoded in accordance with the A-law. You can use this selection when the port Line Type is a FRAMED version. T1 ESF T1 stream with ESF framing. The PCM signals are processed assuming that they are encoded in accordance with the -law. T1 (SF) T1 stream with SF (D4) framing. The PCM signals are processed assuming that they are encoded in accordance with the -law. Unframed/serial unframed data stream, transparently transferred. You can use this selection when the port Line Type is unframed. Default E1 or T1 (ESF)
OAM connectivity
Controls the use of the OAM connectivity ENABLE The use of the OAM protocol for this bundle. connectivity protocol is enabled. This is the recommended selection. Make sure to The OAM connectivity protocol enables select V2 for Payload Format. detecting loss of communication with the destination of TDMoIP traffic and taking steps that prevent the resulting flooding. The protocol also enables checking that the destination uses a compatible configuration. The selection must be compatible with the equipment at the far end of the connection. DISABLE The use of the OAM connectivity protocol is disabled. Default Enable
Note: OAM connectivity must be enabled for 1:1 bundle redundancy. For 1+1 bundle redundancy, OAM connectivity can be either enabled or disabled.
IPmux-24 Ver. 3.5
4-55
Chapter 4 Configuration Name Jitter Buffer Description
Specifies the value of the jitter buffer to 2.5180 msec (framed) be used on this bundle. 0.5180 msec (unframed) You should use the shortest feasible Default 3.0 buffer, to minimize connection latency. Specifies whether to optimize the clock for accurateness or for constant delay Data Accurate clock is more important than constant delay Delay Constant delay is more important than accurate clock Default Data
Sensitive
OOS Mode
Defines whether Out of Service (OOS) signal is transmitted. The OOS signal is sent toward the IP path when loss of signal, loss of frame, or AIS is detected at the TDM line.
Tx OOS OOS transmission is enabled OOS suppression OOS transmission is disabled Default Tx OOS
VLAN Tagging
Controls the use of VLAN tagging for the Enable VLAN tagging is enabled traffic generated by this bundle Disable VLAN tagging is disabled Default Disable
VLAN ID
When VLAN tagging is enabled, specifies the VLAN ID number used by the bundle traffic sent through this port. When VLAN tagging is disabled, this parameter is not displayed. When using redundant bundles, make sure that primary and secondary bundles use different VLANs to create different networks paths for PW traffic over a Layer-2 PSN. For Layer-3 PSNs using VLAN tagging is not required.
14094
VLAN Priority
When VLAN tagging is enabled, specifies the priority assigned to the bundle traffic using the selected VLAN. When VLAN tagging is disabled, this parameter is not displayed.
07
Source IP Address
Source IP address used for protected bundles. The primary and secondary bundles must use one of the following differentiation methods: Different IP addresses Different VLAN IDs.
Host IP Host IP address is used for primary bundle. This value is available only if a PW host IP is not defined. PW IP PW host IP address is used for primary bundles Redundant PW IP Redundant PW host IP address is used for primary bundles Default PW IP (if a PW host is configured) or Host IP (if a PW host is not configured)
4-56
IPmux-24 Ver. 3.5
Installation and Operation Manual Name Description Possible Values
Note: When the IPmux-24 bridge operates in VLAN-aware mode with per-port traffic priority classification, VLAN priority of a primary and secondary bundles is copied from the default VLAN priority of the pseudowire/management bridge port.
RTP Header Controls whether an RTP (Real-time Transport Protocol) header is added to the bundle. The RTP headers can be used with all PSN types (IP/UDP, MPLS, Ethernet). Defines format of the RTP payload Enable RTP header is added to the bundle Disable RTP header is not added to the bundle Default Disable 07f Default 65 SSRC Synchronization source identifier for the 04294967295 (32 bits) RTP session. The identifier is selected Default 0
RTP Payload Type
randomly to ensure that no two synchronization sources within the same RTP session have the same SSRC identifier.
Table 4-21. Connection Parameters (TDMoIP CE Connection, MPLS/ETH PSN)

Name Destination IP Address MPLS Egress Label Description See Table 4-20 Controls the use of an interworking MPLS label for the transmit (outbound) direction of the bundle. Network termination units, such as IPmux-24, ignore the outbound label. Enable MPLS Egress Label is enabled Disable MPLS Egress Label is disabled Default Disable Possible Values
Outbound Tunnel Label Specifies the outbound MPLS label used for the bundle. This parameter is displayed only when Outbound Label Tagging is enabled. Outbound EXP Bits Specifies the value of the outbound EXP bits in the packet header used for the bundle. This parameter is displayed only when Outbound Label Tagging is enabled. Connection Status Destination Bundle Next Hop Type See Table 4-20 See Table 4-20 Type of the next hop device
161048575 Default 16
07 Default 0
IP The next hop device is an IP router MAC The next hop device is an MPLS LER Default IP
Next Hop TDM Bytes in Frame (x48 bytes)
See Table 4-20 See Table 4-20
IPmux-24 Ver. 3.5
4-57
Chapter 4 Configuration Name Payload Format Far End Type OAM Connectivity Jitter Buffer Sensitive OOS Mode VLAN Tagging VLAN ID Description See Table 4-20 See Table 4-20 See Table 4-20 See Table 4-20 See Table 4-20 See Table 4-20 See Table 4-20 See Table 4-20
Table 4-22. Connection Parameters (CESoPSN Connection, UDP/IP PSN)

Name Destination IP Address Next Hop IP TOS Description See Table 4-20 See Table 4-20 See Table 4-20 Possible Values
Connection Status Destination bundle TDM Frames in Packet Payload Format OAM connectivity Jitter Buffer Sensitive OOS Mode VLAN Tagging VLAN ID VLAN Priority
See Table 4-20 See Table 4-20 Defines number of TDM frames in one packet See Table 4-20 See Table 4-20 See Table 4-20 See Table 4-20 See Table 4-20 See Table 4-20 See Table 4-20 See Table 4-20 41440/Number of Timeslots
Table 4-23. Connection Parameters (CESoPSN Connection, MPLS/ETH PSN)

Name Destination IP Address Outbound Label Tagging Description See Table 4-20 See Table 4-21 Possible Values
Outbound Tunnel Label See Table 4-21 Outbound EXP Bits See Table 4-21
4-58
IPmux-24 Ver. 3.5
Installation and Operation Manual Name Connection Status Destination Bundle Next Hop Type Next Hop TDM Frames in Packet Payload Format Far End Type OAM Connectivity Jitter Buffer Sensitive OOS Mode VLAN Tagging VLAN ID Description See Table 4-20 See Table 4-20 See Table 4-21 See Table 4-20 See Table 4-22 See Table 4-20 See Table 4-20 See Table 4-20 See Table 4-20 See Table 4-20 See Table 4-20 See Table 4-20 See Table 4-20 Possible Values
Table 4-24. Connection Parameters (SAToP Connection, UDP/IP PSN)

Name Destination IP Address Next Hop IP TOS Connection Status Destination bundle TDM Bytes in Packet Description See Table 4-20 See Table 4-20 See Table 4-20 See Table 4-20 See Table 4-20 Defines UDP payload length (number of payload bytes in one Ethernet frame) 321440 (E1) 241440 (T1) Default 32 (E1), 24 (T1) Payload Format OAM connectivity Jitter Buffer Sensitive OOS Mode VLAN Tagging VLAN ID VLAN Priority See Table 4-20 See Table 4-20 See Table 4-20 See Table 4-20 See Table 4-20 See Table 4-20 See Table 4-20 See Table 4-20 0.5180 Default 3.0 Possible Values
IPmux-24 Ver. 3.5
4-59
Table 4-25. Connection Parameters (SAToP Connection, MPLS/ETH PSN)

Outbound Tunnel Label See Table 4-21 Outbound EXP Bits Connection Status Destination Bundle Next Hop Type Next Hop TDM Bytes in Packet Payload Format Far End Type OAM Connectivity Jitter Buffer See Table 4-21 See Table 4-20 See Table 4-20 See Table 4-21 See Table 4-20 See Table 4-24 See Table 4-20 See Table 4-20 See Table 4-20 See Table 4-20 0.5180 Default 3.0 Sensitive OOS Mode VLAN Tagging VLAN ID See Table 4-20 See Table 4-20 See Table 4-20 See Table 4-20
Table 4-26. Connection Parameters (HDLC Connection, UDP/IP PSN)

Name Destination IP Address Next Hop IP TOS Connection Status Destination bundle Payload Format OAM connectivity VLAN Tagging VLAN ID VLAN Priority Description See Table 4-20 See Table 4-20 See Table 4-20 See Table 4-20 See Table 4-20 See Table 4-20 See Table 4-20 See Table 4-20 See Table 4-20 See Table 4-20 Possible Values
4-60
IPmux-24 Ver. 3.5
Table 4-27. Connection Parameters (HDLC Connection, MPLS/ETH PSN)

Outbound Tunnel Label See Table 4-21 Outbound EXP Bits Connection Status Destination Bundle Next Hop Type Next Hop Payload Format OAM Connectivity Sensitive VLAN Tagging VLAN ID See Table 4-21 See Table 4-20 See Table 4-20 See Table 4-21 See Table 4-20 See Table 4-20 See Table 4-20 See Table 4-20 See Table 4-20 See Table 4-20
Notes
When PSN Type is MPLS/ETH the payload format is always V2. Make sure that selected VLAN is configured as a member of the network port
VLANs (see Configuring the Ethernet Bridge below).

When VLAN Tagging is enabled, IPmux-24 checks for matching VLAN ID on
transmitted frames only; frames received with a non-matching VLAN ID will not be dropped.
IPmux-24 assigns internal bundle numbers that are normally transparent to
the end user. However, in case you create bundle connections that mix together different types of payload formats or PSN types, then the internal bundle numbering scheme may need to be understood in order to prevent conflicts that would be visible as bit errors. The internal bundle number (IBN) is assigned in the following manner: V1: IBN = Bundle ID; V2: IBN = Bundle ID + 1; MPLS: IBN = Bundle ID + 15. Bundle IDs must be assigned in a manner that the internal bundle numbers are unique.
Configuring the Ethernet Bridge

The IPmux-24 bridge connects Ethernet ports of the unit. The bridge operates in the VLAN-aware and VLAN-unaware modes. Learning and filtering can be enabled or disabled. Static MAC addresses are stored in the MAC table. Each bridge port can be assigned to a VLAN. To configure the bridge: 1. From the Configuration menu, select Bridge. The Bridge menu is displayed (see Figure 4-49). 2. From the Bridge menu, configure the following:
IPmux-24 Ver. 3.5
4-61
VLAN Mode: Aware (IPmux-24 bridge handles VLANs) Unaware (IPmux-24 bridge does not handle VLANs) Forwarding Mode (Operation mode of the bridge): Transparent (No filtering is performed. IPmux-24 forwards all received frames.) Filter (IPmux-24 filters traffic according the received MAC addresses) Aging Time (Amount of time a LAN node (station) is allowed to be inactive before it is removed from the network): 300 to 3600 seconds. Configuration>Bridge 1. 2. 3. 4. 5. 6. 7. VLAN Mode Forwarding Mode Aging Time[300 - 4080] Static MAC Table Erase MAC Table Bridge Port VLAN Membership (Unaware) (Transparent) ...(300) []> > > 1 M/ 1 C
ESC-prev.menu; !-main menu; &-exit
Figure 4-49. Bridge Menu
Configuring MAC Table

You can add static MAC addresses to the IPmux-24 MAC table. When the bridge operates in the VLAN-aware mode, it is possible to assign VLAN ID to a MAC address. The same MAC address can be assigned to more than one bridge port (with or without VLAN). To add a static MAC addresses: 1. From the Bridge menu, select Static MAC Table. The Static MAC Table appears (see Figure 4-50). 2. From the Static MAC Table, type A to add a static MAC address. The Static MAC Table display changes, entering the Add mode (see Figure 4-52). 3. When in Add mode, perform the following: Select MAC Address, and enter a new MAC address. Select Received Bridge Port, and choose an IPmux-24 interface this MAC address will be attached to. If the bridge operates in the VLAN-aware mode, specify VLAN ID with which frames from the current MAC address are expected to arrive. Save the changes. Press <Esc> to return to the Static MAC Table.
4-62
IPmux-24 Ver. 3.5
To remove a static address from the table: From the Static MAC Table (Figure 4-50), select a MAC address that you want to remove and type R. The static MAC address is deleted from the table. To delete static addresses from the MAC table: 1. From the Static MAC Table (Figure 4-50), type C to delete all static MAC addresses. IPmux-24 displays the following message: Are you sure??? (Y/N) 2. Type Y to confirm deletion of all static MAC addresses from the table. To delete learned addresses from the MAC table: 1. From the Bridge menu, select Erase MAC Table to delete all learned addresses from the MAC table. IPmux-24 displays the following message: MAC table will be cleared. Continue??? (Y/N) 2. Type Y to confirm deletion of all learned MAC addresses from the table. Configuration>Configuration>Bridge>Static MAC Table MAC Address Received Bridge Port 1 10-00-00-00-00-00 Network A - Add R Remove C - Clear Table 1 M/ 1 C
ESC-prev.menu; !-main menu; &-exit; ?-help
Figure 4-50. Static MAC Table (VLAN-Unaware)

Configuration>Configuration>Bridge>Static MAC Table VLAN ID MAC Address Received Bridge Port 1 1 10-00-00-00-00-00 Network A - Add R Remove C - Clear Table ESC-prev.menu; !-main menu; &-exit; ?-help 1 M/ 1 C
Figure 4-51. Static MAC Table (VLAN-Aware)

Configuration>Configuration>Bridge>Static MAC Table 1. Vlan Id[1 - 4094] (0) 2. MAC Address ... (10-00-00-00-00-00) 3. Received Bridge Port 4. Save All > ESC-prev.menu; !-main menu; &-exit > (Network)
1 M/ 1 C
Figure 4-52. Static MAC Table, Add Mode (VLAN-Aware)
IPmux-24 Ver. 3.5
4-63
Configuring the Bridge Ports

IPmux-24 bridge ports support filtering of incoming traffic, accepting all frames or only those, which have VLAN tags. The incoming frames can be assigned PVID and priority by the bridge ports. There are five ports on the IPmux-24 bridge: Network Ethernet port Network/user Ethernet port User Ethernet port Pseudowire (PW). If only a management host IP is defined, this port is used for both management and pseudowire traffic. Management (MNG). This port is activated only when a PW host IP is defined in addition to the management host IP.
To configure the bridge ports: 1. From the Bridge menu, select Bridge Port. The Bridge Port menu is displayed (see Figure 4-53). 2. From the Bridge Port menu, type f to select the bridge port that you intend to configure, and set the following parameters: Ingress Filtering (Controls filtering of the incoming traffic) Enable (The bridge port accepts only frames with tags of the VLANs, which include this user port as a member.) Disable (The bridge port accepts all incoming frames) Accept Frame Type (Specifies the frame types to be accepted by the bridge port) All (The bridge port accepts all frames (tagged, untagged, priority-tagged). Untagged and priority-tagged frames receive PVID of the user bridge port.) Tag only (The bridge port accepts only tagged frames, discarding untagged and priority-tagged)
Note
The Ingress Filtering and Accept Frame Type parameters are available only in the VLAN-aware mode.
Port VID (Port VID to be added by the user bridge port to the arriving frames): 14094
Note
PVID operation depends on the tag handling mode:

None PVID is added to the untagged and priority-tagged frames only. Stack PVID is added to all arriving frames (tagged, untagged or priority
tagged).
Default Priority Tag (Default priority tag to be added by the user bridge port to the untagged frames. No default priority tags are added to the frames arriving with assigned port priority): 07.
4-64
IPmux-24 Ver. 3.5
Egress Tag Handling (Defines if a bridge port adds port VID at the egress only to untagged or to all arriving frames) None (PVID is added to the untagged and priority-tagged frames only) Stacking (PVID is added to all arriving frames) Ingress Tag Handling (Defines if a bridge port strips port VID at the ingress or leaves frames intact) None (Frames are left intact at the port ingress) Stripping (PVID is removed from the frames at the port ingress) Configuration>Configuration>Bridge>Bridge Port Port Label > (1) Bridge Port > (Netrwork-ETH1) 1. Ingress Filtering 2. Accept Frame Type 4. Default Priority Tag [0 - 2] 5. Egress Tag Handling 6. Ingress Tag Handling 7. L2CP Handling > F - Forward ESC-prev.menu; !-main menu; &-exit 1 M/ 1 C > ... (Enable) ... (All) ... (0) (None) (None)
3. Port VID\Stacking VID [1 - 4094] ... (1)
Figure 4-53. Bridge Port Menu (Network 1)
Configuring L2CP Handling

Each IPmux-24 bridge port can be configured to tunnel or discard layer 2 control protocol traffic. Tunneling the L2CP traffic allows service providers access network equipment connected to IPmux-24.
Note
L2CP handling cannot be configured for the management and PW host bridge ports.
To configure the L2CP handling: 1. From the Bridge Port menu (Configuration > Configuration > Bridge > Bridge Port), type f to select the bridge port which L2CP policy you intend to configure. 2. Select L2CP Handling. The L2CP Handling menu is displayed (see Figure 4-54). 3. From the L2CP Handling menu, select one of the standard multicast MAC addresses and define how the bridge port handles its L2CP traffic: Tunnel (L2CP frames are forwarded as ordinary data)
IPmux-24 Ver. 3.5
4-65
Discard (L2CP frames are discarded) Default: Tunnel Configuration>Configuration>Bridge>Bridge Port>L2CP Handling MAC Dest Address 1. 01:80:C2:00:00:00 2. 01:80:C2:00:00:01 3. 01:80:C2:00:00:02 4. 01:80:C2:00:00:03 5. 01:80:C2:00:00:04 6. 01:80:C2:00:00:05 7. 01:80:C2:00:00:06 8. 01:80:C2:00:00:07 9. 01:80:C2:00:00:08 10.01:80:C2:00:00:09 11.01:80:C2:00:00:0A 12.01:80:C2:00:00:0B ... (N) > Please select item <1 to 16> ESC-prev.menu; !-main menu; &-exit 1 M/ 1 C Handling (Tunnel) (Tunnel) (Tunnel) (Tunnel) (Tunnel) (Tunnel) (Tunnel) (Tunnel) (Tunnel) (Tunnel) (Tunnel) (Tunnel)
Figure 4-54. L2CP Handling Menu
Configuring the VLAN Membership

Each IPmux-24 port can be defined as a VLAN member. The ports can also be configured to add or to strip the VLAN tag at the egress. To configure the VLAN membership: 1. From the Bridge menu, select VLAN Membership. The VLAN Membership menu is displayed (see Figure 4-55). 2. From VLAN Membership menu, type a and add a new VLAN, and enter the new VLAN number or type f to select an existing VLAN, to which you intend to assign an IPmux-24 bridge port. 3. When the number of the required VLAN is displayed at the top of the menu, do the following: Select Egress Tagged Ports to assign network and/or user ports to be the tagged members of the current VLAN. These ports add the current VLAN tag to all frames at egress. Select Egress Untagged Ports to assign network and/or user ports to be the untagged members of the current VLAN. These ports strip the current VLAN tag from all frames at egress.
4-66
IPmux-24 Ver. 3.5
Select Egress Unmodified Ports to assign network and/or user ports to be the unmodified members of the current VLAN. These ports leave VLAN tags intact on all frames at egress.
Note
Each port can be an untagged member in only one VLAN.

To assign an IPmux-24 port to a VLAN: 1. From the Egress Tagged Ports or Egress Untagged Ports menu, type a to add a port. The display changes, entering the Add mode (see Figure 4-55). 2. When in Add mode, perform the following: 1. Select the IPmux-24 port range, displayed as [1 5], and enter the desired port number. 2. Save the change. 3. Type a to add another port, and enter its number. 4. Save the change. 5. Press <Esc> to return to the VLAN Membership menu. 6. Save the changes. To delete IPmux-24 ports assigned to VLAN: 1. From the Egress Tagged Ports or Egress Untagged Ports menu, select Delete Range and specify bridge ports that you intend to disconnect from the current VLAN and save the changes The ports which will be disconnected are selected one after another or as a group in the x-y format in the ascending order. For example, if you want to disconnect ports 1, 2 and 3 from the VLAN, you can do it in the following succession: Delete Range 1, Delete Range 2, Delete Range 3, Save. Alternatively, you can specify the port range and do it in just two steps as follows: Delete Range 1-3, Save. 2. Press <Esc> to return to the VLAN Membership menu. 3. Save the changes.
Configuration>Bridge>VLAN Membership>Egress Tagged Ports 1. [1 - 3]... (-) > Please select item <1 to 1> ESC-prev.menu; !-main menu; &-exit; A-add 1 M/ 1 C
Figure 4-55. Egress Tagged Ports Menu, Add Mode
IPmux-24 Ver. 3.5
4-67
Configuration>Bridge>VLAN Membership>Egress Tagged Ports 1. [1 - 3]... (1) 2. Delete Range... > Please select item <1 to 2> ESC-prev.menu; !-main menu; &-exit; A-add 1 M/ 1 C
Figure 4-56. Port 1 is about to be Added to VLAN 1 as a Tagged Port
Configuring Quality of Service (QoS)

IPmux-24 supports configuration of two QoS categories: priority and rate limitation. QoS configuration is performed via the QoS menu (Main menu > Configuration > QoS).
Configuring the Traffic Priority

IPmux-24 provides four priority queues for each port or pseudowire traffic. User traffic can be prioritized according to the VLAN priority, DSCP, IP Precedence or per port basis. To select the traffic priority type: 1. From the Configuration menu, select QoS. The QoS menu is displayed. 2. From the QoS menu, select Priority. The Priority menu is displayed (see Figure 4-57). 3. From the Priority menu, select Classification and from the Classification menu choose one of the following traffic prioritization methods for each IPmux-24 bridge port: 802.1p (Priority is determined according to VLAN priority) DSCP frame DSCP field (the Differentiated Services Codepoint, as specified in RFC 2474). IP Precedence (Priority is determined according to the 3 MSB of the IP ToS field) Per Port (Priority is determined by the port default VLAN priority. In the case of the pseudowire traffic it is copied from the host priority setting.).
4-68
IPmux-24 Ver. 3.5
Configuration>QoS>Priority>Classification 1. Network ETH1 2. Network/User ETH2 3. User ETH3 4. MNG >(802.1p) >(802.1p) >(802.1p) >(802.1p)
5. PW or PW/MNG >(802.1p) > ESC-prev.menu; !-main menu; &-exit
1 M/ 1 C
Figure 4-57. Classification Menu

To define the priority mapping: 1. Once the priority type is defined, select Mapping from the Priority menu. The Mapping menu appears. The Mapping menu changes according to the selected priority type (802.1p, DSCP, IP Precedence, per port). 2. From the Mapping menu, select one of the classification methods: 802.1p priority Assign each priority tag, supported by IEEE 802.1p (07) to a specific priority queue (traffic class 0 (lowest), traffic class 1, traffic class 2, or traffic class 3) DSCP priority Assign each DSCP (063) to a specific priority queue (traffic class 0 (lowest), traffic class 1, traffic class 2, or traffic class 3) IP Precedence priority Assign each 3 MSB of the IP ToS field value (07) to a specific priority queue (traffic class 0 (lowest), traffic class 1, traffic class 2, or traffic class 3) Per port priority Per port mapping is determined by default VLAN priority of the bridge port. Configuration>Configuration>QoS>Priority>Mapping>802.1p 1. User priority 0 2. User priority 1 3. User priority 2 4. User priority 3 5. User priority 4 6. User priority 5 7. User priority 6 8. User priority 7 > S - Save ESC-prev.menu; !-main menu; &-exit >(Traffic class 0) >(Traffic class 0) >(Traffic class 1) >(Traffic class 1) >(Traffic class 2) >(Traffic class 2) >(Traffic class 2) >(Traffic class 2)
1 M/ 1 C
Figure 4-58. Mapping for 802.1p Priority Menu
IPmux-24 Ver. 3.5
4-69
Configuring Rate Limitation

IPmux-24 supports data rate limitation at the egress and ingress of the network and user ports. IPmux-24 limits the data rate proper, without taking into account Ethernet frame intergaps.
Configuring Ingress Rate Limitation

Via ingress rate limitation the user controls the rate of traffic received at the network and user interfaces. The traffic that exceeds the selected rate limitation value for an IPmux-24 port is dropped. In addition to that IPmux-24 defines maximum packet burst for each rate limitation value. This enables service providers to compensate their subscribers for underused bandwidth by allowing temporary traffic bursts. Also, the rate limitation can be applied to all packets or to their certain types (broadcast, multicast, etc).
Note
The 100666 Mbps data rates are not supported by IPmux-24 with Fast Ethernet interfaces.
To configure the ingress rate limitation: 1. From the Rate Limitation menu (Configuration > QoS > Rate Limitation), select Ingress. The Ingress menu is displayed (Figure 4-59). 2. From the Ingress menu, type f to select the network or user port to which you intend to apply rate and burst limitation. 3. Select Rate Limitation and define the maximum ingress data rate allowed on the port (see Table 4-28). 4. Select Burst Size and define the maximum allowed size of the packet buffer (in kilobytes) to be used by the port when traffic bursts occur. See Table 4-28 for the allowed burst values depending on configured port rate limitation. Traffic bursts permitted only if the traffic has been sent to the IPmux-24 below the rate limit for a certain period of time. 5. Select Limit Packet Type and choose a packet type to which the rate/burst limitation is to be applied: All The limitation is applied to all arriving packets Broadcast & Multicast & Flooded Unicast The limitation is applied to broadcast, multicast and flooded unicast packets Broadcast & Multicast The limitation is applied to broadcast and multicast packets Broadcast The limitation is applied to broadcast packets.
4-70
IPmux-24 Ver. 3.5
Configuration>QoS>Rate Limitation>Ingress Port Label > (1) Port > (Network Port) 1. Rate Limitation > 2. Burst Size (in kB) > 3. Limit Packet Type > > Please select item <1 to 3> F - Forward S Save ESC-prev.menu; !-main menu; &-exit (1Mbps) (12K) (All)
1 M/ 1 C
Figure 4-59. Ingress Rate Limitation Menu Table 4-28. Rate and Burst Limitation
Rate Limit 12 kB 1 Mbps 1.5 Mbps 2 Mbps 3 Mbps 4 Mbps 5 Mbps 6 Mbps 7 Mbps 8 Mbps 9 Mbps 10 Mbps 15 Mbps 20 Mbps 25 Mbps 30 Mbps 35 Mbps 40 Mbps X X Burst Size 24 kB 48 kB 96 kB 41 Mbps 45 Mbps 50 Mbps 60 Mbps 71 Mbps 83 Mbps 90 Mbps 100 Mbps 125 Mbps 166 Mbps 200 Mbps 250 Mbps 333 Mbps 400 Mbps 500 Mbps 666 Mbps X X X X X X X X X X X X X X Rate Limit 12 kB Burst Size 24 kB 48 kB X 96 kB X
Configuring Egress Rate Limitation

To configure the egress rate limitation: 1. From the QoS menu, select Rate Limitation. The Rate Limitation menu is displayed. 2. From the Rate Limitation menu, select Egress. The Egress menu is displayed.
IPmux-24 Ver. 3.5
4-71
3. From the Ingress menu, type f to select the network or user port to which you intend to apply rate limitation. 4. Select Rate Limitation and define the maximum egress data rate allowed on the port (see Table 4-28).
4.3
Performing Additional Tasks
This section describes additional operations available supported by the IPmux-24 management software, including the following: Displaying inventory Setting data and time Editing banner information Displaying IPmux-24 status Transferring software and configuration files Resetting the unit.
Displaying the Inventory

The IPmux-24 inventory displays information on current software and hardware revisions of the unit. It also provides the IPmux-24 interface description. To display the IPmux-24 inventory: Inventory From the Main menu, select Inventory.
SOFTWARE Boot version Application version Backup version HARDWARE Version Host MAC address PW MAC address PW Redundant MAC address ERP MAC address Security Key ... (N) > ESC-prev.menu; !-main menu; &-exit
(1.14 ) (3.50a8 14/03/2010 16:30:56) (2.10a6 01/04/2009 16:55:02) (0.0/TCXO) (0020D2265244) (0020D226515E) (0010E1164256) (0030B4535223) (SSL + SSH)
1 M/ 1 C
Figure 4-60. Inventory Screen (Page 1)
4-72
IPmux-24 Ver. 3.5
Inventory ... (P) INTERFACE TDM1 TDM2 TDM3 TDM4 ETH1/Net ETH2/User1 ETH3/User2 CPLD Carrier Class Support Real Time Clock > ESC-prev.menu; !-main menu; &-exit 1 M/ 1 C
(E1 over UTP) (E1 over UTP) (E1 over UTP) (E1 over UTP) (ETHERNET over Multimode LC) (ETHERNET over Multimode LC) (ETHERNET over UTP) (No) (Not Exist)
Figure 4-61. Inventory Screen (Page 2)
Setting the Date and Time

You can set the date and time for the IPmux-24 internal real-time clock. When configured to To set date and time: 1. From the System menu, select Date and Time. The Date and Time menu appears (see Figure 4-62). 2. From the Date and Time menu, configure all necessary parameters, referring to Table 4-29. Configuration>System>Date and Time Time Since Last Poll (Minutes) 1. 2. 3. 4. 5. 6. > System Date System Time Broadcast Mode Poll Interval (Minutes) [1 1440] UTC Offset [-12 13] NTP Servers > > > > > [] (1) (01-01-2010) (00:00:01) (Disable) (15) (+2)
1 M/ 1 C
Figure 4-62. Date and Time Menu
IPmux-24 Ver. 3.5
4-73
Table 4-29. Date and Time Values

Name System Date Description Current system date entered manually or received from an NTP server in the dd:mm: yyyy format Current system time entered manually or received from an NTP server in the hh:mm:ss format Controls listening to NTP broadcast messages for date/time retrieval Enable IPmux-24 listens to NTP broadcast messages on the network Disable IPmux-24 does not listen to NTP broadcast messages on the network and retrieves date/time values from defined NTP servers Default Disable Poll Interval Defines time between two consecutive NTP requests. This parameter is not available when: UTC Offset NTP Servers Broadcast mode is enabled The 1st polling has not been completed No unicast NTP server is defined. 11440 Default 15 Possible Values
System Time
Broadcast Mode
Defines offset of NTP or RTC from UTC in -12 to +13 (-7200780 minutes) minutes Configures unicast NTP server(s), see below
To configure an NTP server: 1. From the Date and Time menu, select NTP Servers. The NTP Servers menu is displayed. 2. From the NTP Servers menu, type a to add a new server. 3. Define the following parameters for each added NTP server: IP address of the server to provide timestamps Administrative status of the NTP server: Prefer Preferable source for timestamp retrieval Enable Secondary source for timestamp retrieval. IPmux-24 sends time/date requests to an enabled NTP server only if preferred servers do not respond or are not defined. Disable Disabled source for timestamp retrieval. IPmux-24 does not send time/date requests to a disabled NTP server. UDP port (Source UDP port of NTP packets sent to the configured server) 165535
4-74
IPmux-24 Ver. 3.5
Stratum (NTP server stratum) 0255 4. Once a server is added, you can select the server and: Type q to request a timestamp Type m to modify its parameters Type r to remove the server Type x to delete all configured servers 5. In addition to the configuration parameters, the NTP Servers menu, displays the following information: Last timestamp received from the server Period of time (in seconds) elapsed since the last meaningful reply from the server. Configuration>System>Date and Time>NTP Servers ID 1. NTP Server 001.001.001.001 Admin Status Prefer Enable Disable UDP Port 123 1234 12345 Stratum 4 5 -Last Timestamp 01-10-1949 00:00:10 01-10-1949 00:00:01 -Received ddd:hh:mm:ss Ago 000:00:00:01 000:00:00:10 --
2. 002.002.002.002 3. 003.003.003.003
a - Add; m Modify; r Remove; x Clear Table; q Query Server ESC-prev.menu; !-main menu; &-exit
1 M/ 1 C
Figure 4-63. NTP Servers Menu
Editing Banner Information

Banner is a text displayed immediately after loading application software and before the login screen, see Figure 4-64. You can use it to present any desired information, such as warnings, welcome messages etc. Banner text size is limited to ten lines with 80 alphanumeric characters in each line.
IPmux-24 Ver. 3.5
4-75
*** W A R N I N G *** All content of this product are PROPRIETARY INFORMATION. Disclosure of information found in this product for any unauthorized use is *STRICTLY PROHIBITED*. Unauthorized or improper use of this product may result in administrative disciplinary action and/or civil charges/criminal penalties. By continuing you indicate your awareness of and consent to these terms and conditions of use. DO NOT LOG IN unless you agree to the conditions stated in this warning.
Figure 4-64. Banner Display

To edit banner information: 1. From the Edit Banner menu (Configuration > System > Edit Banner), type a number (110) corresponding to a banner line that you intend to edit. 2. Enter desired text and press <Enter>. 3. Save the changes. Configuration>System>Edit Banner 1. ... 2. ... 3. ... 4. ... 5. ... 6. ... 7. ... 8. ... 9. ... 10.... > ( *** W A R N I N G *** ) (All content of this product are PROPRIETARY INFORMATION. ) (Disclosure of information found in this product ) (for any unauthorized use is *STRICTLY PROHIBITED*. ) (Unauthorized or improper use of this product ) (may result in administrative disciplinary action ) (and/or civil charges/criminal penalties. ) (By continuing you indicate your awareness of ) (and consent to these terms and conditions of use. ) (DO NOT LOG IN unless you agree to the conditions stated in this w...)
1 M/ 1 C
Figure 4-65. Edit Banner Menu
Configuring Syslog Parameters

To allow logging/sharing of system events on an external server, you need to configure the Syslog server parameters. To configure the Syslog parameters: From the Syslog menu (Configuration > System > Syslog), configure the following: Logging Status (Enables or disables event logging):
4-76
IPmux-24 Ver. 3.5
Enable (IPmux-24 logs events onto Syslog server) Disable (IPmux-24 logs the events internally) Server IP Address (IP address of the Syslog server to which the event logs are sent): 0.0.0.0255.255.255.255 Server UDP Port (The UDP port of the Syslog server): 165535 Device UDP Port (The local UDP port from which the Syslog messages are sent: 165535
Note
The UDP port values cannot be changed when the logging status is enabled.
Facility (The software module, task or function from which the Syslog messages are sent): Local 17 Severity Level (Only events with the severity which equals or exceeds the selected severity level are sent): Critical corresponds to the Emergency (0) severity level of Syslog Major corresponds to the Alert (1) and Critical (2) severity levels of Syslog Minor corresponds to the Error (3) severity level of Syslog Warning corresponds to the Warning (4) severity level of Syslog Event corresponds to the Notice (5) severity level of Syslog Info corresponds to the Informational (6) severity level of Syslog Debug corresponds to the Debug (7) severity level of Syslog. Server IP Address (IP address of the Syslog server to which the event logs are sent): 0.0.0.0255.255.255.255 Server UDP Port (The UDP port of the Syslog server): 165535
Configuration>System>Syslog 1. Device Logging status 2. Device UDP port 3. Facility 4. Severity level > (Disable) > (514) > (Local 1) > (Minor)
5. Server Parameters > > ESC-prev.menu; !-main menu; &-exit
1 M/ 1 C
Figure 4-66. Syslog Menu
Displaying the Status

The IPmux-24 software allows displaying information on the physical layer and bundle connections. This section describes only status information of the IPmux-24 device. For description of IPmux-24 alarms, refer to Chapter 5. The status information is available via the Status menu.
IPmux-24 Ver. 3.5
4-77
Displaying the Physical Layer Information

At the physical level, you can view the Ethernet and SFP status.
Displaying the Ethernet Physical Layer Information

To display the Ethernet physical layer information: From the ETH Physical Layer screen (Monitoring > Status > Physical ports > ETH physical layer), type F to toggle between the available Ethernet interfaces.
Monitoring>Status>ETH Physical layer Channel Mode Rate(Mbps) Status > > > > (Network-Eth1) (Full Duplex) (100) (Connected)
> F - forward ESC-prev.menu; !-main menu; &-exit
1 M/ 1 C
Figure 4-67. ETH Physical Layer Screen
Displaying the SFP Status

When IPmux-24 is equipped with SFP transceivers, you can display the fiber optic interface properties of the installed SFPs. From the Link Status screen (Monitoring > Physical ports > SFP > Link Status), type F to select a network or user fiber optic interface. The following information is available: Connector type Manufacturer Typical maximum range Fiber type. Monitoring>Physical ports>SFP>Link Status Port Number > (User2-SFP3) Connector Type ... (LC) Manufacturer Name ... (WTD) Typical Max. Range(meters) ... (550) Wave Length > (850nm) Fiber Type > (Multi Mode)
F - Forward ESC-prev.menu; !-main menu; &-exit
1 M/ 1 C
Figure 4-68. Link Status Screen
4-78
IPmux-24 Ver. 3.5
Displaying the Link OAM Status

At the link level IPmux-24 provides status information according to the IEEE 802.3ah requirements. The 802.3ah link status collection must be enabled at the physical level for each IPmux-24 Ethernet interface. To display the links OAM status: 1. Navigate to Monitoring > Application > OAM > Link (802.3ah). 2. From the Link (802.3ah) menu, select Status. The Link (802.3ah) Status screen appears. 3. Press <F> to toggle between the Ethernet ports. Monitoring>Status>Physical ports>Link (802.3ah)>Status Ether Port ... (1) Oper Status > (Passive Wait) Loopback St > (No Loop) Local Information: MAC Address ... (00-20-D2-26-52-44) OAM Mode > (Passive) Unidirect > (Unknown) Vars Retr > (Unknown) Link Events > (Unknown) Loopback > (Unknown) PDU Sise ... (1518) Remote Information: MAC Address ... (00-00-00-00-00-00) OAM Mode > (Unknown) Unidirect > (Unknown) Vars Retr > (Unknown) Link Events > (Unknown) Loopback > (Unknown) PDU Sise ... (0) Vendor OUI > F-Forward; B-Backward ESC-prev.menu; !-main menu; &-exit; ?-help ... (000000)
1 M/ 1 C
Figure 4-69. Link (802.3ah) Status Screen
Displaying the Bundle Connection Information

You can display information on the current bundle connection, its connectivity status, collected sequence errors, and statistics for underflows and overflows of the jitter buffer (see Chapter 5 for details on the bundle statistics). To display the bundle connection information: 1. From the Status menu, select Connection. The Connection screen is displayed (see Figure 4-70). 2. Select Bundle ID and enter the number of the bundle whose status you wish to display. The Bundle Status screen contains the following information:
IPmux-24 Ver. 3.5
4-79
Destination IP address IP address of the destination device Next hop MAC address MAC address of the next hop device Connectivity Status: DISABLE (The bundle has been disabled by the user.) OK (Both the remote and the local IPmux-24 receive Ethernet frames. However, there may be problems such as sequence errors, underflows, overflows, as explained below). Local Fail (Bundle failure at the local IPmux-24) Remote Fail (Bundle failure at the remote IPmux-24) Unavailable (Network problems or configuration error (only applicable when OAM is enabled)) Validation Fail (The remote IPmux-24 replies, but there is a configuration mismatch (only applicable when OAM is enabled)) Sequence errors (Total number of sequence errors (lost or misordered packets) occurred on the bundle) Jitter buffer underflows (Total number of jitter buffer underflows occurred on the bundle) Jitter buffer overflows (Total number of jitter buffer overflows occurred on the bundle). Monitoring>Status>Connection Destination IP address: Next hop MAC address: Connectivity status: > (1.1.1.1) (000000000000) (OK) (0) (0) (0)
Sequence errors: Jitter buffer underflows: Jitter buffer overflows: 1. Bundle ID[1 127 ] >
... (1)
C - Clear counters; F - Forward Bundle ID ESC-prev.menu; !-main menu; &-exit 1 M/ 1 C
Figure 4-70. Connection Screen
Displaying the System Clock Information

You can view the status of the active system clock. The system clock status information is available only if the transmit clock source of one of the TDM links is set to the system timing.
4-80 Performing Additional Tasks IPmux-24 Ver. 3.5
To display the system clock status: From the Status menu, select System clock.
Monitoring>Status>System clock > > ESC-prev.menu; !-main menu; &-exit Active clock (Adaptive) (Channel 1) 1 M/ 1 C
Figure 4-71. System Clock Status Screen
Displaying the MAC Address Table

IPmux-24 stores all static and learned MAC addresses and associated bridge ports, where each MAC address was defined or learned. When displaying MAC table contents, the user can apply the filters to view MAC addresses that match filtering criteria. Each filter can be used separately or it can be combined with other two to narrow down displayed MAC address range. From MAC Address Displays all static and learned MAC addresses, starting from the specified address To MAC Address Displays all static and learned MAC addresses, ending by the specified address Bridge Port Displays all static and learned MAC addresses associated with the specified bridge port.
To display the MAC address table: 1. From the Bridge menu (Monitoring > Bridge), select MAC Table. The MAC Table menu is displayed. Monitoring>Bridge>MAC Table 1. 2. 3. 4. From MAC Address To MAC Address Bridge Port View MAC Table ... (00-00-00-00-00-00) ... (FF-FF-FF-FF-FF-FF) ... (All/Network/User1/User2/Host/PW) []
Please select item <1 to 4> > ESC-prev.menu; !-main menu; &-exit 1 M/ 1 C
Figure 4-72. MAC Table Menu

2. From the MAC Table menu, define address filtering criteria and select View MAC Table to display the list of static and learned MAC addresses. The View MAC Table screen is displayed.
IPmux-24 Ver. 3.5
4-81
Monitoring>Bridge>MAC Table>View MAC Table MAC address 00-20-D2-23-35-8F 00-20-D2-24-55-21 00-20-D2-23-35-8F Bridge port Network Network Network Status Static Learned Static
1 2 1
> F-Forward B-Backward ESC-prev.menu; !-main menu; &-exit
1 M/ 1 C
Figure 4-73. View MAC Table Menu
Displaying List of Connected Managers

To display list of managers currently connected to IPmux-24: From the Managers menu (Monitoring > Managers), select Connected Managers. The Connected Managers screen is displayed (Figure 4-74). The Connected Managers screen includes the following information: IP Address IP address of the connected remote agent. For an ASCII terminal connection (UART), this field remains empty. Terminal Type Type of the terminal used by the manager (UART, Telnet, SSL, SSH) User Name The login user name. Monitoring>Managers>Connected Managers Index IP Address Terminal Type 1 UART 2 158.15.163.20 SSH 3 158.15.163.30 SSL 4 158.15.163.40 Telnet R - Refresh Table ESC-prev.menu; !-main menu; &-exit; ?-help User Name su su user user 1 M/ 1 C
Figure 4-74. Connected Managers Screen
Displaying the RFER Information

When the Resilient Fast Ethernet Ring (RFER) is enabled, IPmux-24 allows displaying status of the ring, as well as the status of the network ports and MAC addresses the adjacent nodes. To display the RFER status information: From the Protection menu (Monitoring>Status>Protection), select RFER (Proprietary). The RFER (Proprietary) screen is displayed. The RFER (Proprietary) screen displays the following information:
4-82
IPmux-24 Ver. 3.5
Ring status Status of the RFER Closed The RFER is closed, data flow is normal Open The RFER is open, data flow is reversed Disabled The RFER is not operational Port Status Status of the IPmux-24 network port in the RFER application: Blocking The port operates as a blocking node, transferring the RFER status messages only Up The port is operational Down The port is not operational Monitoring>Status>Protection>RFER (Proprietary) Ring Status Port 1 Status Port 2 Status > > > (CLOSED) (UP) (Down) 1 M/ 1 C
Figure 4-75. RFER (Proprietary) Status Screen
Displaying the ERP Status

When the G.8032 Ethernet Ring Protection (ERP) is enabled, IPmux-24 allows displaying status of the ring, as well as the status of the East, West and RPL ports, WTR counter and last received R-APS message. To display the ERP status: From the Protection menu, select ERP (G.8302). The ERP (G.8302) Status screen is displayed. The ERP (G.8302) screen displays the following information: Ring administrative status (Enabled, Disabled) Ring state Current state of the ERP mechanism (Init, Idle, Protected) Bridge number (1) RPL port East/West port number East/West port state (Blocked, Forwarding) East/West port SF source Source of the signal failure (Server Layer, OAM, Admin) WTR counter status Last R-APS Rx Last received R-APS message (N/A, NR, NR-RB, SF)
IPmux-24 Ver. 3.5
4-83
Monitoring>Status>Protection>ERP (G.8302) Ring Number Ring Admin Status Ring State Bridge Number RPL Port East Port Number East Port State East Port SF Source West Port Number West Port State West Port SF Source WTR Status Last R-APS Rx > (1) (Enabled) (Idle) (1) (None) (3) (Forward) (None) (4) (Forward) (None) (Stopped) (NR)
F- Forward Ring; B-Backward Ring; ESC-prev.menu; !-main menu; &-exit 1 M/ 1 C
Figure 4-76. ERP (G.8302) Status Screen
Displaying the LAG Status

When the link aggregation is enabled, it is possible to display the current LAG status. To display the LAG status: 1. From the Status menu (Monitoring > Status), select LAG. The LAG Status screen is displayed (see Figure 4-77). 2. Press f to select an Ethernet port. The status screen includes information on the actor (active) and partner (standby) port status. Monitoring>Status>Protection>LAG Port Label Ethernet Port Actor Port synchronized Partner Port synchronized F - Forward ESC-prev.menu; !-main menu; &-exit; ?-help 1 M/ 1 C
> > > >
(1) (Network 1) (No) (No)
Figure 4-77. LAG Status Screen
Displaying the Dual Homing Status

When the dual homing is enabled, it is possible to display its current status.
4-84 Performing Additional Tasks IPmux-24 Ver. 3.5
To display the dual homing status: From the Protection menu (Monitoring > Status > Protection), select Dual Homing. The Dual Homing Status screen is displayed (see Figure 4-78). The status screen includes information on the current dual homing status, as well the currently active ports. Monitoring>Status>Protection>Dual Dual Homing Status Port 1 Status Port 2 Status Homing > (ENABLED) > (ACTIVE) > (NOT ACTIVE) 1 M/ 1 C
ESC-prev.menu; !-main menu; &-exit; ?-help
Figure 4-78. Dual Homing Status Screen
Displaying the Bundle Protection Status

When the bundle protection is enabled, it is possible to display status of its member bundles. To display the bundle protection status: 1. From the Protection menu (Monitoring > Status > Protection), select Bundle. The Bundle Protection Status screen is displayed (see Figure 4-79). 2. Type f or b to select a bundle redundancy group. The status screen includes information on the current status of the primary and secondary bundles. Monitoring>Status>Protection>Bundle Redundancy Group <1> Primary Bundle Status Secondary Bundle Status F Forward; B Backward ESC-prev.menu; !-main menu; &-exit; ?-help > > (ACTIVE) (NOT ACTIVE)
1 M/ 1 C
Figure 4-79. Bundle Protection Status Screen
Displaying Service OAM (802.1ag) Status

You can view the status of service OAM (802.1ag). To view the service OAM status: 1. Navigate to the OAM (802.1ag) status menu (Monitoring>Status> OAM (802.1ag). The OAM (802.1ag) status screen appears. 2. Select required MD, MA and MEPs. See Table 4-30 for a description of the parameters.
IPmux-24 Ver. 3.5
4-85
Monitoring>Status>OAM (802.1ag) MD Name MA Name Primary Vlan [ 1 4094] Remote MEP Address Remote Mep Status 1. 2. 3. 4. > MD ID MA ID[1 - 16] MEP ID[1 - 8191] Remote MEP ID[1 - 8191] ... ... ... ... ... ... ... ... ... (DEFAULT) (DEFAULT) (0) (00-20-C2-01-02-03) (Fail) (1) (1) (1) (0)
1 M/2 C
Figure 4-80. Service OAM Status Screen Table 4-30. Service OAM Status Parameters
Parameter MD Name MA Name Primary Vlan Remote MEP Address Remote Mep Status Description Displays maintenance domain name corresponding to MD ID Displays maintenance association name corresponding to MA ID Displays VLAN ID from OAM messages Displays the remote MEP MAC address Displays the current status of the remote MEP 14094 MAC address Not Applicable No remote MEP is defined O.K. The remote MEP status is OK according to OAM messages received Fail The remote MEP status is not OK according to OAM messages received Mismerge Mismerge occurred RDI RDI occurred Unexpected Period Unexpected period occurred Cross Connect Defect Displays the cross-connect defect Unexpected Mep Unexpected MD Level Possible Values
Note: This parameter appears only if a cross-connect defect exists.
4-86
IPmux-24 Ver. 3.5
Installation and Operation Manual Parameter Remote MD Format Description Displays the maintenance domain name format of the remote MEP
Chapter 4 Configuration Possible Values None No name defined String Alphanumeric value DNS DNS format MACAndUINT MAC and UINT format
Note: This parameter appears only if the remote MD name format is different from the local MD name format for this MEP.
Remote MD Name Displays the maintenance domain name of the remote MEP
Note: This parameter appears only if the remote MD name is different from the local MD name for this MEP.
Remote MA Format Displays the maintenance association name format of the remote MEP String Alphanumeric value PrimaryVid Primary VLAN Uint Unsigned 16-bit integer ICC Defined by ITU-T Y.1731 (32)
Note: This parameter appears only if the remote MA name format is different from the local MA name format for this MEP.
Remote MA Name Displays the maintenance association name of the remote MEP
Note: This parameter appears only if the remote MA name is different from the local MA name for this MEP.
Remote CC Period Displays the continuity check interval of the remote MEP
Note: This parameter appears only if the continuity check interval is different from the local continuity check interval for this MEP.
MD ID MA ID MEP ID Remote MEP ID Specifies the maintenance domain ID Specifies the maintenance association ID Specifies the MEP ID Specifies the remove MEP ID 116 116 18191 18191
Transferring Software and Configuration Files

Software and configuration files can be transferred using TFTP. Complete information on upgrading the IPmux-24 software is provided in Chapter 6.
TFTP Application
The TFTP protocol is typically used for remote IP-to-IP file transfers via the product unit's Ethernet interface. It can be used, however, for local file transfer as well, as the transfer rate of the Ethernet interface is much faster than that of the RS-232 interface. For TFTP file transfers, a TFTP server application must be installed on the local or remote computer. As it runs in the background, the TFTP server waits for any
IPmux-24 Ver. 3.5
4-87
TFTP file transfer request originating from the product unit, and carries out the received request automatically. A variety of third-party applications, such as 3Cdaemon (available from www.3com.com) or PumpKIN (available from http://kin.klever.net/pumpkin/), allow the instant creation of a TFTP server on a client computer. For more information, refer to the documentation of these applications.
Figure 4-81. Downloading a Software Application File to IPmux-24 via TFTP
Setting-up a TFTP Server

If you use a local laptop and TFTP is the preferred transfer method, a TFTP server application must be installed on it. As mentioned above, third-party applications are available and you should refer to their setup documentation.
Checking the Firewall Settings

TFTP file transfers are carried out through Port 69. You should check that the firewall you are using on the server computer allows communication through this port. To allow communication through Port 69 in Windows XP: 1. Double-click the My Network Places icon, located on the desktop. The My Network Place window appears. 3. On the Network Tasks sidebar, click View network connections. The available network connections are displayed.
4-88
IPmux-24 Ver. 3.5
Figure 4-82. View Network Connections

4. On the Network Tasks sidebar, click Change Windows Firewall settings. The Windows Firewall dialog box appears.
Figure 4-83. Change Firewall Settings

5. Click the Exceptions tab.
IPmux-24 Ver. 3.5
4-89
Figure 4-84. Windows Firewall Dialog Box Exceptions Tab

6. Check whether Port 69 appears on the exceptions list. If it does not, click Add Port and add it to the list of exceptions.
Note
Different firewall types require different configuration. Refer to your firewall's documentation to check how TFTP file transfers can be allowed to pass through it using a UDP-type port.
To transfer a file using TFTP: 1. From the Utilities menu, select File Utilities. 2. From the File Utilities, select Download/Upload using TFTP. 3. From the Download/Upload using TFTP menu, configure the following: File name (Name of the file that you intend to transfer) Command (Operation type) No operation Software download Software upload Configuration download Configuration upload Software download and reset
4-90
IPmux-24 Ver. 3.5
Server IP (IP address of the TFTP server) Retry Timeout (Interval between connection retries in seconds). Total Timeout (TFTP connection timeout in seconds) View Transfer Status (Current status of the TFTP transfer) 4. Save the changes. IPmux-24 starts file transfer using TFTP. Utilities>File Utilities>Download/upload using TFTP 1. 2. 3. 4. 5. 6. File name Command Server IP Retry timeout(sec)[0 - 1000] Total timeout(sec)[0 - 1000] View transfer status ... > ... ... ... > (FILE.IMG) (No operation) (0.0.0.0) (1) (5)
1 M/ 1 C
Figure 4-85. Download/Upload Using TFTP Menu
Resetting the Unit

IPmux-24 supports two types of reset: Reset to the default setting Resetting all parameters Resetting all parameters, except for management values Overall reset of the device.
Resetting to the Defaults

You can reset IPmux-24 to its default settings. The reset to the defaults does not affect the master clock setting. In addition, you can reset local IPmux-24 without affecting its management parameters (host IP address, mask and default gateway, defined network managers and management access methods). To reset IPmux-24 to the default settings: 1. From the System menu, select Factory default. 2. From the Factory Default menu, perform one the following steps: Select All to reset all IPmux-24 parameters to the default settings. Select Except Management to reset all parameters, except for management values. IPmux-24 displays the following message: Configuration will be lost and System will be reset. Continue ??? (Y/N)
IPmux-24 Ver. 3.5
4-91
3. Type Y to confirm the reset. IPmux-24 performs the requested type of reset.
Performing Overall Reset

You can perform the overall reset of IPmux-24. The reset does not affect the unit configuration. To reset IPmux-24: 1. From the Main menu, select Utilities. The Utilities menu appears (see Figure 4-86). 2. From the Utilities menu, select Reset. A confirmation message appears. System will be reset. Continue ??? (Y/N) 3. Type Y to confirm the reset. Utilities 1. File utilities 2. Reset > >
1 M/ 1 C
Figure 4-86. Utilities Menu
4-92
IPmux-24 Ver. 3.5
Chapter 5 Monitoring and Diagnostics

This chapter describes how to: Monitor performance Detect errors Handle events Troubleshoot problems Perform diagnostic tests.
5.1
Monitoring Performance
IPmux-24 provides powerful performance monitoring tools, which consist of the following three levels: E1/T1 statistics Status of the physical E1/T1 parameters (signal, framing, etc.) Ethernet statistics Ethernet connection status (speed, duplex mode, bytes transmitted & received, etc.) Bundle connection statistics PW bundle connection status on the PSN level Link OAM (802.3ah) statistics Service OAM (802.1ag) statistics.
Displaying E1/T1 Statistics

E1/T1 statistics refer to the physical status of the E1/T1 traffic reaching IPmux-24 from the adjacent E1/T1 device. The E1 statistics parameters comply with the G.703, G.704, G.804, G.706, G.732, and G.823 standards. The T1 statistics parameters comply with the ANSI T.403, AT&T R62411, G.703, G.704 and G.804 standards. E1/T1 statistics are monitored and saved under consecutive intervals. Each interval is 15 minutes long. There are 96 intervals, which represent the last 24 hours. Whenever a new interval is started, the counters are reset to zero. The old interval shows the total of events that occurred during its 15-minite period. The current active interval is always marked as interval 0 (you will see that the Time Since counter is running). The previous interval is marked as 1 and so on. The E1/T1 statistic counters cannot be reset manually.
IPmux-24 Ver. 3.5
5-1
To view the E1/T1 statistics: 1. From the Monitoring menu (Figure 5-11), select Statistics. The Statistics menu appears (Figure 5-1). 2. From the Statistics menu, select TDM physical Layer. The TDM physical Layer (E1) or Physical Layer (T1) screen appears (see Figure 5-2). 3. From the TDM physical layer (E1/T1) menu, type F to select the E1/T1 link that you intend to monitor. 4. Select Interval, enter the number of the interval whose statistics you wish to display, and press Enter or Type ^B (Shift+Ctrl+B) to scroll backward or ^F (Shift+Ctrl+F) to scroll forward through the available intervals. Statistics 1. TDM physical layer > 2. Connection > 3. Bridge > > Please select item <1 to 3> ESC-prev.menu; !-main menu; &-exit
1 M/ 1 C
Figure 5-1. Statistics Menu

Monitoring>Statistics>TDM physical layer (E1) Channel ID (1) LOS: LOF (Red): LCV: RAI (Yellow): AIS: FEBE: BES: Time Since (sec): 1. Interval (0) (0) (0) (0) (0) (0) (0) (366) ... (0) Valid Intervals: (96) DM: ES: SES: UAS: LOMF: (0) (0) (0) (0) (0)
F - Forward; ^B - Prev Interval; ^F - Next Interval ESC-prev.menu; !-main menu; &-exit
1 M/ 1 C
Figure 5-2. E1/T1 Statistics
5-2
IPmux-24 Ver. 3.5
Table 5-1. E1/T1 Statistics

Alarm LOS Description Number of seconds with Loss of Signal. A Loss of Signal indicates that there is either no signal arriving from the adjacent E1/T1 device or no valid E1 voltage mask or no voltage alteration between positive and negative amplitudes. For E1 links, the LOS counter will increase by one for each second during which a consecutive 255 pulses have no pulse of negative or positive polarity. For T1 links, the LOS counter will increase by one for each second during which a consecutive 192 pulses have no pulse of negative or positive polarity. A LOS alarm is also indicated by the front panel E1/T1 SYNC LED (red). The green E1/T1 SYNC LED indicates that the E1/T1 synchronization has been restored). Recommendations: Check the physical layer (connectors, cables, etc.) LOF (Red) Number of seconds with Loss of Frame. A Loss of Frame indicates a second that IPmux-24 lost E1/T1 synch opposite its adjacent E1/T1 device. In more detail, this is a period of 2.5 seconds for T1 or 100 msec for E1, during which an OOF (Out Of Frame) error persisted and no AIS errors were detected. For E1 links an OOF defect is declared when three consecutive frame alignment signals have been received with an error. For T1 links, an OOF defect is declared when the receiver detects two or more framing errors within a three msec period for ESF signals and 0.75 msec for D4 signals, or two or more errors out of five or fewer consecutive framing-bits. A LOF alarm is also indicated by the front panel E1/T1 SYNC LED (red). When the IPmux enters a red alarm condition, it sends an Yf bit (yellow alarm or RAI) towards the adjacent E1/T1 device. Recommendations: Check all framing related parameters for E1/T1, and physical connections. LCV Number of seconds with Line Code Violations. A Line Code Violation indicates an error on the pulse structure, either a Bipolar Violation (BPV) or an Excessive Zeros (EXZ) error event. BPV is the occurrence of a pulse with the same polarity as the previous pulse. EXZ is the occurrence of a zero string greater than 15 for AMI or 7 for B8ZS. For an E1 link, the LCV counter will increase by one, for each second during which a BPV or EXZ errors have occurred. For T1 links, the LCV counter will increase for each second during which two consecutive BPVs of the same polarity are received. Complies with ITU-TI.431, 0.161, G775 and G.821 standards. Recommendations: Check physical link for bad/loose connection, impedance matching (balanced or unbalanced) and noisy environment.
IPmux-24 Ver. 3.5
5-3
Chapter 5 Monitoring and Diagnostics Alarm RAI (Yellow) Description
Number of seconds with Remote Alarm Indicators. A Remote Alarm Indicator is sent by a device when it enters RED state (loses sync). RAI Alarm indicates that the adjacent E1/T1 device had lost E1/T1 synch and hence sent an RAI towards the IPmux, which entered a Yellow alarm mode (similarly, IPmux sends RAI towards adjacent E1/T1 when IPmux enters LOF state (Red alarm). In both E1/T1 links the RAI counter increases by one for each second during which an RAI pattern is received from the far end framer. The RAI alarm is also indicated by the front panel ALM LED (red). Recommendations: Check reason for E1/T1 device to be in LOF (out of synch state) by checking physical link integrity at the Tx direction of the IPmux towards E1/T1 device and framing related parameters.
AIS
Number of seconds with Alarm Indication Signals. An Alarm Indication Signal implies an upstream failure of the adjacent E1/T1 device. AIS will be sent to the opposite direction of which the Yellow alarm is sent. For E1 links, the AIS counter will increase by one for each second during which a string of 512 bits contains fewer than three zero (0) bits. For T1 links, the AIS counter will increase by one for each second during which an unframed all 1 signal is received for 3 msec. The AIS condition is indicated by the front panel E1/T1 SYNC LED (red). Recommendations: Check why the E1/T1 device is sending AIS (all ones) stream towards IPmux, for example, Red alarm on a different interface of E1/T1 device (upstream).
FEBE
Number of seconds with Far End Block Errors. The FEBE is sent to transmitting device notifying that a flawed block has been detected at the receiving device. Exists only for E1 MF-CRC4. The FEBE alarm is also indicated by the front panel ALM LED (red). The FEBE counter will increase by one for each second during which the FEBE indication is received. Recommendation: Check physical link integrity.
BES
Bursty Errored Seconds (also known as Errored seconds type B) are seconds during which fewer than 319 and more than one CRC errors occurred with neither AIS nor SEF (Severely Errored Frames) detected. The BES counter will increase by one for each second containing the condition described above. The CRC is calculated for the previous frame in order to prevent processing delay. Complies with AT&T TR-62411 and TR-54016 standards. Not applicable if the line type is set to Unframed. Available only at T1-ESF or E1-CRC4 modes (performance monitoring functionality). Recommendations: Check physical link integrity, G.704 frame format integrity and Sync. (The CRC bits are included in TS0 for E1 multiframe links and in the frame alignment bits for T1 ESF links).
5-4
IPmux-24 Ver. 3.5
Installation and Operation Manual Alarm DM Description
A Degraded Minute is calculated by collecting all the available seconds, subtracting any SES and sorting the result in 60-second groups. The DM counter will increase by one for each 60-second group in which the cumulative errors during the 60-second interval exceed 1E-6. Available in T1-ESF or E1-CRC4 modes only, (performance monitoring functionality). Recommendations: See BES recommendations.
ES
An Errored Second is a second containing one or more of the following: CRC error SEF (OOF) AIS (T1 only) If SES is active ES runs for 10 seconds and then stops. Recommendations: Check physical link integrity. Follow the recommendation concerning LOF, BEF and AIS.
SES
A Severely Errored Second is a second containing one of the following: 320 or more CRC errors events One or more OOF defect One or more AIS events occurred (T1 only) The SES counter will be cleared after reaching 10 and an UAS will then be activated. Recommendations: Check physical link integrity. See also ES alarm recommendation.
UAS
Unavailable Second parameter refers to the number of seconds during which the interface is unavailable. The UAS counter will start increasing after 10 consecutive SES occurrences and will be deactivated as a result of 10 consecutive seconds without SES. After SES clearance the UAS counter will then diminish 10 seconds from the overall count. Recommendations: See above recommendations.
LOMF
Number of seconds of Loss of Multi Frame. A Loss of Multi Frame indicates a second with no sync on the multi frame mode, i.e., the receiving device is unable to detect the four ABCD bits pattern on. The LOMF alarm is also indicated by the front panel ALM LED (red). TS16 MSB in frame 0 for two consecutive multiframes. Available only for E1 multiframe mode (CAS). Recommendations: Check physical link integrity, signaling method (CAS enable only), and framing-related parameters.
IPmux-24 Ver. 3.5
5-5
Displaying Ethernet Statistics

You can display statistic data for the network and user Ethernet ports. To view the Ethernet statistics: 1. From the Statistics menu, select Bridge. The Bridge screen appears (see Figure 5-3). 2. From the Bridge screen, type F to toggle between network, user, management host or pseudowire host ports. Table 5-2 describes the Ethernet statistics data. 3. Type C to reset the port counters. 4. Type A to reset counters of all IPmux-24 Ethernet ports. Monitoring>Statistics>Bridge Channel > Frames Received Total Frames: Total Octets: Oversize Frames Fragments: Jabber: Dropped Frames: CRC Errors: > (User1-Eth2) (0) (0) (0) (0) (0) (0) (0) Frames Transmitted Correct Frames: (0) Correct Octets: (0) Collisions: (0)
F - forward; C - clear counters; A - clear ALL port counters ESC-prev.menu; !-main menu; &-exit
1 M/ 1 C
Figure 5-3. Ethernet Statistics Table 5-2. Ethernet Statistics Parameters

Parameter Frames Received Total Frames Total Octets Oversize Frames Fragments The total number of correct frames received. When a valid connection is established the number should increase steadily. The total number of octets (bytes) received. When a valid connection is established the number should increase steadily. Number of frames exceeding the maximum allowed frame size, but are otherwise valid Ethernet frames (good CRC). The number of frames that are shorter than 64 bytes and have an invalid CRC. Description
5-6
IPmux-24 Ver. 3.5
Installation and Operation Manual Parameter Jabber Description
The number of frames that are too long and have an invalid CRC. A jabber is transmission by a data station beyond the time interval allowed by the protocol, usually affecting the rest of the network. In an Ethernet network, devices compete for use of the line, attempting to send a signal and then retrying in the event that someone else tried at the same time. A jabber can look like a device that is always sending, effectively bringing the network to a halt. Recommendations Check network interface card or any other transmitting devices and external electrical interference.
Dropped Frames
Number of dropped frames due to delivery problems. Recommendations: Check the network interface card.
CRC Errors
The amount of frames with invalid CRCs.
Frames Transmitted Correct Frames Correct Octets Collisions The number of frames successfully transmitted. When a valid connection is established the number should increase steadily. The number of octets successfully transmitted. When a valid connection is established the number should increase steadily. The number of successfully transmitted frames which transmission is inhibited by a collision event. A collision occurs in half-duplex connection when two devices try to transmit at the same time. This counter tracks the number of times frames have collided. This event exists only in half duplex mode, which is not recommended in an IPmux-24 application. Recommendations: Many collisions indicate that the traffic is too heavy for a half-duplex media. Set to a FullDuplex environment if possible.
Displaying Bundle Connection Statistics

The Connection screen provides information about the integrity of the TDMoIP connection, including the status of the jitter buffer. (Each bundle has it own independent jitter buffer). To display the bundle connection statistics information: 1. From the Monitoring menu (Figure 5-11), select Statistics. The Statistics menu appears. 2. From the Statistics menu, select Connection. The Connection screen is displayed (see Figure 5-4). 3. Select Bundle ID, enter the number of the bundle whose statistics you wish to display, and press Enter. 4. Select Interval, enter the number of the interval whose statistics you wish to display, and press Enter. or
IPmux-24 Ver. 3.5
5-7
Type ^B (Shift+Ctrl+B) to scroll backward or ^F (Shift+Ctrl+F) to scroll forward through the available intervals. Monitoring>Statistics>Connection Sequence errors: Jitter buffer underflows: Jitter buffer overflows: Max Jitter buffer deviation [msec]: Time since [sec]: 1. Bundle ID[1 - 511] 2. Interval ... ... ... ... (0) (580) (0) (5) (580) ... (33) ... (0)
>
F - Forward Bundle ID; < - Prev Interval; > - Next Interval ESC-prev.menu; !-main menu; &-exit
1 M/ 1 C
Figure 5-4. Connection Statistics Screen
5-8
IPmux-24 Ver. 3.5
Table 5-3. Bundle Connection Statistics Parameters

Parameter Sequence Errors Description The number of seconds with sequence errors since the last clear. Each packet transmitted by IPmux-24 holds a sequence number. The receiving IPmux-24 checks these numbers at the receive mechanism and expects to see that each new incoming packet is in sequence relative to the previous one (i.e., packet no. 5 is received after no. 4). When, for some reason, this is not the case (i.e., next packet is not in sequence relative to the previous one), this means that there had been a problem with packet flow integrity (and hence data/voice integrity). IPmux will indicate this by increasing the Sequence Errors counter by one. There may be two reasons for a Sequence Error notification: Packet or packets are lost somewhere along the network. Re-ordering of packets by network. Packet re-ordering may occur due to queuing mechanisms, re-routing by the network, or when the router updates very large routing tables. Recommendations: Make sure IPmux-24 traffic has sufficient bandwidth. Make sure Ethernet connection is functioning properly (see Displaying Ethernet Statistics). Make sure Ethernet/IP network provides priority (Quality Of Service) to the IPmux traffic. Priority may be achieved by three means: VLAN tagging, IP TOS marking or by using the constant 2142 decimal value at the UDP destination Port field of each TDMoIP packet. Verify that the IP network devices (switches/routers/modems/etc.) are capable of handling the IPmux PPS rate (Packets Per Second). Make sure the network devices do not drop/lose/ignore packets.
Note: IPmux-24 may support a reordering mechanism, which can sort packets back to their original order in some situations.
IPmux-24 Ver. 3.5
5-9
Chapter 5 Monitoring and Diagnostics Parameter Jitter Buffer Underflows Description
The number of seconds with jitter buffer underflows since the last clear. IPmux-24 is equipped with a Packet Delay Variation Tolerance buffer, also called a jitter buffer, responsible for compensating for IP networks delay variation (IP jitter). The jitter buffer is configured in milliseconds units and exists for each bundle independently. Explanation: Packets leave the transmitting IPmux-24 at a constant rate, but the problem is that they are reaching the opposite IPmux-24 at a rate which is NOT constant, due to network delay variation (caused by congestion, re-routing, queuing mechanisms, wireless media, half-duplex media, etc.). The TDM devices at both ends require a constant flow of data, so they cant tolerate delay variation. Therefore the jitter buffer is required in order to provide the TDM equipment with a synchronous and constant flow. This is done as follows: Upon startup, the jitter buffer stores packets up to its middle point (the number of packets correlates to the buffers configured depth in milliseconds). Only after that point it starts outputting the E1/T1 flow towards its adjacent TDM device. The stored packets assure that the TDM device will be fed with data even if packets are delayed by the IP network. Obviously, if packets are delayed too long, then the buffer is gradually emptied out until it is underflowed. This situation is called buffer starvation. Each underflow event increases the jitter buffer underflow counter by one and indicates a problem in the end-to-end voice/data integrity. The second functionality of the jitter buffer is that in adaptive mode the jitter buffer is also a part of a mechanism being used to reconstruct the clock of the far end TDM side. An underflow situation can be a cause of: Buffer starvation: Packets delay variation causes the buffer to empty out gradually until it is underflowed. Continuous Sequence Errors. The sequence error means a halt in the valid stream of packet arrival into the jitter buffer. Packets are being stopped/lost/dropped. Too small jitter buffer configuration that cant compensate for the network delay variation. When all system elements are not locked on the same master clock, it will lead to a situation in which data is clocked out of the jitter buffer at a rate different from the one it is clocked into. This will gradually result in either an overflow or underflow event, depending on which rate is higher. The event will repeat itself periodically as long as the system clock is not locked. When an overflow (see below) situation occurs, IPmux-24 instantly flushes the jitter buffer, causing a forced underflow. So when you need to calculate the real underflow events and not the self-initiated ones, subtract the number of overflows from the total number of underflows counted by the device. Recommendations: Try increasing the jitter buffer size. Check reasons for sequence errors or lost/dropped packets (if present), system clocking configuration, Ethernet environment (full duplex) and connection, packets drop/loss/ignore by routers/switches or non-uniform packets output by routers/switches due to queuing mechanisms. Make sure the same amount of TS for bundle is configured on each side of the IPmux-24 application, and that the TDM bytes in frame parameter is identical in both IPmux-24 units. Make sure Ethernet/IP network provides priority (Quality Of Service) to the IPmux-24 traffic. Priority may be achieved by three means: VLAN tagging, IP TOS marking or by using the constant 2142 decimal value at each IPmux UDP destination Port field.
5-10
IPmux-24 Ver. 3.5
Installation and Operation Manual Parameter Jitter Buffer Overflows Description
The number of seconds with at least one jitter buffer overflow event since the last clear. Explanation: In steady state, the jitter buffer is filled up to its middle point, which means it has the space to hold an additional similar quantity of packets. Overflow is opposite phenomenon of the Underflow, i.e., when a big burst of packets reaches the IPmux (a burst with more packets than the Jitter Buffer can store), the buffer will be filled up to its top. In this case, an unknown number of excessive packets are dropped and hence IPmux initiates a forced underflow by flushing (emptying) the buffer in order to start fresh from the beginning. An overflow situation always results in an immediate Underflow, forced by the IPmux. After the buffer is flushed, the process of filling up the buffer is started again, as explained above (Underflow section). An overflow situation can be a cause of: A big burst of packets, filling up the buffer completely. The burst itself can often be a cause of some element along the IP network queuing the packets and then transmitting them all at once. Insufficient jitter buffer size. When system isnt locked on the same clock, it will lead to a situation in which data is clocked out of the jitter buffer at a rate different from the one it is clocked into. This will gradually result in either an overflow or underflow event, depending on which rate is higher. The event will repeat itself periodically as long as the system clock is not locked. Recommendations: Check network devices and try increasing jitter buffer configuration. Check systems clocking configuration Make sure the same amount of TS for bundle is configured on each side of the IPmux-24 application, and that the TDM bytes in frame parameter is identical in both IPmux-24 units
Max Jitter Buffer Deviation Time Since (sec)
The maximum jitter buffer deviation (msec) in the interval (300 sec). This is the maximum jitter level IPmux-24 had to compensate for in the selected interval. The time elapsed, in seconds, since the beginning of the selected interval.
Displaying Service OAM (8021ag) Statistics

You can display end-to-end connectivity and performance monitoring data for the existing service OAM. The statistics are available for the 15-minute and 24-hour periods. To display the service OAM statistics: 1. From the Statistics menu, select the following: 15 Min Intervals (service OAM statistics for a selected 15-min interval) 24 Hours Counters (service OAM statistics for the last 24 hours) Service Counters (Total OAM statistics collected since the service was enabled) The selected OAM Statistics screen is displayed as illustrated in Figure 5-5 and Figure 5-6. Table 5-4 and Table 5-5 explain the service OAM statistics parameters.
IPmux-24 Ver. 3.5
5-11
2. Select required MD, MA, MEP and service. 3. Press <Ctrl + F> or <Ctrl + B> to select an interval (196).
Note
No interval selection is available for the 24-hour statistics.
Monitoring>Statistics>OAM>15 Min. Counters Frames Above Delay Obj.... Frames Below Delay Obj.... Frames Above DV Obj. ... Frames Below DV Obj. ... Frames Transmitted ... Frames Lost ... Unavailable Seconds ... 1. 2. 3. 4. 5. MD ID MA ID MEP ID[1 - 8191] Service Interval ... ... ... ... ... (0) (0) (0) (0) (101902) (0) (101899) (1) (1) (3443) (1) (1) Elapsed Time Min. RT Delay (Msec) Avg. RT Delay (Msec) Max. RT Delay (Msec) Avg. DV Max. DV ... (102767) ... (0.0) ... (0.0) ... (0.0) ... (0.0) ... (0.0)
Please select item <1 to 3> F - Forward(SVC); B - Backward(SVC); ^F - Forward(Int.); ^B - Backward(Int.) ESC-prev.menu; !-main menu; &-exit 1 Mngr/s
Figure 5-5. Service OAM Statistics (15-Minute Interval) Table 5-4. Service OAM Interval Statistic Parameters
Parameter Frames Above Delay Obj. Frames Below Delay Obj. Frames Above DV Obj. Frames Below DV Obj. Frames Transmitted Frames Lost Unavailable Seconds Elapsed Time Min. RT Delay Avg. RT Delay Description Number of frames that exceeded delay objective Number of frames below or equal delay objective Number of frames that exceeded delay variation objective Number of frames below or equal delay variation objective Total number of OAM frames transmitted in the selected interval Number of frames lost in the selected interval Number of seconds during which the service was unavailable in the current interval Time (in seconds) elapsed from beginning of the interval 0900 Minimum round trip delay (in mseconds) calculated in the interval (or up to elapsed time in selected interval) Average round trip delay (in mseconds) calculated in the interval (or up to elapsed time in current interval)
5-12
IPmux-24 Ver. 3.5
Installation and Operation Manual Parameter Max. RT Delay Avg. DV Max. DV Description
Maximum round trip delay (in mseconds) calculated in the interval (or up to elapsed time in current interval) Average delay variation (in mseconds) calculated in the interval (or up to elapsed time in selected interval) Maximum delay variation (in mseconds) calculated in the interval (or up to elapsed time in selected interval)
Monitoring>Statistics>OAM>Service Counters OAM Tx frames counter OAM Frames lost counter OAM Frame loss Ratio Elapsed time Unavailable seconds Unavailability Ratio Current Delay (msec) Current Delay Variation (msec) 1. MD ID 2. MA ID 3. MEP ID[1 - 8191] 4. Service ... ... ... ... ... ... ... ... (2087328632) (0 (0) (1487) (0) (0) (0.0) (0.0)
... (1) ... (1) ... (3443) ... (1)
Please select item <1 to 4> C-Reset Counters ESC-prev.menu; !-main menu; &-exit
1 Mngr/s
Figure 5-6. Service OAM Counters Table 5-5. Service OAM Statistic Parameters
Parameter OAM Tx Frames Counter OAM Frames Lost Counter OAM Frame Loss Ratio Elapsed Time Unavailable Seconds Unavailability Ratio Current Delay Current Delay Variation Description Total number of OAM frames transmitted since the service was enabled Total number of OAM frames lost since the service was enabled Total number of lost OAM frames divided by total number of transmitted OAM frames since the service was enabled Time (in seconds) elapsed since the service was enabled Total number of unavailable seconds since the service was enabled Total number of unavailable seconds divided by elapsed time Delay of OAM frames (in msec) Delay variation (in msec)
IPmux-24 Ver. 3.5
5-13
Displaying Link OAM (802.3ah) Statistics

You can display link OAM statistics for the Ethernet ports. To display link OAM statistics: 1. Navigate to the link OAM statistics menu (Monitoring > Status > Physical ports > Link (802.3ah) > Statistics). The link OAM statistics screen appears as illustrated in Figure 5-7. 2. Type f or b to select required Ethernet port. IPmux-24 Monitoring>Status>Physical ports>Link (802.3ah)>Statistics Ethernet Port OAM Mode Link OAM Version Rx Rx Rx Rx Rx Rx Information Var Request Var Response Loopback Ctrl Event Notify Org Specific ... (1) (Passive) ... (01.22.0) ... ... ... ... ... ... (0) (0) (0) (0) (0) (0) Tx Tx Tx Tx Tx Tx Information Var Request Var Response Loopback Ctrl Event Notify Org Specific ... ... ... ... ... ... (0) (0) (0) (0) (0) (0)
Rx Unrecognized ... (0) > F-Forward; B-Backward; ESC-prev.menu; !-main menu; &-exit
1 M/2 C
Figure 5-7. Ethernet Link OAM Statistics Screen
Displaying the ERP Statistics

When the G.8032 Ethernet Ring Protection (ERP) is enabled, IPmux-24 allows collecting statistics on R-APS messages sent and received by the East and West ports.
5-14
IPmux-24 Ver. 3.5
Monitoring>Statistics>Protection>ERP (G.8302) Ring Number East Port R-APS SF Rx East Port R-APS NR Rx East Port R-APS NR,RB Rx Total Valid Rx Total Errors Rx West Port R-APS SF Rx West Port R-APS NR Rx West Port R-APS NR,RB Rx Total Valid Rx Total Errors Rx (1) (5) (3) (0) (0) (0) (5) (3) (0) (0) (0) East Port R-APS SF Tx East Port R-APS NR Txx East Port R-APS NR,RB Tx Total Valid Tx Total Errors Tx West Port R-APS SF Tx West Port R-APS NR Tx West Port R-APS NR,RB Tx Total Valid Tx Total Errors Tx (5) (3) (0) (0) (0) (5) (3) (0) (0) (0)
F- Forward Ring; B-Backward Ring; C- Clear counters ESC-prev.menu; !-main menu; &-exit
1 M/2 C
Figure 5-8. ERP (G.8032) Statistics Screen Table 5-6. ERP (G.8032) Statistic Parameters
Parameter R-APS SF Message Tx/Rx Description Total number of R-APS Signal Fail (SF) messages received or transmitted by East/West port. Received R-APS Signal Fail message indicates a failed port in the ring. Transmitted R-APS Signal Fail message indicates a failed port in the node. Total number of R-APS No Request (NR) messages received or transmitted by East/West port. Received R-APS No Request message indicates absence of failed ports in the ring. Transmitted R-APS No Request message indicates that the node fixed its failed port. Total number of R-APS No Request (NR), RPL Blocked (RB) messages received or transmitted by East/West port. Received R-APS No Request, RPL Blocked message indicates that RPL port is blocked and all other not-failed blocked ports are unblocked in the ring. Transmitted from the RPL No Request, RPL Blocked message indicates that RPL port is blocked. Total number of valid R-APS messages received or transmitted by East/West port Total number of errored R-APS messages received or transmitted by East/West port
R-APS NR Message Tx/Rx
R-APS NR, RB Tx/Rx
Total Valid Rx/Tx Total Errors Rx/Tx
IPmux-24 Ver. 3.5
5-15
5.2

Detecting Errors
IPmux-24 employs the following error and fault detection methods: Power-up self test LEDs Alarms and traps Statistic counters.
Power-Up Self-Test
IPmux-24 performs hardware self-test upon turn-on. The self-test sequence checks the critical circuit functions of IPmux-24 (framer and bridge). The self-test results are displayed via the Diagnostics menu. To display the self-test results: 1. From the Main menu, select Diagnostics. 2. The Diagnostics menu appears (see Figure 5-9). From the Diagnostics menu, select Self Test Results. The Self Test Results screen appears (see Figure 5-10). Diagnostics 1. 2. 3. 4. > Please select item <1 to 4> ESC-prev.menu; !-main menu; &-exit Ping Trace route Loopback Self Test Results > > > >
1 M/ 1 C
Figure 5-9. Diagnostics Menu

Diagnostics>Self Test Results Framer Test (Pass) Bridge Test (Pass) > ESC-prev.menu; !-main menu; &-exit 1 M/ 1 C
Figure 5-10. Self Test Results Screen
5-16
Detecting Errors
IPmux-24 Ver. 3.5
LEDs
LEDs located on the device inform users about Ethernet, E1/T1 link and alarm status. For the detailed description of LEDs and their functions, refer to Chapter 3.
Alarms and Traps

IPmux-24 reports problems and fault conditions by storing events in the event log. For the detailed description of the events and instructions on how to use the event log, see Handling Events below.
Statistic Counters
The TDM and Ethernet interface performance as well as pseudowire connection data is continuously collected during equipment operation. The collected data enables the system administrator to monitor the transmission performance, and thus the quality of service provided to users, for statistical purposes. For detailed description of the statistic counter, see Monitoring Performance above.
5.3
Handling Events
IPmux-24 maintains an Event Log file, which can hold up to 2048 events. All events are time-stamped.
Displaying Events
To display events: 1. From the Main menu, select Monitoring. The Monitoring menu is displayed (see Figure 5-11). 2. From the Monitoring menu, select Event Log. The Event Log menu is displayed (see Figure 5-12). 3. From the Event Log menu, select Read log file. The Read Log File screen appears (see Figure 5-13). 4. In the Read Log File screen, use the <Ctrl> + <U> and <Ctrl> + <D> key combinations to scroll the alarm list up and down.
IPmux-24 Ver. 3.5
Handling Events
5-17
Monitoring 1. 2. 3. 4. > Please select item <1 to 3> ESC-prev.menu; !-main menu; &-exit Statistics Status Event Log Managers > > > >
1 M/ 1 C
Figure 5-11. Monitoring Menu

Monitoring>Event log 1. Read log file 2. Clear log file > Please select item <1 to 2> ESC-prev.menu; !-main menu; &-exit []
1 M/ 1 C
Figure 5-12. Event Log Menu

Monitoring>Event Log>Read log file Index 30 29 28 27 26 25 24 Log entry 18:20:03 LOGIN VIA TERMINAL 18:02:13 UAS START 18:02:03 LOS START 18:02:03 COLD START 17:56:48 UAS START 17:56:38 LOS START 17:56:38 COLD START
2004-01-22 2004-01-22 2004-01-22 2004-01-22 2004-01-22 2004-01-22 2004-01-22
TDM SLOT TDM SLOT TDM SLOT TDM SLOT
CH 1 CH 1 CH 1 CH 1
> ^D - scroll down, ^U - scroll up ESC-prev.menu; !-main menu; &-exit; ?-help
1 M/ 1 C
Figure 5-13. Read Log File Table 5-7 presents the event types that appear in the event log alphabetically, as
well as the actions required to correct the event (alarm) indication. To correct the reported problem, perform corrective actions in the given order until the problem is corrected. If the problem cannot be fixed by carrying out the listed actions, IPmux-24 must be checked by the authorized technical support personnel.
5-18
Handling Events
IPmux-24 Ver. 3.5
Clearing Events
To clear events: 1. From the Event Log menu, select Clear log file. IPmux-24 displays the following message: Logfile will be cleared. Continue ??? (Y/N) 2. Type Y to confirm the log file clearing.
Table 5-7. Event List

Event COLD START CON LOCAL FAIL CONNECTIVITY MISMERGE Description IPmux-24 has been powered up Ethernet frames are not received by the local IPmux-24 on the specified connection IPmux-24 MEP received a CCM with correct MD level (which is equal to the IPmux-24 MEP MD level), but incorrect MA ID. This indicates that CCMs from a different service have merged with CCMs belonging to one of the IPmux-24 MEPs. Ethernet frames are not received by the remote IPmux-24 on the specified connection Bundle X has been disabled Bundle connection failure has ended Remote TDM PW device is not available (only applicable when OAM is Enabled) Connection is invalid (only applicable when OAM is Enabled) IPmux-24 is in dual homing protection mode. Ethernet link 1 is currently active. IPmux-24 is in dual homing protection mode. Ethernet link 2 is currently active. IPmux-24 MEP stopped receiving CCM from its peer MEP IPmux-24 has encountered an internal fatal error T1 inband loopback has been activated on remote IPmux-24 T1 inband loopback has been deactivated on remote IPmux-24 Corrective Action None Check path over PSN
1. Check the 802.1ag OAM

configuration.
2. Check path over PSN.
CON REMOTE FAIL
Check path over PSN
CON CLOSED TDM SLOT BUNDLE X CON SYNC CON UNAVAILABLE CON VALIDATION FAIL DUAL HOMING: ETHERNET SLOT CH1 IS ACTIVE DUAL HOMING: ETHERNET SLOT CH2 IS ACTIVE FAIL FATAL ERROR IN BAND REMOTE LOOP START IN BAND REMOTE LOOP END
None None Check the connection of the remote TDM PW device Check the bundle parameters None None Check connectivity to remote device IPmux-24 requires servicing None None
IPmux-24 Ver. 3.5
Handling Events
5-19
Chapter 5 Monitoring and Diagnostics Event IN BAND LOCAL LOOP START IN BAND LOCAL LOOP END INVALID LOGIN VIA TERMINAL INVALID LOGIN VIA WEB Description T1 inband loopback has been activated on local IPmux-24 T1 inband loopback has been deactivated on local IPmux-24 Invalid user name or password was entered, when attempting to access IPmux-24 via local terminal Invalid user name or password was entered, when attempting to access IPmux-24 via Web browser Invalid user name or password was entered, when attempting to access IPmux-24 via Telnet The current IP address was assigned the IPmux-24 host by DHCP server The current IP address was released by IPmux-24 IPmux-24 is in LAG mode. Ethernet link 1 is currently active. Line AIS state detected has ended IPmux-24 has AIS (alarm indicator signal) state on its E1/T1 port LINE FEBE state detected has ended IPmux-24 has LINE FEBE state on its E1/T1 port LINE RAI state detected has ended IPmux-24 has LINE RAI (remote alarm indication) state on its E1/T1 port The unit was accessed via local terminal The unit was accessed via Web browser The unit was accessed via Telnet IPmux-24 has a LOF (loss of frame) state on its E1/T1 port
Installation and Operation Manual Corrective Action None None
None
None
INVALID LOGIN VIA TELNET IP x.x.x.x ASSIGNED BY SERVER x.x.x.x IP x.x.x.x IS RELEASED LAG: ETHERNET SLOT CH1 IS ACTIVE LINE AIS END LINE AIS START LINE FEBE END LINE FEBE START
None
None None None None Check for a fault at the PDH network, on the receive direction None Check for errors in the E1/T1 connection on the transmit direction None Check for a fault at the E1/T1 connectivity on the transmit direction None None None
LINE RAI END LINE RAI START
LOGIN VIA TERMINAL LOGIN VIA WEB LOGIN VIA TELNET LOF START
1. Check the E1/T1 cable

connection.
2. Check all framing-related

parameters for E1/T1 interface. LOF END LOS END LOS START LOF state detected has ended LOS state detected has ended IPmux-24 has a LOS (loss of signal) state on its E1/T1 port None None
1. Check the E1/T1 cable

connection.
5-20
Handling Events
IPmux-24 Ver. 3.5
Installation and Operation Manual Event Description
Chapter 5 Monitoring and Diagnostics Corrective Action
2. Check input signal.

LOSS OF CONTINUITY: EVC X MEP X REMOTE MEP X A MEP receives no CCM frames from a peer MEP during an interval equal to 3.5 times the CCM transmission period
1. Check connectivity to remote

device.
2. Check devices for hardware

failures.
3. Check the 802.1ag OAM

configuration. RDI DETECTED SYSTEM USER RESET UAS START UAS END UNEXPECTED MD LEVEL RDI is detected in CCM received from a peer MEP The user initiated software reset via the system menu Ten consecutive severely errored seconds were detected Ten consecutive seconds without SES were detected IPmux-24 MEP received a CCM with incorrect MD level (less than the MEPs own level) IPmux-24 MEP received a CCM with correct MD level, correct MA ID, but an incorrect MEP ID IPmux-24 MEP received a CCM with correct MD level, correct MA ID, correct MEP ID, but incorrect value of the Period field (the value is different from a transmission period of the MEPs CCM) Check connectivity to remote device None Check physical interface connections. None Check the 802.1ag OAM configuration Check the 802.1ag OAM configuration Check the 802.1ag OAM configuration
UNEXPECTED MEP
UNEXPECTED PERIOD
Masking Alarm Traps

You can mask some IPmux-24 alarm traps to prevent it from being sent to the management stations. To mask alarms: 1. From the Management menu, select Alarm trap mask. The Alarm Trap Mask menu appears (see Figure 5-14). 2. From the Alarm Traps Mask menu, select Alarm ID to choose alarm that you intend to mask.
Note
List of the alarm traps can be displayed by typing ?.

3. Select Trap Status to enable or disable masking of the selected alarm.
IPmux-24 Ver. 3.5
Handling Events
5-21
Configuration>System>Management>Alarm trap mask Active alarm traps: 1. Alarm ID <use 'help'>[1 - 40] 2. Trap status > Please select item <1 to 2> S - Save; ? - Help ESC-prev.menu; !-main menu; &-exit > (-) ... (39) (Masked)
1 M/ 1 C
Figure 5-14. Alarm Trap Mask Menu Table 5-8. Trap List
Trap alarmLOS alarmLOF alarmAIS alarmRDI alarmFEBE alarmExtClk BundleConenctionStatus Description, Severity Loss of Signal (LOS Physical Layer), major Loss of Frame (LOF Physical Layer), major Alarm Indication Signal Received (AIS Line Physical Layer), major Remote Defect Indication Received (RDI Line Physical Layer), major Far End Block Error (FEBE Line Layer), major External clock source has failed, minor Bundle connectivity status: prtStatusChangeTrap ethIfRingStatusChange sysRedundancyActivePortTrap ethOamCfmDefectCondition O.K major Remote fail minor Local fail major Validation Fail major Unavailable major 1.3.6.1.4.1.164.6.1.0.3 1.3.6.1.4.1.164.3.1.6.1.4.0.1 1.3.6.1.4.1.164.3.3.0.9 1.3.6.1.4.1.164.3.1.6.1.3.0.1 OID 1.3.6.1.4.1.164.6.1.3.0.7 1.3.6.1.4.1.164.6.1.3.0.8 1.3.6.1.4.1.164.6.1.3.0.10 1.3.6.1.4.1.164.6.1.3.0.11 1.3.6.1.4.1.164.6.1.3.0.12 1.3.6.1.4.1.164.6.1.0.10 1.3.6.1.4.1.164.6.1.3.0.15
Change in the NET or NET/USER port status when Ethernet ring is active Change in Ethernet ring status Change of active port status in bundle redundancy group Status of the 802.1ag OAM CC traffic: fail major mismerge major rdi major status active major status not active major
5-22
Handling Events
IPmux-24 Ver. 3.5
Installation and Operation Manual Trap Description, Severity erpPortStateChanged erpRingStateChanged unexpectedMep major unexpectedMdLevel major
Chapter 5 Monitoring and Diagnostics OID
Change in an ERP port status Change in ERP ring status
1.3.6.1.4.1.164.3.1.6.1.4.0.2 1.3.6.1.4.1.164.3.1.6.1.4.0.3
5.4
Troubleshooting
Table 5-9 presents the event types as they appear on the Event Log File and lists the actions required to correct the event (alarm) indication. Table 5-9. Troubleshooting Chart
Fault E1/T1 equipment connected to IPmux-24 is not synchronized with IPmux-24. Probable Cause Configuration or physical layer problems Remedial Action
1. Check cables and physical

connectivity.
2. Check IPmux-24 E1/T1

configuration and, if necessary, other IPmux-24 parameters.
3. Check E1/T1 physical connection

(use loopbacks). Slips and errors in E1/T1 equipment Ethernet port in switch and IPmux-24 are not in the same rate or duplex mode Ethernet port is set to work in half duplex mode (may cause extreme PDV because of collisions and backoffs) Timing configuration is not properly set (periodic buffer under/overflows shown on IP channel status menu) Network PDV or lost frames
1. Check E1/T1 physical connection

(use loopbacks).
2. Check timing settings according to

explanation in this manual.
3. Check switch and IPmux-24 port

configuration (negotiation, rate, duplex mode).
4. Check PDV introduced by the

network, and, if necessary, increase PDVT jitter buffer setting..
Echo in voice
High delay in voice path
1. Check network delay and try to

decrease it.
2. Try to decrease PDVT (jitter) buffer.
5.5

Testing the Unit
Diagnostic capabilities of IPmux-24 include: Activating loopbacks (internal and external) Responding to T1 inband loopback activation code
IPmux-24 Ver. 3.5
Testing the Unit
5-23
Pinging IP hosts Running a trace route Running 802.1ag tests (loopback and trace route).
Running Diagnostic Loopbacks

External Loopback
IPmux-24 can be set to start an external loopback to test the connection between the E1/T1 port and the PBX. In this mode, data coming from the PBX is both looped back to the PBX and transmitted forward to the IP network (see Figure 5-15).
Note
External loopback cannot be activated on the TDM links with transmit clock source configured to adaptive.
Figure 5-15. External Loopback
Internal Loopback
The E1/T1 module can be set to start an internal loopback to test the connection between the E1/T1 port and the IP network. In this mode, data coming from the IP network is both looped back to the IP network and transmitted forward to the PBX connected to the E1/T1 port (see Figure 5-16).
Figure 5-16. Internal Loopback

To run a loopback: 1. From the Diagnostics menu (Figure 5-9), select Loopback. The Loopback menu is displayed (see Figure 5-17). 2. From the Loopback menu, type F to select the E1/T1 link that you intend to test. 3. From the Loopback menu, select Loopback state, and choose loopback that you intend to run (Internal or External).
5-24
Testing the Unit
IPmux-24 Ver. 3.5
Diagnostics>Loopback Channel ID 1. Loopback State >
(1) > (External)
F - forward; S - save Please select item <1 to 1> ESC-prev.menu; !-main menu; &-exit
1 M/ 1 C
Figure 5-17. Loopback Menu

To disable a loopback: From the Loopback menu, select Loopback state, and set it to Disable.
To display the diagnostic loopback status: From the Status menu, select Diagnostics loopback.
Monitoring>Status>Diagnostics loopback Channel ID (1) Loopback state: > (Disable)
>
1 M/ 1 C
Figure 5-18. Diagnostic Loopback Screen
Activating T1 Inband Loopbacks

T1 physical loopbacks can be activated by receiving a loopback activation code from TDM equipment connected to the T1 port. When IPmux-24 receives a loopback activation code, it closes an external loopback (see Figure 5-19), or translates the TDM-based loopback activation code into the packet-based pattern and sends it to the opposite IPmux device, which closes an internal loopback (see Figure 5-20). The inband loopback can be activated only if the OAM connectivity is enabled and only one bundle is configured for each port of the device. An inband loopback is deactivated automatically, if: TDM connection is down Ethernet connection is down The user activated an internal or external loopback manually.
IPmux-24 Ver. 3.5
Testing the Unit
5-25
Figure 5-19. T1 Inband Loopback Performed by Local IPmux-24
Figure 5-20. T1 Inband Loopback Performed by Remote IPmux-24

To activate an inband loopback: From the Inband Loop Detection menu (Diagnostics > Loopback > Inband Loop Detection), perform the following: Select Loop Location and set it as follows: Local System (External loopback is activated in the local IPmux-24) Remote System (Internal loopback is activated in the remote IPmux-24) Disable (IPmux-24 ignores inband activation code). Define loop-up code length (Length of the code to be sent by the TDM device in order to activate a loopback) Define loop-up code (Code to be sent by the TDM device in order to activate a loopback) Define loop-down code length (Length of the code to be sent by the TDM device in order to deactivate a loopback) Define loop-up code (Code to be sent by the TDM device in order to deactivate a loopback).
5-26
Testing the Unit
IPmux-24 Ver. 3.5
Diagnostics>Loopback (T1)>Inband Loop Detection 1. 2. 3. 4. 5. Loop Loop Loop Loop Loop Location up length[1 - 8] up code[Hex] down length[1 - 8] down code[Hex] > (Local System) ... (5) ... (10) ... (3) ... (4)
> Please select item <1 to 5> ESC-prev.menu; !-main menu; &-exit
1 M/ 1 C
Figure 5-21. Inband Loop Detection Menu
Pinging IP Hosts
You can ping remote IP host to check the IPmux-24 IP connectivity. To ping an IP host: 1. From the Diagnostics menu (Figure 5-9), select Ping. The Ping menu appears (see Figure 5-22). 2. From the Ping menu, configure the following: Interface (Direction (switch port), to which the ping is sent): System host IP (IPmux-24 sends ping to an IP address in the management subnet) PW host IP (IPmux-24 sends ping to an IP address in the PW traffic subnet) Redundant PW host IP (IPmux-24 sends ping to an IP address in the PW traffic subnet) Destination IP Address (IP address of the host that you intend to ping): 0.0.0.0 to 255.255.255.255. VLAN Tagging: Enable (VLAN tagging is enabled) Disable (VLAN tagging is disabled) VLAN ID: 14095 VLAN Priority: 07
Note
The VLAN ID and VLAN Priority configuration is available only if the VLAN tagging is enabled.
Number of frames to send: 050. 0 means endless ping. 3. Select Ping Send to start sending pings.
IPmux-24 Ver. 3.5
Testing the Unit
5-27
Diagnostics>Ping 1. Interface 2. Destination IP address 3. VLAN tagging 4. VLAN ID[1 - 4095] 5. VLAN priority[0 - 7] 6. Number of frames to send[0 - 50] 7. Send Ping > Please select item <1 to 7> ESC-prev.menu; !-main menu; &-exit (PW Host IP) ... (0.0.0.0) (Enable) ... (0) ... (0) ... (1)
1 M/ 1 C
Figure 5-22. Ping Menu
Running a Trace Route

You can run a trace route to a remote IP host to check the IPmux-24 system host IP connectivity.
Note
Trace route cannot be used to check pseudowire connectivity.

To run a trace route to an IP host: 1. From the Diagnostics menu (Figure 5-9), select Trace route. The Trace route menu appears (see Figure 5-23). 2. From the Trace route menu, configure the following: Interface (Direction (switch port), via which the traceroute request is sent): System host IP (IPmux-24 traces route to an IP address in the management subnet) PW host IP (IPmux-24 traces route to an IP address in the PW traffic subnet) Redundant PW host IP (IPmux-24 traces route to an IP address in the PW traffic subnet) Destination IP Address (IP address of the host to which you intend to trace the route): 0.0.0.0 to 255.255.255.255. VLAN Tagging: Enable (VLAN tagging is enabled) Disable (VLAN tagging is disabled) VLAN ID: 14095 VLAN Priority: 07
5-28
Testing the Unit
IPmux-24 Ver. 3.5
Note
The VLAN ID and VLAN Priority configuration is available only if the VLAN tagging is enabled.
3. Select Trace route send to start the trace route.
Diagnostics>Trace route 1. 2. 3. 4. 5. 6. > Please select item <1 to 6> ESC-prev.menu; !-main menu; &-exit Interface Destination IP address VLAN tagging VLAN ID[1 - 4095] VLAN priority tag [0 - 7] Trace route send (System Host IP) ... (0.0.0.0) (Enable) ... (1) ... (0)
1 M/ 1 C
Figure 5-23. Trace Route Menu
Running 802.1ag Tests

You can use loopback or link trace to test OAM connectivity and links. You run the OAM tests from the OAM test menu (Diagnostics > OAM Tests).
Performing OAM Loopback

This diagnostic utility verifies OAM connectivity on Ethernet connections. You can execute the loopback according to the destination address or the remote maintenance end point (MEP).
Note
The option for remote MEP ID is available only if IPmux-24 can resolve at least one remote MEP MAC address.
To verify OAM connectivity: 1. Navigate to the OAM Tests Loopback menu (Diagnostics > OAM Tests (802.1ag) > Loopback). The OAM Tests Loopback menu appears (see Figure 5-24). 2. Define the test parameters according to Table 5-10. 3. Select Send Loopbacks to send the specified number of OAM loopbacks. The loopbacks are sent. 4. Select Results. The Results screen appears as illustrated in Figure 5-25. The result parameters are described in Table 5-11.
IPmux-24 Ver. 3.5
Testing the Unit
5-29
Main Menu > Diagnostics > OAM Test (802.1ag) > Loopback 1. 2. 3. 4. 5. MD ID MA ID MEP ID[1 - 8191] Destination Type Remote MEP ID Remote MEP Address 6. Number of LBs to Send[0 - 50] Please select item <1 to 9> ESC-prev. menu; !-main menu; &-exit ... (1) ... (1) ... (1) (Remote MEP ID) ... (150) ... (00-20-D2-C3-C3-C3) ... (0)
1 M/2 C
Figure 5-24. OAM Loopback Menu Table 5-10. OAM Loopback Parameters
Parameter MD ID MA ID MEP ID Destination Type Description Specifies the maintenance domain ID Specifies the maintenance association ID Specifies the MEP ID The destination type for the loopback Possible Values 116 116 18191 Destination Address Loopback is sent to a MAC address Remote MEP ID Loopback is sent to a destination ID Default: Remote MEP ID Destination Address The MAC address of the destination device Unicast: 00-00-00-00-00-00 through FF-FF-FF-FF-FF-FF Multicast: 01-80-C2-xx-xx-xy Remote MEP ID The MEP ID of another MEP in the same MA to which to send the loopback 18191
Note: This parameter appears in the menu only if Destination Type is Remote MEP ID.
Remote MEP Address The MAC address corresponding to the remote MEP ID.
Note: This parameter is read-only and appears in the menu only if Destination Type is Remote MEP ID. It is automatically updated by the system when you enter a valid remote MEP ID.
Number of LBs to Send The number of loopbacks to send 050 Default: 0
5-30
Testing the Unit
IPmux-24 Ver. 3.5
IPmux-24 Main Menu > Diagnostics > OAM Test (802.1ag) > Loopback > Results Destination Address Messages Sent Replies In-Order Replies Out-of-Order Messages Lost/Timed out Messages Lost/Timed out % > ESC-prev. menu; !-main menu; &-exit ... ... ... ... ... ... (00-11-B3-55-A6-77) (14) (14) (0) (0) (0) 1 M/2 C
Figure 5-25. OAM Loopback Results Menu Table 5-11. OAM Loopback Result Parameters
Parameter Destination Address Messages Sent Description The target MAC address of the loopback message Number of loopback messages that were sent 050 Possible Values
Note: This parameter appears only if the destination address is unicast.

Replies In-Order The number of replies to loopback that were received in order 050

Replies Out-ofOrder The number of replies to loopback that were received out of order. 050

Messages Lost/Timed out The number of loopback messages that were lost or timed out, calculated by the total number of loopback messages sent minus the number of successful and unsuccessful replies received 050

Messages Lost/Timed out % The percentage of loopback messages that were lost or timed out 04,294,967,295
Performing OAM Link Trace

This diagnostic utility traces the OAM route to the destination, specified either by the MAC address or the maintenance end point (MEP).
Note
The option to specify the destination MEP ID is available only if IPmux-24 can resolve at least one remote MEP MAC address.
IPmux-24 Ver. 3.5
Testing the Unit
5-31
To trace OAM route: 1. Navigate to the OAM Tests Link Trace menu (Diagnostics > OAM Tests (802.1ag)> Link Trace). The OAM Tests Link Trace menu appears (see Figure 5-26). 2. Define the test parameters according to Table 5-12. 3. Select Send Link Trace to perform the link trace. 4. Select Results to view the results of the link trace, as illustrated in Figure 5-27. The result parameters are described in Table 5-13. Main Menu > Diagnostics > OAM Tests (802.1ag)> Link Trace 1. 2. 3. 4. 5. MD ID MA ID MEP ID[1 - 8191] Destination Type Target MEP ID Target MEP Address 6. TTL[1 - 64] 7. Send Link Trace 8. Results Please select item <1 to 9> ESC-prev. menu; !-main menu; &-exit ... (1) ... (1) ... (1) (Target MEP ID) ... (150) ... (00-20-D2-C3-C3-C3) ... (64) >
1 M/2 C
Figure 5-26. OAM Link Trace Menu Table 5-12. OAM Link Trace Parameters
Parameter MD ID MA ID MEP ID Destination Type Description Specifies the maintenance domain ID Specifies the maintenance association ID Specifies the MEP ID The destination type for the link trace Possible Values 116 116 18191 Target MAC Address A link is traced to a MAC address Target MEP ID A link is traced to a MEP ID Default: Target MEP ID Target MEP ID The MEP ID of another MEP in the same MA to which to send the link trace message 18191
Note: This parameter appears in the menu only if Destination Type is Target MEP ID.
Target MEP Address The MAC address corresponding to the target MEP ID.
Note: This parameter is read-only. It is automatically updated by the system when you enter a valid target MEP ID.
5-32
Testing the Unit
IPmux-24 Ver. 3.5
Installation and Operation Manual Parameter Target MAC Address TTL Description The MAC address of the link trace destination
Chapter 5 Monitoring and Diagnostics Possible Values 00-00-00-00-00-00 through FF-FF-FF-FF-FF-FF 164
The number of hops. Each unit in the link trace decrements the TTL until it reaches 0, which terminates the link trace.
Main Menu > Diagnostics > OAM Tests > Link Trace (802.1ag)> Results Hop 1 MAC Address 00-20-D2-C3-C3-C3 ING/EGR Action IngOK Port ID ETH1 Relay Action RlyHit 1 M/2 C
ESC-prev. menu; !-main menu; &-exit
Figure 5-27. Link Trace Results Table 5-13. Link Trace Result Parameters
Parameter Hop MAC Address Description The hop number on the way to the target, calculated by the sent TTL value minus the received TTL value The MAC address of the entity that sent the LTR Possible Values 164 00-00-00-00-00-00 through FF-FF-FF-FF-FF-FF IngOK, IngDown, IngBlocked, IngVID; EgrOK, EgrDown, EgrBlocked, EgrVID Port ID Relay Action Port that was used for hop The relay action RlyHit, RlyFDB, RlyMPDB
ING/EGR Action
Ingress or egress action that was taken in hop
Setting a Permanently Active Bundle

If there is a need to run a diagnostic test on a bundle configured as a member of a bundle protection mechanism, you can configure it as a permanently active. This prevents the pseudowire traffic from switching to another bundle even after conditions causing bundle failure have been cleared. The force mode is available for the 1:1 redundancy only. In the non-revertive recovery mode the forced bundle remains to be active even if the second bundle becomes available and the force mode is disabled. To set a permanently active bundle: 1. From the Bundle Protection Switching menu (Diagnostics > Bundle Protection Switching), enter f or b to display a bundle. 2. Select Force to configure selected bundle as permanently active.
IPmux-24 Ver. 3.5 Testing the Unit 5-33
Diagnostics> Bundle protection switching 1. Force > Please select item <1 to 1> F-forward; B-backward ESC-prev.menu; !-main menu; &-exit (Disable)
1 M/ 1 C
Figure 5-28. Bundle Protection Switching Menu
5.6
Frequently Asked Questions
Q: How does the IPmux handle/propagate alarms on the TDM and Ethernet side? A: The IPmux handles alarms on the TDM and Ethernet side in the following manner: TDM side alarms Unframed mode: In case of LOS (Loss Of Signal) on the local IPmux side, AIS will be sent towards the IP side, and will then be transferred over the E1/T1 to the remote TDM device. All other alarms sent from the near-end TDM device (including information on timeslot 0), will be propagated transparently by the local IPmux, to the remote end TDM device (over the IP connection). Framed mode: In case of LOS/LOF/AIS detected on the local IPmux side, a user-configurable conditioning pattern (00 to FF) will be sent on the relevant timeslots (over the IP connection), to the far-end TDM device. A user-configurable conditioning pattern can also be applied on the ABCD bits (CAS signaling 1 to F) going towards the remote PBX. The frame synch on the E1/T1 level is maintained in favor of the end TDM devices. Ethernet Side Alarms Unframed mode: In case of local failure on the IPmux, or a situation of jitter buffer underflow/overflow, an (unframed) AIS will be sent towards the near-end TDM side Framed mode: In case of local failure on the IPmux, or situation of jitter buffer underflow/overflow, a conditioning pattern (00 to FF) will be sent towards the near-end TDM device on the timeslots related to that specific bundle. A userconfigurable conditioning pattern can also be applied on the ABCD bits (CAS signaling 1 to F), going towards the local TDM device. In this case the synch on the E1/T1 level is maintained in favor of the TDM end devices.
5-34
IPmux-24 Ver. 3.5
Q: How can I ensure the IPmux TDMoIP traffic priority over an IP Ethernet network? A: The IPmux units offer three different methods of the TDMoIP traffic prioritization over an IP/Ethernet network: VLAN ID (Layer 2) ToS field (Layer 3) UDP destination port (Layer 4). Each QoS feature is based on a different OSI level and can be used individually in order to ensure the TDMoIP traffic priority. When determining which feature to use, it is important to verify that the different elements on the network, (switches / routers / etc.), support the selected priority mechanism and are also configured to give the highest priority to the labeled IPmux traffic. Notice that the priority is given to the TDMoIP traffic by the network elements and the IPmux is merely tagging the packets. VLAN ID The IPmux complies with the IEEE 802.1p&Q standards. This enables the user to set both VLAN ID and VLAN Priority. It adds four bytes to the MAC layer (Layer 2) of the Ethernet frame. These bytes contain information about the VLAN ID, and the VLAN priority, which runs from 07. The IPmux only tags the packets, while the switches are responsible for giving the priority according to the VLAN info. Verify that the IPmux traffic has the highest priority in the relevant Ethernet network. ToS There are several RFCs (RFC791, RFC1349, RFC2474) that define how the IP ToS should be configured. The ToS is a byte located in the IP header (Layer 3). In general the Type of Service octet, in most cases, consists of three fields: The first field, labeled "PRECEDENCE", is intended to denote the importance or priority of the datagram. The second field, labeled "TOS", denotes how the network should make tradeoffs between throughput, delay, reliability, and cost. The last field, labeled "MBZ" (for "must be zero") above, is currently unused. The IPmux can configure the whole IP ToS byte, and therefore it is adaptable to each RFC in the market. The IP ToS parameter in the IPmux is userconfigured in terms of decimal value. However, on the frame itself it of course appears in binary format. The decimal value varies between 0 and 255 (8 bits). A configuration example: Setting IP precedence of 101 and IP ToS of 1000 will give us the byte 10110000, which means that the IPmux IP ToS parameter should be configured to 176 decimals.
IPmux-24 Ver. 3.5
5-35
UDP Destination Port The IPmux uses the UDP protocol (Layer 4) in order to transfer the TDMoIP traffic. In the UDP protocol, the Destination port field is always set to the decimal value of 2142, hence all the packets leaving the IPmux are tagged accordingly. This unique value was assigned to RAD by the IANA organization for TDMoIP applications. The network elements may be used to give priority to the TDMoIP traffic according to the UDP destination field. Q: Does allocating a sufficient bandwidth ensure the proper functionality of an IPmux-based application? A: A sufficient bandwidth is not enough to ensure a steady environment for the IPmux, since networks loaded with additional non-IPmux LAN traffic (e.g. PC traffic) or incompetent PSN may cause several problems: Jitter The IPmux packets may suffer a delay variation (although all the traffic will eventually pass through due to that fact that there is sufficient bandwidth). Packets will be delayed for different periods of time due to overloaded networks, queuing mechanisms, etc. IPmux can compensate for some jitter, but bigger jitter causes problems. Misordering Packets might be sent in different order than the order in which they were originally sent from the IPmux. Packet Loss Packets might be dropped/ignored by some elements in the network (routers/switches) due to insufficient processing power to handle the load, queuing mechanisms, buffer overflows, etc. Normally these problems are solved by giving priority to the IPmux traffic over all other traffic. As can be shown, even though there is sufficient bandwidth, there might still be cases in which the traffic will be transmitted from all the sources at the same time and thus create a momentary load on the network element (router/switch), even when this load that does not exceed the available bandwidth. Since the IPmux is constantly transmitting, the TDMoIP traffic will always be a part of such a load. When no priority is given to the PW traffic, the network elements will handle the PW traffic as any other type of traffic. All the above degrade the performance of the IPmux unit, although an adequate amount of bandwidth is provided for the IPmux.
5.7
Technical Support
Technical support for this product can be obtained from the local distributor from whom it was purchased. For further information, please contact the RAD distributor nearest you or one of RAD's offices worldwide. This information can be found at www.rad.com (offices About RAD > Worldwide Offices; distributors Where to Buy > End Users).
5-36
Technical Support
IPmux-24 Ver. 3.5
Chapter 6 Software Upgrade

This chapter explains how to upgrade IPmux-24 to version 3.5. Software upgrade is required to fix product limitations, enable new features, or to make the unit compatible with other devices that are already running the new software version. The information includes the following: Detailed conditions required for the upgrade Any impact the upgrade may have on the system Overview of downloading options Upgrade via the File Utilities menu Upgrade via the Boot menu.
6.1
Compatibility Requirements
Following are the software releases that can be upgraded to version 3.5. The hardware revisions that can accept the software version 3.5 are also listed. Software 1.0 and above Hardware 1.0 and above.
6.2
Impact
IPmux-24 resets automatically after the software upgrade, resulting in up to two minutes of downtime. Upgrade to version 3.5 does not affect any user settings.
6.3
Software Upgrade Options
Application software can be downloaded to IPmux-24 via the S/W & File Transfer using TFTP menu (Utilities > File Utilities > Download/upload using TFTP), using the TFTP, or via the Boot menu, using XMODEM or TFTP.
IPmux-24 Ver. 3.5
Software Upgrade Options
6-1
6.4
Prerequisites
This section details the IPmux-24 software and versions compatible with version 3.5. It also lists the software file names and outlines system requirements needed for the upgrade procedure.
Software Files
Version 3.5 releases are distributed as software files named IPMUX.img. The files can be obtained from the local RAD business partner from whom the device was purchased.
System Requirements
Before starting the upgrade, verify that you have the following: For upgrade via TFTP: Operational IPmux-24 unit with valid IP parameters configured for the host Connection to a PC with a TFTP server application (such as 3Cdaemon or PumpKIN), and a valid IP address Software file (IPMUX.img) stored on the PC For upgrade via XMODEM: Operational IPmux-24 unit Connection to a PC with a terminal emulation application (such as HyperTerminal) Software file (IPMUX.img) stored on the PC.
6.5
Upgrading Software via the File Utilities Menu
The recommended software downloading method is downloading by means of the TFTP, using the Download/upload using TFTP menu reached from the File Utilities menu. Network administrators can use this procedure to distribute new software releases to all the managed IPmux-24 units in the network from a central location.
Figure 6-1. Downloading a Software Application File to IPmux-24 via TFTP
6-2
IPmux-24 Ver. 3.5
Use the following procedure to download software release 3.5 to IPmux-24 via the File Utilities menu. 1. Verify that the IPMUX.img is stored on the PC with the TFTP server application. 2. Verify that the IPmux-24 host has valid IP parameters. 3. Ping the PC to verify the connection. 4. Activate the TFTP server application. 5. Download the IPMUX.img from the PC to IPmux-24.
Note
Configuration values shown in this chapter are examples only.
Verifying the Host Parameters

The IPmux-24 host must have host IP parameters configured according to your network requirements. Otherwise you will not be able to establish a proper communication session with the TFTP server. Refer to the following manual section for additional information:
Connecting to the ASCII Terminal in Chapter 2 Working with Terminal in Chapter 3 Configuring IP Host Parameters and Configuring the Host Encapsulation in
Chapter 4.
To verify the IPmux-24 host parameters: 1. Display the Host IP menu (Configuration > System > Management > Host IP), and verify that the host IP address, IP mask are configured according to your network requirements. Configuration>System>Management>Host IP 1. 2. 3. 4. 5. 6. 7. 8. > Please select item <1 to 8> ESC-prev.menu; !-main menu; &-exit 1 M/ 1 C IP address IP mask DHCP DHCP Status Read Community Write Community Trap Community Encapsulation ... (192.168.10.2) ... (255.255.255.0) (Disable) > ... (public) ... (private) ... (SNMP_trap) >
Figure 6-2. Configuring the Host

2. Display the Encapsulation menu (Configuration > System > Management > Host IP > Encapsulation), and verify that the host encapsulation parameters are configured according to your network requirements.
IPmux-24 Ver. 3.5
6-3
Configuration>System>Management>Host>Encapsulation 1. Host Tagging 2. Host VLAN ID [1 - 4094] 3. Host VLAN Priority [0 - 7] > ESC-prev.menu; !-main menu; &-exit 1 M/ 1 C (Tagged) ... (300) ... (7)
Figure 6-3. Verifying Host Encapsulation Settings
Pinging the PC
Check the integrity of the communication link between IPmux-24 and the PC by sending a ping from the unit to the PC. To ping the PC: 1. From the Ping menu (Diagnostics > Ping) menu, select an interface to specify direction (switch port), to which the ping is sent.
Note
PW host can be selected only if it was previously configured.

2. Enter the PC IP address as the destination IP address of the ping.
Note
If the destination IP is in a different subnet, configure the host default gateway.

3. Enable or disable VLAN tagging according to your network requirements. 4. Select Ping Send to start sending pings. A reply from the PC indicates a proper communication link 5. If the ping request is timed out, check the link between IPmux-24 and the PC (physical path, configuration parameters etc).
Diagnostics>Ping 1. Interface 2. Destination IP address 3. VLAN tagging 4. Number of frames to send[1 - 4] 5. Ping Send > Please select item <1 to 5> ESC-prev.menu; !-main menu; &-exit (PW Host IP) ... (192.168.10.20) (Disable) ... (1)
1 M/ 1 C
Figure 6-4. Pinging the PC
6-4
IPmux-24 Ver. 3.5
Activating the TFTP Server

Once the TFTP server is activated on the PC, it waits for any TFTP file transfer request originating from the product, and carries out the received request automatically. Transferring Software and Configuration Files section in Chapter 4 explains how to prepare your PC for the TFTP file transfer. To run the TFTP server: Activate a TFTP server application, such as 3Cdaemon (available from www.3com.com) or PumpKIN (available from http://kin.klever.net/pumpkin/).
Downloading the New Software Release File to the Unit

This procedure is used to replace the current software version with the new software release (IPMUX.img). To download the new software release file: 1. From the Download/upload using TFTP menu (Utilities > File Utilities > Download/upload using TFTP), enter the following: File name IPMUX.img Command Software Download and Reset Server IP IP address of the PC. 2. Save the changes to initiate the download. The software download begins. When the process is completed, new software release (IPMUX.img) replaces the current software version and becomes active. IPmux-24 resets automatically. Utilities>File Utilities>Download/upload using TFTP 1. 2. 3. 4. 5. 6. File name Command Server IP Retry timeout(sec)[0 - 1000] Total timeout(sec)[0 - 1000] View transfer status ... > ... ... ... > (IPMUX.img) (Software download and reset) (192.168.10.20) (1) (5)
1 M/ 1 C
Figure 6-5. Transferring New Software Release Using TFTP
6.6
Upgrading Software via the Boot Menu
Software downloading may also be performed using the Boot menu. The Boot menu can be reached while IPmux-24 performs initialization, for example, after power-up.
IPmux-24 Ver. 3.5
6-5
You may need to start the loading from the Boot menu when it is not possible to activate TFTP from the Download/upload using TFTP menu (for example, because the IPmux-24 software has not yet been downloaded or is corrupted).
Caution The Boot menu procedures are recommended only for use by authorized
personnel, because this menu provides many additional options that are intended for use only by technical support personnel. Two software downloading options are available from the Boot menu: Downloading using the XMODEM protocol. This is usually performed by downloading from a PC directly connected to the CONTROL port of the unit.
Figure 6-6. Downloading a Software Application File to IPmux-24 via XMODEM

Downloading using the TFTP. This is usually performed by downloading from a remote location that provides an IP communication path to an Ethernet port of IPmux-24.
Using the XMODEM Protocol

Use the following procedure to download software release 3.5 to IPmux-24 via XMODEM. 1. Verify that the IPMUX.img is stored on the PC with the terminal application. 2. Configure the communication parameters of the selected PC serial port for asynchronous communication for 115.2 kbps, no parity, one start bit, eight data bits and one stop bit. Turn all types of flow control off. 3. Turn off IPmux-24. 4. Activate the terminal application. 5. Turn on IPmux-24 and immediately start pressing the <Enter> key several times in sequence until you see the Boot screen. A typical screen is shown below (the exact version and date displayed by your IPmux-24 may be different).
Note
If you miss the timing, IPmux-24 performs a regular reboot process (this process starts with Loading and ends with a message to press <Enter> a few times to display the log in screen).
6-6
IPmux-24 Ver. 3.5
Boot version 1.60 (Mar 6 2006) Boot manager version 7.04 (Mar 6 2006) 0 - Exit Boot-Manager 1 - Dir 2 - Set active software copy 3 - Delete software copy 4 - Download an application by XMODEM 5 - Format Flash 6 - Show basic hardware information 7 - Reset board 8 - System configuration. 9 - Download an application by TFTP Press the ESC key to go back to the main menu. Select:
Figure 6-7. Boot Menu

To download software release via XMODEM: 1. From the Boot menu, select Download an Application by XMODEM. The program requests to specify which software file to be downloaded. Choose the software you want to work on 0 - boot-manager 1 - application file 1. Select application file. A message is displayed that requests the partition number to which the new software is to be downloaded, and offers a recommended value. 2. If there is no special reason to select a different value, type the recommended number and then press <Enter>. A typical display is shown below: Select Copy number for download ( 1 ) Select: 1 3. The process starts. The following message is displayed: Erasing Partition please wait .... Please start the XMODEM download. 4. Start the transfer in accordance with the program you are using. For example, if you are using the Windows HyperTerminal utility: Select Transfer in the HyperTerminal menu bar, and then select Send File on the Transfer menu. The Send File window is displayed: Select the prescribed IPmux-24 software file name (you may use the Browse function to find it). In the Protocol field, select Xmodem.
IPmux-24 Ver. 3.5
6-7
When ready, press Send in the Send File window. You can now monitor the progress of the downloading in the Send File window.
Note
If downloading fails, repeat the whole procedure.

5. When the downloading process is successfully completed, you will see a sequence of messages similar to the following:
Loading ... Decompressing to RAM. Processing archive: FLASH Extracting IPMUX.BIN .......................................................... .................................................................... CRC OK Running ... ******************************************************************* * In order to start working - press the ENTER button for few times* *******************************************************************
6. At this stage, press the <Enter> key several times to go to the log in screen.
Using the TFTP

Use the following procedure to download software release 3.5 to IPmux-24 via TFTP. 1. Verify that the IPMUX.img is stored on the PC with the TFTP server application. 2. Define IP parameters via the Boot Manager menu. 3. Activate the TFTP server application. 4. Download the IPMUX.img from the PC to IPmux-24. To define IP parameters via the Boot Manager menu: 1. From the Boot menu (Figure 6-7), select System Configuration to start the configuration of the IPmux-24 IP communication parameters, as needed for TFTP transfer. The parameters are displayed in consecutive lines. For each parameter, you can accept the current values by simply pressing <Enter> to continue, or type a new value: IP Address: used to select the IP address of IPmux-24. To change the current value, type the desired IP address in the dotted quad format, and then <Enter> to continue. IP Mask: used to select the IP subnet mask of IPmux-24. To change the current value, type the IP subnet mask address in the dotted quad format, and then <Enter> to continue.
6-8
IPmux-24 Ver. 3.5
Default Gateway Address: when the TFTP server is located on a different LAN, you must define the IP address of the default gateway to be used by IPmux-24. Make sure to select an IP address within the subnet of the assigned IPmux-24 IP address. To change the current value, type the desired IP address in the dotted quad format, and then <Enter> to end the configuration. If no default gateway is needed, for example, because the TFTP server is attached to the same LAN as IPmux-24 being loaded, enter 0.0.0.0. 2. Press <Enter> to display the Boot menu. 3. Select Perform Reset to the board to reset IPmux-24. The new parameters take effect only after the resetting is completed. To download software from the Boot menu using TFTP: 1. From the Boot menu, select Download an Application by TFTP and then press <Enter> to start the TFTP transfer. Please Enter the Target File Name message is displayed. 2. Enter the name of the desired software distribution file (make sure to include the path, when necessary). When done, press <Enter> to continue. Please Enter the Server IP address message is displayed. 3. Enter the IP address of the server on which the software distribution file resides and then <Enter> to continue. If no errors are detected, the downloading process starts, and the screen displays its relative progress. 4. After the transfer is successfully completed, return to the Boot menu and select Exit Boot-Manager. When the IPmux-24 initialization is ended, the unit loads the new software.
Note
If downloading failed, repeat the whole procedure.
IPmux-24 Ver. 3.5
6-9
6-10
IPmux-24 Ver. 3.5
Chapter 7 Application Tutorial

This chapter describes how to build two typical applications using IPmux-24: CESoPSN Generic pseudowire application with ring protection.
7.1

CESoPSN Application
In this section you will learn how to: Create a CESoPSN pseudowire connection Verify the pseudowire connection Check that the traffic runs error-free over the pseudowire connection.
Figure 7-1 illustrates a typical CESoPSN pseudowire application.
Figure 7-1. CESoPSN Application
Equipment List
The following is a list of equipment required for setting up a typical CESoPSN application:
IPmux-24 Ver. 3.5
IPmux-24 Gmux-2000 system with GbE and E1-PW/28 modules PATCH-28B patch panel DXC-4 (functioning as an E1 generator) PC running Windows XP CBL-G703-14-PATCH cable Two straight Ethernet cables with RJ-45 connectors One cross Ethernet cable with RJ-45 connectors
CESoPSN Application 7-1
One cross E1 cable with RJ-45 connectors RJ-45 loopback plug.
Installing the Units

Before starting configuration, install units as follows: 1. Connect the GE 1 port of the GbE module to the NET 1 port of IPmux-24 using a straight Ethernet cable.
Note
The SFP-9G transceiver is installed in the GE 1 port of the GbE module.

ACT LINK
GE 1
LINK TX
PAUSE RX
GE 2
LINK TX
PAUSE RX
GbE
MONITOR
GbE
Straight Ethernet Cable
CONTROL
NET 1
NET/USER 2
USER 3
E1/T1 1 2 3 4
DCE
10/100BASE-T
SYNC
SYNC
SYNC
SYNC
IPmux-24
Figure 7-2. Connecting Gmux-2000 to IPmux-24

2. Connect the PC to the USER 3 port of IPmux-24 using a cross Ethernet cable.
NET 1 NET/USER 2 USER 3 E1/T1 1 2 3 4
CONTROL
DCE
10/100BASE-T
SYNC
SYNC
SYNC
SYNC
IPmux-24
Cross Ethernet Cable
LAN
PC
Figure 7-3. Connecting the PC to IPmux-24

3. Connect the E1 port 1 of IPmux-24 to the CHANNEL 1 port of DXC-4 using an E1 cross cable with RJ-45 connectors.
7-2
CESoPSN Application
IPmux-24 Ver. 3.5
Figure 7-4. Connecting IPmux-24 to DXC-4

4. Connect the CH 1-14 connector of the E1-PW/28 module to the IO 1 connector of the PATCH-28B patch panel.
1 2 3 4 5 6 7 8 9 11 13 15 17 19 21 23 25 27 10 12 14 16 18 20 22 24 26 28
L R
CH 1-14
CH 15-28
E1.PW/28/BAL
E1-PW/28 CBL-G703-14-PATCH Cable
IO 2
IO 1
PATCH-28B
Figure 7-5. Connecting the E1-PW/28 Module to the PATCH-28B Patch Panel
5. Install the RJ-45 loopback plug in E1 port 1 of the PATCH-28B patch panel to loop the E1 traffic.
Configuring Gmux-2000
The following section explains the main configuration actions for a Gmux-2000 chassis with E1-PW/28 and GbE modules.
Loading Hardware Configuration

When powering on Gmux-2000 for the first time, the first step is to load the hardware configuration, which means to configure Gmux-2000 to recognize the modules installed into the chassis. To load the hardware configuration: 1. From the Database Tools menu (Config > Database tools), select Factory Default. 2. Press Y to confirm. 3. Select Load Hardware. 4. Press Y to confirm. 5. Select Update Database.
IPmux-24 Ver. 3.5 CESoPSN Application 7-3
6. Verify the following message appears at the bottom of the screen: DB UPDATED SUCCESSFULLY. Pseudowire Gateway Config>Database tools 1. Choose DB number[1 - 5] ... (5) 2. Factory default 3. Load database 4. Load hardware 5. Check sanity 6. Update database < ESC-prev.menu; !-main menu; &-exit; @-debug
1 Mngr/s
Figure 7-6. Updating the Database

7. Navigate to the Card Type menu (Configuration > System > Card type), and verify that the E1-PW/28 (slot 1) and the GbE (slot 6) modules were recognized by the device. Pseudowire Gateway Configuration>System>Card type SLOT: DB : SLOT: DB : SLOT: DB : PS-1 PS-AC IO/1 CES-E1-PW IO/6 GbE PS-2 PS-AC IO/2 ----------IO/7 ----------PS-3 PS-AC IO/3 ----------IO/8 ----------CL-1 CL IO/4 ----------IO/9 ----------CL-2 CL IO/5 -----------
1. -----------2. PS-AC 3. PS-DC < ESC-prev.menu; !-main menu; &-exit; @-debug
1 Mngr/s
Figure 7-7. Verifying the Module Recognition
Configuring the Host IP Parameters

Configure the Gmux-2000 IP addresses which will be used for the bundle connectivity and management. To configure the host IP parameters: 1. From the Host IP menu (Configuration > System > Host IP), set the host IP parameters as follows: IP address 192.168.100.100 IP mask 255.255.255.0 Default gateway 192.168.100.1
7-4
CESoPSN Application
IPmux-24 Ver. 3.5
Pseudowire Gateway Configuration>System>Host IP INTERFACE ONLINE CL: GbE 1/IF 1: GbE 1/IF 2: IP ADDRESS 0.0.0.0 192.168.100.100 0.0.0.0 IP MASK 0.0.0.0 255.255.255.0 0.0.0.0 DEFAULT GATEWAY 0.0.0.0 192.168.100.1 0.0.0.0
Figure 7-8. Configuring the Host IP Parameters

2. Press S to save. The following message is displayed: DB WAS CHANGED. PERFORM UPD DB TO SAVE CHANGES IN ONLINE FILE. 3. Ignore the message. The online file will be updated at the end of the configuration process.
Configuring the Manager List

To enable Gmux-2000 management via a remote management station, the NMS IP address must be added to the manager list. To configure the manager list: 1. From the Manager List menu (Configuration > System > Management > Manager list), press A to add a new NMS. 2. Configure the following: IP address 192.168.100.200 Interface GIG A-IO 6/1 (slot 6, port 1) Pseudowire Gateway Configuration>System>Management>Manager list MNG NUM[1 - 100] IP ADDRESS NEXT HOP INTERFACE TRAP(FOR MANAGER) VLAN VALID VLAN ID[0 - 4095] VLAN PRIORITY[0 - 7] ... ... ... > (1) (192.168.100.200) (0.0.0.0) (GIG A-IO 6/1) (No) (No) ... (0) ... (0)
1. 2. 3. 4. 5.
Figure 7-9. Configuring the Manager List
Verifying the Master Clock Source

Gmux-2000 has to be configured to provide the clock for the entire application. To ensure that all of its ports are set for the same clock, the system clock must be used. To verify the master clock source: Navigate to the Master Clock menu (Config > System > Clock source > System A > Master clock), and verify that the master clock source is set to Internal.
IPmux-24 Ver. 3.5
CESoPSN Application
7-5
Pseudowire Gateway Configuration>System>Clock source>System A>Master clock 1. Master clock source 2. Save parameters > (Internal)
Figure 7-10. Verifying the Master Clock Source
Enabling the GbE Module

By default the GbE interfaces are disabled. Port 1 of the GbE module in slot 6 must be enabled. To enable port 1 of the GbE module: 1. From the Physical Layer menu (Configuration > Physical layer), select IO and choose the GbE module slot (6). Pseudowire Gateway Configuration>Physical layer 1. IO[1 - 9] ... (6) 2. E1 port > 3. First GbE IF ... (0/0) 4. Second GbE IF ... (0/0) 5. Delete all slot's bundles 6. Disconnect all slot's bundles 7. Save slot parameters > F - next; B - prev; S Save ESC-prev.menu; !-main menu; &-exit; @-debug
Figure 7-11. Selecting I/O Slot 6

2. Select GbE Port. Pseudowire Gateway Configuration>Physical layer 1. 2. 3. 4. 5. IO[1 - 9] Arp refresh L4 pools configuration GbE port Monitor port ... (6) > (No Arp Refresh) > > >
> F - next; B - prev; ESC-prev.menu; !-main menu; &-exit; @-debug
Figure 7-12. Selecting the GbE Port

3. Select GbE Port.
7-6 CESoPSN Application IPmux-24 Ver. 3.5
4. Choose Connect State and set it to Connect. Pseudowire Gateway Configuration>Physical layer>GbE port - (IO 6:GBETH PORT 1 CARD TYPE- GbE) 1. 2. 3. 4. > GbE port[1 - 2] Connect state VLAN valid Auto Negotiation ... (1) (Connect) (No) (Enable)
> F - next; B - prev; ESC-prev.menu; !-main menu; &-exit; @-debug
Figure 7-13. Enabling the GbE Port

5. Navigate back to the Physical Layer menu and select First GbE IF to configure port 1 of the GbE module in slot 6 for PW traffic. Pseudowire Gateway Configuration>Physical layer 1. IO[1 - 9] ... (6) 2. E1 port > 3. First GbE IF ... (6/1) 4. Second GbE IF ... (0/0) 5. Delete all slot's bundles 6. Disconnect all slot's bundles 7. Save slot parameters > F - next; B - prev; S Save ESC-prev.menu; !-main menu; &-exit; @-debug
Figure 7-14. Selecting a GbE Interface for PW Traffic
Configuring the E1 Interface

The E1 interface must be configured at the physical layer to conform to the application requirements. To configure the E1 interface at the physical layer: 1. From the Physical Layer menu (Configuration > Physical layer), select E1 Port. 2. From the E1 Port menu, configure the following: Transmit clock source System A Line type Framed G.704.
IPmux-24 Ver. 3.5
CESoPSN Application
7-7
Pseudowire Gateway Configuration>Physical layer>E1 port - (IO 1:E1 PORT 1 CARD TYPE- CES-E1-PW Interface Type > (Balanced) (1) (Connected) (7E) (FF) (System A) (Short Haul) (Framed G.704) (CCITT)
1. Channel ID[1 - 28] ... 2. Admin Status 3. Idle code[0 - ff] ... 4. OOS code[0 - ff] ... 5. Transmit clk source > 6. RX Sensitivity > 7. Assign entire port to bundle > 8. Line type > 9. Restoration Time > > ESC-prev.menu; !-main menu; &-exit; @-debug
Figure 7-15. Configuring E1 at the Physical Layer (Gmux-2000)
Adding and Connecting a Bundle

In order to establish the CES connectivity between the Gmux-2000 and IPmux-24 it is necessary to add a bundle (PW connection) and connect it to a destination device. To add a bundle: 1. From the Connection menu (Configuration > Connection), press X to add a new bundle. Pseudowire Gateway Configuration>Connection - (BUNDLE 0) 1. Bundle ID[1 - 2000] ... (0)
> F - next; B - prev; X - add bundle ESC-prev.menu; !-main menu; &-exit; @-debug
Figure 7-16. Adding a New Bundle

2. Once the bundle is added, select Connection Mode, and change it to CES. 3. Save the changes. To connect the bundle: 1. From the Connection Configuration screen (Configuration > Connection > Connection configuration - (BUNDLE 1)), configure the following: Connection state Enable Source CBID 1
7-8
CESoPSN Application
IPmux-24 Ver. 3.5
Destination CBID 1 Payload format V2 TDM frame in packet 5 Jitter buffer 3 msec OAM connectivity Enable OOS L bit mode TX OOS and L bit Destination IP 192.168.100.101 Network slot port 6/1 2. Save the changes. Pseudowire Gateway Configuration>Connection>Connection configuration Connection state Source CBID Dest CBID Payload format TDM frame in frame Jitter buffer in Ms[0-200] Sensitivity OAM connectivity OAM indication Payload type Far end type OOS L bit mode Destination IP Network slot port Next hop IP TOS Adaptive clock VLAN tagging Enable 1 1 V2 5 3.00 Sensitive to data Enable Source port number Data E1 TX OOS and L bit <192.168.100.101> 6/1 <0.0.0.0> 0 Disable Disable (BUNDLE 1)
| v
^ | | v ^ |
Figure 7-17. Connecting the Bundle
Assigning Timeslots to the Bundle

Now the E1 timeslots must be assigned to the newly-created bundle. To assign E1 timeslots to the bundle: 1. From the TS Assignment menu (Configuration > TS Assignment), select TS Assignment. The TS Assignment menu is displayed (Figure 7-18). 2. From the TS Assignment menu, assign timeslots 110 to bundle 1. 3. Save the changes. 4. Update the database.
IPmux-24 Ver. 3.5
CESoPSN Application
7-9
Pseudowire Gateway Config>TS Assignment>TS assignment - (IO 1:T1 PORT 1 CARD TYPE- CES-E1-PW) TIME SLOT NUM : TS 1 TS 2 Bundle number: 1 1 TS type: Full Full ->> 1. Change cell [1 - 2000] > TS 3 TS 4 TS 5 TS 6 TS 7 TS 8 TS 9 TS 10 1 1 1 1 1 1 1 1 Full Full Full Full Full Full Full Full ... (0)
Please select item <1 to 1> ESC-prev.menu; !-main menu; &-exit; @-debug; ?-help; S-save
Figure 7-18. Assigning Timeslots 110 to Bundle 1
Configuring IPmux-24
The following section explains the main configuration actions for IPmux-24.
Resetting IPmux-24 to its Defaults

To start configuration from the scratch, you must reset IPmux-24 to its defaults. To reset IPmux-24 to its defaults: 1. From the Factory Default menu (Configuration>System>Factory default), select Full. 2. Press Y to confirm the reset. 3. Wait for the device to reload. Configuration>System>Factory default 1. Full 2. Except management Please select item <1 to 2> ESC-prev.menu; !-main menu; &-exit
1 M/ 1 C
Figure 7-19. Resetting IPmux-24 to its Defaults
Configuring the Host IP Parameters

To establish a proper connection between IPmux-24 and an NMS, you must configure its host IP address. This IP is also used as a destination for the incoming pseudowire traffic. To configure the host IP parameters: 1. From the Host IP menu (Configuration > System > Management > Host IP), select DHCP and set to Disable. 2. Save the changes. 3. Configure the following: IP address 192.168.100.101 IP mask 255.255.255.0 4. Save the changes.
Configuration>System> Management>Host IP 1. IP address 2. IP mask 3. DHCP 4. Read Community 5. Write Community 6. Trap Community > Please select item <1 to 6> S - save ESC-prev.menu; !-main menu; &-exit ... (192.168.100.101) ... (255.255.255.0) (Disable) ... (public) ... (private) ... (SNMP_trap)
1 M/ 1 C
Figure 7-20. Configuring Host IP Parameters
Configuring the Manager List

The NMS must be added to the manager list of the unit. To configure the manager list: 1. From the Management List menu (Configuration > System > Management > Manager List), type a to add a management station. The Management List menu display changes, entering the Add mode. 2. When in Add mode, set IP address of the management station to 192.168.10.200. Set IP mask of the management station to 255.255.255.0. 3. Save the changes. Configuration>System>Management>Manager List Manager ID (1) 1. IP Address ... (192.168.10.200) 2. Trap Mask ... (Disable) > ESC-prev.menu; !-main menu; &-exit
1 M/ 1 C
Figure 7-21. Adding a Network Manager
Configuring the E1 Interface

The E1 interface must be configured at the physical layer to conform to the application requirements. To configure the E1 interface at the physical layer: 1. From the Physical Layer menu (Configuration > Physical layer), select TDM (E1). 2. From the TDM (E1) menu, configure the following: Transmit clock source Adaptive Line type Framed G.704.
IPmux-24 Ver. 3.5
CESoPSN Application
7-11
Configuration>Physical layer> TDM (E1) Channel ID Restoration Time Signaling Mode (1) (CCITT) (CAS Disabled)
>
1. Administrative Status (Up) 2. Transmit Clock Source > (Adaptive) 3. Source Clock Quality > (other/unknown) 4. Trail Mode (Termination) 5. Line Type > (Framed G.704) 6. Line Interface (DSU) 7. Idle Code ... (7E) 8. Send Upon Fail (OOS code) 9. OOS Code ... (FF) 10. Ethernet Network Type > (Wan) > ESC-prev.menu; !-main menu; &-exit; @-debug
1 M/ 1 C
Figure 7-22. Configuring E1 at the Physical Layer (IPmux-24)
Assigning Timeslots to the Bundle

You must select the pseudowire bundle type (CESoPSN) and assign timeslots to it. To select the pseudowire bundle type: From the Connection menu (Configuration > Connection), set the PW type to CESoPSN.
Configuration>Connection 1. 2. 3. 4. 5. 6. 7. 8. > PW host IP Redundant PW host IP Multiplexing Bundle ID[1 - 511] PW type PSN type DS0 bundle Bundle connection > > (Source Port) ... (1) > (CESoPSN) > (UDP/IP) []> >
1 M/ 1 C
Figure 7-23. Selecting the Bundle Type

To assign timeslots to the bundle: 1. Select Bundle ID, and select a bundle to which you intend to assign timeslots. 2. Select DS0 bundle. The DS0 Bundle menu appears (see Figure 7-24).
Configuration>Connection>DS0 bundle TDM Channel ID: 1 Bundle ID: 1 +1 +2 +3 +4 TS 0 1 0 0 0 1 0 0 1 0 0 1 0 0 TS 10 TS 20 TS 30
+5 1 0 0
+6 1 0 0
+7 1 0 0
+8 1 0 0
+9 1 0 0
+10 1 0 0
1. Change cell [0 - 1] >
... (0)
Please select item <1 to 1> E Enable all; L Disable all ESC-prev.menu; !-main menu; &-exit; ?-help
1 M/ 1 C
Figure 7-24. Assigning Timeslots to the Bundle

3. From the DS0 Bundle, assign timeslots 1 to 10 to the current bundle by selecting a timeslot and choosing 1 (active) or 0 (free).
Connecting the Bundle

You must configure bundle connection parameters to connect the IPmux-24 bundle to the previously configured bundle on Gmux-2000. To connect the IPmux-24 bundle: 1. From the Bundle Connection menu (Configuration > Connection > Bundle Connection), configure the following: Destination IP address 192.168.100.100 Connection status Enable Destination bundle 1 TDM Frames In Packet 5 2. Save the changes.
IPmux-24 Ver. 3.5
CESoPSN Application
7-13
Configuration>Connection>Bundle connection TDM channel ID: 1 Bundle ID: 1 1. 2. 3. 4. 5. 6. 7. 8. 9. 11. 12. 13. > Destination IP address Next hop IP TOS[0 - 255] Connection status Destination bundle[1 - 8063] TDM Frames In Packet[1 288] Payload format OAM connectivity Jitter buffer [msec][2.5 - 200] Sensitive OOS mode VLAN tagging ... (192.168.100.100) ... (-) ... (0) (Enable) ... (1) ... (5) (V2) (Disable) ... (3.0) (Data) (Tx OOS) (Disable)
Please select item <1 to 13> F - Forward Bundle ID; D - Delete; ? - Help ESC-prev.menu; !-main menu; &-exit
1 M/ 1 C
Figure 7-25. Connecting Bundle 1 on IPmux-24 to Bundle 1 on Gmux-2000
Verifying the Bundle Connection Status

The bundle 1 connection status must be verified at IPmux-24 and Gmux-2000. To verify the bundle 1 connection status (IPmux-24): 1. Display the Connection screen (Monitoring > Status > Connection). 2. Select Bundle ID to choose bundle 1. 3. Verify that the bundle 1 connectivity status is OK. Monitoring>Status>Connection Destination IP address: Next hop MAC address: Connectivity status: > (192.168.100.100) (00-20-D2-24-05-F) (OK) (0) (0) (0)
Sequence errors: Jitter buffer underflows: Jitter buffer overflows:
1. Bundle ID[1 127 ] ... (1) > C - Clear counters; F - Forward Bundle ID ESC-prev.menu; !-main menu; &-exit
1 M/ 1 C
Figure 7-26. Verifying the Bundle Connection Status (IPmux-24)

To verify the bundle 1 connection status (Gmux-2000): 1. Display the Bundle Counters screen (Monitoring>Status > Connection > Bundle counters).
7-14
CESoPSN Application
IPmux-24 Ver. 3.5
2. Select Bundle ID to choose bundle 1. 3. Verify that the bundle 1 connectivity status is OK. Monitoring>Status>Connection>Bundle counters - (BUNDLE 1 CES) 1. Bundle ID[1 - 2000] ... (1) Destination IP address ... (192.168.100.101) Connectivity Status ... (O.K) Sequence Errors ... (0) Jitter buffer Underflows ... (0) Jitter buffer Overflows ... (0) Min Jitter buffer Level [Msec] ... (0.00) Max Jitter buffer Level [Msec] ... (4.50) Frames TX to PSN ... (2563786) Frames RX from PSN .. (2575187) > Please select item <1 to 1> F - next; B - prev; C - reset counters ESC-prev.menu; !-main menu; &-exit; @-debug
Figure 7-27. Verifying the Bundle Connection Status (Gmux-2000)
Testing the Application

You have to verify that data is running error-free over the pseudowire connection you created. RADs DXC-4 can be used to generate E1 traffic which is going to be carried between IPmux-24 and Gmux-2000. This section describes a RADs proprietary application to generate and forward E1 or T1 traffic via DXC-4. You can use any application with similar functionality for this purpose.
Configuring the E1/T1 Traffic Generator

The E1/T1 traffic generator application is distributed as an executable file (Rldxc4.exe). To configure the E1/T1 traffic generator: 1. Run the Rldxc4.exe file. The E1/T1 Traffic Generator Main screen is displayed. 2. From the Connection menu, select Connect Chassis.
IPmux-24 Ver. 3.5
CESoPSN Application
7-15
Figure 7-28. Adding DXC-4 as Chassis 1 to the E1/T1 Traffic Generator

3. Select Com and Com Number = 2 to define the COM 2 port as a management port for DXC-4. The Chassis 1 item appears under Resources in the left-hand pane of the E1/T1 traffic generator.
Figure 7-29. Defining the DXC-4 Management Method

4. In the left-hand pane, select Chassis 1. 5. In the right-hand pane, select the Ports Setup tab and configure the following: Link Type E1 g732n Source clock lbt1 Port number 1.
7-16
CESoPSN Application
IPmux-24 Ver. 3.5
Figure 7-30. Configuring the DXC-4 E1 Port Parameters

6. In the right-hand pane, select the Bert Setup tab and assign timeslots 110 to E1 stream.
IPmux-24 Ver. 3.5
CESoPSN Application
7-17
Figure 7-31. Assigning Timeslots to E1 Stream

7. Save the changes. 8. In the right-hand pane, select the Bert Statistics tab. 9. Click the button to start the BERT.
10. Verify that the Sync Loss and Error Bits counters remain at 0.
7-18
CESoPSN Application
IPmux-24 Ver. 3.5
Figure 7-32. Displaying the BERT Results

11. Run the BER test for 30 seconds. 12. From Gmux-2000 display the GbE Port Counters screen (Monitoring > Status > Physical Layer > GbEth Port > GbE port counters), select GbE port 1 and verify that the error counters remain at 0. Monitoring>Status>Connection>Bundle counters - (BUNDLE 1 CES) 1. GbE port[1 - 2] ... (1) Port Status (Up) RX correct pkts ... (208143302) TX correct pkts ... (208291127) RX correct octets ... (1740616870) TX correct octets ... (1746982680) RX correct unicast pkts ... (208139433) TX correct unicast pkts ... (208126282) RX discard pkts ... (0) TX discard pkts ... (0) RX interface errors ... (0) TX interface errors ... (0) RX unknown protocol ... (0) > Please select item <1 to 1> F - next; B - prev; C - reset counters ESC-prev.menu; !-main menu; &-exit; @-debug
Figure 7-33. Verifying Error-Free Data Transfer (Gmux-2000)

13. From the E1/T1 traffic generator application, click the E1 traffic.
IPmux-24 Ver. 3.5
button to stop the
CESoPSN Application
7-19
7.2
Typical Pseudowire Application with Ring Protection
The section provides detailed instructions for configuring four IPmux-24 units in a ring topology operating opposite a centrally located Gmux-2000 (see Figure 7-34). Each IPmux-24 transfers PW data to Gmux-2000 a single bundle. Data flow is protected by the VLAN-based resilient Ethernet ring.
Figure 7-34. Four IPmux-24 Units in Cellular Backhauling Application with a Resilient Ethernet Ring
Equipment List
The following is a list of equipment required for setting up a typical ring application:
7-20
Four IPmux-24 units Gmux-2000 system with GbE and E1-PW/28 modules PATCH-28B patch panel Packet-switch network equipment (router etc) PC running Windows XP CBL-G703-14-PATCH cable Fiber optic cable with LC connectors Four straight Ethernet cables with RJ-45 connectors.
IPmux-24 Ver. 3.5
Installing the Units

Before starting configuration, install units as follows: 1. Connect the GE 1 port of the GbE module to PSN equipment, such as a router, using a fiber optic cable.
Figure 7-35. Connecting Gmux-2000 to PSN Equipment

2. Connect the IPmux-24 USER 3 port to PSN equipment, such as a router using a straight Ethernet cable (see Figure 7-36). 3. Connect the NET 1 and NET/USER 2 ports of IPmux-24 (A), IPmux-24 (B), IPmux-24 (C) and IPmux-24 (D) using straight Ethernet cables to form a ring (see Figure 7-36).
To Packet-Switched Network Equipment
Ethernet Cable
CONTROL
NET 1
NET/USER 2
USER 3
E1/T1 1 2 3 4
DCE
10/100BASE-T
SYNC
SYNC
SYNC
SYNC
IPmux-24 (A) Straight Ethernet Cable Straight Ethernet Cable
CONTROL
NET 1
NET/USER 2
USER 3
E1/T1 1 2 3 4 CONTROL
NET 1
NET/USER 2
USER 3
E1/T1 1 2 3 4
DCE
10/100BASE-T
SYNC
SYNC
SYNC
SYNC
DCE
10/100BASE-T
SYNC
SYNC
SYNC
SYNC
IPmux-24 (D)
IPmux-24 (B)
CONTROL
NET 1
NET/USER 2
USER 3
E1/T1 1 2 3 4
DCE
10/100BASE-T
SYNC
SYNC
SYNC
SYNC
IPmux-24 (C)
Figure 7-36. Connecting IPmux-24 Units in a Ring

4. Connect the E1 port 1 of IPmux-24 to the BTS using a straight or cross E1 cable (depending on the BTS model) with RJ-45 connectors.
IPmux-24 Ver. 3.5
7-21
CONTROL
NET 1
NET/USER 2
USER 3
E1/T1 1 2 3 4
DCE
10/100BASE-T
SYNC
SYNC
SYNC
SYNC
IPmux-24
E1 Cable
To BTS
Figure 7-37. Connecting IPmux-24 to the BTS

5. Connect the CH 1-14 connector of the E1-PW/28 module to the IO 1 connector of the PATCH-28B patch panel.
1 2 3 4 5 6 7 8 9 11 13 15 17 19 21 23 25 27 10 12 14 16 18 20 22 24 26 28
L R
CH 1-14
CH 15-28
E1.PW/28/BAL
E1-PW/28 CBL-G703-14-PATCH Cable
IO 2
IO 1
PATCH-28B
Figure 7-38. Connecting the E1-PW/28 Module to the PATCH-28B Patch Panel
Configuration Sequence
Below are the basic configuration steps that need to be followed when deploying IPmux-24 units in a ring topology. 1. Configuring the management host 2. Setting the TDM physical layer parameters (line type, clocking, etc.) according to the application requirements and topology 3. Configuring the pseudowire host 4. Setting the bridge to VLAN-aware mode 5. Configuring all network and network/user ports to be egress tagged ports in the ring, PW and management VLANs 6. Enabling the ring functionality (IPmux-24 resets automatically) 7. Setting priority classification method to 802.1p 8. Mapping traffic priority as follows: Priority 7 (reserved for the ring status traffic) mapped to traffic class 2 Priority 6 (PW traffic) mapped to traffic class 1 Priority 5 (management traffic) mapped to traffic class 0 9. Unmasking the ring status traps: prtStatusChangeTrap (27) and ethIfRingStatusChange (28)
7-22
IPmux-24 Ver. 3.5
10. Allocating timeslots to bundles 11. Connecting bundles to the central Gmux-2000.
Table 7-1. Configuration Summary

Device E1 Parameters Management Host Parameters IP address: 192.168.10.2 VLAN ID: 9 VLAN priority: 5 PW Host Parameters IP address: 192.168.11.2 VLAN ID: 11 VLAN priority: 6 Bundle Parameters Ring Traffic
IPmux-24 (A)
Transmit clock source: Adaptive Line type: Framed G.704 CRC-4 enabled CAS disabled
Bundle 1: full E1
VLAN ID: 100 VLAN priority: 7
IPmux-24 (B)
IP address: 192.168.10.3 VLAN ID: 9 VLAN priority: 5
Bundle 1: full E1
IPmux-24 (C)
Bundle 1: full E1
IPmux-24 (C)
Bundle 1: full E1
Configuring Gmux-2000
Gmux-2000 configuration procedure is similar to the one explained in the Configuring Gmux-2000 section of the CESoPSN Application above. The only difference is that the IPmux-24 bundles are connected to four Gmux-2000 bundles, and each of them carries a full E1.
Configuring IPmux-24
The following section explains the main configuration actions for a ring application with four IPmux-24 devices.
Configuring the Management Host

Refer to the Configuring the Host IP Parameters section above for instruction on how to configure the management host parameters of the IPmux-24 units.
IPmux-24 Ver. 3.5
7-23
Setting the TDM Physical Layer Parameters

Refer to the Configuring the E1 Interface section above for instruction on how to configure physical layer of the E1 interfaces.
Configuring the Pseudowire Host

Define parameters of the PW host to be used as a destination for the incoming pseudowire traffic. To configure the pseudowire host: 1. From the PW host IP menu (Configuration > Connection > PW Host IP), configure the following: IPmux-24 (A): PW host IP address 192.168.11.2 PW host IP mask 255. 255. 255.0 IPmux-24 (B): PW host IP address 192.168.11.3 PW host IP mask 255. 255. 255.0 IPmux-24 (C): PW host IP address 192.168.11.4 PW host IP mask 255. 255. 255.0 IPmux-24 (D): PW host IP address 192.168.11.5 PW host IP mask 255. 255. 255.0 2. From the PW Encapsulation menu (Configuration > Connection > PW host IP > PW Encapsulation), configure the VLAN parameters of all PW host as follows: PW host VLAN 11 PW host VLAN priority 6 Configuration>Connection>PW Host IP 1. 2. 3. 4. > IP address IP mask Default next hop Pw Encapsulation ... (192.168.11.2) ... (255. 255. 255.0) ... (-) >
1 M/ 1 C
Figure 7-39. Configuring the Pseudowire Host IP for IPmux-24 (A)
Configuring the Bridge

The IPmux-24 bridge must be configured to the VLAN-aware mode with filtering.
7-24
IPmux-24 Ver. 3.5
To configure the bridge: From the Bridge menu (Configuration > Bridge), configure the following: VLAN Mode Aware Forwarding Mode Filter Configuration>Bridge 1. 2. 3. 4. 5. 6. 7. VLAN Mode Forwarding Mode Aging Time[300 - 3060] Static MAC Table Erase MAC Table Bridge Port VLAN Membership (Aware) (Filter) ...(300) []> > >
1 M/ 1 C
Figure 7-40. Configuring the General Bridge Parameters
Configuring the VLAN Membership

To configure the VLAN Membership: From the VLAN Membership menu (Configuration > Bridge > VLAN Membership), set the network and network/user ports of all IPmux-24 units to be tagged members of VLAN 9 (management), 11 (pseudowire) and 100 (ring): 1. Type a to invoke the Add mode. 2. In the Add mode, set VLAN ID to 9, 11 or 100. 3. Save the changes. 4. Select Egress Tagged Ports and type a to invoke the Add mode. 5. In the Add mode, set Egress Tagged Port to 1 and 2. Configuration>Bridge>Vlan Membership Vlan Id[1 - 4094] ... (9) 1. Egress Tagged Ports > (1,2) 2. Egress Untagged Ports > () > Please select item <1 to 2> A - Add New VLAN ; F - Forward ; D - Delete ESC-prev.menu; !-main menu; &-exit
1 M/ 1 C
Figure 7-41. Configuring Network Port as VLAN 9 Members (IPmux-24 A)
Enabling the Ring Functionality

When the preliminary configuration is completed, enable the ring functionality.
IPmux-24 Ver. 3.5
7-25
To enable the ring functionality: From the Protection menu (Configuration > System > Protection), set the Ring Administrative Status to Up. IPmux-24 resets itself automatically. The ring becomes operational, reversing the Ethernet traffic flow direction, if one of the ring segments fails. Configuration>System>Protection Group ID (1) Port Members (1,2) Redundancy Method (Ring) 1. 2. 3. 4. 5. > Ring Administrative Status Keep Alive Tx Time[Msec][2 - 100] Keep Alive Drops To Fall[1 - 10] PTP VLAN ID Mcast VLAN ID (Up) (13) (3) (4001) (4002))
... ... ... ...
1 M/ 1 C
Figure 7-42. Enabling the Ethernet Ring
Configuring the Priority Classification Method

IPmux-24 Ethernet ring protection is a VLAN-based mechanism. This is why the traffic must be prioritized using the VLAN priority method 802.1p. To configure the priority classification method: From the Classification menu (Configuration > QoS > Priority > Classification), set the priority classification method of each network port (Network-ETH1 and Network/User-ETH2) and TDM PW traffic to 802.1p.
IPmux-24 Configuration>QoS>Priority>Classification 1. Network-ETH1 2. Network/User-ETH2 3. User-ETH3 4. TDM PW > > > > (802.1p ) (802.1p) (Port default priority ) (802.1p)
1 M/ 1 C
Figure 7-43. Configuring the Priority Classification Method
Mapping the 802.1p Priorities to Traffic Classes

To ensure a proper operation of the Ethernet ring, map the 802.1p priorities as follows: Priority 7 (ring status traffic) to traffic class 2
7-26
IPmux-24 Ver. 3.5
Priority 6 (PW traffic) to traffic class 1 Priority 5 (management traffic) to traffic class 0.
To map priorities to traffic classes: From the 802.1p menu (Configuration > Configuration > QoS > Priority > Mapping > 802.1p), map the user priorities 57 to the traffic classes, as explained above.
IPmux-24 Configuration>Configuration>QoS>Priority>Mapping>802.1p 1. User priority 0 2. User priority 1 3. User priority 2 4. User priority 3 5. User priority 4 6. User priority 5 7. User priority 6 8. User priority 7 > Please select item <1 to 8> ESC-prev.menu; !-main menu; &-exit >(Traffic class 0) >(Traffic class 0) >(Traffic class 0) >(Traffic class 0) >(Traffic class 0) >(Traffic class 0) >(Traffic class 1) >(Traffic class 3)
1 M/ 1 C
Figure 7-44. Mapping the 802.1p Priorities
Unmasking Ring Status Traps

In order to receive status indications of the port and ring status changes, you have to unmask the prtStatusChangeTrap (27) and ethIfRingStatusChange (28) traps. To unmask the ring status alarms: 1. From the Management menu, select Alarm trap mask. The Alarm Trap Mask menu appears (see Figure 7-45). 2. From the Alarm Traps Mask menu, select Alarm ID and enter 27 for the port status change trap or 28 for the ring status change trap. 3. Set Trap Status to Unmask.
IPmux-24 Ver. 3.5
7-27
Configuration>System>Management>Alarm trap mask Active alarm traps: 1. Alarm ID (use 'help')[1 - 40] 2. Trap status > Please select item <1 to 2> S - Save; ? - Help ESC-prev.menu; !-main menu; &-exit > (-) ... (28) (Unmask)
1 M/ 1 C
Figure 7-45. Unmasking the Ring Status Trap
Configuring and Connecting the PW Bundles

Refer to the Assigning Timeslots to the Bundle and Connecting the Bundle sections above for instruction on how to add timeslots to the bundles and connect them to the central Gmux-2000. Each IPmux-24 transfers PW data to Gmux-2000 over a single bundle, see Table 7-1 for the timeslot allocation information.
7-28
IPmux-24 Ver. 3.5
Appendix A Connection Data

A.1 E1 and T1 Connector
Balanced Connector
The E1 and T1 interfaces of IPmux-24 terminate in 8-pin RJ-45 connectors, wired in accordance with Table A-1.
Table A-1. E1/T1 Port Connector Pinout

Pin 1 2 3, 6 4 5 7, 8 Designation RD (R) RD (T) TD (R) TD (T) Direction Input Input Output Output N/A Function Receive data (ring) Receive data (tip) FGND Transmit data (ring) Transmit data (tip) Not connected
Balanced-to-Unbalanced Adapter Cable

When IPmux-24 is ordered with unbalanced E1 interface, it is necessary to convert the RJ-45 connector to the standard pair of BNC female connectors used by unbalanced E1 interfaces. For that purpose, RAD offers a 150-mm long adapter cable, CBL-RJ45/2BNC/E1/X, wired in accordance with Figure A-1.
Receive (Green)
RJ-45
RX Ring RX Tip NC TX Ring TX Tip NC NC NC
1 2 3 4 5 6 7 8
Transmit (Red)
BNC Female
. . .
Receive (Green BNC)
. . .
Transmit (Red BNC)
Shielded RJ-45
Figure A-1. CBL-RJ45/2BNC/E1/X Cable Wiring Diagram

IPmux-24 Ver. 3.5 E1 and T1 Connector A-1
A.2
Ethernet Connectors
The Ethernet electrical interfaces terminate in 8-pin RJ-45 connectors, wired in accordance with Table A-2 (Fast Ethernet) or Table A-3 (Gigabit Ethernet).
Table A-2. 100BaseT Connector Pinout

Pin 1 2 3 4 5 6 7 8 Function Tx+ Tx Rx+ Rx
Table A-3. 1000BaseT Connector Pinout

Pin 1 2 3 4 5 6 7 8 MDI A+ AB+ C+ CBD+ DMDIX B+ BA+ D+ DAC+ C-
A-2
Ethernet Connectors
IPmux-24 Ver. 3.5
A.3
CONTROL Connector
The control terminal interface terminates in a V.24/RS-232 9-pin D-type female DCE connector. Table A-4 lists the CONTROL connector pin assignments.
Table A-4. CONTROL Connector Pinout

Pin 1 2 3 4 5 6 7 8 9 Function Tx Rx GND
A.1
External Clock Connector
The external clock interface terminates in an 8-pin RJ-45 connector, which also serves for alarm relay. Table A-5 lists the connector wiring.
Table A-5. EXT. CLK Connector Pinout

Pin 1 2 3 4 5 6 7 8 Function RxRing (clock in) RxTip (clock in) Alarm In (RS-232 level signal) TxRing (clock out, optional) TxTip (clock out, optional) Dry contact relay (normally shorted to pin 7) Dry contact relay (central pin) Dry contact relay (normally open, closed if an alarm is active)
IPmux-24 Ver. 3.5
External Clock Connector
A-3
A.2
Alarm Relay
IPmux-24 supports dry contact alarm relay via dedicated pins 6, 7 and 8 of the RJ-45 EXT. CLK connector (see Table A-5).
A-4
Alarm Relay
IPmux-24 Ver. 3.5
Supplement
AC/DC Adapter (AD) Plug

for DC Power Supply Connection
Note Ignore this supplement if the unit is AC-powered.
Certain units are equipped with a wide-range AC/DC power supply. These units are equipped with a standard AC-type 3-prong power input connector located on the unit rear panel. This power input connector can be used for both AC and DC voltage inputs. For DC operation, a compatible straight or 90-degree AC/DC Adapter (AD) plug for attaching to your DC power supply cable is supplied with your RAD product (see Figure 1 and Figure 2). Connect the wires of your DC power supply cable to the AD plug, according to the voltage polarity and assembly instructions provided on page 2.
Figure 1. Straight AD Plug
Figure 2. 90-Degree AD Plug Caution

Prepare all connections to the AD plug before inserting it into the units power connector.
Publication No. SUP-930-07/08
The Access Company
AC/DC Adapter (AD) Plug
To prepare the AD plug and connect it to the DC power supply cable: 1. Loosen the cover screw on the bottom of the AD plug to open it (see Figure 3). 2. Run your DC power supply cable through the removable cable guard and through the open cable clamp. 3. Place each DC wire lead into the appropriate AD plug wire terminal according to the voltage polarity mapping shown. Afterwards, tighten the terminal screws closely. 4. Fit the cable guard in its slot and then close the clamp over the cable. Tighten the clamp screws to secure the cable. 5. Reassemble the two halves of the AD plug and tighten the cover screw. 6. Connect the assembled power supply cable to the unit.
Figure 3. AD Plug Details
Note: You have to flip over the non-90-degree AD plug type by 180 degrees to insert it into the unit. After inserting it, verify that the blue (negative) wire is connected to the POWER and the brown (positive) wire is connected to the RETURN.
Reversing the wire voltage polarity will not cause damage to the unit, but the internal protection fuse will not function.
Warning
Always connect a ground wire to the AD plugs chassis (frame) ground terminal. Connecting the unit without a protective ground, or interrupting the grounding (for example, by using an extension power cord without a grounding conductor) can damage the unit or the equipment connected to it! The AD adapter is not intended for field wiring.
24 Raoul Wallenberg Street, Tel Aviv 69719, Israel Tel: +972-3-6458181, Fax +972-3-6483331, +972-3-6498250 E-mail: erika_y@rad.com, Web site: http://www.rad.com
Customer Response Form

RAD Data Communications would like your help in improving its product documentation. Please complete and return this form by mail or by fax or send us an e-mail with your comments. Thank you for your assistance!
Manual Name: Publication Number:
IPmux-24 Ver. 3.5 488-200-07/10
Please grade the manual according to the following factors:
Excellent
Installation instructions Operating instructions Manual organization Illustrations The manual as a whole
Good
Fair
Poor
Very Poor
What did you like about the manual?
Error Report
Type of error(s) or problem(s): Incompatibility with product Difficulty in understanding text Regulatory information (Safety, Compliance, Warnings, etc.) Difficulty in finding needed information Missing information Illogical flow of information Style (spelling, grammar, references, etc.) Appearance Other Please list the exact page numbers with the error(s), detail the errors you found (information missing, unclear or inadequately explained, etc.) and attach the page to your fax, if necessary.
Please add any comments or suggestions you may have.
You are:
Distributor End user VAR Other
Who is your distributor? Your name and company: Job title: Address: Direct telephone number and extension: Fax number: E-mail:
Publication No. 488-200-07/10
Order this publication by Catalog No. 803781
International Headquarters
24 Raoul Wallenberg Street Tel Aviv 69719, Israel Tel. 972-3-6458181 Fax 972-3-6498250, 6474436 E-mail market@rad.com
North America Headquarters

900 Corporate Drive Mahwah, NJ 07430, USA Tel. 201-5291100 Toll free 1-800-4447234 Fax 201-5295777 E-mail market@rad.com
www.rad.com
The Access Company

IPmux-24 3.5 MN

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

IPmux-24 3.5 MN

Încărcat de

Drepturi de autor:

Formate disponibile

INSTALLATION AND OPERATION MANUAL

The Access Company

Installation and Operation Manual Notice

19992010 RAD Data Communications Ltd.

Publication No. 488-200-07/10

General Safety Instructions

Handling Energized Products

Connecting Data and Telecommunications Cables

FXS (Foreign Exchange Subscriber)

Electromagnetic Compatibility (EMC)

FCC-15 User Information

Canadian Emission Requirements

Warning per EN 55022 (CISPR-22)

Mise au rebut du produit

Instructions gnrales de scurit

Manipuler des produits sous tension

Connexion au courant du secteur

Safety: Supplementary Information:

Channel Circuit Emulation Service

Data Diagnostics Encapsulation

Flow Control Frame

Full Duplex G.703

Master Clock Network

Quick Start Guide

Installing the Unit

Connecting the Interfaces

Connecting the Power

Configuring the Unit

IPmux-24 Ver. 3.5

Configuring the Unit

Quick Start Guide

Installation and Operation Manual

Starting a Terminal Session for the First Time

Configuring the IP Management Parameters

Configuring the System Clock

Configuring E1 and T1 at the Physical Level

Configuring the Unit

IPmux-24 Ver. 3.5

Installation and Operation Manual

Quick Start Guide

IPmux-24 Ver. 3.5

Configuring the Unit

Quick Start Guide

Installation and Operation Manual

Configuring the Unit

IPmux-24 Ver. 3.5

Installation and Operation Manual

IPmux-24 Ver. 3.5

Installation and Operation Manual

Installation and Operation Manual

Installation and Operation Manual

IPmux-24 Ver. 3.5

Installation and Operation Manual

IPmux-24 Ver. 3.5

IPmux-24 Ver. 3.5

Installation and Operation Manual

Figure 1-1. 2G/3G Cellular Backhaul over an Ethernet Ring

IPmux-24 Ver. 3.5

Installation and Operation Manual

IPmux-24 Ver. 3.5

Installation and Operation Manual

IPmux-24 Ver. 3.5