1-- ******************************************************************* 2-- CISCO-WIRELESS-NOTIFICATION-MIB.my 3-- April 2009, Venkatraghavan Sankarasubbu, Poon Leung 4-- 5-- Copyright (c) 2009-2011 by Cisco Systems Inc. 6-- All rights reserved. 7-- ******************************************************************* 8 9CISCO-WIRELESS-NOTIFICATION-MIB DEFINITIONS ::= BEGIN 10 11IMPORTS 12 MODULE-IDENTITY, 13 NOTIFICATION-TYPE, 14 Unsigned32, 15 OBJECT-TYPE 16 FROM SNMPv2-SMI 17 MODULE-COMPLIANCE, 18 NOTIFICATION-GROUP, 19 OBJECT-GROUP 20 FROM SNMPv2-CONF 21 DateAndTime, 22 TEXTUAL-CONVENTION, 23 TruthValue 24 FROM SNMPv2-TC 25 SnmpAdminString 26 FROM SNMP-FRAMEWORK-MIB 27 InetAddressType, 28 InetAddress 29 FROM INET-ADDRESS-MIB 30 CiscoAlarmSeverity 31 FROM CISCO-TC 32 ciscoMgmt 33 FROM CISCO-SMI; 34 35 36-- ******************************************************************** 37-- * MODULE IDENTITY 38-- ******************************************************************** 39 40ciscoWirelessNotificationMIB MODULE-IDENTITY 41 LAST-UPDATED "201106060000Z" 42 ORGANIZATION "Cisco Systems, Inc." 43 CONTACT-INFO 44 "Cisco Systems 45 Customer Service 46 Postal: 170 W Tasman Drive 47 San Jose, CA 95134 48 USA 49 Tel: +1 800 553-NETS 50 E-mail: cs-wnbu-snmp@cisco.com" 51 DESCRIPTION 52 "This MIB is intended to be implemented on those Network 53 Management applications that manage a network of wireless 54 devices through the Controller and send relevant management 55 information to Northbound Operation Support Systems. The 56 Northbound OSS, with the information received shall present a 57 consolidated view of the whole network of wireless devices. 58 59 The NM learns the status of the managed devices from the 60 Controller through interfaces like the SNMP, and raises 61 events. Depending upon the event severity, alerts are raised 62 for the events. The alert/event information is sent to the 63 Northbound OSS in the form of SNMP Notifications. This MIB 64 defines these Notifications. 65 66 The MIB objects cWNotificationDescription, 67 cWNotificationSpecialAttributes and cWNotificationVirtualDomains 68 have been defined to have a maximum size of 1024. The bigger 69 size is required for the following reasons. 70 71 1. If the size is reduced, the information intended to be 72 sent to the Northbound applications will be truncated / lost. 73 74 2. Networks using UDP are better in handling fragmentation than 75 before. 76 77 3. In case if the implementation is used in those networks that 78 can't handle Notifications of a larger size, the intent is to 79 suggest the use of the TCP as the transport protocol for SNMP as 80 against the UDP. 81 82 4. The respective objects may not have the maximum defined range 83 at all the times. The higher range is just to accommodate those 84 cases where the size can hit the maximum value. 85 86 The relationships between NCS, CC, AP, MN and 87 Mgmt-Appl can be depicted as follows : 88 89 +................+ +................+ 90 + + + + 91 + NB OSS 1 + .. + NB OSS n + 92 + + + + 93 +................+ +................+ 94 ^ ^ 95 . . 96 . . Notifications 97 . . 98 . 99 +..........+ 100 + + 101 + NCS + 102 + + 103 +..........+ 104 ^ ^ ^ 105 . . . SNMP 106 . . . 107 . . . 108 . . . 109 +......+ +......+ +......+ 110 + + + + + + 111 + CC + + CC + + CC + 112 + + + + + + 113 +......+ +......+ +......+ 114 .. . . 115 . . . . 116 . . . . 117 . . . . 118 . . . . 119 +......+ +......+ +......+ +......+ 120 + + + + + + + + 121 + AP + + AP + + AP + + AP + 122 + + + + + + + + 123 +......+ +......+ +......+ +......+ 124 . . . 125 . . . . 126 . . . . 127 . . . . 128 . . . . 129 +......+ +......+ +......+ +......+ 130 + + + + + + + + 131 + MN + + MN + + MN + + MN + 132 + + + + + + + + 133 +......+ +......+ +......+ +......+ 134 135 136 GLOSSARY 137 138 Access Point ( AP ) 139 140 An entity that contains an 802.11 medium access 141 control (MAC) and physical layer (PHY) interface 142 and provides access to the distribution services via 143 the wireless medium for associated clients. 144 145 LWAPP APs encapsulate all the 802.11 frames in 146 LWAPP frames and sends it to the Controller to which 147 it is logically connected to. 148 149 Alert 150 151 An alert is an NM response to one or more related Events from 152 Managed Object. If the Event learnt is severe enough to let the 153 user know about, the NM raises an alert i.e if event has one of 154 the following severity critical, major, minor or warning. One 155 or more Events can result in a single alert being raised. 156 157 Central Controller ( CC ) 158 159 The central entity that terminates the LWAPP protocol 160 tunnel from the LWAPP APs. Throughout this MIB, 161 this entity is also referred to as 'Controller'. 162 163 Event 164 165 An Event is an occurrence or detection of some condition in and 166 around the network. Event can be generated by the NM 167 corresponding to traps received or through polling the managed 168 object. 169 170 Light Weight Access Point Protocol ( LWAPP ) 171 172 This is a generic protocol that defines the 173 communication between the Access Points and the 174 Controllers. 175 176 Managed Object 177 178 Managed Objects are used to represent those entities being 179 managed by the NM. It could be an AP, WLAN, Controller or 180 an MN. 181 182 Mobile Node ( MN ) 183 184 Mobile Nodes are roaming 802.11 wireless devices that would 185 associate to an AP to get their uplink to the wired network. 186 Mobile Nodes are also known as clients. 187 188 Network Management Application ( NM ) 189 190 Application which manages network of managed objects using 191 SNMP. It provides network management functions of FCAPS - 192 Fault, Configuration, Accounting, Performance and Security to 193 manage the network. 194 195 Notification 196 197 NM application like NCS sends Notifications defined through 198 this MIB, corresponding to their Alerts and Events to a 199 Northbound OSS to provide a consolidated view. 200 201 Operations Support Systems ( OSS ) 202 203 Management applications in the network that receive 204 Notifications from NM (like NCS) and provide consolidated view 205 of the whole network of wireless devices. 206 207 Received Signal Strength Indicator ( RSSI ) 208 209 A measure of the strength of the signal as observed by the 210 entity that received it, expressed in 'dbm'. 211 212 Signal-Noise Ratio ( SNR ) 213 214 A measure of the quality of the signal relative to the strength 215 of noise expressed in 'dB'. 216 217 Virtual Domain 218 219 A NM's Virtual Domain is a logical grouping that consists of a 220 set of managed objects like Controllers, APs, WLANs, maps etc. 221 It restricts a user's view to information relevant to these 222 managed objects. Through a virtual domain, an administrator can 223 ensure that users are only able to view the managed objects and 224 maps for which they are responsible. A managed object can belong 225 to more than one virtual domain. 226 227 Network Control System ( NCS ) 228 229 Network Control System (NCS) is a converged platform for 230 wired, wireless, and security policy management in a single 231 solution for faster troubleshooting and more efficient network 232 operations. 233 234 235 Wireless LAN ( WLAN ) 236 237 A WLAN refers to the network of IEEE 802.11 complaint wireless 238 devices within mutual communication range of each other via 239 the wireless medium. 240 241 REFERENCE 242 243 [1] Wireless LAN Medium Access Control (MAC) and 244 Physical Layer (PHY) Specifications. 245 246 [2] IEEE 802.11 - The original 1 Mbit/s and 2 Mbit/s, 247 2.4 GHz RF and IR standard." 248 REVISION "201106060000Z" 249 DESCRIPTION 250 "Adding a new enumeration type 'ncs' to 251 CWirelessNotificationCategory object. 252 Changing 'WCS' to 'NCS'" 253 REVISION "201009150000Z" 254 DESCRIPTION 255 "Adding a new enumeration type 'switch' to 256 CWirelessNotificationCategory object." 257 REVISION "200910280000Z" 258 DESCRIPTION 259 "Initial version of this MIB module." 260 ::= { ciscoMgmt 712 } 261 262 263 264CWirelessNotificationType ::= TEXTUAL-CONVENTION 265 STATUS current 266 DESCRIPTION 267 "This textual convention defines the different Notification 268 types. 269 270 Unknown : This indicates an unknown Notification type. 271 272 Alert : This indicates that the Notification is generated due 273 to an Alert generated by a set of Events. 274 275 Event : This indicates that the Notification is generated due 276 to an Event related to a Managed Object. The Event can 277 be raised through polling the Managed Object, 278 receiving SNMP Notifications from the Managed Object 279 etc." 280 SYNTAX INTEGER { 281 unknown(1), 282 alert(2), 283 event(3) 284 } 285 286CWirelessNotificationCategory ::= TEXTUAL-CONVENTION 287 STATUS current 288 DESCRIPTION 289 "This textual convention defines the different 290 Notification categories. The semantics are as follows. 291 292 'unknown' This indicates an unknown category. 293 294 'accessPoints' The Notification is associated with 295 APs. 296 297 'adhocRogue' The Notification is associated with 298 adhoc rogue APs. 299 300 'clients' The Notification is associated with 301 client/mobile nodes. 302 303 'controllers' The Notification is associated 304 with Controllers. 305 306 'coverageHole' The Notification is associated with 307 holes in radio coverage. 308 309 'contextAwareNotifications' The Notification is associated with 310 Alerts generated by location service 311 for Event definitions configured 312 on the MSE like 313 containment,chokepoint etc. 314 315 'interference' The Notification is associated with 316 interference in radio coverage by 317 APs. 318 319 'meshLinks' The Notification is associated with 320 mesh wireless networks. 321 322 'mobilityService' The Notification is associated with 323 MSE status. 324 325 'performance' The Notification is associated with 326 wireless network performance. 327 328 'rogueAP' The Notification is associated with 329 rogue APs detected in the network. 330 331 'rrm' The Notification is associated to 332 radio resource management. 333 334 'security' The Notification is associated with 335 security of wireless networks. 336 337 'wcs' The Notification is associated with 338 WCS. 339 340 'switch' The Notification is associated with 341 Ethernet switch. 342 343 'ncs' The Notification is associated with 344 NCS." 345 SYNTAX INTEGER { 346 unknown(1), 347 accessPoints(2), 348 adhocRogue(3), 349 clients(4), 350 controllers(5), 351 coverageHole(6), 352 interference(7), 353 contextAwareNotifications(8), 354 meshLinks(9), 355 mobilityService(10), 356 performance(11), 357 rogueAP(12), 358 rrm(13), 359 security(14), 360 wcs(15), 361 switch(16), 362 ncs(17) 363 } 364ciscoWirelessNotificationMIBNotifs OBJECT IDENTIFIER 365 ::= { ciscoWirelessNotificationMIB 0 } 366 367ciscoWirelessNotificationMIBObjects OBJECT IDENTIFIER 368 ::= { ciscoWirelessNotificationMIB 1 } 369 370ciscoWirelessNotificationMIBConform OBJECT IDENTIFIER 371 ::= { ciscoWirelessNotificationMIB 2 } 372 373cWNotificationData OBJECT IDENTIFIER 374 ::= { ciscoWirelessNotificationMIBObjects 1 } 375 376 377cwNotificationHistoryTableMaxLength OBJECT-TYPE 378 SYNTAX Unsigned32 (1..4294967295) 379 MAX-ACCESS read-write 380 STATUS current 381 DESCRIPTION 382 "This object represents the maximum number of entries 383 permissible in cwNotificationHistoryTable. When user sets this 384 to a lower value, for example from 100 to 50, entries 385 corresponding to older Notifications will be deleted to adjust 386 to the new setting." 387 DEFVAL { 100 } 388 ::= { cWNotificationData 1 } 389-- ******************************************************************** 390-- * NCS Notification Table 391-- ******************************************************************** 392 393cwNotificationHistoryTable OBJECT-TYPE 394 SYNTAX SEQUENCE OF CwNotificationHistoryEntry 395 MAX-ACCESS not-accessible 396 STATUS current 397 DESCRIPTION 398 "This table represents the information about the Notifications 399 sent by the NM to Northbound applications. The Notification 400 fields are populated from the corresponding Alert/Event.Whenever 401 the NM sends a Notification to one of the Northbound 402 applications, a row will be added to this table. When the number 403 of maximum allowed of entries is decreased through 404 cwNotificationHistoryTableMaxLength, the least recent entries 405 will be deleted." 406 ::= { cWNotificationData 2 } 407 408cwNotificationHistoryEntry OBJECT-TYPE 409 SYNTAX CwNotificationHistoryEntry 410 MAX-ACCESS not-accessible 411 STATUS current 412 DESCRIPTION 413 "Each entry represents a conceptual row in 414 cwNotificationHistoryTable and corresponds to the information 415 about a Notification sent by the NM to Northbound applications." 416 INDEX { cWNotificationIndex } 417 ::= { cwNotificationHistoryTable 1 } 418 419CwNotificationHistoryEntry ::= SEQUENCE { 420 cWNotificationIndex Unsigned32, 421 cWNotificationTimestamp DateAndTime, 422 cWNotificationUpdatedTimestamp DateAndTime, 423 cWNotificationKey SnmpAdminString, 424 cWNotificationCategory CWirelessNotificationCategory, 425 cWNotificationSubCategory OCTET STRING, 426 cWNotificationManagedObjectAddressType InetAddressType, 427 cWNotificationManagedObjectAddress InetAddress, 428 cWNotificationSourceDisplayName OCTET STRING, 429 cWNotificationDescription OCTET STRING, 430 cWNotificationSeverity CiscoAlarmSeverity, 431 cWNotificationSpecialAttributes OCTET STRING, 432 cWNotificationType CWirelessNotificationType, 433 cWNotificationVirtualDomains OCTET STRING 434} 435 436cWNotificationIndex OBJECT-TYPE 437 SYNTAX Unsigned32 (1..4294967295) 438 MAX-ACCESS not-accessible 439 STATUS current 440 DESCRIPTION 441 "This object represents a monotonically increasing 442 integer that uniquely identifies the information about the 443 Notification. When the maximum value defined by 444 cwNotificationHistoryTableMaxLength is reached, the value wraps 445 back to 1." 446 ::= { cwNotificationHistoryEntry 1 } 447 448cWNotificationTimestamp OBJECT-TYPE 449 SYNTAX DateAndTime 450 MAX-ACCESS read-only 451 STATUS current 452 DESCRIPTION 453 "This object in the Notification represents the time when the 454 corresponding Alert/Event was raised by the NM for a particular 455 condition in the network." 456 ::= { cwNotificationHistoryEntry 2 } 457 458cWNotificationUpdatedTimestamp OBJECT-TYPE 459 SYNTAX DateAndTime 460 MAX-ACCESS read-only 461 STATUS current 462 DESCRIPTION 463 "This object in the Notification represents the time when Alert 464 was last updated. Alerts persist over time and it is possible 465 that their field(s) get changed. For example, when severity 466 changes from a higher level (ex critical to major or major to 467 minor or minor to clear), then the severity field gets updated. 468 This object represents the time when it happened. This object 469 will not be populated for Events." 470 ::= { cwNotificationHistoryEntry 3 } 471 472cWNotificationKey OBJECT-TYPE 473 SYNTAX SnmpAdminString (SIZE (1..255)) 474 MAX-ACCESS read-only 475 STATUS current 476 DESCRIPTION 477 "This object represents the entity string that describes the 478 network condition identified by cwNotificationType for which 479 this Notification is generated." 480 ::= { cwNotificationHistoryEntry 4 } 481 482cWNotificationCategory OBJECT-TYPE 483 SYNTAX CWirelessNotificationCategory 484 MAX-ACCESS read-only 485 STATUS current 486 DESCRIPTION 487 "This object represents the category of the network condition 488 represented by cwNotificationType for which this Notification 489 is generated." 490 ::= { cwNotificationHistoryEntry 5 } 491 492cWNotificationSubCategory OBJECT-TYPE 493 SYNTAX OCTET STRING (SIZE (1..256)) 494 MAX-ACCESS read-only 495 STATUS current 496 DESCRIPTION 497 "This object represents the sub category of the network 498 condition identified by cwNotificationType for which this 499 Notification is generated. This object can be used to further 500 filter down Alert/Event under a particular category." 501 ::= { cwNotificationHistoryEntry 6 } 502 503cWNotificationManagedObjectAddressType OBJECT-TYPE 504 SYNTAX InetAddressType 505 MAX-ACCESS read-only 506 STATUS current 507 DESCRIPTION 508 "This object represents the type of the Internet 509 network address made available through 510 cWNotificationManagedObjectAddress." 511 ::= { cwNotificationHistoryEntry 7 } 512 513cWNotificationManagedObjectAddress OBJECT-TYPE 514 SYNTAX InetAddress 515 MAX-ACCESS read-only 516 STATUS current 517 DESCRIPTION 518 "This object represents the network address of the Managed 519 Object. The type of the address stored in this object is 520 determined by the 521 cWNotificationManagedObjectAddressType object." 522 ::= { cwNotificationHistoryEntry 8 } 523 524cWNotificationSourceDisplayName OBJECT-TYPE 525 SYNTAX OCTET STRING (SIZE (1..256)) 526 MAX-ACCESS read-only 527 STATUS current 528 DESCRIPTION 529 "This object represents the display name for the source that 530 triggered the network condition represented by 531 cwNotificationType for which this Notification is generated." 532 ::= { cwNotificationHistoryEntry 9 } 533 534cWNotificationDescription OBJECT-TYPE 535 SYNTAX OCTET STRING (SIZE (1..1024)) 536 MAX-ACCESS read-only 537 STATUS current 538 DESCRIPTION 539 "This object represents a detailed description of the network 540 condition represented by cwNotificationType for which this 541 Notification is generated. For example, rogueAp Alert is 542 described as follows, 'Rogue AP '00:1b:2b:35:6a:f3' is removed; 543 it was detected as Rogue AP by AP 'test_1' Radio Type 544 '802.11b''." 545 ::= { cwNotificationHistoryEntry 10 } 546 547cWNotificationSeverity OBJECT-TYPE 548 SYNTAX CiscoAlarmSeverity 549 MAX-ACCESS read-only 550 STATUS current 551 DESCRIPTION 552 "This object represents the severity of the network condition 553 represented by cwNotificationType for which this Notification is 554 generated." 555 ::= { cwNotificationHistoryEntry 11 } 556 557cWNotificationSpecialAttributes OBJECT-TYPE 558 SYNTAX OCTET STRING (SIZE (1..1024)) 559 MAX-ACCESS read-only 560 STATUS current 561 DESCRIPTION 562 "This object represents the specialized attributes required 563 to describe the network condition identified by 564 cWNotificationType. These include SNR, RSSI, channel information 565 etc. This value is formatted as 'name=value' pairs in CSV 566 format. For example, rogueAP Alert's special attributes are sent 567 as 'detectingAPRadioType=a0,YCoordinate=0, state=11, 568 rogueApType=0, spt Status=0, ssId=wpspsk, on80211A=0, 569 numOfDetectingAps=0, on80211B=1, XCoordinate=0, 570 classificationType=3, channelNumber=6, containmentLevel=0, 571 rssi=-51, rogueApMacAddr=00:1b:2b:35:6a:f3, onNetwork=0, total 572 RogueClients=0'. This string can be parsed to get different 573 name-value pairs." 574 ::= { cwNotificationHistoryEntry 12 } 575 576cWNotificationType OBJECT-TYPE 577 SYNTAX CWirelessNotificationType 578 MAX-ACCESS read-only 579 STATUS current 580 DESCRIPTION 581 "This object represents the type of this Notification. This 582 basically indicates the trigger that has caused the NM to 583 generate this Notification." 584 ::= { cwNotificationHistoryEntry 13 } 585 586cWNotificationVirtualDomains OBJECT-TYPE 587 SYNTAX OCTET STRING (SIZE (1..1024)) 588 MAX-ACCESS read-only 589 STATUS current 590 DESCRIPTION 591 "This object represents the name of one or multiple virtual 592 domains(comma separated) the source of the network condition 593 represented by cWNotificationType is logically assigned to. For 594 example, 'root, California, San Jose' indicates that the source 595 of the network condition is logically assigned to these 596 multiple virtual domains." 597 ::= { cwNotificationHistoryEntry 14 } 598 599 600 601cwNotificationMOStatusEnable OBJECT-TYPE 602 SYNTAX TruthValue 603 MAX-ACCESS read-write 604 STATUS current 605 DESCRIPTION 606 "This object is to control the generation of 607 ciscoWirelessMOStatusNotification. 608 609 A value of 'true' indicates that the NM generates 610 ciscoWirelessMOStatusNotification Notification. 611 612 A value of 'false' indicates that the NM does not 613 generate ciscoWirelessMOStatusNotification Notification." 614 DEFVAL { true } 615 ::= { cWNotificationData 3 } 616 617-- ******************************************************************** 618-- * NOTIFICATION TYPE objects 619-- ******************************************************************** 620 621ciscoWirelessMOStatusNotification NOTIFICATION-TYPE 622 OBJECTS { 623 cWNotificationTimestamp, 624 cWNotificationUpdatedTimestamp, 625 cWNotificationKey, 626 cWNotificationCategory, 627 cWNotificationSubCategory, 628 cWNotificationManagedObjectAddressType, 629 cWNotificationManagedObjectAddress, 630 cWNotificationSourceDisplayName, 631 cWNotificationDescription, 632 cWNotificationSeverity, 633 cWNotificationSpecialAttributes, 634 cWNotificationVirtualDomains 635 } 636 STATUS current 637 DESCRIPTION 638 "This Notification is generated by the NM in response to an 639 Alert or Event related to a network device managed by it." 640 ::= { ciscoWirelessNotificationMIBNotifs 1 } 641-- ******************************************************************** 642-- * Conformance Information 643-- ******************************************************************** 644 645ciscoWirelessNotificationMIBCompliances OBJECT IDENTIFIER 646 ::= { ciscoWirelessNotificationMIBConform 1 } 647 648ciscoWirelessNotificationMIBGroups OBJECT IDENTIFIER 649 ::= { ciscoWirelessNotificationMIBConform 2 } 650 651 652ciscoWirelessNotificationMIBCompliance MODULE-COMPLIANCE 653 STATUS current 654 DESCRIPTION 655 "The compliance statement for the SNMP entities which 656 implement the CISCO-WIRELESS-NOTIFICATION-MIB." 657 MODULE -- this module 658 MANDATORY-GROUPS { 659 ciscoWirelessNotificationObjectsGroup, 660 ciscoWirelessNotificationsGroup, 661 ciscoWirelessNotificationConfigGroup, 662 ciscoWirelessNotificationEnableGroup 663 } 664 ::= { ciscoWirelessNotificationMIBCompliances 1 } 665 666-- ******************************************************************** 667-- * Units of conformance 668-- ******************************************************************** 669 670ciscoWirelessNotificationConfigGroup OBJECT-GROUP 671 OBJECTS { cwNotificationHistoryTableMaxLength } 672 STATUS current 673 DESCRIPTION 674 "This collection of objects is used to manage the information 675 about Notifications." 676 ::= { ciscoWirelessNotificationMIBGroups 1 } 677 678ciscoWirelessNotificationsGroup NOTIFICATION-GROUP 679 NOTIFICATIONS { ciscoWirelessMOStatusNotification } 680 STATUS current 681 DESCRIPTION 682 "This collection of objects represent the Notifications 683 generated by the NM." 684 ::= { ciscoWirelessNotificationMIBGroups 2 } 685 686ciscoWirelessNotificationObjectsGroup OBJECT-GROUP 687 OBJECTS { 688 cWNotificationTimestamp, 689 cWNotificationUpdatedTimestamp, 690 cWNotificationKey, 691 cWNotificationCategory, 692 cWNotificationSubCategory, 693 cWNotificationManagedObjectAddressType, 694 cWNotificationManagedObjectAddress, 695 cWNotificationSourceDisplayName, 696 cWNotificationDescription, 697 cWNotificationSeverity, 698 cWNotificationSpecialAttributes, 699 cWNotificationType, 700 cWNotificationVirtualDomains 701 } 702 STATUS current 703 DESCRIPTION 704 "This collection of objects provide the information 705 about the Notifications generated by the NM." 706 ::= { ciscoWirelessNotificationMIBGroups 3 } 707 708ciscoWirelessNotificationEnableGroup OBJECT-GROUP 709 OBJECTS { cwNotificationMOStatusEnable } 710 STATUS current 711 DESCRIPTION 712 "This collection of objects is used to control the generation 713 of Notifications." 714 ::= { ciscoWirelessNotificationMIBGroups 4 } 715 716END 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789