1-- ******************************************************************* 2-- Description of managed objects for Ethernet access interfaces. 3-- 4-- January 2005, Gunnar Lovblom 5-- 6-- Copyright (c) 2005, 2007, 2009 by Cisco Systems Inc. 7-- All rights reserved. 8-- ****************************************************************** 9 10CISCO-ETHERNET-ACCESS-MIB DEFINITIONS ::= BEGIN 11 12IMPORTS 13 Integer32, 14 MODULE-IDENTITY, 15 OBJECT-TYPE 16 FROM SNMPv2-SMI 17 MODULE-COMPLIANCE, 18 OBJECT-GROUP 19 FROM SNMPv2-CONF 20 TEXTUAL-CONVENTION 21 FROM SNMPv2-TC 22 ifIndex 23 FROM IF-MIB 24 vtpVlanIndex, 25 managementDomainIndex 26 FROM CISCO-VTP-MIB 27 ciscoMgmt 28 FROM CISCO-SMI; 29 30 31ciscoEthernetAccessMIB MODULE-IDENTITY 32 LAST-UPDATED "200709140000Z" 33 ORGANIZATION "Cisco Systems, Inc." 34 CONTACT-INFO 35 "Cisco Systems 36 Customer Service 37 38 Postal: 170 W Tasman Drive 39 San Jose, CA 95134 40 41 Tel: +1 800 553-NETS 42 43 E-mail: cs-dsbu@cisco.com" 44 DESCRIPTION 45 "The tables defined by this MIB module contain a collection 46 of managed objects that are general in nature and apply to 47 an edge device in an organizations network, e.g. a Metro 48 Ethernet network. An edge device, is a customer located 49 equipment, this is the first device which will connect the 50 Service Provider's network and map subscriber traffic into 51 the next layer. The access media could be either CAT5 or 52 fiber. The access device (edge device) can be designed for 53 DSL, Ethernet or other technologies, however, this MIB is 54 designed for Ethernet. 55 56 Terminology: 57 UNI - User to Network Interface 58 NNI - Network to Network Interface. 59 ENI - Enhanced Network Interface. Enhanced UNI port. 60 module/device 61 - In an environment (specifically, in an SNMP context) 62 consisting of a single chassis which can contain 63 multiple cards, the term 'module' refers to a card 64 and the term 'device' refers to the whole chassis. 65 In an environment where multiple chassis are 'stacked' 66 together, the term 'module' refers to a chassis and 67 the term 'device' refers to the whole stack. 68 In an environment containing only a single chassis 69 without removable cards, the terms 'device' and 70 'module' both refer to the chassis and its contents." 71 REVISION "200709140000Z" 72 DESCRIPTION 73 "Added ENI as a new port type to the ceaPortType and 74 ceaPortCapability objects." 75 REVISION "200501180000Z" 76 DESCRIPTION 77 "Initial version of this MIB module." 78 ::= { ciscoMgmt 466 } 79 80 81-- MIB Objects Definitions 82 83ciscoEthernetAccessMIBObjects OBJECT IDENTIFIER 84 ::= { ciscoEthernetAccessMIB 1 } 85 86ciscoEthernetAccessMIBConform OBJECT IDENTIFIER 87 ::= { ciscoEthernetAccessMIB 2 } 88 89ceaGlobals OBJECT IDENTIFIER 90 ::= { ciscoEthernetAccessMIBObjects 1 } 91 92ceaConfig OBJECT IDENTIFIER 93 ::= { ciscoEthernetAccessMIBObjects 2 } 94 95 96-- Textual Conventions 97 98CeaVlanUNIType ::= TEXTUAL-CONVENTION 99 STATUS current 100 DESCRIPTION 101 "The type of a VLAN. 102 103 'other' -- this VLAN is not a UNI VLAN 104 105 'isolated' -- this VLAN is a UNI isolated VLAN. 106 UNI ports that are members of a UNI isolated VLAN can 107 not communicate with other ports in that VLAN, however 108 NNI ports can communicate with UNI and NNI ports in the 109 same VLAN. 110 111 'community' -- this VLAN is a UNI community VLAN. 112 UNI and NNI ports that are members of the community 113 VLAN can communicate with all other UNI and NNI ports 114 in the same VLAN." 115 SYNTAX INTEGER { 116 other(1), 117 isolated(2), 118 community(3) 119 } 120 121ceaMaxNNIPorts OBJECT-TYPE 122 SYNTAX Integer32 (0..512) 123 MAX-ACCESS read-only 124 STATUS current 125 DESCRIPTION 126 "The max number of interfaces per module for which the 127 ceaPortType can have the value 'nni'. 128 The value of 0 is returned by this object if there is no 129 limitation to the number of NNI ports." 130 ::= { ceaGlobals 1 } 131 132ceaMaxUNIVlanCommunityPorts OBJECT-TYPE 133 SYNTAX Integer32 (0..512) 134 MAX-ACCESS read-only 135 STATUS current 136 DESCRIPTION 137 "The maximum number of ports on this device for which 138 the ceaUNIVlanType object can have the value 'community'. 139 The value of 0 is returned by this object if there is no 140 limitation to the number of UNI VLAN Communities." 141 ::= { ceaGlobals 2 } 142-- ceaPortTable 143 144ceaPortTable OBJECT-TYPE 145 SYNTAX SEQUENCE OF CeaPortEntry 146 MAX-ACCESS not-accessible 147 STATUS current 148 DESCRIPTION 149 "This table contains Ethernet port specific information. 150 There exists an entry for each Ethernet port with an ifType 151 of 6 (ethernetCsmacd) in this table. 152 Note that the maximum number of NNI ports that can be 153 configured per module on this device is given by the value 154 of ceaMaxNNIPorts." 155 ::= { ceaConfig 1 } 156 157ceaPortEntry OBJECT-TYPE 158 SYNTAX CeaPortEntry 159 MAX-ACCESS not-accessible 160 STATUS current 161 DESCRIPTION 162 "A set of Ethernet port specific parameters for a device 163 which can be configured with a mixture of port types 164 defined by the ceaPortType object." 165 INDEX { ifIndex } 166 ::= { ceaPortTable 1 } 167 168CeaPortEntry ::= SEQUENCE { 169 ceaPortType INTEGER, 170 ceaPortCapability BITS 171} 172 173ceaPortType OBJECT-TYPE 174 SYNTAX INTEGER { 175 unspecified(1), 176 uni(2), 177 nni(3), 178 eni(4) 179 } 180 MAX-ACCESS read-write 181 STATUS current 182 DESCRIPTION 183 "The current configuration of the port. Only ports that are 184 supported by the ceaPortCapability object can be set. 185 Unspecified port type is any other port type than NNI, 186 UNI or ENI. 187 unspecified = Not UNI, or NNI, or ENI 188 uni = User to Network Interface port type. 189 nni = Network to Network Interface port type. 190 eni = Enhanced UNI port type." 191 ::= { ceaPortEntry 1 } 192 193ceaPortCapability OBJECT-TYPE 194 SYNTAX BITS { 195 nni(0), 196 uni(1), 197 eni(2) 198 } 199 MAX-ACCESS read-only 200 STATUS current 201 DESCRIPTION 202 "Types supported by the Ethernet port. If a port doesn't 203 support the port type the ceaPortType will not allow 204 set of the unsupported type. 205 nni = Port supports NNI. 206 uni = Port supports UNI. 207 eni = Port supports ENI." 208 ::= { ceaPortEntry 2 } 209 210 211-- ceaUNIVlanTable 212 213ceaUNIVlanTable OBJECT-TYPE 214 SYNTAX SEQUENCE OF CeaUNIVlanEntry 215 MAX-ACCESS not-accessible 216 STATUS current 217 DESCRIPTION 218 "This table contains UNI VLAN information for all the VLANs 219 which currently exist on this device. 220 The number of UNI ports that can belong to a VLAN type 221 'community' is limited by the ceaMaxUNIVlanCommunityPorts 222 object." 223 ::= { ceaConfig 2 } 224 225ceaUNIVlanEntry OBJECT-TYPE 226 SYNTAX CeaUNIVlanEntry 227 MAX-ACCESS not-accessible 228 STATUS current 229 DESCRIPTION 230 "There is an entry in this table for each VLAN that 231 exist on this device." 232 INDEX { 233 managementDomainIndex, 234 vtpVlanIndex 235 } 236 ::= { ceaUNIVlanTable 1 } 237 238CeaUNIVlanEntry ::= SEQUENCE { 239 ceaUNIVlanType CeaVlanUNIType 240} 241 242ceaUNIVlanType OBJECT-TYPE 243 SYNTAX CeaVlanUNIType 244 MAX-ACCESS read-write 245 STATUS current 246 DESCRIPTION 247 "Indicates the VLAN type defined for the UNI VLAN." 248 ::= { ceaUNIVlanEntry 1 } 249 250 251-- MIB Conformance Statements 252 253cEthernetAccessMIBCompliances OBJECT IDENTIFIER 254 ::= { ciscoEthernetAccessMIBConform 1 } 255 256cEthernetAccessMIBGroups OBJECT IDENTIFIER 257 ::= { ciscoEthernetAccessMIBConform 2 } 258 259 260-- Compliance 261 262cEthernetAccessMIBCompliance MODULE-COMPLIANCE 263 STATUS current 264 DESCRIPTION 265 "The compliance statement for entities that implement the 266 CISCO-ETHERNET-ACCESS-MIB. Implementation of this MIB is 267 mandatory for any platform that have Ethernet UNI/NNI 268 capable interfaces." 269 MODULE -- this module 270 MANDATORY-GROUPS { 271 ceaPortGroup, 272 ceaVlanGroup 273 } 274 275 OBJECT ceaUNIVlanType 276 MIN-ACCESS read-only 277 DESCRIPTION 278 "Write access is not required." 279 280 OBJECT ceaPortType 281 MIN-ACCESS read-only 282 DESCRIPTION 283 "Write access is not required." 284 ::= { cEthernetAccessMIBCompliances 1 } 285 286-- Units of Conformance 287 288ceaPortGroup OBJECT-GROUP 289 OBJECTS { 290 ceaMaxNNIPorts, 291 ceaPortType, 292 ceaPortCapability 293 } 294 STATUS current 295 DESCRIPTION 296 "A collection of managed objects defining port types." 297 ::= { cEthernetAccessMIBGroups 1 } 298 299ceaVlanGroup OBJECT-GROUP 300 OBJECTS { 301 ceaMaxUNIVlanCommunityPorts, 302 ceaUNIVlanType 303 } 304 STATUS current 305 DESCRIPTION 306 "A collection of managed objects defining VLAN types." 307 ::= { cEthernetAccessMIBGroups 2 } 308 309END 310 311 312 313