1CTRON-IF-REMAP-2-MIB DEFINITIONS ::= BEGIN 2 3-- ctron-if-remap-2-mib.txt 4-- Revision: 02.00.02 5-- Part Number: 6-- Date: September 15, 1998 7 8-- Cabletron Systems, Inc. 9-- 35 Industrial Way, P.O. Box 5005 10-- Rochester, NH 03867-0505 11-- (603) 332-9400 12-- support@ctron.com 13 14-- This module provides authoritative definitions for Cabletron's 15-- enterprise-specific Interface Remap MIB. 16-- 17-- This module will be extended, as required. 18-- 19 20-- Cabletron Systems reserves the right to make changes in 21-- specification and other information contained in this document 22-- without prior notice. The reader should consult Cabletron Systems 23-- to determine whether any such changes have been made. 24-- 25-- In no event shall Cabletron Systems be liable for any incidental, 26-- indirect, special, or consequential damages whatsoever (including 27-- but not limited to lost profits) arising out of or related to this 28-- document or the information contained in it, even if Cabletron 29-- Systems has been advised of, known, or should have known, the 30-- possibility of such damages. 31-- 32-- Cabletron grants vendors, end-users, and other interested parties 33-- a non-exclusive license to use this Specification in connection 34-- with the management of Cabletron products. 35 36-- Copyright August 98 Cabletron Systems 37 38 IMPORTS 39 OBJECT-TYPE 40 FROM RFC-1212 41 ctIFRemap2 42 FROM CTRON-MIB-NAMES; 43 44 45 ctIFRemap2Config OBJECT IDENTIFIER ::= { ctIFRemap2 1 } 46 47 48-- The ctIFRemap2Config group is used to control ifremapping. Ifremapping 49-- provides the ability to map one port or one vlan directly to another port. 50-- This control is defined by creating a row in the ctIFRemap2Table 51-- specifying source slot, source port, destination slot, and destination 52-- port with ctIFRemap2Status set to a value of enable(1) or by creating 53-- a row in the ctIFRemap2VlanTable specifying source slot, source vlan, 54-- destination slot, destination port with ctIFRemap2VlanStatus set to a 55-- value of enable(1). 56-- 57-- When a source port is remapped to a destination port, the destination 58-- port will transmit out all packets received or transmitted on the 59-- source port. Counters on the destination port will increment for all 60-- packets transmitted be it by normal packet forwarding or due to 61-- ifremap. 62-- 63-- When a source vlan is remapped to a destination port, the destination 64-- port will transmit out all packets received on the source vlan. Counters 65-- on the destination port will increment for all packets transmitted be it 66-- by normal packet forwarding or due to ifremap. 67-- 68-- All tables in this MIB contain a slot instance. In the case of a 69-- stand-alone device the slot will always be 1. 70-- 71-- Any mention of a vlan in this text refers to a Virtual Local Area Network 72-- that is compliant to IEEE Draft P802.1Q/D11. 73 74 75-- 76-- The IFRemap Table 77-- 78 79ctIFRemap2Table OBJECT-TYPE 80 SYNTAX SEQUENCE OF CtIFRemap2Entry 81 ACCESS not-accessible 82 STATUS mandatory 83 DESCRIPTION 84 "This table provides the ability to remap all frames from one 85 port onto another port. A port is defined by 86ctIFRemap2PortIndex 87 from the ctIFRemap2PortTable below. Only ports listed in the 88 ctIFRemap2PortTable are available for remapping. 89 90 A given source port may only be mapped to only one destination 91 port. Once a port is reserved as part of a ctIFRemap2Table entry, 92 it may not be used in any other ctIFRemap2Table entries (ie. If 93 remapping port 1 to port 3, then neither port 1 or port 3 may be 94 used as a ctIFRemap2SourcePort or ctIFRemap2DestPort in another 95 ctIFRemap2Table entry). 96 97 Each row that exists in this table defines such a relationship. 98 By disabling a row in this table the remapping relationship no 99 longer exists. 100 101 Each entry will be referenced by slot. In the case of a 102 stand-alone device the slot will always be 1. 103 104 If a given relationship cannot be created the set will fail 105 with a BAD-VALUE error." 106 ::= { ctIFRemap2Config 1 } 107 108 109ctIFRemap2Entry OBJECT-TYPE 110 SYNTAX CtIFRemap2Entry 111 ACCESS not-accessible 112 STATUS mandatory 113 DESCRIPTION 114 "Describes a particular ifremap entry." 115 INDEX { ctIFRemap2SourceSlot, ctIFRemap2SourcePort, 116 ctIFRemap2DestSlot, ctIFRemap2DestPort } 117 ::= { ctIFRemap2Table 1 } 118 119 120CtIFRemap2Entry ::= 121 SEQUENCE { 122 ctIFRemap2SourceSlot 123 INTEGER, 124 ctIFRemap2SourcePort 125 INTEGER, 126 ctIFRemap2DestSlot 127 INTEGER, 128 ctIFRemap2DestPort 129 INTEGER, 130 ctIFRemap2Status 131 INTEGER, 132 ctIFRemap2PhysicalErrors 133 INTEGER, 134 ctIFRemap2EgressType 135 INTEGER 136 } 137 138 139ctIFRemap2SourceSlot OBJECT-TYPE 140 SYNTAX INTEGER 141 ACCESS read-only 142 STATUS mandatory 143 DESCRIPTION 144 "The slot combined with the ctIFRemap2SourcePort which will 145 have all packets redirected to the destination port as defined 146 by ctIFRemap2DestSlot and ctIFRemap2DestPort." 147 ::= { ctIFRemap2Entry 1 } 148 149 150ctIFRemap2SourcePort OBJECT-TYPE 151 SYNTAX INTEGER 152 ACCESS read-only 153 STATUS mandatory 154 DESCRIPTION 155 "The port combined with the ctIFRemap2SourceSlot which will 156 have all packets redirected to the destination port as defined 157 by ctIFRemap2DestSlot and ctIFRemap2DestPort." 158 ::= { ctIFRemap2Entry 2 } 159 160 161ctIFRemap2DestSlot OBJECT-TYPE 162 SYNTAX INTEGER 163 ACCESS read-only 164 STATUS mandatory 165 DESCRIPTION 166 "The slot combined with the ctIFRemap2DestPort which will 167 see all packets redirected from ctIFRemap2SourceSlot and 168 ctIFRemap2SourcePort." 169 ::= { ctIFRemap2Entry 3 } 170 171 172ctIFRemap2DestPort OBJECT-TYPE 173 SYNTAX INTEGER 174 ACCESS read-only 175 STATUS mandatory 176 DESCRIPTION 177 "The port combined with the ctIFRemap2DestSlot which will 178 see all packets redirected from ctIFRemap2SourceSlot and 179 ctIFRemap2SourcePort." 180 ::= { ctIFRemap2Entry 4 } 181 182 183ctIFRemap2Status OBJECT-TYPE 184 SYNTAX INTEGER { 185 enable(1), 186 disable(2) 187 } 188 ACCESS read-write 189 STATUS mandatory 190 DESCRIPTION 191 "Defines the status of the ifremap entry. Setting 192 ctIFRemap2Status to a value of enable(1) has the effect of 193 creating an entry in the table when it does not already exist. 194 Setting ctIFRemap2Status to a value of disable(2) disables the 195 entry and deletes the row from the table. Therefore this 196 table only contains entries that are active." 197 DEFVAL { enable } 198 ::= { ctIFRemap2Entry 5 } 199 200 201ctIFRemap2PhysicalErrors OBJECT-TYPE 202 SYNTAX INTEGER { 203 enable(1), 204 disable(2), 205 unsupported(3) 206 } 207 ACCESS read-write 208 STATUS mandatory 209 DESCRIPTION 210 "Enable or disable remapping of physical errors. This object 211 controls whether or not frames with physical errors should be 212 remapped out the destination port for this entry. By default, 213 this will be enabled when an entry is created. 214 215 NOTE: This action is always superseded by the value of 216 ctIFRemap2PhysErrsCapable for either the source or destination 217 port specified in this remap entry. If a port is not 218 physically capable of transmitting or receiving error frames, 219 then this object will return unsupported(3) and the value 220 cannot be changed." 221 DEFVAL { enable } 222 ::= { ctIFRemap2Entry 6 } 223 224 225ctIFRemap2EgressType OBJECT-TYPE 226 SYNTAX INTEGER { 227 normal(1), 228 alwaysTagged(2), 229 alwaysUntagged(3) 230 } 231 ACCESS read-write 232 STATUS mandatory 233 DESCRIPTION 234 "Defines how each packet will be tagged when sent out the 235 ctIFRemap2DestPort. Setting ctIFRemap2EgressType to normal(1) 236 will set packets to be sent out as they are seen by 237 ctIFRemap2SourcePort. Setting ctIFRemap2EgressType to 238 alwaysTagged(2) will set packets to always be sent out 239 ctIFRemap2DestSlot and ctIFRemap2DestPort with a tag. Setting 240 ctIFRemap2EgressType to alwaysUntagged(3) will set packets to always 241 be sent out ctIFRemap2DestSlot and ctIFRemap2DestPort without a tag. 242 If the module is not configured to support packet tagging (i.e. 802.1d 243 bridge mode) then setting this object to alwaysTagged(2) or 244 alwaysUntagged(3) will return a BAD-VALUE error." 245 DEFVAL { normal } 246 ::= { ctIFRemap2Entry 7 } 247 248-- 249-- The IFRemap Port Table 250-- 251 252ctIFRemap2PortTable OBJECT-TYPE 253 SYNTAX SEQUENCE OF CtIFRemap2PortEntry 254 ACCESS not-accessible 255 STATUS mandatory 256 DESCRIPTION 257 "This table holds all valid ports that are remappable or 258 able to accept a remapped packet." 259 ::= { ctIFRemap2Config 2 } 260 261 262ctIFRemap2PortEntry OBJECT-TYPE 263 SYNTAX CtIFRemap2PortEntry 264 ACCESS not-accessible 265 STATUS mandatory 266 DESCRIPTION 267 "Describes a particular supported remappable port." 268 INDEX { ctIFRemap2PortSlot, ctIFRemap2PortIndex } 269 ::= { ctIFRemap2PortTable 1 } 270 271 272CtIFRemap2PortEntry ::= 273 SEQUENCE { 274 ctIFRemap2PortSlot 275 INTEGER, 276 ctIFRemap2PortIndex 277 INTEGER, 278 ctIFRemap2PortReference 279 OBJECT IDENTIFIER, 280 ctIFRemap2PhysErrsCapable 281 INTEGER 282 } 283 284 285ctIFRemap2PortSlot OBJECT-TYPE 286 SYNTAX INTEGER 287 ACCESS read-only 288 STATUS mandatory 289 DESCRIPTION 290 "Defines the slot in which the remap capable module resides. 291 In the case of a stand-alone device the slot will always be 1." 292 ::= { ctIFRemap2PortEntry 1 } 293 294 295ctIFRemap2PortIndex OBJECT-TYPE 296 SYNTAX INTEGER 297 ACCESS read-only 298 STATUS mandatory 299 DESCRIPTION 300 "Defines an port that is remappable or is able to accept a 301 remapped packet. Ideally indices will start with 1 and will 302 be numbered continuously through the number of available remap 303 ports. However, this need not necessarily be the case. 304 Indices may be sparse and begin with any number if desired 305 for a particular implementation." 306 ::= { ctIFRemap2PortEntry 2 } 307 308 309ctIFRemap2PortReference OBJECT-TYPE 310 SYNTAX OBJECT IDENTIFIER 311 ACCESS read-only 312 STATUS mandatory 313 DESCRIPTION 314 "This object returns an OID referencing an object which 315 uniquely corresponds to this remap port. The only criteria 316 is that this OID is a leaf, and that it exists and is 317 accessible. For example, if remap functionality is running 318 on an 802.1d compliant bridge, remap port #1 could reference 319 dot1dBasePort.1. Alternatively you could reference a mib2 320 interface like ifIndex.1 or a Cabletron Secure Fast port. 321 Mixing these types (some refer to bridge ports, others refer 322 to SFS ports) is not advised, but not prohibited" 323 ::= { ctIFRemap2PortEntry 3 } 324 325 326ctIFRemap2PhysErrsCapable OBJECT-TYPE 327 SYNTAX INTEGER { 328 supported(1), 329 unsupported(2) 330 } 331 ACCESS read-only 332 STATUS mandatory 333 DESCRIPTION 334 "Indicate whether the port is incapable of remapping physical 335 errors. If the capability is supported, this object will 336 return supported(1). If the capability is unsupported, this 337 object will return unsupported(2)." 338 ::= { ctIFRemap2PortEntry 4 } 339 340 341-- 342-- The IFRemap Slot Table 343-- 344 345ctIFRemap2SlotTable OBJECT-TYPE 346 SYNTAX SEQUENCE OF CtIFRemap2SlotEntry 347 ACCESS not-accessible 348 STATUS mandatory 349 DESCRIPTION 350 "This table contains all information pertaining to the 351 abilities or limitations of a particular remap capable 352 module." 353 ::= { ctIFRemap2Config 3 } 354 355 356ctIFRemap2SlotEntry OBJECT-TYPE 357 SYNTAX CtIFRemap2SlotEntry 358 ACCESS not-accessible 359 STATUS mandatory 360 DESCRIPTION 361 "Describes a particular entry in the ctIFRemap2SlotTable. 362 Each entry is indexed by the physical slot in which the 363 module resides." 364 INDEX { ctIFRemap2SlotIndex } 365 ::= { ctIFRemap2SlotTable 1 } 366 367 368CtIFRemap2SlotEntry ::= 369 SEQUENCE { 370 ctIFRemap2SlotIndex 371 INTEGER, 372 ctIFRemap2SlotMaxRemaps 373 INTEGER, 374 ctIFRemap2SlotMaxRemoteDests 375 INTEGER 376 } 377 378 379ctIFRemap2SlotIndex OBJECT-TYPE 380 SYNTAX INTEGER 381 ACCESS read-only 382 STATUS mandatory 383 DESCRIPTION 384 "Defines the slot in which the remap capable module resides. 385In 386 the case of a stand-alone device the slot will always be 1." 387 ::= { ctIFRemap2SlotEntry 1 } 388 389 390ctIFRemap2SlotMaxRemaps OBJECT-TYPE 391 SYNTAX INTEGER 392 ACCESS read-only 393 STATUS mandatory 394 DESCRIPTION 395 "The maximum number of entries allowed to be sourced from the 396 module in this slot in the ctIFRemap2Table." 397 ::= { ctIFRemap2SlotEntry 2 } 398 399ctIFRemap2SlotMaxRemoteDests OBJECT-TYPE 400 SYNTAX INTEGER 401 ACCESS read-only 402 STATUS mandatory 403 DESCRIPTION 404 "The maximum number of remote destination ports per remote 405 module. For example, a value of 3 means that I can have no 406 more than 3 remap destination ports between this module, and 407 any other given module in the same chassis simultaneously. I 408 can have multiple source ports remapped to each of the three 409 remote destination ports. I can also remap to up to three 410 remote destination ports on each of the other modules in the 411 chassis simultaneously." 412 ::= { ctIFRemap2SlotEntry 3 } 413 414 415-- 416-- The IFRemap Vlan Table 417-- 418-- The ctIFRemap2VlanTable may only be implemented on a Cabletron Bridge 419-- which supports the use of IEEE Draft P802.1Q/D11 compliant vlans. 420-- 421-- The implementation of this table is OPTIONAL 422 423ctIFRemap2VlanTable OBJECT-TYPE 424 SYNTAX SEQUENCE OF CtIFRemap2VlanEntry 425 ACCESS not-accessible 426 STATUS mandatory 427 DESCRIPTION 428 "This table provides the ability to remap all frames from any 429 port on a particular vlan to a specific destination port. 430 Each row that exists in this table defines such a relationship. 431 By disabling a row in this table the remapping relationship no 432 longer exists. 433 434 Multiple vlans may be mapped to a given destination port 435 (ie. vlan 11 and vlan 35 may both remap to port 10). 436 437 A port is defined by ctIFRemap2PortIndex in the ctIFRemap2PortTable, 438 above. Only ports listed in the ctIFRemap2PortTable are available 439 for remapping. A vlan is defined by ctVlanVID in the 440 ctVlanConfigTable. Only vlans listed in the ctVlanConfigTable are 441 available for remapping. 442 443 Each entry will be referenced by slot. In the case of a 444 stand-alone device the slot will always be 1. 445 446 If a given relationship cannot be created the set will fail 447 with a BAD-VALUE error." 448 REFERENCE 449 "ctvlan-ext-mib .4.4.1.1" 450 ::= { ctIFRemap2Config 4 } 451 452 453ctIFRemap2VlanEntry OBJECT-TYPE 454 SYNTAX CtIFRemap2VlanEntry 455 ACCESS not-accessible 456 STATUS mandatory 457 DESCRIPTION 458 "Describes a particular ifremap Vlan entry." 459 INDEX { ctIFRemap2VlanSourceSlot, ctIFRemap2VlanSourceVlan, 460 ctIFRemap2VlanDestSlot, ctIFRemap2VlanDestPort } 461 ::= { ctIFRemap2VlanTable 1 } 462 463CtIFRemap2VlanEntry ::= 464 SEQUENCE { 465 ctIFRemap2VlanSourceSlot 466 INTEGER, 467 ctIFRemap2VlanSourceVlan 468 INTEGER, 469 ctIFRemap2VlanDestSlot 470 INTEGER, 471 ctIFRemap2VlanDestPort 472 INTEGER, 473 ctIFRemap2VlanStatus 474 INTEGER, 475 ctIFRemap2VlanEgressType 476 INTEGER 477 } 478 479ctIFRemap2VlanSourceSlot OBJECT-TYPE 480 SYNTAX INTEGER 481 ACCESS read-only 482 STATUS mandatory 483 DESCRIPTION 484 "The slot combined with the ctIFRemap2VlanSourceVlan which will 485 have all packets redirected to the destination port as defined 486 by ctIFRemap2VlanDestSlot and ctIFRemap2VlanDestPort." 487 ::= { ctIFRemap2VlanEntry 1 } 488 489 490ctIFRemap2VlanSourceVlan OBJECT-TYPE 491 SYNTAX INTEGER 492 ACCESS read-only 493 STATUS mandatory 494 DESCRIPTION 495 "The vlan combined with the ctIFRemap2VlanSourceSlot which will 496 have all packets redirected to the destination port as defined 497 by ctIFRemap2VlanDestSlot and ctIFRemap2VlanDestPort." 498 ::= { ctIFRemap2VlanEntry 2 } 499 500 501ctIFRemap2VlanDestSlot OBJECT-TYPE 502 SYNTAX INTEGER 503 ACCESS read-only 504 STATUS mandatory 505 DESCRIPTION 506 "The slot combined with the ctIFRemap2VlanDestPort which will 507 see all packets redirected from ctIFRemap2VlanSourceSlot and 508 ctIFRemap2VlanSourceVlan." 509 ::= { ctIFRemap2VlanEntry 3 } 510 511 512ctIFRemap2VlanDestPort OBJECT-TYPE 513 SYNTAX INTEGER 514 ACCESS read-only 515 STATUS mandatory 516 DESCRIPTION 517 "The port combined with the ctIFRemap2VlanDestSlot which will 518 see all packets redirected from ctIFRemap2VlanSourceSlot and 519 ctIFRemap2VlanSourceVlan." 520 ::= { ctIFRemap2VlanEntry 4 } 521 522 523ctIFRemap2VlanStatus OBJECT-TYPE 524 SYNTAX INTEGER { 525 enable(1), 526 disable(2) 527 } 528 ACCESS read-write 529 STATUS mandatory 530 DESCRIPTION 531 "Defines the status of the ifremap vlan entry. Setting 532 ctIFRemap2VlanStatus to a value of enable(1) has the effect of 533 creating an entry in the table when it does not already exist. 534 Setting ctIFRemap2VlanStatus to a value of disable(2) disables the 535 entry and deletes the row from the table. Therefore this 536 table only contains entries that are active. 537 538 If ctIFRemap2VlanSourceVlan is already being used by another 539 ctIfRemap2Vlan entry or ctifRemap2 Entry then a set to 540 ctIFRemap2VlanStatus of value enable(1) will return with a 541 BAD-VALUE error." 542 DEFVAL { enable } 543 ::= { ctIFRemap2VlanEntry 5 } 544 545 546ctIFRemap2VlanEgressType OBJECT-TYPE 547 SYNTAX INTEGER { 548 received(1), 549 alwaysTagged(2), 550 alwaysUntagged(3) 551 } 552 ACCESS read-write 553 STATUS mandatory 554 DESCRIPTION 555 "Defines how each packet will be tagged when sent out the 556 ctIFRemap2VlanDestPort. Setting ctIFRemap2VlanEgressType to 557 received(1) will set packets to be sent out ctIFRemap2VlanDestSlot 558 and ctIFRemap2VlanDestPort exactly as they are received by 559 ctIFRemap2VlanSourceVlan. Setting ctIFRemap2VlanEgressType to 560 alwaysTagged(2) will set packets to be sent out 561 ctIFRemap2VlanDestSlot and ctIFRemap2VlanDestPort with the 562 vlan tag associated with ctIFRemap2VlanSourceVlan. If this port 563 does not have a vlan tag associated with it then all packets will 564 be remapped without a tag. Setting ctIFRemap2VlanEgressType to 565 alwaysUntagged(3) will set packets to be sent out 566 ctIFRemap2VlanDestSlot and ctIFRemap2VlanDestPort without any 567 tag reguardless of ctIFRemap2VlanSourceVlan's tagging status." 568 DEFVAL { received } 569 ::= { ctIFRemap2VlanEntry 6 } 570 571END 572