|
Hi James, See my embedded remarks. Regards, Moti Morgenstern From: James Huang
[mailto:James.huang at huawei.com] Hi, stefaan, I have
read the discussion thread carefully. In my
understanding, in the case of Ethernet, when configuring an ANCP session in the
AN, the steps should be followed: 1. specify which
should be used by ancpAnSessionConfigRelatedInterface [MM] If the session is not associated with an entity that is
identified solely by an ifIndex the ancpAnSessionConfigRelatedEntity should be
used instead (or as well, depending on the specific case). 2. specify which
VLAN should be used. If the VLAN does not exist, it should be created; and an IP
address should be assigned to this VLAN interface, which would be used as the Source IP address in the ANCP packets; and also a routing
table should be added if necessary. [MM] The management model only allows you to indicate that a
session is associated with S-VLAN (or both S- and C-VLAN). It currently does
not refer to questions like “What if the VLAN does not exist?”, “How is the
MSAN’s IP address for each session specified?”, etc. Is this
correct? But I
still do not get the point why we should specify the layer2 interface, although
it is also defined in the ANCP framework. [MM] I’m not sure I understand what you mean, so I’ll try to
repeat what I already wrote. The ANCP session may “ride over” various interfaces/entities.
Sometimes such an interface has simply an ifIndex pattern but sometimes not. One
example is the ATM VCC but it’s only an example. Thanks! Best
Regards James 发件人: DE CNODDER Stefaan
[mailto:stefaan.de_cnodder at alcatel-lucent.be] Hi James, Some replies below From:
ancp-bounces at ietf.org [mailto:ancp-bounces at ietf.org] On Behalf Of James
Huang Hi, Moti, Do you mean we should specify which lower-layer entity should be
used to transmit ANCP message by using ancpAnSessionConfigRelatedEntity? If yes, then what is the difference between
ancpAnSessionConfigRelatedInterface and
ancpAnSessionConfigRelatedEntity, as shown below? I think they both specify an
interface in case of Ethernet, it is duplicated. [Stefaan] Not only Ethernet is covered but also ATM
…… (taken from
draft-ietf-ancp-mib-an-04 )
ancpAnSessionConfigRelatedInterface InterfaceIndex,
ancpAnSessionConfigRelatedEntity
RowPointer,
ancpAnSessionConfigSvid
VlanIdOrNone,
…… BTW, when creating an ANCP session, we need to specify the IP
addr of the ANCP server ? BRAS; that would be sufficient; what is the point to
specify the lower-layer entity? The AN should choose the lower-layer entity
itself. [Stefaan] these MIB objects have been added since version 02 of
the draft based on a discussion in February last year. In principle just
specifying the IP address of the NAS is sufficient but some people preferred to
also explicitly configure the underlying interface (VLAN, PVC, ...). The
discussion last year started with this message http://www.ietf.org/mail-archive/web/ancp/current/msg00484.html
regards, Stefaan Thanks! Best Regards James 发件人: Moti Morgenstern
[mailto:Moti.Morgenstern at ecitele.com] Hi James, The ANCP session is always associated with some lower-layer
entity, e.g., a virtual bridge port, an ATM VCC, Ethernet interface, etc. Notice that each one of the “lower-layer” entities listed here
has a different identifier-type. The bridge port has a port id, the VCC is
identified by (ifIndex, VPI, VCI) and the Ethernet interface has a unique
ifIndex value. So, the value in ancpAnSessionConfigRelatedEntity is the SNMP
Object ID that uniquely identifies the associated lower-layer entity. The format is therefore, as you understand, an index into
another SNMP table. Regards, Moti Morgenstern From:
ancp-bounces at ietf.org [mailto:ancp-bounces at ietf.org] On Behalf Of James
Huang Hi, all, I have some
questions about the implementation of ANCP MIB item
ancpAnSessionConfigRelatedEntity; can anybody give me some idea? Thanks in
advance! http://tools.ietf.org/html/draft-ietf-ancp-mib-an-04 ancpAnSessionConfigRelatedEntity
OBJECT-TYPE
SYNTAX RowPointer
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object contains the name of an object instance
uniquely identifying a lower layer entity associated
with this session. For example, in the case where
the session is associated with an ATM VCC, this object
might be set to an object identifier uniquely identifying
that VCC (e.g., an object instance in atmVclTable).
If unused, this object MUST have the value zeroDotZero.
The value of this object is persistent."
DEFVAL { zeroDotZero } ::= { ancpAnSessionConfigEntry
16 } Question: 1. “a lower layer entity associated with this session” What is the association between a lower layer entity and an ANCP
session? Is it associated with partition id? What is the application scenario for this? 2. what is the format of the name/identifier "Access-Node-Identifier atm slot/port:vpi.vci", which is
defined in TR-101, or an index, i.e. an index of the atmVclTable? Best Regards James |