Home

ITIL 4 Overview

Leave a comment

In a nutshell… ITIL 4 is an overhaul to ITILv3, a lot of modification here and there, more holistic method…all-rounder framework

A lot of good additional material for IT Service Management (ITSM) in this ITIL4, Let’s overview it one by one (im writing it in English, but some in Bahasa…why? Ya suka suka gue lah…wkkwkw)

First…
ITIL4 (or ITIL 4, with space)

Notice it’s not ITILv4…but ITIL 4, its for ITIL for Industry 4.0

And it seems to left behind its abbreviation (IT Infra. Library), now just ITIL4 with no abbr.

Secondthe 4 Dimensions of Service Management, the four different views about ITSM

The new ITIL of the four P’s (people, partner, product, process)

  1. Organization and People

    Talk about how we can form some sort of function/team with required skillsets to achieve its (organization) objectives

  2. Information and Technology

    The Information is the today world currency, and how to properly utilize it with the right tools (Technology) and Skills (People)

  3. Partners and Suppliers

    Differencing Partner (take-and-give method, MoU, kerjasama seperti Microsoft dan Cisco) and Supplier (One-way method, seperti Enterprises/Perusahaan dengan Vendor)

  4. Value Streams and Processes

    The organization must improvise and adapt to ever changing business challenges and circumstances, they must define the steps that the organization takes to create and deliver product (the Value Stream), and to make that we must take input and transform that into output via process (banyak company yang “telat” menyadari perubahan2 bisnis sehingga harus gulung tikar… perusahaan Taksi yang punya ribuan armada bisa kalah sama perusahaan aplikasi yang ga punya armada sama sekali, di perusahaan online bahkan armada2 tersebut bukan lagi sebagai bawahan/karyawan, but treated as a PARTNER)

  5. annndd THE EXTERNAL FACTORS (PESTEL – political, economic, social, technology, environment, and legal)

    Remember…these external factors can CHANGE the GAME

Third…
Service Value System (SVS), the core material in ITIL4 after the 4 Dimensions of Service Management, how we create value

Guiding Principles, Governance, Service Value Chain, Practices, even Continual Improvement has their own sub-chapter in ITIL 4 Foundation material

Note: many of Service Lifecycle processes in ITILv3 now put into ITIL4 Practices

What missing in ITILv3 is customer involvement

In ITIL4…BOTH Service Provider and Service Consumer must co-create the value, not just the Service Provider

For example, when Application Developer develop an Application that very intuitive design, highly secure, stable process, and (add anything else here…) but…

…If user can’t or won’t use the apps, then it useless…READ: no value

So ITIL 4 stress about how we as service provider and user as service consumer can collaborate, what’s good and what’s not, and then consumer use the product to service its own user/consumer (service relationship)

Example: TELKOM punya consumen Bank Mandiri yang punya konsumen PT. ABC yang punya konsumen PT. XYZ…and so on (each service indirectly affects other, so value is the real concern)

So, ITIL4 focus on OUTCOME, not just the OUTPUT

OUTCOME = result for stakeholder, enabled by one or more outputs, focused on customers DESIRED OUTCOME (not our Desired Outcome as SP)

The difference?

OUTPUT can be report, bill, email , etc…that CAN BE MEASURED

But OUTCOME (often) can’t be measured…it’s the experience itself

Example? OUTPUT = this article, I write this ITIL4 overview to myself and hopefully others to learn and remember

OUTCOME = apply, me and other can implement this ITIL4 concept (not just see, hear, and nods…masuk kuping kiri keluar kuping kanan)

Contoh “kita ngasi deliverables, seperti training, buku, customer support sebagai output…tapi dipake ga? berguna ga? apa training ini cuma dibuat untuk ngabisin duit aja? Ga ada outcome”

Fourththe 7 Guiding Principles

The guiding principles embody the core messages of ITIL and ITSM in general…which is universally applicable to all IT Disciplines

This one though…created to address Agile and DevOps problem that ITILv3 lack of, which is the programmer world that lacks and need the ITSM disciplines the most

Nine? You said Seven?? (for ITIL Foundation, you just have to remember the first 7, ITIL practitioner add two more to the table)

  1. Focus on Value (self-explanatory)
  2. Start Where You Are (jangan bikin baru klo yang lama masi bisa kita improve)
  3. Progress iteratively with feedback (simple…don’t try to be superman, selesain satu2, utilize the feedback)
  4. Collaborate and promote visibility (kolaborasi dan kedua belah pihak sama2 tahu apa yang dikerjakan… service provider yang berkolaborasi dengan service consumer will create powerful value)
  5. Think and Work holistically (biasakan berfikir menyeluruh, jgn berfikir untuk tim kita…but for the organization, mungkin solusi itu bagus buat kita, tapi jelek buat perusahaan secara menyeluruh)
  6. Keep it simple and practical (klo bisa di permudah ya jangan di persulit…iya toh?!?)
  7. Optimize and Automate (apapun yang bisa kita bikin simple klo lo bisa di otomatisasikan dan optimasi, segala sesuatu yang repetitive klo bisa di otomatisasikan)
  8. Observe Directly (klo denger dari orang lain…katanya katanya, biasanya ga akurat, lo harus liat secara langsung)
  9. Be Transparent (self-explanatory)

8 and 9 not necessary for ITIL4 Foundation (but worth mentioning for)

Fifth…
The Practices

The ITILv3 Service Lifecycle Processes now taken into concept called Practices

Practice can be viewed as CAPABILITY…Your…Organization…Capability

So, in order to create some value to your services there is 3 main practices

General Management Practices (4 out of 14 practices that important for ITIL 4 Foundation Exam)

  • These practices have been adopted and adapted for service management from GENERAL BUSINESS MANAGEMENT DOMAIN

Service Management Practices (6 out of 17 practices that important for ITIL 4 Foundation Exam)

  • Lots of these practices can be found in ITILv3 Service Lifecycle (so if you have experience in ITILv3, you’ll do good in here)

Technical Management Practices (3 practices)

  • These practices is the domain of your best friend colleagues at work…the engineers who deal with technology all the time

We will cover all the practices later (if I have time)

Sixth…
Service Value Chain

So, you want to create value for your services? You have the ability and capability? Then consider these 6 activities, because all your practices above will be directly and indirectly affected one or more Service Value Chain activities below

  1. Plan: activity that create plans, portfolios, policies…to ensure a shared understanding of what we or the organization trying to achieve and how this will be done
  2. Improve: activity that ensure continual improvement of all products, services, and practices across all 4 Dimensions of Service Management
  3. Engage: activity that engage with stakeholders and understanding their needs
  4. Design and Transition: activity that create new and changed services (lu butuh fase transisi ketika mau implement major change of services, biar ga fail pas GO-LIVE) and ensure it will meet stakeholder expectations for quality, cost, and time to market (in ITILv3 this topic reside in Change Management process)
  5. Obtain/Build: activity that create service components (beli sesuatu apa yang bisa bikin service jalan…atau bikin), ensure they are available when and where they are needed (and meet the agreed specification…SLA)…intinya, lu butuhnya apa biar service kita jalan…entah beli, bikin, atau ngambil punya orang *maling!!*(yg ini abaikan)
  6. Deliver and Support: activity that…ensure delivery and “after sales” activity…layanan purna jual

Seventh…
Continual Improvement

This is…the CSI (continual service improvement of ITILv3) for ITIL 4

References

ITIL 4 Foundation ebook

IPv6 6rd Tunnel Concept and Configuration

2 Comments

Ahhh… its good to be back…

Assalamu’alaikum brothers and sisters, sory beberapa bulan ga nge-blog, biasa… (sok) sibuk

——————–

Straight to the point… ini makhluk apalagi 6rd (rapid deployment) Tunnel??

Prerequisite:

1. Ngerti 6to4 Tunneling Concept and Configuration

2. ga ngerti 6to4?…belajar IPv6 Stateless and Statefull Configuration, IPv6 Concept, IPv6 Tunnel dulu aja

———————

The Concept

Mudahnya… 6rd tunnel ini upgrade dari 6to4 tunnel (masih ada turunan), why? Kenapa memang dengan 6to4 tunnel? Karena:

1. get rid of 6to4 biggest weakness… the mandatory of using 2002::/16 prefix

2. all customer ip tunnel given by ISP (jadi sistem tunnelnya stateless autoconfig), artinya…bisa QoS, Security juga terjaga, dll

———————–

The Configuration

R1-BR (bertindak sebagai BORDER-RELAY), R2 dan R3 tinggal nerima IP tunnel dari R1

Configurasi di R1

Dan ditambahin static route buat konek antar tunnel

Configurasi di R2 & R3

Untuk ke network dengan prefix 2019:abcd:: …diarahkan ke tunnel0

Tapi untuk selain itu…arahkan ke 2019:abcd:1:: (ini ip-tunnelnya R1-BR), yang mana…ip 2019:abcd:1:: sudah automatically configured (how?…next chapter below)

—————

Wait wait wait… maksudnya “br” apa? maksudnya “prefix-len” apa? maksudnya “6RD_PREFIX” apa? pelan2 mas bro

The Explanation

Untuk membuat 6rd tunnel bekerja…kita butuh 3 hal

1. IPv6 General Prefix
makanya kita nulis “ipv6 general-prefix [NAMA_PREFIX] …“, karena sifatnya yang stateless alias minta domain (baca: ip prefix) dari tempat lain, trus dipasang dengan local addressnya (remember EUI-64)

2. IPv4 Address yang dimasukkan ke IPv6 Address
ini sama persis metodenya kek 6to4 Tunnel

3. CE (Customer Edge) dan BR (Border Relay) Router
sebenernya tanpa BR bisa…klo intention kita mau konek antar CE network (contoh konek ke 2019:abcd::/32 network)
tapi klo kita mau konek keluar dari network tunnel tersebut, kita butuh BR (contoh konek ke 2019:1::1)
keywordnya “br” di router2 CE

Karena 6rd tunnel butuh ipv4 prefix…kita harus specify “prefix-length“-nya (dalam case ini /16)

/16 (dari 32bit ipv4 address) itu berarti…ignore 16 bit pertama, yang 16 bit selanjutnya buat ditambahin/di-embed ke IPv6 address

Prefix dari ipv6 6rd tunnelnya juga kita harus definisikan (dalam case ini “prefix 2019:abcd::/32“), alias…itu ipv4 prefix-length yang kita setting sebelumnya, akan dimasukkin after 2019:abcd::/32

How we convert ipv4 (decimal) ke ipv6 (hexa)???…that why you need to learn 6to4 first, ada caranya disitu

Ip R1 yang 2019:abcd:1:: itu juga didapat dengan cara seperti itu

Klo ipnya bukan 172.16.0.1 gimana? Klo ip-nya 172.16.192.225? atau ip2 lain?

…learn 6to4, learn how to convert decimal to hexa, klo udah ngerti… metode inject prefix ini mudah

———————–

Verifikasi

R2 dapet ip tunnel anycast

Status tunnel operational, prefixnya dapet, border-relay nya dapet

Status “show tunnel 6rd” di R1

Tes ping ke masing2 loopback

Yang lupa gue tambahin disini….

WIRESHARK…dan SPAN, buat ngeliat alur traffic

Plus…Mikrotik seems not supported 6rd until this date (possible if using script)

And last but not least

.

.

.

.

.

.

.

#2019PrabowoSandi

——————–

References:

https://networklessons.com/cisco/ccie-routing-switching-written/ipv6-6rd-rapid-deployment/

https://www.cisco.com/c/en/us/products/collateral/ios-nx-os-software/enterprise-ipv6-solution/whitepaper_c11-665758.html

http://ip-hamsterviel.blogspot.com/2012/06/world-of-6rd-configuring-6rd-in-cisco.html

https://www.youtube.com/watch?v=QyFRoxBbCHo

https://www.youtube.com/watch?v=sL-8-HVS7s0

https://forum.mikrotik.com/viewtopic.php?t=64861

https://forum.mikrotik.com/viewtopic.php?f=9&t=134621

Older Entries