What is Network Path Analyzer?

Network Path Analyzer is a network reachability analysis tool based on real-time network configuration. Its primary data input is the network routing and security configuration in a customer tenancy, augmented with key network runtime state data, such as the status of a load balancer backend set or the state of a FastConnect virtual circuit.

Network Path Analyzer answers the following questions that are essential for the cloud network operations team to obtain an accurate and deep understanding of endpoint reachability in their cloud networks:

• If they can’t, why? What is missing?
• If they can, how? Over which routing paths, using which security policies?

Finding the answers to these questions in a complex network can be labor-intensive and time-consuming. It involves analyzing the virtual network topologies, carefully walking through multiple route tables, and scrutinizing different network security groups (NSGs) or security lists along the multi-hop network paths. If done manually, it can be error-prone.

Network Path Analyzer is a great network troubleshooting tool. Additionally, since it doesn’t use or need any traffic along the network paths because it operates solely on the configuration and runtime state data, it is also an effective tool for proactive configuration validation.

Benefits of Network Path Analyzer

Armed with Network Path Analyzer, you can realize the following benefits:

• Troubleshoot reachability issues caused by misconfiguration much faster, significantly reducing the Mean Time to Resolution (MTTR) for this type of outage
• Proactively verify and validate the network routing and security policy configuration for your reachability intents before even starting to send application traffic.
• A tool to perform on-demand validation of the logical network paths to match your intent

How to use Network Path Analyzer

Network Path Analyzer is directly available under Networking on the Oracle Cloud Console. You only need to create a path analysis and run it. An API is available to programmatically create, manage, and run your path analyses.

When creating a path analysis, specify the source and destination endpoints, the network protocol, and the source and the destination ports. For endpoints, you can select an IP address or an OCI resource. The viable OCI resource options include an IP address from a VCN subnet, a compute instance virtual network interface card (VNIC), an application load balancer, or a network load balancer.

In my simulation, I am checking bi-directional communication between 2 compute instances.

Select the “Network Path Analyzer” option in the Network Command Center

Click “Create Path Analysis”

Now fill in the Source and Destination information.

In my case I am testing communication between 2 compute instances (VM) via port 22 (SSH).

After filling in the information, perform the analysis.

After a few minutes, a communication report will be displayed where you can identify if it is working or if there is some type of problem.

Network Path Analyzer can assist with your troubleshooting process for the following reachability-related scenarios:

• Virtual machines (VMs) in your multi-VCN applications can’t communicate with each other. You want to check the configured path.
• Your frontend web server in a multitier application can’t reach the load balancer VIP of the application tier.
• Your load balancer can’t reach some of the backends.
• An on-premises endpoint in your hybrid cloud application can’t reach an OCI instance.
• Your on-premises site can’t access a cloud application hosted by your Oracle instances.

Network Path Analyzer is a tool to assist in troubleshooting reachability issues by quickly identifying misconfiguration and reducing the MTTR caused by configuration issues. It’s also an effective tool for customers to proactively verify their network configuration against their reachability intents so that they can proactively catch and correct misconfiguration and reduce outages.

I hope this article can help you

See you in the next article.

Disclaimer: “The postings on this site are my own and do not necessarily represent my current employer positions, strategies, or opinions. The information here was edited to be useful for general purpose, specific data, and identifications was removed to allow reaching a generic audience and to be useful.

Começamos criando uma compute instance no OCI em uma sub-rede Virtual Cloud Network (VCN) onde temos acesso SSH, seja via Internet Gateway ou um canal privado. Esta VCN deve ter um Gateway de Serviço que permitirá acesso privado à Oracle Services Network para fins de acesso ao Object Storage. Estou usando o Oracle Linux 8 em ARM de baixo custo para minha implantação. Você pode alterar o formato dependendo das necessidades desejadas.

Ja fiz um artigo sobre isso “Criando um Compute Instance”

Crie o bucket que vamos usar para armazenar nossos dados. Deve ser do tipo Armazenamento padrão. Certifique-se de que esteja definido como privado, a menos que você queira armazenar também os dados de outras pessoas.

Precismos usar Grupos Dinâmicos para atribuir à nossa instância um Instance Principal e, em seguida, escrever políticas para permitir que ela funcione com nosso novo bucket.

Criando um Dynamic Group

Criamos um grupo dinâmico para vincular políticas à nossa instância. Neste exemplo, estamos usando apenas uma instância, portanto identificamos essa instância pelo OCID.

A seguir, vamos vincular nosso Dynamic Group a um conjunto de permissões usando uma Política.

Criando uma Politica para acesso ao Object Storage.

É aqui que atribuímos permissões aos membros do Dynamic Group que acabamos de criar. Criaremos uma política com uma instrução que permite que a instância que executa o backup interaja com o bucket específico que queremos montar.

Temos tudo setado para que possamos fazer a instalação no Linux e configurar a ferramenta rclone para que possamos ter acesso ao Object Storage.

Instalando pacotes e arquivo de configuração.

Faremos SSH em nossa instância usando o usuário opc com acesso sudo. A partir daí, instalaremos o rclone e o fuse:

[opc@vm-blog var]$ sudo yum-config-manager --enable ol8_developer && sudo yum install -y rclone fuse fuse3
Oracle Linux 8 Development Packages (aarch64)                                                                                                                         134 MB/s | 108 MB     00:00
Last metadata expiration check: 0:00:31 ago on Wed 13 Dec 2023 09:18:37 PM GMT.
Package fuse3-3.3.0-17.0.1.el8.aarch64 is already installed.
Dependencies resolved.
======================================================================================================================================================================================================
 Package                                   Architecture                               Version                                              Repository                                            Size
======================================================================================================================================================================================================
Installing:
 fuse                                      aarch64                                    2.9.7-17.0.1.el8                                     ol8_baseos_latest                                     81 k
 rclone                                    aarch64                                    1.65.0-1.0.1.el8                                     ol8_developer                                         19 M

Transaction Summary
======================================================================================================================================================================================================
Install  2 Packages

Total download size: 19 M
Installed size: 76 M
Downloading Packages:
(1/2): fuse-2.9.7-17.0.1.el8.aarch64.rpm                                                                                                                              2.3 MB/s |  81 kB     00:00
(2/2): rclone-1.65.0-1.0.1.el8.aarch64.rpm                                                                                                                             95 MB/s |  19 MB     00:00
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Total                                                                                                                                                                  94 MB/s |  19 MB     00:00
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Preparing        :                                                                                                                                                                              1/1
  Installing       : rclone-1.65.0-1.0.1.el8.aarch64                                                                                                                                              1/2
  Installing       : fuse-2.9.7-17.0.1.el8.aarch64                                                                                                                                                2/2
  Running scriptlet: fuse-2.9.7-17.0.1.el8.aarch64                                                                                                                                                2/2
  Verifying        : fuse-2.9.7-17.0.1.el8.aarch64                                                                                                                                                1/2
  Verifying        : rclone-1.65.0-1.0.1.el8.aarch64                                                                                                                                              2/2

Installed:
  fuse-2.9.7-17.0.1.el8.aarch64                                                                    rclone-1.65.0-1.0.1.el8.aarch64

Complete!
[opc@vm-blog var]$

A seguir, criaremos um link simbolico para o diretorio /usr/bin directory:

[opc@vm-blog var]$ sudo ln -s /usr/bin/rclone /sbin/mount.rclone
[opc@vm-blog var]$

Crie um diretório para rclone em /etc/rclone e use o editor de sua preferência para criar um /etc/rclone/rclone.conf

Teste da instalação

A execução dos seguintes comandos montará o sistema de arquivos remoto (Object Storage):

sudo mkdir -p /backup

Depois que nosso local de montagem for criado:

[root@vm-blog rclone]# sudo rclone mount \
>     backup:blog_backup /backup\
>     --allow-other \
>     --cache-dir /tmp/rclone/cache \
>     --config /etc/rclone/rclone.conf \
>     --dir-perms 0770 \
>     --file-perms 0660 \
>     --log-file /var/log/rclone.log \
>     --log-level ERROR \
>     --tpslimit 50  \
>     --umask 0117 \
>     --vfs-cache-mode writes \
>     --vfs-fast-fingerprint &
[1] 73993

A seguir, vamos montar o storage editando nosso /etc/fstab (ponto de monagem deve ser um diretório existente):

backup:blog_backup /backup rclone rw,umask=0117,nofail,_netdev,args2env,config=/etc/rclone/rclone.conf,uid=1000,gid=1000,file_perms=0760,dir_perms=0770,allow_other,vfs_cache_mode=writes,cache_dir=/tmp/rclone/cache 0 0

Depois que seu fstab for editado:

[root@vm-blog /]# sudo mount -av
/                        : ignored
/boot                    : already mounted
/boot/efi                : already mounted
/var/oled                : already mounted
/dev/shm                 : already mounted
none                     : ignored
/backup                  : already mounted
[root@vm-blog /]#

Para este teste configurei o diretório de backup padrão para banco de dados e servidor Web no Object Storage.

Podemos ver aqui que os backups foram gerados no /backup.

Aqui podemos confirmar que os objetos estão no bucket e sincronizados com o arquivos que foram gerados no servidor pelo backup.

Espero que este artigo possa te auxiliar em uma solução simples e sincronizada para seus backups, lembrando que todos os recursos utilizados para este artigos são Always Free.

Te vejo em um próximo artigo.

Até a próxima.

Disclaimer: “The postings on this site are my own and do not necessarily represent my current employer positions, strategies, or opinions. The information here was edited to be useful for general purpose, specific data, and identifications was removed to allow reaching a generic audience and to be useful.

Recebi esta mensagem na console:

Me fez lembrar do ORA-0600, mas vamos lá do que se trata este erro.

A VM ou Compute Instance, envia uma solicitação de protocolo de resolução de endereço (ARP) para a placa de interface de rede virtual (VNIC) da instância. Se o ARP falhar, a máquina virtual (VM) será marcada como sem resposta e a mensagem de erro aparecerá.

Diante disso qual seria as possiveis soluções para analisar e arrumar isso:

Verifique as métricas de integridade da infraestrutura para determinar se há um problema contínuo de infraestrutura. Se houver um problema contínuo de infraestrutura, aguarde até que os engenheiros da OCI resolvam o problema e verifique novamente a métrica instance_accessibility_status.

Se não houver um problema contínuo de infraestrutura, provavelmente há um problema de software ou configuração incorreta de rede que você mesmo deve resolver. Confirme se o sistema operacional e a rede estão configurados corretamente. Consulte as documentações sobre Troubleshooting Compute Instance e Network.

Se as etapas de solução de problemas de computação e rede não forem bem-sucedidas, você poderá usar a reinicialização de diagnóstico para reconstruir a instância inacessível, mas recomendo abrir um chamado para o time de OCI para analise e validação antes de utilizar este recurso.

Espero que isso possa te ajuda em algum momento.

Até a próxima.

Disclaimer: “The postings on this site are my own and do not necessarily represent my current employer positions, strategies, or opinions. The information here was edited to be useful for general purpose, specific data, and identifications was removed to allow reaching a generic audience and to be useful.

1. Stop the instance that you can’t log in to. 

Stop the instance that you can’t connect to. In the Oracle Cloud Infrastructure Console, go to the details page for the instance and click Stop.

2. Detach the boot volume.

Detach the boot volume. In the Boot Volume section, click the Actions icon and choose Detach. 

3. Attach the boot volume to a running Linux instance.

Attach the boot volume to another Linux instance by going to Block Storage >> Boot Volumes >> Boot Volumes Details.  Click  Attach to Instance in Attached Instances. 

Select the iSCSI, Select Instance and click in Attach

Run the iSCSI commands to attach the device and make it visible to the local operating system.

Your boot-volume should appear as /dev/sdb3.

4. Fix the authorized_keys file.

Make /dev/sdb3, which is the root (/) partition where you can recover the opc SSH key file, available to the local operating system using “mount” command.

sudo mount  /dev/sdb3 /mnt

5. Fix the opc SSH key by editing the /mnt/home/opc/.ssh/authorized_keys file and adding your SSH key public file.

sudo vi /mnt/home/opc/.ssh/authorized_keys

After you add or change the SSH public key you need to use, save, and exit it.

6. Run umount /mnt.

sudo umount /mnt

7. Detach the iSCSI boot volume by running the detach iSCSI commands.

Unmount the device and detach it by running the iSCSI commands

Ensure that the /dev/sdb disk is no longer available or visible through the SSH connection, and then detach it.

Click in Continue Detachment

Click in Detach

8. Reattach the boot volume to the instance where you wanted to recover the SSH key, wait for it to become operational.

Click in Attach Boot Volume

After the boot volume is attached, start the Compute Instance.

See you soon in other articles.

Stay tuned by following us on Twitter @aontalba and Linkedin.

Disclaimer: “The postings on this site are my own and do not necessarily represent my current employer positions, strategies, or opinions. The information here was edited to be useful for general purpose, specific data, and identifications was removed to allow reaching a generic audience and to be useful.”

Na semana passada, foi anunciado que a Oracle e a Microsoft criaram uma conexão nuvem-nuvem entre o Oracle Cloud Infrastructure e o Microsoft Azure em determinadas regiões.

Essa conexão permite que você configure cargas de trabalho entre nuvens sem tráfego entre as nuvens que passam pela Internet.

Serviços de Interconexão OCI e Azure:

Limitada à região do Azure Leste dos EUA (eastus) e à região OCI Ashburn (us-ashburn-1) .

O local de peering ExpressRoute está próximo ou no mesmo local de peering que o OCI FastConnect.

O lado da identidade é sua integração comum e bem conhecida entre o IDCS e o Microsoft Active Directory.

Fornece baixa latência e alta conectividade entre nuvens

Network Peering possível entre o Azure e o OCI.

Aplicativo de várias camadas pode ser particionado para executar o banco de dados no OCI e no aplicativo no Azure

Cross-Connect pode ser estabelecido circuito ExpressRoute no Azure e Fastconnect em OCI.

Tráfego entre os dois provedores em uma rede privada.

O tráfego de rede pode ser controlado usando a Lista de Segurança (OCI) e os Grupos de Segurança de Rede (Azure)

Last week, it was announced that Oracle and Microsoft have created a cloud-to-cloud connection between Oracle Cloud Infrastructure and Microsoft Azure in certain regions.

This connection allows you to configure workloads between clouds without traffic between the clouds that pass through the Internet.

OCI and Azure Interconnect services:

Limited to Azure East US (eastus) region and the OCI Ashburn (us-ashburn-1) region as of now.

ExpressRoute peering location is in proximity to or in the same peering location as the OCI FastConnect.

Identity side its common and well known integration between IDCS and Microsoft Active Directory.

Provides low latency and high throughput cross-cloud connectivity

Network Peering possible between Azure and OCI.

Multi-tier application can be partitioned to run DB on OCI and Application on Azure

Cross-Connect can be established ExpressRoute circuit in Azure and Fastconnect on OCI.

Traffic between the 2 providers over a private network.

Network traffic can be controlled using Security List (OCI) and Network Security Groups (Azure)

Link about official documentation:

https://docs.cloud.oracle.com/iaas/Content/Network/Concepts/azure.htm

Hope this helps. See you !!!

André  Ontalba

Disclaimer: “The postings on this site are my own and don’t necessarily represent may actual employer positions, strategies or opinions. The information here was edited to be useful for general purpose, specific data and identifications was removed to allow reach generic audience and to be useful.”