No matter how sophisticated the technology is , It still takes people !
Subscribe to this blog
Follow by Email
What is an SNTP?
The Simple Network Time Protocol (SNTP) is a simpler version of the Network Time Protocol (NTP). SNTP synchronizes the time between networked computer systems and is relied on when data is being transferred via the Internet. The NTP protocol is one of the most established protocols still used on the Internet. It uses a GPS or radio clock to tell time and is accurate past the seconds place.
Why is the SNTP Necessary?
The need for precise time synchronization has continued to increase with the evolution of computer technology over the past several decades. In the networking field, network servers and their client computers require precision to the millisecond and beyond in order to ensure data file transfers occur without errors. Computers also require specific time synchronization in order to ensure data packet and email delivery in the proper sequence to destination networks and email recipients. The importance of the SNTP and NTP protocols exponentially expands with the number of computers that are on a network in order to prioritize network traffic appropriately. Computers that Use the SNTP Protocol
Servers are the primary SNTP protocol users. Servers use the protocol in order to keep the time on network services and client computers synchronized based on Internet standards. Web servers that put a heavy demand on traffic may have to switch to the NTP for time service requirements. However, the SNTP protocol is suitable for providing the time for all services and client computers on small to medium networks. What are the Security Implications of the SNTP Protocol?
The SNTP protocol’s data is subject to packet sniffing since it is plain text that is transmitted over a local network and the Internet without encryption. It may also be susceptible to a dictionary or brute force attack in order to guess the authentication and encryption keys and strings. The protocol also uses the UDP communications protocol, which may be open to IP spoofing attacks.
First, we will install the AD LDS Instance: 1. Create and AD LDS instance by clicking Start -> Administrative Tools -> Active Directory Lightweight Directory Services Setup Wizard. The Setup Wizard appears. 2. Click Next . The Setup Options dialog box appears. For the sake of this guide, a unique instance will be the primary focus. I will have a separate post regarding AD LDS replication at some point in the near future. 3. Select A unique instance . 4. Click Next and the Instance Name dialog box appears. The instance name will help you identify and differentiate it from other instances that you may have installed on the same end point. The instance name will be listed in the data directory for the instance as well as in the Add or Remove Programs snap-in. 5. Enter a unique instance name, for example IDG. 6. Click Next to display the Ports configuration dialog box. 7. Leave ports at their default values unless you have conflicts with the default values. 8. Click N
Steps to configure the vCenter Server to generate SNMP traps: A.In the Home page of vSphere Client B.Select vCenter Server Settings C.Select SNMP configuration D.Enable one of the SNMP receivers E. Provide the details for : Receiver URL : Provide the host name of the Management Server (target SNMP server / monitoring tool) which will be connected to the VMware vCenter Server. (VMware vCenter Server sends the SNMP traps to this Management Server) Configure port 162 as the SNMP port. Community String: Provide community string (default string is "public") SNMP versions v1/v2/v3 are supported That is all that is needed for the configuration. Now you need to configure alarm for generating SNMP traps in the vCenter server. When ever there is a change in the environment ( host state change, VM state change ,etc) the trigger will be generated and send an alert to the monitoring server. Configure the Alarms After you have setup the external SNMP server, v
What is an Inventory? An Inventory is the process of mounting media in the drive and reading the media label, which is then displayed in the Devices view. If this is the first time that Backup Exec ™ has encountered this media, the media label is also added to the Media view. Note : Each time new tape is introduced in the tape drive or robotic library, it must be inventoried so that the Backup Exec database gets updated with the new tape Information. To Inventory a Tape/Robotic Library: 1. Insert the tape 2. Click the Devices tab 3. Select the correct tape drive/robotic library slot 4. Right-click on the tape drive/robotic library slot and select Inventory (Figure 1) Figure 1 The inventory will complete and should display the correct tape name. What is a Catalog? When cataloging a tape, Backup Exec reads the header information from the tape and stores it in a file on the hard drive. The information contained in the catalog includes, but is not limited