JUNOS Configuration Sample Clauses

JUNOS Configuration. In the previous deliverable, two possible solutions for the initial step in the discovery phase were introduced. In the implemented prototype, the discovery phase’s starting point is an SNMP trap which is sent by the device that wants to connect to the FEDERICA NOC. A requirement of this option is that the device that wishes to connect must know the NOC’s IP address to which it should connect. This requirement can be avoided, by having the trap receiver on another location and forwarding the packet to the central NOC. In this case, when the trap receiver forwards the packet, the original source address of an SNMP trap packet’s IP header is still the outgoing interface of the original sender. In this prototype, a central NMS has been simulated, without intermediate elements. Another requirement is that the management interfaces (me0 on switches, fxp0 on routers) should be assigned an IP address. This is a basic requirement for the use of SNMP and is also needed by the NOC so that they can connect to the device that has sent the trap and wishes to connect to the infrastructure. The Juniper routers (MX‐480) and switches (EX‐3200) currently used in the FEDERICA infrastructure have the possibility to be SNMP enabled. The JUNOS software installed on these devices supports SNMP versions 1, 2 and 3. All standard SNMP MIBs are supported, and Juniper has developed several enterprise‐specific MIBs. For this prototype, only standard SNMP MIBs are implemented and no Juniper MIBs are used. However, in the future, when other types of equipment will be implemented, other types of MIBs can easily be discovered. In the Juniper equipment, SNMP is disabled by default and therefore, must be enabled for each device. This is an easy procedure done by entering the [edit snmp] hierarchy level, and then the SNMP will be enabled on the device. Once the SNMP is enabled, it must be configured in such a way that it will send a trap to the NOC upon booting. This configuring must be done manually on the local device. At an absolute minimum, the following statements should be included at the [edit snmp] hierarchy level as seen in the image below. These statements are explained in further detail below. snmp { trap‐group "FEDERICA" { categories start‐up; targets { //The IP address of the NOC xxx.xxx.xxx.xxx; version all; } } The first statement enables the use of SNMP on the device as explained previously. The next statement introduces the trap‐group called FEDERICA. Establishing trap‐group...
AutoNDA by SimpleDocs

Related to JUNOS Configuration

  • Configuration The configuration for the Purchase Right Aircraft will be the Detail Specification for Model 767-3S2F aircraft at the revision level in effect at the time of the Supplemental Agreement. Such Detail Specification will be revised to include (i) changes required to obtain required regulatory certificates and (ii) other changes as mutually agreed upon by Boeing and Customer.

  • Functionality Customer is entitled to additional functionality previously purchased or bundled with the software if available in the version or update released on or after the start date of the Agreement. Customer acknowledges that certain functionality in current and previous software versions may not be available in future upgrades. Added functionality may require additional paid services (clinical and technical) to configure and support.

  • Software Use Case Red Hat Enterprise Virtualization Supported on physical hardware solely to support virtual quests. Red Hat Enterprise Virtualization is designed to run and manage virtual instances and does not support user-space applications. Red Hat Enterprise Virtualization may be used as a virtual desktop infrastructure solution, however, the Subscription does not come with any software or support for the desktop operating system. You must purchase the operating system for each instance of a desktop or server separately.

  • Technology Upgrades Notwithstanding any other provision of this Agreement, Verizon shall have the right to deploy, upgrade, migrate and maintain its network at its discretion. The Parties acknowledge that Verizon, at its election, may deploy fiber throughout its network and that such fiber deployment may inhibit or facilitate PNG’s ability to provide service using certain technologies. Nothing in this Agreement shall limit Verizon's ability to modify its network through the incorporation of new equipment or software or otherwise. PNG shall be solely responsible for the cost and activities associated with accommodating such changes in its own network.

  • Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:

  • Technical Specification As enumerated in Special Conditions of Contract/Scope of Work/attached Drawing/ Details/Schedule of Rates.

  • Software Upgrades Software Upgrades consist of new product releases which are issued periodically and may include new functionality, enhancements, and bug fixes. Software Upgrades are provided only for standard hardware platforms and operating systems supported by COMSPOC as described in the Documentation. Software Upgrades will apply only to unmodified Software and commercially released updated versions of the Software. You are responsible for making or arranging for updates to interfaces for nonstandard devices or custom applications. Software Upgrades are provided subject to the terms and conditions of the then current and applicable COMSPOC Software License Agreement, available on COMSPOC’s website at xxxx://xxx.xxxxxxx.xxx/sla or with the deliverable Software or upon request. All major product releases and maintenance releases will be made available and may be shipped directly to you, upon request by contacting your COMSPOC point of contact or xxxxxxx@xxxxxxx.xxx. You may upgrade to the latest product version at any time during the term of the Annual Support and Upgrades Agreement. If you opt not to renew the Annual Support and Upgrade Agreement, You have 60 days from the end of the Annual Support and Upgrades Agreement term to upgrade to the latest product version available prior to the end of the Annual Support and Upgrades Agreement term. If You request an upgrade beyond this 60-day period, You will be required to renew the Annual Support and Upgrades Agreement in order to upgrade to the latest product version.

  • Software Updates XXXXX agrees to keep current with software licensed from Skyward and will install new versions on a timeline approved by XXXXX governance. This timeline will be communicated by NWRDC to the Districts. School District Workstations Configuration requirements for devices and their software that school district personnel use to access WSIPC’s software modules can be found on our website: xxxxx://xxx.xxxxx.xxx/technology‐team/. State Reports XXXXX will provide, at no additional fee, all data reports required by the state that impact 50% or more of the school districts in the state. WSIPC and NWRDC will work with state agencies to gather requirements on the required data. WSIPC will inform NWRDC staff of any mandated changes to state reports and NWRDC will communicate the information to the District. Appendix B NWRDC FTE Fees Fiscal Only NWRDC Software Support Services XXXXX Software Licensing Total FTE Fee $13.63 $20.34 $33.97 $15.56 $13.08 $28.64 $24.52 $20.34 $44.86 Student Only Full Service

  • Interoperability To the extent required by applicable law, Cisco shall provide You with the interface information needed to achieve interoperability between the Software and another independently created program. Cisco will provide this interface information at Your written request after you pay Cisco’s licensing fees (if any). You will keep this information in strict confidence and strictly follow any applicable terms and conditions upon which Cisco makes such information available.

  • LAYOUT OF WORK The Contractor shall lay out its Work from base lines and benchmarks indicated on the Drawings, and shall be responsible for verification of all measurements in connection with the layout. The Contractor shall furnish all stakes, templates, platforms, equipment, tools, materials, and labor required to lay out any part of the Work. The Contractor shall also be responsible for maintaining and preserving all stakes and other marks established by Princeton University until authorized to remove them. If such marks are destroyed by the Contractor or through its negligence before their removal is authorized, Princeton University may replace them and deduct the expense of the replacement from any amounts due or to become due to the Contractor. CLAUSE C15 NOISE

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!