[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Question on LMP-MIB ?
Zafar,
You
could keep the remote IPCC address in the LMP MIB (after I add this field to the
control channel table).
Martin
At 04:13 PM 4/15/2002 -0500, Loc Chu
wrote:
Hi all,
The Section 3 of the LMP draft
states:
"To establish a control channel, the destination IP address
on the far end of
the control channel must be known. This
knowledge may be manually configured
or automatically discovered."
Also, Section 9 of the LMP draft states:
"The manner in
which a Config message is addressed may depend on the signaling
transport mechanism. When the transport mechanism is a
point-to-point link, Config
messages SHOULD be sent to the
Multicast address (224.0.0.1). Otherwise, Config
messages
MUST be sent to an IP address on the neighboring node. This is
configured
at both ends of the control channel."
In case
of IPCC's are out-of-fiber/out-of-band and NOT point-to-point link, we have
to
use a specific IP address for the remote end of the IPCC. Where
do we keep the remote
IPCC Address ?
Hi Loc,
I think, the IP address of the neighboring node should
also be used, in this case as well. Why you feel that IPCC address need to be
different from IP address of the neighboring node?
Thanks
Regards... Zafar
if not, is it possible to have a field in
lmpControlChannelEntry MIB for configuring
the remote IPCC address such
as:
lmpCcRemoteIpAddr OBJECT-TYPE
SYNTAX
InetAddress
MAX-ACCESS read-create
STATUS
current
DESCRIPTION "IP address associated with remote
IPCC."
::= { lmpControlChannelEntry 23 }
Thanks in
advance for your help or any clarification since my question is too
implementation specific.
Regards,
--
Loc Chu
Software Development
Engineer Alcatel, USA
Research &
Innovation
1000 Coit Rd. Plano, TX 75075 M/S:CTO2
Advanced Routers and Cross Connects Phone: 972-477-2463
Fax:
972-477-2972