This module manages Cisco's WiMAX ASN Gateway (ASN-GW).
A WiMAX network supports wireless data communication through
WiMAX radio (802.16) technology.
The high level architecture of a first generation WiMAX network
with the respective protocols for each interface is shown below:
+
| R2 |
+
| | R1 | | R6 | | |
| MS |
| | | | | |
+
| | | R3 |
R8 | R4 | |
| | | |
+
| | R1 | | R6 | |
| MS |
| | | | | | |
+
| |
+
The diagram below depicts the relation of the subscriber to the
session and flows:
+
| ASN-GW | - Subscriber -Session -Flow (connected via data path)
+
| -Flow (connected via data path)
|
+
A subscriber initiates a call from a MS. A session is created
between the BS and the ASN-GW for that call. Multiple flows can
be created for the session with different QOS parameters. For
example one flow can created for a voice stream and another
for data. Data paths are created between the BS and ASN-GW to
forward the data packets of the created flows.
When the first subscriber from any MS connected to a BS
initiates a call via the BS to the ASN-GW, a signaling path is
created between the BS and the ASN-GW. There is only one
signaling path between each BS and ASN-GW. Signaling paths
and base stations can be used interchangeably.
The signaling and data paths remains active as long as there are
subscribers connected to the ASN-GW from any MS connected to the
BS. If a path has no session/flow connected, it will be purged
after a certain period of time. This situation can occur when
all subscribers on a certain path are disconnected. A subscriber
disconnecting from a certain path does not indicate that the
subscriber has left the network, it could simply be handing off
to a different path.
The IP addresses of the signaling and data paths can be the same
or different both in the BS side and in the ASN-GW side.
+
| Base | | ASN-GW |
| Station| | |
| | SigPath | |
| IP(B1)|<............>|IP(A1) |
| | | |
| | | |
| | DataPath 1 | |
| IP(B2)|<............>|IP(A2) |
| | | |
| | DataPath 2 | |
| IP(B3)|<............>|IP(A3) |
+
Relationships:
Base Station 1 to many Mobile Stations
ASN-GW 1 to many Base Stations
Subscriber 1 to 1 Sessions
Session 1 to many Flows
Datapath 1 to many Flows
Signaling Path 1 to 1 Base Station
Acronyms and terms:
AAA AAA refers to a framework that specifies the
protocols procedures for authentications,
authorizatitin and accounting associated
with the user, MS and subscribed serviced.
AGW ASN-GW
ASN ASN (Access Service network) is defined as
a complete set of network functions needed
to provide radio access to a WiMAX
subscriber.
ASN-GW ASN-Gateway is a logical entity that
represents an aggregation of Control Plane
functional entities that are either paired
with a corresponding function in the ASN
(for e.g BS instance) a resident function is
the CSN or another functions in the ASN.
For every MS, a BS is associated with
exactly one default ASN-GW. However,
ASN-GW functions for every MS may be
distributes amongst multiple
ASN-GWs located in one or more ASNs. The
ASN-GW utilizes Session Redudancy to ensure
a backup ASN-GW is available in case the
primary ASN-GW goes down.
BS Base Station is a logical entity that
represents an aggregation of Control Plane
functional entities that are either paired
with a corresponding function in the ASN
(e.g. BS instance), a resident function
in the CSN or a function in another ASN. The
ASN-GW may also perform Bearer Plane routing
or bridging function.
BSID The Base Station Identifier is a global
unique identifier for a WiMAX base station.
CPE Customer Premise Equipment.
CSN CSN (Connectivity Service Network) is
defined as a set of network functions that
provide IP connectivity services to the
WiMAX subscribers.
Data Path Corresponding to each subscriber, data paths
are created to foward packets between the
ASN-GW and the subscribers.
DPID Data Path ID is used to identify the tunnel
carrying MS traffic between ASN gateways or
between the ASN gateway and base station.
As of 8/28/07, only the GRE key is to be
used as the DPID.
Flow A service flow is a unidirectional logical
flow between the network and the Subscriber
Station. A service flow is created to handle
a different QoS over the connection oriented
MAC. A subscriber can have multiple service
flows associated and each service flow is
associcated with an uplink and downlink
classifier.
GRE Generic Routing Encapsulation. Refer to
RFC 1701 for more details.
LB Load Balancing
Messages Messages are packets exchanged on the
signaling paths.
MS The Mobile Station is a generalized mobile
equipment set providing connectivity between
subscriber equipment and a base station (BS)
The Mobile Station may be a host or a CPE
type of device that can support multiple
hosts.
MSID The Mobile Station Identifier is the 802.16
identifier used for all subscriber stations,
and is used in all the messages over R6. The
identifier associates all requests from a
mobile to the ASN-GW.
Packets Packets are datagrams fowarded over the data
paths.
R1 Communication protocol between mobile and BS
as per the air interface (PHY and MAC)
specifications (IEEE P802.16d/e). R1 may
include additional protocols related to the
management plane.
R2 The interface between the MS and CSN
associated with Authentication,
Services Authorization, IP Host
Configuration management, and mobility
management. This is a logical interface thus
does not reflect a direct protocol interface
between MS and CSN.
R3 The interface between the ASN and the CSN to
support AAA, policy enforcement and mobility
management capabilities. It also encompasses
the bearer plane methods (e.g., tunneling)
to transfer IP data between the ASN and the
CSN.
R4 Communication protocol between ASN-GWs.
R4 consists of a set of control and bearer
plane protocols originating/terminating in
various entities within the ASN that
coordinate MS mobility between ASNs.
In Release 1, R4 is the only interoperable
interface between
heterogeneous or dissimilar ASNs.
R5 Consists of a set of control plane and
bearer plane protocols for internetworking
between CSNs operated by either the home or
visited NSP.
R6 Communication protocol between ASN-GW and BS
R6 consists of a set of control and bearer
plane protocols for communication between
the BS and the ASN GW.
The bearer plane consists of intra-ASN
data path or inter-ASN tunnels between the
BS and ASN-GW.
The control plane includes protocols for
IP tunnel management (establish, modify, and
release) in accordance with the MS mobility
events. R6 may also serve as a conduit for
exchange of MAC states information between
neighboring BSs.
R8 Communication protocol between base
stations.
R8 consists of a set of control plane
message flows and, in some situations,
bearer plane data flows between the
base stations to ensure fast and seamless
handover.
Bearer plane consists of protocols that
allow the data transfer between Base
Stations involved in handover of a
certain MS.
Control plane consists of the inter-BS
communication protocol defined in IEEE
802.16 and additional set of protocols
that allow controlling the data
transfer between the Base Stations involved
in handover of a certain MS.
Session Session is a connection between one or more
MS and a network element in order to
exchange link-level frames or packets.
SFID The service flow is identified using a SFID
(Service Flow Identifier).
Signaling Path A signaling path exists between the BS and
ASN-GW, and is used for all signaling such
as creating, dleteing, authenticating,
as we as additional functions related to
the subscriber.
SR Session Redundancy
Subscriber The 802.16 subscriber entity connects over
the 802.16 airlink, and eventually results
in the creation of the subscriber object at
the ASN-GW.
UHO Unpredicitive Handoff
PMIP Proxy Mobile Internet Protocol
HA Home Agent
REFERENCE
[1] WIMAX Forum Network Architecture,
(Stage 3: Detailed Protocols and Procedures)
Release 1.1.1 September 14, 2007.
Parsed from file CISCO-ASN-GATEWAY-MIB.mib
Module: CISCO-ASN-GATEWAY-MIB
This module manages Cisco's WiMAX ASN Gateway (ASN-GW).
A WiMAX network supports wireless data communication through
WiMAX radio (802.16) technology.
The high level architecture of a first generation WiMAX network
with the respective protocols for each interface is shown below:
+
| R2 |
+
| | R1 | | R6 | | |
| MS |
| | | | | |
+
| | | R3 |
R8 | R4 | |
| | | |
+
| | R1 | | R6 | |
| MS |
| | | | | | |
+
| |
+
The diagram below depicts the relation of the subscriber to the
session and flows:
+
| ASN-GW | - Subscriber -Session -Flow (connected via data path)
+
| -Flow (connected via data path)
|
+
A subscriber initiates a call from a MS. A session is created
between the BS and the ASN-GW for that call. Multiple flows can
be created for the session with different QOS parameters. For
example one flow can created for a voice stream and another
for data. Data paths are created between the BS and ASN-GW to
forward the data packets of the created flows.
When the first subscriber from any MS connected to a BS
initiates a call via the BS to the ASN-GW, a signaling path is
created between the BS and the ASN-GW. There is only one
signaling path between each BS and ASN-GW. Signaling paths
and base stations can be used interchangeably.
The signaling and data paths remains active as long as there are
subscribers connected to the ASN-GW from any MS connected to the
BS. If a path has no session/flow connected, it will be purged
after a certain period of time. This situation can occur when
all subscribers on a certain path are disconnected. A subscriber
disconnecting from a certain path does not indicate that the
subscriber has left the network, it could simply be handing off
to a different path.
The IP addresses of the signaling and data paths can be the same
or different both in the BS side and in the ASN-GW side.
+
| Base | | ASN-GW |
| Station| | |
| | SigPath | |
| IP(B1)|<............>|IP(A1) |
| | | |
| | | |
| | DataPath 1 | |
| IP(B2)|<............>|IP(A2) |
| | | |
| | DataPath 2 | |
| IP(B3)|<............>|IP(A3) |
+
Relationships:
Base Station 1 to many Mobile Stations
ASN-GW 1 to many Base Stations
Subscriber 1 to 1 Sessions
Session 1 to many Flows
Datapath 1 to many Flows
Signaling Path 1 to 1 Base Station
Acronyms and terms:
AAA AAA refers to a framework that specifies the
protocols procedures for authentications,
authorizatitin and accounting associated
with the user, MS and subscribed serviced.
AGW ASN-GW
ASN ASN (Access Service network) is defined as
a complete set of network functions needed
to provide radio access to a WiMAX
subscriber.
ASN-GW ASN-Gateway is a logical entity that
represents an aggregation of Control Plane
functional entities that are either paired
with a corresponding function in the ASN
(for e.g BS instance) a resident function is
the CSN or another functions in the ASN.
For every MS, a BS is associated with
exactly one default ASN-GW. However,
ASN-GW functions for every MS may be
distributes amongst multiple
ASN-GWs located in one or more ASNs. The
ASN-GW utilizes Session Redudancy to ensure
a backup ASN-GW is available in case the
primary ASN-GW goes down.
BS Base Station is a logical entity that
represents an aggregation of Control Plane
functional entities that are either paired
with a corresponding function in the ASN
(e.g. BS instance), a resident function
in the CSN or a function in another ASN. The
ASN-GW may also perform Bearer Plane routing
or bridging function.
BSID The Base Station Identifier is a global
unique identifier for a WiMAX base station.
CPE Customer Premise Equipment.
CSN CSN (Connectivity Service Network) is
defined as a set of network functions that
provide IP connectivity services to the
WiMAX subscribers.
Data Path Corresponding to each subscriber, data paths
are created to foward packets between the
ASN-GW and the subscribers.
DPID Data Path ID is used to identify the tunnel
carrying MS traffic between ASN gateways or
between the ASN gateway and base station.
As of 8/28/07, only the GRE key is to be
used as the DPID.
Flow A service flow is a unidirectional logical
flow between the network and the Subscriber
Station. A service flow is created to handle
a different QoS over the connection oriented
MAC. A subscriber can have multiple service
flows associated and each service flow is
associcated with an uplink and downlink
classifier.
GRE Generic Routing Encapsulation. Refer to
RFC 1701 for more details.
LB Load Balancing
Messages Messages are packets exchanged on the
signaling paths.
MS The Mobile Station is a generalized mobile
equipment set providing connectivity between
subscriber equipment and a base station (BS)
The Mobile Station may be a host or a CPE
type of device that can support multiple
hosts.
MSID The Mobile Station Identifier is the 802.16
identifier used for all subscriber stations,
and is used in all the messages over R6. The
identifier associates all requests from a
mobile to the ASN-GW.
Packets Packets are datagrams fowarded over the data
paths.
R1 Communication protocol between mobile and BS
as per the air interface (PHY and MAC)
specifications (IEEE P802.16d/e). R1 may
include additional protocols related to the
management plane.
R2 The interface between the MS and CSN
associated with Authentication,
Services Authorization, IP Host
Configuration management, and mobility
management. This is a logical interface thus
does not reflect a direct protocol interface
between MS and CSN.
R3 The interface between the ASN and the CSN to
support AAA, policy enforcement and mobility
management capabilities. It also encompasses
the bearer plane methods (e.g., tunneling)
to transfer IP data between the ASN and the
CSN.
R4 Communication protocol between ASN-GWs.
R4 consists of a set of control and bearer
plane protocols originating/terminating in
various entities within the ASN that
coordinate MS mobility between ASNs.
In Release 1, R4 is the only interoperable
interface between
heterogeneous or dissimilar ASNs.
R5 Consists of a set of control plane and
bearer plane protocols for internetworking
between CSNs operated by either the home or
visited NSP.
R6 Communication protocol between ASN-GW and BS
R6 consists of a set of control and bearer
plane protocols for communication between
the BS and the ASN GW.
The bearer plane consists of intra-ASN
data path or inter-ASN tunnels between the
BS and ASN-GW.
The control plane includes protocols for
IP tunnel management (establish, modify, and
release) in accordance with the MS mobility
events. R6 may also serve as a conduit for
exchange of MAC states information between
neighboring BSs.
R8 Communication protocol between base
stations.
R8 consists of a set of control plane
message flows and, in some situations,
bearer plane data flows between the
base stations to ensure fast and seamless
handover.
Bearer plane consists of protocols that
allow the data transfer between Base
Stations involved in handover of a
certain MS.
Control plane consists of the inter-BS
communication protocol defined in IEEE
802.16 and additional set of protocols
that allow controlling the data
transfer between the Base Stations involved
in handover of a certain MS.
Session Session is a connection between one or more
MS and a network element in order to
exchange link-level frames or packets.
SFID The service flow is identified using a SFID
(Service Flow Identifier).
Signaling Path A signaling path exists between the BS and
ASN-GW, and is used for all signaling such
as creating, dleteing, authenticating,
as we as additional functions related to
the subscriber.
SR Session Redundancy
Subscriber The 802.16 subscriber entity connects over
the 802.16 airlink, and eventually results
in the creation of the subscriber object at
the ASN-GW.
UHO Unpredicitive Handoff
PMIP Proxy Mobile Internet Protocol
HA Home Agent
REFERENCE
[1] WIMAX Forum Network Architecture,
(Stage 3: Detailed Protocols and Procedures)
Release 1.1.1 September 14, 2007.
Parsed from file CISCO-ASN-GATEWAY-MIB.my.txt
Company: None
Module: CISCO-ASN-GATEWAY-MIB
This module manages Cisco's WiMAX ASN Gateway (ASN-GW).
A WiMAX network supports wireless data communication through
WiMAX radio (802.16) technology.
The high level architecture of a first generation WiMAX network
with the respective protocols for each interface is shown below:
+
| R2 |
+
| | R1 | | R6 | | |
| MS |
| | | | | |
+
| | | R3 |
R8 | R4 | |
| | | |
+
| | R1 | | R6 | |
| MS |
| | | | | | |
+
| |
+
The diagram below depicts the relation of the subscriber to the
session and flows:
+
| ASN-GW | - Subscriber -Session -Flow (connected via data path)
+
| -Flow (connected via data path)
|
+
A subscriber initiates a call from a MS. A session is created
between the BS and the ASN-GW for that call. Multiple flows can
be created for the session with different QOS parameters. For
example one flow can created for a voice stream and another
for data. Data paths are created between the BS and ASN-GW to
forward the data packets of the created flows.
When the first subscriber from any MS connected to a BS
initiates a call via the BS to the ASN-GW, a signaling path is
created between the BS and the ASN-GW. There is only one
signaling path between each BS and ASN-GW. Signaling paths
and base stations can be used interchangeably.
The signaling and data paths remains active as long as there are
subscribers connected to the ASN-GW from any MS connected to the
BS. If a path has no session/flow connected, it will be purged
after a certain period of time. This situation can occur when
all subscribers on a certain path are disconnected. A subscriber
disconnecting from a certain path does not indicate that the
subscriber has left the network, it could simply be handing off
to a different path.
The IP addresses of the signaling and data paths can be the same
or different both in the BS side and in the ASN-GW side.
+
| Base | | ASN-GW |
| Station| | |
| | SigPath | |
| IP(B1)|<............>|IP(A1) |
| | | |
| | | |
| | DataPath 1 | |
| IP(B2)|<............>|IP(A2) |
| | | |
| | DataPath 2 | |
| IP(B3)|<............>|IP(A3) |
+
Relationships:
Base Station 1 to many Mobile Stations
ASN-GW 1 to many Base Stations
Subscriber 1 to 1 Sessions
Session 1 to many Flows
Datapath 1 to many Flows
Signaling Path 1 to 1 Base Station
Acronyms and terms:
AAA AAA refers to a framework that specifies the
protocols procedures for authentications,
authorizatitin and accounting associated
with the user, MS and subscribed serviced.
AGW ASN-GW
ASN ASN (Access Service network) is defined as
a complete set of network functions needed
to provide radio access to a WiMAX
subscriber.
ASN-GW ASN-Gateway is a logical entity that
represents an aggregation of Control Plane
functional entities that are either paired
with a corresponding function in the ASN
(for e.g BS instance) a resident function is
the CSN or another functions in the ASN.
For every MS, a BS is associated with
exactly one default ASN-GW. However,
ASN-GW functions for every MS may be
distributes amongst multiple
ASN-GWs located in one or more ASNs. The
ASN-GW utilizes Session Redudancy to ensure
a backup ASN-GW is available in case the
primary ASN-GW goes down.
BS Base Station is a logical entity that
represents an aggregation of Control Plane
functional entities that are either paired
with a corresponding function in the ASN
(e.g. BS instance), a resident function
in the CSN or a function in another ASN. The
ASN-GW may also perform Bearer Plane routing
or bridging function.
BSID The Base Station Identifier is a global
unique identifier for a WiMAX base station.
CPE Customer Premise Equipment.
CSN CSN (Connectivity Service Network) is
defined as a set of network functions that
provide IP connectivity services to the
WiMAX subscribers.
Data Path Corresponding to each subscriber, data paths
are created to foward packets between the
ASN-GW and the subscribers.
DPID Data Path ID is used to identify the tunnel
carrying MS traffic between ASN gateways or
between the ASN gateway and base station.
As of 8/28/07, only the GRE key is to be
used as the DPID.
Flow A service flow is a unidirectional logical
flow between the network and the Subscriber
Station. A service flow is created to handle
a different QoS over the connection oriented
MAC. A subscriber can have multiple service
flows associated and each service flow is
associcated with an uplink and downlink
classifier.
GRE Generic Routing Encapsulation. Refer to
RFC 1701 for more details.
LB Load Balancing
Messages Messages are packets exchanged on the
signaling paths.
MS The Mobile Station is a generalized mobile
equipment set providing connectivity between
subscriber equipment and a base station (BS)
The Mobile Station may be a host or a CPE
type of device that can support multiple
hosts.
MSID The Mobile Station Identifier is the 802.16
identifier used for all subscriber stations,
and is used in all the messages over R6. The
identifier associates all requests from a
mobile to the ASN-GW.
Packets Packets are datagrams fowarded over the data
paths.
R1 Communication protocol between mobile and BS
as per the air interface (PHY and MAC)
specifications (IEEE P802.16d/e). R1 may
include additional protocols related to the
management plane.
R2 The interface between the MS and CSN
associated with Authentication,
Services Authorization, IP Host
Configuration management, and mobility
management. This is a logical interface thus
does not reflect a direct protocol interface
between MS and CSN.
R3 The interface between the ASN and the CSN to
support AAA, policy enforcement and mobility
management capabilities. It also encompasses
the bearer plane methods (e.g., tunneling)
to transfer IP data between the ASN and the
CSN.
R4 Communication protocol between ASN-GWs.
R4 consists of a set of control and bearer
plane protocols originating/terminating in
various entities within the ASN that
coordinate MS mobility between ASNs.
In Release 1, R4 is the only interoperable
interface between
heterogeneous or dissimilar ASNs.
R5 Consists of a set of control plane and
bearer plane protocols for internetworking
between CSNs operated by either the home or
visited NSP.
R6 Communication protocol between ASN-GW and BS
R6 consists of a set of control and bearer
plane protocols for communication between
the BS and the ASN GW.
The bearer plane consists of intra-ASN
data path or inter-ASN tunnels between the
BS and ASN-GW.
The control plane includes protocols for
IP tunnel management (establish, modify, and
release) in accordance with the MS mobility
events. R6 may also serve as a conduit for
exchange of MAC states information between
neighboring BSs.
R8 Communication protocol between base
stations.
R8 consists of a set of control plane
message flows and, in some situations,
bearer plane data flows between the
base stations to ensure fast and seamless
handover.
Bearer plane consists of protocols that
allow the data transfer between Base
Stations involved in handover of a
certain MS.
Control plane consists of the inter-BS
communication protocol defined in IEEE
802.16 and additional set of protocols
that allow controlling the data
transfer between the Base Stations involved
in handover of a certain MS.
Session Session is a connection between one or more
MS and a network element in order to
exchange link-level frames or packets.
SFID The service flow is identified using a SFID
(Service Flow Identifier).
Signaling Path A signaling path exists between the BS and
ASN-GW, and is used for all signaling such
as creating, dleteing, authenticating,
as we as additional functions related to
the subscriber.
SR Session Redundancy
Subscriber The 802.16 subscriber entity connects over
the 802.16 airlink, and eventually results
in the creation of the subscriber object at
the ASN-GW.
UHO Unpredicitive Handoff
PMIP Proxy Mobile Internet Protocol
HA Home Agent
REFERENCE
[1] WIMAX Forum Network Architecture,
(Stage 3: Detailed Protocols and Procedures)
Release 1.1.1 September 14, 2007.
ciscoAgwMIB MODULE-IDENTITY LAST-UPDATED "200905260000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO "Cisco Systems Customer Service Postal:170 W. Tasman Drive San Jose, CA 95134 USA Tel:+1 800 553-NETS E-mail:[email protected]" DESCRIPTION "This module manages Cisco's WiMAX ASN Gateway (ASN-GW). A WiMAX network supports wireless data communication through WiMAX radio (802.16) technology. The high level architecture of a first generation WiMAX network with the respective protocols for each interface is shown below: + | R2 | + | | R1 | | R6 | | | | MS | | | | | | | + | | | R3 | R8 | R4 | | | | | | + | | R1 | | R6 | | | MS | | | | | | | | + | | + The diagram below depicts the relation of the subscriber to the session and flows: + | ASN-GW | - Subscriber -Session -Flow (connected via data path) + | -Flow (connected via data path) | + A subscriber initiates a call from a MS. A session is created between the BS and the ASN-GW for that call. Multiple flows can be created for the session with different QOS parameters. For example one flow can created for a voice stream and another for data. Data paths are created between the BS and ASN-GW to forward the data packets of the created flows. When the first subscriber from any MS connected to a BS initiates a call via the BS to the ASN-GW, a signaling path is created between the BS and the ASN-GW. There is only one signaling path between each BS and ASN-GW. Signaling paths and base stations can be used interchangeably. The signaling and data paths remains active as long as there are subscribers connected to the ASN-GW from any MS connected to the BS. If a path has no session/flow connected, it will be purged after a certain period of time. This situation can occur when all subscribers on a certain path are disconnected. A subscriber disconnecting from a certain path does not indicate that the subscriber has left the network, it could simply be handing off to a different path. The IP addresses of the signaling and data paths can be the same or different both in the BS side and in the ASN-GW side. + | Base | | ASN-GW | | Station| | | | | SigPath | | | IP(B1)|<............>|IP(A1) | | | | | | | | | | | DataPath 1 | | | IP(B2)|<............>|IP(A2) | | | | | | | DataPath 2 | | | IP(B3)|<............>|IP(A3) | + Relationships: Base Station 1 to many Mobile Stations ASN-GW 1 to many Base Stations Subscriber 1 to 1 Sessions Session 1 to many Flows Datapath 1 to many Flows Signaling Path 1 to 1 Base Station Acronyms and terms: AAA AAA refers to a framework that specifies the protocols procedures for authentications, authorizatitin and accounting associated with the user, MS and subscribed serviced. AGW ASN-GW ASN ASN (Access Service network) is defined as a complete set of network functions needed to provide radio access to a WiMAX subscriber. ASN-GW ASN-Gateway is a logical entity that represents an aggregation of Control Plane functional entities that are either paired with a corresponding function in the ASN (for e.g BS instance) a resident function is the CSN or another functions in the ASN. For every MS, a BS is associated with exactly one default ASN-GW. However, ASN-GW functions for every MS may be distributes amongst multiple ASN-GWs located in one or more ASNs. The ASN-GW utilizes Session Redudancy to ensure a backup ASN-GW is available in case the primary ASN-GW goes down. BS Base Station is a logical entity that represents an aggregation of Control Plane functional entities that are either paired with a corresponding function in the ASN (e.g. BS instance), a resident function in the CSN or a function in another ASN. The ASN-GW may also perform Bearer Plane routing or bridging function. BSID The Base Station Identifier is a global unique identifier for a WiMAX base station. CPE Customer Premise Equipment. CSN CSN (Connectivity Service Network) is defined as a set of network functions that provide IP connectivity services to the WiMAX subscribers. Data Path Corresponding to each subscriber, data paths are created to foward packets between the ASN-GW and the subscribers. DPID Data Path ID is used to identify the tunnel carrying MS traffic between ASN gateways or between the ASN gateway and base station. As of 8/28/07, only the GRE key is to be used as the DPID. Flow A service flow is a unidirectional logical flow between the network and the Subscriber Station. A service flow is created to handle a different QoS over the connection oriented MAC. A subscriber can have multiple service flows associated and each service flow is associcated with an uplink and downlink classifier. GRE Generic Routing Encapsulation. Refer to RFC 1701 for more details. LB Load Balancing Messages Messages are packets exchanged on the signaling paths. MS The Mobile Station is a generalized mobile equipment set providing connectivity between subscriber equipment and a base station (BS) The Mobile Station may be a host or a CPE type of device that can support multiple hosts. MSID The Mobile Station Identifier is the 802.16 identifier used for all subscriber stations, and is used in all the messages over R6. The identifier associates all requests from a mobile to the ASN-GW. Packets Packets are datagrams fowarded over the data paths. R1 Communication protocol between mobile and BS as per the air interface (PHY and MAC) specifications (IEEE P802.16d/e). R1 may include additional protocols related to the management plane. R2 The interface between the MS and CSN associated with Authentication, Services Authorization, IP Host Configuration management, and mobility management. This is a logical interface thus does not reflect a direct protocol interface between MS and CSN. R3 The interface between the ASN and the CSN to support AAA, policy enforcement and mobility management capabilities. It also encompasses the bearer plane methods (e.g., tunneling) to transfer IP data between the ASN and the CSN. R4 Communication protocol between ASN-GWs. R4 consists of a set of control and bearer plane protocols originating/terminating in various entities within the ASN that coordinate MS mobility between ASNs. In Release 1, R4 is the only interoperable interface between heterogeneous or dissimilar ASNs. R5 Consists of a set of control plane and bearer plane protocols for internetworking between CSNs operated by either the home or visited NSP. R6 Communication protocol between ASN-GW and BS R6 consists of a set of control and bearer plane protocols for communication between the BS and the ASN GW. The bearer plane consists of intra-ASN data path or inter-ASN tunnels between the BS and ASN-GW. The control plane includes protocols for IP tunnel management (establish, modify, and release) in accordance with the MS mobility events. R6 may also serve as a conduit for exchange of MAC states information between neighboring BSs. R8 Communication protocol between base stations. R8 consists of a set of control plane message flows and, in some situations, bearer plane data flows between the base stations to ensure fast and seamless handover. Bearer plane consists of protocols that allow the data transfer between Base Stations involved in handover of a certain MS. Control plane consists of the inter-BS communication protocol defined in IEEE 802.16 and additional set of protocols that allow controlling the data transfer between the Base Stations involved in handover of a certain MS. Session Session is a connection between one or more MS and a network element in order to exchange link-level frames or packets. SFID The service flow is identified using a SFID (Service Flow Identifier). Signaling Path A signaling path exists between the BS and ASN-GW, and is used for all signaling such as creating, dleteing, authenticating, as we as additional functions related to the subscriber. SR Session Redundancy Subscriber The 802.16 subscriber entity connects over the 802.16 airlink, and eventually results in the creation of the subscriber object at the ASN-GW. UHO Unpredicitive Handoff PMIP Proxy Mobile Internet Protocol HA Home Agent REFERENCE [1] WIMAX Forum Network Architecture, (Stage 3: Detailed Protocols and Procedures) Release 1.1.1 September 14, 2007." REVISION "200905260000Z" DESCRIPTION "Following objects were added to cagwStateTable cagwCurrentPmipEnabledSubs, Following objects were added to cagwUserGrpStatistics cagwUserGrpPodReqRecv, cagwUserGrpPodSuccessNotifsSent, cagwUserGrpPodFailureNotifsSent, cagwUserGrpCoaReqRecv, cagwUserGrpCoaSuccessNotifsSent, cagwUserGrpCoaFailureNotifsSent, cagwUserGrpRejSession, Following objects were added to cagwGlobalStatistics cagwPktsDroppedMipIncomplete, cagwCreatedPmipEnabledSubs, cagwDeletedPmipEnabledSubs, cagwPktsDropPmipStaticIpHost, cagwIdleModeEntryMsBsInitiated, cagwIdleModeEntryBwgInitiated, cagwIdleModeEntryFailures, cagwIdleModeExitMsBsInitiated, cagwIdleModeExitBwgInitiated, cagwIdleModeExitFailures, cagwIdleModeLocUpdtPgidChange, cagwIdleModeLocUpdtPowerDown, cagwIdleModeLocUpdtPeriodic, cagwIdleModeLocUpdtFailures, cagwIdleModePageAttemptsDwnlnkData, cagwIdleModePageFailuresDwnlnkData, cagwIdleModePageAttemptsLocUpdt, cagwIdleModePageFailuresLocUpdt, cagwIdleModeDirectedPagingSuccess, cagwIdleModeDirectedPagingRetries, cagwIdleModeFloodPagingSuccess, cagwIdleModeFloodPagingRetries, cagwPodRequestsRecv, cagwPodSuccessNotifsSent, cagwPodFailureNotifsSent, cagwCoaReqRecv, cagwCoaSuccessNotifsSent, cagwCoaFailureNotifsSent, cagwHotlineUplinkPktDropAclDeny, cagwHotlineDownlinkPktDropAclDeny, cagwUplinkPktDropUsrgrpAclDeny, cagwDownlinkPktDropUsrgrpAclDeny, cagwDownlinkPktDropPagingAclDeny, Following object were added to cagwDhcpStatistics cagwDhcpProxyDiscoverPackets, cagwDhcpProxyOfferPackets, cagwDhcpProxyRequestPackets, cagwDhcpProxyDeclinePackets, cagwDhcpProxyAckPackets, cagwDhcpProxyNakPackets, cagwDhcpProxyReleasePackets, cagwDhcpProxyInformPackets, cagwDhcpProxyLeaseQueryPackets, cagwDhcpProxyUnknownPackets" REVISION "200804220000Z" DESCRIPTION "Following objects were added to cagwStateTable cagwCurrentFramedRoutes, cagwCurrentFramedRouteSubs, cagwCurrentAutoProvSessions, cagwCurrentSessionsWithIpPktsRedir. Following objects were added to cagwGlobalStatistics cagwRejectedSessionUnapprovedBs, cagwPktsDroppedStaticIpHostNotAllowed, cagwPktsDroppedMulticastBroadcast cagwSlaProfileNotFound. Following objects were obsoleted in cagwGlobalStatistics cagwFramedRouteInserted, cagwFramedRouteInsertFailed, cagwFramedRouteDeleted. Following objects were added to cagwUserGrpStatistics cagwUserGrpOverwritten." REVISION "200803240000Z" DESCRIPTION "Following objects were deprecated in cagwGlobalStatistics cagwReceivedDataPkts, cagwReceivedDataBytes, cagwSentDataPkts, cagwSentDataBytes. Following objects were added to cagwGlobalStatistics cagwIpGreReceivedDataPkts, cagwIpGreReceivedDataBytes, cagwIpGreSentDataPkts, cagwIpGreSentDataBytes, cagwEthGreReceivedDataPkts, cagwEthGreReceivedDataBytes, cagwEthGreSentdDataPkts, cagwEthGreSentDataBytes, cagwRejectedHosts, cagwAgedOutStaticHosts, cagwSuccessfulHandoff, cagwFailedHandoff, cagwSuccessfulCMACKeyUpdate, cagwFailedCMACKeyUpdate, cagwSuccessfulSecurityKeyExchange, cagwFailedSecurityKeyExchange, cagwIpGreReceivedRedirectedPkts, cagwIpGreReceivedRedirectedBytes, cagwEthGreReceivedRedirectedPkts, cagwEthGreReceivedRedirectedBytes, cagwThrottlingOfPuntsDataPktsDrops, cagwLearningUpStreamDataPktsDrops, cagwPuntedDataPkts. Following objects were deprecated in cagwUserGrpEntry cagwUserGrpPacketsSent, cagwUserGrpBytesSent, cagwUserGrpPacketsReceived, cagwUserGrpBytesReceived. Following objects were added to cagwUserGrpEntry cagwUserGrpIpGrePacketsSent, cagwUserGrpIpGreBytesSent, cagwUserGrpIpGrePacketsReceived, cagwUserGrpIpGreBytesReceived, cagwUserGrpEthGrePacketsSent, cagwUserGrpEthGreBytesSent, cagwUserGrpEthGrePacketsReceived, cagwUserGrpEthGreBytesReceived Following objects were made obsolete cagwPathTable. Following object were added to cagwPathStatistics cagwPathRev1Table Following object were added to cagwStatistics cagwArpStatistics." REVISION "200709260000Z" DESCRIPTION "Initial version of this MIB module." ::= { ciscoMgmt 638 }
ciscoAgwMIB OBJECT IDENTIFIER ::= { ciscoMgmt 638 }
Vendor: Cisco
Module: CISCO-ASN-GATEWAY-MIB
[Automatically extracted from oidview.com]
ciscoAgwMIB MODULE-IDENTITY LAST-UPDATED "200905260000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO "Cisco Systems Customer Service Postal:170 W. Tasman Drive San Jose, CA 95134 USA Tel:+1 800 553-NETS E-mail:[email protected]" DESCRIPTION "This module manages Cisco's WiMAX ASN Gateway (ASN-GW). A WiMAX network supports wireless data communication through WiMAX radio (802.16) technology. The high level architecture of a first generation WiMAX network with the respective protocols for each interface is shown below: + | R2 | + | | R1 | | R6 | | | | MS | | | | | | | + | | | R3 | R8 | R4 | | | | | | + | | R1 | | R6 | | | MS | | | | | | | | + | | + The diagram below depicts the relation of the subscriber to the session and flows: + | ASN-GW | - Subscriber -Session -Flow (connected via data path) + | -Flow (connected via data path) | + A subscriber initiates a call from a MS. A session is created between the BS and the ASN-GW for that call. Multiple flows can be created for the session with different QOS parameters. For example one flow can created for a voice stream and another for data. Data paths are created between the BS and ASN-GW to forward the data packets of the created flows. When the first subscriber from any MS connected to a BS initiates a call via the BS to the ASN-GW, a signaling path is created between the BS and the ASN-GW. There is only one signaling path between each BS and ASN-GW. Signaling paths and base stations can be used interchangeably. The signaling and data paths remains active as long as there are subscribers connected to the ASN-GW from any MS connected to the BS. If a path has no session/flow connected, it will be purged after a certain period of time. This situation can occur when all subscribers on a certain path are disconnected. A subscriber disconnecting from a certain path does not indicate that the subscriber has left the network, it could simply be handing off to a different path. The IP addresses of the signaling and data paths can be the same or different both in the BS side and in the ASN-GW side. + | Base | | ASN-GW | | Station| | | | | SigPath | | | IP(B1)|<............>|IP(A1) | | | | | | | | | | | DataPath 1 | | | IP(B2)|<............>|IP(A2) | | | | | | | DataPath 2 | | | IP(B3)|<............>|IP(A3) | + Relationships: Base Station 1 to many Mobile Stations ASN-GW 1 to many Base Stations Subscriber 1 to 1 Sessions Session 1 to many Flows Datapath 1 to many Flows Signaling Path 1 to 1 Base Station Acronyms and terms: AAA AAA refers to a framework that specifies the protocols procedures for authentications, authorizatitin and accounting associated with the user, MS and subscribed serviced. AGW ASN-GW ASN ASN (Access Service network) is defined as a complete set of network functions needed to provide radio access to a WiMAX subscriber. ASN-GW ASN-Gateway is a logical entity that represents an aggregation of Control Plane functional entities that are either paired with a corresponding function in the ASN (for e.g BS instance) a resident function is the CSN or another functions in the ASN. For every MS, a BS is associated with exactly one default ASN-GW. However, ASN-GW functions for every MS may be distributes amongst multiple ASN-GWs located in one or more ASNs. The ASN-GW utilizes Session Redudancy to ensure a backup ASN-GW is available in case the primary ASN-GW goes down. BS Base Station is a logical entity that represents an aggregation of Control Plane functional entities that are either paired with a corresponding function in the ASN (e.g. BS instance), a resident function in the CSN or a function in another ASN. The ASN-GW may also perform Bearer Plane routing or bridging function. BSID The Base Station Identifier is a global unique identifier for a WiMAX base station. CPE Customer Premise Equipment. CSN CSN (Connectivity Service Network) is defined as a set of network functions that provide IP connectivity services to the WiMAX subscribers. Data Path Corresponding to each subscriber, data paths are created to foward packets between the ASN-GW and the subscribers. DPID Data Path ID is used to identify the tunnel carrying MS traffic between ASN gateways or between the ASN gateway and base station. As of 8/28/07, only the GRE key is to be used as the DPID. Flow A service flow is a unidirectional logical flow between the network and the Subscriber Station. A service flow is created to handle a different QoS over the connection oriented MAC. A subscriber can have multiple service flows associated and each service flow is associcated with an uplink and downlink classifier. GRE Generic Routing Encapsulation. Refer to RFC 1701 for more details. LB Load Balancing Messages Messages are packets exchanged on the signaling paths. MS The Mobile Station is a generalized mobile equipment set providing connectivity between subscriber equipment and a base station (BS) The Mobile Station may be a host or a CPE type of device that can support multiple hosts. MSID The Mobile Station Identifier is the 802.16 identifier used for all subscriber stations, and is used in all the messages over R6. The identifier associates all requests from a mobile to the ASN-GW. Packets Packets are datagrams fowarded over the data paths. R1 Communication protocol between mobile and BS as per the air interface (PHY and MAC) specifications (IEEE P802.16d/e). R1 may include additional protocols related to the management plane. R2 The interface between the MS and CSN associated with Authentication, Services Authorization, IP Host Configuration management, and mobility management. This is a logical interface thus does not reflect a direct protocol interface between MS and CSN. R3 The interface between the ASN and the CSN to support AAA, policy enforcement and mobility management capabilities. It also encompasses the bearer plane methods (e.g., tunneling) to transfer IP data between the ASN and the CSN. R4 Communication protocol between ASN-GWs. R4 consists of a set of control and bearer plane protocols originating/terminating in various entities within the ASN that coordinate MS mobility between ASNs. In Release 1, R4 is the only interoperable interface between heterogeneous or dissimilar ASNs. R5 Consists of a set of control plane and bearer plane protocols for internetworking between CSNs operated by either the home or visited NSP. R6 Communication protocol between ASN-GW and BS R6 consists of a set of control and bearer plane protocols for communication between the BS and the ASN GW. The bearer plane consists of intra-ASN data path or inter-ASN tunnels between the BS and ASN-GW. The control plane includes protocols for IP tunnel management (establish, modify, and release) in accordance with the MS mobility events. R6 may also serve as a conduit for exchange of MAC states information between neighboring BSs. R8 Communication protocol between base stations. R8 consists of a set of control plane message flows and, in some situations, bearer plane data flows between the base stations to ensure fast and seamless handover. Bearer plane consists of protocols that allow the data transfer between Base Stations involved in handover of a certain MS. Control plane consists of the inter-BS communication protocol defined in IEEE 802.16 and additional set of protocols that allow controlling the data transfer between the Base Stations involved in handover of a certain MS. Session Session is a connection between one or more MS and a network element in order to exchange link-level frames or packets. SFID The service flow is identified using a SFID (Service Flow Identifier). Signaling Path A signaling path exists between the BS and ASN-GW, and is used for all signaling such as creating, dleteing, authenticating, as we as additional functions related to the subscriber. SR Session Redundancy Subscriber The 802.16 subscriber entity connects over the 802.16 airlink, and eventually results in the creation of the subscriber object at the ASN-GW. UHO Unpredicitive Handoff PMIP Proxy Mobile Internet Protocol HA Home Agent REFERENCE [1] WIMAX Forum Network Architecture, (Stage 3: Detailed Protocols and Procedures) Release 1.1.1 September 14, 2007." REVISION "200905260000Z" DESCRIPTION "Following objects were added to cagwStateTable cagwCurrentPmipEnabledSubs, Following objects were added to cagwUserGrpStatistics cagwUserGrpPodReqRecv, cagwUserGrpPodSuccessNotifsSent, cagwUserGrpPodFailureNotifsSent, cagwUserGrpCoaReqRecv, cagwUserGrpCoaSuccessNotifsSent, cagwUserGrpCoaFailureNotifsSent, cagwUserGrpRejSession, Following objects were added to cagwGlobalStatistics cagwPktsDroppedMipIncomplete, cagwCreatedPmipEnabledSubs, cagwDeletedPmipEnabledSubs, cagwPktsDropPmipStaticIpHost, cagwIdleModeEntryMsBsInitiated, cagwIdleModeEntryBwgInitiated, cagwIdleModeEntryFailures, cagwIdleModeExitMsBsInitiated, cagwIdleModeExitBwgInitiated, cagwIdleModeExitFailures, cagwIdleModeLocUpdtPgidChange, cagwIdleModeLocUpdtPowerDown, cagwIdleModeLocUpdtPeriodic, cagwIdleModeLocUpdtFailures, cagwIdleModePageAttemptsDwnlnkData, cagwIdleModePageFailuresDwnlnkData, cagwIdleModePageAttemptsLocUpdt, cagwIdleModePageFailuresLocUpdt, cagwIdleModeDirectedPagingSuccess, cagwIdleModeDirectedPagingRetries, cagwIdleModeFloodPagingSuccess, cagwIdleModeFloodPagingRetries, cagwPodRequestsRecv, cagwPodSuccessNotifsSent, cagwPodFailureNotifsSent, cagwCoaReqRecv, cagwCoaSuccessNotifsSent, cagwCoaFailureNotifsSent, cagwHotlineUplinkPktDropAclDeny, cagwHotlineDownlinkPktDropAclDeny, cagwUplinkPktDropUsrgrpAclDeny, cagwDownlinkPktDropUsrgrpAclDeny, cagwDownlinkPktDropPagingAclDeny, Following object were added to cagwDhcpStatistics cagwDhcpProxyDiscoverPackets, cagwDhcpProxyOfferPackets, cagwDhcpProxyRequestPackets, cagwDhcpProxyDeclinePackets, cagwDhcpProxyAckPackets, cagwDhcpProxyNakPackets, cagwDhcpProxyReleasePackets, cagwDhcpProxyInformPackets, cagwDhcpProxyLeaseQueryPackets, cagwDhcpProxyUnknownPackets" REVISION "200804220000Z" DESCRIPTION "Following objects were added to cagwStateTable cagwCurrentFramedRoutes, cagwCurrentFramedRouteSubs, cagwCurrentAutoProvSessions, cagwCurrentSessionsWithIpPktsRedir. Following objects were added to cagwGlobalStatistics cagwRejectedSessionUnapprovedBs, cagwPktsDroppedStaticIpHostNotAllowed, cagwPktsDroppedMulticastBroadcast cagwSlaProfileNotFound. Following objects were obsoleted in cagwGlobalStatistics cagwFramedRouteInserted, cagwFramedRouteInsertFailed, cagwFramedRouteDeleted. Following objects were added to cagwUserGrpStatistics cagwUserGrpOverwritten." REVISION "200803240000Z" DESCRIPTION "Following objects were deprecated in cagwGlobalStatistics cagwReceivedDataPkts, cagwReceivedDataBytes, cagwSentDataPkts, cagwSentDataBytes. Following objects were added to cagwGlobalStatistics cagwIpGreReceivedDataPkts, cagwIpGreReceivedDataBytes, cagwIpGreSentDataPkts, cagwIpGreSentDataBytes, cagwEthGreReceivedDataPkts, cagwEthGreReceivedDataBytes, cagwEthGreSentdDataPkts, cagwEthGreSentDataBytes, cagwRejectedHosts, cagwAgedOutStaticHosts, cagwSuccessfulHandoff, cagwFailedHandoff, cagwSuccessfulCMACKeyUpdate, cagwFailedCMACKeyUpdate, cagwSuccessfulSecurityKeyExchange, cagwFailedSecurityKeyExchange, cagwIpGreReceivedRedirectedPkts, cagwIpGreReceivedRedirectedBytes, cagwEthGreReceivedRedirectedPkts, cagwEthGreReceivedRedirectedBytes, cagwThrottlingOfPuntsDataPktsDrops, cagwLearningUpStreamDataPktsDrops, cagwPuntedDataPkts. Following objects were deprecated in cagwUserGrpEntry cagwUserGrpPacketsSent, cagwUserGrpBytesSent, cagwUserGrpPacketsReceived, cagwUserGrpBytesReceived. Following objects were added to cagwUserGrpEntry cagwUserGrpIpGrePacketsSent, cagwUserGrpIpGreBytesSent, cagwUserGrpIpGrePacketsReceived, cagwUserGrpIpGreBytesReceived, cagwUserGrpEthGrePacketsSent, cagwUserGrpEthGreBytesSent, cagwUserGrpEthGrePacketsReceived, cagwUserGrpEthGreBytesReceived Following objects were made obsolete cagwPathTable. Following object were added to cagwPathStatistics cagwPathRev1Table Following object were added to cagwStatistics cagwArpStatistics." REVISION "200709260000Z" DESCRIPTION "Initial version of this MIB module." ::= { ciscoMgmt 638 }
ciscoAgwMIB MODULE-IDENTITY LAST-UPDATED "200905260000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO "Cisco Systems Customer Service Postal:170 W. Tasman Drive San Jose, CA 95134 USA Tel:+1 800 553-NETS E-mail:[email protected]" DESCRIPTION "This module manages Cisco's WiMAX ASN Gateway (ASN-GW). A WiMAX network supports wireless data communication through WiMAX radio (802.16) technology. The high level architecture of a first generation WiMAX network with the respective protocols for each interface is shown below: + | R2 | + | | R1 | | R6 | | | | MS | | | | | | | + | | | R3 | R8 | R4 | | | | | | + | | R1 | | R6 | | | MS | | | | | | | | + | | + The diagram below depicts the relation of the subscriber to the session and flows: + | ASN-GW | - Subscriber -Session -Flow (connected via data path) + | -Flow (connected via data path) | + A subscriber initiates a call from a MS. A session is created between the BS and the ASN-GW for that call. Multiple flows can be created for the session with different QOS parameters. For example one flow can created for a voice stream and another for data. Data paths are created between the BS and ASN-GW to forward the data packets of the created flows. When the first subscriber from any MS connected to a BS initiates a call via the BS to the ASN-GW, a signaling path is created between the BS and the ASN-GW. There is only one signaling path between each BS and ASN-GW. Signaling paths and base stations can be used interchangeably. The signaling and data paths remains active as long as there are subscribers connected to the ASN-GW from any MS connected to the BS. If a path has no session/flow connected, it will be purged after a certain period of time. This situation can occur when all subscribers on a certain path are disconnected. A subscriber disconnecting from a certain path does not indicate that the subscriber has left the network, it could simply be handing off to a different path. The IP addresses of the signaling and data paths can be the same or different both in the BS side and in the ASN-GW side. + | Base | | ASN-GW | | Station| | | | | SigPath | | | IP(B1)|<............>|IP(A1) | | | | | | | | | | | DataPath 1 | | | IP(B2)|<............>|IP(A2) | | | | | | | DataPath 2 | | | IP(B3)|<............>|IP(A3) | + Relationships: Base Station 1 to many Mobile Stations ASN-GW 1 to many Base Stations Subscriber 1 to 1 Sessions Session 1 to many Flows Datapath 1 to many Flows Signaling Path 1 to 1 Base Station Acronyms and terms: AAA AAA refers to a framework that specifies the protocols procedures for authentications, authorizatitin and accounting associated with the user, MS and subscribed serviced. AGW ASN-GW ASN ASN (Access Service network) is defined as a complete set of network functions needed to provide radio access to a WiMAX subscriber. ASN-GW ASN-Gateway is a logical entity that represents an aggregation of Control Plane functional entities that are either paired with a corresponding function in the ASN (for e.g BS instance) a resident function is the CSN or another functions in the ASN. For every MS, a BS is associated with exactly one default ASN-GW. However, ASN-GW functions for every MS may be distributes amongst multiple ASN-GWs located in one or more ASNs. The ASN-GW utilizes Session Redudancy to ensure a backup ASN-GW is available in case the primary ASN-GW goes down. BS Base Station is a logical entity that represents an aggregation of Control Plane functional entities that are either paired with a corresponding function in the ASN (e.g. BS instance), a resident function in the CSN or a function in another ASN. The ASN-GW may also perform Bearer Plane routing or bridging function. BSID The Base Station Identifier is a global unique identifier for a WiMAX base station. CPE Customer Premise Equipment. CSN CSN (Connectivity Service Network) is defined as a set of network functions that provide IP connectivity services to the WiMAX subscribers. Data Path Corresponding to each subscriber, data paths are created to foward packets between the ASN-GW and the subscribers. DPID Data Path ID is used to identify the tunnel carrying MS traffic between ASN gateways or between the ASN gateway and base station. As of 8/28/07, only the GRE key is to be used as the DPID. Flow A service flow is a unidirectional logical flow between the network and the Subscriber Station. A service flow is created to handle a different QoS over the connection oriented MAC. A subscriber can have multiple service flows associated and each service flow is associcated with an uplink and downlink classifier. GRE Generic Routing Encapsulation. Refer to RFC 1701 for more details. LB Load Balancing Messages Messages are packets exchanged on the signaling paths. MS The Mobile Station is a generalized mobile equipment set providing connectivity between subscriber equipment and a base station (BS) The Mobile Station may be a host or a CPE type of device that can support multiple hosts. MSID The Mobile Station Identifier is the 802.16 identifier used for all subscriber stations, and is used in all the messages over R6. The identifier associates all requests from a mobile to the ASN-GW. Packets Packets are datagrams fowarded over the data paths. R1 Communication protocol between mobile and BS as per the air interface (PHY and MAC) specifications (IEEE P802.16d/e). R1 may include additional protocols related to the management plane. R2 The interface between the MS and CSN associated with Authentication, Services Authorization, IP Host Configuration management, and mobility management. This is a logical interface thus does not reflect a direct protocol interface between MS and CSN. R3 The interface between the ASN and the CSN to support AAA, policy enforcement and mobility management capabilities. It also encompasses the bearer plane methods (e.g., tunneling) to transfer IP data between the ASN and the CSN. R4 Communication protocol between ASN-GWs. R4 consists of a set of control and bearer plane protocols originating/terminating in various entities within the ASN that coordinate MS mobility between ASNs. In Release 1, R4 is the only interoperable interface between heterogeneous or dissimilar ASNs. R5 Consists of a set of control plane and bearer plane protocols for internetworking between CSNs operated by either the home or visited NSP. R6 Communication protocol between ASN-GW and BS R6 consists of a set of control and bearer plane protocols for communication between the BS and the ASN GW. The bearer plane consists of intra-ASN data path or inter-ASN tunnels between the BS and ASN-GW. The control plane includes protocols for IP tunnel management (establish, modify, and release) in accordance with the MS mobility events. R6 may also serve as a conduit for exchange of MAC states information between neighboring BSs. R8 Communication protocol between base stations. R8 consists of a set of control plane message flows and, in some situations, bearer plane data flows between the base stations to ensure fast and seamless handover. Bearer plane consists of protocols that allow the data transfer between Base Stations involved in handover of a certain MS. Control plane consists of the inter-BS communication protocol defined in IEEE 802.16 and additional set of protocols that allow controlling the data transfer between the Base Stations involved in handover of a certain MS. Session Session is a connection between one or more MS and a network element in order to exchange link-level frames or packets. SFID The service flow is identified using a SFID (Service Flow Identifier). Signaling Path A signaling path exists between the BS and ASN-GW, and is used for all signaling such as creating, dleteing, authenticating, as we as additional functions related to the subscriber. SR Session Redundancy Subscriber The 802.16 subscriber entity connects over the 802.16 airlink, and eventually results in the creation of the subscriber object at the ASN-GW. UHO Unpredicitive Handoff PMIP Proxy Mobile Internet Protocol HA Home Agent REFERENCE [1] WIMAX Forum Network Architecture, (Stage 3: Detailed Protocols and Procedures) Release 1.1.1 September 14, 2007." REVISION "200905260000Z" DESCRIPTION "Following objects were added to cagwStateTable cagwCurrentPmipEnabledSubs, Following objects were added to cagwUserGrpStatistics cagwUserGrpPodReqRecv, cagwUserGrpPodSuccessNotifsSent, cagwUserGrpPodFailureNotifsSent, cagwUserGrpCoaReqRecv, cagwUserGrpCoaSuccessNotifsSent, cagwUserGrpCoaFailureNotifsSent, cagwUserGrpRejSession, Following objects were added to cagwGlobalStatistics cagwPktsDroppedMipIncomplete, cagwCreatedPmipEnabledSubs, cagwDeletedPmipEnabledSubs, cagwPktsDropPmipStaticIpHost, cagwIdleModeEntryMsBsInitiated, cagwIdleModeEntryBwgInitiated, cagwIdleModeEntryFailures, cagwIdleModeExitMsBsInitiated, cagwIdleModeExitBwgInitiated, cagwIdleModeExitFailures, cagwIdleModeLocUpdtPgidChange, cagwIdleModeLocUpdtPowerDown, cagwIdleModeLocUpdtPeriodic, cagwIdleModeLocUpdtFailures, cagwIdleModePageAttemptsDwnlnkData, cagwIdleModePageFailuresDwnlnkData, cagwIdleModePageAttemptsLocUpdt, cagwIdleModePageFailuresLocUpdt, cagwIdleModeDirectedPagingSuccess, cagwIdleModeDirectedPagingRetries, cagwIdleModeFloodPagingSuccess, cagwIdleModeFloodPagingRetries, cagwPodRequestsRecv, cagwPodSuccessNotifsSent, cagwPodFailureNotifsSent, cagwCoaReqRecv, cagwCoaSuccessNotifsSent, cagwCoaFailureNotifsSent, cagwHotlineUplinkPktDropAclDeny, cagwHotlineDownlinkPktDropAclDeny, cagwUplinkPktDropUsrgrpAclDeny, cagwDownlinkPktDropUsrgrpAclDeny, cagwDownlinkPktDropPagingAclDeny, Following object were added to cagwDhcpStatistics cagwDhcpProxyDiscoverPackets, cagwDhcpProxyOfferPackets, cagwDhcpProxyRequestPackets, cagwDhcpProxyDeclinePackets, cagwDhcpProxyAckPackets, cagwDhcpProxyNakPackets, cagwDhcpProxyReleasePackets, cagwDhcpProxyInformPackets, cagwDhcpProxyLeaseQueryPackets, cagwDhcpProxyUnknownPackets" REVISION "200804220000Z" DESCRIPTION "Following objects were added to cagwStateTable cagwCurrentFramedRoutes, cagwCurrentFramedRouteSubs, cagwCurrentAutoProvSessions, cagwCurrentSessionsWithIpPktsRedir. Following objects were added to cagwGlobalStatistics cagwRejectedSessionUnapprovedBs, cagwPktsDroppedStaticIpHostNotAllowed, cagwPktsDroppedMulticastBroadcast cagwSlaProfileNotFound. Following objects were obsoleted in cagwGlobalStatistics cagwFramedRouteInserted, cagwFramedRouteInsertFailed, cagwFramedRouteDeleted. Following objects were added to cagwUserGrpStatistics cagwUserGrpOverwritten." REVISION "200803240000Z" DESCRIPTION "Following objects were deprecated in cagwGlobalStatistics cagwReceivedDataPkts, cagwReceivedDataBytes, cagwSentDataPkts, cagwSentDataBytes. Following objects were added to cagwGlobalStatistics cagwIpGreReceivedDataPkts, cagwIpGreReceivedDataBytes, cagwIpGreSentDataPkts, cagwIpGreSentDataBytes, cagwEthGreReceivedDataPkts, cagwEthGreReceivedDataBytes, cagwEthGreSentdDataPkts, cagwEthGreSentDataBytes, cagwRejectedHosts, cagwAgedOutStaticHosts, cagwSuccessfulHandoff, cagwFailedHandoff, cagwSuccessfulCMACKeyUpdate, cagwFailedCMACKeyUpdate, cagwSuccessfulSecurityKeyExchange, cagwFailedSecurityKeyExchange, cagwIpGreReceivedRedirectedPkts, cagwIpGreReceivedRedirectedBytes, cagwEthGreReceivedRedirectedPkts, cagwEthGreReceivedRedirectedBytes, cagwThrottlingOfPuntsDataPktsDrops, cagwLearningUpStreamDataPktsDrops, cagwPuntedDataPkts. Following objects were deprecated in cagwUserGrpEntry cagwUserGrpPacketsSent, cagwUserGrpBytesSent, cagwUserGrpPacketsReceived, cagwUserGrpBytesReceived. Following objects were added to cagwUserGrpEntry cagwUserGrpIpGrePacketsSent, cagwUserGrpIpGreBytesSent, cagwUserGrpIpGrePacketsReceived, cagwUserGrpIpGreBytesReceived, cagwUserGrpEthGrePacketsSent, cagwUserGrpEthGreBytesSent, cagwUserGrpEthGrePacketsReceived, cagwUserGrpEthGreBytesReceived Following objects were made obsolete cagwPathTable. Following object were added to cagwPathStatistics cagwPathRev1Table Following object were added to cagwStatistics cagwArpStatistics." REVISION "200709260000Z" DESCRIPTION "Initial version of this MIB module." ::= { ciscoMgmt 638 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.638.0 | ciscoAgwMIBNotifs | 6 | 6 | None |
| 1.3.6.1.4.1.9.9.638.1 | ciscoAgwMIBObjects | 5 | 288 | None |
| 1.3.6.1.4.1.9.9.638.2 | ciscoAgwMIBConform | 2 | 27 | None |
To many brothers! Only 100 nearest brothers are shown.
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| ... | ||||
| 1.3.6.1.4.1.9.9.589 | ciscoGslbSystemMIB | 3 | 103 | This MIB module defines objects for network and system information of Global Server Load Balancer(GSLB) as a network device. A G… |
| 1.3.6.1.4.1.9.9.590 | ciscoCvpMIB | 3 | 255 | The Cisco Unified Customer Voice Portal (CVP) application integrates with both traditional time-division multiplexing (TDM) and I… |
| 1.3.6.1.4.1.9.9.592 | ciscoPrefPathMIB | 3 | 56 | The MIB module for the management of preferred path. This MIB enables managers to configure and monitor Preferred Path parameters.… |
| 1.3.6.1.4.1.9.9.593 | ciscoFcSdvMIB | 3 | 28 | This MIB instrumentation is for managing Fibre Channel (FC) SAN Device Virtualization (SDV) solution on Cisco Fibre Channel devic… |
| 1.3.6.1.4.1.9.9.594 | ciscoApplicationAccelerationMIB | 3 | 37 | This is a MIB for managing Application Acceleration System(s). This MIB includes instrumentation for providing the performance st… |
| 1.3.6.1.4.1.9.9.595 | ciscoGslbDnsMIB | 3 | 165 | The MIB defines objects for status and statistics information of DNS related operations of Global Server Load Balancer(GSLB). Th… |
| 1.3.6.1.4.1.9.9.597 | ciscoContentServicesMIB | 3 | 349 | Content Service is a capability to examine IP/TCP/UDP headers, payload and enable billing based on the content being provided. Ab… |
| 1.3.6.1.4.1.9.9.598 | ciscoLwappAAAMIB | 3 | 73 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC), that terminate the Light Weigh… |
| 1.3.6.1.4.1.9.9.599 | ciscoLwappDot11ClientMIB | 4 | 49 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.600 | ciscoGslbHealthMonMIB | 3 | 90 | The MIB defines objects related to global keepalive properties in GSLB devices. It contains the tables for keep alive configurat… |
| 1.3.6.1.4.1.9.9.601 | ciscoResilientEthernetProtocolMIB | 3 | 77 | This MIB module defines objects required for managing Resilient Ethernet Protocol (REP). Resilient Ethernet Protocol (REP) is a C… |
| 1.3.6.1.4.1.9.9.602 | ciscoPacketCaptureMIB | 3 | 103 | The MIB module for the management of packet capture feature. |
| 1.3.6.1.4.1.9.9.603 | ciscoThreatMitigationServiceMIB | 3 | 68 | This MIB provides management information about the Threat Mitigation Service(TMS) entity named 'Consumer'. TMS is part of Cisco's… |
| 1.3.6.1.4.1.9.9.604 | cdot1CfmMIB | 3 | 166 | Connectivity Fault Management module for managing IEEE 802.1ag |
| 1.3.6.1.4.1.9.9.606 | ciscoLwappMeshLinkTestMIB | 3 | 46 | ciscoLwappMeshLinkTestMIB MODULE-IDENTITY LAST-UPDATED "200702050000Z" ORGANIZATION "Cisco Systems Inc." CONTACT-INFO "Cisco Sy… |
| 1.3.6.1.4.1.9.9.607 | ciscoDot11HtPhyMIB | 3 | 71 | This MIB is intended to be implemented on Cisco's WLAN devices that provide the wired uplink to wireless clients through the high… |
| 1.3.6.1.4.1.9.9.610 | ciscoLwappRogueMIB | 3 | 78 | This MIB is intended to be implemented on all those devices operating as Central Controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.611 | ciscoLwappDot11ClientCCXTextualConventions | 0 | 0 | This module defines the textual conventions used throughout the Cisco enterprise MIBs designed for implementation on Central Cont… |
| 1.3.6.1.4.1.9.9.612 | ciscoLwappDot11MIB | 3 | 17 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.613 | ciscoEvcMIB | 3 | 156 | Metro Ethernet services can support a wide range of applications and subscriber needs easily, efficiently and cost-effectively. … |
| 1.3.6.1.4.1.9.9.614 | ciscoLwappDot11LdapMIB | 3 | 33 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.615 | ciscoLwappRrmMIB | 3 | 28 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.616 | ciscoLwappMeshMIB | 3 | 121 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight… |
| 1.3.6.1.4.1.9.9.617 | ciscoLwappMeshStatsMIB | 4 | 98 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight… |
| 1.3.6.1.4.1.9.9.618 | ciscoLwappSysMIB | 3 | 163 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.619 | ciscoLwappLocalAuthMIB | 3 | 53 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.620 | ciscoLwappMeshBatteryMIB | 3 | 34 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight… |
| 1.3.6.1.4.1.9.9.621 | ciscoH324DialControlMIB | 2 | 34 | This MIB module enhances the IETF Dial Control MIB (RFC2128) by providing H.324 call information over a telephony network. ITU-T R… |
| 1.3.6.1.4.1.9.9.622 | ciscoLwappDot11ClientTsMIB | 3 | 34 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.623 | ciscoLwappCdpMIB | 3 | 51 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight… |
| 1.3.6.1.4.1.9.9.624 | ciscoIpSlaTCMIB | 0 | 0 | This MIB contains textual conventions used by CISCO IPSLA MIBs. Acronyms: FEC: Forward Equivalence Class LPD: Label Path Discovery L… |
| 1.3.6.1.4.1.9.9.626 | ciscoDot11HtMacMIB | 3 | 40 | This MIB is intended to be implemented on Cisco's WLAN devices that provide the wired uplink to wireless clients through the high… |
| 1.3.6.1.4.1.9.9.627 | ciscoDot11RadarMIB | 3 | 25 | This MIB module is for IEEE 802.11a/h Root device, i.e. Access Point (AP) or Root Bridge. This MIB allows dynamic frequency selec… |
| 1.3.6.1.4.1.9.9.628 | ciscoServiceControlSubscribersMIB | 3 | 37 | This MIB provides global and specific information on subscribers managed by a service control entity, which is a network element … |
| 1.3.6.1.4.1.9.9.630 | ciscoTelnetServerMIB | 3 | 34 | MIB module for displaying and configuring Telnet related features in a device. Telnet is a program to log into another computer o… |
| 1.3.6.1.4.1.9.9.631 | ciscoServiceControlLinkMIB | 3 | 21 | This MIB module provides information about the status and configuration of links used by service control entities. The link on a … |
| 1.3.6.1.4.1.9.9.632 | ciscoSmeMIB | 3 | 54 | MIB module to manage Storage Media Encryption (SME) service. SME is an encryption service provided by an encryption node residing… |
| 1.3.6.1.4.1.9.9.633 | ciscoIpSlaAutoMIB | 3 | 57 | This module defines the MIB for IP SLA Automation. IP SLA Automation consists of the following: 1. Use of grouping - Group is an … |
| 1.3.6.1.4.1.9.9.634 | ciscoServiceControlTpStatsMIB | 3 | 39 | This MIB provides information and statistics on the traffic processor(s) of a service control entity, which is a network element … |
| 1.3.6.1.4.1.9.9.635 | ciscoIpSlaJitterMIB | 3 | 57 | This MIB module defines templates for IP SLA operations of UDP Jitter and ICMP Jitter. The UDP Jitter operation is designed to me… |
| 1.3.6.1.4.1.9.9.636 | ciscoIpSlaEchoMIB | 3 | 71 | This MIB module defines the templates for IP SLA operations of ICMP echo, UDP echo and TCP connect. The ICMP echo operation measu… |
| 1.3.6.1.4.1.9.9.637 | ciscoServiceControlRdrMIB | 3 | 56 | This MIB module defines objects describing statistics and configuration relating to the Raw Data Record Formatter running on a se… |
| 1.3.6.1.4.1.9.9.639 | ciscoOtnIfMIB | 3 | 137 | This MIB module defines the managed objects for physical layer characteristics of DWDM optical channel interfaces and performanc… |
| 1.3.6.1.4.1.9.9.640 | ciscoImageLicenseMgmtMIB | 3 | 31 | The MIB module for managing the running image level of a Cisco device. Cisco's licensing mechanism provides flexibility to run a … |
| 1.3.6.1.4.1.9.9.642 | ciscoBridgeDomainMIB | 3 | 24 | A bridge domain is one of the means by which it is possible to define a broadcast domain on a bridging device. It is an alternati… |
| 1.3.6.1.4.1.9.9.643 | ciscoTelepresenceMIB | 3 | 119 | The MIB module defines the managed objects for a Telepresence system. Telepresence refers to a set of technologies which allow a p… |
| 1.3.6.1.4.1.9.9.644 | ciscoTelepresenceCallMIB | 3 | 178 | The MIB module defines the managed objects for Telepresence calls. Telepresence refers to a set of technologies which allow a pers… |
| 1.3.6.1.4.1.9.9.645 | ciscoEtherExtMIB | 3 | 18 | The MIB module to describe generic objects for ethernet-like network interfaces. This MIB provides ethernet-like network interfac… |
| 1.3.6.1.4.1.9.9.646 | ciscoAonStatusMIB | 3 | 80 | This MIB module defines managed objects that facilitate the management of AON node. The information available through this MIB in… |
| 1.3.6.1.4.1.9.9.647 | ciscoGgsnExtMIB | 3 | 212 | This MIB module extends the CISCO-GGSN-MIB. This MIB module manages the Gateway GPRS Support Node (GGSN) devices. A GGSN device pr… |
| 1.3.6.1.4.1.9.9.648 | ciscoVirtualInterfaceMIB | 2 | 32 | The MIB module for creation and deletion of Virtual Interfaces and Virtual Interface Groups. In addition to this MIB, interface … |
| 1.3.6.1.4.1.9.9.650 | ciscoL4L7moduleRedundancyMIB | 3 | 71 | The L4-7 SLB devices are used for scaling websites, building web enabled applications, and migrating to web services. The followin… |
| 1.3.6.1.4.1.9.9.651 | ciscoCommonRolesExtMIB | 3 | 37 | A MIB Module for managing the roles that are common between access methods like Command Line Interface (CLI), SNMP and XML interf… |
| 1.3.6.1.4.1.9.9.652 | ciscoSwitchStatsMIB | 3 | 106 | The MIB module provides management information for configuration and monitoring of traffic statistics on Cisco's switching device… |
| 1.3.6.1.4.1.9.9.653 | ciscoAdmissionPolicyMIB | 3 | 36 | This MIB module defines managed objects that facilitate the management of policies upon host(s) admission to a network. The inform… |
| 1.3.6.1.4.1.9.9.654 | ciscoMabMIB | 3 | 20 | MIB module for monitoring and configuring MAC Authentication Bypass (MAB) feature in the system. MAC Auth Bypass feature provides… |
| 1.3.6.1.4.1.9.9.655 | ciscoDigitalMediaSystemsMIB | 3 | 195 | Acronyms and Definitions The following acronyms and terms are used in this document: DMS: Digital Media Systems DAM: Digital As… |
| 1.3.6.1.4.1.9.9.656 | ciscoAuthFrameworkMIB | 3 | 117 | MIB module for Authentication Framework in the system. Authentication Framework provides generic configurations for authenticatio… |
| 1.3.6.1.4.1.9.9.657 | ciscoSbcCallStatsMIB | 3 | 201 | The main purpose of this MIB is to define the statistics information for Session Border Controller application. The statistics ar… |
| 1.3.6.1.4.1.9.9.658 | ciscoSessBorderCtrlrEventMIB | 3 | 208 | The main purpose of this MIB is to define the SNMP notifications and alarms generated by Session Border Controller application an… |
| 1.3.6.1.4.1.9.9.660 | ciscoNportVirtualizationMIB | 3 | 19 | The MIB module for the management of N_port Virtualization or NPV within the framework of Cisco's N_port virtualization (NPV) Arc… |
| 1.3.6.1.4.1.9.9.661 | ciscoWan3gMIB | 3 | 378 | This MIB module provides network management support for Cisco cellular 3G WAN products. *** ABBREVIATIONS, ACRONYMS, AND SYMBOLS … |
| 1.3.6.1.4.1.9.9.662 | ciscoCbpTcMIB | 0 | 0 | This MIB module defines textual conventions used by the CISCO-CBP-BASE-CFG-MIB, CISCO-CBP-BASE-MON-MIB, and any MIB modules exten… |
| 1.3.6.1.4.1.9.9.663 | ciscoSwitchHardwareCapacityMIB | 3 | 141 | This MIB module defines the managed objects for hardware capacity of Cisco switching devices. The hardware capacity information c… |
| 1.3.6.1.4.1.9.9.664 | ciscoMmodalContactAppsMIB | 3 | 359 | The Cisco Unified Multi-Modal Contact Applications (MMCA) platform is a highly scalable, modular, extensible, open and secure pl… |
| 1.3.6.1.4.1.9.9.667 | ciscoServiceControllerMIB | 2 | 31 | This MIB module defines objects describing traffic controllers used by a service control entity. A service control entity is a ne… |
| 1.3.6.1.4.1.9.9.668 | ciscoP2PIfMIB | 3 | 16 | The Point to Point Interface MIB module. This MIB manages the generic objects for Serial link or SONET/SDH like point to point ne… |
| 1.3.6.1.4.1.9.9.669 | ciscoCdmaPdsnExtMIB | 3 | 178 | This MIB is an extension to the CISCO-CDMA-PDSN-MIB. A CDMA network supports wireless data communication through 3G CDMA radio acc… |
| 1.3.6.1.4.1.9.9.670 | ciscoReportIntervalTcMIB | 0 | 0 | CISCO-REPORT-INTERVAL-TC-MIB |
| 1.3.6.1.4.1.9.9.672 | ciscoMobilityTapMIB | 3 | 24 | This module manages Cisco's intercept feature for Mobility Gateway Products. This MIB is used along with CISCO-TAP2-MIB MIB to int… |
| 1.3.6.1.4.1.9.9.673 | ciscoFCoEMIB | 2 | 45 | This MIB module is for configuring and monitoring Fibre Channel over Ethernet (FCoE) related entities. This MIB defines the Virtu… |
| 1.3.6.1.4.1.9.9.679 | ciscoIeee8021CfmExtMIB | 3 | 55 | A MIB module for extending the IEEE8021-CFM-MIB and IEEE8021-CFM-V2-MIB to add objects which provide additional information about… |
| 1.3.6.1.4.1.9.9.680 | ciscoNhrpExtMIB | 3 | 36 | This MIB module is an extension of the NHRP MIB module as defined in RFC 2677. It defines notifications associated with critical … |
| 1.3.6.1.4.1.9.9.683 | ciscoEnergywiseMIB | 3 | 162 | The MIB is used to manage and optimize power usage in networks. Cisco EnergyWise is a specification of data, discovery and protoco… |
| 1.3.6.1.4.1.9.9.686 | ciscoLwappInterfaceMIB | 3 | 27 | ciscoLwappInterfaceMIB MODULE-IDENTITY LAST-UPDATED "200901090000Z" ORGANIZATION "Cisco Systems Inc." CONTACT-INFO "Cisco Syste… |
| 1.3.6.1.4.1.9.9.688 | ciscoFlowMonitorTcMIB | 0 | 0 | This MIB module defines textual conventions used by the MIB modules defining objects describing flow monitoring. GLOSSARY ========… |
| ... | ||||