FibeAir 70 PRODUCT DESCRIPTION May 2011 | Ver. 10.0 4Gon www.4Gon.co.uk info@4gon.co.
Trademarks Ceragon, the Ceragon logo and FibeAir 70™ are all trademarks of Ceragon Ltd. All other product names and trademarks mentioned in this document are trademarks or registered trademarks of their respective companies. Copyrights Copyright © 2011 Ceragon Ltd. All rights reserved. No part of this publication may be reproduced or distributed in any form or by any means, or stored in a database or retrieval system, without the prior written consent of Ceragon.
Safety and Regulatory Notices The following are mandatory notices for installation and operation of FibeAir 70, 70GHz Wireless Backhaul Link. Indications appearing here are required by the designated government and regulatory agencies for purposes of safety and compliance. General Do not install or operate this System in the presence of flammable gases or fumes. Operating any electrical instrument in such an environment is a safety hazard.
About this Document This document is the Installation and User Manual for the FibeAir 70, 70GHz Wireless Links. Audience This document assumes a working knowledge of wireless backhaul platforms and their operating environments. This document is intended for use by all persons who are involved in planning, installing, configuring and using the FibeAir 70 system. Conventions The following conventions are used in this document in order to make locating, reading, and using information easier.
TABLE OF CONTENTS 1 2 3 Introduction to the FibeAir 70 System 13 1.1 System Applications 14 1.2 Main Features 14 1.3 Functional Description 15 1.4 Management 15 1.5 Technical Specifications 16 Installing the FibeAir 70 17 2.1 Site Preparation 17 2.2 FibeAir 70 Package Content 18 2.3 System Installation 19 2.3.1 2.3.2 2.3.3 2.3.4 2.3.5 2.3.6 2.3.
3.2 3.3 4 ODU Setup using the web-EMS 31 3.2.1 3.2.2 3.2.3 3.2.4 3.2.5 3.2.6 3.2.7 3.2.8 31 32 35 38 38 39 42 43 Connecting to the ODU Quick Configuration System Bridge Events Radio Ethernet Interface Configuration Advanced Settings ODU Setup using the CLI 46 3.3.1 3.3.2 3.3.3 3.3.4 3.3.5 3.3.6 46 46 47 48 51 52 Connecting to the ODU System IP RF Ethernet Interfaces Save and Reset FibeAir 70 Network Configuration 53 4.1 FibeAir 70 Bridging Model 53 4.2 Default Bridge Configuration 54 4.
4.6.1 4.6.2 4.6.3 4.6.4 4.6.5 4.6.6 73 74 74 74 74 74 4.7 FibeAir 70 Commissioning and Acceptance Form 75 4.8 Invoking the CLI 77 4.9 CLI Command Syntax 78 4.9.1 4.9.2 4.9.3 4.9.4 4.9.5 4.9.6 78 79 79 81 84 84 Basic Conventions Common Syntax Rules Repeatedly Used Identifiers CLI Command Types Designating Objects in CLI Commands Designating Named Objects 4.10 Viewing the CLI Command History 88 4.11 Invoking CLI Help and Auto completion 89 4.12 CLI Error Messages 91 4.
5.4 5.5 5.6 5.7 5.8 5.9 Bridging Port 110 5.4.1 5.4.2 110 112 Bridging Port Commands Bridging Port Attributes VLAN Common 115 5.5.1 5.5.2 115 115 VLAN Common Commands VLAN Common Attributes VLAN Table 117 5.6.1 5.6.2 5.6.3 117 119 121 VLAN Table Commands VLAN Table Attributes VLAN-to-SNMP ifTable Attributes C-VLAN Registration 126 5.7.1 5.7.2 126 127 C-VLAN Registration Commands C-VLAN Registration Attributes PEP Virtual Port 129 5.8.1 5.8.
5.14 RF 5.14.1 5.14.2 6 150 RF Commands RF Attributes Performing Advanced CLI Operations 6.1 6.2 6.3 6.4 6.5 6.6 6.7 6.8 150 151 159 Configuration Files 160 6.1.1 6.1.2 6.1.3 160 160 160 Saving Configurations Viewing Configurations Removing the Startup Configuration Rollback Operations 161 6.2.1 161 Rollback Commands Software Upgrade 162 6.3.1 162 Software Upgrade Commands Ceragon File System (CFS) 164 6.4.1 6.4.2 6.4.3 6.4.
6.8.1 6.8.2 6.9 MD Commands MD Attributes 185 185 Maintenance Association 188 6.9.1 6.9.2 MA Commands MA Attributes 188 188 6.10 Component Maintenance Association 191 6.10.1 6.10.2 MA-COMP Commands MA-COMP Attributes 6.11 Maintenance End Point 6.11.1 6.11.2 6.11.3 MEP Commands Definitions of Writable MEP Attributes Definitions of Read-Only MEP Attributes 6.12 Received CCM Presentation 6.12.1 6.12.2 Parsing and Displaying CCM Messages CCM Parameter Definitions 6.13 Peer MEP Create 6.13.1 6.
7 FibeAir 70 Diagnostics 229 7.1 Diagnostics Tools 229 7.2 The Troubleshooting and Diagnostics Process 229 7.3 FibeAir 70 ODU LEDs 231 7.4 FibeAir 70 System Alarms and Events 232 7.5 FibeAir 70 System Statistics 235 7.5.1 7.5.2 7.5.3 235 237 238 7.6 RF Statistics VLAN Statistics Ethernet Statistics FibeAir 70 System Loopbacks 239 7.6.1 239 Loopback Diagrams Page 11 4Gon www.4Gon.co.uk info@4gon.co.
TABLE OF FIGURES FIGURE 1-1 FIBEAIR 70 SYSTEM 13 FIGURE 2-1 FIBEAIR 70 MOUNTING ASSEMBLY DETAILS 20 FIGURE 2-2 FIBEAIR 70 CONNECTION PANEL DETAILS 22 FIGURE 2-3 FIBEAIR 70 DC POWER CONNECTOR PIN-OUT DIAGRAM 22 FIGURE 2-4 ALL-W EATHER CONNECTING CABLE SHELL ASSEMBLY 23 FIGURE 2-5 INSTALLED FIBEAIR 70 UNIT 27 FIGURE 4-1 GENERIC MODEL OF THE FIBEAIR 70 BRIDGE 54 FIGURE 4-2 BASIC FIBEAIR 70 VLAN CONFIGURATION 60 FIGURE 4-3 FIBEAIR 70 MULTIPLE CUSTOMER VLAN CONFIGURATION 64 FIGURE 5-1 THE FIBEA
1 Introduction to the FibeAir 70 System The FibeAir 70 is member of Ceragon FibeAir family of wireless products, featuring carrier grade, high capacity Ethernet with flexible support of the 71-76 GHz regulated E-Band. The FibeAir 70 radio supports up to 1.2 Gbps aggregated traffic. Designed with strenuous carrier wireless backhaul demands in mind, FibeAir 70 solutions are equally at home in the mobile backhaul, in the enterprise, or in Ethernet service provider networks.
1.1 System Applications For Mobile Operators To meet growing subscriber demand, providers are constantly seeking additional network capacity to enable delivery of bandwidth-intensive data services. Nowhere are these challenges felt more acutely than in the backhaul network. Ceragon offers easily-deployed, Gigabit wireless solutions for mobile operators seeking to dramatically raise backhaul capacity.
Among key features of the FibeAir 70 systems is: 1.3 • Provides aggregated Gigabit-per-second data rates utilizing the newly allocated E-band spectrum, while being spectral efficient. • Integrates easily into existing networks, enabling operators to quickly and seamlessly scale and boost their network capacity and as they grow and introduce future technologies and services.
1.5 Technical Specifications FibeAir 70 – Product Highlights Data throughput Up to 70 Mbps Frequency Band 71-76 GHz According to ETSI EN 302 217-3 V1.3.1 (2009-07) Air Interface TDD, OFDM Channel Size 250 MHz or 500 MHz (Typical) Additional: n*62.
2 Installing the FibeAir 70 This chapter describes how to install and perform the basic setup for FibeAir 70 antenna outdoor units (ODUs) in a FibeAir 70 wireless network. Topics covered here include: 2.
• Install the FibeAir 70 ODU where network connections and optional power cabling are ready for operation and are easily accessed. • Install the FibeAir 70 ODU where proper electrical outdoor grounding is readily available. Typically, the grounding connection attached directly to the mounting pole. If not already present, then suitable structure -to-earth grounding connections must be created before installation. Note: 2.
2.3 System Installation 2.3.1 Required Tools Ensure that you have the following tools with you when performing the FibeAir 70 installation: 2.3.
2.3.3 Mounting the FibeAir 70 Figure 2-1 shows details of the FibeAir 70 Mounting Assembly. 1. Unit Mounting Bolts 6. Azimuth Adjustment Lock Bolts 2. Back Mounting Bracket 7. Elevation Adjustment Lock Bolts 3. Front Mounting Bracket 8. Azimuth Fine Adjustment Screw (± 8°) 4. Quick Release Plate (Attached to ODU) 9. Elevation Fine Adjustment Screw (± 16°) 5. Quick Release Hook 10.
If needed, change the ODU polarity position to match the orientation of the remote pair ODU by removing the Quick Release Plate, changing its orientation, and reattaching. For ease of reference, the markings “V” (vertical) and “H” (horizontal) are engraved on the back side of the ODU.
Connect the opposite end of the Grounding Cable to the earth connection, typically located on the mounting pole. In case earth connection is out of reach of the Grounding cable, install alternative cable. 2.3.5 Cabling Connections Cable connection panel details are shown in Figure 2-2. Network connections are made according to port availability on the ODU.
Cable Preparation Before inserting a cable connector into the ODU, it must first be enclosed in a protective AllWeather Shell, supplied with the FibeAir 70 unit. The protective All-Weather Shell assembly is shown in Figure 2-4. An identical All-Weather Shell is provided for each ODU connector: power supply, data interface, and management interface. Unscrew and remove the protective seals from each ODU cable interface opening that will be used in the configuration. 1. Cable Inlet Portion 3.
Removing Connectors from the FibeAir 70 ODU Caution: To avoid accidental damage to the connector, always use the following order to remove cable connections from the ODU (Refer to Figure 2-4): 1. Unscrew the Cable Inlet Portion ( ) of the All-Weather Shell first to release the gasket seal and remove tension from the cable connector. 2. Unscrew the Connector Outlet Portion ( )of the All-Weather Shell from its ODU port. 3. Remove the cable connector from its port.
2.3.6 Antenna ODU Alignment Two alignment stages (that is, course and fine al alignments) ignments) are required during installation on both local and remote FibeAir 70 Antenna ODUs. Accurate alignment of the ODU is critical for achieving the strongest receive signal possible. Verify the ODU is in Alignment Mode by checking the RF LED color – orange indicated Alignment Mode . Note: The FibeAir 70 ODU is shipped from the factory configured for Alignment Mode.
Before using the DVM, set its output to millivolts. Dividing the RSSI millivolt output by 10 will provide the actual receive signal strength calculation. For example, a DVM millivolt reading of 450 mV is equivalent to -45 dBm. Align the fine azimuth axis. Use the hexagonal wrench to adjust the Azimuth Fine Adjustment Screw ( ). Be sure to sweep the complete range of the azimuth in order to determine the maximum received signal strength position.
Figure 2-5 Installed FibeAir 70 Unit 2.3.7 Initial System Setup Disconnect the DVM from the FibeAir 70 ODU by removing the probes from the AUX port. Carefully reinsert and tighten replace the AUX port protective seal. Using the web-EMS or CLI configure the ODU to Adaptive Mode (See Section 5.14.1.1) on both local and remote units. Configure one unit to Role=Master and the second to Role=Slave. Save configuration and reset the ODU.
3 FibeAir 70 Configuration This chapter presents the FibeAir 70 ODU configuration steps for link setup. It describes the initial configuration procedures to be carried out after antennas alignment. Topics covered here include: • Default configuration information • ODU configuration using web-EMS • ODU configuration using CLI Networking configuration, including bridge management model, VLANs setup and configuration examples, is presented in chapter 4 “FibeAir 70 Network Configuration”. 3.
3.1.3 Default IP Address The FibeAir 70 ODU supports up to four IP addresses that can be on different subnets and associated to different VLANs. Static route can be assigned to each IP. By default, two IP addresses (IPs 1 and 4) are defined: 3.1.4 Index 1 4 IP Address 192.168.0.1 172.16.100.1 IP Mask 255.255.255.0 255.255.255.0 Route 0.0.0.0 0.0.0.0 Destination 0.0.0.0 0.0.0.0 Destination Mask 255.255.255.0 255.255.255.0 Default IP Gateway 0.0.0.0 0.0.0.
3.1.5 Default Ethernet Interface Configuration Many FibeAir 70 interface configuration items are hardcoded. However, the following items are configurable and their default values provided here: Configuration Item Default Value Admin Status Up (enabled) Interface Alias None (empty string) Ethernet Type 1000fd (Electrical RJ45, 1000 Full-Duplex) Auto-Negotiation Enabled Page 30 4Gon www.4Gon.co.uk info@4gon.co.
3.2 ODU Setup using the web-EMS This section provides information on the configuration steps of the ODU be carried out after antennas alignment. 3.2.1 Connecting to the ODU 1. Launch Internet Browser and enter the ODU’s IP address on the address bar (https://192.168.0.1). 2. Wait for the Java Applet to load and enter the username and password (admin, admin).
3.2.2 Quick Configuration 3.2.2.1 System Information Set ODU’s system information parameters: • Name • Date • Time Click “Apply” to apply changes. 3.2.2.2 IP Page 32 4Gon www.4Gon.co.uk info@4gon.co.
Set ODU’s IP attributes for one of the 4 available IPs: • IP Address • IP Mask • Route (static route) • Destination (static route) • Destination Mask (static route) • Default IP Gateway • VLAN In order to change the default IP (IP #1, 192.168.0.1) click “Add” and enter the required values under IP index 1). Click “Apply” to apply changes. Note: once IP address changed you will lose the connection to the ODU.
3.2.2.3 Radio Set ODU’s radio parameters and check radio status: • Frequency [MHz] • Channel-width [MHz] • Role or Slave. In a link one side should be configured as Master and the second as Slave. Master • Transmit Asymmetry For symmetric configuration (50% for Tx and Rx) use 50tx-50rx. You may set the link to asymmetric configuration (75%/25%). In such case, set 75tx-25rx for the Master unit and 25tx-75rx for the Slave unit.
3.2.2.4 Ethernet Ports Set Eth1 and Eth2 ports configuration: • Admin (port enable) Up • or Down Auto-negotiation Enable • or Disable Speed Manually set the port’s speed (10/100/1000, HF/FD) when auto-negotiation disabled. Set speed to 1000xfd when SFP is used. Click “Apply” to apply changes. Default port configuration: RJ45, Auto-negotiation enabled. 3.2.2.
3.2.3.2 Inventory Check the Inventory list of the ODU, including the sub-parts and their information. 3.2.3.3 IP Set ODU’s IP attributes for one of the 4 available IPs: IP Address, IP Mask, Route (static route), Destination (static route), Destination Mask (static route), Default IP Gateway, and VLAN. In order to change or add an IP, click “Add” and enter the required values under the appropriate IP index). Click “Apply” to apply changes. Page 36 4Gon www.4Gon.co.uk info@4gon.co.
3.2.3.4 SNMP Set SNMP managers trap destination: destination IP address, port number and community. Up to 5 managers can be defined. Click “Apply” to apply changes. Page 37 4Gon www.4Gon.co.uk info@4gon.co.
3.2.4 Bridge Use the Bridge section to set VLANs and ports configuration. Networking configuration, including bridge management model, VLANs setup and configuration examples, is presented in chapter 4 “FibeAir 70 Network Configuration”. 3.2.5 Events Check current alarms and alarm log: 3.2.5.1 Alarms Currently active alarms. 3.2.5.2 Logs Alarm history log. Page 38 4Gon www.4Gon.co.uk info@4gon.co.
3.2.6 Radio Use the Radio section to set and check radio parameters and statistics: 3.2.6.1 Radio Set ODU’s radio parameters: • Frequency [MHz] • Channel-width [MHz] • Role – Master or Slave In a link one side should be configured as Master and the second as Slave. • Transmit Asymmetry For symmetric configuration (50% for Tx and Rx) use 50tx-50rx. You may set the link to asymmetric configuration (75%/25%). In such case, set 75tx-25rx for the Master unit and 25tx-75rx for the Slave unit.
Check ODU’s status: • Operational Status – Up or Down (radio link status) • Tx and Rx State – indicates Tx and Rx chains status • RSSI [dBm] – Receiver Signal Strengh Indicator • CINR [dB] – Carrier to Interference + Noise ratio. Radio link’s signal quality indication. For normal conditions CINR>13 indicates good signal level. • Ptx [dBm] – ODU’s monitored Tx power 3.2.6.2 Modulations Check ODU’s supported modulation profiles (loaded in factory.
3.2.6.3 RF Statistics Check RF statistics counters to identify radio errors: • Current – real time statistics counters since last clear. No errors on In Errored Octets, In Errored Packets and In Lost Packets indicate error-free operation of the radio link. • History –96 intervals of 15 minutes (total 24 hours) of the statistics counters. 3.2.6.4 Statistics Summary Check RSSI, CINR and Modulation history (graph and table).
3.2.7 Ethernet Interface Configuration Click the ODU’s Ethernet interfaces to configure and monitor the status of the Ethernet line interfaces (Eth1 and Eth2): 3.2.7.1 Admin Status Interface enable/disable: Up or Down. 3.2.7.2 Ethernet Type Interface type (RJ45 or SFP) and speed/duplex (when Auto Negotiation disabled): 10hd, 10fd, 100hd, 100fd, 1000hd, 1000fd, 1000xhd, 1000xfd. Set speed to 1000xfd when SFP is used. 3.2.7.3 Auto Negotiation Interface Auto Negotiation: Enabled or Disabled.
3.2.7.4 Loopback Set loopback timeout (in seconds) and loopback mode: Disabled,Internal,Internal-mac-swap,External,External-mac-swap. 3.2.7.5 Alarm Propagation Enable Alarm Propagation for radio and line faults (port shutdown). 3.2.7.6 Pipe To Set interface pipe mode, connecting one of the line interfaces (Eth1 or Eth2) to another interface (host, Eth0, Eth1, Eth2). Click “Apply” to apply changes. 3.2.7.7 Ethernet Statistics Check Ethernet interface statistics counters: 3.2.
3.2.8.2 Scripts The ODU supports running scripts. A script is a list of commands that runs locally on the ODU. Script output is displayed on a script output screen and its output can be copied and saved. 3.2.8.3 Software The FibeAir 70 system supports switching in real time between two distinct software versions. Because the System simultaneously maintains both an Active, running software version and a Standby, passive software version, an upgrade can be performed with minimal interruption of service.
Click “Add” to add a user and assign it to one of the user types: Type user Default Password N/A tech N/A super N/A admin admin 3.2.8.5 Access Rights Read only access, excluding the ability of viewing the user names, passwords and other security settings. Read only access to configuration settings, Ability to clear statistics, alarm and log lists, run diagnostics. Read-write access, except from the user names, passwords and other security settings.
3.3 ODU Setup using the CLI This section provides information on the configuration steps of the ODU be carried out after antennas alignment using the Command Line Interface (CLI). Initial configuration for each ODU is performed as follows: • Invoke the CLI using a standard SSH client. • Access the ODU using its default IP address. • Assign a network IP Address, Name and RF value for the ODU. • Verify ODU performance. Note: 3.3.
• Time FA-70> set system name Local_Site Local_Site> system date 2011.01.18 time 15:08:00 To check the System settings: Local_Site>show system system system system system system system system system system system system 3.3.3 description snmpid uptime contact name location voltage temperature date time cli-timeout : : : : : : : : : : : FA-70 1.3.6.1.4.1.31926 0000:00:05:10 undefined Local_Site undefined 55 39 2011.01.
To check the IP settings: Local_Site>show ip 3.3.4 ip ip ip ip ip ip ip 1 1 1 1 1 1 1 ip-addr mask route destination dst-mask default-ipgw vlan : : : : : : : 192.168.0.11 255.255.255.0 0.0.0.0 0.0.0.0 255.255.255.0 192.168.0.254 0 ip ip ip ip ip ip ip 4 4 1 1 1 1 1 ip-addr mask route destination dst-mask default-ipgw vlan : : : : : : : 172.16.100.1 255.255.255.0 0.0.0.0 0.0.0.0 255.255.255.0 0.0.0.
To check the available supported modulations: Local_Site>show modulation Modulation subchannels repetitions fec-rate cinr-low cinr-high qpsk 1 4 0.5 -128 12 qpsk 2 2 0.5 8 14 qpsk 4 1 0.
Local_Site>show rf statistics rf rf rf rf rf rf rf rf rf rf rf rf rf rf rf rf rf rf in-octets in-idle-octets in-good-octets in-errored-octets out-octets out-idle-octets in-pkts in-good-pkts in-errored-pkts in-lost-pkts out-pkts min-cinr max-cinr min-rssi max-rssi min-modulation max-modulation elapsed-time : : : : : : : : : : : : : : : : : : 32535265564 29775780985 9370230 0 30552267600 30531707551 129957 129452 0 0 231519 13 18 -56 -33 qpsk 2 2 0.5 qpsk 4 1 0.
3.3.5 Ethernet Interfaces The FibeAir 70 system consists of 4 Ethernet interfaces: • Host – management interface • Eth0 – radio interface • Eth1 – ODU interface, port 1 • Eth2 – ODU interface, port 2 Set Eth1 and Eth2 ports configuration, if desired configuration is different from default: • Admin (port enable) – Enable by default • Auto-negotiation – Enable by default • Speed Manually set the port’s speed (10/100/1000, HF/FD) when auto-negotiation disabled.
3.3.6 Save and Reset Save the new configuration using the copy command: Local_Site> copy running-configuration startup-configuration Saving the running (currently active) configuration will make it the default configuration that is available after a reset and upon startup. To exit the RF Alignment Mode, and after each change in the RF settings, perform a System Reset: Local_Site> reset system This command resets the ODU’s and readies the ODU for operation. Page 52 4Gon www.4Gon.co.uk info@4gon.co.
4 FibeAir 70 Network Configuration This chapter presents the FibeAir 70 bridge management model and describes the initial procedures for configuring the FibeAir 70 network. Topics covered here include: 4.1 • FibeAir 70 bridging model • VLANs and ports settings • FibeAir 70 network configuration examples FibeAir 70 Bridging Model Figure 4-1 shows the default bridge model when Provider Bridge Feature is enabled (by license).
Figure 4-1 Generic Model of the FibeAir 70 Bridge Each component acts as a virtual bridge. A component can have both external and internal ports. An external port name is identical to its interface name. An internal port name uses the name of its peer component. For example, as shown in Figure 4-1, when C-component 1 is connected to the S-component, the corresponding internal port in the C-component will be called s1 and in the S-component will be called c1.
4.2 Default Bridge Configuration The default bridge configuration (by license) is Provider Bridge disabled. This configuration allows configuration and monitoring of VLANs in the web-EMS only. When Provider Bridge license = Enable: VLANs configuration and monitoring available in CLI only (Bridge section will be grayed out in web-EMS). All advanced networking options require Provider Bridge license = Enable. 4.3 Bridge Configuration using the Web-EMS 4.3.
• When a packet is transmitted out of the port, VID=1 is removed (untagged on all ports). • All traffic (and management data) is transmitted to all ports (over VID 1). In addition, VID 4094 for IP address 4 (see 3.2.3.3) is defined on all ports but Eth0 (radio) – local management only (and not in-band over the radio). 4.3.2 Configuring VLAN and Port Click “Add” to add or edit VLANs: Page 56 4Gon www.4Gon.co.uk info@4gon.co.
Configure the following VLAN attributes: • VID – VLAN ID (or IDs) • FDB ID – enter 1 (in Provider Bridge configuration, up to 64 FDBs are available for different S-VLANs) • Egress Set – the ports this VLAN will be set to (Host – management, Eth0 – radio, Eth1 – ODU port 1, Eth2 – ODU port 2) • Untagged Set – set on what ports (subset of the ports defined in Egress Set) the packet will transmitted out untagged (VLAN removed).
Click “Edit” to edit the port and to change the PVID: 4.3.3 VLAN Statistics To check the VLAN statistics: Page 58 4Gon www.4Gon.co.uk info@4gon.co.
4.4 Bridge Configuration using the CLI In order to configure and monitor VLANs using the CLI, Provider Bridge license should be set to disable (CLI: set license provider-bridge disable). 4.4.
4.5 FibeAir 70 Network Configuration Examples This section provides examples of basic FibeAir-7 network configurations which can be useful when creating your local FibeAir 70 configuration. Note: 4.5.1 The following configuration example details the configuration settings when the Provider Bridge Feature is enabled (by license). For details, refer to Section 4.5.2.
set vlan c4 100 egress eth2,s1 untagged eth2 set vlan c2 100 egress eth0,s1 untagged none Assign VID=100 to port ETH2 and Host towards S1 (with Priority=7): set bridge-port c1 host pvid 100 prio 7 set bridge-port c4 eth2 pvid 100 prio 7 Disable port ETH1 capability to send untagged traffic on VID=1: set vlan c3 1 egress none untagged none Configuring Customer Ethernet Services and In-Band Management Connect ETH2, ETH0 (RF) and Host ports via S1 using VID=100.
Confirming the VLAN Configuration Enter the following command to confirm the new VLAN configuration: FA-70>show vlan all all component-id s1 c1 c1 c2 c2 c2 c2 c2 c3 c3 c3 c3 c4 c4 vid 1 1 100 1 100 110 120 130 1 110 120 130 1 100 fdb-id 1 1 1 1 1 1 1 1 1 1 1 1 1 1 egress c1,c2,c3,c4 host,s1 host,s1 eth0,s1 eth0,s1 eth0,s1 eth0,s1 eth0,s1 none eth1,s1 eth1,s1 eth1,s1 eth2,s1 eth2,s1 untagged c1,c2,c3,c4 host,s1 host eth0,s1 none none none none none none none none eth2,s1 eth2 Enter the following comman
Examining VLAN Statistics In the event of VLAN performance problems, ODU transmission can be monitored using the show vlan statistics command: FA-70>show vlan all all statistics component c1 c1 c2 c2 c2 c2 c2 c3 c3 c3 c3 c4 c4 4.5.
Note that customer Ethernet services from port ETH1 that arrive with different VLAN IDs and priorities will be transferred as-is. 4.5.3 Creating a Multiple Customer VLAN Configuration This VLAN configuration example is for FibeAir 70 sites serving multiple customers or service providers. It comprises: • Ten paired FibeAir 70 RF units (EH1 through EH10) using local and remote inband management VLAN (VID = 111). • Two separate, unique customer Ethernet VLANs (VIDs = 200-203).
set ip ip-addr 10.0.0.51 route 10.0.0.
set vlan c3 111 egress eth1, s1 set vlan s1 111 fdb-id 5 egress c1, eth0, eth2 Configure bridge port management: set bridge-port c1 s1 admit tagged filter enabled set bridge-port c1 host pvid 111 prio 6 admit untagged set bridge-port s1 c1 pvid 111 prio 6 Map the Management C-VLAN to the Management S-VLAN: set cvlan-reg c3 eth1 111 svid 111 Configure Customer VLANs: set vlan c3 200-203 egress eth1, s1 Configure Service VLAN: set vlan s1 1000 fdb-id 10 egress c3, eth2, eth0 Map the Customer VLANs to the
set bridge-port s1 c1 pvid 111 prio 6 Map Management C-VLAN to the Management S-VLAN: set cvlan-reg c3 eth1 111 svid 111 Configure Service VLAN: set vlan s1 2000 fdb-id 10 egress eth2, eth0 EH 4 Configuration Configure RF: set rf role master frequency 74000 mode adaptive Configure the IP address: set ip ip-addr 10.0.0.54 route 10.0.0.
EH 5 Configuration Configure RF: set rf role master frequency 74000 mode adaptive Configure the IP address: set ip ip-addr 10.0.0.55 route 10.0.0.
Configure Service VLANs: set vlan s1 2000 fdb-id 11 egress eth2, eth0 set vlan s1 1000 fdb-id 10 egress eth1, eth0 EH 7 Configuration Configure RF: set rf role master frequency 74000 mode adaptive Configure the IP address: set ip ip-addr 10.0.0.57 route 10.0.0.
Configure the IP address: set ip ip-addr 10.0.0.58 route 10.0.0.
set vlan c3 111 egress eth1, s1 set vlan s1 111 fdb-id 5 egress c1, c3, eth0 Configure bridge port management: set bridge-port c1 s1 admit tagged filter enabled set bridge-port c1 host pvid 111 prio 6 admit untagged set bridge-port s1 c1 pvid 111 prio 6 Configure Customer VLANs: set vlan c4 200-203 egress eth2, s1 Map Management C-VLAN to the Management S-VLAN: set cvlan-reg c3 eth1 111 svid 111 Configure Service VLAN: set vlan s1 2000 fdb-id 10 egress c4, eth0 Map the Customer VLANs to the Service VLA
Map Management C-VLAN to the Management S-VLAN: set cvlan-reg c3 eth1 111 svid 111 Configure Customer VLANs: set vlan c4 200-203 egress eth2, s1 Configure Service VLAN: set vlan s1 1000 fdb-id 10 egress c4, eth0 Map the Customer VLANs onto the Service VLAN: set cvlan-reg c4 eth2 200 svid 1000 set cvlan-reg c4 eth2 201 svid 1000 set cvlan-reg c4 eth2 202 svid 1000 set cvlan-reg c4 eth2 203 svid 1000 Page 72 4Gon www.4Gon.co.uk info@4gon.co.
The commissioning and acceptance procedure verifies the correct installation and the proper, safe, and robust operation of the FibeAir 70 RF link. Topics covered here include: 4.
4.6.2 RF Link Test This inspection verifies the RF link status, in accordance with Chapters 2 and 3 of this manual. 4.6.
4.
RF Link Tests Expected RSSI dBm dBm Measured RSSI dBm dBm Measured CINR dB dB Green “RF” led Yes No Yes No RF operational status Up Yes No Yes No BER test No errors BER______ Test duration _______ hours RF Statistics error counters clear Yes No errors BER______ Test duration _______ hours No Yes No Ethernet Services Tests Packet-Loss test Packet Analyzer No Packet-Loss SW-based VLAN Statistics dropped-packets counters clear No Packet-Loss Test duration _______ hours Test d
This chapter describes how to use the FibeAir 70 Command Line Interface (CLI) client to configure and maintain FibeAir 70 devices on your network. Topics covered here include: • Invoking the CLI • CLI command syntax • Referring to FibeAir 70 objects • Managing FibeAir 70 objects • Displaying FibeAir 70 objects • CLI help and auto completion • CLI error messages Hint: This chapter provides information and procedures on basic FibeAir 70 CLI operations.
4.9 CLI Command Syntax After invoking the CLI, the User inputs commands to the CLI. Each CLI command is submitted to the FibeAir 70 device for execution, after which a response is typically returned.
4.9.2 Common Syntax Rules This document uses the following notation conventions when presenting CLI usage examples. These syntax conventions are found in commands, index names, objects and attributes. Syntax 4.9.3 Meaning {a | b | c} One of the specified values must be entered on the command line The name of a required attribute, explained in an accompanying or referenced section. [name] The name of an optional attribute, explained in an accompanying or referenced section.
Convention Meaning A comma-separated list of external port names, e.g., host, eth0, eth1, eth2. Any combination of the names can be included in the list. (For details, see Section 4.9.6.) A list of ranges of VIDs from 1 to 4094. The notation covers commaseparated lists of the numbers within the specified range, as well a range of numbers separated by a hyphen, e.g., 5-25. (For details, see Section 0.) A list of ranges of FIDs from 1 to 64.
4.9.4 CLI Command Types The CLI uses a limited number of commands to create, maintain and monitor a FibeAir 70 configuration. To perform this operation… …use this CLI Command: Create, update or modify an object Set Display the characteristics or values of an object Show Reset or delete specified characteristics or values of an object Clear Reset the RF or System Reset The following sections describe the generic use of these routine CLI commands.
4.9.4.2 Show Commands The Show command is used to display the current characteristics and other values for a chosen object. The generic form the Show command is: show object-name [attribute-name] If a show command is entered in an incomplete fform, orm, when possible, the CLI will automatically complete missing object-ids with the keyword all, and missing attributes with the keyword info.
Line-by-line per attribute displays the objects in the form: : Note that multiple may be displayed using this form. The Table display method presents the information in blocks and omits the object name and IDs, as in the form: 4.9.4.3 Clear Commands The Clear command is used to reset or delet delete e the specified values for a chosen object.
Reset System Resetting the System reboots and reloads the currently saved Sys System tem startup configuration. FA-70>reset system Reset System is used for power up and is required after software upgrades. Note: 4.9.5 Resetting the System causes a service disruption of approximately 90 seconds in duration. Designating Objects in CLI Commands The CLI requires explicit identifiers to perform operations on the objects in an FibeAir 70 configuration. The User designates a specific object (e.g.
CLI Name Referenced Object eth0 The wireless port eth1 Wired Ethernet port eth2 Wired Ethernet port host Internal CPU s1 S-component 1 c1 C-component 1 c2 C-component 2 c3 C-component 3 c4 C-component 4 The CLI supports specifying a list of named objects by entering multiple comma-separated names.
Note that not every combination of keywords is valid. For example, the command bridgeport c1, c2 host is invalid, because two different C-components cannot be associated with the same port. 4.9.6.1 Designating Indexed Objects Countable FibeAir 70 CLI objects are specified by their unique identifying keyword, followed by the object’s index number. A VLAN is a typical, countable object. For example: vlan 230 refers to the VLAN that indexed to number 230.
More specifically: object 2, 9, 23-25 means the collection of double indexed objects: {2, 23}, {2, 24}, {2, 25}, {9, 23}, {9, 24}, {9, 25}. For show and clear commands it is possible to put the word all instead of either of indexes. For example: object 2, 9 all or object all 23-25 or object all all. For specific per-command definitions see 4.9.4 Page 87 4Gon www.4Gon.co.uk info@4gon.co.
4.10 Viewing the CLI Command History The FibeAir 70 CLI maintains a history of the 100 most recent commands that were entered by the User. This is especially useful when recalling long, complex or repetitive entries. To recall commands from the history buffer, the User can press the following keys: Keypress Result Up Arrow Recall commands in the history buffer, beginning with the most recent command. Press the key repeatedly to recall successively older commands.
4.11 Invoking CLI Help and Auto completion The FibeAir 70 CLI assists the User both actively and passively, using the following means: • The User can explicitly request syntax help on the command line. • The User can explicitly request auto completion assistance on the command line. • The CLI command interpreter always checks the validity and completeness of a string that is entered on the command line.
Automatically completes a specific command name. For example: FA-70> set vl FA-70> set vlan FA-70> se vl 33 e FA-70> set vlan 33 egress If more than one command matches the string that was entered by the User, the CLI indicates that an ambiguous command has been entered. Note that the autocompletion feature does not function for indexes, MAC addresses or IP addresses. ? or Help Returns a list of top-level CLI commands only. (without a string) Page 90 4Gon www.4Gon.co.uk info@4gon.
4.12 CLI Error Messages FibeAir 70 CLI issues three types of error messages: • %Ambiguous command. This error occurs when the command entered can only be partially interpreted. If possible, following the error message, a help syntax line is returned to assist the User in correcting the command, as described in Section 4.10.
4.13 Viewing the FibeAir 70 Statistics History The FibeAir 70 CLI enables viewing of standard operational and performance statistics for various objects in the System. View the statistics history using the show command: show
5 CLI Managed Object Reference This chapter describes all FibeAir 70 System objects that can be created, modified, displayed or deleted using the command line interface. Use Figure 5-1 to quickly identify and locate a specific FibeAir 70 object according to its logical function in the FibeAir 70 System. Figure 5-1 The FibeAir 70 CLI Object Model Page 93 4Gon www.4Gon.co.uk info@4gon.co.
5.1 System The System object provides access to general operating parameters of the device. The System object corresponds to the System Group MIB2 described in RFC-3418. 5.1.1 System Commands 5.1.1.1 Set Assign and modify device parameters using the Set command: set system [contact ] [name ] [location ] [date ] [time ] 5.1.1.
5.1.2 System Attributes 5.1.2.1 System Description Description A text string describing the entity. This value generally includes the full name and version identification of the system's hardware type, operatingsystem, and networking software. CLI Attribute Name Description SNMP Object ID sysDescr (1.3.6.1.2.1.1.1) Value Variable text Access RO Default EH-70 HW W.X SW Y.Z Where: W.X is the HW version and Y.Z is the SW version Dependencies 5.1.2.
5.1.2.3 System Up Time Description The length of time that has passed since the network management portion of the system was last re-initialized. CLI Attribute Name up-time SNMP Object ID sysUpTime (1.3.6.1.2.1.1.3) Value ddd:hh:mm:ss Where: ddd = decimal integer representing days (it can be an arbitrary number of digits) hh = two-digit decimal integer representing the hours of a day [0..23] mm = two-digit decimal integer representing minutes of an hour [0..
5.1.2.6 System Location Description The physical location of this node (e.g., 'telephone closet, 3rd floor' CLI Attribute Name location SNMP Object ID sysLocation (1.3.6.1.2.1.1.6) Value Up to 256 characters. If no system location exists, the value returns a zero-length string. Access RW Default "sysLocation undefined" Dependencies None 5.1.2.7 Input Voltage Description The system input voltage. CLI Attribute Name voltage SNMP Object ID CeragonSysVoltage (1.3.6.1.4.1.31926.1.
5.1.2.9 System Date and Time Description The host's local date and time of day. CLI Attribute Name date, time SNMP Object ID hrSystemDate (1.3.6.1.2.1.25.1.2) As defined in RFC 2790 Value yyyy-mm-dd hh:mm:ss Where: yyyy = year (0 – 9999) hh mm = month (1 – 12) mm = minute (0 – 60) dd = day (1 – 31) ss Access RW Default None Dependencies None = hour (0 – 24) = second (0 – 60) Page 98 4Gon www.4Gon.co.uk info@4gon.co.
5.2 Eth The Eth object provides access to Ethernet network-related device parameters. The Eth object corresponds to the Interface MIB2 described in RFC-2863. 5.2.1 Eth Commands Note: The Eth object is always followed by one or more name strings that correspond to ports or devices to be acted upon. In the commands below, this string is represented as . For more details on this convention, see Section 4.9.6., Designating Named Objects. 5.2.1.
5.2.1.3 Clear Reset selected attributes of the device using the Clear command: clear eth { | all} [{info | description | mtu | mac-addr | admin | operational | last-change | name | alias | eth-type | eth-act-type | auto-neg | statistics}] 5.2.2 Eth Attributes 5.2.2.1 Description Description A text string describing the interface. This value generally includes the manufacturer’s name, the product name and the interface hardware and software versions.
5.2.2.3 MAC Address Description The address of the interface at its protocol sub-layer. CLI Attribute Name mac-addr SNMP Object ID ifPhysAddress (1.3.6.1.2.1.2.2.1.6) Value host0 = (read from hardware) rf0 = + 1 eth1 = + 2 eth2 = + 3 Access RO Default NN-NN-NN-NN-NN-NN where NN is a hexadecimal number (for example 00-AF-DD-1E-2D-A3) Dependencies 5.2.2.
Default N/A Dependencies If the Administrative Status attribute (admin) is in the Down state, then the operational attribute should also be in the Down state. If the Administrative Status attribute (admin) changes to the Up state, then the operational attribute should also change to the Up state if the interface is ready to transmit and receive network traffic. it should remain in the Down state if and only if there is a fault condition that prevents the interface from going to the Up state. 5.2.2.
5.2.2.8 State Trap Description An integer that indicates whether linkUp/linkDown traps should be generated for this interface. CLI Attribute Name trap SNMP Object ID ifLinkDownTrapEnable (1.3.6.1.2.1.31.1.1.1.14) Value 1 = Enabled 2 = Disabled Access RW Default 1 = Enabled Dependencies None 5.2.2.9 Connector Description An integer that indicates whether the interface sublayer has a physical connector. CLI Attribute Name connector SNMP Object ID ifConnectorPresent (1.3.6.1.2.1.31.1.1.
5.2.2.11 Ethernet Type Description This object identifier represents the operational type of MAU that the administrator has assigned. As described below, the use of this attribute is limited when autonegotiation is enabled for the MAU. CLI Attribute Name eth-type SNMP Object ID ifMauDefaultType (1.3.6.1.2.1.26.2.1.1.11) Part of ifMauTable (1.3.6.1.2.1.26.2.1) Value The possible values are: 10hd dot3MauType10BaseTHD (1.3.6.1.2.1.26.4.10) 10fd dot3MauType10BaseTFD (1.3.6.1.2.1.26.4.
10hd dot3MauType10BaseTHD (1.3.6.1.2.1.26.4.10) 10fd dot3MauType10BaseTFD (1.3.6.1.2.1.26.4.11) 100hd dot3MauType100BaseTXHD (1.3.6.1.2.1.26.4.15) 100fd dot3MauType100BaseTXFD (1.3.6.1.2.1.26.4.16) 1000hd dot3MauType1000BaseTHD (1.3.6.1.2.1.26.4.29) 1000fd dot3MauType1000BaseTFD (1.3.6.1.2.1.26.4.30) 1000xhd dot3MauType1000BaseXHD (1.3.6.1.2.1.26.4.21) 1000xfd dot3MauType1000BaseXFD (1.3.6.1.2.1.26.4.22) Access RO Default 1000fd Dependencies None 5.2.2.
5.2.2.15 Loopback Timeout Description Loopback timeout, expressed in seconds CLI Attribute Name loopback-timeout SNMP Object ID N/A Value Integer Access RW Default Disabled Dependencies None 5.2.2.16 Alarm Propagation Mode Description Alarm propagation mode is used to define System behavior in case of a link failure CLI Attribute Name alarm-propagation SNMP Object ID N/A Value The possible alarm propagation values are: Disabled No propagation is performed.
Table 5-1 Statistics for the Eth Object Incoming Octets CLI Name Description SNMP Object ID in-octets The total number of octets received on the interface, including framing characters. ifInOctets The number of unicast packets received on the interface. ifInUcastPkts The number of packets which were chosen to be discarded due to RX FIFO full ifInDiscards The number of received erred packets. ifInErrors The total number of octets transmitted out of the interface, including framing characters.
5.3 Bridge The Bridge object provides access to the Bridge parameters. The Bridge object corresponds to the Bridge MIB described in IEEE8021-BRIDGE-MIB. 5.3.1 Bridge Commands Note: The Bridge object is always followed by one or more name strings that correspond to ports or devices to be acted upon. In the commands below, this string is represented as . For more details on this convention, see Section 4.9.6., Designating Named Objects. 5.3.1.
5.3.2 Bridge Attributes 5.3.2.1 Component ID Description The component identifier is used to distinguish between the multiple virtual bridge instances within a PBB. CLI Attribute Name N/A SNMP Object ID ieee8021BridgeBaseComponentId (1.3.111.2.802.1.1.2.1.1.1.1.1). Value 1 Access Not Accessible This attribute is used as the index key to ieee8021BridgeBaseTable (1.3.111.2.802.1.1.2.1.1) Default s1 Dependencies The component id = s1 cannot be supplied as argument when using the clear command.
5.4 Bridging Port The Bridging Port object provides access to port-wide definitions from the Bridge. The Bridging Port object corresponds to the Bridge MIB (RFC-4188) and the Bridge MIB Extensions (RFC-4363). 5.4.1 Bridging Port Commands When using the bridge-port commands, any combination of components and ports may be specified. However, only certain combinations will produce a result.
[admit untagged | tagged | all] [filter enabled | disabled] When the Provider Bridge feature is disabled, use the following syntax: set bridge-port [] [pvid ] [prio {0..7}] [admit untagged | tagged | all] [filter enabled | disabled] When the Provider Bridge feature is disabled can only include the external ports eth1, eth2, eth0 and Host. 5.4.1.2 Show Display bridging port attributes using the Show command.
5.4.2 Bridging Port Attributes 5.4.2.1 Component ID Description The component identifier is used to distinguish between the multiple virtual bridge instances within a PB. CLI Attribute Name N/A SNMP Object ID ieee8021BridgeBasePortComponentId (1.3.111.2.802.1.1.2.1.1.4.1.1) Value Access N/A Default N/A Dependencies Component identifiers must be defined in the Bridge Component table (See Section 5.3). 5.4.2.1.
Description The port-level VLAN ID that is assigned to untagged frames or PriorityTagged frames received on the port. CLI Attribute Name pvid SNMP Object ID ieee8021QBridgePvid (1.3.111.2.802.1.1.4.1.4.5.1.1) Value 1..4094 Access RW Default 1 Dependencies Each PVID must correspond to a valid VLAN on the corresponding component. In practice, this means that the VLAN must already be configured in the VLAN Table for the component before its VID can be assigned as the PVID for a port. 5.4.2.
Dependencies 5.4.2.4 If ingress filtering is enabled on the same port, then accepting untagged frames only is not compatible, since the combination effectively leads to discarding all frames on the port. (See Section 5.4.2.4.) Bridge Port Ingress Filtering Description The ingress filtering state of the port. When Enabled, the device discards incoming frames for VLANs that do not include the port in its Member Set. When Disabled, the device accepts all incoming frames to the port.
5.5 VLAN Common The VLAN Common object provides general information about VLAN bridges that are active in the network. Use this object to query general attributes which are common to multiple VLANs. 5.5.1 VLAN Common Commands 5.5.1.1 Show Display VLANs using the Show command: show vlan-common [{ | all} [{ info | version | max-vid | max-num | curr-num}]] 5.5.2 VLAN Common Attributes 5.5.2.
5.5.2.3 Maximum VLAN ID Description The maximum IEEE 802.1Q VLAN-ID that this device supports. CLI Attribute Name max-vid SNMP Object ID ieee8021QBridgeMaxVlanId (1.3.111.2.802.1.1.4.1.1.1.1.3) Value 1..4094 Access RO Default N/A Dependencies None 5.5.2.4 Maximum Number of VLANs Description The maximum number of IEEE 802.1Q VLANs that this device supports. CLI Attribute Name max-num SNMP Object ID ieee8021QBridgeMaxSupportedVlans (1.3.111.2.802.1.1.4.1.1.1.1.4) Value 1..
5.6 VLAN Table The VLAN Table object enables the management of VLANs by the CLI. VLAN definitions are stored in a table containing static configuration information for each VLAN that is configured into the device by local or network management. All VLAN Table entries are permanent and will be restored when the device is reset. This object corresponds to SNMP object qBridgeVlanStaticGroup dot1qVlanStaticTable. 5.6.1 VLAN Table Commands Note: 5.6.1.
When the Provider Bridge feature is enabled, use the following syntax: clear vlan { | all} { | all} [statistics] When the Provider Bridge feature is disabled, use the following syntax: clear vlan { | all} [statistics] • Before deleting a C-VLAN, verify that it is not being used as a key to the CVLAN Registration Table. Do not delete the C-VLAN if such an entry exists.
5.6.2 VLAN Table Attributes 5.6.2.1 Component Identifier Description The component identifier is used to distinguish between multiple virtual bridge instances within a PB. CLI Attribute Name N/A SNMP Object ID ieee8021QBridgeVlanStaticComponentId (1.3.111.2.802.1.1.4.1.4.3.1.1) Value Access N/A Default s1 Dependencies Component identifiers must be defined in the Bridge Component table (See Section 5.3). 5.6.2.2 VLAN ID Description The VLAN-ID referring to this VLAN.
5.6.2.4 Untagged Ports Set Description The set of ports that should transmit egress packets for this VLAN as untagged. This set is allowed only for S-VLANs. CLI Attribute Name Untagged SNMP Object ID ieee8021QBridgeVlanStaticUntaggedPorts (1.3.111.2.802.1.1.4.1.4.3.1.4) Value Access RC Default Empty Dependencies This set must be subset of the egress ports set (See Section 5.6.2.3). 5.6.2.5 FDB ID Description The ID of the filtering database used for this VLAN.
5.6.2.7 Per-VLAN Outgoing Packets Description The number of valid frames transmitted by this port to its segment from the local forwarding process for this VLAN. This object includes bridge management frames originated by this device that are classified as belonging to this VLAN (e.g., MMRP, but not MVRP or STP). CLI Attribute Name out-pkts SNMP Object ID ieee8021QBridgeTpVlanPortOutFrames (1.3.111.2.802.1.1.4.1.4.6.1.2) Value 0..264 Access RO Default N/A Dependencies N/A 5.6.2.
5.6.3.1 Description Description A textual string containing information about the interface. This string should include the name of the manufacturer, the product name and the version of the interface hardware/software. CLI Attribute Name N/A SNMP Object ID ifDescr (1.3.6.1.2.1.2.2.1.2) Value ASCII representation of the VLAN ID SNMP Access RO 5.6.3.2 Type Description The type of interface.
5.6.3.5 Administrative Status Description The desired state of the interface. CLI Attribute Name N/A SNMP Object ID ifAdminStatus (1.3.6.1.2.1.2.2.1.7) Value Up (1) SNMP Access RW (Only a single value is allowed.) 5.6.3.6 Operational Status Description The current operational state of the interface.
5.6.3.9 State Trap Description Indicates whether linkUp/linkDown traps should be generated for this interface. CLI Attribute Name N/A SNMP Object ID ifLinkDownTrapEnable (1.3.6.1.2.1.31.1.1.1.14) Value Disabled (2) SNMP Access RW (Only a single value is allowed.) 5.6.3.10 High Speed Indication Description An estimate of the interface's current bandwidth in units of 1,000,000 bits per second. CLI Attribute Name N/A SNMP Object ID ifHighSpeed (1.3.6.1.2.1.31.1.1.1.
5.6.3.13 Alias Description This object is an 'alias' name for the interface as specified by a network manager, and provides a non-volatile 'handle' for the interface. CLI Attribute Name N/A SNMP Object ID ifAlias (1.3.6.1.2.1.31.1.1.1.18) Value Zero-length string SNMP Access RW Page 125 4Gon www.4Gon.co.uk info@4gon.co.
5.7 C-VLAN Registration An element of the C-VID registration table accessed by PB C-VLAN component, Customer Edge Port bridge port number, and C-VID. Each element contains the mapping between a CVID and the S-VID which carries the service and booleans for handling untagged frames at the PEP and CEP. 5.7.1 C-VLAN Registration Commands 5.7.1.
5.7.1.3 Clear Delete C-VLAN Registration entries using the Clear command: clear cvlan-reg { | all} { | all} { | all} 5.7.2 C-VLAN Registration Attributes 5.7.2.1 Bridge Port Description The bridge port for the C-VLAN Registration entry. CLI Attribute Name N/A SNMP Object ID ieee8021BridgeBasePort (1.3.111.2.802.1.1.2.1.1.4.1.
5.7.2.3 S-VID Description The S-VID of this C-VLAN Registration entry. This value will be added to the C-tagged frames of the C-VID. (See Section 5.7.2.2.) CLI Attribute Name svlan SNMP Object ID ieee8021PbCVidRegistrationSVid (1.3.111.2.802.1.1.5.1.2.1.2) Value 1..4094 Access RC Default N/A Dependencies The VID must be defined in the VLAN Table for an S-component (See Section 5.6). 5.7.2.
5.8 PEP Virtual Port The PEP Virtual Port object specifies components of the PEP Table, which is used to configure ingress port filtering. PEP Table entries define traffic flows from the provider network to the customer edge port. The table is indexed by ComponentID and S-VID. The columns allow the default C-VID value and default User Priority to be specified and PEP's ingress filtering operation to be controlled. 5.8.1 PEP Virtual Port Commands 5.8.1.
[{all | } [{all | } [{info | cpvid | prio | admit | filter}]]]]. 5.8.1.3 Clear Delete PEP Virtual Port entries using the Clear command: clear pep-vp { | all} {s1 | all} { | all}. Page 130 4Gon www.4Gon.co.uk info@4gon.co.
5.8.2 PEP Virtual Port Attributes 5.8.2.1 Bridge Port Description The bridge port for the PEP Virtual Port entry. CLI Attribute Name bridge-port SNMP Object ID ieee8021BridgeBasePort (1.3.111.2.802.1.1.2.1.1.4.1.2) Value s1 Access N/A Default N/A Dependencies The Bridge Port specified in the command must be an internal port (PEP) that belongs to the corresponding C-component. 5.8.2.2 PEP S-VID Description The 12-bit S-VID that is associated with the PEP.
5.8.2.4 PEP Default User Priority Description An integer range 0-7 to be used for untagged frames received at the Provider Edge Port. CLI Attribute Name prio SNMP Object ID ieee8021PbEdgePortDefaultUserPriority (1.3.111.2.802.1.1.5.1.3.1.3) Value 0..7 Access RC Default None Dependencies None 5.8.2.5 PEP Acceptable Frame Types Description The frame types that will be accepted upon receipt at the PEP. CLI Attribute Name admit SNMP Object ID ieee8021PbEdgePortAcceptableFrameTypes (1.3.
5.9 S-VID Translation Table The S-VID Translation Table object is used to configure the VID Translation Table, which maintains a bi-directional mapping between a Local S-VID (used in data and protocol frames transmitted and received through a CNP or PNP) and a Relay S-VID (used by the filtering and forwarding process). Each VID Translation Table definition contains Component, Port, Local S-VID values and the Relay S-VID values for each specified S-VID.
5.9.1.2 Clear Delete S-VID Translation Table entries and clear their associated statistics using the Clear command: clear all} svid-xlat {s1 | all} { | all} { | 5.9.1.3 Show Display S-VID Translation Table entries using the Show command: show svid-xlat [{s1 | all} [{ | all} [{ | all} [info]]]] Page 134 4Gon www.4Gon.co.uk info@4gon.co.
5.9.2 VID Translation Table Attributes 5.9.2.1 Bridge Port Description The bridge port for the VID Translation Table entry. CLI Attribute Name N/A SNMP Object ID ieee8021BridgeBasePort (1.3.111.2.802.1.1.2.1.1.4.1.2) Value host, eth0, eth1, eth2 Access N/A Default N/A Dependencies The Bridge Port specified in the command must belong to a corresponding S-component. 5.9.2.2 Local S-VID Description The internal S-VID on received (transmitted) at the ISS of a CNP or PNP.
5.9.2.3 Relay S-VID Description The translated S-VID delivered (received) over the EISS from a CNP or PNP. CLI Attribute Name relay-svid SNMP Object ID ieee8021PbVidTranslationRelayVid (1.3.111.2.802.1.1.5.1.1.1.2) Value 1..4094 Access RC Default N/A Dependencies The VID must be defined in the VLAN Table (See Section 5.6) and the Bridge Port specified in the command must belong to the S-component.
5.10 Forwarding Data Base (FDB) The FDB object enables access to general parameters of the FDB Address Table, which specifies configuration and control information for each Filtering Database currently operating on the device. Entries in the FDB Address Table appear automatically when VLANs are assigned FDB IDs in the VLAN Table (See Section 5.6). The system maintains 64 permanent instances of the FDB object. This object corresponds to SNMP ieee8021QBridgeFdbTable object. 5.10.1 FDB Commands 5.10.1.
5.10.2.2 FDB ID Description The identity of this Forwarding Database. The system maintains 64 permanent instances of the FDB object. CLI Attribute Name fdb-id SNMP Object ID ieee8021QBridgeFdbId (1.3.111.2.802.1.1.2.1.2.1.1.2) It is an index to ieee8021QBridgeFdbTable (1.3.111.2.802.1.1.2.1.2.1) Value 1..64 Access N/A Default 1 Dependencies None 5.10.2.3 Aging Time Description The timeout period in seconds for aging out dynamically-learned forwarding information.
5.10.2.5 Dynamic Count Description The current number of dynamic entries in this Forwarding Database. The value of this object is incremented each time an entry is created or deleted View the value of this object using the show command together with the statistics qualifier CLI Attribute Name num-of-dynamic SNMP Object ID ieee8021QBridgeFdbDynamicCount (1.3.111.2.802.1.1.2.1.2.1.1.3) It belongs to ieee8021QBridgeFdbTable (1.3.111.2.802.1.1.2.1.2.
5.11 FDB Address Table The FDB Address Table object contains information about unicast entries for which the device has forwarding and/or filtering information. This information is used by the transparent bridging function when determining how to propagate a received frame. Entries in the FDB Address Table appear automatically when VLANs are assigned FDB IDs in the VLAN Table (See Section 5.6). This object corresponds to SNMP ieee8021QBridgeTpFdbTable object. 5.11.1 FDB Address Table Commands 5.11.1.
clear fdb-table {s1 | all} { | all} { | all} Note that deleting an FDB Address Table entry will fail if its port exists in the FDB with “self” as the assigned status. Page 141 4Gon www.4Gon.co.uk info@4gon.co.
5.11.2 FDB Address Table Attributes 5.11.2.1 Bridge Component ID Description The component identifier is used to distinguish between the multiple virtual bridge instances within a PBB. CLI Attribute Name N/A SNMP Object ID ieee8021QBridgeFdbComponentId (1.3.111.2.802.1.1.2.1.2.1.1.1) It is an index to ieee8021QBridgeTpFdbTable (1.3.111.2.802.1.1.4.1.2.2) and also to ieee8021QBridgeFdbTable (1.3.111.2.802.1.1.2.1.2.
5.11.2.4 FDB Port Description The bridge port from which the MAC address has been learned. CLI Attribute Name port SNMP Object ID ieee8021QBridgeTpFdbPort (1.3.111.2.802.1.1.4.1.2.2.1.2) It belongs to ieee8021QBridgeTpFdbTable (1.3.111.2.802.1.1.4.1.2.2) Value host, eth0, eth1, eth2, c1, c2, c3, c4, s1 Access RC Default N/A Dependencies None 5.11.2.5 Address Entry Status Description The status of this FDB Address Table entry.
5.12 IP The IP object is a table that maintains addressing information relevant to an entity's interfaces. This table is use used d to describe the default routers known to the entity. Currently, only one default route is supported. This object corresponds to SNMP MIB object ipAddressGroup ipAddressTable (RFC-4293). 5.12.1 IP Commands Note: 5.12.1.1 When DHCP is enabled, the configuration received from the network will override all manually-configured parameters.
5.12.1.2 Show Display IP entries using the Show command: show ip [ [{route | mask | vlan}]] 5.12.1.3 Clear Delete IP entries and clear their associated statistics using the Clear command: clear ip Page 145 4Gon www.4Gon.co.uk info@4gon.co.
5.12.2 IP Attributes 5.12.2.1 IP Index CLI Only object Description The index to the IP addres table SNMP Object ID N/A SNMP Syntax N/A Access N/A CLI Name none Value 1..4 CLI Commands set ip ip-addr 5.12.2.2 IP Address Description The IP address to which this entry's addressing information pertains. The address type of this object is specified in ipAddressAddrType. SNMP Object ID 1.3.6.1.2.1.4.34.1.
CLI Syntax ip address in the form X.X.X.X where X is a decimal number from 0 to 255 (for example 10.0.15.74) Access NA Default 0.0.0.0 CLI Commands set ip route 5.12.2.5 VLAN CLI Only object Description VLAN assigned to the IP. SNMP Object ID N/A SNMP Name N/A Access RC CLI Name vlan Value 0..
5.13 ARP The ARP object is a translation table that is used for mapping between IP addresses and physical addresses. This object corresponds to SNMP MIB object ipNetToPhysicalTable (RFC-4293). 5.13.1 ARP Commands 5.13.1.1 Set Create and modify ARP entries using the Set command: set arp [ip-address ] If the ARP entry does not already exist, the Set command creates it and assigns the attributes specified.
5.13.2 ARP Attributes 5.13.2.1 ARP Interface The index value that uniquely identifies the interface for this entry. Description The interface identified here is identical to that of the MIB's ifIndex. CLI Attribute Name interface SNMP Object ID ipNetToPhysicalIfIndex (1.3.6.1.2.1.4.35.1.1) Value 1..4 Access NA Default 1 Dependencies None 5.13.2.2 ARP IP Address Description The IP Address that corresponds to the media-dependent physical address.
5.14 RF The RF object corresponds to definitions in the private Ceragon SNMP MIB (1.3.6.1.4.1.31926.1). 5.14.1 RF Commands 5.14.1.1 Set Create and modify RF device characteristics using the Set command: set rf [num-of-channels 1..2] [frequency 0 | 50000..80000] [role master | slave] [mode adaptive | static | alignment] [rx-ber-test disable | enable] [tx-ber-test disable | enable] [rx-link-id ] [tx-link-id ] [cinr-low -127..127] [cinr-interval 0..
5.14.2 RF Attributes 5.14.2.1 Number of Channels Description The maximum allowed bandwidth, expressed in MHz. CLI Attribute Name num-of-channels SNMP Object ID rfNumOfChannels (1.3.6.1.4.1.31926.2.1.1.2) Value 1..2 Access RW Default 2 Dependencies None 5.14.2.2 Channel Width Description The channel width, expressed in MHz. CLI Attribute Name channel-width SNMP Object ID rfChannelWidth (1.3.6.1.4.1.31926.2.1.1.3) Value 250 Access RO Default N/A Dependencies None 5.14.2.
Dependencies 5.14.2.5 None Mode Selector Description Specifies the current RF device operating mode. The available modes are: adaptive, static or alignment. CLI Attribute Name mode SNMP Object ID rfModeSelector (1.3.6.1.4.1.31926.2.1.1.
5.14.2.7 CINR Interval Description The interval used to determine the value for CINR, expressed in milliseconds. CLI Attribute Name cinr-interval SNMP Object ID rfCinrInterval (1.3.6.1.4.1.31926.2.1.1.15) Value 0..2000 Access RW Default 0 Dependencies None 5.14.2.8 RSSI Interval Description The interval used to determine the value for RSSI, expressed in milliseconds. CLI Attribute Name rssi-interval SNMP Object ID rfRssiInterval(1.3.6.1.4.1.31926.2.1.1.16) Value 0..
Dependencies 5.14.2.11 None RX State Description An integer that specifies the current state of the RF receive link. CLI Attribute Name rx-state SNMP Object ID rfRxState (1.3.6.1.4.1.31926.2.1.1.25) Value 1 = Sync 2 = Search countdown 3 = Found countdown 4 = Normal Access RO Default N/A Dependencies None 5.14.2.12 TX State Description An integer that specifies the current state of the RF transmit link. CLI Attribute Name tx-state SNMP Object ID rfTxState (1.3.6.1.4.1.31926.2.
This object is accessible via SNMP Only Description Average carrier to interference noise ratio [-6..30] SNMP Object ID rfAverageCinr (1.3.6.1.4.1.31926.2.1.1.18) SNMP Syntax integer Access RO 5.14.2.15 Average RSSI This object is accessible via SNMP Only Description Average received signal strength indication, measured in DB. [-100..-60] SNMP Object ID rfAverageRssi (1.3.6.1.4.1.31926.2.1.1.19) SNMP Syntax integer Access RO 5.14.2.
Wherein: mod Modulation type. {QPSK, QAM16, QAM64} scnum The number of subchannels [1..4] rep Repetition {1, 2, 4} fec FEC {0.5, 0.67, 0.8} frame The frame number to be used for the execution of the new modulation (only in static mode) The mode must be present in the Modulation Table 5.14.2.19 Encryption Description RF Encryption Mode. SNMP Object ID TBD Syntax {disabled | static-key} Access RW Default disabled Dependencies Visible only to admin user (?). 5.14.2.
Table 5-2 summarizes and describes all RF object statistics. Table 5-2 Statistics for the RF Object CLI Name Description SNMP Object ID Incoming Octets in-octets The total number of octets received from the RF link. rfInOctets (1.3.6.1.4.1.31926.2.2.1.1) Incoming Idle Octets in-idle-octets The total number of octets received from the RF link while idle. rfInIdleOctets (1.3.6.1.4.1.31926.2.2.1.2) Incoming Good Octets in-good-octets The number of good octets received from the RF link.
Table 5-3 Statistics History for the RF Object usrHistoryObjectIndex usrHistoryObjectVariable 1 rfInOctets (1.3.6.1.4.1.31926.2.2.1.1) 2 rfInIdleOctets (1.3.6.1.4.1.31926.2.2.1.2) 3 rfInGoodOctets (1.3.6.1.4.1.31926.2.2.1.3) 4 rfInErroredOctets (1.3.6.1.4.1.31926.2.2.1.4) 5 rfOutOctets (1.3.6.1.4.1.31926.2.2.1.5) 6 rfOutIdleOctets (1.3.6.1.4.1.31926.2.2.1.6) 7 rfInPkts (1.3.6.1.4.1.31926.2.2.1.7) 8 rfInGoodPkts (1.3.6.1.4.1.31926.2.2.1.8) 9 rfInErroredPkts (1.3.6.1.4.1.31926.2.2.1.
6 Performing Advanced CLI Operations This chapter describes the advanced use of the FibeAir 70 Command Line Interface (CLI) client. Prior to performing operations that are described here, it is recommended that the User be completely familiar with basic FibeAir 70 CLI commands and object operations.
6.1 Configuration Files The FibeAir 70 System supports the use of stored network configurations. Generally, a stored configuration is automatically loaded on System startup or following a System reset. 6.1.1 Saving Configurations A stored configuration is created by saving the currently active (running) configuration as the default configuration. Note: The running configuration FibeAir 70 is not automatically saved in non-volatile RAM.
6.2 Rollback Operations The FibeAir 70 system supports rolling back of network configurations. A rollback is a safety measure to prevent unwanted System changes in the event that a loss of communication occurs while performing configuration activities. The Rollback timeout function reloads the saved startup configuration in the event that no command is entered within a predefined timeout period.
In response, the System will display the requested rollback values. 6.3 Software Upgrade The FibeAir 70 system supports switching in real time between two distinct software versions. Because the System simultaneously maintains both an Active, running software version and a Standby, passive software version, an upgrade can be performed with minimal interruption of service. Flash Banks and Software Images Figure 6-1 shows the relationship between flash banks and software images in the FibeAir 70 system.
The software version is followed by the creation date and time of the version. The first digit of the version number represents the major version number, the second digit represents the minor version number, the third digit represents the SVN revision, and the fourth digit represents the version build number. 6.3.1.
If no accept sw is entered before the accept-timeout-sec period ends (See Section 6.3.1.3), then the System will Reset and wake up with software version image that is stored in the Active flash bank. Effectively, this means that the software version rolls back. Note that such a rollback will also be performed if a Reset occurs (for whatever reason) before the accept sw command is entered. 6.4 Ceragon File System (CFS) FibeAir 70 supports the use of pre-composed, multiple-line command scripts.
Since, currently there is no DNS; the location is specified as IP Address in the dotted notation. ftp://liberty:secret@127.23.46.17/mill-config 6.4.2.2 Specifying Local Files Use the [prefix:[directory/]]filename syntax to specify a file located on the device specified by prefix. For example, flash:backup-config specifies the file named backup-config in the configs directory of Flash memory. Some devices do not support directories. 6.4.2.
Command Purpose del works only for flash; available only for root, admin and super; 6.4.3.2 Displaying the List of Stored Files The command dir displays the list of the stored files in the form of table: < time> Wherein: 6.4.4 Mnemonic Description Num The sequential number size File size in bytes date Storage date time Storage time name File name Examples Copying file demo.txt from ftp server (server’s IP address – 192.168.0.
FA-70>dir flash: Num Size Date Time Name ---------------------------------------- 6.5 1 2 02.03.2011 14:59:32 demo.txt 2 1035 23.02.2011 09:35:11 finallog 3 6122 24.02.2011 11:06:32 rf.ini 4 8 12.02.2011 21:20:43 rftype_cfg 5 5613 02.03.2011 08:51:19 startup-configuration.txt 6 566 02.03.2011 08:51:19 startup-debug-configuration.txt 7 5688 02.03.2011 16:51:45 scripts/clear_statistics 8 2121 25.02.2011 08:50:24 scripts/qos-dscp 9 2117 24.02.
6.5.2 Running Scripts Execute scripts using the Run command: run script In response, the System will execute the script filename that is specified. The System can use an auto completion mechanism to search in the local directory for script files. Entering a search string, followed by a after the run script command invokes auto complete. 6.5.3 Adding Scripts To add a script to the ODU, edit it in a text file. The script should consist valid CLI commands.
6.5.5 Deleting Scripts Delete scripts from flash:scripts using the Del command: FA-70>del flash:scripts/DemoScript.txt Page 169 4Gon www.4Gon.co.uk info@4gon.co.
6.6 System Event and Alarm Handling The FibeAir 70 system supports logging history of standard network events and alarms. Hint: For detailed definitions of System Events and Alarms, and instructions on how to use them in diagnosing FibeAir 70 system problems, see Section 7.4. 6.6.1 Event and Alarm Commands 6.6.1.
In response, all active System logs are cleared. Page 171 4Gon www.4Gon.co.uk info@4gon.co.
6.7 Physical Inventory The FibeAir 70 objects described here correspond to the Entity MIB defined in RFC 4133. The tables implemented are: entPhysicalTable (1.3.6.1.2.1.47.1.1.1) 6.7.1 Physical Inventory Commands 6.7.1.
6.7.2 Physical Inventory Attributes 6.7.2.1 Inventory Index Description The index for the table entry. CLI Attribute Name none. SNMP Object ID entPhysicalIndex (1.3.6.1.2.1.47.1.1.1.1.1) SNMP Syntax integer32 (1..2147483647) CLI Syntax integer Access N/A (index) CLI Commands show inventory set inventory 6.7.2.2 Physical Descriptor Description A textual description of physical entity.
6.7.2.4 Class Description An indication of the general hardware type of the physical entity. If no appropriate standard registration identifier exists for this physical entity, then the value 'other(1)' is returned. If the value is unknown by this agent, then the value 'unknown(2)' is returned. CLI Attribute Name class SNMP Object ID entPhysicalClass (1.3.6.1.2.1.47.1.1.1.1.5) SNMP Syntax INTEGER { other(1), unknown(2), chassis(3), backplane(4), container(5), -- e.g.
6.7.2.6 Physical Name Description The textual name of the physical entity. The value of this object should be the name of the component as assigned by the local device and should be suitable for use in commands entered at the device's `console'. This might be a text name (e.g., `console') or a simple component number (e.g., port or module number, such as `1'), depending on the physical component naming syntax of the device.
6.7.2.7 Physical Hardware Revision Description The vendor-specific hardware revision string for the physical entity. The preferred value is the hardware revision identifier actually printed on the component itself (if present). Note that if revision information is stored internally in a non-printable (e.g., binary) format, then the agent must convert such information to a printable format, in an implementation-specific manner.
CLI Syntax character string Access RO CLI Commands show inventory sw-rev 6.7.2.10 Physical Serial Number The vendor-specific serial number string for the physical entity. The preferred value is the serial number string actually printed on the component itself (if present). Description Not every physical component will have a serial number, or even need one. Physical entities for which the associated value of the entPhysicalIsFRU object is equal to 'false(2)' (e.g.
6.7.2.12 Physical Model Name Description The vendor-specific model name identifier string associated with this physical component. The preferred value is the customer-visible part number, which may be printed on the component itself. If the model name string associated with the physical component is unknown to the agent, then this object will contain a zero-length string. CLI Attribute Name model-name SNMP Object ID entPhysicalModelName (1.3.6.1.2.1.47.1.1.1.1.
6.7.3 Physical Inventory Assignments Hierarchy Figure 6-2 shows all physical inventory entities and their relationship. Figure 6-2 Physical Inventory Hierarchy Scheme 6.7.3.
6.7.3.2 Antenna Attribute Value Inventory Index 2 Descriptor “Ceragon Antenna” Contained In 1 Class other Parent Relative Position 0 Name “Antenna” Hardware Revision empty Firmware Revision empty Software Revision empty Serial Number empty Manufacturer Name “Ceragon” Model Name empty Field Replaceable Unit Indicator not-replaceable 6.7.3.
Model Name empty Field Replaceable Unit Indicator not-replaceable 6.7.3.4 Base Band Board Attribute Value Inventory Index 4 Descriptor “Ceragon FA-70 Base Band Board” Contained In 1 Class container Parent Relative Position 2 Name “Base Band Board” Hardware Revision Firmware Revision empty Software Revision empty Serial Number Manufacturer Name “Ceragon” Model Name empty Field Replaceable Unit Indicator not-replaceable 6.7.3.
Software Revision empty Serial Number empty Manufacturer Name “Ceragon” Model Name empty Field Replaceable Unit Indicator not-replaceable 6.7.3.
Name “CPLD” Hardware Revision empty Firmware Revision Software Revision empty Serial Number empty Manufacturer Name “Ceragon” Model Name empty Field Replaceable Unit Indicator not-replaceable 6.7.3.
Contained In 4 Class module Parent Relative Position 5 Name “Boot” Hardware Revision empty Firmware Revision empty Software Revision Serial Number empty Manufacturer Name “Ceragon” Model Name empty Field Replaceable Unit Indicator not-replaceable Page 184 4Gon www.4Gon.co.uk info@4gon.co.
6.8 Maintenance Domain 6.8.1 MD Commands Note: MD CLI commands are available only when the FibeAir 70 Provider Bridge feature is enabled. 6.8.1.1 Set set cfm-md [format ] [name ] [level ] [mhf-creation ] [mhfid-permission ] Note that md-name must be unique in the system. 6.8.1.2 Show show cfm-md { | all} {format | name | level | mhfid-permission | info} 6.8.1.
6.8.2.2 Name Description Each Maintenance Domain has a unique name. This facilitates easy identification of administrative responsibility for each Maintenance Domain. SNMP Object ID dot1agCfmMdName (1.3.111.2.802.1.1.8.1.5.2.1.1) CLI Attribute Name name CLI Syntax According to the format as described in Section 6.8.2.3 Access RC Default Empty CLI Commands show cfm-md name set cfm-md name 6.8.2.
6.8.2.5 MHF Creation Description Enumerated value indicating whether the management entity can create MHFs (MIP Half Function) for this Maintenance Domain. SNMP Object ID dot1agCfmMdMhfCreation (1.3.111.2.802.1.1.8.1.5.2.1.5) CLI Attribute Name mhf-creation CLI Syntax {none | default | explicit} Access RC Default None CLI Commands show cfm-md mhf-creation set cfm-md mhf-creation none 6.8.2.
6.9 Maintenance Association 6.9.1 MA Commands Note: 6.9.1.1 MA CLI commands are available only when the FibeAir 70 Provider Bridge feature is enabled. Set set cfm-ma [format ] [name ] [interval ] Note that ma-name is mandatory in the Set command. The name must be unique in the system. 6.9.1.2 Show show cfm-ma { | all} { | all} {name | component | interval | info} 6.9.1.
6.9.2.2 MA Index Description Index of the Maintenance Association table (dot1agCfmMdMaNextIndex) needs to be inspected to find an available index for row-creation. SNMP Object ID dot1agCfmMaIndex (1.3.111.2.802.1.1.8.1.6.1.1.1) Access N/A Dependencies An MA Index entry cannot be deleted if it is used as the key in MA, MEP, Received CCM Presentation, Peer MEP Create or LTR DB. 6.9.2.3 MA Format Description A value that represents a type (and the resulting format) of the Maintenance Domain Name.
6.9.2.5 Interval Description The interval to be used between CCM transmissions by all MEPs in the MA. SNMP Object ID 1.3.111.2.802.1.1.8.1.6.1.1.4 (dot1agCfmMaNetCcmInterval) CLI Attribute Name interval CLI Syntax {3.3ms | 10ms | 100ms | 1s | 10s | 1min | 10min} Access RC Default 1s CLI Commands show cfm-ma interval set cfm-ma interval 10ms Page 190 4Gon www.4Gon.co.uk info@4gon.co.
6.10 Component Maintenance Association 6.10.1 MA-COMP Commands Note: MA-COMP CLI commands are available only when the FibeAir 70 Provider Bridge feature is enabled. 6.10.1.1 Set set cfm-ma-comp [vlan ] [mhf-creation ] [mhfid-permission ] 6.10.1.2 Show show cfm-ma-comp { | all} { | all} {vlan | mhf-creation | mhfid-permission | info} 6.10.1.
6.10.2.3 MA Index This is the same attribute as the one described in Section 6.9.2.2. Page 192 4Gon www.4Gon.co.uk info@4gon.co.
6.10.2.4 Service Selector Description Service Selector identifier to which the MP is attached, or 0, if none. The type of the Service Selector is defined by the value of ieee8021CfmMaCompPrimarySelectorType. In the current implementation the type is always VLAN ID. Thus the Service Selector is the Primary VLAN ID with which the Maintenance Association is associated, or 0 if the MA is not attached to any VID. SNMP Object ID ieee8021CfmMaCompPrimarySelectorOrNone (1.3.111.2.802.1.1.8.1.6.4.1.
6.11 Maintenance End Point 6.11.1 MEP Commands Note: 6.11.1.1 MEP CLI commands are available only when the FibeAir 70 Provider Bridge feature is enabled. Set set cfm-mep [interface ] [dir {down | up}] [vlan {1..4094}] [admin-state {active | inactive}] [cci {enabled | disabled}] [msg-prio {0..7}] [low-defect ] [alarmtime {250..1000}] [reset-time {250..
6.11.2.3 MEPID Description An integer that is unique for all the Maintenance End Points (MEPs) in the same Maintenance Association that identifies a specific Maintenance Association End Point. SNMP Object ID 1.3.111.2.802.1.1.8.1.7.1.1.
6.11.2.5 Direction Description The direction in which the MEP is facing on the Bridge Port. SNMP Object ID 1.3.111.2.802.1.1.8.1.7.1.1.3 (dot1agCfmMepDirection) CLI Attribute Name dir CLI Syntax {up | down} Access RC Default down CLI Commands set cfm-mep dir up | down show cfm-mep dir Dependencies 6.11.2.6 Only one MEP can be defined for the same combination of Interface, Direction and Primary VLAN.
6.11.2.8 CCI Description If set to True, the MEP will generate CCM messages. SNMP Object ID 1.3.111.2.802.1.1.8.1.7.1.1.7 (dot1agCfmMepCciEnabled) CLI Attribute Name cci CLI Syntax {enabled | disabled} Access RC Default disabled CLI Commands set cfm-mep cci enabled show cfm-mep cci 6.11.2.9 Message Priority Description The priority value for CCMs and LTMs transmitted by the MEP.
6.11.2.11 Alarm Time Description The time that a defect must be present before a fault alarm is issued SNMP Object ID 1.3.111.2.802.1.1.8.1.7.1.1.11 (dot1agCfmMepFngAlarmTime) CLI Attribute Name alarm-time CLI Syntax 250..000 Access RC Default 250 CLI Commands set cfm-mep alarm-time
6.11.2.14 LBM Destination MEPID Description The Maintenance Association End Point Identifier of another MEP in the same Maintenance Association to which the LBM is to be sent. This address will be used if the value of the column dot1agCfmMepTransmitLbmDestIsMepId is True. SNMP Object ID 1.3.111.2.802.1.1.8.1.7.1.1.
6.11.2.17 LBM Data TLV Description An arbitrary amount of data to be included in the Data TLV, if the Data TLV is selected to be sent. SNMP Object ID 1.3.111.2.802.1.1.8.1.7.1.1.31 (dot1agCfmMepTransmitLbmDataTlv) CLI Attribute Name lbm-tx-data CLI Syntax String of hexadecimal digits. Two digits constitute an octet thus the length must be even.
6.11.2.20 LTM Destination MAC Address Description A unicast destination MAC address specifying the target MAC Address Field to be transmitted. This address will be used if the value of the column dot1agCfmMepTransmitLtmTargetIsMepId is False. SNMP Object ID 1.3.111.2.802.1.1.8.1.7.1.1.
6.11.2.23 LTM Transmit TTL Description The TTL field indicates the number of hops remaining to the LTM. Decremented by 1 by each Linktrace Responder that handles the LTM. The value returned in the LTR is one less than that received in the LTM. If the LTM TTL is 0 or 1, the LTM is not forwarded to the next hop, and if 0, no LTR is generated SNMP Object ID 1.3.111.2.802.1.1.8.1.7.1.1.41 (dot1agCfmMepTransmitLtmTtl) CLI Attribute Name ltm-tx-ttl CLI Syntax 0..
6.11.2.25 Transmit LTM Status Description A Boolean flag set to True by the Bridge Port to indicate that another LTM may be transmitted. Reset to False by the MEP Linktrace Initiator State Machine. Setting the status to True (tx-pending) will initiate LTM sending. Only one message is sent, after which the value automatically changes to False (txidle). Note that if the Number of LTM to Transmit is zero the status turns to False (tx-idle) immediately. SNMP Object ID 1.3.111.2.802.1.1.8.1.7.1.1.
6.11.3.3 Highest Priority Defect Description The highest priority defect that has been present since the MEPs Fault notification Generator State Machine was last in the reset state. SNMP Object ID 1.3.111.2.802.1.1.8.1.7.1.1.13 (dot1agCfmMepHighestPrDefect) CLI Attribute Name high-defect CLI Syntax {none | rdi-ccm | mac-status | remote-ccm | error-ccm | xcon-ccm} Access RO 6.11.3.4 MEP Defects Description A vector of Boolean error conditions from IEEE 802.
6.11.3.7 LBM Transmit Result Description Indicates the result of the operation. SNMP Object ID 1.3.111.2.802.1.1.8.1.7.1.1.34 (dot1agCfmMepTransmitLbmResultOK) CLI Attribute Name lbm-tx-result CLI Syntax {ok | not-ok} Access RO 6.11.3.8 LBM Transmit Sequence Number Description The Loopback Transaction Identifier (dot1agCfmMepNextLbmTransId) of the first LBM sent. The value returned is undefined if dot1agCfmMepTransmitLbmResultOK is False. SNMP Object ID 1.3.111.2.802.1.1.8.1.7.1.1.
Access 6.11.3.12 RO Transmit LBR Counter Description Total number of Loopback Replies transmitted. SNMP Object ID 1.3.111.2.802.1.1.8.1.7.1.1.25 (dot1agCfmMepLbrOut) CLI Attribute Name lbr-tx CLI Syntax Integer Access RO 6.11.3.13 LTM Next Sequence Number Description Next transaction identifier/sequence number to be sent in a Linktrace message. This sequence number can be zero when it wraps around. SNMP Object ID 1.3.111.2.802.1.1.8.1.7.1.1.
CLI Attribute Name ltm-tx-sn CLI Syntax Integer Access RO Page 207 4Gon www.4Gon.co.uk info@4gon.co.
6.12 Received CCM Presentation 6.12.1 Parsing and Displaying CCM Messages The following information is displayed per CCM message stored: Eth Source Address VLAN Priority (PCP) Drop Eligibility VLAN ID MD Level Version RDI CCM Interval Sequence Number Counters: TxFCf, RxFCb, TxFCb If present: Sender Chassis Subtype and ID Management Address Domain Management Address Port Status -- {blocked | up} (according to IEEE 802.
6.12.2.3 MEPID This is the same attribute as the one described in Section 6.11.2.3. An entry cannot be created if a corresponding MEPID does not exist. 6.12.2.4 Last Error Condition CCM Description The last-received CCM that triggered an DefErrorCCM fault. SNMP Object ID 1.3.111.2.802.1.1.8.1.7.1.1.15 (dot1agCfmMepErrorCcmLastFailure) CLI Attribute Name last-error-ccm CLI Syntax According to Section 6.12.1 Access RO CLI Commands show cfm-ccm last-error-ccm 6.12.2.
6.13 Peer MEP Create 6.13.1 Peer MEP Create Commands Note: 6.13.1.1 Peer MEP Create CLI commands are available only when the FibeAir 70 Provider Bridge feature is enabled. Set A Peer MEP entry is created with the Set command: set cfm-peer-mep-create The Set command causes automatic creation of entries in the Peer MEP DB for all MEPIDs that have entries in MEP Table and this Peer MEP ID. 6.13.1.
6.13.2.3 Peer MEPID Description Integer identifying a specific Peer Maintenance Association End Point. SNMP Object ID dot1agCfmMaMepListIdentifier (1.3.111.2.802.1.1.8.1.6.3.1.1) CLI Syntax 1..8191 Access N/A CLI Commands set cfm-peer-mep-create show cfm-peer-mep-create clear cfm-peer-mep-create Page 211 4Gon www.4Gon.co.uk info@4gon.co.
6.14 Peer MEP DB 6.14.1 Peer MEP DB Commands Note: Peer MEP DB CLI commands are available only when the FibeAir 70 Provider Bridge feature is enabled. 6.14.1.1 Show Peer MEP DB information is displayed using the following Show command: show cfm-peer-mep-db [{ | all} [{ | all} [{ | all} [{ | all}}]]] The information displayed is only for Peer MEPs which have been reported.
6.14.2.5 Peer MEP State Description The operational state of the remote MEP IFF State machines. This state machine monitors the reception of valid CCMs from a remote MEP with a specific MEPID. It uses a timer that expires in 3.5 times the length of time indicated by the dot1agCfmMaNetCcmInterval object. SNMP Object ID 1.3.111.2.802.1.1.8.1.7.3.1.
6.14.2.8 Remote Defect Indication Description State of the RDI bit in the last received CCM. On corresponds to True. SNMP Object ID 1.3.111.2.802.1.1.8.1.7.3.1.5 (dot1agCfmMepDbRdi) CLI Attribute Name rdi CLI Syntax {on | off} Access RO CLI Commands show cfm-peer-mep-db 6.14.2.
6.14.2.11 Peer Chassis ID Subtype Description This object specifies the format of the Chassis ID received in the last CCM. SNMP Object ID 1.3.111.2.802.1.1.8.1.7.3.1.8 (dot1agCfmMepDbChassisIdSubtype) CLI Attribute Name chassis-id-subtype CLI Syntax {chassis-comp | if-alias | port-comp | mac | net-addr | if-name} Access RO CLI Commands show cfm-peer-mep-db 6.14.2.12 Peer Chassis ID Description The Chassis ID.
6.14.2.14 Management Address Description The TAddress that can be used to access the SNMP agent of the system transmitting the CCM, received in the CCM Sender ID TLV from that system. If the related object dot1agCfmMepDbManAddressDomain contains the value 'zeroDotZero', this object dot1agCfmMepDbManAddress must have a zero-length OCTET STRING as a value. SNMP Object ID 1.3.111.2.802.1.1.8.1.7.3.1.11 (dot1agCfmMepDbManAddress) CLI Attribute Name mng-addr CLI Syntax IP Address – dotted notation.
6.15 LTR DB 6.15.1.1 LTR Storage Overview The LTRs that arrive are stored on per-MEP basis in the LTR database, as shown in Figure 6-3. { [MD Name], MA Name, MEP ID } LTR (SN = X) LTR (SN = X+1) LTR (SN = X) LTR (SN = X+1) ... LTR (SN = X+n) LTR (SN = X+n) LTR (SN = X+1) Figure 6-3. Per-MEP LTR Storage Structure The LTRs are stored in the ascending sequence number order and the LTRs with the same sequence number (i.e. replies to the same LTM) are grouped together.
It is possible to specify more than one SN in the command by designating indexed objects (See Section 04.9.6.1). 6.15.3 LTR DB Attributes 6.15.3.1 MD Index This is the same attribute as the one described in Section 6.8.2.1. An entry cannot be created if a corresponding MD Index does not exist. 6.15.3.2 MA Index This is the same attribute as the one described in Section 6.9.2.2. An entry cannot be created if a corresponding MA Index does not exist. 6.15.3.
6.15.3.6 LTR Forwarded Indicator Description Indicates if a LTM was forwarded by the responding MP, as returned in the 'FwdYes' flag of the flags field. SNMP Object ID 1.3.111.2.802.1.1.8.1.7.2.1.4 (dot1agCfmLtrForwarded) CLI Attribute Name ltr-forward CLI Syntax {forwarded | not-forwarded} Access RO CLI Commands show cfm ltr-db {} | all 6.15.3.7 LTR Relay Indicator Description Possible values the Relay action field can take. SNMP Object ID 1.3.111.2.802.1.1.
6.15.3.10 LTR Management Address Domain Description The TDomain that identifies the type and format of the related dot1agCfmMepDbManAddress object, used to access the SNMP agent of the system transmitting the LTR. SNMP Object ID 1.3.111.2.802.1.1.8.1.7.2.1.11 (dot1agCfmLtrManAddressDomain) CLI Attribute Name mng-addr-domain CLI Syntax {snmp-udp, snmp-ieee802} Access RO CLI Commands show cfm ltr-db {} | all 6.15.3.
6.15.3.13 LTR Ingress MAC Address Description MAC address returned in the ingress MAC address field. If the dot1agCfmLtrIngress object contains the value ingNoTlv(0), then the contents of this object are meaningless. SNMP Object ID 1.3.111.2.802.1.1.8.1.7.2.1.
show cfm ltr-db {} | all CLI Commands 6.15.3.17 LTR Egress MAC Address Description MAC address returned in the ingress MAC address field. If the dot1agCfmLtrIngress object contains the value ergNoTlv(0), then the contents of this object are meaningless. SNMP Object ID 1.3.111.2.802.1.1.8.1.7.2.1.
CLI Syntax {on | off} Access RO CLI Commands show ltr-db {} | all 6.15.3.21 LTR Last Egress Identifier Description An octet field holding the Last Egress Identifier returned in the LTR Egress Identifier TLV of the LTR. The Last Egress Identifier identifies the MEP Linktrace Initiator that originated, or the Linktrace Responder that forwarded, the LTM to which this LTR is the response. This is the same value as the Egress Identifier TLV of that LTM. SNMP Object ID 1.
6.16 Outgoing Queues 6.16.1 Outgoing Queues Commands 6.16.1.1 Show Display the Queue statistics using Show command: show out-queue {{eth0, eth1, eth2, rf} | all} {1..8 | all} statistics In response the software displays counters of all queues.
6.16.2 Outgoing Queue Attributes 6.16.2.1 Interface Name Description Interface name SNMP Object ID TBD CLI Syntax {eth0 | eth1 | eth2 | rf} | all Access N/A CLI Commands show out-queue {{eth0, eth1, eth2, rf} | all} {1..8 | all} statistics 6.16.2.2 Queue ID Description Queue ID SNMP Object ID TBD CLI Syntax Range from 1 to 8 Access N/A CLI Commands show queue {{eth0, eth1, eth2, rf} | all} {1..8 | all} statistics 6.16.2.
6.17 Incoming Queues Currently Incoming Queues are defined only for rf. However, the design should take into account the possibility that the other interfaces will also have incoming queues and their statistics may be different from rf’s 6.17.1 Incoming Queues Commands 6.17.1.1 Show Display the Queue statistics using the Show command: show in-queue {rf | all} {1..4 | all} statistics In response the software displays counters of all queues.
6.17.2 Incoming Queues Attributes 6.17.2.1 Interface Name Description Interface name SNMP Object ID TBD CLI Syntax rf (currently only one, but may be extended in the future) Access N/A CLI Commands show in-queue {rf | all} {1..4 | all} statistics 6.17.2.2 Queue ID Description Queue ID SNMP Object ID TBD CLI Syntax Range from 1 to 4 Access N/A CLI Commands show in-queue 6.17.2.3 {rf | all} {1..
6.17.2.5 6.18 Lost Frame Counter Description The counter of the per-Q lost rx frames SNMP Object ID TBD CLI Syntax lost 0..264 Access RO CLI Commands show queue {rf | all} {1..
7 FibeAir 70 Diagnostics The FibeAir 70 System’s highly reliable and easy-to-use radio link features a wide range of built-in indicators and diagnostic tools designed to allow a User to quickly evaluate a link’s performance identify operating faults and resolve them. The general diagnostics process for a FibeAir 70 link is to identify whether there is a problem that needs to be addressed, to isolate the root cause of the problem, and to implement the steps that are required to solve the problem.
Define the problem as either a customer-impact type (for example, loss of element management, or no Ethernet services over the link) or a product-related type (for example, a link is down or an ODU does not power up). Check and Gather Relevant Information Examining the link’s status indications will provide both current and historical information regarding the link’s performance and alarms. Indications include ODU LEDs, System Alarms and System Statistics.
7.3 FibeAir 70 ODU LEDs The following table lists the possible status of all LEDs, together with a description for purposes of diagnostics.
7.4 FibeAir 70 System Alarms and Events The following table lists all System Alarms and Events, together with their severity, possible cause and corrective actions. Indication Link Down Classification and Severity Alarm High Temperature High Alarm Medium Explanation The communication link (either the RF or one of the Ethernet ports) is not operational. The ODU temperature has exceeded a predefined threshold. Probable Cause Ethernet: Ethernet: 1) A cable is disconnected.
Indication Classification and Severity Explanation Probable Cause Corrective Actions Cold Start Event The ODU is reinitializating due to a Power-Up or Reset action. N/A N/A Link Up Event The communication link (either the RF or one of the Ethernet ports) is operational. N/A N/A Modulation Change Event The modulation setting for the RF link (currently in Adaptive mode) has changed. N/A N/A Synthesizer Locked Event The synthesizer has been locked.
Indication Change Classification and Severity Explanation Probable Cause Corrective Actions FibeAir 70 system has changed. Page 234 4Gon www.4Gon.co.uk info@4gon.co.
7.5 FibeAir 70 System Statistics The FibeAir 70 system uses advanced RF and Ethernet counters to provide real-time performance statistics for radio transmission activities, Ethernet ports and VLAN traffic. The following statistics enable quick analysis of system and component performance in support of troubleshooting and diagnostics. Hint: For general details on the objects and attributes appearing below, see their explanations in Chapter 5. 7.5.
The RF transmission quality indicators are rf in-errored-pkts and rf in-lost-pkts. The advancement of these statistics indicates that there are error/lost packets in the network and that radio transmission is not error-free (i.e., there is a problem). For detailed explanations of all RF statistics, see Table 5-2. Page 236 4Gon www.4Gon.co.uk info@4gon.co.
7.5.
7.5.3 Ethernet Statistics Statistics counters are displayed per Ethernet port.
7.6 FibeAir 70 System Loopbacks The FibeAir 70 radio uses Ethernet and RF loopbacks designed to enable fault isolation and Ethernet service performance testing. • Ethernet Loopback. Internal and external loops are performed on the interface, testing the local ODU, the radio link and the remote ODU. • RF Loopback. External loopb is performed on the RF interface of the switch.
When testing a link from one side (Local), External Line loopback should be applied on the Local unit. Loopback can be applied separately for ETH1 and ETH2. To set Ethernet External Loopback Loopback can be set with or without MAC Address swap. Set the loopback mode to external for the desired Ethernet port and set the loopbacktimeout in seconds: set eth eth1 loopback-timeout 300 set eth eth1 loopback-mode external-mac-swap To clear the Loopback set eth eth1 loopback-mode disable 7.6.1.
The Ethernet traffic from the Customer’s end-equipment or Ethernet analyzer is looped at the Ethernet interface of the remote ODU, enabling testing of the connection (cable/Fiber), the interface between end-equipment and the ODU, both local and remote ODUs, and the radio transmission. Loopback can be applied separately for ETH1 and ETH2. To set Ethernet Internal Line Loopback Loopback can be set with or without MAC Address swap.
