I pmux 24-manual

IPmux-24 TDM Pseudowire Access Gateway

Version 3.5

INSTA

LLATIO

N A

ND

O

PER

ATIO

N M

AN

UA

L

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: [email protected]

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: [email protected]

© 1999–2010 RAD Data Communications Ltd. Publication No. 488-200-07/10

mailto:[email protected]�


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 unit’s 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.

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.

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.

Warning

Warning

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 Safety Status

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

SELV Safety Extra Low Voltage:

Ports which do not present a safety hazard. Usually up to 30 VAC or 60 VDC.

xDSL (without feeding voltage), Balanced E1, T1, Sub E1/T1

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.

FXS (Foreign Exchange Subscriber) 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.

FXO (Foreign Exchange Office), xDSL (with feeding voltage), U-Interface ISDN

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.

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.

To reduce the risk of fire, use only No. 26 AWG or larger telecommunication line cords.

Pour réduire les risques s’incendie, utiliser seulement des conducteurs de télécommunications 26 AWG ou de section supérieure.

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.

Caution

Attention

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 numérique de la classe A respecte toutes les exigences du Règlement sur le matériel brouilleur du Canada.

Warning per EN 55022 (CISPR-22)

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 résidentiel, cet appareil peut provoquer des brouillages radioélectriques. Dans ces cas, il peut être demandé à l’utilisateur de prendre les mesures appropriées.

Das vorliegende Gerät fällt unter die Funkstörgrenzwertklasse A. In Wohngebieten können beim Betrieb dieses Gerätes Rundfunkströrungen auftreten, für deren Behebung der Benutzer verantwortlich ist.

Warning

Avertissement

Achtung

Fra

nça

is

Mise au rebut du produit

Afin de faciliter la réutilisation, le recyclage ainsi que d'autres formes de récupération d'équipement mis au rebut dans le cadre de la protection de l'environnement, il est demandé au propriétaire de ce produit RAD de ne pas mettre ce dernier au rebut en tant que déchet municipal non trié, une fois que le produit est arrivé en fin de cycle de vie. Le client devrait proposer des solutions de réutilisation, 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.

Instructions générales de sécurité

Les instructions suivantes servent de guide général d'installation et d'opération sécurisées des produits de télécommunications. Des instructions supplémentaires sont éventuellement indiquées dans le manuel.

Symboles de sécurité

Ce symbole peut apparaitre sur l'équipement ou dans le texte. Il indique des risques potentiels de sécurité pour l'opérateur ou le personnel de service, quant à l'opération du produit ou à sa maintenance.

Danger de choc électrique ! Evitez tout contact avec la surface marquée tant que le produit est sous tension ou connecté à des lignes externes de télécommunications.

Mise à la terre de protection : la cosse ou la borne marquée devrait être connectée à la prise de terre de protection du bâtiment.

Avertissement

Fra

nça

is

Certains produits peuvent être équipés d'une diode laser. Dans de tels cas, une étiquette indiquant la classe laser ainsi que d'autres avertissements, le cas échéant, sera jointe près du transmetteur optique. Le symbole d'avertissement laser peut aussi être joint.

Veuillez observer les précautions suivantes :

• Avant la mise en marche de l'équipement, assurez-vous que le câble 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 câbles ou connecteurs de fibre optique cassés ou sans terminaison et n'observez pas directement un rayon laser.

• L'usage de périphériques optiques avec l'équipement augmentera le risque pour les yeux.

• L'usage de contrôles, ajustages ou procédures autres que celles spécifiées ici pourrait résulter en une dangereuse exposition aux radiations.

ATTENTION : Le rayon laser peut être invisible !

Les utilisateurs pourront, dans certains cas, insérer leurs propres émetteurs-récepteurs Laser SFP dans le produit. Les utilisateurs sont avertis que RAD ne pourra pas être tenue responsable de tout dommage pouvant résulter de l'utilisation d'émetteurs-récepteurs non conformes. Plus particulièrement, les utilisateurs sont avertis de n'utiliser que des produits approuvés par l'agence et conformes à la réglementation locale de sécurité laser pour les produits laser de classe 1.

Respectez toujours les précautions standards de sécurité durant l'installation, l'opération et la maintenance de ce produit. Seul le personnel de service qualifié et autorisé devrait effectuer l'ajustage, la maintenance ou les réparations de ce produit. Aucune opération d'installation, d'ajustage, de maintenance ou de réparation ne devrait être effectuée par l'opérateur ou l'utilisateur.

Manipuler des produits sous tension

Règles générales de sécurité

Ne pas toucher ou altérer l'alimentation en courant lorsque le câble d'alimentation est branché. Des tensions de lignes peuvent être présentes dans certains produits, même lorsque le commutateur (s'il est installé) est en position OFF ou si le fusible est rompu. Pour les produits alimentés par CC, les niveaux de tension ne sont généralement pas dangereux mais des risques de courant peuvent toujours exister.

Avant de travailler sur un équipement connecté aux lignes de tension ou de télécommunications, retirez vos bijoux ou tout autre objet métallique pouvant venir en contact avec les pièces sous tension.

Sauf s'il en est autrement indiqué, tous les produits sont destinés à être mis à la terre durant l'usage normal. La mise à la terre est fournie par la connexion de la fiche principale à une prise murale équipée d'une borne protectrice de mise à la terre. Si une cosse de mise à la terre est fournie avec le produit, elle devrait être connectée à tout moment à une mise à la terre de protection par un conducteur de diamètre 18 AWG ou plus. L'équipement monté en châssis ne devrait être monté que sur des châssis et dans des armoires mises à la terre.

Branchez toujours la mise à la terre en premier et débranchez-la en dernier. Ne branchez pas des câbles de télécommunications à un équipement qui n'est pas mis à la terre. Assurez-vous que tous les autres câbles sont débranchés avant de déconnecter la mise à la terre.

Avertissement

Fra

nça

is

Connexion au courant du secteur

Assurez-vous que l'installation électrique est conforme à la réglementation locale.

Branchez toujours la fiche de secteur à une prise murale équipée 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 bâtiment devrait avoir une capacité élevée de rupture et devrait fonctionner sur courant de court-circuit dépassant 35A (40A aux Etats-Unis et Canada).

Branchez toujours le câble 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 câble d'alimentation ne peut pas être facilement débranché en cas d'urgence, assurez-vous qu'un coupe-circuit ou un disjoncteur d'urgence facilement accessible est installé dans l'installation du bâtiment.

Le disjoncteur devrait déconnecter simultanément les deux pôles si le système de distribution de courant est de type IT.

Connexion d'alimentation CC

Sauf s'il en est autrement spécifié dans le manuel, l'entrée CC de l'équipement est flottante par rapport à la mise à la terre. Tout pôle doit être mis à la terre en externe.

A cause de la capacité de courant des systèmes à alimentation CC, des précautions 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 isolée de toute source de courant CA (secteur) et que l'installation est conforme à la réglementation 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 bâtiment devrait avoir une capacité élevée de rupture et devrait fonctionner sur courant de court-circuit dépassant 35A (40A aux Etats-Unis et Canada).

Avant la connexion des câbles 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 câbles d'alimentation CC, connectez d'abord le conducteur de mise à la terre à la borne correspondante, puis le pôle positif et en dernier, le pôle négatif. Remettez le coupe-circuit en position ON.

Un disjoncteur facilement accessible, adapté et approuvé devrait être intégré à l'installation du bâtiment.

Le disjoncteur devrait déconnecter simultanément les deux pôles si l'alimentation en courant CC est flottante.

Declaration of Conformity

Manufacturer's Name: RAD Data Communications Ltd.

Manufacturer's Address: 24 Raoul Wallenberg St., Tel Aviv 69719, Israel

declares that the product:

Product Name: IPmux-24

conforms to the following standard(s) or other normative document(s):

EMC: EN 55022:1998 + A1:2000, A2:2003

Information technology equipment – Radio disturbance characteristics – Limits and methods of measurement.

EN 50024: 1998 A1:2001, A2:2003

Information technology equipment – Immunity characteristics – Limits and methods of measurement.

EN 61000-3-2:2000 + A2:2005

Electromagnetic compatibility (EMC) - Part 3-2: Limits - Limits for harmonic current emissions (equipment input current up to and including 16A per phase).

EN 61000-3-3:1995 + A1:2001

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.

Safety: EN 60950-1:2001 + A11:2004

Information technology equipment – Safety – Part 1: General requirements.

Supplementary Information:

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 Communications GmbH, Otto-Hahn-Str. 28-30, 85521 Ottobrunn-Riemerling, Germany

Glossary

Address A coded representation of the origin or destination of data.

Attenuation Signal power loss through equipment, lines or other transmission devices. Measured in decibels.

AWG The American Wire Gauge System, which specifies wire width.

Balanced A transmission line in which voltages on the two conductors are equal in magnitude, but opposite in polarity, with respect to ground.

Bandwidth 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.

Bipolar Signaling method in E1/T1 representing a binary “1” by alternating positive and negative pulses, and a binary “0” by absence of pulses.

Bit The smallest unit of information in a binary system. Represents either a one or zero (“1” or “0”).

Bridge A device interconnecting local area networks at the OSI data link layer, filtering and forwarding frames according to media access control (MAC) addresses.

Buffer 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.

Byte A group of bits (normally 8 bits in length).

Cell 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.

CESoPSN 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).

Channel A path for electrical transmission between two or more points. Also called a link, line, circuit or facility.

Circuit Emulation Service

Technology for offering circuit emulation services over packet-switched 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.

Clock A term for the source(s) of timing signals used in synchronous transmission.

Data Information represented in digital form, including voice, text, facsimile and video.

Diagnostics The detection and isolation of a malfunction or mistake in a communications device, network or system.

Encapsulation 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.

ERPS 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.

Ethernet 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.

Flow Control A congestion control mechanism that results in an ATM system implementing flow control.

Frame 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.

Framing 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.

Full Duplex A circuit or device permitting transmission in two directions (sending and receiving) at the same time.

G.703 An ITU standard for the physical and electrical characteristics of various digital interfaces, including those at 64 kbps and 2.048 Mbps.

Gateway 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.

Impedance The combined effect of resistance, inductance and capacitance on a transmitted signal. Impedance varies at different frequencies.

Interface A shared boundary, defined by common physical interconnection characteristics, signal characteristics, and meanings of exchanged signals.

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).

Jitter The deviation of a transmission signal in time or phase. It can introduce errors and loss of synchronization in high speed synchronous communications.

Loading 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.

Loopback 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.

NTP 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.

Manager 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.

Master Clock The source of timing signals (or the signals themselves) that all network stations use for synchronization.

Network (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.

Packet An ordered group of data and control signals transmitted through a network, as a subset of a larger message.

Payload 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.

Physical Layer 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.

Port The physical interface to a computer or multiplexer, for connection of terminals and modems.

Protocol A formal set of conventions governing the formatting and relative timing of message exchange between two communicating systems.

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.

SAToP Structure-Agnostic Time Division Multiplexing (TDM) over Packet. A method for encapsulating Time Division Multiplexing (TDM) bit-streams (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.

Space In telecommunications, the absence of a signal. Equivalent to a binary 0.

T1 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.

Throughput 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).

TDMoIP® 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.

IPmux-24 Ver. 3.5 Configuring the Unit 1

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.

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.

Caution

Quick Start Guide Installation and Operation Manual

2 Configuring the Unit IPmux-24 Ver. 3.5

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.

Installation and Operation Manual Quick Start Guide

IPmux-24 Ver. 3.5 Configuring the Unit 3

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.

Quick Start Guide Installation and Operation Manual

4 Configuring the Unit IPmux-24 Ver. 3.5

IPmux-24 Ver. 3.5 i

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

Table of Contents Installation and Operation Manual

ii IPmux-24 Ver. 3.5

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 Introduction ............................................................................................................... 2-1 2.2 Site Requirements and Prerequisites .......................................................................... 2-1 2.3 Package Contents ...................................................................................................... 2-1 2.4 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 Turning On the Unit ................................................................................................... 3-1 3.2 Indicators .................................................................................................................. 3-1 3.3 Default Settings ......................................................................................................... 3-3 3.4 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

Installation and Operation Manual Table of Contents

IPmux-24 Ver. 3.5 iii

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


iv IPmux-24 Ver. 3.5

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

Installation and Operation Manual Table of Contents

IPmux-24 Ver. 3.5 v

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 Compatibility Requirements ........................................................................................ 6-1 6.2 Impact ....................................................................................................................... 6-1 6.3 Software Upgrade Options ......................................................................................... 6-1 6.4 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


vi IPmux-24 Ver. 3.5

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

IPmux-24 Ver. 3.5 Overview 1-1

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).

The unit can also be ordered with Fast Ethernet interfaces only (IPmux-24/FE).

Note

Chapter 1 Introduction Installation and Operation Manual

1-2 Overview IPmux-24 Ver. 3.5

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.

Installation and Operation Manual Chapter 1 Introduction


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.



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).



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.



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 Center’s 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.


IPmux-24 Ver. 3.5 Functional Description 1-7

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).


1-8 Functional Description IPmux-24 Ver. 3.5

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 n×64 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).



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.

• 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.

Note



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



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.

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

Note



Table 1-1. UDP/IP Frame Structure

Field Length (Bytes) Field

7 Preamble

1 SFD

6 Destination MAC Address

6 Source MAC Address

2 Type 0x800

1 Vers/HLEN

1 Service Type

2 Total Length

2 Identification

1 Flags/Fragment Offset (most)

1 Fragment Offset (least)

1 Time to Live

1 Protocol

2 Header Checksum

4 Source IP Address

4 Destination IP Address

2 UDP Source Port

2 UDP Destination Port

2 UDP Message Length

2 UDP Checksum

4 PW Control Word

... Data

4 CRC

IP Layer

ETH Layer

UDP Layer

Data Layer

LLC Layer Note: IEEE 802.1p&Q VLAN tagging (additional 4 bytes if enabled), 0x8100.

The UDP source port field is

used to transfer a destination

bundle number. See Note

below.

ETH Layer



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.

802.1D Tag Protocol Type

81 00

user_priority

CFI

= 0 VID

8 6 5 4 1 8 1

Priority VLAN ID

Figure 1-8. VLAN Tag Format (802.1p&Q)

UDP Support

Table 1-2. UDP Ports Definition

Field Length (Bits) Field Description Value Function

2 bytes UDP Source Port 2–497d* Destination bundle

2 bytes UDP Destination Port 2142d Standard TDMoIP UDP port

* The MSB of this field can be either 1 or 0 for inband end-to-end proprietary signaling.

The UDP Source Port field is used for destination bundle indication.

For more information about VLAN tagging, refer to IEEE standard 802.1p&Q.

Note

Note



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


7 Preamble

1 SFD



2 Type 0x8847

20 MPSL PW label

3 EXP

1 Stacking bit

8 TTL

20 Inner label

3 EXP

1 Stacking bit

8 TTL

4 PW Control Word

... Data

4 CRC

ETH Layer


ETH Layer

MPLS Layer (Bits)

The inner label field is used to

transfer a destination bundle

number.

Data Layer



Ethernet (MEF 8) Encapsulation

Table 1-4. Ethernet Frame Structure


7 Preamble

1 SFD



2 Type 0x88d8

20 ECID

13 0x102

4 PW Control Word

... Data

4 CRC

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.

MAC Layer


ETH Layer

Data Layer

ECID Layer



Non P-FormatAAL1 Cell

TDM Payload(Voice/CAS)

TDMoIP Payloadup to 30 AAL1 Cells

ControlWord

L2/L3Header

EthernetPacketCRC

P-Format AAL1 CELL(Structured Bundles

only)

OR

46-Octet PayloadPCRCSNC PointerE

47-Octet PayloadPCRCSNC

Figure 1-11. TDMoIP CE Encapsulation

L2/L3Header

ControlWord TDM Payload CRC Ethernet

Packet

N TDM Bytes

TDMBitstream

FRG bits = 00(no fragmentation)

Figure 1-12. SAToP Encapsulation



4 25 254 254

Frame1

Frame2

FrameN

Frame 1

4 25 4 25 4 25

Frame 2 Frame N

L2/L3Header

ControlWord CRC Ethernet Packet

TDM Payload

FRG bits = 00(no fragmentation)

Figure 1-13. CESoPSN Encapsulation (E1, Bundle with Timeslots 4 and 25)

HDLC TypeTDMoIP Payload

Control Word

L2/L3 Header

HDLC Frame in TDM

Ethernet Packet

CRC

CRC-16DataFlags

Zero BitDeletion

Flags

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.

PDV

t

t

Packets Leaving IPmux-24

Packets Arriving

Figure 1-15. Packet Delay Variation



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 (Jitter) Buffer Depth

Normal Operation(No PDV)

Maximum Jitter Buffer Size(2 PDVT + 2 PCT + 1 msec)

PDVT Buffer + Packet Creation Time

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) = TS

0.125N 47 ××

Where:

N = 48

ebytes/framTDM

TS = number of assigned timeslots (in unframed mode= 32 for E1, 24 for T1)



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) = TS0.125N ×

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

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: 5447/n for a full E1

4107/n for a full T1 Framed: 8000 × k/(46.875 × n)

Where k = number of assigned timeslots

Where n = 48

ebytes/framTDM

The maximum Ethernet throughput is calculated by:

PCT1

bits 8)

bytes) (in size frame

( ××+++4444444 34444444 21

payloadoverhead frameCW VLAN

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.

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.

Note

Note



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.

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 Source IP Check VLAN Check

Management Performed Performed

TDM over IP Performed Performed in the

VLAN-aware mode

Receiving Ping Not performed Not performed, even if it is

one of the IPs that is

configured for the manager

or for the connection

ARP Not performed

Telnet Performed only when Telnet access mark is

from manager

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.

Note



Table 1-6. VLAN Check for Packets Sent by IPmux-24

Packet Type VLAN Support

Management As configured for the manager

TDM over IP As configured for the connection

Answer to Ping 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 No VLAN value unless it is to one of the managers or the connection’s IP

address Telnet

Ping initiated by IPmux-24

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



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).

VLANs reserved for the ring messages cannot be used for other traffic.

Note



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.

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.

Note



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.



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.

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:

Note



• 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,



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



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.



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 don’t 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



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, RAD’s 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.


1-32 Technical Specifications IPmux-24 Ver. 3.5

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 Technical Specifications

E1 Interface Number of Ports 1, 2 or 4

Compliance ITU-T Rec. G.703, G.704, G.706, G.732, G.823

Data Rate 2.048 Mbps

Line Code HDB3

Framing Unframed, framed, multiframe; with or without CRC-4

Signaling CAS, CCS (transparent)

Line Impedance Balanced: 120Ω; unbalanced: 75Ω

Signal Levels 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%

Jitter Performance As per ITU-T G.823

Connector Balanced: RJ-45

Unbalanced: Two BNC coax (via an adapter cable)


IPmux-24 Ver. 3.5 Technical Specifications 1-33

T1 Interface Number of Ports 1, 2 or 4

Compliance ANSI T1.403, AT&T TR-62411, ITU-T Rec. G.703, G.704, G.824

Data Rate 1.544 Mbps

Line Code B8ZS, B7ZS, AMI

Framing Unframed, SF, ESF

Signaling CAS (robbed bit), CCS (transparent)

Line Impedance Balanced: 100Ω

Signal Levels 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 As per AT&T TR-62411, G.824 (for internal, loopback and external clock modes)

Connector RJ-45

Ethernet Interface

Compliance IEEE 802.3, 802.3u, 802.1p&Q

Port Combinations Any port can be either SFP slot or built-in UTP

Interfaces UTP (10/100BaseT)

SFP-based fiber optic (1000BaseX or 100BaseFx)

SFP-based electrical (10/100/1000BaseT)

Frame Size 1632 bytes max

Fiber Optic Specifications

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 Adaptive Clock

Frequency Accuracy Better than 16 ppb and G.823 synchronization interface requirements (clause 6), when locked to a PRC (stratum 1) or SSU (stratum 2) clock



Frequency Accuracy in Holdover

±16 ppb ±1 ppb of aging per day

Pseudowire Number of Bundles Up to 64

Standard Compliance

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.5–180 msec (unframed) with 0.1 msec granularity

2.5–180 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 As per G.826 and RFC 2495

Ethernet As per RFC 2819

Receive Buffer Indication

Overflow, underflow, sequence error

Alarm Relay Dry Contact Via pin 6, pin 7 and pin 8 of the EXT CLK connector (RJ-45)

Indicators General 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


IPmux-24 Ver. 3.5 Technical Specifications 1-35

T1 T1 SYNC (red/green) – T1 synchronization status

Ethernet LINK/ACT (green) – Link/activity status

Power AC/DC Source 100–240 VAC, 50/60 Hz or 48/60 VDC nominal (40 to 72 VDC)

DC Source 24/48/60 VDC nominal (18 to 72 VDC)

Power Consumption 13W max

Physical Height 47 mm (1.8 in)

Width 215 mm (8.4 in)

Depth 147 mm (5.8 in)

Weight 0.7 kg (1.5 lb)

Environment Temperature IPmux-24: 0°C to 50°C (32°C to 122°F)

IPmux-24/H: -30 to 65°C (-22 to 149°F)

Humidity Up to 90%, non-condensing



IPmux-24 Ver. 3.5 Package Contents 2-1

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.

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 0°C to 50°C (32°C to 122°F), 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)

Warning

Chapter 2 Installation and Setup Installation and Operation Manual

2-2 Mounting the Unit IPmux-24 Ver. 3.5

• 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 Cable Type

Control

terminal

DB-9 to DB-9, RS-232/V.24 compliant cable for ASCII-based terminal

control

Ethernet 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.

Installation and Operation Manual Chapter 2 Installation and Setup

IPmux-24 Ver. 3.5 Installing SFP Modules 2-3

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.

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.

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.

Note

Warning


2-4 Connecting to E1/T1 Devices IPmux-24 Ver. 3.5

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.

RESTOREDEFAULT

CONTROL

DCE GbE/100Fx

NET1

NET/USER2

USER3

10/100BASE-T

1

SYNC

2 3 4

SYNC SYNC SYNC

E1/T1

Figure 2-2. NET 1 and NET/USER 2 Fiber Optic Connectors

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 1–4. Unbalanced E1 interface is provided via CBL-RJ45/2BNC/E1/X adapter cable (see Appendix A for the connector pinouts and cable wiring diagram).

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.

Caution

Note


IPmux-24 Ver. 3.5 Connecting to ASCII Terminal 2-5

RESTOREDEFAULT

CONTROL

DCE GbE/100Fx

NET1

NET/USER2

USER3

10/100BASE-T

1

SYNC

2 3 4

SYNC SYNC SYNC

E1/T1

Figure 2-4. E1/T1 1–4 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.

RESTOREDEFAULT

CONTROL

DCE GbE/100Fx

NET1

NET/USER2

USER3

10/100BASE-T

1

SYNC

2 3 4

SYNC SYNC SYNC

E1/T1

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.

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.

Caution


2-6 Connecting to Power IPmux-24 Ver. 3.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


IPmux-24 Ver. 3.5 Connecting to Power 2-7

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.

Note


2-8 Connecting to Power IPmux-24 Ver. 3.5

IPmux-24 Ver. 3.5 Indicators 3-1

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.

RAD

IPmux-24

PWR TST 1 2 3

ETHLINK/ACT

Figure 3-1. Front Panel

Chapter 3 Operation Installation and Operation Manual

3-2 Indicators IPmux-24 Ver. 3.5

Figure 3-2. Rear Panel

Table 3-1. LEDs and Controls

Name Type Function Location

PWR Green LED ON – Power is ON Front panel

TST/ALM Red/yellow

LED

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

Front panel

E1 SYNC Red/green

LED

ON (green) – E1 link is synchronized

ON (red) – E1 link has lost synchronization

OFF – E1 link is disabled

Rear panel

T1 SYNC Red/green

LED

ON (green) – T1 link is synchronized

ON (red) – T1 link has lost synchronization

OFF – T1 link is disabled

Rear panel

ETH

LINK/ACT 1

Green LED ON – Network Ethernet link is OK

Blinks – Data is being transmitted or received on the network

Ethernet link

Front panel

ETH

LINK/ACT 2

Green LED ON – User Ethernet link 1 is OK

Blinks – Data is being transmitted or received on the user

Ethernet link 1

Front panel

ETH

LINK/ACT 3

Green LED ON – User Ethernet link 2 is OK

Blinks – Data is being transmitted or received on the user

Ethernet link 2

Front panel

EXT. CLK 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

Rear panel

RESTORE

DEFAULT

Button Restores default values Rear panel

Installation and Operation Manual Chapter 3 Operation

IPmux-24 Ver. 3.5 Default Settings 3-3

3.3 Default Settings

The following table lists the default settings of the IPmux-24 parameters.

Table 3-2. Default Settings

Parameter Default Value Menu Path Manual Section

Accept Frame Type All Configuration > Bridge >

Bridge Port

Configuring the Bridge

Ports

Access All Configuration > System >

Management >

Management access >

User access

Defining Management

Access Permissions

Accounting Port – Configuration > System >

Management >

Management Access >

RADIUS Parameters

Configuring RADIUS

Client

Admin status Down Configuration > System >

OAM > CFM >

Maintenance Domains >

Maintenance Associations

> MEP

Configuring

Maintenance

Endpoints

Administrative status Up Configuration > Physical

layer > ETH

Configuring Ethernet

Interfaces

Administrative status Up Configuration > Physical

layer > TDM

Configuring the E1/T1

TDM Interface

Aging time 300 sec Configuration > Bridge Configuring the

Ethernet Bridge

Authentication Port – Configuration > System >

Management >

Management Access >

RADIUS Parameters

Configuring RADIUS

Client

Auto negotiation Disable for fiber optic

interface

Enable for copper

interface

Configuration > Physical

layer > ETH


Interfaces

Baud rate 115200 bps Configuration > System >

Control port

Configuring Control

Port Parameters

Broadcast Mode Disable Configuration > System >

Date and Time

Setting the Date and

Time

Burst size 12 bytes Configuration > QoS >

Rate Limitation > Ingress

Configuring Ingress

Rate Limitation


3-4 Default Settings IPmux-24 Ver. 3.5


CCI Enabled True Configuration > System >

OAM > CFM >



> MEP

Configuring

Maintenance

Endpoints

Connection status Enable Configuration >

Connection > Bundle

connection

Configuring Bundle

Connections

Contact Person name of contact person Configuration > System >

Management > Device

info

Assigning a Name to

the Unit and Its

Location

Continuity Verification

Mode

CC Based Configuration > System >

OAM > CFM >



> MEP

Configuring

Maintenance

Endpoints

Default CCM/LTM Priority 0 Configuration > System >

OAM > CFM >



> MEP

Configuring

Maintenance

Endpoints

Default gateway – Configuration > System >

Management > Host IP

Managing IP

Parameters of the

Host

Default next hop – Configuration >

Connection > PW host IP

Configuring Bundle

Connections

Default Priority Tag 0 Configuration > Bridge >

Bridge Port


Ports

Descriptor Number – Configuration > Physical

layer > Link OAM > Link

OAM Descriptors

Configuring Link OAM

Descriptors

Descriptor Number – Configuration>Physical

layer>Link OAM>Link OAM

Parameters

Assigning Link OAM

Descriptor to an

Ethernet Port

Destination Address Type Multicast Configuration > System >

OAM > CFM >



> MEP

Configuring

Maintenance

Endpoints

Destination bundle 1 Configuration >

Connection > Bundle

connection

Configuring Bundle

Connections




Destination IP address – Configuration >

Connection > Bundle

connection

Configuring Bundle

Connections

Destination MAC Address 01-80-C2-00-00-33 Configuration > System >

OAM > CFM >



> MEP

Configuring

Maintenance

Endpoints

Device Logging Status Disable Configuration > System >

Syslog

Configuring Syslog

Parameters

Device UDP Port 514 Configuration > System >

Syslog

Configuring Syslog

Parameters

DHCP Enable Configuration > System >


Managing IP

Parameters of the

Host

Ethernet network type WAN Configuration > Physical

layer > TDM


TDM Interface

Facility Local 1 Configuration > System >

Syslog

Configuring Syslog

Parameters

Fall back clock Adaptive Configuration > System >

System clock

Configuring the

System Clock

Fall back source Channel 1 Configuration > System >

System clock

Configuring the

System Clock

Far end type E1 or T1 (ESF) Configuration >

Connection > Bundle

connection

Configuring Bundle

Connections

Forwarding Mode Filter Configuration > Bridge Configuring the

Ethernet Bridge

Host Tagging Untagged Configuration > System >

Management > Host IP >

Encapsulation

Configuring the Host

Encapsulation

Host Tagging Untagged Configuration >


> PW encapsulation

Configuring Bundle

Connections

Idle code 7E Configuration > Physical

layer > TDM


TDM Interface

Ingress Filtering Enable Configuration > Bridge >

Bridge Port


Ports

IP address – Configuration > System >


Managing IP

Parameters of the

Host




IP address – Configuration >


Configuring Bundle

Connections

IP mask 0.0.0.0 Configuration > System >


Managing IP

Parameters of the

Host

IP mask 0.0.0.0 Configuration >


Configuring Bundle

Connections

IP TOS 0 Configuration >

Connection > Bundle

connection

Configuring Bundle

Connections

Jitter buffer 3.0 Configuration >

Connection > Bundle

connection

Configuring Bundle

Connections

Keep Alive Drops To Fall 3 Configuration > System >

Protection

Configuring the Ring

Protection

Keep Alive Tx Time 13 Configuration > System >

Protection


Protection

LAG Enable Disabled Configuration > Physical

layer > LAG

Configuring the LAG

Limit Packet Type All Configuration > QoS >


Configuring Ingress

Rate Limitation

Line bildout -7.5 Configuration > Physical

layer > TDM (T1)

Configuring the T1

TDM Interface

Line code B8ZS Configuration > Physical

layer > TDM (T1)

Configuring the T1

TDM Interface

Line interface DSU Configuration > Physical

layer > TDM


TDM Interface

Line length 0–133 feet Configuration > Physical

layer > TDM (T1)

Configuring the T1

TDM Interface

Line type ESF Configuration > Physical

layer > TDM (T1)

Configuring the T1

TDM Interface

Line type Framed G.704 Configuration > Physical

layer > TDM (E1)

Configuring the E1

TDM Interface

L2CP Handling Tunnel Configuration > Bridge >

Bridge Port > L2CP

Handling

Configuring L2CP

Handling

MPLS Egress Label Configuration >

Connection > Bundle

connection

Configuring Bundle

Connections




Number of Retries 1 Configuration > System >

Management >

Management Access >

RADIUS Parameters

Configuring RADIUS

Client

Mark signaling code D Configuration > Physical

layer > TDM


TDM Interface

Master clock Rx clock Configuration > System >

System clock

Configuring the

System Clock

Master source Channel 1 Configuration > System >

System clock

Configuring the

System Clock

Max Capability Advertised 100baseT Full Duplex Configuration > Physical

layer > ETH


Interfaces

Mcast VLAN ID 4002 Configuration > System >

Protection


Protection

Network ETH1 Port default priority Configuration > QoS >

Priority > Classification

Configuring Quality of

Service (QoS)

Network/User ETH2 Port default priority Configuration > QoS >



Service (QoS)

Next hop – Configuration >

Connection > Bundle

connection

Configuring Bundle

Connections

OAM connectivity Enable Configuration >

Connection > Bundle

connection

Configuring Bundle

Connections

OAM Mode – Configuration > Physical


OAM Descriptors


Descriptors

OAM Rate Limit – Configuration > Physical


OAM Descriptors


Descriptors

OAM Status Disable Configuration>Physical

layer>Link OAM>Link OAM

Parameters

Assigning Link OAM

Descriptor to an

Ethernet Port

OOS code FF Configuration > Physical

layer > TDM


TDM Interface

OOS mode Tx OOS Configuration >

Connection > Bundle

connection

Configuring Bundle

Connections

OOS signaling Space Configuration > Physical

layer > TDM


TDM Interface




Payload format V2 Configuration >

Connection > Bundle

connection

Configuring Bundle

Connections

Permission Full control Configuration > System >

Management >

Management access >

User access

Defining Management

Access Permissions

Poll Interval Configuration > System >

Date and Time


Time

Port VID 1 Configuration > Bridge >

Bridge Port


Ports

Primary Bundle 1 Configuration > System >

Protection > Bundle

Protection

Configuring Bundle

Protection

Primary VID 1 Configuration > System >

OAM > CFM >



> MEP

Configuring

Maintenance

Endpoints

Primary PORTID Network-ETH1 Configuration > System >

OAM > CFM >



> MEP

Configuring

Maintenance

Endpoints

Protection mode Dual Homing Configuration > System >

Protection > Dual Homing

Configuring Dual

Homing

PSN type UDP/IP Configuration >

Connection

Configuring Bundle

Connections

PTP VLAN ID 4001 Configuration > System >

Protection


Protection

PW type TDMoIP CE Configuration >

Connection

Configuring Bundle

Connections

RADIUS Enable Remote Configuration > System >

Management >

Management Access

Controlling

Management Access

Rate Limitation No Limit Configuration > QoS >

Rate Limitation > Egress

Configuring Egress

Rate Limitation

Rate Limitation No Limit Configuration > QoS >


Configuring Ingress

Rate Limitation

Read Community public Configuration > System >


Managing IP

Parameters of the

Host




Recovery Revertive Configuration > System >

Protection > Bundle

Protection

Configuring Bundle

Protection

Redundancy Type 1+1 Configuration > System >

Protection > Bundle

Protection

Configuring Bundle

Protection

Redundancy Function None Configuration >

Connection

Configuring Bundle

Connections

Restoration time Fast (1 Second) Configuration > Physical

layer > TDM (T1)

Configuring the T1

TDM Interface

Revertive mode Not Revertive Configuration > System >


Configuring Dual

Homing

Ring Administrative

Status

Down Configuration > System >

Protection


Protection

Rx sensitivity Short haul Configuration > Physical

layer > TDM


TDM Interface

Secondary Bundle 1 Configuration > System >

Protection > Bundle

Protection

Configuring Bundle

Protection

Server IP Address 0.0.0.0 Configuration > System >

Management >

Management Access >

RADIUS Parameters

Configuring RADIUS

Client

Server IP Address 0.0.0.0 Configuration > System >

Syslog

Configuring Syslog

Parameters

Server UDP Port 514 Configuration > System >

Syslog

Configuring Syslog

Parameters

Severity Level Minor Configuration > System >

Syslog

Configuring Syslog

Parameters

Shared Secret – Configuration > System >

Management >

Management Access >

RADIUS Parameters

Configuring RADIUS

Client

SNMP access Enable Configuration > System >

Management >

Management Access

Controlling

Management Access

SNMPv3 Disable Configuration > System >

Management

Enabling SNMPv3

Send upon fail OOS code Configuration > Physical

layer > TDM


TDM Interface

Sensitive Data Configuration >

Connection > Bundle

Configuring Bundle

Connections




connection

Set Active Port None Configuration > System >


Configuring Dual

Homing

Shut Down Duration

Upon Flip

0 Configuration > System >


Configuring Dual

Homing

Signaling mode None Configuration > Physical

layer > TDM (T1)

Configuring the T1

TDM Interface

Source clock quality Other/unknown Configuration > Physical

layer > TDM


TDM Interface

Source IP Address PW IP Configuration >

Connection > Bundle

connection

Configuring Bundle

Connections

Space signaling code 1 Configuration > Physical

layer > TDM


TDM Interface

Speed & Duplex 10baseT Half Duplex Configuration > Physical

layer > ETH


Interfaces

Standard OAM EtherType 8902 Configuration>System>

OAM>CFM

Adding and

Configuring

Maintenance Domains

Standard OAM MAC

Address

01-80-C2-00-00-30 Configuration>System>

OAM>CFM

Adding and

Configuring

Maintenance Domains

System Location the location of this device Configuration > System >

Management > Device

info

Assigning a Name to

the Unit and Its

Location

System Name IPmux-24 Configuration > System >

Management > Device

info

Assigning a Name to

the Unit and Its

Location

Tag Handling None Configuration > Bridge >

Bridge Port


Ports

Telnet/SSH access Enable Configuration > System >

Management >

Management Access

Controlling

Management Access

TDM bytes in frame 1 Configuration >

Connection > Bundle

connection

Configuring Bundle

Connections

TDM PW Port default priority Configuration > QoS >



Service (QoS)

Timeout 1 Configuration > System >

Management >

Management Access >

RADIUS Parameters

Configuring RADIUS

Client


IPmux-24 Ver. 3.5 Configuration and Management Alternatives 3-11


Trail mode Termination Configuration > Physical

layer > TDM


TDM Interface

Transmit clock source Adaptive Configuration > Physical

layer > TDM


TDM Interface

Trap Community SNMP_trap Configuration > System >


Managing IP

Parameters of the

Host

User ETH3 Port default priority Configuration > QoS >



Service (QoS)

User name su Configuration > System >

Management >

Management access >

User access

Defining Management

Access Permissions

UTC Offset +2 Configuration > System >

Date and Time


Time

VLAN Mode Unaware Configuration > Bridge Configuring the

Ethernet Bridge

VLAN tagging Disable Configuration >

Connection > Bundle

connection

Configuring Bundle

Connections

Wait to Restore 0 Configuration > System >


Configuring Dual

Homing

Web access Enable Configuration > System >

Management >

Management Access

Controlling

Management Access

Write Community private Configuration > System >


Managing IP

Parameters of the

Host

WTR 10 Configuration > System >

Protection > Bundle

Protection

Configuring Bundle

Protection

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, RAD’s SNMP-based management system with a graphical user interface. See RADview SC/TDMoIP User's Manual for details


3-12 Configuration and Management Alternatives IPmux-24 Ver. 3.5

• 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.



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.



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.




To enter as a technician:

1. Enter tech for user name.


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.

Nothing 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).

• 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 R – move to the right

^D – scroll down ^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:



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™



• 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 browser’s 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.



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.

Main Menu System

Router

Configuration

Host IP

Management

User Acce ss

InventoryConfigurationMonitoringDiagnosticsUtilities

Management System clock Control port Syslog Date/Time ProtectionOAMFactory default

Static Route TableDefault Gateway

SystemPhysica l LayerConnectionBridgeQoSRouter

IP address IP mask DHCP Read Community Write Community Trap Community Encapsulation

Device infoSNMPv3Host IPManager listSNMP Engine IDSNMPv3 SettingsManagement accessAlarm trap mask User name

Per mission Access 'su' password New password Confirmation

System nameSystem locationContact person

Host Tagging Host VLAN IDHost VLAN Priority

Manager List

Management Access

Alarm Trap Mask

IP addressTrap mask

User Access Telnet/SSH Access Web AccessSNMP Access RADIUS AuthenticationRADIUS Parameters

Alarm ID Trap status

Device Info

Encapsula tion

Server IP AddressShared SecretNumber of RetriesTimeoutAuthentication PortAccounting Port

RADIUS Parameters

UsersTargets & NotifySNMPv1/v3 MappingSNMPv3 Factory DefaultsSummary Target TableSummary User Table

Secur ity NameAuthentication ProtocolAuthentication PasswordPrivacy ProtocolPrivacy Password

Target ParamsTarget AddressNotifyTrap

NameMessage Processing ModelSecurity ModelSecurity NameSecurity Level

NameIP Addr essParams NameAddress MaskTag List

NameTag

Trap NameNotify Name

SNMPv3 Settings

Users

Targets and Notify

Target Para ms

Target Address

Notify

Trap

Figure 3-7. Main Menu > Configuration > System > Management



Main Menu SystemConfiguration

Syslog

System Clock

Control PortInventoryConfigurationMonitoringDiagnosticsUtilities

Management System clock Control port Syslog Date/Time ProtectionOAMFactory default

SystemPhysica l LayerConnectionBridgeQoS

Device Logging StatusDevice UDP PortFacility Severity Level Server Parameters

Mase r clockMaster sourceFall back clock Fall back source

Baud Rate

Date/Time

Protection

RFER (Proprietary)

Ring Port Parameters

ERP (G.8032)

Dual Homing

NTP Servers

Factory Default

CFM

Sys tem DateSys tem TimeBroadcast ModePoll IntervalUTC OffsetNTP Servers

Dual HomingBundle ProtectionRFER (Proprietary)ERP (G.8032)

Ring Administrative StatusKeep Alive Tx TimeKeep Alive Drops To FallPTP VLAN ID Mcast VLAN ID

Eas t mepidEas t mdEas t maWest mepidWest mdWest ma

Ring NumberAdmin StatusBridge NumberEast Port NumberWest Port NumberRPL PortWTRGuard Timer Holdoff TimerR-APS VidR-APS Me lTra ffic VLANsForce SF CommandRing Port Parameters

Protection modeRevertive modeWait to RestoreShut Down Duration Upon FlipSet Active Port

NTP ServerAdmin StatusUDP PortStratum

FullExcept management

See Figure 3-9

Bundle ProtectionPrimary Bundle IDSecondary Bundle IDRedundancy TypeRecoveryWTR

Figure 3-8. Configuration > System

SystemManagement System clock Control port Date/Time ProtectionOAMFactory default

CFM CFM Maintenance DomainsMaintenance Associat ions

MEP ServicesCFM Maintenance DomainsStandard OAM MAC Address Standard OAM EtherType

Protocol TypeMD Name Format MD NameMD LevelMaintenance Associations

MA Name FormatMA Name CCM Interval MEP

Admin Status Primary VIDPrimary PORTID Destination Address TypeRemote MEP IDs Destination MAC AddressDefault CCM/LTM P riorityCCI Enabled Continuity Verification Mode Services

Performance Monitoring Prior ityDelay Object iveDelay Variation Objective

Event ReportFrame Loss Ratio Frame Above Delay Frame Above Delay Variation Unavailability Ratio

Figure 3-9. Configuration > System > OAM



Configuration Physical Layer TDM (E1)

Or

TDM (T1)

ETH Configuration

LAG

Link OAM Link OAM Descriptors

Link OAM Parameters

SystemPhysical layerConnectionBridgeQoS

TDM interface typeTDM ETHLAGLink OAMExternal clock interface

Administrative statusTransmit clock sourceSource clock qualityTrail modeLine typeLine interfaceIdle code Send upon failOOS codeOOS signalingMark signaling codeSpace signaling codeEthernet network type

Administrative

Send upon failOOS codeSignaling modeOOS signalingMark signaling codeSpace signaling codeEthernet network type

statusTransmit clock sourceSource clock qualityRx sensitivityTrail modeLine typeLine interfaceLine length or Line BildOutRestoration timeIdle code

Administrative statusAuto negotiationMax capability advertisedSpeed & Duplex

LAG EnableAggregator

Link OAM DescriptorsLink OAM Parameters

Descriptor NumberOAM Mode OAM Rate Limit

OAM Status Descriptor Number

Figure 3-10. Configuration > Physical Layer

Connection PW Host IP PW EncapsulationPW Host IPBundle IDConnection modePSN typeDS0 bundleBundle connection

IP addressIP maskPW encapsulation

Host TaggingHost VLAN IDHost VLAN Priority

ConfigurationSystemPhysical layerConnectionBridgeQoS

Figure 3-11. Configuration > Connection > PW Host IP

Connection

Bundle Connection

PW Host IPBundle IDConnection modePSN typeDS0 bundleBundle connection

Destination IP AddressBundle Name Next Hop IP TOS Connection Status Destination Bundle Redundancy FunctionTDM Bytes In FramePayload Format Far End Type OAM ConnectivityJitter BufferSensitive OOS Mode VLAN Tagging Source IP Address


Figure 3-12. Configuration > Connection (TDMoIP CE Connection and UDP/IP PSN)



Connection

Bundle Connection


Destination IP AddressBundle Name MPLS Egress Label Connection Status Destination BundleRedundancy Function Next Hop Type Next Hop IP Address TDM Bytes In FramePayload FormatFar End TypeOAM Connectivity Jitter Buffer Sensitive OOS Mode VLAN Tagging


Figure 3-13. Configuration > Connection (TDMoIP CE Connection and MPLS/ETH PSN)

Connection

Bundle Connection


Destination IP Address Bundle Name Connection Status Destination Bundle Redundancy FunctionNext Hop Type Next Hop MAC AddressTDM Bytes In FrameFar End Type Jitter BufferSensitive OOS ModeVLAN Tagging Source IP Address


Figure 3-14. Configuration > Connection (TDMoIP CE Connection and MAC/ETH PSN)

ConnectionBundle Connection


Destination IP AddressBundle Name Next Hop IP TOS Connection Status Destination Bundle Redundancy Function TDM Frames In Packet Payload Format OAM ConnectivityJitter Buffer SensitiveOOS ModeVLAN Tagging Source IP Address


Figure 3-15. Configuration > Connection (CESoPSN Connection and UDP/IP PSN)

Connection

Bundle Connection


Destination IP Address MPLS Egress Label Connection Status Destination Bundle Redundancy Function Next Hop Type Next Hop IP Address TDM Frames In Packet Payload FormatOAM Connectivity Jitter Buffer Sensitive OOS Mode VLAN Tagging Source IP Address


Figure 3-16. Configuration > Connection (CESoPSN Connection and MPLS/ETH PSN)



Connection

Bundle 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 SensitiveOOS Mode VLAN TaggingSource IP Address


Figure 3-17. Configuration > Connection (CESoPSN Connection and MAC/ETH PSN)

Connection

Bundle Connection

PWHost IPBundle IDConnection modePSN typeDS0 bundleBundle connection

Destination IP Address Bundle Name Next Hop IP TOS Connection Status Destination Bundle TDM Bytes In Packet Payload Format OAM ConnectivityJitter Buffer Sensitive OOS Mode VLAN TaggingSource IP Address


Figure 3-18. Configuration > Connection (SAToP Connection and UDP/IP PSN)

Connection

Bundle Connection


Destination IP Address Bundle NameMPLS Egress Label Connection Status Destination Bundle Redundancy Function Next Hop Type Next Hop IP AddressTDM Bytes In Packet Payload FormatOAM Connectivity Jitter BufferSensitive OOS Mode VLAN TaggingSource IP Address


Figure 3-19. Configuration > Connection (SAToP Connection and MPLS/ETH PSN)

Connection

Bundle Connection


Destination IP Address Bundle Name Connection Status Destination Bundle Redundancy Function Next Hop Type Next Hop MAC Address TDM Bytes In Packet Jitter BufferSensitiveOOS Mode VLAN Tagging Source IP Address


Figure 3-20. Configuration > Connection (SAToP Connection and MAC/ETH PSN)



Connection Bundle Connection


Destination IP Address Bundle Name Next Hop IP TOS Connection Status Redundancy Function Payload Format OAM Connectivity VLAN Tagging Source IP Address


Figure 3-21. Configuration > Connection (HDLC Connection and UDP/IP PSN)



Destination IP Address Bundle NameMPLS Egress Label Connection Status Destination Bundle Redundancy Function Next Hop Type Next Hop IP Address Payload Format OAM ConnectivityVLAN Tagging Source IP Address


Figure 3-22. Configuration > Connection (HDLC Connection and MPLS/ETH PSN)



Destination IP AddressBundle NameConnection StatusDestination 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)


Egress Tagged PortsEgress Untagged Ports

Ingress FilteringAccept Frame TypePort VID

Tag Handling

/Stacking VIDDefault Priority Tag

VLAN ModeForwarding ModeAging TimeStatic MAC TableErase MAC TableBridge PortVLAN Membership

BridgeBridge Port

(User)

Figure 3-24. Configuration > Bridge


PriorityRate Limitation

ClassificationMapping

Network ETH1Network/User ETH2User ETH3TDM PW

EgressIngress

Rate Limitation

Rate LimitationBurst SizeLimit Packet Type

QoS Priority

Classification

Rate Limitation Egress

Ingress

Figure 3-25. Configuration > QoS


3-24 Turning IPmux-24 Off IPmux-24 Ver. 3.5

Monitoring StatisticsOAM

StatusPhysical Ports

Protection

SFP

Event Log

Managers

StatisticsStatusEvent logManagers

TDM physical layerConnectionBridgeOAM

15 Min. Counters24 Hours Counters Service Counters

Diagnostics loopback Physical portsLAG ConnectionOAM (802.1ag)System ClockProtection

ETH physical layer SFP

Ring Dual Homing

Link status

Read log fileClear log file

Connected Managers

Figure 3-26. Monitoring

DiagnosticsPing

Trace Route

Loopback

Self Test Results

PingTrace routeLoopbackSelf test results

InterfaceDestination IP addressVLAN tagging

Number of frames to sendPing Send

VLAN IDVLAN priority

Destination IP addressVLAN tagging VLAN IDVLAN priorityTrace route send

Loopback stateInband loop detection (T1 only)

Framer testBridge test

Figure 3-27. Diagnostics

Utilities File Utilities Download/Upload Using FTPFile UtilitiesReset

Download/upload using FTP File name Command Server IP Retry timeoutTotal 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.

IPmux-24 Ver. 3.5 Configuring for Management 4-1

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.

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 unit’s 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.

Note

Chapter 4 Configuration Installation and Operation Manual

4-2 Configuring for Management IPmux-24 Ver. 3.5

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 ... (0.0.0.0) 3. DHCP (Enable) 4. DHCP Status > 5. Read Community ... (public) 6. Write Community ... (private) 7. Trap Community ... (SNMP_trap) 8. Encapsulation > > Please select item <1 to 8> ESC-prev.menu; !-main menu; &-exit 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)

When the IP address lease is going to expire, DHCP client automatically requests lease extension.

Note

Installation and Operation Manual Chapter 4 Configuration


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 (1–4094).

If the host tagging is enabled, select Host VLAN priority to specify priority of the host VLAN (0–7).

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 (Tagged) 2. Host VLAN ID [1 - 4094] ... (300) 3. Host VLAN Priority [0 - 7] ... (7) > ESC-prev.menu; !-main menu; &-exit 1 M/ 1 C

Figure 4-2. Encapsulation Menu

Note



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 ... (IPmux-24) 2. System Location ... (the location of this device) 3. Contact Person ... (name of contact person) > Please select item <1 to 3> ESC-prev.menu; !-main menu; &-exit 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.



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 IP Address Trap mask

1 172.18.159.35 Disable

1. Change cell ... (Disable) 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 List Manager ID (1) 1. IP Address ... (0.0.0.0) 2. Trap Mask ... (Disable) > ESC-prev.menu; !-main menu; &-exit 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.



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.)



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.

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.

Note



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)



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)



Configuration>System>Management> SNMPv3 Settings> Target & Notify > Target Params

1. Name ... () 2. Message Processing Model > () 3. Security Model > () 4. Security Name ... () 5. 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. Name ... () 2. IP Address ... () 3. Params Name ... () 4. Tag List ... () > ESC-prev.menu; !-main menu; &-exit 1 M/ 1 C

Figure 4-11. Target Address Menu



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. Community Index ... () 2. Community Name ... () 3. Security Name ... () 4. Transport Tag ... () > ESC-prev.menu; !-main menu; &-exit 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.



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 user’s access rights (full control or read-only).

Select Access, and specify the user’s access methods (ASCII terminal, Telnet, Web browser, Telnet and Web browser, or all of them).

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. User name ... (su) 2. Permission > (Full Control) 3. Access > (All) 4. 'su' password ... () 5. New password ... () 6. Confirmation ... () > Please select item <1 to 6> ESC-prev.menu; !-main menu; &-exit 1 M/ 1 C

Figure 4-13. User Access Menu

Note



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 SSL-enabled 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

Network Manager(s) not

Defined

SNMP Access

Enable Anybody Anybody

Disable Nobody Nobody

Managers Only Only defined network

managers

Nobody

Telnet Access

Enable/Enable Secure Anybody Anybody


Managers Only/

Managers Only Secure

Only defined network

managers

Nobody

Web Access

Enable/Enable Secure Anybody Anybody


Managers Only/

Managers Only Secure

Only defined network

managers

Anybody



Configuration>System>Management>Management Access

1. User Access > 2. TELNET/SSH access > (Enable) 3. WEB access > (Enable) 4. SNMP access > (Disable) 5. Access Policy > > ESC-prev.menu; !-main menu; &-exit 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

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

Note



Number of retries (The number of retries to be made when sending request to the RADIUS server): 1–5

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.): 1–60

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 (8) Parity > (None) Stop bits (1) Flow control > (None) 1. Baud rate (bps) > (115200) > ESC-prev.menu; !-main menu; &-exit 1 M/ 1 C

Figure 4-15. Control Port Menu


4-16 Configuring for Operation IPmux-24 Ver. 3.5

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 Description Possible Values

Master clock Master clock type 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


IPmux-24 Ver. 3.5 Configuring for Operation 4-17


Fallback clock Fallback clock type 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

If the configured fallback clock source fails, the internal timing is used as the fallback clock source instead.

Configuration>System>System clock

1. Master clock > (Rx Clock) 2. Master source > (Channel 1) 3. Fall back clock > (Adaptive) 4. Fall back source > (Channel 1) > Please select item <1 to 4> S - save ESC-prev.menu; !-main menu; &-exit 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).

Note



Configuration>Physical layer

1. TDM interface type > (E1) 2. TDM > 3. ETH > 4. LAG > 5. External clock interface (Balanced) > Please select item <1 to 4> ESC-prev.menu; !-main menu; &-exit 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.

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.

Note



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. Ring Administrative Status (Down) 2. Keep Alive Tx Time[Msec][2 - 100] ... (13) 3. Keep Alive Drops To Fall[1 - 10] ... (3) 4. PTP VLAN ID ... (4001) 5. Mcast VLAN ID ... (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


Ring Administrative

Status

Administrative status of the redundancy

ring

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

2–100 msec

Default: 13

Keep Alive Drops To

Fall

Number of keep-alive PtP messages not

received from adjacent ring member,

after which IPmux-24 declares link failure

1–10

Default: 3

PTP VLAN ID VLAN ID for point-to-point messages.

This VLAN ID must not be used by other

services in the network.

1–4094

Default: 4001

Mcast VLAN ID VLAN ID for multicast messages. This

VLAN ID must not be used by other

services in the network.

1–4094

Default: 4002

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,



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 … (1) 2. Admin Status … (Enabled) 3. Bridge Number … (1) 4. East Port Number … (1) 5. West Port Number … (2) 6. RPL Port … (East) 7. WTR (min) … (5) 8. Guard Timer (msec) … (500) 9. Holdoff Timer (msec) … (0) 10.R-APS Vid … (5) 11.R-APS Mel … (3) 12.Traffic VLANs … (1,3,100,101,4000) 13.Force SF Command … (SF East) 14.Port Specific Parameters > > 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


Ring Number Administrative status of the redundancy

ring

1




Admin Status Administrative status of the ring node Enable – The node is operational

Disable – The node is not operational

Default: Down

Bridge Number Number of the node bridge 1

East Port Number Configures one of the Ethenet ports to

be the East port of the node

1, 2

West Port Number Configures one of the Ethenet ports to

be the West port of the node

1, 2

RPL Port Defines the East or West port of the

node to be the RPL Owner

East, West, N/A

Default: N/A

WTR Timer Period of time used by RPL Owner to

verify that the ring has stabilized before

blocking the RPL after signal recovery

5–12 min

Default: 5

Guard Timer Period of time during which all received

R-APS messages are ignored by the ERP

mechanism. This prevents the ring nodes

from receiving outdated R-APS messages

circulating the network.

10 msec–2 sec

Default: 500 msec

Holdoff Timer Period of time during which the

underlying Ethernet layer attempts to

filter out intermittent link faults before

reporting them to the ERP mechanism

0–10000 msec

Default: 0

R-APS VID VLAN ID fro R-APS messages 0–4095

Default: 0

R-APS MEL Maintenance Entity Group Level

providing a communication channel for

ring automatic protection switching

(R-APS) information

0–7

Default: 0

Traffic VLANs 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.

0–4095




Force SF Command 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.

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 … (1) 2. East md (maintenance domain – level) … (2) 3. East ma (maintenance association – Vlan Id) … (3) 4. West mepid … (3) 5. West md (maintenance domain – level) … (4) 6. West ma (maintenance association – Vlan Id) … (5) > Please select item <1 to 6> F- Forward Ring; B-Backward Ring; ESC-prev.menu; !-main menu; &-exit 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.



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).

• 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 ... (Enabled) 2. Aggregator > > Please select item <1 to 2> ESC-prev.menu; !-main menu; &-exit 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).

Note



Configuration>System>Protection>Dual Homing Group ID (1) Primary Port > (Network-ETH1) Secondary Port > (Network/User-ETH2)

1. Protection mode (Dual Homing) 2. Revertive mode (Not Revertive) 3. Wait to Restore (sec)[0 - 720] ... (0) 4. Shut Down Duration Upon Flip[0 - 30] ... (0) 5. Set Active Port > (None) > Please select item <1 to 5> ESC-prev.menu; !-main menu; &-exit 1 M/ 1 C

Figure 4-22. Dual Homing Menu, Dual Homing is Enabled

Table 4-5. Dual Homing Parameters

Name Description Possible Values

Revertive mode Port recovery mode 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

restoration and using the link for

the data transfer

0–720 sec

Default – 0

Shut Down Duration

Upon Flip

Period of time during which the

failed link suspends its

transmission in order to inform

the remote device of the link

failure

0–30 sec

Default – 0

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



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.

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


1. Primary Bundle ID[1 - 127] ... (1) 2. Secondary Bundle ID[1 - 127] ... (1) 3. Redundancy Type > (1+1)

4. Recovery > (Non Revertive)

5. WTR[0 - 99] ... (10) > Please select item <1 to 5> ESC-prev.menu; !-main menu; &-exit 1 M/ 1 C

Figure 4-24. Bundle Protection Menu, Add Mode

Note



Table 4-6. Bundle Protection Parameters


Primary Bundle Active (primary) bundle. Make

sure that the same bundle is

configured as primary via Bundle

Connection menu.

Whole bundle range supported by IPmux-24

Default – 1

Secondary Bundle Redundant (secondary) bundle.

Make sure that the same bundle

is configured as secondary via

Bundle Connection menu.

Whole bundle range supported by IPmux-24

Default – 1

Redundancy Type Bundle protection 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.

0–99 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.




Primary Secondary Redundancy Type Recovery WTR 1 2 1:1 Revertive 2 3 4 1+1 A-Add;R-Remove;C-Clear ESC-prev.menu; !-main menu; &-exit 1 M/ 1 C

Figure 4-25. Bundle Protection Menu, 3–4 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.



Configuration>Application>OAM>CFM 1. Maintenance Domains > 2. Standard OAM MAC Address ... (01-80-C2-00-00-30) 3. Standard OAM EtherType[0 - ffff] ...(8902) > Please select item <1 to 3> ESC-prev.menu; !-main menu; &-exit 1 M/2 C

Figure 4-26. OAM CFM Menu

Table 4-7. OAM CFM Parameters


Standard OAM

MAC Address

Specifies the MAC Address for OAM CFM

messages

Multicast MAC address

Default – 01-80-C2-00-00-30

Standard OAM

EtherType

Specifies the EtherType for OAM CFM

messages

0–ffff

Default – 8902

2. Select Maintenance Domains to continue configuration.

The Maintenance Domain (MD) menu appears. If you haven’t 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) 1. Protocol Type (Standard) 2. MD Name Format > (String) 3. MD Name ... (DEFAULT) 4. MD Level[0-7] ... (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.



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) 1. Protocol Type (Standard) 2. MD Name Format > (String) 3. MD Name ... (DEFAULT) 4. MD Level ... (3) 5. Maintenance Associations > 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


MD ID The maintenance domain’s identification 1–16

Protocol Type Specifies whether to use the RAD proprietary OAM

mechanism or the standard OAM mechanism 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

0–7

Default: 3



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 haven’t 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 ... (1) MA ID ... (1) 1. MA Name Format > (String) 2. MA Name ... (DEFAULT) 3. CCM Interval > (1 Second) 4. MEP > 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.



...OAM>CFM>Maintenance Domains>Maintenance Associations MD ID ... (1) MA ID ... (1) 1. MA Name Format > (String) 2. MA Name ... (DEFAULT) 3. CCM Interval > (1 Second) 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


MD ID Displays the maintenance domain ID to which the

maintenance association belongs

1–16

MA ID The maintenance association’s identification 1–16

MA Name

Format

Specifies the format of the maintenance association name


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



Configuring Maintenance Endpoints

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 ... (1) MA ID ... (1) 1. MEP ID[1 – 8191] > (0) Please select item <1 to 1> ESC-prev.menu; !-main menu; &-exit 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 ... (1) MA ID ... (1) MEP ID ... (1) 1. Admin Status (Up) 2. Primary VID[1 - 4094] ... (1) 3. Primary PORTID > (Network-ETH1) 4. Destination Address Type (Multicast) 5. Remote MEP IDs > (4) Destination MAC Address ... (01-80-C2-00-00-33) 6. Default CCM/LTM Priority[0 - 7] ... (0) 7. CCI Enabled (True) 8. Continuity Verification Mode > (CC Based) 9. Services 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. Configure the MEP services as described in Configuring Maintenance Endpoint Services

Table 4-10. MEP Parameters


MD ID Displays the corresponding maintenance domain ID 1–16

MA ID Displays the corresponding maintenance association ID 1–16

MEP ID Specifies the MEP identification.

1–8191

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

1–4094

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

unit’s MEP ID must remain unique.

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

1–8191

Destination MAC

Address

Specifies the MAC address to which OAM messages are

sent.

A valid MAC address

Default – 01-80-C2-00-00-

33

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).




Default CCM/

LTM Priority

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.

0–7

Default – 0

CCI Enabled Specifies whether continuity check messages are sent

for this MEP

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) 1. Performance Monitoring (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.



IPmux-24 ...Maintenance Domains>Maintenance Associations>MEP>Services Service [1 – 3] ... (1) 1. Performance Monitoring (Enabled) 2. Priority[0-7] ... (0) 3. Delay Objective (msec)[1-1000] ... (1) 4. Delay Variation Objective (msec)[1-1000] ... (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


Service Three services are automatically created for each MEP, for

which you can configure event reporting

1–3

Performance

Monitoring

Enables/disables performance monitoring for the service. If

performance monitoring is disabled, no event reporting is

done.

Enabled

Disabled

Default – Disabled

Priority Specifies the priority of OAM messages from this service

0–7

Default – 0

Delay Objective Specifies the planned delay for the service

1–1000

Default – 1

Delay Variation

Objective

Specifies the planned delay variation for the service

1–1000

Default – 1

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).



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 > (None) > Please select item <1 to 1> ESC-prev.menu; !-main menu; &-exit 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 > (Log) 2. Rising Threshold > (1E-10) 3. Falling Threshold > (1E-10) > Please select item <1 to 3> S-Save ESC-prev.menu; !-main menu; &-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 ... (Log) 2. Rising Threshold ... (1) 3. Falling Threshold ... (1) 4. Sampling Interval (Sec) ... (1) > Please select item <1 to 4> S-Save ESC-prev.menu; !-main menu; &-exit 1 M/2 C

Figure 4-38. MEP Service Event Reporting Menu for Frames Above Delay or Frames Above Delay Variation



Table 4-12. MEP Service Event Reporting Parameters


Event Reporting

Type

Specifies the type of event reporting 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:

1–4,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

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–4,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




Sampling Interval Specifies the interval in seconds over

which the data is sampled and

compared with the rising and falling

thresholds

1–4,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 ... (1)

2. OAM Mode > (Passive)

3. OAM Loopback Rx > (Ignore)

4. OAM Rate Limit [1 – 100] ... (60)

ESC-prev. menu; !-main menu; &-exit 1 M/2 C

Figure 4-39. Ethernet Link OAM Descriptors Menu



Table 4-13. Link OAM Descriptor Parameters

Parameter Description Values

Descriptor Number Specifies the identification of the OAM

descriptor

1–511

Mode Specifies whether to initiate OAM activities or

just respond to OAM activities. Currently

IPmux-24 supports passive mode only.

Passive –IPmux-24 does not initiate

OAM activities, but responds to them,

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

Process–IPmux-24 processes OAM

loopback messages

Default – Ignore

OAM Rate Limit Specifies how many OAM frames can be sent

in one second

1–100

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)

1. OAM Status > (Disable)

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

Figure 4-40. Ethernet Link OAM Parameters Menu

Table 4-14. Link OAM Parameters


OAM Status Specifies if OAM is enabled or disabled for

the port. You must associate a descriptor to

the port before you can enable OAM.

Enable – OAM is enabled

Disable – OAM is disabled

Default – Disable




Descriptor Number Specifies the OAM descriptor to use for the

port

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


Administrative Status Administrative status of E1 interface 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




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

0–ff

Default – 7E

Send Upon Fail Notification sent to the E1 side if

Ethernet link fails

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

0–ff

Default – FF




OOS signaling 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.

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.

0–f

Default – D

Space Signaling Code OOS signaling code sent when the

Space OOS signaling is selected.

Relevant for the framed MF or framed

MF CRC4 line types only.

0–f

Default – 1

Ethernet Network Type Type of the Ethernet network which is

used for the pseudowire connection.

Different network types are

characterized by different packet delay

variation models. This parameter is

relevant only when the adaptive clock

mode is selected.

WAN – Layer 3 network

LAN – Layer 2 network

Default – WAN

Configuration>Physical layer>TDM (E1) Channel ID (1) Restoration time >(CCITT) Signaling mode (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 (LTU) 7. Idle code[0 - ff] ... (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



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 CBL-RJ45/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


Administrative Status Administrative status of T1 interface 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




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

Short haul: -10 dB

Long haul: -32 dB

Default – Short haul

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 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

IPmux-24 T1 port connector and the

network access point (DSU mode only)

0–133 ft

133–266 ft

266–399 ft

399–533 ft

533–655 ft

Default: 0–133




Line buildOut Tx gain level relative to T1 output

transmit level (CSU mode only)

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

to normal operation after sync loss

TR-6211 (10 seconds)

Fast (1 second)

Default: Fast (1 second)

Idle Code Code transmitted to fill unused

timeslots in the T1 frames

0–ff

Default – 7E

Send Upon Fail Notification sent to the T1 side if

Ethernet link fails

OOS Code – Out-of-service code

AIS – Alarm indication signal

Default – OOS code

OOS code Code to be sent to the T1 side if

Ethernet link fails

0–ff

Default – FF

Signaling mode T1 signaling mode None

Robbed Bit

Default – None

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

0–f (ESF framing)

0–3 (SF framing)

Default – 0D (ESF), 01 (SF)

Space Signaling Code OOS signaling code sent when the

Space OOS signaling is selected.

0–f (ESF framing)

0–3 (SF framing)

Default – 01




Ethernet Network Type Type of the Ethernet network which is

used for the pseudowire connection.

Different network types are

characterized by different packet delay

variation models. This parameter is

relevant only when the adaptive clock

mode is selected.

WAN – Layer 3 network

LAN – Layer 2 network

Default – WAN

Configuration>Physical layer>TDM (T1) Channel ID (1) 1. Administrative status (Up) 2. Transmit clock source >(Adaptive) 3. Source clock quality >(Other/unknown) 4. Rx Sensitivity (Short haul) 5. Trail Mode (Termination) 6. Line type >(ESF) 7. Line code >(B8ZS) 8. Line interface >(DSU) 9. Line length (feet) >(0-133) 10. Restoration time >(TR-621 (10 seconds)) 11. Idle Code[0 - ff] ... (7E) 12. Send upon fail (OOS Code) 13. OOS code[0 - ff] ... (FF) 14. Signaling mode (Robbed Bit) 15. OOS signaling > (Space) 16.Mark signaling code[0 - f] ... (D) 17.Space signaling code[0 - f] ... (1) 18.Ethernet network type > (Wan) > Please select item <1 to 18> ESC-prev.menu; !-main menu; &-exit 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).



Table 4-17. Ethernet Interface Parameters


Administrative Status Administrative status of Ethernet

interface

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 half-duplex mode. In order to avoid this, disable autonegotiation and configure the ports manually. Half-duplex 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.



Configuration>Physical layer>ETH Channel > (User ETH3) Speed & Duplex > (1000baseX Full Duplex) 1. Administrative status (Up) 2. Auto negotiation (Disable) 3. Flow control (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.

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.)

Next hop IP address cannot be the same as default gateway IP address.

Note

Note



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 IP Mask Next Hop 30.30.30.30 255.255.255.0 10.10.10.1 30.30.30.34 255.255.255.0 20.20.20.1 50.50.50.0 255.255.255.0 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 Bundle ID

1 1–31

2 33–63

3 65–95

4 97–127

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).



Configuration>Connection

1. PW host IP > 2. Redundant PW host IP > 3. Multiplexing (Source Port) 4. Bundle ID[1 - 511] ... (1) 5. PW type > (TDMoIP CE) 6. PSN type > (UDP/IP) 7. DS0 bundle []> 8. Bundle connection > > Please select item <1 to 8> ESC-prev.menu; !-main menu; &-exit 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 ... (0.0.0.0) 2. IP mask ... (0.0.0.0) > Please select item <1 to 2> ESC-prev.menu; !-main menu; &-exit 1 M/ 1 C

Figure 4-46. PW Host IP Menu

Table 4-19. PW Host IP Parameters


IP address 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.

Valid IP address

IP Mask IP mask of the PW host, used for the

pseudowire traffic

Valid IP mask

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:



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 (1–4), 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 +5 +6 +7 +8 +9 +10

TS 0 1 0 0 0 0 0 0 0 0 0

TS 10 0 0 0 0 0 0 0 0 0 0

TS 20 0 0 0 0 0 0 0 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).

• 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)

Note



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).

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).

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. Destination IP Address ... (2.2.2.10) 2. Bundle Name ... (Bundle 1) 3. Next Hop ... (1.1.1.1) 4. IP TOS[0 - 255] ... (0) 5. Connection Status (Enable) 6. Destination Bundle[1 - 8063] ... (1) 7. Redundancy Function > (Primary) 8. TDM Bytes In Frame(x48 Bytes)[1 - 30] ... (1) 9. Payload Format > (V2) 10. Far End Type > (E1) 11. OAM Connectivity (Disable) 12. Jitter Buffer [msec][2.5 - 180] ... (3.0) 13. Sensitive (Data) 14. OOS Mode (Tx OOS) 15. VLAN Tagging (Enable) 16. VLAN ID[1 - 4094] ... (111) 17. VLAN Priority[0 - 7] ... (7) 18. RTP Header (Enable) 19. RTP Payload Type[0 - 7f] ... (65) 20. SSRC ... (0) 18. Source IP Address (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)

Note

Note



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)


Destination IP Address IP address of the destination device 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.

Valid IP address

Default – None

IP TOS Specifies the Layer 3 priority assigned to

the traffic generated by this bundle.

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.

0–255

Default – 0




Connection Status Administrative status of the connection 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.

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 CESoPSN and

SAToP PWs operate over UDP/IP PSN

• +1 when the TDMoIP is set to the V1

payload format.

Destination bundle must be the same for

both primary and secondary bundles

operating in protection mode.

1–8063

Default – 1

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

1–30

Default – 1




Payload Format 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.

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

protocol for this bundle.

The OAM connectivity protocol enables

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.

ENABLE – The use of the OAM

connectivity protocol is enabled. This is

the recommended selection. Make sure to

select V2 for Payload Format.

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.




Jitter Buffer Specifies the value of the jitter buffer to

be used on this bundle.

You should use the shortest feasible

buffer, to minimize connection latency.

2.5–180 msec (framed)

0.5–180 msec (unframed)

Default – 3.0

Sensitive 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

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

traffic generated by this bundle

Enable – VLAN tagging is enabled

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.

1–4094

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.

0–7

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)




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).

Enable – RTP header is added to the

bundle

Disable – RTP header is not added to the

bundle

Default – Disable

RTP Payload Type Defines format of the RTP payload 0–7f

Default – 65

SSRC Synchronization source identifier for the

RTP session. The identifier is selected randomly to ensure that no two synchronization sources within the same RTP session have the same SSRC identifier.

0–4294967295 (32 bits)

Default – 0

Table 4-21. Connection Parameters (TDMoIP CE Connection, MPLS/ETH PSN)


Destination IP Address See Table 4-20

MPLS Egress Label 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

Outbound Tunnel Label Specifies the outbound MPLS label used

for the bundle.

This parameter is displayed only when

Outbound Label Tagging is enabled.

16–1048575

Default – 16

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.

0–7

Default – 0

Connection Status See Table 4-20

Destination Bundle See Table 4-20

Next Hop Type Type of the next hop device IP – The next hop device is an IP router

MAC – The next hop device is an MPLS LER

Default – IP

Next Hop See Table 4-20

TDM Bytes in Frame

(x48 bytes)

See Table 4-20




Payload Format See Table 4-20

Far End Type See Table 4-20

OAM Connectivity See Table 4-20

Jitter Buffer See Table 4-20

Sensitive See Table 4-20

OOS Mode See Table 4-20

VLAN Tagging See Table 4-20

VLAN ID See Table 4-20

Table 4-22. Connection Parameters (CESoPSN Connection, UDP/IP PSN)




IP TOS See Table 4-20


Destination bundle See Table 4-20

TDM Frames in Packet Defines number of TDM frames in one

packet

4–1440/Number of Timeslots


OAM connectivity See Table 4-20






VLAN Priority See Table 4-20

Table 4-23. Connection Parameters (CESoPSN Connection, MPLS/ETH PSN)



Outbound Label

Tagging

See Table 4-21

Outbound Tunnel Label See Table 4-21

Outbound EXP Bits See Table 4-21






Next Hop Type See Table 4-21


TDM Frames in Packet See Table 4-22









Table 4-24. Connection Parameters (SAToP Connection, UDP/IP PSN)







TDM Bytes in Packet Defines UDP payload length (number of

payload bytes in one Ethernet frame)

32–1440 (E1)

24–1440 (T1)

Default – 32 (E1), 24 (T1)



Jitter Buffer See Table 4-20 0.5–180

Default – 3.0








Table 4-25. Connection Parameters (SAToP Connection, MPLS/ETH PSN)



Outbound Label

Tagging

See Table 4-21







TDM Bytes in Packet See Table 4-24




Jitter Buffer See Table 4-20 0.5–180

Default – 3.0





Table 4-26. Connection Parameters (HDLC Connection, UDP/IP PSN)














Table 4-27. Connection Parameters (HDLC Connection, MPLS/ETH PSN)



Outbound Label

Tagging

See Table 4-21












• 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:

Notes



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. VLAN Mode (Unaware) 2. Forwarding Mode (Transparent) 3. Aging Time[300 - 4080] ...(300) 4. Static MAC Table []> 5. Erase MAC Table 6. Bridge Port > 7. VLAN Membership > ESC-prev.menu; !-main menu; &-exit 1 M/ 1 C

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).


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.



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 ESC-prev.menu; !-main menu; &-exit; ?-help 1 M/ 1 C

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 > (Network)

4. Save All > ESC-prev.menu; !-main menu; &-exit 1 M/ 1 C

Figure 4-52. Static MAC Table, Add Mode (VLAN-Aware)



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)

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): 1–4094

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): 0–7.

Note

Note



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 ... (Enable)

2. Accept Frame Type ... (All)

3. Port VID\Stacking VID [1 - 4094] ... (1) 4. Default Priority Tag [0 - 2] ... (0)

5. Egress Tag Handling (None)

6. Ingress Tag Handling (None)

7. L2CP Handling > > F - Forward ESC-prev.menu; !-main menu; &-exit 1 M/ 1 C

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.

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)

Note



Discard – (L2CP frames are discarded)

Default: Tunnel

Configuration>Configuration>Bridge>Bridge Port>L2CP Handling

MAC Dest Address Handling

1. 01:80:C2:00:00:00 (Tunnel) 2. 01:80:C2:00:00:01 (Tunnel) 3. 01:80:C2:00:00:02 (Tunnel) 4. 01:80:C2:00:00:03 (Tunnel) 5. 01:80:C2:00:00:04 (Tunnel) 6. 01:80:C2:00:00:05 (Tunnel) 7. 01:80:C2:00:00:06 (Tunnel) 8. 01:80:C2:00:00:07 (Tunnel) 9. 01:80:C2:00:00:08 (Tunnel) 10.01:80:C2:00:00:09 (Tunnel)

11.01:80:C2:00:00:0A (Tunnel)

12.01:80:C2:00:00:0B (Tunnel)

... (N) > Please select item <1 to 16> ESC-prev.menu; !-main menu; &-exit 1 M/ 1 C

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.



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.

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).


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.


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

Note



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.).



Configuration>QoS>Priority>Classification

1. Network ETH1 >(802.1p)

2. Network/User ETH2 >(802.1p)

3. User ETH3 >(802.1p)

4. MNG >(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 (0–7) to a specific priority queue (traffic class 0 (lowest), traffic class 1, traffic class 2, or traffic class 3)

DSCP priority – Assign each DSCP (0–63) 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 (0–7) 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 >(Traffic class 0)







8. User priority 7 >(Traffic class 2) > S - Save ESC-prev.menu; !-main menu; &-exit 1 M/ 1 C

Figure 4-58. Mapping for 802.1p Priority Menu



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).

The 100–666 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.

Note



Configuration>QoS>Rate Limitation>Ingress Port Label > (1) Port > (Network Port)

1. Rate Limitation > (1Mbps) 2. Burst Size (in kB) > (12K) 3. Limit Packet Type > (All) > Please select item <1 to 3> F - Forward S – Save ESC-prev.menu; !-main menu; &-exit 1 M/ 1 C

Figure 4-59. Ingress Rate Limitation Menu

Table 4-28. Rate and Burst Limitation

Rate Limit Burst Size Rate Limit Burst Size

12 kB 24 kB 48 kB 96 kB 12 kB 24 kB 48 kB 96 kB

1 Mbps 41 Mbps X X

1.5 Mbps 45 Mbps X

2 Mbps 50 Mbps

3 Mbps 60 Mbps

4 Mbps 71 Mbps X X

5 Mbps 83 Mbps

6 Mbps 90 Mbps X X

7 Mbps 100 Mbps X

8 Mbps 125 Mbps

9 Mbps 166 Mbps X

10 Mbps 200 Mbps X X

15 Mbps 250 Mbps

20 Mbps 333 Mbps X X

25 Mbps 400 Mbps X

30 Mbps 500 Mbps X

35 Mbps 666 Mbps X

40 Mbps X 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.


4-72 Performing Additional Tasks IPmux-24 Ver. 3.5

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:

• From the Main menu, select Inventory.

Inventory SOFTWARE Boot version (1.14 ) Application version (3.50a8 14/03/2010 16:30:56) Backup version (2.10a6 01/04/2009 16:55:02) HARDWARE Version (0.0/TCXO) Host MAC address (0020D2265244) PW MAC address (0020D226515E) PW Redundant MAC address (0010E1164256) ERP MAC address (0030B4535223) Security Key (SSL + SSH) ... (N) > ESC-prev.menu; !-main menu; &-exit 1 M/ 1 C

Figure 4-60. Inventory Screen (Page 1)


IPmux-24 Ver. 3.5 Performing Additional Tasks 4-73

Inventory ... (P) INTERFACE TDM1 (E1 over UTP) TDM2 (E1 over UTP) TDM3 (E1 over UTP) TDM4 (E1 over UTP) ETH1/Net (ETHERNET over Multimode LC) ETH2/User1 (ETHERNET over Multimode LC) ETH3/User2 (ETHERNET over UTP) CPLD Carrier Class Support (No) Real Time Clock (Not Exist) > ESC-prev.menu; !-main menu; &-exit 1 M/ 1 C

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)

1. System Date > (01-01-2010) 2. System Time > (00:00:01) 3. Broadcast Mode > (Disable) 4. Poll Interval (Minutes) [1 – 1440] > (15) 5. UTC Offset [-12 – 13] > (+2) 6. NTP Servers [] > Please select item <1 to 2> ESC-prev.menu; !-main menu; &-exit 1 M/ 1 C

Figure 4-62. Date and Time Menu



Table 4-29. Date and Time Values


System Date Current system date entered manually or

received from an NTP server in the

dd:mm: yyyy format

System Time Current system time entered manually or

received from an NTP server in the

hh:mm:ss format

Broadcast Mode 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:

• Broadcast mode is enabled

• The 1st polling has not been

completed

• No unicast NTP server is defined.

1–1440

Default – 15

UTC Offset Defines offset of NTP or RTC from UTC in

minutes

-12 to +13 (-720–0–780 minutes)

NTP Servers 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) – 1–65535



Stratum (NTP server stratum) – 0–255

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 NTP Server Admin UDP Stratum Last Received Status Port Timestamp ddd:hh:mm:ss Ago 1. 001.001.001.001 Prefer 123 4 01-10-1949 000:00:00:01 00:00:10 2. 002.002.002.002 Enable 1234 5 01-10-1949 000:00:00:10 00:00:01 3. 003.003.003.003 Disable 12345 -- -- -- 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.



*** 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 (1–10) corresponding to a banner line that you intend to edit.

2. Enter desired text and press <Enter>.


Configuration>System>Edit Banner

1. ... ( *** W A R N I N G *** ) 2. ... (All content of this product are PROPRIETARY INFORMATION. ) 3. ... (Disclosure of information found in this product ) 4. ... (for any unauthorized use is *STRICTLY PROHIBITED*. ) 5. ... (Unauthorized or improper use of this product ) 6. ... (may result in administrative disciplinary action ) 7. ... (and/or civil charges/criminal penalties. ) 8. ... (By continuing you indicate your awareness of ) 9. ... (and consent to these terms and conditions of use. ) 10.... (DO NOT LOG IN unless you agree to the conditions stated in this w...) > Please select item <1 to 10> ESC-prev.menu; !-main menu; &-exit 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):



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.0–255.255.255.255

Server UDP Port (The UDP port of the Syslog server): 1–65535

Device UDP Port (The local UDP port from which the Syslog messages are sent: 1–65535

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 1–7

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.0–255.255.255.255

• Server UDP Port (The UDP port of the Syslog server): 1–65535

Configuration>System>Syslog

1. Device Logging status > (Disable) 2. Device UDP port > (514)

3. Facility > (Local 1)

4. Severity level > (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.

Note



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 > (Network-Eth1) Mode > (Full Duplex) Rate(Mbps) > (100) Status > (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



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 link’s 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: Remote Information: MAC Address ... (00-20-D2-26-52-44) MAC Address ... (00-00-00-00-00-00) OAM Mode > (Passive) OAM Mode > (Unknown) Unidirect > (Unknown) Unidirect > (Unknown) Vars Retr > (Unknown) Vars Retr > (Unknown) Link Events > (Unknown) Link Events > (Unknown) Loopback > (Unknown) Loopback > (Unknown) PDU Sise ... (1518) PDU Sise ... (0) Vendor OUI ... (000000) > F-Forward; B-Backward ESC-prev.menu; !-main menu; &-exit; ?-help 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:



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: (1.1.1.1) Next hop MAC address: (000000000000) Connectivity status: > (OK) Sequence errors: (0) Jitter buffer underflows: (0) Jitter buffer overflows: (0) 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.



To display the system clock status:

• From the Status menu, select System clock.

Monitoring>Status>System clock Active clock > (Adaptive) > (Channel 1) ESC-prev.menu; !-main menu; &-exit 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. From MAC Address ... (00-00-00-00-00-00) 2. To MAC Address ... (FF-FF-FF-FF-FF-FF) 3. Bridge Port ... (All/Network/User1/User2/Host/PW) 4. View MAC Table [] 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.



Monitoring>Bridge>MAC Table>View MAC Table MAC address Bridge port Status 1 00-20-D2-23-35-8F Network Static 2 00-20-D2-24-55-21 Network Learned 1 00-20-D2-23-35-8F Network Static > 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 User Name 1 UART su 2 158.15.163.20 SSH su 3 158.15.163.30 SSL user 4 158.15.163.40 Telnet user R - Refresh Table ESC-prev.menu; !-main menu; &-exit; ?-help 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:



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 > (CLOSED)

Port 1 Status > (UP)

Port 2 Status > (Down)

ESC-prev.menu; !-main menu; &-exit 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)



Monitoring>Status>Protection>ERP (G.8302) Ring Number … (1) Ring Admin Status … (Enabled) Ring State … (Idle) Bridge Number … (1) RPL Port … (None) East Port Number … (3) East Port State … (Forward) East Port SF Source … (None) West Port Number … (4) West Port State … (Forward) West Port SF Source … (None) WTR Status … (Stopped) Last R-APS Rx … (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 > (1) Ethernet Port > (Network 1) Actor Port synchronized > (No) Partner Port synchronized > (No) F - Forward ESC-prev.menu; !-main menu; &-exit; ?-help 1 M/ 1 C

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.



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 Homing Dual Homing Status > (ENABLED) Port 1 Status > (ACTIVE) Port 2 Status > (NOT ACTIVE) ESC-prev.menu; !-main menu; &-exit; ?-help 1 M/ 1 C

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 > (ACTIVE) Secondary Bundle Status > (NOT ACTIVE) F – Forward; B – Backward ESC-prev.menu; !-main menu; &-exit; ?-help 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.



Monitoring>Status>OAM (802.1ag) MD Name ... (DEFAULT) MA Name ... (DEFAULT) Primary Vlan [ 1 – 4094] ... (0) Remote MEP Address ... (00-20-C2-01-02-03) Remote Mep Status ... (Fail) 1. MD ID ... (1) 2. MA ID[1 - 16] ... (1) 3. MEP ID[1 - 8191] ... (1) 4. Remote MEP ID[1 - 8191] ... (0) > Please select item <1 to 4> ESC-prev.menu; !-main menu; &-exit 1 M/2 C

Figure 4-80. Service OAM Status Screen

Table 4-30. Service OAM Status Parameters


MD Name Displays maintenance domain name

corresponding to MD ID

MA Name Displays maintenance association name

corresponding to MA ID

Primary Vlan Displays VLAN ID from OAM messages 1–4094

Remote MEP

Address

Displays the remote MEP MAC address MAC address

Remote Mep Status Displays the current status of the remote MEP 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

Note: This parameter appears only if a cross-connect defect exists.




Remote MD Format Displays the maintenance domain name

format of the remote MEP

None – No name defined


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


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 Specifies the maintenance domain ID 1–16

MA ID Specifies the maintenance association ID 1–16

MEP ID Specifies the MEP ID 1–8191

Remote MEP ID Specifies the remove MEP ID 1–8191

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



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.



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.



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.

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

Note



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)


IPmux-24 starts file transfer using TFTP.

Utilities>File Utilities>Download/upload using TFTP

1. File name ... (FILE.IMG) 2. Command > (No operation) 3. Server IP ... (0.0.0.0) 4. Retry timeout(sec)[0 - 1000] ... (1) 5. Total timeout(sec)[0 - 1000] ... (5) 6. View transfer status > > ESC-prev.menu; !-main menu; &-exit 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)



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 > Please select item <1 to 2> ESC-prev.menu; !-main menu; &-exit 1 M/ 1 C

Figure 4-86. Utilities Menu

IPmux-24 Ver. 3.5 Monitoring Performance 5-1

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.

Chapter 5 Monitoring and Diagnostics Installation and Operation Manual

5-2 Monitoring Performance IPmux-24 Ver. 3.5

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: (0) DM: (0)

LOF (Red): (0) ES: (0)

LCV: (0) SES: (0)

RAI (Yellow): (0) UAS: (0)

AIS: (0) LOMF: (0)

FEBE: (0)

BES: (0) Time Since (sec): (366) Valid Intervals: (96) 1. Interval ... (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

Installation and Operation Manual Chapter 5 Monitoring and Diagnostics


Table 5-1. E1/T1 Statistics

Alarm Description

LOS 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.



Alarm Description

RAI (Yellow) 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).



Alarm Description

DM 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.



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 > (User1-Eth2) Frames Received Frames Transmitted Total Frames: (0) Correct Frames: (0) Total Octets: (0) Correct Octets: (0) Oversize Frames (0) Collisions: (0) Fragments: (0) Jabber: (0) Dropped Frames: (0) CRC Errors: (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 Description

Frames Received

Total Frames The total number of correct frames received. When a valid connection is established the

number should increase steadily.

Total Octets The total number of octets (bytes) received. When a valid connection is established the


Oversize

Frames

Number of frames exceeding the maximum allowed frame size, but are otherwise valid

Ethernet frames (good CRC).

Fragments The number of frames that are shorter than 64 bytes and have an invalid CRC.




Jabber 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

The number of frames successfully transmitted. When a valid connection is established the


Correct

Octets

The number of octets successfully transmitted. When a valid connection is established the


Collisions 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 Full-

Duplex 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



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: ... (0) Jitter buffer underflows: ... (580) Jitter buffer overflows: ... (0) Max Jitter buffer deviation [msec]: ... (5) Time since [sec]: (580) 1. Bundle ID[1 - 511] ... (33) 2. Interval ... (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



Table 5-3. Bundle Connection Statistics Parameters


Sequence

Errors

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.




Jitter Buffer

Underflows

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 can’t 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 buffer’s 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 can’t 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.




Jitter Buffer

Overflows

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 isn’t 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 system’s 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

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.

Time Since

(sec)

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.



2. Select required MD, MA, MEP and service.

3. Press <Ctrl + F> or <Ctrl + B> to select an interval (1–96).

No interval selection is available for the 24-hour statistics.

Monitoring>Statistics>OAM>15 Min. Counters

Frames Above Delay Obj.... (0) Elapsed Time ... (102767) Frames Below Delay Obj.... (0) Frames Above DV Obj. ... (0) Min. RT Delay (Msec) ... (0.0) Frames Below DV Obj. ... (0) Avg. RT Delay (Msec) ... (0.0) Frames Transmitted ... (101902) Max. RT Delay (Msec) ... (0.0) Frames Lost ... (0) Unavailable Seconds ... (101899) Avg. DV ... (0.0) Max. DV ... (0.0) 1. MD ID ... (1) 2. MA ID ... (1) 3. MEP ID[1 - 8191] ... (3443) 4. Service ... (1) 5. Interval ... (1) 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


Frames Above Delay Obj. Number of frames that exceeded delay objective

Frames Below Delay Obj. Number of frames below or equal delay objective

Frames Above DV Obj. Number of frames that exceeded delay variation objective

Frames Below DV Obj. Number of frames below or equal delay variation objective

Frames Transmitted Total number of OAM frames transmitted in the selected interval

Frames Lost Number of frames lost in the selected interval

Unavailable Seconds Number of seconds during which the service was unavailable in the current

interval

Elapsed Time Time (in seconds) elapsed from beginning of the interval 0–900

Min. RT Delay Minimum round trip delay (in mseconds) calculated in the interval (or up to

elapsed time in selected interval)

Avg. RT Delay Average round trip delay (in mseconds) calculated in the interval (or up to

elapsed time in current interval)

Note




Max. RT Delay Maximum round trip delay (in mseconds) calculated in the interval (or up

to elapsed time in current interval)

Avg. DV Average delay variation (in mseconds) calculated in the interval (or up to


Max. DV Maximum delay variation (in mseconds) calculated in the interval (or up to


Monitoring>Statistics>OAM>Service Counters

OAM Tx frames counter ... (2087328632) OAM Frames lost counter ... (0 OAM Frame loss Ratio ... (0) Elapsed time ... (1487) Unavailable seconds ... (0) Unavailability Ratio ... (0) Current Delay (msec) ... (0.0) Current Delay Variation (msec) ... (0.0)

1. MD ID ... (1) 2. MA ID ... (1) 3. MEP ID[1 - 8191] ... (3443)

4. Service ... (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


OAM Tx Frames Counter Total number of OAM frames transmitted since the service was

enabled

OAM Frames Lost Counter Total number of OAM frames lost since the service was enabled

OAM Frame Loss Ratio Total number of lost OAM frames divided by total number of

transmitted OAM frames since the service was enabled

Elapsed Time Time (in seconds) elapsed since the service was enabled

Unavailable Seconds Total number of unavailable seconds since the service was enabled

Unavailability Ratio Total number of unavailable seconds divided by elapsed time

Current Delay Delay of OAM frames (in msec)

Current Delay Variation Delay variation (in msec)



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 ... (1) OAM Mode (Passive) Link OAM Version ... (01.22.0) Rx Information ... (0) Tx Information ... (0) Rx Var Request ... (0) Tx Var Request ... (0) Rx Var Response ... (0) Tx Var Response ... (0) Rx Loopback Ctrl ... (0) Tx Loopback Ctrl ... (0) Rx Event Notify ... (0) Tx Event Notify ... (0) Rx Org Specific ... (0) Tx Org Specific ... (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.



Monitoring>Statistics>Protection>ERP (G.8302) Ring Number … (1) East Port R-APS SF Rx … (5) East Port R-APS SF Tx … (5) East Port R-APS NR Rx … (3) East Port R-APS NR Txx … (3) East Port R-APS NR,RB Rx … (0) East Port R-APS NR,RB Tx … (0) Total Valid Rx … (0) Total Valid Tx … (0) Total Errors Rx … (0) Total Errors Tx … (0) West Port R-APS SF Rx … (5) West Port R-APS SF Tx … (5) West Port R-APS NR Rx … (3) West Port R-APS NR Tx … (3) West Port R-APS NR,RB Rx … (0) West Port R-APS NR,RB Tx … (0) Total Valid Rx … (0) Total Valid Tx … (0) Total Errors Rx … (0) Total Errors Tx … (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


R-APS SF Message Tx/Rx 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.

R-APS NR Message Tx/Rx 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.

R-APS NR, RB Tx/Rx 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 Valid Rx/Tx Total number of valid R-APS messages received or transmitted by

East/West port

Total Errors Rx/Tx Total number of errored R-APS messages received or transmitted by

East/West port


5-16 Detecting Errors IPmux-24 Ver. 3.5

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. Ping > 2. Trace route > 3. Loopback > 4. Self Test Results > > Please select item <1 to 4> ESC-prev.menu; !-main menu; &-exit 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


IPmux-24 Ver. 3.5 Handling Events 5-17

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.


5-18 Handling Events IPmux-24 Ver. 3.5

Monitoring

1. Statistics > 2. Status > 3. Event Log > 4. Managers > > Please select item <1 to 3> ESC-prev.menu; !-main menu; &-exit 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 Log entry 30 2004-01-22 18:20:03 LOGIN VIA TERMINAL 29 2004-01-22 18:02:13 UAS START TDM SLOT CH 1 28 2004-01-22 18:02:03 LOS START TDM SLOT CH 1 27 2004-01-22 18:02:03 COLD START 26 2004-01-22 17:56:48 UAS START TDM SLOT CH 1 25 2004-01-22 17:56:38 LOS START TDM SLOT CH 1 24 2004-01-22 17:56:38 COLD START > ^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.



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 Description Corrective Action

COLD START IPmux-24 has been powered up None

CON LOCAL FAIL Ethernet frames are not received by the

local IPmux-24 on the specified connection

Check path over PSN

CONNECTIVITY MISMERGE 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.

1. Check the 802.1ag OAM

configuration.

2. Check path over PSN.

CON REMOTE FAIL Ethernet frames are not received by the

remote IPmux-24 on the specified

connection

Check path over PSN

CON CLOSED TDM SLOT

BUNDLE X

Bundle X has been disabled None

CON SYNC Bundle connection failure has ended None

CON UNAVAILABLE Remote TDM PW device is not available

(only applicable when OAM is Enabled)

Check the connection of the

remote TDM PW device

CON VALIDATION FAIL Connection is invalid (only applicable when

OAM is Enabled)

Check the bundle parameters

DUAL HOMING: ETHERNET

SLOT CH1 IS ACTIVE

IPmux-24 is in dual homing protection

mode. Ethernet link 1 is currently active.

None

DUAL HOMING: ETHERNET

SLOT CH2 IS ACTIVE

IPmux-24 is in dual homing protection

mode. Ethernet link 2 is currently active.

None

FAIL IPmux-24 MEP stopped receiving CCM from

its peer MEP

Check connectivity to remote

device

FATAL ERROR IPmux-24 has encountered an internal

fatal error

IPmux-24 requires servicing

IN BAND REMOTE LOOP

START

T1 inband loopback has been activated on

remote IPmux-24

None

IN BAND REMOTE LOOP

END

T1 inband loopback has been deactivated

on remote IPmux-24

None




IN BAND LOCAL LOOP

START

T1 inband loopback has been activated on

local IPmux-24

None

IN BAND LOCAL LOOP

END

T1 inband loopback has been deactivated

on local IPmux-24

None

INVALID LOGIN VIA

TERMINAL

Invalid user name or password was

entered, when attempting to access

IPmux-24 via local terminal

None

INVALID LOGIN VIA WEB Invalid user name or password was


IPmux-24 via Web browser

None

INVALID LOGIN VIA

TELNET

Invalid user name or password was


IPmux-24 via Telnet

None

IP x.x.x.x ASSIGNED BY

SERVER x.x.x.x

The current IP address was assigned the

IPmux-24 host by DHCP server

None

IP x.x.x.x IS RELEASED The current IP address was released by

IPmux-24

None

LAG: ETHERNET SLOT CH1

IS ACTIVE

IPmux-24 is in LAG mode. Ethernet link 1 is

currently active.

None

LINE AIS END Line AIS state detected has ended None

LINE AIS START IPmux-24 has AIS (alarm indicator signal)

state on its E1/T1 port

Check for a fault at the PDH

network, on the receive direction

LINE FEBE END LINE FEBE state detected has ended None

LINE FEBE START IPmux-24 has LINE FEBE state on its E1/T1

port

Check for errors in the E1/T1

connection on the transmit

direction

LINE RAI END LINE RAI state detected has ended None

LINE RAI START IPmux-24 has LINE RAI (remote alarm

indication) state on its E1/T1 port

Check for a fault at the E1/T1

connectivity on the transmit

direction

LOGIN VIA TERMINAL The unit was accessed via local terminal None

LOGIN VIA WEB The unit was accessed via Web browser None

LOGIN VIA TELNET The unit was accessed via Telnet None

LOF START IPmux-24 has a LOF (loss of frame) state

on its E1/T1 port 1. Check the E1/T1 cable

connection.

2. Check all framing-related

parameters for E1/T1 interface.

LOF END LOF state detected has ended None

LOS END LOS state detected has ended None

LOS START IPmux-24 has a LOS (loss of signal) state

on its E1/T1 port 1. Check the E1/T1 cable

connection.




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 RDI is detected in CCM received from a

peer MEP Check connectivity to remote

device

SYSTEM USER RESET The user initiated software reset via the

system menu None

UAS START Ten consecutive severely errored seconds

were detected Check physical interface

connections.

UAS END Ten consecutive seconds without SES were

detected None

UNEXPECTED MD LEVEL IPmux-24 MEP received a CCM with

incorrect MD level (less than the MEP’s

own level)

Check the 802.1ag OAM

configuration

UNEXPECTED MEP IPmux-24 MEP received a CCM with correct

MD level, correct MA ID, but an incorrect

MEP ID


configuration

UNEXPECTED PERIOD 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 MEP’s CCM)


configuration

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.

List of the alarm traps can be displayed by typing ?.

3. Select Trap Status to enable or disable masking of the selected alarm.

Note



Configuration>System>Management>Alarm trap mask

Active alarm traps: > (-)

1. Alarm ID <use 'help'>[1 - 40] ... (39) 2. Trap status (Masked) > Please select item <1 to 2> S - Save; ? - Help ESC-prev.menu; !-main menu; &-exit 1 M/ 1 C

Figure 5-14. Alarm Trap Mask Menu

Table 5-8. Trap List

Trap Description, Severity OID

alarmLOS Loss of Signal (LOS Physical Layer), major 1.3.6.1.4.1.164.6.1.3.0.7

alarmLOF Loss of Frame (LOF Physical Layer), major 1.3.6.1.4.1.164.6.1.3.0.8

alarmAIS Alarm Indication Signal Received (AIS Line

Physical Layer), major

1.3.6.1.4.1.164.6.1.3.0.10

alarmRDI Remote Defect Indication Received (RDI

Line Physical Layer), major

1.3.6.1.4.1.164.6.1.3.0.11

alarmFEBE Far End Block Error (FEBE Line Layer),

major

1.3.6.1.4.1.164.6.1.3.0.12

alarmExtClk External clock source has failed, minor 1.3.6.1.4.1.164.6.1.0.10

BundleConenctionStatus Bundle connectivity status:

• O.K – major

• Remote fail – minor

• Local fail – major

• Validation Fail – major

• Unavailable – major

1.3.6.1.4.1.164.6.1.3.0.15

prtStatusChangeTrap Change in the NET or NET/USER port status

when Ethernet ring is active

1.3.6.1.4.1.164.6.1.0.3

ethIfRingStatusChange Change in Ethernet ring status 1.3.6.1.4.1.164.3.1.6.1.4.0.1

sysRedundancyActivePortTrap Change of active port status in bundle

redundancy group

1.3.6.1.4.1.164.3.3.0.9

ethOamCfmDefectCondition Status of the 802.1ag OAM CC traffic:

• fail – major

• mismerge – major

• rdi – major

• status active – major

• status not active – major

1.3.6.1.4.1.164.3.1.6.1.3.0.1


IPmux-24 Ver. 3.5 Testing the Unit 5-23

Trap Description, Severity OID

• unexpectedMep – major

• unexpectedMdLevel – major

erpPortStateChanged Change in an ERP port status 1.3.6.1.4.1.164.3.1.6.1.4.0.2

erpRingStateChanged Change in ERP ring status 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 Probable Cause Remedial Action

E1/T1 equipment connected to

IPmux-24 is not synchronized

with IPmux-24.

Configuration or physical layer

problems

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


5-24 Testing the Unit IPmux-24 Ver. 3.5

• 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).

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).

Note



Diagnostics>Loopback Channel ID (1)

1. Loopback State > (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) > ESC-prev.menu; !-main menu; &-exit 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.



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).



Diagnostics>Loopback (T1)>Inband Loop Detection

1. Loop Location > (Local System) 2. Loop up length[1 - 8] ... (5) 3. Loop up code[Hex] ... (10) 4. Loop down length[1 - 8] ... (3) 5. Loop down code[Hex] ... (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: 1–4095

VLAN Priority: 0–7

The VLAN ID and VLAN Priority configuration is available only if the VLAN tagging is enabled.

Number of frames to send: 0–50.

0 means endless ping.

3. Select Ping Send to start sending pings.

Note



Diagnostics>Ping

1. Interface (PW Host IP) 2. Destination IP address ... (0.0.0.0) 3. VLAN tagging (Enable) 4. VLAN ID[1 - 4095] ... (0) 5. VLAN priority[0 - 7] ... (0) 6. Number of frames to send[0 - 50] ... (1) 7. Send Ping > Please select item <1 to 7> ESC-prev.menu; !-main menu; &-exit 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.

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: 1–4095

VLAN Priority: 0–7

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. Interface (System Host IP) 2. Destination IP address ... (0.0.0.0) 3. VLAN tagging (Enable) 4. VLAN ID[1 - 4095] ... (1) 5. VLAN priority tag [0 - 7] ... (0) 6. Trace route send > Please select item <1 to 6> ESC-prev.menu; !-main menu; &-exit 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).

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.

Note

Note



Main Menu > Diagnostics > OAM Test (802.1ag) > Loopback 1. MD ID ... (1) 2. MA ID ... (1) 3. MEP ID[1 - 8191] ... (1) 4. Destination Type (Remote MEP ID) 5. Remote MEP ID ... (150) Remote MEP Address ... (00-20-D2-C3-C3-C3) 6. Number of LBs to Send[0 - 50] ... (0) Please select item <1 to 9> ESC-prev. menu; !-main menu; &-exit 1 M/2 C

Figure 5-24. OAM Loopback Menu

Table 5-10. OAM Loopback Parameters





Destination Type The destination type for the loopback

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

Note: This parameter appears in the menu only if Destination Type is Remote MEP ID.

1–8191

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

0–50

Default: 0



IPmux-24 Main Menu > Diagnostics > OAM Test (802.1ag) > Loopback > Results Destination Address ... (00-11-B3-55-A6-77) Messages Sent ... (14) Replies In-Order ... (14) Replies Out-of-Order ... (0) Messages Lost/Timed out ... (0) Messages Lost/Timed out % ... (0) > ESC-prev. menu; !-main menu; &-exit 1 M/2 C

Figure 5-25. OAM Loopback Results Menu

Table 5-11. OAM Loopback Result Parameters


Destination

Address

The target MAC address of the loopback message

Messages Sent Number of loopback messages that were sent

Note: This parameter appears only if the destination address is unicast.

0–50

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


0–50

Replies Out-of-

Order

The number of replies to loopback that were received out of

order.


0–50

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


0–50

Messages

Lost/Timed out %

The percentage of loopback messages that were lost or timed

out


0–4,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).

The option to specify the destination MEP ID is available only if IPmux-24 can resolve at least one remote MEP MAC address.

Note



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. MD ID ... (1) 2. MA ID ... (1) 3. MEP ID[1 - 8191] ... (1) 4. Destination Type (Target MEP ID) 5. Target MEP ID ... (150) Target MEP Address ... (00-20-D2-C3-C3-C3) 6. TTL[1 - 64] ... (64) 7. Send Link Trace 8. Results > Please select item <1 to 9> ESC-prev. menu; !-main menu; &-exit 1 M/2 C

Figure 5-26. OAM Link Trace Menu

Table 5-12. OAM Link Trace Parameters





Destination Type The destination type for the link trace

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

Note: This parameter appears in the menu only if Destination Type is Target MEP ID.

1–8191

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.




Target MAC

Address

The MAC address of the link trace destination 00-00-00-00-00-00

through

FF-FF-FF-FF-FF-FF

TTL The number of hops. Each unit in the link trace decrements

the TTL until it reaches 0, which terminates the link trace.

1–64

Main Menu > Diagnostics > OAM Tests > Link Trace (802.1ag)> Results Hop MAC Address ING/EGR Action Port ID Relay Action 1 00-20-D2-C3-C3-C3 IngOK ETH1 RlyHit ESC-prev. menu; !-main menu; &-exit 1 M/2 C

Figure 5-27. Link Trace Results

Table 5-13. Link Trace Result Parameters


Hop The hop number on the way to the target, calculated by the

sent TTL value minus the received TTL value

1–64

MAC Address The MAC address of the entity that sent the LTR 00-00-00-00-00-00

through

FF-FF-FF-FF-FF-FF

ING/EGR Action Ingress or egress action that was taken in hop IngOK, IngDown,

IngBlocked, IngVID;

EgrOK, EgrDown,

EgrBlocked, EgrVID

Port ID Port that was used for hop

Relay Action The relay action RlyHit, RlyFDB,

RlyMPDB

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.


5-34 Frequently Asked Questions IPmux-24 Ver. 3.5

Diagnostics> Bundle protection switching

1. Force (Disable) > Please select item <1 to 1> F-forward; B-backward ESC-prev.menu; !-main menu; &-exit 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 user-configurable 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.


IPmux-24 Ver. 3.5 Frequently Asked Questions 5-35

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 0–7. 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 user-configured 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.


5-36 Technical Support IPmux-24 Ver. 3.5

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).

http://www.rad.com/�

IPmux-24 Ver. 3.5 Software Upgrade Options 6-1

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.

Chapter 6 Software Upgrade Installation and Operation Manual

6-2 Upgrading Software via the File Utilities Menu IPmux-24 Ver. 3.5

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

Installation and Operation Manual Chapter 6 Software Upgrade

IPmux-24 Ver. 3.5 Upgrading Software via the File Utilities Menu 6-3

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.

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. IP address ... (192.168.10.2) 2. IP mask ... (255.255.255.0) 3. DHCP (Disable) 4. DHCP Status > 5. Read Community ... (public) 6. Write Community ... (private) 7. Trap Community ... (SNMP_trap) 8. Encapsulation > > Please select item <1 to 8> ESC-prev.menu; !-main menu; &-exit 1 M/ 1 C

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.

Note


6-4 Upgrading Software via the File Utilities Menu IPmux-24 Ver. 3.5

Configuration>System>Management>Host>Encapsulation

1. Host Tagging (Tagged) 2. Host VLAN ID [1 - 4094] ... (300) 3. Host VLAN Priority [0 - 7] ... (7) > ESC-prev.menu; !-main menu; &-exit 1 M/ 1 C

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.

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.

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 (PW Host IP)

2. Destination IP address ... (192.168.10.20)

3. VLAN tagging (Disable)

4. Number of frames to send[1 - 4] ... (1)

5. Ping Send > Please select item <1 to 5> ESC-prev.menu; !-main menu; &-exit 1 M/ 1 C

Figure 6-4. Pinging the PC

Note

Note


IPmux-24 Ver. 3.5 Upgrading Software via the Boot Menu 6-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. File name ... (IPMUX.img) 2. Command > (Software download and reset) 3. Server IP ... (192.168.10.20) 4. Retry timeout(sec)[0 - 1000] ... (1) 5. Total timeout(sec)[0 - 1000] ... (5) 6. View transfer status > > ESC-prev.menu; !-main menu; &-exit 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.


6-6 Upgrading Software via the Boot Menu IPmux-24 Ver. 3.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).

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).

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).

Caution

Note



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.



When ready, press Send in the Send File window. You can now monitor the progress of the downloading in the Send File window.

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.

Note



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.

If downloading failed, repeat the whole procedure.

Note



IPmux-24 Ver. 3.5 CESoPSN Application 7-1

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

• 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

Chapter 7 Application Tutorial Installation and Operation Manual

7-2 CESoPSN Application IPmux-24 Ver. 3.5

• 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.

The SFP-9G transceiver is installed in the GE 1 port of the GbE module.

Straight Ethernet Cable

GbE MONITOR

ACT LINK GE 1 LINK PAUSE

TX RX

GE 2 LINK PAUSE

TX RX

GbE

IPmux-24DCE

CONTROL

SYNC

1 2 3 4E1/T1

SYNC SYNC SYNC

USER3

NET/USER2

NET1

10/100BASE-T

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.

PC

LAN

Cross Ethernet Cable

IPmux-24DCE

CONTROL

SYNC

1 2 3 4E1/T1

SYNC SYNC SYNC

USER3

NET/USER2

NET1

10/100BASE-T

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.

Note

Installation and Operation Manual Chapter 7 Application Tutorial


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.

E1.PW/28/BAL

E1-PW/28

CH 1-14 CH 15-281 3 5 7 9 11 13 15 17 19 21 23 25 27

2 4 6 8 10 12 14 16 18 20 22 24 26 28

LR

IO 2 IO 1

PATCH-28B

CBL-G703-14-PATCH Cable

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.



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: PS-1 PS-2 PS-3 CL-1 CL-2 DB : PS-AC PS-AC PS-AC CL CL SLOT: IO/1 IO/2 IO/3 IO/4 IO/5 DB : CES-E1-PW ----------- ----------- ----------- ----------- SLOT: IO/6 IO/7 IO/8 IO/9 DB : GbE ----------- ----------- ----------- 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



Pseudowire Gateway Configuration>System>Host IP INTERFACE IP ADDRESS IP MASK DEFAULT GATEWAY ONLINE CL: 0.0.0.0 0.0.0.0 0.0.0.0 GbE 1/IF 1: 192.168.100.100 255.255.255.0 192.168.100.1 GbE 1/IF 2: 0.0.0.0 0.0.0.0 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] ... (1) 1. IP ADDRESS ... (192.168.100.200) 2. NEXT HOP ... (0.0.0.0) 3. INTERFACE > (GIG A-IO 6/1) 4. TRAP(FOR MANAGER) (No) 5. VLAN VALID (No) VLAN ID[0 - 4095] ... (0) VLAN PRIORITY[0 - 7] ... (0)

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.



Pseudowire Gateway Configuration>System>Clock source>System A>Master clock 1. Master clock source > (Internal) 2. Save parameters

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.


1. IO[1 - 9] ... (6) 2. Arp refresh > (No Arp Refresh) 3. L4 pools configuration > 4. GbE port > 5. Monitor port >

> F - next; B - prev; ESC-prev.menu; !-main menu; &-exit; @-debug

Figure 7-12. Selecting the GbE Port

3. Select GbE Port.



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. GbE port[1 - 2] ... (1) 2. Connect state (Connect) 3. VLAN valid (No) 4. Auto Negotiation (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.


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.



Pseudowire Gateway Configuration>Physical layer>E1 port - (IO 1:E1 PORT 1 CARD TYPE- CES-E1-PW

Interface Type > (Balanced)

1. Channel ID[1 - 28] ... (1) 2. Admin Status (Connected) 3. Idle code[0 - ff] ... (7E) 4. OOS code[0 - ff] ... (FF) 5. Transmit clk source > (System A) 6. RX Sensitivity > (Short Haul) 7. Assign entire port to bundle > 8. Line type > (Framed G.704) 9. Restoration Time > (CCITT) > 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.


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



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


Pseudowire Gateway Configuration>Connection>Connection configuration - (BUNDLE 1) Connection state Enable Source CBID 1 Dest CBID 1 | Payload format V2 v TDM frame in frame 5 Jitter buffer in Ms[0-200] 3.00 Sensitivity Sensitive to data ^ OAM connectivity Enable | OAM indication Source port number Payload type Data | Far end type E1 v OOS L bit mode TX OOS and L bit Destination IP <192.168.100.101> ^ Network slot port 6/1 | Next hop <0.0.0.0> IP TOS 0 Adaptive clock Disable VLAN tagging Disable

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 1–10 to bundle 1.


4. Update the database.



Pseudowire Gateway Config>TS Assignment>TS assignment - (IO 1:T1 PORT 1 CARD TYPE- CES-E1-PW)

TIME SLOT NUM : TS 1 TS 2 TS 3 TS 4 TS 5 TS 6 TS 7 TS 8 TS 9 TS 10 Bundle number: 1 1 1 1 1 1 1 1 1 1 TS type: Full Full Full Full Full Full Full Full Full Full ->> 1. Change cell [1 - 2000] ... (0) >

Please select item <1 to 1> ESC-prev.menu; !-main menu; &-exit; @-debug; ?-help; S-save

Figure 7-18. Assigning Timeslots 1–10 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.


3. Configure the following:

IP address– 192.168.100.101

IP mask – 255.255.255.0




Configuration>System> Management>Host IP 1. IP address ... (192.168.100.101) 2. IP mask ... (255.255.255.0) 3. DHCP (Disable) 4. Read Community ... (public) 5. Write Community ... (private) 6. Trap Community ... (SNMP_trap) > Please select item <1 to 6> S - save ESC-prev.menu; !-main menu; &-exit 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.


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.



Configuration>Physical layer> TDM (E1)

Channel ID (1) Restoration Time > (CCITT) Signaling Mode (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. PW host IP > 2. Redundant PW host IP > 3. Multiplexing (Source Port) 4. Bundle ID[1 - 511] ... (1) 5. PW type > (CESoPSN) 6. PSN type > (UDP/IP) 7. DS0 bundle []> 8. Bundle connection > > Please select item <1 to 8> ESC-prev.menu; !-main menu; &-exit 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 +5 +6 +7 +8 +9 +10

TS 0 1 1 1 1 1 1 1 1 1 1

TS 10 0 0 0 0 0 0 0 0 0 0

TS 20 0 0 0 0 0 0 0 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 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




Configuration>Connection>Bundle connection TDM channel ID: 1 Bundle ID: 1 1. Destination IP address ... (192.168.100.100) 2. Next hop ... (-) 3. IP TOS[0 - 255] ... (0) 4. Connection status (Enable) 5. Destination bundle[1 - 8063] ... (1) 6. TDM Frames In Packet[1 – 288] ... (5) 7. Payload format (V2) 8. OAM connectivity (Disable) 9. Jitter buffer [msec][2.5 - 200] ... (3.0) 11. Sensitive (Data) 12. OOS mode (Tx OOS) 13. VLAN tagging (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: (192.168.100.100) Next hop MAC address: (00-20-D2-24-05-F) Connectivity status: > (OK)

Sequence errors: (0) Jitter buffer underflows: (0) Jitter buffer overflows: (0) 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).



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. RAD’s 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 RAD’s 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.



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.



Figure 7-30. Configuring the DXC-4 E1 Port Parameters

6. In the right-hand pane, select the Bert Setup tab and assign timeslots 1–10 to E1 stream.



Figure 7-31. Assigning Timeslots to E1 Stream


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.



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 button to stop the E1 traffic.


7-20 Typical Pseudowire Application with Ring Protection IPmux-24 Ver. 3.5

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:

• 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 Typical Pseudowire Application with Ring Protection 7-21

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).

IPmux-24 (A)DCE

CONTROL

SYNC

1 2 3 4E1/T1

SYNC SYNC SYNC

USER3

NET/USER2

NET1

10/100BASE-T


IPmux-24 (D)DCE

CONTROL

SYNC

1 2 3 4E1/T1

SYNC SYNC SYNC

USER3

NET/USER2

NET1

10/100BASE-T

IPmux-24 (C)DCE

CONTROL

SYNC

1 2 3 4E1/T1

SYNC SYNC SYNC

USER3

NET/USER2

NET1

10/100BASE-T



Ethernet Cable

To Packet-Switched Network Equipment

IPmux-24 (B)DCE

CONTROL

SYNC

1 2 3 4E1/T1

SYNC SYNC SYNC

USER3

NET/USER2

NET1

10/100BASE-T


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.



E1 Cable

IPmux-24DCE

CONTROL

SYNC

1 2 3 4E1/T1

SYNC SYNC SYNC

USER3

NET/USER2

NET1

10/100BASE-T

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.

E1.PW/28/BAL

E1-PW/28

CH 1-14 CH 15-281 3 5 7 9 11 13 15 17 19 21 23 25 27

2 4 6 8 10 12 14 16 18 20 22 24 26 28

LR

IO 2 IO 1

PATCH-28B

CBL-G703-14-PATCH Cable

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)



10. Allocating timeslots to bundles

11. Connecting bundles to the central Gmux-2000.

Table 7-1. Configuration Summary

Device E1 Parameters Management Host

Parameters

PW Host Parameters

Bundle Parameters Ring Traffic

IPmux-24 (A) Transmit clock source:

Adaptive

Line type: Framed

G.704 CRC-4 enabled

CAS disabled

IP address:

192.168.10.2

VLAN ID: 9

VLAN priority: 5

IP address:

192.168.11.2

VLAN ID: 11

VLAN priority: 6

Bundle 1: full E1 VLAN ID: 100

VLAN priority: 7

IPmux-24 (B) Transmit clock source:

Adaptive

Line type: Framed

G.704 CRC-4 enabled

CAS disabled

IP address:

192.168.10.3

VLAN ID: 9

VLAN priority: 5

IP address:

192.168.11.3

VLAN ID: 11

VLAN priority: 6


VLAN priority: 7

IPmux-24 (C) Transmit clock source:

Adaptive

Line type: Framed

G.704 CRC-4 enabled

CAS disabled

IP address:

192.168.10.4

VLAN ID: 9

VLAN priority: 5

IP address:

192.168.11.4

VLAN ID: 11

VLAN priority: 6


VLAN priority: 7

IPmux-24 (C) Transmit clock source:

Adaptive

Line type: Framed

G.704 CRC-4 enabled

CAS disabled

IP address:

192.168.10.5

VLAN ID: 9

VLAN priority: 5

IP address:

192.168.11.5

VLAN ID: 11

VLAN priority: 6


VLAN priority: 7

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.



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 mask – 255. 255. 255.0

IPmux-24 (C):


PW host IP mask – 255. 255. 255.0

IPmux-24 (D):


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. IP address ... (192.168.11.2) 2. IP mask ... (255. 255. 255.0) 3. Default next hop ... (-) 4. Pw Encapsulation > > Please select item <1 to 4> ESC-prev.menu; !-main menu; &-exit 1 M/ 1 C

Figure 7-39. Configuring the Pseudowire Host IP for IPmux-24 (A)


The IPmux-24 bridge must be configured to the VLAN-aware mode with filtering.



To configure the bridge:

• From the Bridge menu (Configuration > Bridge), configure the following:

VLAN Mode – Aware

Forwarding Mode –Filter

Configuration>Bridge

1. VLAN Mode (Aware) 2. Forwarding Mode (Filter) 3. Aging Time[300 - 3060] ...(300) 4. Static MAC Table []> 5. Erase MAC Table 6. Bridge Port > 7. VLAN Membership > ESC-prev.menu; !-main menu; &-exit 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.


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.



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. Ring Administrative Status (Up) 2. Keep Alive Tx Time[Msec][2 - 100] ... (13) 3. Keep Alive Drops To Fall[1 - 10] ... (3) 4. PTP VLAN ID ... (4001) 5. Mcast VLAN ID ... (4002)) > Please select item <1 to 5> ESC-prev.menu; !-main menu; &-exit 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 > (802.1p ) 2. Network/User-ETH2 > (802.1p) 3. User-ETH3 > (Port default priority ) 4. TDM PW > (802.1p) > ESC-prev.menu; !-main menu; &-exit 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



• 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 5–7 to the traffic classes, as explained above.

IPmux-24 Configuration>Configuration>QoS>Priority>Mapping>802.1p








8. User priority 7 >(Traffic class 3) > Please select item <1 to 8> ESC-prev.menu; !-main menu; &-exit 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.



Configuration>System>Management>Alarm trap mask

Active alarm traps: > (-)

1. Alarm ID (use 'help')[1 - 40] ... (28) 2. Trap status (Unmask) > Please select item <1 to 2> S - Save; ? - Help ESC-prev.menu; !-main menu; &-exit 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.

IPmux-24 Ver. 3.5 E1 and T1 Connector A-1

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 Designation Direction Function

1 RD (R) Input Receive data (ring)

2 RD (T) Input Receive data (tip)

3, 6 – – FGND

4 TD (R) Output Transmit data (ring)

5 TD (T) Output Transmit data (tip)

7, 8 – N/A 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.

RJ-45

BNCFemale

Receive(Green)

Transmit(Red)

1

2

3

4

5

6

7

8

ShieldedRJ-45

Transmit(Red BNC)

Receive(Green BNC)

RX Ring

RX Tip

NC

TX Ring

TX Tip

NC

NC

NC

...

...

Figure A-1. CBL-RJ45/2BNC/E1/X Cable Wiring Diagram

Appendix A Connection Data Installation and Operation Manual

A-2 Ethernet Connectors IPmux-24 Ver. 3.5

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 Function

1 Tx+

2 Tx–

3 Rx+

4 –

5 –

6 Rx–

7 –

8 –

Table A-3. 1000BaseT Connector Pinout

Pin MDI MDIX

1 A+ B+

2 A- B-

3 B+ A+

4 C+ D+

5 C- D-

6 B- A-

7 D+ C+

8 D- C-

Installation and Operation Manual Appendix A Connection Data

IPmux-24 Ver. 3.5 External Clock Connector A-3

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 Function

1 –

2 Tx

3 Rx

4 –

5 GND

6 –

7 –

8 –

9 –

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 Function

1 RxRing (clock in)

2 RxTip (clock in)

3 Alarm In (RS-232 level signal)

4 TxRing (clock out, optional)

5 TxTip (clock out, optional)

6 Dry contact relay (normally shorted to pin 7)

7 Dry contact relay (central pin)

8 Dry contact relay (normally open, closed if an alarm is active)

Appendix A Connection Data Installation and Operation Manual

A-4 Alarm Relay IPmux-24 Ver. 3.5

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).

Publication No. SUP-930-07/08

The Access Company

AC/DC Adapter(AD) Plug

for DC Power Supply Connection

Supplement

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

Prepare all connections to the AD plug before inserting it into the unit’s power connector.

Caution

Note

AC/DC Adapter (AD) Plug

2

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.

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.

Figure 3. AD Plug Details

• Reversing the wire voltage polarity will not cause damage to the unit, but the internal protection fuse will not function.

• Always connect a ground wire to the AD plug’s 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.

Warning

24 Raoul Wallenberg Street, Tel Aviv 69719, Israel

Tel: +972-3-6458181, Fax +972-3-6483331, +972-3-6498250

E-mail: [email protected], 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: IPmux-24 Ver. 3.5

Publication Number: 488-200-07/10

Please grade the manual according to the following factors:

Excellent Good Fair Poor Very Poor

Installation instructions

Operating instructions

Manual organization

Illustrations

The manual as a whole

What did you like about the manual?


http://www.rad.com/�

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 [email protected]

North America Headquarters 900 Corporate Drive

Mahwah, NJ 07430, USA

Tel. 201-5291100 Toll free 1-800-4447234

Fax 201-5295777

E-mail [email protected]

www.rad.com The Access Company

I pmux 24-manual

Engineering

rad requests

limited warranty rad

operation manual

local distributor

registered trademark

access company

usa tel

israel tel