gNMI_Containerlab

-

 root@digi-oss:/home/labadmin/mohan/2jan26# cat sr_lab.clab.yml

name: sr_lab
topology:
  nodes:
    sr1:
      kind: nokia_srlinux
      image: ghcr.io/nokia/srlinux:latest
      startup-config: sr1.cfg
    sr2:
      kind: nokia_srlinux
      image: ghcr.io/nokia/srlinux:latest
      startup-config: sr2.cfg
  links:
    - endpoints: ["sr1:e1-1", "sr2:e1-1"]

root@digi-oss:/home/labadmin/mohan/2jan26# cat sr1.cfg
set / interface ethernet-1/1 admin-state enable
set / interface ethernet-1/1 subinterface 0 ipv4 admin-state enable
set / interface ethernet-1/1 subinterface 0 ipv4 address 192.168.0.1/31
set / network-instance default interface ethernet-1/1.0

root@digi-oss:/home/labadmin/mohan/2jan26# cat sr2.cfg
set / interface ethernet-1/1 admin-state enable
set / interface ethernet-1/1 subinterface 0 ipv4 admin-state enable
set / interface ethernet-1/1 subinterface 0 ipv4 address 192.168.0.0/31
set / network-instance default interface ethernet-1/1.0

root@digi-oss:/home/labadmin/mohan/2jan26# sudo containerlab deploy -t sr_lab.clab.yml
13:04:02 INFO Containerlab started version=0.71.1
13:04:02 INFO Parsing & checking topology file=sr_lab.clab.yml
13:04:02 INFO Creating lab directory path=/home/labadmin/mohan/2jan26/clab-sr_lab
13:04:03 INFO Creating container name=sr2
13:04:03 INFO Creating container name=sr1
13:04:03 INFO Running postdeploy actions kind=nokia_srlinux node=sr1
13:04:03 INFO Created link: sr1:e1-1 ▪┄┄▪ sr2:e1-1
13:04:03 INFO Running postdeploy actions kind=nokia_srlinux node=sr2
13:04:25 INFO Adding host entries path=/etc/hosts
13:04:25 INFO Adding SSH config for nodes path=/etc/ssh/ssh_config.d/clab-sr_lab.conf
🎉 A newer containerlab version (0.72.0) is available!
Release notes: https://containerlab.dev/rn/0.72/
Run 'sudo clab version upgrade' or see https://containerlab.dev/install/ for installation options.
╭────────────────┬──────────────────────────────┬─────────┬───────────────────╮
│       Name      │          Kind/Image          │  State  │   IPv4/6 Address  │
├─────────────────┼──────────────────────────────┼─────────┼───────────────────┤
│ clab-sr_lab-sr1 │ nokia_srlinux                │ running │ 172.20.20.7       │
│                 │ ghcr.io/nokia/srlinux:latest │         │ 3fff:172:20:20::7 │
├─────────────────┼──────────────────────────────┼─────────┼───────────────────┤
│ clab-sr_lab-sr2 │ nokia_srlinux                │ running │ 172.20.20.8       │
│                 │ ghcr.io/nokia/srlinux:latest │         │ 3fff:172:20:20::8 │
╰─────────────────┴──────────────────────────────┴─────────┴───────────────────╯


#verify ping works
A:root@sr1# show interface ethernet-1/1
=================================================================================================================================================================================
ethernet-1/1 is up, speed 25G, type None
  ethernet-1/1.0 is up
    Network-instances:
      * Name: default (default)
    Encapsulation   : null
    Type            : routed
    IPv4 addr    : 192.168.0.1/31 (static, preferred, primary)
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
=================================================================================================================================================================================

--{ running }--[  ]--
A:root@sr1# ping network-instance default 192.168.0.0
Using network instance default
PING 192.168.0.0 (192.168.0.0) 56(84) bytes of data.
64 bytes from 192.168.0.0: icmp_seq=1 ttl=64 time=51.8 ms
64 bytes from 192.168.0.0: icmp_seq=2 ttl=64 time=2.28 ms
64 bytes from 192.168.0.0: icmp_seq=3 ttl=64 time=2.26 ms



##GNMIC tool & subscribe

(pyang-venv) root@digi-oss:/home/labadmin/mohan/test# gnmic -a 172.20.20.7:57400 -u admin -p NokiaSrl1! --skip-verify   subscribe   --path "/interface[name=ethernet-1/1]/statistics/out-unicast-packets"   --stream-mode sample   --sample-interval 2s
{
  "source": "172.20.20.7:57400",
  "subscription-name": "default-1767359634",
  "timestamp": 1767359634573513325,
  "time": "2026-01-02T13:13:54.573513325Z",
  "updates": [
    {
      "Path": "interface[name=ethernet-1/1]/statistics/out-unicast-packets",
      "values": {
        "interface/statistics/out-unicast-packets": "313"
      }
    }
  ]
}
{
  "sync-response": true
}
{
  "source": "172.20.20.7:57400",
  "subscription-name": "default-1767359634",
  "timestamp": 1767359636573101050,
  "time": "2026-01-02T13:13:56.57310105Z",
  "updates": [
    {
      "Path": "interface[name=ethernet-1/1]/statistics/out-unicast-packets",
      "values": {
        "interface/statistics/out-unicast-packets": "315"
      }
    }
  ]
}



Comments

Post a Comment

Popular posts from this blog

gNMI_with_grafana on containerlabs

-
Image
  root@digi-oss:/home/labadmin/mohan/2jan26_grafana# cat sr_lab.clab.yml name: sr_lab topology:   nodes:     sr1 : {kind: nokia_srlinux, image: ghcr.io/nokia/srlinux:latest, startup-config: sr1.cfg}     sr2 : {kind: nokia_srlinux, image: ghcr.io/nokia/srlinux:latest, startup-config: sr2.cfg}     # gNMIc Collector     gnmic:       kind: linux       image: ghcr.io/openconfig/gnmic:latest       binds: [gnmic-config.yml:/app/gnmic-config.yml:ro]       cmd: "--config /app/gnmic-config.yml subscribe"     # Prometheus TSDB     prometheus:       kind: linux       image: prom/prometheus:latest       binds: [prometheus.yml:/etc/prometheus/prometheus.yml:ro]       ports: ["9090:9090"]     # Grafana Visualization     grafana:       kind: linux       image: grafa...
Read more

EVPN Route type-1 & type-4 in action

-
Image
 Route Type 1: Ethernet Auto-Discovery (A-D) A Type 1 route is advertised by a PE router on a per-Ethernet Segment Identifier (ESI) basis. It is triggered by the presence of a multihomed connection.  Purpose of Type 1 routes Aliasing:  In an all-active multihoming setup, a Type 1 route informs remote PE routers that an Ethernet segment is reachable via multiple PEs. This allows for load-balancing traffic to the same customer device over multiple paths. Fast convergence (Mass MAC Withdrawal):  If a local link to a multihomed customer device fails, the PE sends a withdrawal message for the Type 1 route. Remote PEs can then withdraw all MAC addresses associated with that Ethernet segment, instead of waiting for individual MAC withdrawals, which speeds up convergence. Split-horizon filtering:   The route carries an ESI label to prevent traffic loops in all-active mode. A PE router won't forward broadcast, unknown unicast, and multicast (BUM) traffic back to its sour...
Read more

BGP EVPN TYPE-1 & TYPE-4 in action

-
  🧠 Quick Recap Before Type-4 When an ESI (Ethernet Segment Identifier) is configured on dual-homed leafs: Each leaf advertises: ✅ Type-1 Per-ESI → ESI discovery & mass withdrawal ✅ Type-1 Per-EVI → VLAN (EVI) participation, per-VLAN control Remote VTEPs use these to know who shares the ESI. Now, to decide which leaf forwards BUM traffic (Broadcast, Unknown, Multicast) for each VLAN, they use Type-4 routes . ⚙️ What is a Type-4 Route? Route Type Name Purpose Type-4 Ethernet Segment Route (ES Route) Used for DF election between PEs sharing the same ESI 🔹 Content of Type-4 Route Each PE advertising a shared ESI sends: EVPN Type-4 Route ----------------- - ESI: 0000:0000:0000:0000:000010 - Originating Router’s IP (VTEP IP) - Route Distinguisher - Next Hop: VTEP IP - Extended Communities: - ES-Import RT (derived from ESI) - DF Algorithm (RFC7432 or RFC8584) 🧭 Putting It Together (Flow of Events) Let’s take this topology again: ...
Read more