iConverter Network OAM Application Example

The self-managed iConverter 10/100M and iConverter GX/TM media converters offer the Operations, Administration and Maintenance (OAM) features required to provide a managed demarcation point for Metropolitan Broadband and Enterprise/Campus networks. The 10/100M and GX/TM feature built-in management, complete configuration access, status monitoring, Port MIB Statistics and trap reporting of iConverter modules installed in the chassis at the demarcation point.

These OAM-capable converters can be configured to operate as standalone or multi-module Network Interface Devices (NIDs). The standalone NID provides fibre access with a single, managed copper UTP port. The 10/100M and GX/TM can also be combined with other iConverter modules in a 2 or 5-Module Chassis NID that provides fibre access with multiple fibre and copper ports for customers at a Multiple Tenant Unit (MTU) or end users at an Enterprise department. The 10/100M and GX/TM can be managed with IP-based management or with a secure IP-less management channel.

The IP-based management capability can be accessed via Telnet or SNMP-based management software such as Omnitron's NetOutlook . Tag VLAN can be used to protect this management traffic by prioritizing and isolating it from the user traffic at the demarcation point. This configuration is best suited for networks already using VLAN management. The 10/100M and GX/TM are IEEE802.1Q compliant and are compatible with other VLAN-compliant hardware. When deployed utilizing the secure IP-less management channel, the OAM-capable converter at the demarcation point is securely managed by its fibre link partner (bookend converter) located at the Network Core. Management traffic on the user data lines is IP-less, and carried on a securely encrypted data channel. The IP address of the Management Station is not used on the user network and is isolated by the iConverter Network Management Module (NMM) in the chassis at the Network Core. This protects the management from unauthorized access and Denial of Service attacks. The chassis at the Network Core requires only a single IP address to manage itself and all of the connected remote chassis managed by the secure IP-less channel. This configuration is best suited for networks that have a separate secured network for management traffic, or when management IP addresses are at a premium.