< draft-ietf-ancp-mib-an-09.txt   draft-ietf-ancp-mib-an-10.txt >
Network Working Group S. De Cnodder Network Working Group S. De Cnodder
Internet-Draft Alcatel-Lucent Internet-Draft Alcatel-Lucent
Intended status: Standards Track M. Morgenstern Intended status: Standards Track M. Morgenstern
Expires: November 3, 2012 ECI Telecom Ltd. Expires: August 1, 2013 ECI Telecom Ltd.
May 2, 2012 January 28, 2013
Access Node Control Protocol (ANCP) MIB module for Access Nodes Access Node Control Protocol (ANCP) MIB module for Access Nodes
draft-ietf-ancp-mib-an-09.txt draft-ietf-ancp-mib-an-10.txt
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols. In particular it defines for use with network management protocols. In particular it defines
objects for managing access nodes that are using the Access Node objects for managing access nodes that are using the Access Node
Control Protocol (ANCP). Control Protocol (ANCP).
Status of this Memo Status of this Memo
skipping to change at page 1, line 34 skipping to change at page 1, line 34
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on November 3, 2012. This Internet-Draft will expire on August 1, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 2, line 20 skipping to change at page 2, line 20
4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 3 5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 3
5.1. Textual Conventions . . . . . . . . . . . . . . . . . . . 3 5.1. Textual Conventions . . . . . . . . . . . . . . . . . . . 3
5.2. The ANCP MIB module Subtree . . . . . . . . . . . . . . . 4 5.2. The ANCP MIB module Subtree . . . . . . . . . . . . . . . 4
5.3. The Notifications Subtree . . . . . . . . . . . . . . . . 4 5.3. The Notifications Subtree . . . . . . . . . . . . . . . . 4
5.4. The Table Structures . . . . . . . . . . . . . . . . . . . 4 5.4. The Table Structures . . . . . . . . . . . . . . . . . . . 4
6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 5 6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 5
6.1. Relationship to the Interfaces Group MIB module . . . . . 6 6.1. Relationship to the Interfaces Group MIB module . . . . . 6
6.2. MIB modules required for IMPORTS . . . . . . . . . . . . . 6 6.2. MIB modules required for IMPORTS . . . . . . . . . . . . . 6
7. ANCP MIB Definitions for the Access Node . . . . . . . . . . . 6 7. ANCP MIB Definitions for the Access Node . . . . . . . . . . . 6
8. Security Considerations . . . . . . . . . . . . . . . . . . . 29 8. Security Considerations . . . . . . . . . . . . . . . . . . . 31
9. IANA considerations . . . . . . . . . . . . . . . . . . . . . 34 9. IANA considerations . . . . . . . . . . . . . . . . . . . . . 37
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 35 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 37
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 35 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 37
11.1. Normative References . . . . . . . . . . . . . . . . . . . 35 11.1. Normative References . . . . . . . . . . . . . . . . . . . 37
11.2. Informative References . . . . . . . . . . . . . . . . . . 35 11.2. Informative References . . . . . . . . . . . . . . . . . . 38
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 36 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 38
1. Introduction 1. Introduction
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols. In particular it defines for use with network management protocols. In particular it defines
objects for managing access nodes as described in [RFC5851] that are objects for managing access nodes as described in [RFC5851] that are
using the Access Node Control Protocol defined in [RFC6320]. using the Access Node Control Protocol defined in [RFC6320].
2. The Internet-Standard Management Framework 2. The Internet-Standard Management Framework
skipping to change at page 7, line 9 skipping to change at page 7, line 9
ANCP-TC-MIB DEFINITIONS ::= BEGIN ANCP-TC-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, mib-2, Unsigned32 MODULE-IDENTITY, mib-2, Unsigned32
FROM SNMPv2-SMI -- [RFC2578] FROM SNMPv2-SMI -- [RFC2578]
TEXTUAL-CONVENTION TEXTUAL-CONVENTION
FROM SNMPv2-TC; -- [RFC2579] FROM SNMPv2-TC; -- [RFC2579]
ancpTcMIB MODULE-IDENTITY ancpTcMIB MODULE-IDENTITY
LAST-UPDATED "201204030000Z" -- 3 April 2012 LAST-UPDATED "201301010000Z" -- 1 January 2013
ORGANIZATION "IETF ANCP Working Group" ORGANIZATION "IETF ANCP Working Group"
CONTACT-INFO CONTACT-INFO
" Editors: " Editors:
Stefaan De Cnodder Stefaan De Cnodder
Alcatel-Lucent Alcatel-Lucent
Postal: Copernicuslaan 50 Postal: Copernicuslaan 50
B-2018 Antwerp B-2018 Antwerp
Belgium Belgium
EMail: stefaan.de_cnodder@alcatel-lucent.com EMail: stefaan.de_cnodder@alcatel-lucent.com
skipping to change at page 7, line 39 skipping to change at page 7, line 39
" "
DESCRIPTION DESCRIPTION
"This MIB module provides Textual Conventions to be "This MIB module provides Textual Conventions to be
used by MIB modules for AN and NAS that are implementing used by MIB modules for AN and NAS that are implementing
the Access Node Control Protocol (ANCP). the Access Node Control Protocol (ANCP).
Copyright (C) The IETF Trust (2008). The initial version of Copyright (C) The IETF Trust (2008). The initial version of
this MIB module was published in RFC yyyy; for full legal this MIB module was published in RFC yyyy; for full legal
notices see the RFC itself." notices see the RFC itself."
-- RFC Ed.: replace yyyy with actual RFC number and remove this note -- RFC Ed.: replace yyyy with actual RFC number and remove this note
REVISION "201204030000Z" -- 3 April 2012 REVISION "201301010000Z" -- 1 January 2013
DESCRIPTION "Initial version as published in RFC yyyy." DESCRIPTION "Initial version as published in RFC yyyy."
-- RFC Ed.: replace yyyy with actual RFC number and remove this note -- RFC Ed.: replace yyyy with actual RFC number and remove this note
::= { mib-2 xxx } ::= { mib-2 xxx }
-- The value xxx to be assigned by IANA. -- The value xxx to be assigned by IANA.
-- --
-- Textual Conventions -- Textual Conventions
-- --
AncpSessionCapabilities ::= TEXTUAL-CONVENTION AncpSessionCapabilities ::= TEXTUAL-CONVENTION
skipping to change at page 9, line 17 skipping to change at page 9, line 17
FROM SNMPv2-CONF -- [RFC2580] FROM SNMPv2-CONF -- [RFC2580]
RowStatus, TruthValue, RowPointer RowStatus, TruthValue, RowPointer
FROM SNMPv2-TC -- [RFC2579] FROM SNMPv2-TC -- [RFC2579]
VlanIdOrNone VlanIdOrNone
FROM Q-BRIDGE-MIB -- [RFC4363] FROM Q-BRIDGE-MIB -- [RFC4363]
AncpSessionCapabilities, AncpVersion, AncpSessionCapabilities, AncpVersion,
AncpPartitionId, AncpName AncpPartitionId, AncpName
FROM ANCP-TC-MIB; -- [This document] FROM ANCP-TC-MIB; -- [This document]
ancpAnMIB MODULE-IDENTITY ancpAnMIB MODULE-IDENTITY
LAST-UPDATED "201204030000Z" -- 3 April 2012 LAST-UPDATED "201301010000Z" -- 1 January 2013
ORGANIZATION "IETF ANCP Working Group" ORGANIZATION "IETF ANCP Working Group"
CONTACT-INFO CONTACT-INFO
" Editors: " Editors:
Stefaan De Cnodder Stefaan De Cnodder
Alcatel-Lucent Alcatel-Lucent
Postal: Copernicuslaan 50 Postal: Copernicuslaan 50
B-2018 Antwerp B-2018 Antwerp
Belgium Belgium
EMail: stefaan.de_cnodder@alcatel-lucent.com EMail: stefaan.de_cnodder@alcatel-lucent.com
skipping to change at page 9, line 46 skipping to change at page 9, line 46
Phone: +972 3 926 6258 Phone: +972 3 926 6258
" "
DESCRIPTION DESCRIPTION
"The MIB module for entities implementing the access node "The MIB module for entities implementing the access node
side of the Access Node Control Protocol (ANCP). side of the Access Node Control Protocol (ANCP).
Copyright (C) The IETF Trust (2008). The initial version of Copyright (C) The IETF Trust (2008). The initial version of
this MIB module was published in RFC yyyy; for full legal this MIB module was published in RFC yyyy; for full legal
notices see the RFC itself." notices see the RFC itself."
-- RFC Ed.: replace yyyy with actual RFC number and remove this note -- RFC Ed.: replace yyyy with actual RFC number and remove this note
REVISION "201204030000Z" -- 3 April 2012 REVISION "201301010000Z" -- 1 January 2013
DESCRIPTION "Initial version as published in RFC yyyy." DESCRIPTION "Initial version as published in RFC yyyy."
-- RFC Ed.: replace yyyy with actual RFC number and remove this note -- RFC Ed.: replace yyyy with actual RFC number and remove this note
::= { mib-2 xxx } ::= { mib-2 xxx }
-- The value xxx to be assigned by IANA. -- The value xxx to be assigned by IANA.
ancpAnNotifications OBJECT IDENTIFIER ::= { ancpAnMIB 0 } ancpAnNotifications OBJECT IDENTIFIER ::= { ancpAnMIB 0 }
ancpAnObjects OBJECT IDENTIFIER ::= { ancpAnMIB 1 } ancpAnObjects OBJECT IDENTIFIER ::= { ancpAnMIB 1 }
ancpAnConformance OBJECT IDENTIFIER ::= { ancpAnMIB 2 } ancpAnConformance OBJECT IDENTIFIER ::= { ancpAnMIB 2 }
-- --
skipping to change at page 20, line 28 skipping to change at page 20, line 28
ancpAnCurrentSessionAnName AncpName, ancpAnCurrentSessionAnName AncpName,
ancpAnCurrentSessionNasName AncpName, ancpAnCurrentSessionNasName AncpName,
ancpAnCurrentSessionAnIpAddressType InetAddressType, ancpAnCurrentSessionAnIpAddressType InetAddressType,
ancpAnCurrentSessionAnIpAddress InetAddress, ancpAnCurrentSessionAnIpAddress InetAddress,
ancpAnCurrentSessionAnInstance Unsigned32, ancpAnCurrentSessionAnInstance Unsigned32,
ancpAnCurrentSessionNasInstance Unsigned32, ancpAnCurrentSessionNasInstance Unsigned32,
ancpAnCurrentSessionCapabilities AncpSessionCapabilities, ancpAnCurrentSessionCapabilities AncpSessionCapabilities,
ancpAnCurrentSessionStartUptime TimeTicks, ancpAnCurrentSessionStartUptime TimeTicks,
ancpAnCurrentSessionDiscontinuityTime TimeTicks, ancpAnCurrentSessionDiscontinuityTime TimeTicks,
ancpAnCurrentSessionStatSentMessages ZeroBasedCounter32, ancpAnCurrentSessionStatSentMessages ZeroBasedCounter32,
ancpAnCurrentSessionStatReceivedValidMessages ZeroBasedCounter32, ancpAnCurrentSessionStatReceivedValidMessages ZeroBasedCounter32,
ancpAnCurrentSessionStatDiscardedMessages ZeroBasedCounter32 ancpAnCurrentSessionStatDiscardedMessages ZeroBasedCounter32,
ancpAnCurrentSessionStatReceivedAdjSyn ZeroBasedCounter32,
ancpAnCurrentSessionStatReceivedAdjSynack ZeroBasedCounter32,
ancpAnCurrentSessionStatReceivedAdjAck ZeroBasedCounter32,
ancpAnCurrentSessionStatReceivedAdjRstack ZeroBasedCounter32,
ancpAnCurrentSessionStatTransmittedAdjSyn ZeroBasedCounter32,
ancpAnCurrentSessionStatTransmittedAdjSynack ZeroBasedCounter32,
ancpAnCurrentSessionStatTransmittedAdjAck ZeroBasedCounter32,
ancpAnCurrentSessionStatTransmittedAdjRstack ZeroBasedCounter32
} }
ancpAnCurrentSessionState OBJECT-TYPE ancpAnCurrentSessionState OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
other(1), other(1),
synsent(2), synsent(2),
synrcvd(3), synrcvd(3),
estab(4) estab(4)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 23, line 31 skipping to change at page 23, line 40
ancpAnCurrentSessionStartUptime." ancpAnCurrentSessionStartUptime."
::= { ancpAnCurrentSessionEntry 11 } ::= { ancpAnCurrentSessionEntry 11 }
ancpAnCurrentSessionStatSentMessages OBJECT-TYPE ancpAnCurrentSessionStatSentMessages OBJECT-TYPE
SYNTAX ZeroBasedCounter32 SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of messages that have been sent in this session "The number of messages that have been sent in this session
by the access node. by the access node.
All ANCP messages pertaining to this session after All ANCP messages pertaining to this session shall
the session came to established state shall
be counted, also including adjacency protocol messages be counted, also including adjacency protocol messages
and failure response messages. and failure response messages.
Discontinuities of this counter are indicated by Discontinuities of this counter are indicated by
ancpAnCurrentSessionDiscontinuityTime." ancpAnCurrentSessionDiscontinuityTime."
::= { ancpAnCurrentSessionEntry 12 } ::= { ancpAnCurrentSessionEntry 12 }
ancpAnCurrentSessionStatReceivedValidMessages OBJECT-TYPE ancpAnCurrentSessionStatReceivedValidMessages OBJECT-TYPE
SYNTAX ZeroBasedCounter32 SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of messages that have been received and "The number of messages that have been received and
processed in this session by the access node. processed in this session by the access node.
All ANCP messages pertaining to this session after All ANCP messages pertaining to this session shall
the session came to established state shall
be counted, also including adjacency protocol messages be counted, also including adjacency protocol messages
and failure response messages. and failure response messages.
Discontinuities of this counter are indicated by Discontinuities of this counter are indicated by
ancpAnCurrentSessionDiscontinuityTime." ancpAnCurrentSessionDiscontinuityTime."
::= { ancpAnCurrentSessionEntry 13 } ::= { ancpAnCurrentSessionEntry 13 }
ancpAnCurrentSessionStatDiscardedMessages OBJECT-TYPE ancpAnCurrentSessionStatDiscardedMessages OBJECT-TYPE
SYNTAX ZeroBasedCounter32 SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of messages that in this session have been "The number of messages that in this session have been
received and discarded for whatever reason by the access received and discarded for whatever reason by the access
node. node.
All ANCP messages pertaining to this session after All ANCP messages pertaining to this session shall
the session came to established state shall
be counted, also including adjacency protocol messages be counted, also including adjacency protocol messages
and failure response messages. and failure response messages.
Discontinuities of this counter are indicated by Discontinuities of this counter are indicated by
ancpAnCurrentSessionDiscontinuityTime." ancpAnCurrentSessionDiscontinuityTime."
::= { ancpAnCurrentSessionEntry 14 } ::= { ancpAnCurrentSessionEntry 14 }
ancpAnCurrentSessionStatReceivedAdjSyn OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of adjacency SYN messages that in this
session have been received by the access node.
Discontinuities of this counter are indicated by
ancpAnCurrentSessionDiscontinuityTime."
::= { ancpAnCurrentSessionEntry 15 }
ancpAnCurrentSessionStatReceivedAdjSynack OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of adjacency SYNACK messages that in this
session have been received by the access node.
Discontinuities of this counter are indicated by
ancpAnCurrentSessionDiscontinuityTime."
::= { ancpAnCurrentSessionEntry 16 }
ancpAnCurrentSessionStatReceivedAdjAck OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of adjacency ACK messages that in this
session have been received by the access node.
Discontinuities of this counter are indicated by
ancpAnCurrentSessionDiscontinuityTime."
::= { ancpAnCurrentSessionEntry 17 }
ancpAnCurrentSessionStatReceivedAdjRstack OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of adjacency RSTACK messages that in this
session have been received by the access node.
Discontinuities of this counter are indicated by
ancpAnCurrentSessionDiscontinuityTime."
::= { ancpAnCurrentSessionEntry 18 }
ancpAnCurrentSessionStatTransmittedAdjSyn OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of adjacency SYN messages that in this
session have been transmitted by the access node.
Discontinuities of this counter are indicated by
ancpAnCurrentSessionDiscontinuityTime."
::= { ancpAnCurrentSessionEntry 19 }
ancpAnCurrentSessionStatTransmittedAdjSynack OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of adjacency SYNACK messages that in this
session have been transmitted by the access node.
Discontinuities of this counter are indicated by
ancpAnCurrentSessionDiscontinuityTime."
::= { ancpAnCurrentSessionEntry 20 }
ancpAnCurrentSessionStatTransmittedAdjAck OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of adjacency ACK messages that in this
session have been transmitted by the access node.
Discontinuities of this counter are indicated by
ancpAnCurrentSessionDiscontinuityTime."
::= { ancpAnCurrentSessionEntry 21 }
ancpAnCurrentSessionStatTransmittedAdjRstack OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of adjacency RSTACK messages that in this
session have been transmitted by the access node.
Discontinuities of this counter are indicated by
ancpAnCurrentSessionDiscontinuityTime."
::= { ancpAnCurrentSessionEntry 22 }
-- --
-- Partitions -- Partitions
-- --
ancpAnInterfaceConfigTable OBJECT-TYPE ancpAnInterfaceConfigTable OBJECT-TYPE
SYNTAX SEQUENCE OF AncpAnInterfaceConfigEntry SYNTAX SEQUENCE OF AncpAnInterfaceConfigEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table configures the association of user facing "This table configures the association of user facing
skipping to change at page 25, line 41 skipping to change at page 27, line 39
ancpAnCurrentSessionAnIpAddressType, ancpAnCurrentSessionAnIpAddressType,
ancpAnCurrentSessionAnIpAddress, ancpAnCurrentSessionAnIpAddress,
ancpAnSessionConfigNasIpAddressType, ancpAnSessionConfigNasIpAddressType,
ancpAnSessionConfigNasIpAddress, ancpAnSessionConfigNasIpAddress,
ancpAnCurrentSessionAnInstance, ancpAnCurrentSessionAnInstance,
ancpAnCurrentSessionNasInstance, ancpAnCurrentSessionNasInstance,
ancpAnCurrentSessionStartUptime, ancpAnCurrentSessionStartUptime,
ancpAnCurrentSessionDiscontinuityTime, ancpAnCurrentSessionDiscontinuityTime,
ancpAnCurrentSessionStatSentMessages, ancpAnCurrentSessionStatSentMessages,
ancpAnCurrentSessionStatReceivedValidMessages, ancpAnCurrentSessionStatReceivedValidMessages,
ancpAnCurrentSessionStatDiscardedMessages ancpAnCurrentSessionStatDiscardedMessages,
ancpAnCurrentSessionStatReceivedAdjSyn,
ancpAnCurrentSessionStatReceivedAdjSynack,
ancpAnCurrentSessionStatReceivedAdjAck,
ancpAnCurrentSessionStatReceivedAdjRstack,
ancpAnCurrentSessionStatTransmittedAdjSyn,
ancpAnCurrentSessionStatTransmittedAdjSynack,
ancpAnCurrentSessionStatTransmittedAdjAck,
ancpAnCurrentSessionStatTransmittedAdjRstack
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated whenever an ANCP session "This notification is generated whenever an ANCP session
goes down. A session can go down for several reasons: goes down. A session can go down for several reasons:
1) The ANCP session can be deleted by a manager from the 1) The ANCP session can be deleted by a manager from the
ancpAnSessionConfigTable, and hence it will also be ancpAnSessionConfigTable, and hence it will also be
removed from the ancpAnCurrentSessionTable. removed from the ancpAnCurrentSessionTable.
2) The session can go operational down due to some 2) The session can go operational down due to some
malfunction in the network, the AN, or the NAS. In malfunction in the network, the AN, or the NAS. In
this case, the ANCP session will be still in the this case, the ANCP session will be still in the
ancpAnSessionConfigTable and ancpAnCurrentSessionTable, ancpAnSessionConfigTable and ancpAnCurrentSessionTable,
but the ancpAnCurrentSessionState moves from the estab but the ancpAnCurrentSessionState moves from the estab
state to another state. state to another state.
This notification is only generated when This notification is only generated when
skipping to change at page 28, line 40 skipping to change at page 30, line 45
ancpAnCurrentSessionNasName, ancpAnCurrentSessionNasName,
ancpAnCurrentSessionAnIpAddressType, ancpAnCurrentSessionAnIpAddressType,
ancpAnCurrentSessionAnIpAddress, ancpAnCurrentSessionAnIpAddress,
ancpAnCurrentSessionAnInstance, ancpAnCurrentSessionAnInstance,
ancpAnCurrentSessionNasInstance, ancpAnCurrentSessionNasInstance,
ancpAnCurrentSessionCapabilities, ancpAnCurrentSessionCapabilities,
ancpAnCurrentSessionStartUptime, ancpAnCurrentSessionStartUptime,
ancpAnCurrentSessionDiscontinuityTime, ancpAnCurrentSessionDiscontinuityTime,
ancpAnCurrentSessionStatSentMessages, ancpAnCurrentSessionStatSentMessages,
ancpAnCurrentSessionStatReceivedValidMessages, ancpAnCurrentSessionStatReceivedValidMessages,
ancpAnCurrentSessionStatDiscardedMessages ancpAnCurrentSessionStatDiscardedMessages,
ancpAnCurrentSessionStatReceivedAdjSyn,
ancpAnCurrentSessionStatReceivedAdjSynack,
ancpAnCurrentSessionStatReceivedAdjAck,
ancpAnCurrentSessionStatReceivedAdjRstack,
ancpAnCurrentSessionStatTransmittedAdjSyn,
ancpAnCurrentSessionStatTransmittedAdjSynack,
ancpAnCurrentSessionStatTransmittedAdjAck,
ancpAnCurrentSessionStatTransmittedAdjRstack
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"These objects show the operational state of all ANCP "These objects show the operational state of all ANCP
sessions configured in the access node." sessions configured in the access node."
::= { ancpAnGroups 5 } ::= { ancpAnGroups 5 }
ancpAnInterfaceGroup OBJECT-GROUP ancpAnInterfaceGroup OBJECT-GROUP
OBJECTS { OBJECTS {
ancpAnPartitionsUsed, ancpAnPartitionsUsed,
skipping to change at page 34, line 26 skipping to change at page 36, line 40
* ancpAnCurrentSessionStartUptime * ancpAnCurrentSessionStartUptime
* ancpAnCurrentSessionDiscontinuityTime * ancpAnCurrentSessionDiscontinuityTime
* ancpAnCurrentSessionStatSentMessages * ancpAnCurrentSessionStatSentMessages
* ancpAnCurrentSessionStatReceivedValidMessages * ancpAnCurrentSessionStatReceivedValidMessages
* ancpAnCurrentSessionStatDiscardedMessages * ancpAnCurrentSessionStatDiscardedMessages
* ancpAnCurrentSessionStatReceivedAdjSyn
* ancpAnCurrentSessionStatReceivedAdjSynack
* ancpAnCurrentSessionStatReceivedAdjAck
* ancpAnCurrentSessionStatReceivedAdjRstack
* ancpAnCurrentSessionStatTransmittedAdjSyn
* ancpAnCurrentSessionStatTransmittedAdjSynack
* ancpAnCurrentSessionStatTransmittedAdjAck
* ancpAnCurrentSessionStatTransmittedAdjRstack
SNMP versions prior to SNMPv3 did not include adequate security. SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPSec), Even if the network itself is secure (for example by using IPSec),
even then, there is no control as to who on the secure network is even then, there is no control as to who on the secure network is
allowed to access and GET/SET (read/change/create/delete) the objects allowed to access and GET/SET (read/change/create/delete) the objects
in this MIB module. in this MIB module.
It is RECOMMENDED that implementers consider the security features as It is RECOMMENDED that implementers consider the security features as
provided by the SNMPv3 framework (see [RFC3410], Section 8), provided by the SNMPv3 framework (see [RFC3410], Section 8),
including full support for the SNMPv3 cryptographic mechanisms (for including full support for the SNMPv3 cryptographic mechanisms (for
authentication and privacy). authentication and privacy).
skipping to change at page 35, line 7 skipping to change at page 37, line 34
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
9. IANA considerations 9. IANA considerations
IANA is requested to assign two OID's xxx under mib-2 for ANCP-TC-MIB IANA is requested to assign two OID's xxx under mib-2 for ANCP-TC-MIB
and ANCP-AN-MIB. and ANCP-AN-MIB.
10. Acknowledgements 10. Acknowledgements
The authors would like to thank Paul Reynders and Bert Wijnen for The authors would like to thank Paul Reynders, Bert Wijnen and Tom
their feedback. Taylor for their feedback.
11. References 11. References
11.1. Normative References 11.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Structure of Management Information Schoenwaelder, Ed., "Structure of Management Information
 End of changes. 20 change blocks. 
29 lines changed or deleted 154 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/