Acl's properties

ACL'S 

An ACL is an ordered set of rules for filtering traffic. When the device determines that an ACL applies to a packet, it tests the packet against the rules. The first matching rule determines whether the packet is permitted or denied. If there is no match, the device applies a default rule. The device processes packets that are permitted and drops packets that are denied.

ACLs protect networks and specific hosts from unnecessary or unwanted traffic. For example, ACLs are used to disallow HTTP traffic from a high-security network to the Internet. ACLs also allow HTTP traffic but only to specific sites, using the IP address of the site to identify it in an IP ACL.

The following types of ACLs are supported for filtering traffic:

•IP ACLs—The device applies IP ACLs only to IP traffic.

•MAC ACLs—The device applies MAC ACLs only to non-IP traffic.

For detailed information about how rules are used to configure how an ACL configures network traffic, see the Cisco Nexus 1000V Security Configuration Guide, Release 4.0(4)SV1(1).

ACL Configuration Limits

The following configuration limits apply to ACLs:

•You cannot have more that 128 rules in an ACL.

•You cannot have more than 10,000 ACLs (spread across all the ACLs) in one VEM.

ACL Restrictions

The following restrictions apply to ACLs:

•You cannot apply more than one IP ACL and one MAC ACL in each direction on an interface.

•A MAC ACL applies only to Layer 2 packets.

•VLAN ACLs are not supported.

•IP fragments are not supported n ACL rules.

•Non initial fragments are not subject to ACL lookup.

•The established option to specify TCP flags is not supported.

•You cannot have two not-equal-to (neq) operators in the same rule.

Troubleshooting ACLs

The commands listed in this section can be used on the VSM to see the policies that are configured and applied on the interfaces.

Use the following command to display configured ACLs:

•show access-list summary

Use following commands on the VSM to see run-time information of the ACLMGR and ACLCOMP during configuration errors, and to collect ACLMGR process run-time information configuration errors:

•show system internal aclmgr event-history errors

•show system internal aclmgr event-history msgs

•show system internal aclmgr ppf

•show system internal aclmgr mem-stats (to debug memory usage and leaks)

•show system internal aclmgr status

•show system internal aclmgr dictionary

Use the following commands to collect ACLCOMP process run-time information configuration errors:

•show system internal aclcomp event-history errors

•show system internal aclcomp event-history msgs

•show system internal aclcomp pdl detailed

•show system internal aclcomp mem-stats (to debug memory usage and leaks)

Displaying ACL Policies on the VEM

The commands listed in this section can be used to display configured ACL policies on the VEM.

Use the following command to list the ACLs installed on that server

 ~ # module vem 3 execute vemcmd show acl 

 Acl-id Ref-cnt  Type Numrules  Stats

     1      1    IPv4      1    disabled

The Acl-id is the local ACLID for this VEM. Ref-cnt refers to the number of instances of this ACL in this VEM.

Use the following command to list the interfaces on which ACLs have been installed

 ~ # module vem 3 execute vemcmd show acl pinst 

 LTL   Acl-id    Dir

  16       1    ingress

Debugging Policy Verification Issues

To debug a policy verification failure, follow these steps:

Step 1 On the VSM, enter the debug logfile filename command to redirect the output to a file in bootflash.

Step 2 Enter the debug aclmgr all command.

Step 3 Enter the debug aclcomp all command.

For the VEMs where the policy exists, or is being applied, enter the following these steps from the VSM. The output goes to the console.

Step 4 Enter the module vem module-number execute vemdpalog debug sfaclagent all command.

Step 5 Enter the module vem module-number execute vemdpalog debug sfpdlagent all command.

Step 6 Enter the module vem module-number execute vemlog debug sfacl all command.

Step 7 Enter the module vem module-number execute vemlog start command.

Step 8 Enter the module vem module-number execute vemlog start command.

Step 9 Configure the policy that was causing the verify error.

Step 10 Enter the module vem module-number execute vemdpalog show all command.

Step 11 Enter module vem module-number execute vemlog show all command.

for more visit us : http://www.svtrainings.com/servicenow-training-online

UI properties

UI properties

The Properties attribute of a UI allows you to parameterize a UI with properties, each of which consists of a type, a name, and a default value, thus allowing you to customize the UI. A property can be any MCML or user-defined type. Property default values are shared among all instances of the UI. These values are public and can be overridden. In the following example, the Properties attribute defines default values for the Color and Font attributes of a Text element:
  <UI Name="UsingProperties">
    <Properties>
      <Color Name="Foreground" Color="Blue" />
      <Font Name="DocFont" Font="Verdana,22" />
    </Properties>

    <Content>
      <Text Content="Using Font and Color properties" Font="[DocFont]" Color="[Foreground]" />
    </Content>
  </UI>

You can require the parent UI to supply a value for any property by marking it as "$Required", and an error will occur if that property is not specified. The following example requires the parent UI to define a Label string:
  <UI Name="MainDisplay" BaseUI="me:LabelProperties">
    <Content>
        <me:LabelProperties Label="A Label string is required." />
    </Content>
  </UI>

  <UI Name="LabelProperties">
    <Properties>
      <cor:String Name="Label" String="$Required" />
      <Color Name="ForeColor" Color="Red" />
    </Properties>

    <Content>
      <Text Name="Display" Content="[Label]" Color="[ForeColor]" Font="Arial,20" />
    </Content>
  </UI>

for more visit us : http://www.svtrainings.com/servicenow-training-online

SMTP

SMTP

SMTP (Simple Mail Transfer Protocol) is a TCP/IP protocol used in sending and receiving e-mail. However, since it is limited in its ability to queue messages at the receiving end, it is usually used with one of two other protocols, POP3 or IMAP, that let the user save messages in a server mailbox and download them periodically from the server. In other words, users typically use a program that uses SMTP for sending e-mail and either POP3 or IMAP for receiving e-mail. On Unix-based systems, sendmail is the most widely-used SMTP server for e-mail. A commercial package, Sendmail, includes a POP3 server. Microsoft Exchange includes an SMTP server and can also be set up to include POP3 support.
for more visit us : http://www.svtrainings.com/servicenow-training-online

ITIL FOUNDATION

ITIL FOUNDATION

The Foundation level is the entry level qualification which offers you a general awareness of the key elements, concepts and terminology used in the ITIL service lifecycle, including the links between lifecycle stages, the processes used and their contribution to service management practices.

After passing the ITIL Foundation training and examination, you can expect to gain a general overview and basic understanding of ITIL.

If you want to progress to the next level within the ITIL qualifications scheme, the ITIL Intermediate level, you need to have first passed the ITIL Foundation qualification.

This qualification is primarily aimed at:

Those who require a basic understanding of the ITIL framework
Those who need understanding of how ITIL can be used to enhance IT service management within an organization
IT professionals or others working within an organization that has adopted and adapted ITIL and who need to be informed about, or contribute to, ongoing service improvement.
However, the ITIL Foundation level qualification is open to and can benefit anyone who has an interest in the subject.

Holders of an ITIL Foundation level qualification are likely to require further guidance before being able to apply the ITIL practices for Service Management to professional projects or situations.

for more visit us : http://www.svtrainings.com/servicenow-training-online

SOAP messages

SOAP MESSAGES 

A SOAP message is an ordinary XML document containing the following elements -

Envelope - Defines the start and the end of the message. It is a mandatory element.

Header - Contains any optional attributes of the message used in processing the message, either at an intermediary point or at the ultimate end-point. It is an optional element.

Body - Contains the XML data comprising the message being sent. It is a mandatory element.

Fault - An optional Fault element that provides information about errors that occur while processing the message.

All these elements are declared in the default namespace for the SOAP envelope -

for more   visit us : http://www.svtrainings.com/servicenow-training-online

servicenow provides web development courses:

HTML stands for Hyper Text Markup Language, which is the most widely used language on Web to develop web pages.

HTML was created by Berners-Lee in late 1991 but "HTML 2.0" was the first standard HTML specification which was published in 1995. HTML 4.01 was a major version of HTML and it was published in late 1999. Though HTML 4.01 version is widely used but currently we are having HTML-5 version which is an extension to HTML 4.01, and this version was published in 2012.

Audience

This tutorial is designed for the aspiring Web Designers and Developers with a need to understand the HTML in enough detail along with its simple overview, and practical examples. This tutorial will give you enough ingredients to start with HTML from where you can take yourself at higher level of expertise.

Prerequisites

Before proceeding with this tutorial you should have a basic working knowledge with Windows or Linux operating system, additionally you must be familiar with:

Experience with any text editor like notepad, notepad++, or Editplus etc.

How to create directories and files on your computer.

How to navigate through different directories.

How to type content in a file and save them on a computer.

Understanding about images in different formats like JPEG, PNG format.........................

for more information ..visit  us:

http://www.svtrainings.com/servicenow-training-online

videos on html

https://www.youtube.com/watch?v=h-43aVyBYmo

Customization scripts

Double-clicking the script icon allows opening the script editor. You can change properties of a given script, or associate it with another object via the script dialog. You can attach a new customization script to an object by selecting the object, then navigating to [menu bar --> Add --> Associated customization script].

Following are customization script's main properties:

they run non-threaded.

they are executed all the time: when simulation is running, as well as when simulation is not running.

they are attached to (or associated with) scene objects (i.e. they are associated scripts). Associated scripts form the basis of V-REP's distributed control architecture, and share the convenient property to be automatically duplicated if their associated object is duplicated.

Above properties allow customization scripts to share some of the best features of add-ons and child scripts. Customization scripts allow the creation of customizable models for instance: imagine a model that was dropped into a scene, and that is able to configure or adapt itself, even when simulation is not running. This could be a robot where the user can adjust the various link lengths with a single slider repositioning.

Customization scripts are pass-through scripts. This means that every time they are called, they should perform some task and then return control. If control is not returned, then the whole simulator will hang. Customization scripts operate as functions, and are called by the simulator very often, so as to be able to react to various simulator state changes.

A customization script should be segmented in several parts, as following skeleton script illustrates:

if (sim_call_type==sim_customizationscriptcall_initialization) then
 -- this is called just after this script was created (or reinitialized)
 -- Do some initialization here
 
 -- By default we disable customization script execution during simulation, in order
 -- to run simulations faster:
 simSetScriptAttribute(sim_handle_self,
        sim_customizationscriptattribute_activeduringsimulation,false)
end

if (sim_call_type==sim_customizationscriptcall_nonsimulation) then
 -- This is called on a regular basis when simulation is not running.
 -- This is where you would typically write the main code of
 -- a customization script
end

if (sim_call_type==sim_customizationscriptcall_lastbeforesimulation) then
 -- This is called just before a simulation starts
end

if (sim_call_type==sim_customizationscriptcall_simulationactuation) then
 -- This is called by default from the main script, in the "actuation" phase.
 -- but only if you have previously not disabled this script to be active during
 -- simulation (see the script's initialization code above)
end

if (sim_call_type==sim_customizationscriptcall_simulationsensing) then
 -- This is called by default from the main script, in the "sensing" phase,
 -- but only if you have previously not disabled this script to be active during
 -- simulation (see the script's initialization code above)
end

if (sim_call_type==sim_customizationscriptcall_simulationpausefirst) then
 -- This is called just after entering simulation pause
end

if (sim_call_type==sim_customizationscriptcall_simulationpause) then
 -- This is called on a regular basis when simulation is paused
end

if (sim_call_type==sim_customizationscriptcall_simulationpauselast) then
 -- This is called just before leaving simulation pause
end

if (sim_call_type==sim_customizationscriptcall_firstaftersimulation) then
 -- This is called just after a simulation ended
end

if (sim_call_type==sim_customizationscriptcall_cleanup) then
 -- this is called just before this script gets destroyed (or reinitialized) 
 -- Do some clean-up here
end

CSS properties

CSS Property Groups 

• Animation
• Background
• Border and outline
• Box
• Color
• Content Paged Media
• Print
• Ruby
• Speech
• Table
• Text
• 2D/3D Transform
• Transition
• User-interface

Animation Properties Property Description Ver. @keyframes Specifies the animation 3 animation A shorthand property for all the animation properties below, except the animation-play-state property 3 animation-name Specifies a name for the @keyframes animation 3 animation-duration Specifies how many seconds or milliseconds an animation takes to complete one cycle 3 animation-timing-function Specifies the speed curve of the animation 3 animation-delay Specifies when the animation will start 3 animation-iteration-count Specifies the number of times an animation should be played 3 animation-direction Specifies whether or not the animation should play in reverse on alternate cycles 3 animation-play-state Specifies whether the animation is running or paused...........................

  for more information  visit our site :  http://www.svtrainings.com/servicenow-training-online