Table 13 Setting Interface Type for Non-3Com Peer
Peer
My Configured
Configured
Interface Type
Interface Type
E-IISP
IISP
IISP
IISP
If the peer is running ILMI 4.0, the IME type is determined automatically
as shown in Table 14 but if the peer is running ILMI version 3.0 or 3.1 you
need to configure the local switch by LMA. For more information on
configuring the local switch, see "Update Signaling Protocol Version" on
page 205 in the Management Guide. Table 15 shows how this is done.
Table 14 Auto-configuration of IME Type for Non-3Com/ILMI 4.0 Peer
Compare My Parameter
with Peer's
my system ID larger
my system ID smaller
Table 15 Setting IME Type for Non-3Com/ILMI 3.X Peer
My Resulting IME Type
If peer is Network-Side, set to
User-Side by LMA
If peer is User-Side, set to
Network-Side by LMA
Enabling/Disabling Auto-Discovery
You can enable and disable auto-discovery from the LMA. If the
auto-discovery is enabled, it will determine the protocol parameters as
described in the tables above. If not, you need to change them through
the LMA commands.
If the version is installed over an operational box, the Interface type and
the IME types will be determined according to the flash values.
Manual Discovery
As mentioned previously, when auto-discovery does not operate, you use
LMA to determine the interface type and the IME type. This is called
manual discovery because it complements auto-discovery. Table 16 shows
Automatic Configuration Procedures
My Resulting
Interface Type
Set to IISP
manually
IISP
My Resulting IME Type
User-Side
Network-Side
Peer Resulting IME Type
Network-Side
User-Side
47
Peer Resulting
Interface Type
IISP
IISP
Peer Resulting IME Type
Network-Side
User-Side
Need help?
Do you have a question about the CoreBuilder 7000 and is the answer not in the manual?
Questions and answers