1-- ******************************************************************* 2-- CISCO-LWAPP-MOBILITY-MIB.my 3-- June 2006, Bharat Biswal 4-- 5-- Copyright (c) 2005-2006, 2010-2011 by Cisco Systems Inc. 6-- All rights reserved. 7-- ******************************************************************* 8 9CISCO-LWAPP-MOBILITY-MIB DEFINITIONS ::= BEGIN 10 11IMPORTS 12 MODULE-IDENTITY, 13 OBJECT-TYPE, 14 NOTIFICATION-TYPE, 15 Unsigned32, 16 Integer32 17 FROM SNMPv2-SMI 18 MODULE-COMPLIANCE, 19 OBJECT-GROUP, 20 NOTIFICATION-GROUP 21 FROM SNMPv2-CONF 22 DisplayString, 23 TruthValue, 24 RowStatus, 25 MacAddress 26 FROM SNMPv2-TC 27 InetAddressType, 28 InetAddress 29 FROM INET-ADDRESS-MIB 30 SnmpAdminString 31 FROM SNMP-FRAMEWORK-MIB 32 ciscoMgmt 33 FROM CISCO-SMI; 34 35 36-- ******************************************************************** 37-- * MODULE IDENTITY 38-- ******************************************************************** 39 40ciscoLwappMobilityMIB MODULE-IDENTITY 41 LAST-UPDATED "201008230000Z" 42 ORGANIZATION "Cisco Systems Inc." 43 CONTACT-INFO 44 "Cisco Systems, 45 Customer Service 46 47 Postal: 170 West Tasman Drive 48 San Jose, CA 95134 49 USA 50 51 Tel: +1 800 553-NETS 52 53 Email: cs-snmp@cisco.com" 54 DESCRIPTION 55 "This MIB is intended to be implemented on all those 56 devices operating as Central Controllers (CC) that 57 58 terminate the Light Weight Access Point Protocol 59 60 tunnel from Light-weight LWAPP Access Points. 61 62 63 This MIB provides configuration and status information 64 65 about the 802.11 WLAN mobility. 66 67 68 The relationship between CC and the LWAPP APs 69 70 can be depicted as follows: 71 72 73 +......+ +......+ +......+ +......+ 74 75 + + + + + + + + 76 77 + CC + + CC + + CC + + CC + 78 79 + + + + + + + + 80 81 +......+ +......+ +......+ +......+ 82 83 .. . . . 84 85 .. . . . 86 87 . . . . . 88 89 . . . . . 90 91 . . . . . 92 93 . . . . . 94 95 +......+ +......+ +......+ +......+ 96 +......+ 97 98 + + + + + + + + + 99 + 100 101 + AP + + AP + + AP + + AP + + AP 102 + 103 104 + + + + + + + + + 105 + 106 107 +......+ +......+ +......+ +......+ 108 +......+ 109 110 . . . . 111 112 . . . . . 113 114 . . . . . 115 116 . . . . . 117 118 . . . . . 119 120 +......+ +......+ +......+ +......+ 121 +......+ 122 123 + + + + + + + + + 124 + 125 126 + MN + + MN + + MN + + MN + + MN 127 + 128 129 + + + + + + + + + 130 + 131 132 +......+ +......+ +......+ +......+ 133 +......+ 134 135 136 137 The LWAPP tunnel exists between the controller and 138 139 the APs. The MNs communicate with the APs through 140 141 the protocol defined by the 802.11 standard. 142 143 144 LWAPP APs, upon bootup, discover and join one of the 145 146 controllers and the controller pushes the configuration, 147 148 that includes the WLAN parameters, to the LWAPP APs. 149 150 The APs then encapsulate all the 802.11 frames from 151 152 wireless clients inside LWAPP frames and forward 153 154 the LWAPP frames to the controller. 155 156 157 GLOSSARY 158 159 160 Access Point ( AP ) 161 162 163 An entity that contains an 802.11 medium access 164 165 control ( MAC ) and physical layer ( PHY ) interface 166 167 and provides access to the distribution services via 168 169 the wireless medium for associated clients. 170 171 172 LWAPP APs encapsulate all the 802.11 frames in 173 174 LWAPP frames and sends it to the controller to which 175 176 it is logically connected. 177 178 179 Basic Service Set Identifier (BSSID) 180 181 182 The identifier for the service set comprising of 183 184 all the 802.11 stations under the control of 185 186 one coordinating Access Point. This identifier 187 188 happens to be the MAC address of the dot11 radio 189 190 interface of the Access Point. The wireless 191 192 clients that associate with the Access Point 193 194 get the wired uplink through this particular 195 196 dot11 interface. 197 198 199 Central Controller ( CC ) 200 201 202 The central entity that terminates the LWAPP protocol 203 204 tunnel from the LWAPP APs. Throughout this MIB, 205 206 this entity also referred to as 'controller'. 207 208 209 Light Weight Access Point Protocol ( LWAPP ) 210 211 212 This is a generic protocol that defines the 213 214 communication between the Access Points and the 215 216 Central Controller. 217 218 219 Mobile Node ( MN ) 220 221 222 A roaming 802.11 wireless device in a wireless 223 224 network associated with an access point. 225 226 227 Mobility 228 229 230 Concept by which a Mobile Node can roam from one 231 232 Access Point to another Access Point, across multiple 233 234 Central Controllers, without need for repeated 235 236 authentication. 237 238 239 Mobility Group 240 241 242 A set of Central Controllers which exchange Mobile 243 244 Node's authentication information, so that the Mobile 245 246 Node upon roaming need not re-authenticate. 247 248 249 Mobility Anchor 250 251 252 When a Central Controller in the Mobility Group is 253 254 designated as Mobility Anchor, then all the Mobile 255 256 Node's traffic is tunnelled to it by other 257 258 Controllers in the Mobility Group. 259 260 261 Guest Tunneling (GT) 262 263 264 The concept of designating a Central Controller in 265 266 the Mobility Group as Mobility Anchor, so that all 267 268 the Mobile Node's traffic is tunnelled to it by other 269 270 Controllers in the Mobility Group. 271 272 273 Station Management (SMT) 274 275 276 This term refers to the internal management of the 277 278 802.11 protocol operations by the AP to work 279 280 cooperatively with the other APs and 802.11 281 282 devices in the network. 283 284 285 Ethernet over Internet Protocol (EoIP) 286 287 288 Ethernet over IP (EoIP) is a protocol that creates 289 290 an Ethernet tunnel between two routers on top of an 291 292 IP connection. The EoIP interface appears as an 293 294 Ethernet interface. 295 296 297 Reverse path filtering (RPF) 298 299 300 Reverse path filtering (RPF) is a feature provided 301 302 by most modern Internet Protocol routers, which may 303 304 be used to reduce the risk of customers attacking 305 306 other internet hosts. One of the problems network 307 308 service providers face today is hackers generating 309 310 packets with fake source IP addresses, a technique 311 312 known as spoofing. This is often done in order to 313 314 initiate a denial-of-service attack against another 315 316 internet host or network. 317 318 Since the source IP addresses of the incoming packets 319 320 change, often randomly, and for every packet, the 321 322 target of such an attack can't easily filter out the 323 324 attacking packets. However, the source of the attack, 325 326 i.e. the network service provider of the attacking 327 328 host, has a simple way to stop such packets from ever 329 330 leaving its network. A router always knows which 331 332 networks are reachable via any of its interfaces. 333 334 By checking the source IP address of all packets 335 336 coming in via an interface against the networks known 337 338 to be behind that interface, the router can simply 339 340 drop packets that aren't supposed to come from there. 341 342 Hence, reverse path filtering filters packets 343 344 according to the 'reverse path' to their source 345 346 address. If the path back to the source address 347 348 does not match the path the packet is coming from, 349 350 it is dropped. 351 352 353 354 355 REFERENCE 356 357 358 [1] Part 11 Wireless LAN Medium Access Control ( MAC ) 359 360 and Physical Layer ( PHY ) Specifications. 361 362 363 [2] Draft-obara-capwap-lwapp-00.txt, IETF Light 364 365 Weight Access Point Protocol." 366 REVISION "201008230000Z" 367 DESCRIPTION 368 "Added ciscoLwappMobilityMIBComplianceRev01 that deprecates 369 ciscoLwappMobilityMIBCompliance. 370 Added cLMobilityGroupRev01ConfigGroup object group." 371 REVISION "200607190000Z" 372 DESCRIPTION 373 "Initial version of this MIB module." 374 ::= { ciscoMgmt 576 } 375 376 377ciscoLwappMobilityMIBNotifs OBJECT IDENTIFIER 378 ::= { ciscoLwappMobilityMIB 0 } 379 380ciscoLwappMobilityMIBObjects OBJECT IDENTIFIER 381 ::= { ciscoLwappMobilityMIB 1 } 382 383ciscoLwappMobilityMIBConform OBJECT IDENTIFIER 384 ::= { ciscoLwappMobilityMIB 2 } 385 386-- ******************************************************************* 387-- Per WLAN, anchors table 388-- ******************************************************************* 389 390cLMobilityAnchorTable OBJECT-TYPE 391 SYNTAX SEQUENCE OF CLMobilityAnchorEntry 392 MAX-ACCESS not-accessible 393 STATUS current 394 DESCRIPTION 395 "This table represents the information about the 396 802.11 LWAPP Mobility Anchors on individual WLANs. 397 398 399 +...............+ 400 + + 401 + ROUTER + 402 + 10.16.1.1 + 403 +...............+ 404 .. 405 . . 406 . . 407 . . 408 . . 409 . . 410 10.16.109.112 10.16.105.39 411 +......+ <<-------->> +......+ 412 + + [3]CC2 tunnels + + 413 + CC1 + MN1's traffic + CC2 + 414 + + to Anchor CC1 + + 415 +......+ using EoIP +......+ 416 . . 417 . Anchor Foreign . 418 . . 419 +......+ +......+ 420 + + + + 421 + AP1 + + AP2 + 422 + + + + 423 +......+ +......+ 424 'typhoon' . ^ 'typhoon' 425 . | 426 . [2] associates | 427 . with AP2/CC2 | 428 . | 429 +......+ [1] +......+ 430 + + moves to region + + 431 + MN1 + ---------->>> + MN1 + 432 + + serviced by AP2 + + 433 +......+ +......+ 434 10.16.109.199 10.16.109.199 435 436 In the above diagram, Central Controllers CC1 and CC2 have 437 been configure in a Mobility Group. 438 439 Currently the Mobile Node 'MN1' obtains its IP from the 440 Central Controller 'CC1' with which it first associates 441 via WLAN 'typhoon' through Access Point 'AP1'. 'CC1' 442 obtains DHCP address, say 10.16.109.199 for client 'MN1'. 443 Now the client 'MN1' is identified by 10.16.109.199 for 444 furthure communication with the network and the 445 communication happens via 'CC1'. 446 447 Since, 'CC1' and 'CC2' are in same mobility group, 'CC1' 448 sends the authentication block of 'MN1' to 'CC2'. 449 450 451 Central Controller 'CC2' has an associated Access Point 452 'AP2' which beams WLAN 'typhoon' and uses 10.16.105.0 / 453 255.255.255.0 subnet instead. 454 455 Next, the Mobile Node 'MN1' moves out of range of 'AP1' 456 and gets in to proximity with 'AP2' and continues to use 457 WLAN 'typhoon'. 'CC2' locally authenticates 'MN1' against 458 authentication block shared from 'CC1'. 'CC2' forwards all 459 traffic from 'MN1' to router. This is called WLAN mobility. 460 461 But hold on, 'CC2' uses 10.16.105.0 / 255.255.255.0 subnet 462 for WLAN 'typhoon'. So we have two problems here : 463 464 a> Traffic of 10.16.109.0 / 255.255.255.0 subnet has to be 465 accessible from 10.16.105.0 / 255.255.255.0 subnet. 466 467 b> Unneccessary overloading of 10.16.105.0 / 255.255.255.0 468 subnet by traffic from 10.16.109.0 / 255.255.255.0 subnet. 469 470 How do we address these issues ?? 471 472 If an EoIP tunnel can be established between 'CC1' and 'CC2' 473 and 'CC1' sends all traffic bound to 'MN1', 10.16.109.199, 474 on this tunnel to 'CC2', which in turn forwards it to 'MN1', 475 then, above two subnet-problems are resolved. This is called 476 Mobility Anchoring. 'CC1' is the Mobility Anchor and 'CC2' is 477 the 'Foreign' for WLAN 'typhoon'. 478 479 As per the configuration, user creates a MobilityAnchor entry 480 in 'CC2' for WLAN 'typhoon' with IP address as 'CC1', i.e. 481 10.16.109.112. So, when 'MN1' connects to WLAN 'typhoon' via 482 'AP2', then 'CC2' establishes EoIP tunnel with 10.16.109.112 483 and forwards the packets to 'MN1'. 484 485 Given the above example, the cLMobilityAnchorEntry on 'CC2' 486 looks like : 487 488 ------------------------------------------------------------------ 489 | MIB - ATTRIBUTES | ROW#1 | ROW#2 | 490 ------------------------------------------------------------------ 491 | cLMobilityAnchorWlanSsid | typhoon | | 492 ------------------------------------------------------------------ 493 | cLMobilityAnchorSwitchIPAddress | 10.16.109.112 | | 494 ------------------------------------------------------------------ 495 | cLMobilityAnchorStatus | up(4) | | 496 ------------------------------------------------------------------ 497 | cLMobilityAnchorRowStatus | active(1) | | 498 ------------------------------------------------------------------ 499 500 This feature has advantages for both security and load 501 balancing. It can be used to restrict a WLAN to a single 502 subnet, regardless of the MN's entry point into the network. 503 A 'public' or guest WLAN can thus be accessed throughout an 504 enterprise, but still is restricted to a specific subnet. 505 It can also be used to provide some geographic load balancing, 506 since the WLANs can represent a particular section of a 507 building (ie., engineering, marketing). Those groups can be 508 'anchored' on a particular subnet/switch rather than on the 509 CC of first occurrence (ie., the switch controlling the APs 510 by the front door)." 511 ::= { ciscoLwappMobilityMIBObjects 1 } 512 513cLMobilityAnchorEntry OBJECT-TYPE 514 SYNTAX CLMobilityAnchorEntry 515 MAX-ACCESS not-accessible 516 STATUS current 517 DESCRIPTION 518 "Each entry in this table provides information about 519 one 802.11 LWAPP Mobility Anchor configured on a WLAN 520 on this controller." 521 INDEX { 522 cLMobilityAnchorWlanSsid, 523 cLMobilityAnchorSwitchAddressType, 524 cLMobilityAnchorSwitchAddress 525 } 526 ::= { cLMobilityAnchorTable 1 } 527 528CLMobilityAnchorEntry ::= SEQUENCE { 529 cLMobilityAnchorWlanSsid DisplayString, 530 cLMobilityAnchorSwitchAddressType InetAddressType, 531 cLMobilityAnchorSwitchAddress InetAddress, 532 cLMobilityAnchorStatus BITS, 533 cLMobilityAnchorRowStatus RowStatus 534} 535 536cLMobilityAnchorWlanSsid OBJECT-TYPE 537 SYNTAX DisplayString (SIZE (1..32)) 538 MAX-ACCESS not-accessible 539 STATUS current 540 DESCRIPTION 541 "Local wlan-ssid to connect to Guest/Anchor switch" 542 ::= { cLMobilityAnchorEntry 1 } 543 544cLMobilityAnchorSwitchAddressType OBJECT-TYPE 545 SYNTAX InetAddressType 546 MAX-ACCESS not-accessible 547 STATUS current 548 DESCRIPTION 549 "Guest/Anchor switch Address type." 550 ::= { cLMobilityAnchorEntry 2 } 551 552cLMobilityAnchorSwitchAddress OBJECT-TYPE 553 SYNTAX InetAddress 554 MAX-ACCESS not-accessible 555 STATUS current 556 DESCRIPTION 557 "Guest/Anchor switch Address. 558 The IP Address is limited to IPv4 and IPv6." 559 ::= { cLMobilityAnchorEntry 3 } 560 561cLMobilityAnchorStatus OBJECT-TYPE 562 SYNTAX BITS { 563 controlpath(0), 564 datapath(1) 565 } 566 MAX-ACCESS read-only 567 STATUS current 568 DESCRIPTION 569 "Operational and Connectivity status of the 570 Mobility Anchor. 571 572 controlpath: 573 When bit is '0', this means successive 574 ICMP pings to the anchor have failed. 575 When is '1', this means anchor is 576 reachable and responding to ICMP pings. 577 578 datapath: 579 When bit is '0', this means successive 580 EoIP pings to the anchor have failed. 581 When bit is '1', this means anchor is 582 reachable and responding to EoIP pings." 583 ::= { cLMobilityAnchorEntry 4 } 584 585cLMobilityAnchorRowStatus OBJECT-TYPE 586 SYNTAX RowStatus 587 MAX-ACCESS read-create 588 STATUS current 589 DESCRIPTION 590 "Row Status" 591 ::= { cLMobilityAnchorEntry 5 } 592 593 594-- ******************************************************************** 595-- * Global Dot11 Mobility Anchor Configuration 596-- ******************************************************************** 597 598cLMobilityAnchorGlobalDot11Config OBJECT IDENTIFIER 599 ::= { ciscoLwappMobilityMIBObjects 2 } 600 601 602cLMobilityAnchorGroupKeepAliveNumber OBJECT-TYPE 603 SYNTAX Integer32 (3..20) 604 MAX-ACCESS read-write 605 STATUS current 606 DESCRIPTION 607 "This parameter determines how many successive 608 ping attempts to the anchor should fail before 609 the anchor is declared DOWN." 610 DEFVAL { 3 } 611 ::= { cLMobilityAnchorGlobalDot11Config 1 } 612 613cLMobilityAnchorGroupKeepAliveInterval OBJECT-TYPE 614 SYNTAX Integer32 (1..30) 615 MAX-ACCESS read-write 616 STATUS current 617 DESCRIPTION 618 "This parameter determines the time interval 619 (in seconds) between two consecutive ping attempts 620 to an anchor." 621 DEFVAL { 10 } 622 ::= { cLMobilityAnchorGlobalDot11Config 2 } 623 624cLMobilityAnchorSmtStatus OBJECT-TYPE 625 SYNTAX TruthValue 626 MAX-ACCESS read-write 627 STATUS current 628 DESCRIPTION 629 "This object allows user to enable or disable 630 Symmetric mobility tunneling for the controller. 631 632 The controller provides inter-subnet mobility 633 for clients roaming from one AP to another within 634 a Wireless LAN. This mobility is asymmetric in 635 nature where the client traffic to the wired 636 network is routed out directly via the 'foreign' 637 controller. See the diagram above. This mechanism 638 breaks when an upstream router has RPF enabled. 639 In this case the client traffic will be dropped 640 at the router because the RPF check ensures that 641 the path back to the source address matches the 642 path the packet is coming from. 643 644 This attribute is aimed at addressing this issue. 645 646 It will allow enabling 'Symmetric Mobility 647 Tunneling' or 'Bi-directional Tunneling' 648 for mobile clients such that all the client 649 traffic is sent to the 'anchor' controller and 650 go successfully through RPF check. 651 652 When set to 'true', Symmetric Mobility Tunneling 653 will be enabled on the Controller on next reset. 654 655 When set to 'false', Symmetric Mobility Tunneling 656 will be disabled on the Controller on next reset. 657 658 After setting this attribute to the desired value, 659 user should reset the Controller for the change to 660 take effect." 661 ::= { cLMobilityAnchorGlobalDot11Config 3 } 662 663cLMobilityAnchorCurrentSmt OBJECT-TYPE 664 SYNTAX TruthValue 665 MAX-ACCESS read-only 666 STATUS current 667 DESCRIPTION 668 "This object represents the current state of 669 Symmetric mobility tunneling for the controller. 670 671 When value is 'true', this means Symmetric Mobility 672 Tunneling is currently enabled on the Controller. 673 674 When value is 'false', this means Symmetric Mobility 675 Tunneling is currently disabled on the Controller." 676 ::= { cLMobilityAnchorGlobalDot11Config 4 } 677-- ******************************************************************** 678-- * Global Mobility Group Configuration 679-- ******************************************************************** 680 681cLMobilityMulticastGroupConfig OBJECT IDENTIFIER 682 ::= { ciscoLwappMobilityMIBObjects 4 } 683 684 685cLMobilityMulticastMessagingEnable OBJECT-TYPE 686 SYNTAX TruthValue 687 MAX-ACCESS read-write 688 STATUS current 689 DESCRIPTION 690 "This object specifies whether the mobility multicast 691 messaging feature is enabled or disabled on the controller. 692 693 A value of 'true' enables the multicast messaging among the 694 mobility group memebers and 'false' disables the multicast 695 messaging and uses unicast messaging." 696 ::= { cLMobilityMulticastGroupConfig 1 } 697 698cLMobilityMulticastGroupTable OBJECT-TYPE 699 SYNTAX SEQUENCE OF CLMobilityMulticastGroupEntry 700 MAX-ACCESS not-accessible 701 STATUS current 702 DESCRIPTION 703 "This table is used to configure multicast group 704 IP address per mobility group. Entries are added to the table 705 when configuring multicast group IP address per mobility group." 706 ::= { cLMobilityMulticastGroupConfig 2 } 707 708cLMobilityMulticastGroupEntry OBJECT-TYPE 709 SYNTAX CLMobilityMulticastGroupEntry 710 MAX-ACCESS not-accessible 711 STATUS current 712 DESCRIPTION 713 "Each entry in this table provides information about 714 multicast group IP address per mobility group." 715 INDEX { cLMobilityGroupMacAddress } 716 ::= { cLMobilityMulticastGroupTable 1 } 717 718CLMobilityMulticastGroupEntry ::= SEQUENCE { 719 cLMobilityGroupMacAddress MacAddress, 720 cLMobilityMulticastGroupIPAddress InetAddress, 721 cLMobilityMulticastGroupIPAddressType InetAddressType 722} 723 724cLMobilityGroupMacAddress OBJECT-TYPE 725 SYNTAX MacAddress 726 MAX-ACCESS not-accessible 727 STATUS current 728 DESCRIPTION 729 "This object represents the mobility group name present on the controller." 730 ::= { cLMobilityMulticastGroupEntry 1 } 731 732cLMobilityMulticastGroupIPAddress OBJECT-TYPE 733 SYNTAX InetAddress 734 MAX-ACCESS read-write 735 STATUS current 736 DESCRIPTION 737 "This object represnts the multicast 738 group IP address.The Ip address is limited to ipv4 and ipv6." 739 ::= { cLMobilityMulticastGroupEntry 2 } 740 741cLMobilityMulticastGroupIPAddressType OBJECT-TYPE 742 SYNTAX InetAddressType 743 MAX-ACCESS read-write 744 STATUS current 745 DESCRIPTION 746 "This used represents the multicast 747 group IP address type.The Ip address is limited to ipv4 and 748 ipv6." 749 ::= { cLMobilityMulticastGroupEntry 3 } 750 751 752-- ************************************************************** 753-- * Mobility Group Members Table 754-- ************************************************************** 755 756cLMobilityGroupMembersTable OBJECT-TYPE 757 SYNTAX SEQUENCE OF CLMobilityGroupMembersEntry 758 MAX-ACCESS not-accessible 759 STATUS current 760 DESCRIPTION 761 "This object represents the MWAR List (statically configured 762 members of the mobility group).Entries are added to the table 763 when configuring mobility group members." 764 ::= { ciscoLwappMobilityMIBObjects 5 } 765 766cLMobilityGroupMembersEntry OBJECT-TYPE 767 SYNTAX CLMobilityGroupMembersEntry 768 MAX-ACCESS not-accessible 769 STATUS current 770 DESCRIPTION 771 "This object represents an Entry (conceptual row) in the 772 cLMobilityGroupMembers table." 773 INDEX { cLMobilityGroupMacAddress } 774 ::= { cLMobilityGroupMembersTable 1 } 775 776CLMobilityGroupMembersEntry ::= SEQUENCE { 777 cLMobilityGroupMemberIPAddressType InetAddressType, 778 cLMobilityGroupMemberIPAddress InetAddress, 779 cLMobilityGroupMemberControlPathStatusUp TruthValue, 780 cLMobilityGroupMemberDataPathStatusUp TruthValue 781} 782 783cLMobilityGroupMemberIPAddressType OBJECT-TYPE 784 SYNTAX InetAddressType 785 MAX-ACCESS read-only 786 STATUS current 787 DESCRIPTION 788 "This object represents the IP Address type of the mobility 789 member 790 IP Address represented by cLMobilityGroupMemberIPAddress. The Ip 791 address is limited to ipv4 and ipv6." 792 ::= { cLMobilityGroupMembersEntry 1 } 793 794cLMobilityGroupMemberIPAddress OBJECT-TYPE 795 SYNTAX InetAddress 796 MAX-ACCESS read-only 797 STATUS current 798 DESCRIPTION 799 "This object represents the IP Address of the mobility member 800 corresponding to cLMobilityGroupMacAddress.The Ip address is 801 limited to ipv4 and ipv6." 802 ::= { cLMobilityGroupMembersEntry 2 } 803 804cLMobilityGroupMemberControlPathStatusUp OBJECT-TYPE 805 SYNTAX TruthValue 806 MAX-ACCESS read-only 807 STATUS current 808 DESCRIPTION 809 "This object represents the control path status of the mobility member 810 corresponding to cLMobilityGroupMacAddress." 811 DEFVAL { false } 812 ::= { cLMobilityGroupMembersEntry 3 } 813 814cLMobilityGroupMemberDataPathStatusUp OBJECT-TYPE 815 SYNTAX TruthValue 816 MAX-ACCESS read-only 817 STATUS current 818 DESCRIPTION 819 "This object represents the data path status of the mobility member 820 corresponding to cLMobilityGroupMacAddress." 821 DEFVAL { false } 822 ::= { cLMobilityGroupMembersEntry 4 } 823 824 825 826cLMobilityForeignWlcMapTable OBJECT-TYPE 827 SYNTAX SEQUENCE OF CLMobilityForeignWlcMapEntry 828 MAX-ACCESS not-accessible 829 STATUS current 830 DESCRIPTION 831 "This table is used to create mappings of the foreign controller 832 With the interface/interface group to be used, when clients 833 Directly connected to the foreign controller send the DHCP 834 Request to the anchor controller." 835 ::= { ciscoLwappMobilityMIBObjects 6 } 836 837cLMobilityForeignWlcMapEntry OBJECT-TYPE 838 SYNTAX CLMobilityForeignWlcMapEntry 839 MAX-ACCESS not-accessible 840 STATUS current 841 DESCRIPTION 842 "This represents a row in the cLMobilityForeignWlcIfMappingTable . 843 Entries are added and deleted by explicit user driven action." 844 INDEX { 845 cLMobilityAnchorWlanSsid, 846 cLMobilityForeignWlcMapMacAddress 847 } 848 ::= { cLMobilityForeignWlcMapTable 1 } 849 850CLMobilityForeignWlcMapEntry ::= SEQUENCE { 851 cLMobilityForeignWlcMapMacAddress MacAddress, 852 cLMobilityForeignWlcMapIf SnmpAdminString, 853 cLMobilityForeignWlcMapRowStatus RowStatus 854} 855 856cLMobilityForeignWlcMapMacAddress OBJECT-TYPE 857 SYNTAX MacAddress 858 MAX-ACCESS not-accessible 859 STATUS current 860 DESCRIPTION 861 "This object represents the MAC address of the foreign controller, 862 to which the interface mapping is to be configured." 863 ::= { cLMobilityForeignWlcMapEntry 1 } 864 865cLMobilityForeignWlcMapIf OBJECT-TYPE 866 SYNTAX SnmpAdminString 867 MAX-ACCESS read-create 868 STATUS current 869 DESCRIPTION 870 "This object represents name of the interface/interface group 871 which would be used for the communication 872 with the clients connected to the foreign controller, 873 represented by cLMobilityForeignWlcMapMacAddress ." 874 ::= { cLMobilityForeignWlcMapEntry 2 } 875 876cLMobilityForeignWlcMapRowStatus OBJECT-TYPE 877 SYNTAX RowStatus 878 MAX-ACCESS read-create 879 STATUS current 880 DESCRIPTION 881 "This object represents the row status." 882 ::= { cLMobilityForeignWlcMapEntry 3 } 883 884 885-- ******************************************************************* 886-- * DEFINITION OF OBJECTS ACCESSIBLE FOR NOTIFICATIONS ONLY 887-- ******************************************************************* 888 889cLMobilityTrapVariables OBJECT IDENTIFIER 890 ::= { ciscoLwappMobilityMIBObjects 3 } 891 892 893cLMobilityAnchorWlanId OBJECT-TYPE 894 SYNTAX Unsigned32 895 MAX-ACCESS accessible-for-notify 896 STATUS current 897 DESCRIPTION 898 "This object uniquely identifies one instance of 899 a WLAN on the controller." 900 ::= { cLMobilityTrapVariables 1 } 901 902cLMobilityAnchorAddressType OBJECT-TYPE 903 SYNTAX InetAddressType 904 MAX-ACCESS accessible-for-notify 905 STATUS current 906 DESCRIPTION 907 "Guest/Anchor switch Address type." 908 ::= { cLMobilityTrapVariables 2 } 909 910cLMobilityAnchorAddress OBJECT-TYPE 911 SYNTAX InetAddress 912 MAX-ACCESS accessible-for-notify 913 STATUS current 914 DESCRIPTION 915 "Guest/Anchor switch Address. 916 The IP Address is limited to IPv4 and IPv6" 917 ::= { cLMobilityTrapVariables 3 } 918 919-- ******************************************************************* 920-- * END OF - DEFINITION OF OBJECTS ACCESSIBLE FOR NOTIFICATIONS ONLY 921-- ******************************************************************* 922-- 923 924-- ******************************************************************* 925-- * NOTIFICATIONS 926-- ******************************************************************* 927 928ciscoLwappMobilityAnchorControlPathDown NOTIFICATION-TYPE 929 OBJECTS { 930 cLMobilityAnchorAddressType, 931 cLMobilityAnchorAddress 932 } 933 STATUS current 934 DESCRIPTION 935 "This trap will be declared by the Controller when, 936 successive ICMP ping attempts to the anchor fails 937 and the anchor is conclusively down. 938 Variable cLMobilityAnchorIPAddress denotes the 939 IP Address of the anchor." 940 ::= { ciscoLwappMobilityMIBNotifs 1 } 941 942ciscoLwappMobilityAnchorControlPathUp NOTIFICATION-TYPE 943 OBJECTS { 944 cLMobilityAnchorAddressType, 945 cLMobilityAnchorAddress 946 } 947 STATUS current 948 DESCRIPTION 949 "This trap will be declared by the Controller when, 950 ICMP ping to the anchor is restored and anchor is 951 conclusively up. 952 Variable cLMobilityAnchorIPAddress denotes the 953 IP Address of the anchor." 954 ::= { ciscoLwappMobilityMIBNotifs 2 } 955 956ciscoLwappMobilityAnchorDataPathDown NOTIFICATION-TYPE 957 OBJECTS { 958 cLMobilityAnchorAddressType, 959 cLMobilityAnchorAddress 960 } 961 STATUS current 962 DESCRIPTION 963 "This trap will be declared by the Controller when, 964 successive EoIP ping attempts to the anchor fails 965 and the anchor is conclusively down. 966 Variable cLMobilityAnchorIPAddress denotes the 967 IP Address of the anchor." 968 ::= { ciscoLwappMobilityMIBNotifs 3 } 969 970ciscoLwappMobilityAnchorDataPathUp NOTIFICATION-TYPE 971 OBJECTS { 972 cLMobilityAnchorAddressType, 973 cLMobilityAnchorAddress 974 } 975 STATUS current 976 DESCRIPTION 977 "This trap will be declared by the Controller when, 978 EoIP ping to the anchor is restored and anchor is 979 conclusively up. 980 Variable cLMobilityAnchorIPAddress denotes the 981 IP Address of the anchor." 982 ::= { ciscoLwappMobilityMIBNotifs 4 } 983 984ciscoLwappMobilityAllAnchorsOnWlanDown NOTIFICATION-TYPE 985 OBJECTS { cLMobilityAnchorWlanId } 986 STATUS current 987 DESCRIPTION 988 "This trap will be declared by the Controller when, 989 successive EoIP ping attempts to all the anchors on 990 WLAN, denoted by cLMobilityAnchorWlanId, fails and 991 all the anchors are conclusively down." 992 ::= { ciscoLwappMobilityMIBNotifs 5 } 993 994ciscoLwappMobilityOneAnchorOnWlanUp NOTIFICATION-TYPE 995 OBJECTS { cLMobilityAnchorWlanId } 996 STATUS current 997 DESCRIPTION 998 "This trap will be declared by the Controller when, 999 successive EoIP and UDP ping to atleast one anchor 1000 on the WLAN, denoted by cLMobilityAnchorWlanId, is 1001 restored and anchor is conclusively up." 1002 ::= { ciscoLwappMobilityMIBNotifs 6 } 1003-- ******************************************************************* 1004-- * END OF - NOTIFICATIONS 1005-- ******************************************************************* 1006-- 1007-- ******************************************************************* 1008-- * Compliance statements 1009-- ******************************************************************* 1010 1011ciscoLwappMobilityMIBCompliances OBJECT IDENTIFIER 1012 ::= { ciscoLwappMobilityMIBConform 1 } 1013 1014ciscoLwappMobilityMIBGroups OBJECT IDENTIFIER 1015 ::= { ciscoLwappMobilityMIBConform 2 } 1016 1017 1018ciscoLwappMobilityMIBCompliance MODULE-COMPLIANCE 1019 STATUS deprecated 1020 DESCRIPTION 1021 "The compliance statement for the SNMP entities that 1022 implement the ciscoLwappMobilityMIB module." 1023 MODULE -- this module 1024 MANDATORY-GROUPS { 1025 cLNplus1RedundancyRev01ConfigGroup, 1026 cLNplus1RedundancyRev01StatusGroup, 1027 cLNplus1RedundancyRev01NotifsGroup, 1028 cLSymmetricTunnelingRev01ConfigGroup, 1029 cLSymmetricTunnelingRev01StatusGroup 1030 } 1031 ::= { ciscoLwappMobilityMIBCompliances 1 } 1032 1033ciscoLwappMobilityMIBComplianceRev01 MODULE-COMPLIANCE 1034 STATUS current 1035 DESCRIPTION 1036 "The compliance statement for the SNMP entities that 1037 implement the ciscoLwappMobilityMIB module." 1038 MODULE -- this module 1039 MANDATORY-GROUPS { 1040 cLNplus1RedundancyRev01ConfigGroup, 1041 cLNplus1RedundancyRev01StatusGroup, 1042 cLNplus1RedundancyRev01NotifsGroup, 1043 cLSymmetricTunnelingRev01ConfigGroup, 1044 cLSymmetricTunnelingRev01StatusGroup, 1045 cLMobilityGroupRev01ConfigGroup 1046 } 1047 ::= { ciscoLwappMobilityMIBCompliances 2 } 1048 1049-- ******************************************************************* 1050-- * Units of conformance 1051-- ******************************************************************* 1052 1053cLNplus1RedundancyRev01ConfigGroup OBJECT-GROUP 1054 OBJECTS { 1055 cLMobilityAnchorGroupKeepAliveNumber, 1056 cLMobilityAnchorGroupKeepAliveInterval 1057 } 1058 STATUS current 1059 DESCRIPTION 1060 "This is a collection of objects which can 1061 configured to control functional parameters 1062 of Guest Tunneling N+1 Redundancy feature in 1063 CISCO 4400 / 2006 series of WLAN controllers." 1064 ::= { ciscoLwappMobilityMIBGroups 1 } 1065 1066cLNplus1RedundancyRev01StatusGroup OBJECT-GROUP 1067 OBJECTS { 1068 cLMobilityAnchorStatus, 1069 cLMobilityAnchorRowStatus, 1070 cLMobilityAnchorWlanId, 1071 cLMobilityAnchorAddressType, 1072 cLMobilityAnchorAddress 1073 } 1074 STATUS current 1075 DESCRIPTION 1076 "This collection of objects represents the information 1077 about the general status attributes of Guest Tunneling 1078 N+1 Redundancy in CISCO 4400 / 2006 series of WLAN 1079 controllers." 1080 ::= { ciscoLwappMobilityMIBGroups 2 } 1081 1082cLNplus1RedundancyRev01NotifsGroup NOTIFICATION-GROUP 1083 NOTIFICATIONS { 1084 ciscoLwappMobilityAnchorControlPathDown, 1085 ciscoLwappMobilityAnchorControlPathUp, 1086 ciscoLwappMobilityAnchorDataPathDown, 1087 ciscoLwappMobilityAnchorDataPathUp, 1088 ciscoLwappMobilityAllAnchorsOnWlanDown, 1089 ciscoLwappMobilityOneAnchorOnWlanUp 1090 } 1091 STATUS current 1092 DESCRIPTION 1093 "This is a collection of notifications about the 1094 general functional behavior of Guest Tunneling 1095 N+1 Redundancy in CISCO 4400 / 2006 series of 1096 WLAN controllers." 1097 ::= { ciscoLwappMobilityMIBGroups 3 } 1098 1099cLSymmetricTunnelingRev01ConfigGroup OBJECT-GROUP 1100 OBJECTS { cLMobilityAnchorSmtStatus } 1101 STATUS current 1102 DESCRIPTION 1103 "This is a collection of objects which can be 1104 configured to control functional parameters 1105 of Symmetric Mobility Tunneling feature in 1106 CISCO 4400 / 2006 series of WLAN controllers." 1107 ::= { ciscoLwappMobilityMIBGroups 4 } 1108 1109cLSymmetricTunnelingRev01StatusGroup OBJECT-GROUP 1110 OBJECTS { cLMobilityAnchorCurrentSmt } 1111 STATUS current 1112 DESCRIPTION 1113 "This collection of objects represents the 1114 information about the general status attributes 1115 of Symmetric Mobility Tunneling feature in 1116 CISCO 4400 / 2006 series of WLAN controllers." 1117 ::= { ciscoLwappMobilityMIBGroups 5 } 1118 1119cLMobilityGroupRev01ConfigGroup OBJECT-GROUP 1120 OBJECTS { 1121 cLMobilityMulticastMessagingEnable, 1122 cLMobilityMulticastGroupIPAddress, 1123 cLMobilityMulticastGroupIPAddressType, 1124 cLMobilityGroupMemberIPAddressType, 1125 cLMobilityGroupMemberIPAddress, 1126 cLMobilityGroupMemberControlPathStatusUp, 1127 cLMobilityGroupMemberDataPathStatusUp, 1128 cLMobilityForeignWlcMapIf, 1129 cLMobilityForeignWlcMapRowStatus 1130 } 1131 STATUS current 1132 DESCRIPTION 1133 "This collection of objects represents the 1134 information about the mobility groups and the 1135 interface mappings with foreign controllers." 1136 ::= { ciscoLwappMobilityMIBGroups 6 } 1137 1138END 1139 1140 1141 1142 1143 1144 1145 1146 1147 1148 1149 1150 1151 1152