Best Practice Guidelines

Can someone provide the Cisco Link for the following:
1)How the network enforces parameter settings for each service category Voice and Data.
2)How the network prioritizes among the service categories during congestion?
3)How the network prioritizes among the service categories during link/switch failure?

What you're looking for is Quality of Service.
All your questions can be answered, that is if you are willing to plough through the documentation.
Cisco IOS Quality of Service Solution Configuration Guide, Release 12.4
http://www.cisco.com/univercd/cc/td/doc/product/software/ios124/124cg/hqos_c/index.htm
HTH
Leon
* Please rate posts if you find them helpful.

Similar Messages

  • Best Practice Guidelines to be protected from SPAMs

    Hi,
    Looking for a best practice guideline,inclusive filter rules.
    thanks,

    Best practices will vary widely according to your particular installation.
    Cisco IronPort has put together some guidelines that should be helpful, and posted them in the support portal.
    http://www.ironport.com/support/login.html
    If you login and search the KnowledgeBase for 'best practice', you'll be returned >60 documents regarding various portions of IronPort configuration.
    -whardison

  • Oracle Best Practices / Guidelines regarding Cleaning TEMP files

    Hi folks,
    Can any one help me with a set of steps / guidelines or best practices to clean TEMP files from OBIEE servers (our PROD environment)?
    Does perhaps OBIEE take care of this for you automatically, how is that process happening?
    Thanks a lot for your time and attention and hope to hear from you soon.

    TEMPS files are deleted from the server once a user logs out. But there might be chance where the TEMP files does not get deleted automaticlly, when the user logs out of the system even before the TEMP file has been generated completely. In this case the temp files get stored in the server, and a bounce of services cleans up the files.
    The best practice would be to create a script to empty out the temp directory during the start up of the services.
    -Amith.

  • SAP PI conceptual best practice for synchronous scenarios

    Hi,
    <br /><br />Apologies for the length of this post but I'm sure this is an area most of you have thought about in your journey with SAP PI.
    <br /><br />We have recently upgraded our SAP PI system from 7.0 to 7.1 and I'd like to document  best practice guidelines for our internal development team to follow.
    I'd be grateful for any feedback related to my thoughts below which may help to consolidate my knowledge to date.
    <br /><br />Prior to the upgrade we have implemented a number of synchronous and asynchronous scenarios using SAP PI as the hub at runtime using the Integration Directory configuration.
    No interfaces to date are exposes directly from our backend systems using transaction SOAMANAGER.
    <br /><br />Our asynchronous scenarios operate through the SAP PI hub at runtime which builds in resilience and harnesses the benefits of the queue-based approach.
    <br /><br />My queries relate to the implementation of synchronous scenarios where there is no mapping or routing requirement.  Perhaps it's best that I outline my experience/thoughts on the 3 options and summarise my queries/concerns that people may be able to advise upon afterwards.
    <br /><br />1) Use SAP PI Integration Directory.  I appreciate going through SAP PI at runtime is not necessary and adds latency to the process but the monitoring capability in transaction SXMB_MONI provide full access for audit purposes and we have implemented alerting running hourly so all process errors are raised and we handle accordingly.  In our SAP PI Production system we have a full record of sync messages recorded while these don't show in the backend system as we don't have propogation turned on.  When we first looked at this, the reduction in speed seemed to be outweighed by the quality of the monitoring/alerting given none of the processes are particularly intensive and don't require instant responses.  We have some inbound interfaces called by two sender systems so we have the overhead of maintaing the Integration Repository/Directory design/configuration twice for these systems but the nice thing is SXMB_MONI shows which system sent the message.  Extra work but seemingly for improved visibility of the process.  I'm not suggesting this is the correct long term approach but states where we are currently.
    <br /><br />2) Use the Advanced Adapter Engine.  I've heard mixed reviews about this functionaslity, there areh obvious improvements in speed by avoiding the ABAP stack on the SAP PI server at runtime, but some people have complained about the lack of SXMB_MONI support.  I don't know if this is still the case as we're at SAP PI 7.1 EHP1 but I plan to test and evaluate once Basis have set up the pre-requisite RFC etc. 
    <br /><br />3) Use the backend system's SOAP runtime and SOAMANAGER.  Using this option I can still model inbound interfaces in SAP PI but expose these using transaction SOAMANAGER in the backend ABAP system.  [I would have tested out the direct P2P connection option but our backend systems are still at Netweaver 7.0 and this option is not supported until 7.1 so that's out for now.]  The clear benefits of exposing the service directly from the backend system is obviously performance which in some of our planned processes would be desirable.  My understanding is that the logging/tracing options in SOAMANAGER have to be switched on while you investigate so there is no automatic recording of interface detail for retrospective review. 
    <br /><br />Queries:
    <br /><br />I have the feeling that there is no clear cut answer to which of the options you select from above but the decision should be based upon the requirements.
    <br /><br />I'm curious to understand SAPs intention with these options  -
    <br /><br />- For synchronous scenarios is it assumed that the client should always handle errors therefore the lack of monitoring should be less of a concern and option 3 desirable when no mapping/routing is required? 
    <br /><br />- Not only does option 3 offer the best performance, but the generated WSDL is ready once built for any further system to implement thereby offering the maximum benefit of SOA, therefore should we always use option 3 whenever possible?
    <br /><br />- Is it intended that the AAE runtime should be used when available but only for asynchronous scenarios or those requiring SAP PI functionality like mapping/routing otherwise customers should use option 3?  I accept there are some areas of functionality not yet supported with the AAE so that would be another factor.
    <br /><br />Thanks for any advice, it is much appreciated.
    <br /><br />Alan
    Edited by: Alan Cecchini on Aug 19, 2010 11:48 AM
    Edited by: Alan Cecchini on Aug 19, 2010 11:50 AM
    Edited by: Alan Cecchini on Aug 20, 2010 12:11 PM

    Hi Aaron,
    I was hoping for a better more concrete answer to my questions.
    I've had discussion with a number of experienced SAP developers and read many articles.
    There is no definitive paper that sets out the best approach here but I have gleaned the following key points:
    - Make interfaces asynchronous whenever possible to reduce system dependencies and improve the user experience (e.g. by eliminating wait times when they are not essential, such as by sending them an email with confirmation details rather than waiting for the server to respond)
    - It is the responsibility of the client to handle errors in synchronous scenarios hence monitoring lost through P-P services compared to the details information in transaction SXMB_MONI for PI services is not such a big issue.  You can always turn on monitoring in SOAMANAGER to trace errors if need be.
    - Choice of integration technique varies considerably by release level (for PI and Netweaver) so system landscape will be a significant factor.  For example, we have some systems on Netweaver 7.0 and other on 7.1.  As you need 7.1 for direction connection PI services we'd rather wait until all systems are at the higher level than have mixed usage in our landscape - it is already complex enough.
    - We've not tried the AAE option in a Production scenarios yet but this is only really important for high volume interfaces, something that is not a concern at the moment.  Obviously cumulative performance may be an issue in time so we plan to start looking at AAE soon.
    Hope these comments may be useful.
    Alan

  • Best Practice Guide for object management in Integration Builder

    Hi All,
    I'm looking for a best practice guideline, or a strategy pattern for the management and maintainable of Integration Builder objects.
    Is their such a document, or has someone experience with a huge amount of objects ( 200-300 interfaces) ?
    I was thinking about a folder to sub-folder strategy, but don't feel comfortable with that solution:
    -->Root folders ( business relationship e.g. "Customer", "Supplier", "Bank" etc.)
    >Sub folders ( e.g. "AB Customer", "ZX Supplier", etc)
    Regards
    Oleg

    Hi ,
      I am in the safe confusion one year back, we developed 200 interfaces in XI3.0 ,every interfaces has minimum 10 mapping programs,its difficult manage the alla scenarios ,
    That what i created Software components for as per region like SA(South America), North Americ , Europe, Asia Pacific,we developed interafces for above regions,that why  created software compinehts like that.
    Then i created name spaces inside outbound and inboud to easy to diffentiate ..like that i had done.
    If you are with PI7.1 betetr to go for Folders,create folders and move objects.
    my answer not satisfies you..pls dont mind..:)
    Reagards,
    Raj

  • Best practice for identifying BPEL process boundary

    Hi
    Want to know if there is any best practices / guidelines available to identify how many BPEL processes are required.. I assume once we do a process decomposition we might arrive at an abstract business process boundary.
    However, I also think those processes can be further broken down while actually implementing them using BPEL PM?
    Is there any guidelines that I can use or follow to specify how many BPEL process to define
    Thanks
    Prashanth Rao

    Hi Kumar,
    In order to have Consigment in SAP u need to have master data such as material master, vendor master and purchase inforecord of consignment type. U have to enter the item category k when u enter PO. The goods receipt post in vendor consignment stock will be non valuated.
    1. The intial steps starts with raising purchase order for the consignment item
    2. The vendor recieves the purchase order.
    3. GR happens for the consignment material.
    4. Stocks are recieved and placed under consignment stock.
    5. When ever we issue to prodn or if we transfer post(using mov 411) from consignment to own stock then liability occurs.
    6. Finally comes the settlement using mrko. You settle the amount for the goods which was consumed during a specific period.
    regards
    Anand.C

  • Best Practice for ACS 5.2 Policy

    Hi All,
    I am wondering if there is some sort of best practice guideline to implement ACS? I mean like how we are going to group device, or how the "if then" policy should be structured. Please help..
    Regards,

    Prima,
    The ACS is entirely flexible in the way you to choose to implement it and it is based on your network specificiations. Some networks have site specific Administrators in which they will choose to implement their tacacs policies to permit access to devices in their regions, so they choose to assign a location to a network device.
    Some customers have restrictions in which Adminstrators have access to which devices...so when you choose to group devices based on routers, switches, firewalls, or SAN devices you can choose to implement your policies as such.
    Moving to the user side, some customers have a tiered structure in access levels, contractors, network-operators, admins and superadmins, so you can create policies and shell profiles to grant access to devices based on the user along with which group they are trying to access and finally what commands they are allowed to run.
    Based on your scenario above i assumed TACACS, you can choose to implement radius in the same fashion but more customers base this off of what users are allowed to have certain access...guests (internet only), management (vpn access with higher privs)....etc.
    Thanks,
    Tarik Admani

  • Best Practice Directory Structure

    I'm new to programming and I'm creating a large application
    that will have a lot of pages and components. As I continue to add
    to the project, I find it harder and harder to easily locate the
    pages and components that I need to work with. To help me with this
    problem, I've decided to add a label to every component with the
    location of where it can be found. Now when I view the application
    and I see a component I want to work with, I know where it is
    located.
    This is problably not the best way to handle the problem, it
    will be a pain to go back and remove or comment out these when I'm
    fininshed with the project, but it wil help now.
    Short of having a better memory :>), is there any best
    practice guidelines I should look into and follow when I create my
    directory structure of files and components that will intuitively
    help me quickly locate a component? What do you use to help you?
    Thanks for your ideas and suggestions

    There are many ways to answer this. If you have a big project
    you might consider using a Flex Library Project for your components
    - think of it as writing a set of components you (or your company)
    might one day sell to others - even if you never have that intent.
    The idea is to make the components as reusable as possible in case
    you need them for the next project. Having them in a separate Flex
    Library project (which creates a .swc file) would make that easier.
    The industry best-practice seems to be to create packages
    that begin with your company's domain name, but in reverse order.
    For example, components I write for Adobe go into a package
    beginning with com.adobe which works out to be the file structure
    com/adobe and then is further divided by the application and then
    its parts (eg, com.adobe.scrapbook.editor). Using your company's
    domain to distinguish your components enables you and others to
    combine components from different places without naming conflicts.
    If you divide your application into logical parts you can
    figure out a good package naming convention that is easier to
    remember. For example, I might put all of the skins for my
    Scrapbook Editor into the com.adobe.scrapbook.editor.skins package.
    I can easily find those files and add to them as necessary.
    Other people follow a similar pattern and there are books on
    the subject, too.

  • Best Practice AV set up on SAP Servers

    Hi,
    Has anyone come across or aware of any best practice guidelines for AV setup on SAP servers, for example, which files/drives should you exclude and configuration tuning/reg-edits required. We have McAfee as our standard AV and we do use the HIPS component.
    Thanks,
    Martin

    My best advise is:
    Don't run AV on a database server but rather reconfigure the local/a firewall so that only those ports are open which are necessary to run the SAP application.
    Excluding files may help a bit but neverless, as soon as the AV scanner is installed it will hook up to the filesystem layer and slowing down (maybe not significantly) I/O. I've seen weird side effects in upgrades and patch installations due to an enabled scanner although the database files and executables were excluded from scanning.
    If you're urged to run Windows servers then I would put them in a separate network segment with a firewall in front and enable only the necessary SAP ports (and printing ports). This has a number of advantages:
    - nasty RPC bugs can't be exploited because RPC to the SAP system should be disabled
    - there's no need to reboot the Windows machines on every "Microsoft patch day"
    A virus scanner adds, especially for production database systems, an indeterministic risc to the business.
    Markus

  • WDA Best Practice for Coding

    Hi
    Are there any best practice guidelines for WDA?
    I have seen the naming conventions in the official book which I use but are there any actual coding standards such as whether to use the global controller to hold methods and then call these from the relevant onaction methods.
    i.e.
    METHOD onactionsave .
      lv_subrc = wd_comp_controller->check_input( ).
      check lv_subrc = 0.
      wd_comp_controller->save( ).
    ENDMETHOD.
    Just wondered...
    Also data declarations were traditionally done at the top of a method.  Is this still the case in WDA or is it more normal to declare variables etc as they are required - like in Java?
    Cheers
    Ian

    Hi Ian,
    There will be some guidelines in the new documentation, which is currently not yet available.
    Here some very short tipps:
    - Use an assistance class for each component, which should hold the current data and where you can place central methods. Placing methods in external classes is better than putting them into the component controller, because there is less overhead and more functionality (e.g. optional parameters and exceptions).
    - Hold your current data in the assistance class and only put them into the context if needed (e.g. via supply functions).
    - Call your business logic from the assistance class during event handling. Then you have the opportunity to do navigation or not depending on the output of the business logic.
    - You could use any other class for this purpose, but the assistance class is easier, because it is instantiated by the framework and you can access it via wd_assist-> instead of wd_this->my_class-> .
    - Do not create a model component, because this is just overhead and no advantage. In earlier states of the WD project, we thought, a model component would be a good idea, but we changed our minds
    - Use context mapping, where it is needed, e.g. if you use the same context in different views.
    - It is quite well to call the assistance class from the views.
    - Be careful, if you store any references to component parts in your assistance class. Some references may change during runtime, especially those of context nodes placed in a deep hierarchy.
    Hope this helps, and more tipps will follow in the documentation or weblogs.
    Ciao,  Regina

  • Best practice for deploying the license server

    Was wondering if there is a best practice guideline or a rule of thumb out there for deploying the license server. For instance, is it better to have one license server and all your products connect to that, dev, QA, prod. Or is it better to have a license server for each deployment, i.e. one for dev one for QA.. etc.

    Was wondering if there is a best practice guideline or a rule of thumb out there for deploying the license server. For instance, is it better to have one license server and all your products connect to that, dev, QA, prod. Or is it better to have a license server for each deployment, i.e. one for dev one for QA.. etc.

  • Large ADF Applications - Best Practice

    Hi
    We have a single ADF project (one model, one view/controller) with the following model components:
    68 AMs
    387 VOs
    175 EOs
    This project is ever expanding, and we are suffering some well-known performance problems when open JDeveloper or open the view/controller project.
    Are there any best-practice guidelines on how to structure your ADF projects?
    e.g. what is the maximum recommended number of AMs/VOs/EOs in a single project?
    We have kept everything in a single project after some advice from Oracle to help us to re-use common modules easily.
    We use JDeveloper v10.1.3 and use JHeadstart v10.1.3 SU 1 to generate our view/controller layer, using multiple faces-config files.
    Thanks
    Denis

    Hi Denis,
    We have exactly the same problem in expanding our application but we have a single AM and less EOs, VOs than you right now. There are some threads discussing this issue but I haven't found a complete and standard solution yet. The only thing I know is that almost every thing can be segmented in ADF like projects, application module, faces-config.xml, ...
    Another thing which is very important is that segmenting an application is a tradeoff, it has some advantaes but problems in SCM, security, ...
    S/\EE|)

  • CE Benchmark/Performance Best Practice Tips

    We are in the early stages of starting a CE project where we expect a high volume of web service calls per day (e.g. customer master service, material master service, pricing service, order creation service etc).
    Are there any best-practice guidelines which could be taken into account to avoid any possible performance problems within the web service u201Cinfrastructureu201D? 
    Should master data normally residing in the backend ECC server be duplicated outside ECC? 
    e.g. if individual reads of the master data in the backend system take 2 seconds per call, would it be more efficient to duplicate     the master data on the SAP AS Java server, or elsewhere u2013 if the master data is expected to be read thousands of times each    day.
    Also, what kind of benchmarking tools (SAP std or 3rd party) are available to assess the performance of the different layers of the infrastructure during integration + volume testing phases?
    I've tried looking for any such documentation on SDN, OSS, help.sap.com, but to no avail.
    Many thanks in advance for any help.
    Ali Crawshaw

    Hi Ali,
    For performance and benchmarking have you had a look at Wiley Introscope?
    The following presentation has some interesting information [Wiley Introscope supports CE 7.1|http://www.google.co.za/url?sa=t&source=web&ct=res&cd=7&ved=0CCEQFjAG&url=http%3A%2F%2Fwww.thenewreality.be%2Fpresentations%2Fpdf%2FDay2Track6%2F265CTAC.pdf&ei=BUGES-yyBNWJ4QaN7KzXAQ&usg=AFQjCNE9qA310z2KKSMk4d42oyjuXJ_TfA&sig2=VD1iQvCUmWZMB5OB-Z4gEQ]
    With regards to best practice guidelines, if you are using PI for service routing try to keep to asynch services as far as possible, asynch with acknowledgments if need be. Make sure your CE Java AS is well tuned according to the SAP best practice.
    Will you be using SAP Global Data Types for your service development? If you are then the one performance tip i have regarding the use of GDT's is to keep your GDT structures as small (number of fields) as possible, as large GDT structures have an impact on memory consumption at runtime.
    Cheers
    Phillip

  • ICM Trace Log best practices?

    Hello,
    Partner is asking if we have best practice guidelines/documentation for setting Trace Log file sizes on ICM 7.2.X
    thanks!

    Actually we did open a TAC. Cisco was not able to make a recommendation because the issue is intermittent and we cannot leave tracing on indefinitely. Because of this they instead recommended installing a packet sniffer. However our network support team came back with a similar response - cannot leave packet sniffing turned on indefinitely.
    This is a difficult situation in which we cannot reproduce the issue, we don't know when it will happen again. And we cannot take any proactive action to ensure that we capture the logs on the next occurrence.
    So, has anyone else been through something like this?
    Thanks!
    Joe

  • What is the guideline and/or best practice for EMC setup on ASM?

    We are going to use EMC CX4-480 for ASM storage on RAC. What is the guideline and best practice for EMC setup on ASM?
    Thanks for the advice!

    Probably a poor choice of words. Sorry.
    So basically, I have gotten further, but I just noticed related problem.
    I'm using the WebServices(WS) 1.0. I insert an account, then, on a separate WS call, I insert my contacts for the account. I include the AccountID, and a user defined key from the Account when creating the Contact.
    When I look at my Contact on the CRMOD web page, it shows the appropriate links back to the Account. But when I look at my Account on the CRMOD web page, it shows no Contacts.
    So when I say workflow or Best Practice, I was hoping for guidance on how to properly write my code to accomplish all of the necessary steps. As in this is how you insert an account with a contact(s) and it updates the appropriate IDs so that it shows up properly on the CRMOD web pages.
    Based on the above, it looks like I need to, as the next step, take the ContactID and update the Account with it so that their is a bi-directional link.
    I'm thinking there is a better way in doing this.
    Here is my psuedocode:
    AccountInsert()
    AccountID = NewAcctRec
    ContactInsert(NewAcctRec)
    ContactID = NewContRec
    AccountUpdate(NewContRec)
    Thanks,

Maybe you are looking for