JUNOS Configuration Clause Samples

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 { ▇▇▇.▇▇▇.▇▇▇.▇▇▇; 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‐groups allows SNMP traps to be se...
View Source

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.

  • AIRCRAFT CONFIGURATION The guarantees defined below ("the Guarantees") are applicable to the A330-200 Aircraft as described in the Technical Specification ***, as amended by the Specification Change Notices ("SCN's") for:

  • 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.

  • 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 Covista’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. Covista shall be solely responsible for the cost and activities associated with accommodating such changes in its own network.

  • Customization The listed products are licensed for Customer Manager Suite use and customization only. Use of these tools to develop or customize non-Customer Manager Suite applications is not permitted without the express written authorization of PFPC.