Alcatel Lucent OmniSwitch 6850E Stacking Operations and Troubleshooting

Alcatel Lucent OmniSwitch 6850E Stacking and High Availability Operations Manual

In the medium to large access layer, aggregation layer, and even small core scenarios of enterprise level park networks, the Alcatel Lucent OmniSwitch 6850E series has become a trusted fixed configuration gigabit switch for network engineers due to its line speed IPv4/IPv6 forwarding, modular redundant power supply, flexible PoE+power supply, and rich security policies. However, even the most reliable hardware is inevitably prone to problems such as link oscillation, power supply abnormalities, stack splitting, or configuration errors. This article is based on the hardware architecture of OmniSwitch 6850E and the characteristics of AOS software. It systematically outlines the key points of the entire process from model selection, stack cluster construction, power redundancy design to daily fault location and recovery, providing a professional guide that can be immediately mastered for frontline operations and maintenance.

Model Overview and Selection Decision Tree

The OmniSwitch 6850E family offers 24/48 port copper cable models (including PoE and non PoE), full fiber models (U24X), and comes standard with two 10GBase CX4 stacking/expansion interfaces. By installing OS6-XNI-U2 modules, an additional 2 SFP+10G ports can be added, allowing the entire machine to achieve up to 4 10G uplinks.

Key selection elements:

Port density and PoE budget: Non PoE models (OS6850E-24/48/24X/48X) are suitable for regular data access; The PoE models (P24/P48/P24X/P48X) comply with 802.3af/at, with a maximum of 30W per port. The total budget depends on the power module provided (see below).

Upward speed: All "X" models come with 2 10G SFP+ports by default; Non X models need to obtain an additional 2 10G ports by connecting XNI-U2 modules through the CX-4 interface, in order to achieve 4 × 10G uplink.

Full fiber model: OS6850E-U24X provides 24 SFP ports (supporting 100/1000Base X) and 2 combo ports, suitable for long-distance fiber to desktop or aggregation.

Selection tip: If there is a possibility of upgrading PoE devices in the future, it is recommended to directly choose a PoE model and pair it with a high-power power supply (such as OS6850E-BPPX, 900W AC, which can provide a 780W PoE budget) to avoid replacing the chassis later.

Initial power on and automation configuration

OmniSwitch 6850E supports multiple rapid deployment methods, significantly reducing manual intervention:

Zero contact configuration: Automatically obtain IP and configuration files through DHCP (Option 60/66/67), and automatically pull boot.cfg from TFTP/FTP/SFTP servers after device startup.

USB local import: Save the configuration file to a USB drive, insert it into the device's USB port, and execute copy USB-Flash0:/boot.cfg running config, suitable for deployment in secure areas.

CLI and WebView: Provides familiar AOS command lines and built-in web graphic management tools, supporting HTTPS access.

Engineering suggestion: When configuring for the first time, be sure to change the default password, set the system name and location, and enable NTP synchronization (ntp server<ip>) to ensure accurate log timestamps.

Stacking Cluster Construction and Elastic Design

The OmniSwitch 6850E can be stacked with two CX-4 ports (located on the back panel) or an optional XNI-U2 module SFP+port, supporting up to 8 devices to be virtually one logical switch. The stacked bidirectional total bandwidth is 40 Gbps (full duplex), and it can achieve cross device link aggregation and redundancy.

Standard stacking steps:

Physical connection: Use stacked cables (CX-4 copper cables or SFP+optical fibers) to connect the stacking ports of each unit in a circular topology to avoid single point failures.

Assign Stack ID: Assign a unique number to each member using the seven segment LED display on the front panel or the command stack set ID<1-8>.

Election of primary/backup: The system automatically selects the primary based on priority (default 128) and MAC address, which can be adjusted through stack set priority<value>.

Verification status: Execute the show stack topology to check the health of the links and ensure that all members are in the RUNNING state.

Advanced features:

Remote stacking: Supports fiber optic stacking up to 10 km, suitable for unified management between multiple floors or park buildings.

Split stack protection: If the stack link breaks, the system automatically detects and forms two independent stacks, while using MSTP or ring network protection to avoid broadcast storms.

In Service Software Upgrade (ISSU): seamlessly upgrade AOS between primary and backup members, with business interruption time controlled in milliseconds.

Common malfunction: If members cannot join, first check if the software version (show version) is consistent; Next, check the stack port negotiation status (show stack link) to confirm that the SFP+module speed matches (10G or 1G must be consistent).

Power redundancy architecture and power supply planning

The OmniSwitch 6850E adopts a modular hot swappable power supply, supporting AC, DC, and high-power PoE power supply. The power module is located on the back of the device and does not need to be powered off during replacement (in dual power configuration).

Comparison Table of Power Supply Selection (Key Data):

Power supply model, input type, output power, PoE budget size (width x depth x height)

OS6850E-BP (AC 126W) AC 126W (system) without 16 × 17.5 × 4.4 cm

OS6850E-BP-D (DC 120W) DC-48V 120W (system) None as above

OS6850E-BPP (360W AC) AC 360W (system+PoE) 240W Same as above

OS6850E-BPPH (510W AC) AC 510W (system+PoE) 390W 32 × 17.5 × 4.4 cm

OS6850E-BPPX (900W AC) AC 900W (system+PoE) 780W 32 × 17.5 × 4.4 cm

Deployment suggestion:

Non PoE models must be equipped with at least one BP or BP-D; If redundancy is required, install a second one of the same model.

The PoE model should be selected based on the total power of the powered equipment, either BPPH (390W) or BPPX (780W). For example, if a 48 port PoE model is connected to 20 IP phones (7W each) and 10 APs (15W each), the total demand is about 290W, and BPPH is sufficient; If connecting a PTZ camera (25W), BPPX must be selected.

For scenarios where the depth of the cabinet is limited, the power module can be remotely installed in the power tray (BPS) through an extension cable, reducing the depth of the body (the body is only 27 cm, and the total depth after power on is 44.6 cm).

Redundant configuration: OmniSwitch BPS (Backup Power Shelf) can provide centralized backup power for up to 8 devices simultaneously, supporting full backup or single power backup modes. Suitable for multi device environments with limited rack space.

Power troubleshooting: If the system reports a red PWR LED or abnormal show power display, first check the power cord connection and input voltage; If it still fails, the faulty module can be directly hot unplugged and the backup module can be replaced in a dual power system. Note that replacing the power supply of PoE models does not affect data forwarding, but PoE power supply may be temporarily interrupted (which needs to be operated in the maintenance window).

Deep configuration of security policies

The OmniSwitch 6850E has a built-in Access Guardian framework that provides fine-grained access control based on user identity, enabling BYOD secure access without the need for additional hardware.

Key functions enabled:

802.1X+MAC authentication: Supports multi client mode, allowing coexistence of 802.1X hosts and MAC authentication devices on the same port. Configuration example:

text

interface gigabitethernet 1/1/1

authentication port-control auto

authentication multi-client

mac-authentication enabled

User Network Profile (UNP): The ADIUS server returns the UNP name, and the switch dynamically issues VLAN, ACL, bandwidth, and HIC (Endpoint Compliance) policies to enable policy compliance when users move.

DHCP Snooping+ARP Protection: Enable IP DHCP Snooping and IP ARP Inspection to prevent IP/MAC spoofing.

Traffic Anomaly Detection (TAD): The built-in engine monitors typical traffic patterns of worm viruses and can automatically close ports or alert network administrators.

BPDU blocking and Root Guard: Enable span tree BPDU filter and span tree root guard on the access port to prevent network loopback caused by users connecting to the switch privately.

Maintenance points: Regularly test the reachability of the radius server (test radius server<name>) and audit the TACACS+command authorization logs to ensure compliance.

Systematic positioning of common fault scenarios

6.1 Port unable to UP (copper/fiber optic)

Copper cable: First check the auto negotiation (default enabled), use TDR (Time Domain Reflectometry) to locate the cable breakpoint or short circuit point: TDR cable diagnostics interface gi 1/1/1, the system will return the distance and fault type (open circuit, short circuit, impedance abnormality).

Fiber optic: Check the recognition status of SFP module (show sfp), read DDM data (show sfp ddm), and check whether the optical power, temperature, and bias current exceed the limit. If the light attenuation is too large, clean the fiber optic connector or replace the module.

Protocol layer: If the port is err disable due to BPDU protection or loop detection, use errdisable recovery or manually shut down/no shutdown for recovery.

6.2 Stacking Splitting or Offline Members

Check the status of the stack link (show stack link). If a link is down, try unplugging the cable or replacing the SFP+module.

If there are two Primary instances in the stack, you can use the stack split recovery command to force a merge, but make sure that the stack IDs do not conflict.

Check the system log (show log) for any "stack topology change" events and locate the source of the fault based on the time point.

6.3 Abnormal PoE power supply

Check the total power usage (show poe), and if it exceeds the budget, the high priority port will automatically power off. Adjust port priority {critical | high | low} or add power modules.

If a single port is not powered, check if the port is configured with POE disable or if the powered device exceeds the maximum power of the port (default 30W, adjustable).

Use LLDP Power via MDI TLV to negotiate actual power requirements with devices and achieve dynamic allocation.

6.4 Routing Protocol Neighbor Loss (OSPF/BGP)

Firstly, verify the physical link and IP connectivity (ping neighbors).

Check the VRF configuration (if multiple VRFs are enabled) and confirm that the interface belongs to the correct VRF.

For BGP, check the show BGP summary and if the neighbor status is Idle or Active, check if TCP port 179 is blocked by ACL.

To quickly detect link failures using BFD (Bidirectional Forwarding Detection), it is necessary to enable both the interface and routing protocol simultaneously.

6.5 Software upgrade failure or startup crash

The device flash stores dual images (primary/backup) and dual configuration files. If the new image cannot start, enter boot system backup rollback at the boot prompt.

If the device enters miniboot, the image can be reloaded through XMODEM or USB.

Before upgrading, be sure to back up the current configuration (copy running config) tftp://... ）And read the section on configuration command changes in the version release notes.

Monitoring and Daily Inspection

Environmental monitoring: Regularly perform show temperature checks to check the internal temperature (normal range 0-45 ℃), and show fans to confirm fan operation (noise<48 dB for all models).

Centralized log management: Configure the Syslog server with a minimum level of info, and focus on filtering err and critic messages.

Performance baseline: Utilizing sFlow v5 and RMON to collect port traffic and error counts, establishing a baseline facilitates rapid identification of abnormal surges or packet losses.

MTBF reference: The MTBF of non PoE models can reach over 240000 hours (such as 272970 hours for OS6850E-24), while the MTBF of PoE models is about 160000 to 180000 hours, but the power fan still needs to be replaced on time (usually 5 years).

Expansion features: Metropolitan Ethernet and VRF

The "M" model (this series does not have a separate M suffix, but all 6850Es support Metro features and require corresponding licenses) supports IEEE 802.1ad QinQ, ITU-T Y.1731 performance measurement, G.8032 ring protection (<50ms convergence), and MAC Forced Forwarding (RFC 4562). For service providers or large park edges, these features can be enabled to achieve flexible layer 2 VPN and multi tenant isolation.

At the same time, hardware VRF supports virtualizing a switch into multiple independent routing domains, which is suitable for multi department or multi customer isolation and reduces hardware costs. During configuration, attention should be paid to using static routing or policy routing for inter VRF leakage.