This material is protected by the copyright laws of the United States and other countries. It may not be reproduced, distributed, or altered in
any fashion by any entity (either internal or external to Lucent Technologies), except in accordance with applicable agreements, contracts, or
licensing, without the express written consent of Lucent Technologies. For permission to reproduce or distribute, please email your request to
techcomm@lucent.com.
Notice
Every effort was made to ensure that the information in this document was complete and accurate at the time of printing, but information is
subject to change.
European Community (EC) RTTE compliance
Hereby, Lucent Technologies, declares that the equipment documented in this publication is in compliance with the essential requirements and other relevant provisions of the Radio and Telecommunications Technical Equipment (RTTE) Directive 1999/5/EC.
To view the official Declaration of Conformity certificate for this equipment, according to EN 45014, access the Lucent INS online documentation
library at http://www.lucentdocs.com/ins.
Safety, compliance, and warranty Information
Before handling any Lucent Access Networks hardware product, read the Edge Access and Broadband Access Safety and Compliance Guide included
in your product package. See that guide also to determine how products comply with the electromagnetic interference (EMI) and network
compatibility requirements of your country. See the warranty card included in your product package for the limited warranty that Lucent
Technologies provides for its products.
Security statement
In rare instances, unauthorized individuals make connections to the telecommunications network through the use of access features.
Trademarks
Lucent, the Lucent logo, and all Lucent brand and product names are trademarks or registered trademarks of Lucent Technologies Inc. Other
brand and product names are trademarks of their respective holders.
Ordering Information
You can order the most up-to-date product information and computer-based training online at http://www.lucentdocs.com/bookstore.
Feedback
Lucent Technologies appreciates customer comments about this manual. Please send them to techcomm@lucent.com.
Lucent Technologies
Customer Service
Product and service information, and software upgrades, are available 24 hours a day.
Technical assistance options accommodate varying levels of urgency.
Finding information and software
To obtain software upgrades, release notes, and addenda for this product, log in to
Lucent OnLine Customer Support at http://www.lucent.com/support.
Lucent OnLine Customer Support also provides technical information, product
information, and descriptions of available services. The center is open 24 hours a day,
seven days a week. Log in and select a service.
Obtaining technical assistance
Lucent OnLine Customer Support at http://www.lucent.com/support provides access
to technical support. You can obtain technical assistance through email or the
Internet, or by telephone. If you need assistance, make sure that you have the
following information available:
Customer Service
■Active service or maintenance contract number, entitlement ID, or site ID
■Product name, model, and serial number
■Software version
■Software and hardware options If supplied by your carrier, service profile
identifiers (SPIDs) associated with your line
■Your local telephone company’s switch type and operating mode, such as AT&T,
5ESS Custom, or Northern Telecom National ISDN-1
■Whether you are routing or bridging with your Lucent product
■Type of computer you are using
■Description of the problem
Obtaining assistance through email or the Internet
If your services agreement allows, you can communicate directly with a technical
engineer through Email Technical Support or a Live Chat. Select one of these sites
when you log in to http://www.lucent.com/support.
Calling the technical assistance center (TAC)
If you cannot find an answer through the tools and information of Lucent OnLine
Customer Support or if you have a very urgent need, contact TAC. Access Lucent
OnLine Customer Support at http://www.lucent.com/support and click Contact Us
for a list of telephone numbers inside and outside the United States.
Alternatively, call 1-866-LUCENT8 (1-866-582-3688) from any location in North
America for a menu of Lucent services. Or call +1 510-747-2000 for an operator. You
must have an active services agreement or contract.
Stinger® IP2000 Configuration Guide iii
Contents
Customer Service ........................................................................................................iii
About This Guide ...............................................................................xv
What is in this guide ..................................................................................................xv
Table A-8Current level of support for PIMv2 MIB tables............................... A-29
Stinger® IP2000 Configuration Guide xiii
About This Guide
A Stinger unit with the IP2000 control module (a Stinger IP2000) supports identical
Asynchronous Transfer Mode (ATM) capabilities to those in Stinger units with the
standard control module. In addition, a Stinger IP2000 can terminate IP traffic and
forward it across a built-in Gigabit Ethernet interface.
Note Instructions for installing and configuring the management functions of the
IP2000 are found in the Getting Started Guide for your Stinger platform.
What is in this guide
This guide focuses on the aspects of Stinger configuration that are specific to IP2000
control module capabilities. To fully configure the system for both ATM and IP
capabilities, use this guide with the Stinger ATM Configuration Guide.
Note You can configure the amount of bandwidth allocated to LIM interfaces and
control modules for carrying upstream traffic. For details about that aspect of using
the IP2000 control module, as well as for ATM quality of service (QoS) and other
traffic management capabilities, see the Stinger ATM Configuration Guide.
This guide describes how to configure IP routing and related functions in the Stinger
Stinger. It includes information about local and global network IP issues, as well as
how to configure both IP-routed switch-through ATM permanent virtual circuits
(PVCs) and RFC 1483 PVCs.
This guide also describes how to set up IEEE 802.1Q virtual local area network
(VLAN) support on the Gigabit Ethernet interface, and how to configure the system
to support multicast video over DSL with Internet Group Management Protocol
(IGMP) version-1 or version-2 messaging.
Warning Before installing your Stinger unit, be sure to read the safety instructions
in the Edge Access and Broadband Access Safety and Compliance Guide. For information
specific to your unit, see the “Safety-Related Physical, Environmental, and Electrical
Information” appendix in the Getting Started Guide for your Stinger unit.
Stinger® IP2000 Configuration Guide xv
About This Guide
Documentation conventions
Documentation conventions
Following are all the special characters and typographical conventions used in this
manual:
ConventionMeaning
Monospace textRepresents text that appears on your computer’s screen, or that
could appear on your computer’s screen.
Boldface
monospace text
ItalicsRepresent variable information. Do not enter the words
[ ]Square brackets indicate an optional argument you might add
|Separates command choices that are mutually exclusive.
>Points to the next level in the path to a parameter or menu
Key1+Key2Represents a combination keystroke. To enter a combination
Press EnterMeans press the Enter or Return key or its equivalent on your
Represents characters that you enter exactly as shown (unless
the characters are also in italics—see Italics, below). If you
could enter the characters but are not specifically instructed to,
they do not appear in boldface.
themselves in the command. Enter the information they
represent. In ordinary text, italics are used for titles of
publications, for some terms that would otherwise be in
quotation marks, and to show emphasis.
to a command. To include such an argument, type only the
information inside the brackets. Do not type the brackets unless
they appear in boldface.
item. The item that follows the angle bracket is one of the
options that appear when you select the item that precedes the
angle bracket.
keystroke, press the first key and hold it down while you press
one or more other keys. Release all the keys at the same time.
(For example, Ctrl+H means hold down the Ctrl key and press
the H key.)
computer.
Introduces important additional information.
Note
Warns that a failure to follow the recommended procedure
Caution
Warning
Warning
xvi Stinger® IP2000 Configuration Guide
could result in loss of data or damage to equipment.
Warns that a failure to take appropriate safety precautions
could result in physical injury.
Warns of danger of electric shock.
Stinger documentation set
The Stinger documentation set consists of the following manuals, which can be found
at http://www.lucent.com/support and http://www.lucentdocs.com/ins.
■Read me first:
–Edge Access and Broadband Access Safety and Compliance Guide. Contains
important safety instructions and country-specific information that you must
read before installing a Stinger unit.
–TAOS Command-Line Interface Guide. Introduces the TAOS command-line
environment and shows you how to use the command-line interface
effectively. This guide describes keyboard shortcuts and introduces
commands, security levels, profile structure, and parameter types.
■Installation and basic configuration:
–Getting Started Guide for your Stinger platform. Shows how to install your
Stinger chassis and hardware. This guide also shows you how to use the
command-line interface to configure and verify IP access and basic access
security on the unit, and how to configure Stinger control module
redundancy on units that support it.
About This Guide
Stinger documentation set
–Stinger Compact Remote Installation and Configuration Guide. Provides an
overview of the Stinger Compact Remote and instructions for the installation
and replacement of its components. This guide also describes how to
configure and manage the Compact Remote as a hosted unit.
–Module guides. For each Stinger line interface module (LIM), trunk module,
or other type of module, an individual guide describes the module's features
and provides instructions for configuring the module and verifying its status.
■Configuration:
–Stinger ATM Configuration Guide. Describes how to integrate the Stinger into
the ATM and Digital Subscriber Line (DSL) access infrastructure. The guide
explains how to configure PVCs, and shows how to use standard ATM
features such as quality of service (QoS), connection admission control
(CAC), and subtending.
–Stinger IP2000 Configuration Guide. For Stinger IP2000 systems, this guide
describes how to integrate the system into the IP infrastructure. Topics
include IP-routed switch-through ATM PVCs and RFC 1483 PVCs, IEEE
802.1Q VLAN, and forwarding multicast video transmissions on DSL
interfaces.
–Stinger Private Network-to-Network Interface (PNNI) Supplement. For the optional
PNNI software, this guide provides quick-start instructions for configuring
PNNI and soft PVCs (SPVCs), and describes the related profiles and
commands.
–Stinger SNMP Management of the ATM Stack Supplement. Describes SNMP
management of ATM ports, interfaces, and connections on a Stinger unit to
provide guidelines for configuring and managing ATM circuits through any
SNMP management utility.
–Stinger T1000 Module Routing and Tunneling Supplement. For the optional T1000
module, this guide describes how to configure the Layer 3 routing and virtual
private network (VPN) capabilities.
Stinger® IP2000 Configuration Guide xvii
About This Guide
Related documents
■RADIUS: TAOS RADIUS Guide and Reference. Describes how to set up a unit to use
the Remote Authentication Dial-In User Service (RADIUS) server and contains a
complete reference to RADIUS attributes.
■Administration and troubleshooting: Stinger Administration Guide. Describes
how to administer the Stinger unit and manage its operations. Each chapter
focuses on a particular aspect of Stinger administration and operations. The
chapters describe tools for system management, network management, and
Simple Network Management Protocol (SNMP) management.
■Reference:
–Stinger Reference. An alphabetic reference to Stinger profiles, parameters, and
commands.
–TAOS Glossary. Defines terms used in documentation for Stinger units.
Related documents
The following industry documents provide background information about features
described in this guide:
■RFC 951, Bootstrap Protocol
■RFC 1112, Host Extensions for IP Multicasting
■RFC 1334, PPP Authentication Protocols
■RFC 1483, Multiprotocol Encapsulation over ATM Adaptation Layer 5
■RFC 1587, The OSPF NSSA Option.
■RFC 1700, Assigned Numbers
■RFC 1723, RIP Version 2: Carrying Additional Information
The IP2000 control module supports a fiber-based Gigabit Ethernet (GigE) interface,
with a modular Small Form Factor Pluggable (SFP) transceiver. The IP2000 is
supported on he Stinger FS, the Stinger FS+, Stinger LS, and Stinger RT platforms.
Table 1-1 shows IP2000 model numbers and platform support:
Table 1-1. IP2000 model numbers and platform support
1
IP2000 model numberDescriptionSupporting platforms
STGR-CM-IP2000-FIP2000 with fiber gigabit
Ethernet
STGRRT-CM-IP2000-FIP2000 with fiber gigabit
Ethernet, environmentally
hardened
STGR-SFP-SXShort-haul gigabit Ethernet
SFP module
STGR-SFP-LXLong-haul gigabit Ethernet
SFP module
STGRRT-SFP-LXLong-haul gigabit Ethernet
SFP module,
environmentally hardened
Stinger FS
Stinger FS+
Stinger LS
Stinger RT
Stinger FS
Stinger FS+
Stinger LS
Stinger FS
Stinger FS+
Stinger LS
Stinger RT
Stinger® IP2000 Configuration Guide 1-1
Welcome to the IP2000
IP2000 software specifications
IP2000 software specifications
The IP2000 control module supports the following connection features:
Software capabilitySpecifications
ATM protocolsATM Forum UNI (v3.0 and v3.1)
ATM Forum Interim Interswitch Signaling Protocol (IISP)
ATM Forum Traffic Management v4.0
ATM Forum PNNI 1.0 (optional)
IP routing protocols RIPv1, RIPv2, OSPF
IP multicastInternet Group Management Protocol (IGMP) v1, v2,
Expansion slotOne PC card slot for configuration or upgrade storage
Switching fabric64x64 nonblocking ATM crosspoint switch
1.6Gbps ATM switching capacity
2.4Gpbs IP switching/routing capacity
Stinger® IP2000 Configuration Guide 1-3
Welcome to the IP2000
Network architecture overview
Network architecture overview
A Stinger IP2000 supports all standard Stinger ATM features, such as data and voice
services over DSL. In addition, it supports IP services such as multicast video, unicast
video-on-demand, and other video and IPTV applications. The services supported by
the IP2000 are provided downstream to DSL subscribers. In the upstream direction,
DSL subscribers accessing the Stinger IP2000 via IP over ATM can be directly routed
via the IP infrastructure to Internet services.
A Stinger IP2000 supports IP routing, ATM quality of service and traffic shaping,
virtual LAN, and multicasting capabilities to provide fast, efficient access to ATM and
IP services.
Multicast video
A Stinger IP2000 uses the Internet Group Management Protocol (IGMP) to manage
group memberships of downstream video to a PC application or set-top box, as
shown in Figure 1-1. Administrators can configure levels of service that control
subscribers’ access to specific multicast groups. Connection to originating router can
be across the Gigabit Ethernet interface or through a high-speed IP over ATM
connection.
Figure 1-1. Sample setup showing multicast and unicast video services
Network sideUser side
Multicast
video server
Multicast
router
Unicast video
server
IP router
Internet and voice access
When a subscriber has DSL Integrated Access Device (IAD) equipment (such as a
CellPipe®), the Stinger can deliver integrated voice and data services over the local
copper loop, providing a efficient, low-cost solution for enterprise, small business,
home office, and residential subscribers.
IP multicast
IP unicast
IP/ATM
IP/ATM
CPE
router
CPE
router
Set-top box (STB)
PC
NET-1
STB
NET-2
1-4Stinger® IP2000 Configuration Guide
Network architecture overview
Figure 1-2. Sample setup showing Internet access and voice over ATM
Network sideUser side
Welcome to the IP2000
Internet
ISPVoice
ATM
Voice
gateway
IP/ATM
IP/ATM
ATM
CPE
router
CellPipe
IAD
Multiplexing multiple IP flows on a single ATM VCC
A Stinger IP2000 supports an implementation of Class of Service (CoS) that co-exists
with the Stinger ATM QoS implementation. This feature allows transferring multiple
IP video streams (multicast and unicast) over single user-side ATM virtual circuit.
Figure 1-3. Sample setup showing multiple IP flows to a CPE router
Network sideUser side
InternetVoice
IAD
ISP
ATM
Multicast
router
Voice
gateway
IP multicast
IP/ATM
IP/ATM
Per-VC
priority
queueing
Services:
Internet access
Services:
Voice, Internet
access
Set-top box (STB)
NET-1
Services:
Multicast
video, VoATM,
Internet access
PC
The proprietary CoS implementation enables the delivery of differentiated services
over an IP infrastructure. All traffic handled by the IP2000, whether encapsulated IP
or native ATM, passes through the network processor function.
Non-IP terminated ATM traffic, including operations, administration, and
maintenance (OAM) F5 traffic, is treated as highest priority and handled in an AT M pass-through mode. This traffic passes through the network processor with no further
processing.
RFC 1483 IP traffic that terminates on the IP2000 is reassembled from ATM cells into
IP packets. It is then classified and assigned to priority output queues. Per-VC strictpriority queuing is supported with three priority levels as described in Table 1-2.
Stinger® IP2000 Configuration Guide 1-5
Welcome to the IP2000
Network architecture overview
Table 1-2. CoS and per-VC queueing for prioritizing IP packet processing
Priority queuePriority levelPacket classification assigned to queue
1HighIP Control Protocol Classification
2MediumMulticast Classification
3Low
Per-VC queuing operates in conjunction with the associated ATM shaping rate. The
aggregate rate of the combination of three priority queues (Class of Service Queuing
with Strict Priority) associated with a particular ATM virtual circuit is controlled by
the SCR (sustained cell rate) configured for the VC. In this case, SCR is configured
equal to PCR (peak cell rate). Rate information is configurable in the atm-qos profile
for each virtual circuit. For details about configuring ATM QoS, see the Stinger ATM Configuration Guide.
The IP2000 controller has two Ethernet interfaces, one 10/100 BASE-T interface for
management access to the unit via Telnet or SNMP, and one Gigabit Ethernet
interface for high-speed access to a local IP subnet. For information about configuring
the management interface, see the Getting Started Guide for your Stinger platform.
The Gigabit Ethernet MAC (GMAC) physical interface operates only in full-duplex
mode only for a full 1Gbps throughput. It supports auto-negotiation for advertising
its rate and duplex mode, but not for renegotiating it on the IEEE 802 LAN.
Stinger units with redundant IP2000 controllers can be configured to enable Gigabit
Ethernet port redundancy. With proper configuration, RFC 1483 (MPoA)
connections, VLAN connections, and MBONE interface functions can be maintained
across Gigabit Ethernet following a controller switchover.
2
Configuring the physical and logical interface
The system creates configuration profiles for both IP2000 Ethernet interfaces. For
each controller, interface 1 is always the 10/100 BASE-T management interface, and
interface 2 is the Gigabit Ethernet interface. For example:
To configure the data-link functions of the Gigabit Ethernet interface, open the
ethernet profile. For example:
admin> read ethernet { 1 8 2 }
admin> list
[in ETHERNET/{ shelf-1 first-control-module 2 }]
interface-address* = { shelf-1 first-control-module 2 }
link-state-enabled = no
enabled = yes
ether-if-type = fiber
bridging-enabled = no
filter-name = ""
duplex-mode = full-duplex
pppoe-options = { no no }
bridging-options = { 0 no no }
media-speed-mbit = 1000mb
auto-negotiate = no
For details about each of the parameters shown above, see the Stinger Reference.
Following are some Gigabit Ethernet-specific notes about the profile contents:
ParameterNotes about Gigabit Ethernet settings
interface-address*
link-state-enabled
enabled
ether-if-type
bridging-enabled
filter-name
duplex-mode
pppoe-options
The profile index and interface-address value of the
profile for a Gigabit Ethernet interface always specifies
an interface number of 2. For example:
shelf-1 first-control-module 2
With the default value, the system discards packets and
does not choose an alternate route if the interface is
down. If you set this to yes, the system deletes routes to
the interface when the interface is unavailable, and
then restores the routes when the interface becomes
available again.
If you set this to no and write the profile, the interface is
unavailable.
This setting is read-only and specifies either fiber or
utp (CAT5 unshielded twisted pair).
Enable/disable LAN packet bridging on the interface.
Set this parameter to yes to enable bridging on the
Gigabit Ethernet port. This is required for VLAN
operations. See Chapter 3, “VLAN Configuration.”
Applies a data filter to the interface. See Chapter 10,
“Filter Configuration.”
This setting is read-only and specifies full-duplex mode.
Not used by the IP2000.
2-2Stinger® IP2000 Configuration Guide
ParameterNotes about Gigabit Ethernet settings
bridging-options
media-speed-mbit
auto-negotiate
Not used by the IP2000. If you are configuring VLANs, you
set bridging options in the vlan-ethernet profile (not
in the ethernet profile). For details, see Chapter 3,
“VLAN Configuration.”
This setting is read-only and specifies 1Gbps.
Setting this parameter to yes does not cause the IP2000
to negotiate its duplex mode or speed, but it does cause
the system to advertise a full-duplex 1Gbps port , which
helps to ensure compatibility with remote Gigabit
Ethernet interfaces that support autonegotiation.
Modifying default ethernet settings
With the default settings, the Gigabit Ethernet interface is fully operational. The
following commands enable autonegotiation, to help ensure compatibility with other
Gigabit Ethernet interfaces that can negotiate between full-duplex and half-duplex
operations. (The IP2000 Gigabit Ethernet always operates in full-duplex mode.)
Assigning an IP address in the ip-interface profile
For details about the ip-interface profile, and about enabling dynamic routing or
configuring static routes to enable the system to communicate beyond its own
subnet, see “Configuring ip-interface profiles for Ethernet ports” on page 4-6. The
following commands provide the minimal configuration of an IP address for the
Gigabit Ethernet interface:
After you assign an IP address, you can verify that the Gigabit Ethernet interface is
able to handle IP traffic by checking some command output. For details about the
netstat and gmac commands, see the Stinger Reference.
You can also use the debug-level ifmgr -d command to verify that the Gigabit
Ethernet interface is active. This is described in Appendix A, “IP2000 Diagnostics.”
Checking the routing table
The following command output verifies that the routing table has an entry for the
Gigabit Ethernet interface (IP address 100.1.1.3/32):
admin> netstat -rn
Destination Gateway IF Flg Pref Met Use Age
0.0.0.0/0 1.1.2.1 ie0 SGP 60 1 3817 828
Stinger® IP2000 Configuration Guide 2-3
Gigabit Ethernet Configuration
Verifying the Gigabit Ethernet interface setup
20.1.2.0/24 - ie1-1 C 0 0 0 828
20.1.2.3/32 - local CP 0 0 0 828
100.1.1.0/8 - ie1 C 0 0 4683 828
100.1.1.3/32 - local CP 0 0 1580 828
127.0.0.0/8 - bh0 CP 0 0 0 828
127.0.0.1/32 - local CP 0 0 0 828
127.0.0.2/32 - rj0 CP 0 0 0 828
1.1.2.0/24 - ie0 C 0 0 1428 828
1.1.2.65/32 - local CP 0 0 2937 828
224.0.0.0/4 - mcast CP 0 0 0 828
224.0.0.1/32 - local CP 0 0 0 828
224.0.0.2/32 - local CP 0 0 0 828
224.0.0.9/32 - local CP 0 0 0 828
255.255.255.255/32 - ie0 CP 0 0 0 828
Verifying the network processor setup for the interface
The network processor on the IP2000 creates a connection entry for the Gigabit
Ethernet interface when the interface becomes operational. You can force the
network processor to create a connection entry for the Gigabit Ethernet interface by
using the following command:
admin> gmac -n
NP setup for gmac done.
Verifying the SAR setup for the interface
The Stinger Segmentation and Reassembly (SAR) creates an ATM connection entry
for the Gigabit Ethernet interface. You can force the SAR setup by using the following
command:
admin> gmac -s
GMAC: SAR conn. open with vpi = 0, vci = 200
Verifying IP packet transfer on the interface
The following command clears statistics gathered on the Gigabit Ethernet interface:
admin> gmac -d -c
The next command pings a host on the same subnet as the Gigabit Ethernet interface:
admin> ping 100.1.1.10
PING 100.1.1.10 (100.1.1.10): 56 data bytes
64 bytes from 100.1.1.10: icmp_seq=0 ttl=255 time=0 ms
64 bytes from 100.1.1.10: icmp_seq=1 ttl=255 time=0 ms
64 bytes from 100.1.1.10: icmp_seq=2 ttl=255 time=0 ms
64 bytes from 100.1.1.10: icmp_seq=3 ttl=255 time=0 ms
64 bytes from 100.1.1.10: icmp_seq=4 ttl=255 time=0 ms
64 bytes from 100.1.1.10: icmp_seq=5 ttl=255 time=0 ms
64 bytes from 100.1.1.10: icmp_seq=6 ttl=255 time=0 ms
64 bytes from 100.1.1.10: icmp_seq=7 ttl=255 time=0 ms
--- 100.1.1.10 ping statistics --8 packets transmitted, 8 packets received, 0% packet loss
round-trip min/avg/max = 0/0/0 ms
2-4Stinger® IP2000 Configuration Guide
Gigabit Ethernet Configuration
Gigabit Ethernet port redundancy
The following command displays GMAC statistics that show packet transfer. The
txGoodPackets and rxGoodPackets fields in the command output show 8 packets
transmitted and received in the ICMP sequence shown immediately above. For more
details on the command output fields, see “Total transmit statistics” on page A-24 and
“Total receive statistics” on page A-26.
With the proper configuration, systems with redundant controllers support Gigabit
Ethernet redundancy, which enables the system to maintain RFC 1483 (MPoA)
Stinger® IP2000 Configuration Guide 2-5
Gigabit Ethernet Configuration
Gigabit Ethernet port redundancy
connections, VLAN connections, and LAN MBONE interface functions across a
controller switchover.
Note A soft IP interface configuration is required for Gigabit Ethernet redundancy of
RFC 1483 connections and a LAN MBONE interface.
Configuring a soft IP interface for Gigabit Ethernet redundancy
The soft IP interface is an internal interface that is not associated with a specific
physical port, but that can be accessed through the Ethernet interface of whichever
controller is primary. For background information, see “Defining a soft interface for
increased accessibility” on page 4-8.
The system creates one soft interface profile by default. For example:
You can use the default soft IP interface { {0 0 0 } 0 } for Gigabit Ethernet
redundancy. However, if you have already used the default profile for the soft IP
address of the 10/100M base Ethernet management ports, you can create another
soft IP interface using a profile index of { { 0 0 0 } x }, as long as the IP address in
that profile is on the same subnet as the Gigabit Ethernet ports.
Note The system associates its Ethernet interfaces with a particular soft address
based on the subnet assignment. The IP interface address of the Gigabit Ethernet
ports on the primary and secondary controllers and the soft IP interface address must
be on the same subnet.
Configuring Gigabit Ethernet redundancy for RFC 1483 connections
Figure 2-1 shows a Stinger with redundant IP2000 controllers. The Gigabit Ethernet
port in slot 8 ({ { 1 8 2 } 0 }), the Gigabit Ethernet port in slot 9 ({ { 1 9 2 } 0 }),
and the soft IP interface ({ { 0 0 0 } 1 }), all have IP address assignments on the
same subnet. In addition, the external router has a routing table entry that specifies
the soft IP interface address as the gateway to the CPE router destination.
Figure 2-1. Gigabit Ethernet redundancy for RFC 1483 connectivity