Agentic Development in Practice: How Six AI Agents Built a Web Game - and What Broke

Part 6 of the AI Agents series. The full build story of the browser-playable Snakes & Ladders arena that the six-role software company from Part 5 delivered — beginning, as these things do, with the two times it failed first.

This is a field report on agentic development: what actually happens when you hand a real software project to autonomous AI coding agents and let them run a full development lifecycle. Most guides to agentic coding describe the theory — the roles, the loops, the guardrails. This one is the evidence: three attempts, two abandoned toolchains, a hallucinated graphics API, an AI-issued quality certificate that certified a layer it had never tested, twenty-eight defects closed without being repaired, and a finished game you can play in your browser right now. If you want to know whether AI agents can build software — and, more usefully, how you would ever know — that is what this post is about.

What this post covers:

• Why this game was built three times — twice as native C, by two different agentic drivers, and both times it died.
• What a hallucinated API actually looks like when the compiler grades it, including the subtler case of a function that was real once and has since been removed.
• A QA certificate declaring the application 100% defect-free whose own footnote admits it never tested the layer containing the only visible bug.
• The stretch where my own instruments were wrong four times in a row and the person watching the screen was right every time.
• Twenty-eight defects found by an independent reviewer, closed without being repaired, and then actually repaired.
• Why a finished, tagged, CI-green project needed a week and a full rollback to survive meeting one phone.
• The finished game running on 19 GitHub-hosted runners across three operating systems and two CPU architectures.

The finished arena, playing itself. Procedural board, SVG snakes and ladders, four autonomous players, twelve audio cues — and no build step anywhere in sight.

In Part 5 I forked a production coding CLI into a six-role software development company — CEO, CPO, CTO, programmer, reviewer and tester, running as native subagents on free NVIDIA NIM models. That post was about the harness. It closed by naming the thing the harness actually produced and promising the details here: a four-player Indian Snakes & Ladders arena that plays itself in any browser, with no build step and no server.

This is that story. It does not begin where you would expect, because the browser was not the plan. It was the third plan.

Build a Six-Role AI Software Company by Forking Kimi Code: Multi-Agent SDLC on NVIDIA NIM

Part 5 of the AI Agents series. A six-role software development company — CEO, CPO, CTO, programmer, reviewer, tester — running as native subagents inside a downstream fork of the Kimi Code CLI, powered by free NVIDIA NIM (Nemotron) models, verified on six platforms, and shipping a browser-playable Snakes and Ladders arena.

What this post covers:

• How to build a multi-agent AI software development team that runs an end-to-end SDLC (inception, blueprint, code, review, test) inside a single coding CLI session.
• Why forking a production coding CLI (Kimi Code) is a better fit than assembling a separate multi-agent framework (ChatDev, AutoGen, CrewAI) for real-world software delivery.
• How to make an OpenAI-compatible NVIDIA NIM (Nemotron 3 Ultra 550B, Nemotron 3 Super 120B) endpoint work with a client that assumes Kimi/Anthropic API conventions.
• A step-by-step install of pre-built binaries on Linux (x64 / ARM64), macOS (Intel / Apple Silicon), and Windows (x64 / ARM64).
• Honest engineering post-mortems: the WaitFor timeout saga, a GitHub Actions YAML parse bisect, and provider-compatibility gotchas for OpenAI-compatible gateways.
• A live browser deliverable — a four-player Indian Snakes & Ladders arena — produced end-to-end by the agent team.

Six subagents on Nemotron 3 Super 120B via NVIDIA NIM, in one kimi session, closing out a bad-regressions report against a Snakes and Ladders workspace. Sixty-two minutes in; the tester is still running the verification suite across 153 tool calls.

For four posts now this blog has been running someone else's virtual software company — ChatDev 2.0, wired up to free NVIDIA NIM models, and put through progressively harder assignments: a smoke test on Linux, a live AI news debate wall, a cross-platform Ludo game, and finally a public GitHub release stress-tested on eleven runners. The framework held up. Along the way it also demonstrated, in Part 3, that a green build and a passing test suite can quietly ship a completely broken headline feature; and, in Part 4, that "it works on my machine" reliably hides four defects until the code lands on a machine that was not the author's.

This post moves the company one layer down. Instead of using someone else's multi-agent AI framework and someone else's models, SANYALnet Labs now owns the coding harness itself. The virtual software company is no longer a Python process orchestrated from outside; it lives inside a downstream fork of a production AI coding CLI, as six bindable subagents — autonomous coding agents that share a single session, a single model, and a single conversation transcript. This is agentic SDLC done as one continuous transcript, not a message bus between processes.

Publishing an AI-Built Game: Eleven Runners, Two CPU Architectures, Four Hidden Bugs

Runbook · Public release & CI proof · Part 4

A complete game played on an Arm64 Linux cloud build machine with no monitor, no desktop and nobody watching. The application drew this picture of itself.

Publishing an AI-Built Game: Eleven Runners, Two CPU Architectures, Four Hidden Bugs

In Part 3 of this series, ChatDev 2.0 built SANYALnet Labs Ludo AI Arena—a C#/.NET 10/Avalonia desktop game in which four autonomous AI players play a full match by themselves. Five free models failed at it; one paid DeepSeek run costing about a dollar shipped it. The post ended with the game running on four machines in my house, and a build report from the agents declaring everything green. Both of those statements were true. Neither of them meant the software was actually finished.

Build a Cross-Platform Ludo Game with ChatDev 2.0: Free AI Models Fail, a $1 DeepSeek Run Ships It

Runbook · Multi-agent application build · Part 3

The finished game: four autonomous AI players, a live event log of model-chosen moves, and a die that flashes without shoving the board around.

Building a Desktop Game with ChatDev 2.0: When Free AI Models Fail, and a One-Dollar DeepSeek Run Ships It

In Part 2 of this series, ChatDev 2.0 took a detailed specification and built a Live News Debate Wall—a self-contained Python web service that turned business headlines into a fictional AI-parody debate. That project answered a friendly question: can the virtual software company build a real application from a real spec? It could. This time the question was less friendly.

Build and Run a Live AI News Debate Wall with ChatDev on Linux

Runbook · Multi-agent application build

ChatDev’s finished Live News Debate Wall turns live business headlines into an AI-parody debate—complete with policy, bureaucracy, Vogon poetry and Yoda.

Building a live AI news debate wall with ChatDev 2.0: from requirements prompt to a tested Linux service

In the first part of this series, I installed ChatDev 2.0 on Linux, connected its virtual software company to an OpenAI-compatible GLM endpoint, and proved that the complete agent graph could design, write, review, test and deliver a runnable program. This time, the factory gets an actual assignment.

DO NOT PANIC: Free Windows Stock Market Dashboard

DO NOT PANIC Portfolio Visualizer turns delayed market data into an animated, full-screen financial display.

Stock-market dashboards usually resemble spreadsheets that have acquired several extra panels and begun making demands. We wanted something different: a financial display that could live on a second monitor, office screen, television, or wall-mounted panel without looking like an accounting department had occupied the room.

The result is DO NOT PANIC Portfolio Visualizer 1.0, a free animated stock market dashboard for 64-bit Windows 10 and Windows 11. It combines delayed portfolio quotes, four customizable ticker tapes, floating charts, global market clocks, macro indicators, financial headlines, and rotating city or stock-exchange backgrounds. It is now available from the project’s official GitHub release and its itch.io download page.

Install ChatDev 2.0 on Linux: AI Agents That Build Real Software

Runbook · Multi-agent software factory

Building software with a team of AI agents: installing ChatDev 2.0 and passing a full-lifecycle smoke test

For a while now I've wanted to break out of the closed ecosystems I write code in every day — OpenAI's ChatGPT and Codex, Anthropic's Claude and Claude Code. The reason is simple: the free, openly available models have been closing the gap with the $20-a-month subscription tiers so quickly that paying for a walled garden increasingly feels like a habit rather than a necessity. That instinct was sharpened by Bill Gurley's July 2026 Washington Post opinion piece — Gurley, president and founder of the P3 Institute and a former venture capitalist, argues that the flood of powerful models being given away for free is not a security threat but ordinary competition: the oldest strategy in software, cost leadership, driving price down toward the near-zero cost of copying a model. It is, in the essay's words, simply "what competition looks like." Convinced that the open side is where the momentum now lies, I went hunting for a serious free-model toolchain to build real software with — and ChatDev is the most promising thing I found.

ROBOCOPY: ERROR 87 (0x00000057) Changing File Attributes

Warning - this post does not really offer a solution to the root problem :)

I ran into this when trying to mirror one external USB hard disk drive with a NTFS file system to another external USB hard drive with exFAT file system:

2024/12/12 08:18:03 ERROR 87 (0x00000057) Changing File Attributes <source file pathname>

The parameter is incorrect.

Waiting 30 seconds...

Add a AI powered conversational site search bar to your website or blog

Everyone having a website or a blog adds a "Search this website" search bar prominently somewhere near the top for visitors to punch in queries and find specific information quickly. With the advent of free and cheap AI engines that use natural language processing techniques to create humanlike conversational dialogue, the ubiquitous "Search this site" box can become far more friendly.

I looked around the 'net and created a AI powered conversational search bar for a travel blog in around 15 minutes. To see how it works, head to interactive The Vagabond Couple Travel Blog Search and type in "Victoria Falls" or any other place that is posted in that blog and has been already been crawled by the engine. Alternatively, try typing in something like FORTRAN into the AI Chat Bot for this blog.

Please be aware the AI engine's knowledge base is confined to just the blog and its posts that it has crawled at the current time, not the wider internet.

This is how I did it.

HECnet-in-a-Box distribution: A virtual machine for quick and effortless connection to HECnet - the global hobbyist DECnet network

HECnet in a box

Here is a Oracle VirtualBox appliance intended for people wanting to get on HECnet (the global hobbyist DECnet computer network) in a few minutes (after obtaining Nodenames and DECnet addresses from one of the HECnet Area owners) .

It comes with a bridge that provides TAP interfaces and a VDE Switch for emulators to connect to, as well as a DECnet/Python instance and a SimH PDP-11/70 running RSX-11M-Plus. Configuration involves answering a few questions pertaining to node names and addresses and firing them up which shouldn't take more than a few minutes. Instructions are in the README file.

Both SimH and QEMU support VDE switches directly, so it is easy to keep adding SimH and QEMU emulated machines to it.

The home partition has 80GB of space as-shipped, and memory is set to 2GB but it is a VirtualBox thing and it is trivial to bump up memory as needed.

Maybe it will be of help to people interested in joining HECnet with minimal effort. It can be downloaded from

• archive.org (recommended, BitTorrent link, QR code above)
• https://bit.ly/hecnet-in-a-box-v2-google-drive-torrent (BitTorrent)
• https://bit.ly/hecnet-in-a-box-v2-pcloud-premium
• https://bit.ly/hecnet-in-a-box
• https://bit.ly/hecnet-in-a-box-megashare

Any feedback for the next revision welcome.

Thank you Paul Koning for DECnet/Python and Johnny Billquist for the immaculately curated RSX distribution.

Linux: Keep Disk Usage of System Journal (systemd-journald) in check

systemd-journald sometimes uses up a ridiculous amount of disk space under /var/log/journal. Here are the steps to limit systemd-journald to use 16MB of disk space under /var/log/journal.

1) Edit the configuration file  /etc/systemd/journald.conf and set SystemMaxUse=16M uncommenting it if necessary.

2) Stop the service and its trigger sockets:

# systemctl stop systemd-journald-dev-log.socket systemd-journald.socket systemd-journald
# systemctl status systemd-journald-dev-log.socket systemd-journald.socket systemd-journald

3) If /var/log/journal does not  exist, create it:

# ls -l /var/log/journal/*

If not found:

# mkdir -p /var/log/journal
# systemd-tmpfiles --create --prefix /var/log/journal

4) Clear out existing transient and persistent journals.

# rm -rvf /var/log/journal/*
# rm -rvf /run/log/journal/*

5) Start the service and its trigger sockets:

# systemctl start systemd-journald-dev-log.socket systemd-journald.socket systemd-journald
# systemctl status systemd-journald-dev-log.socket systemd-journald.socket systemd-journald

6) Flush any transient journal entries into persistent storage:

#killall -USR1 systemd-journald # forces in-memory journal to be written to /var/log/journal/*

7) Now you can check the disk space used by journals periodically using:

# du -h /var/log/journal

Note: A quick cleanup of journal storage can be done using the following command which clears up all old entries so that disk usage falls below the indicated parameter:

# journalctl --vacuum-size=2M --rotate

A WORDLE like game for VAX VMS in Pascal

I am trying hard to find a name to credit properly for this awesome little Pascal program "Wordmul" for the legendary MULTICS operating system. This gem was brought to my attention by the gurus at comp.os.vms newgroup. It turns out porting the Pascal/Multics source to VAX Pascal and Linux Free Pascal was fairly trivial.

Those who are interested in this sort of thing can grab the ports here.

Disclaimer: "Wordle" is probably a trademarked copyrighted protected intellectual property etc. of the New York Times, and I or others having fun in Pascal code on ancient systems intend no infringement. Here is the official Wordle on the day I am posting this.

CISCO SWITCH DECNET ROUTING SNMP MIB ::= the mib files needed for complete snmp traversal (including snmpwalk) of DECnet router information

I run a CISCO 7204VXR switch nostalgically named IMPRTR which, among other things, runs a bunch of GRE tunnels carrying DECnet network protocol traffic connecting to other DECnet Level-2 Area Routers providing DECnet communication with various VAX, PDP and other DECnet-speaking machines around the world as a part of HECnet (the global hobbyist DECnet network).

At this time I am running Cisco IOS Software, 7200 Software (C7200-A3JK9S-M), Version 12.4(25d), RELEASE SOFTWARE (fc1) on the 7204VXR. The software comes with an excellent SNMP agent that includes DECnet routing information available to external SNMP clients.

The intent of this post is to summarize in one place the MIB definition files and configuration instructions for Debian-based Linux distributions for accessing the information provided by the SNMP agent on the switch in a pretty way. A specific goal was to have snmpwalk display DECnet information using fully defined human-readable OIDs instead of long series of dot-separated raw SNMP OIDs. 

The following is based on Net-SNMP package installed from standard repos on (a) Ubuntu 20.04.2 LTS and (b) MX Linux 19.2 machines. Both distros are based on Debian for which the MIB search path defaults to $HOME/.snmp/mibs:/usr/share/snmp/mibs:/usr/share/snmp/mibs/iana:/usr/share/snmp/mibs/ietf:/usr/share/mibs/site:/usr/share/snmp/mibs:/usr/share/mibs/iana:/usr/share/mibs/ietf:/usr/share/mibs/netsnmp.

1) Net-SNMP Preparation: Install and Clean Up the full suite of default MIBs

These steps are common for any installation of Net-SNMP on a Debian-derived Linux distribution (including Ubuntu 20.04). As root:

# apt-get install snmp

# apt-get install snmp-mibs-downloader

Edit /etc/snmp/snmp.conf and comment out the line that reads "mibs:" by adding a "#" at the beginning of that line:

# As the snmp packages come without MIB files due to license reasons, loading
# of MIBs is disabled by default. If you added the MIBs you can reenable
# loading them by commenting out the following line.
#mibs :

Lastly, to avoid "Bad operator (INTEGER): At line 73 in /usr/share/snmp/mibs/ietf/SNMPv2-PDU" errors later on, replace the entire file /usr/share/snmp/mibs/ietf/SNMPv2-PDU with the one here.

At this point, SNMP tools should be able to find and use the MIBs. Test with

# snmptranslate -Tl | less

which should produce:

.iso(1).org(3)

.iso(1).org(3).dod(6)

.iso(1).org(3).dod(6).internet(1)

.iso(1).org(3).dod(6).internet(1).directory(1)

.iso(1).org(3).dod(6).internet(1).mgmt(2)

.iso(1).org(3).dod(6).internet(1).mgmt(2).mib-2(1)

.iso(1).org(3).dod(6).internet(1).mgmt(2).mib-2(1).system(1)

.iso(1).org(3).dod(6).internet(1).mgmt(2).mib-2(1).system(1).sysDescr(1)
... and so on

2) Install Cisco DECnet Router MIB definitions

We need three additional MIBs for fully defining human-readable OIDs comprising DECnet-related entries in Cisco's SNMP information base. Grab them from the following links and copy them to /usr/share/snmp/mibs directory that is included in Net-SNMP MIB search path.

1. CISCO-SMI.txt »
2. IF-MIB.txt »
3. OLD-CISCO-DECNET-MIB.txt »

3) Install Cisco DECnet Router MIB definitions

Walk the CISCO MIB using a command line like below. Provide the correct IP address and community string.

snmpwalk -m ALL -v2c -c <community string>  <Hostname/IP address of CISCO router> 1.3.6.1.4.1.9.3.1.26

For one of my CISCO  DECnet routers, this produces the output below. As an example, I have highlighted the parts that tell me DECnet Area 12 is reachable at a DECnet Cost of 10 in 2 Hops. It also tells me the next hop to Area 12 is Node 59.1020, as derived from the last two bytes of DECnet MAC address FC:EF. A easy way to translate DECnet MAC addresses to Node addresses is my Javascript "DECnet - MAC address - SCSSYSTEMID Calculator".

OLD-CISCO-DECNET-MIB::dnArea.1 = INTEGER: 1

OLD-CISCO-DECNET-MIB::dnArea.2 = INTEGER: 2

OLD-CISCO-DECNET-MIB::dnArea.5 = INTEGER: 5

OLD-CISCO-DECNET-MIB::dnArea.9 = INTEGER: 9

OLD-CISCO-DECNET-MIB::dnArea.12 = INTEGER: 12

OLD-CISCO-DECNET-MIB::dnArea.24 = INTEGER: 24

OLD-CISCO-DECNET-MIB::dnArea.27 = INTEGER: 27

OLD-CISCO-DECNET-MIB::dnArea.28 = INTEGER: 28

OLD-CISCO-DECNET-MIB::dnArea.29 = INTEGER: 29

OLD-CISCO-DECNET-MIB::dnArea.30 = INTEGER: 30

OLD-CISCO-DECNET-MIB::dnArea.31 = INTEGER: 31

OLD-CISCO-DECNET-MIB::dnArea.33 = INTEGER: 33

OLD-CISCO-DECNET-MIB::dnArea.34 = INTEGER: 34

OLD-CISCO-DECNET-MIB::dnArea.35 = INTEGER: 35

OLD-CISCO-DECNET-MIB::dnArea.38 = INTEGER: 38

OLD-CISCO-DECNET-MIB::dnArea.39 = INTEGER: 39

OLD-CISCO-DECNET-MIB::dnArea.41 = INTEGER: 41

OLD-CISCO-DECNET-MIB::dnArea.42 = INTEGER: 42

OLD-CISCO-DECNET-MIB::dnArea.52 = INTEGER: 52

OLD-CISCO-DECNET-MIB::dnArea.59 = INTEGER: 59

OLD-CISCO-DECNET-MIB::dnArea.60 = INTEGER: 60

OLD-CISCO-DECNET-MIB::dnArea.61 = INTEGER: 61

OLD-CISCO-DECNET-MIB::dnArea.62 = INTEGER: 62

OLD-CISCO-DECNET-MIB::dnACost.1 = INTEGER: 10

OLD-CISCO-DECNET-MIB::dnACost.2 = INTEGER: 8

OLD-CISCO-DECNET-MIB::dnACost.5 = INTEGER: 15

OLD-CISCO-DECNET-MIB::dnACost.9 = INTEGER: 7

OLD-CISCO-DECNET-MIB::dnACost.12 = INTEGER: 10

OLD-CISCO-DECNET-MIB::dnACost.24 = INTEGER: 13

OLD-CISCO-DECNET-MIB::dnACost.27 = INTEGER: 7

OLD-CISCO-DECNET-MIB::dnACost.28 = INTEGER: 15

OLD-CISCO-DECNET-MIB::dnACost.29 = INTEGER: 9

OLD-CISCO-DECNET-MIB::dnACost.30 = INTEGER: 7

OLD-CISCO-DECNET-MIB::dnACost.31 = INTEGER: 0

OLD-CISCO-DECNET-MIB::dnACost.33 = INTEGER: 6

OLD-CISCO-DECNET-MIB::dnACost.34 = INTEGER: 8

OLD-CISCO-DECNET-MIB::dnACost.35 = INTEGER: 14

OLD-CISCO-DECNET-MIB::dnACost.38 = INTEGER: 18

OLD-CISCO-DECNET-MIB::dnACost.39 = INTEGER: 5

OLD-CISCO-DECNET-MIB::dnACost.41 = INTEGER: 5

OLD-CISCO-DECNET-MIB::dnACost.42 = INTEGER: 6

OLD-CISCO-DECNET-MIB::dnACost.52 = INTEGER: 14

OLD-CISCO-DECNET-MIB::dnACost.59 = INTEGER: 3

OLD-CISCO-DECNET-MIB::dnACost.60 = INTEGER: 10

OLD-CISCO-DECNET-MIB::dnACost.61 = INTEGER: 5

OLD-CISCO-DECNET-MIB::dnACost.62 = INTEGER: 15

OLD-CISCO-DECNET-MIB::dnAHop.1 = INTEGER: 2

OLD-CISCO-DECNET-MIB::dnAHop.2 = INTEGER: 2

OLD-CISCO-DECNET-MIB::dnAHop.5 = INTEGER: 3

OLD-CISCO-DECNET-MIB::dnAHop.9 = INTEGER: 1

OLD-CISCO-DECNET-MIB::dnAHop.12 = INTEGER: 2

OLD-CISCO-DECNET-MIB::dnAHop.24 = INTEGER: 3

OLD-CISCO-DECNET-MIB::dnAHop.27 = INTEGER: 2

OLD-CISCO-DECNET-MIB::dnAHop.28 = INTEGER: 3

OLD-CISCO-DECNET-MIB::dnAHop.29 = INTEGER: 2

OLD-CISCO-DECNET-MIB::dnAHop.30 = INTEGER: 2

OLD-CISCO-DECNET-MIB::dnAHop.31 = INTEGER: 0

OLD-CISCO-DECNET-MIB::dnAHop.33 = INTEGER: 2

OLD-CISCO-DECNET-MIB::dnAHop.34 = INTEGER: 1

OLD-CISCO-DECNET-MIB::dnAHop.35 = INTEGER: 1

OLD-CISCO-DECNET-MIB::dnAHop.38 = INTEGER: 4

OLD-CISCO-DECNET-MIB::dnAHop.39 = INTEGER: 2

OLD-CISCO-DECNET-MIB::dnAHop.41 = INTEGER: 1

OLD-CISCO-DECNET-MIB::dnAHop.42 = INTEGER: 1

OLD-CISCO-DECNET-MIB::dnAHop.52 = INTEGER: 3

OLD-CISCO-DECNET-MIB::dnAHop.59 = INTEGER: 1

OLD-CISCO-DECNET-MIB::dnAHop.60 = INTEGER: 2

OLD-CISCO-DECNET-MIB::dnAHop.61 = INTEGER: 1

OLD-CISCO-DECNET-MIB::dnAHop.62 = INTEGER: 2

OLD-CISCO-DECNET-MIB::dnAIfIndex.1 = INTEGER: 1

OLD-CISCO-DECNET-MIB::dnAIfIndex.2 = INTEGER: 1

OLD-CISCO-DECNET-MIB::dnAIfIndex.5 = INTEGER: 1

OLD-CISCO-DECNET-MIB::dnAIfIndex.9 = INTEGER: 14

OLD-CISCO-DECNET-MIB::dnAIfIndex.12 = INTEGER: 25

OLD-CISCO-DECNET-MIB::dnAIfIndex.24 = INTEGER: 1

OLD-CISCO-DECNET-MIB::dnAIfIndex.27 = INTEGER: 1

OLD-CISCO-DECNET-MIB::dnAIfIndex.28 = INTEGER: 1

OLD-CISCO-DECNET-MIB::dnAIfIndex.29 = INTEGER: 1

OLD-CISCO-DECNET-MIB::dnAIfIndex.30 = INTEGER: 1

OLD-CISCO-DECNET-MIB::dnAIfIndex.31 = INTEGER: 0

OLD-CISCO-DECNET-MIB::dnAIfIndex.33 = INTEGER: 1

OLD-CISCO-DECNET-MIB::dnAIfIndex.34 = INTEGER: 20

OLD-CISCO-DECNET-MIB::dnAIfIndex.35 = INTEGER: 21

OLD-CISCO-DECNET-MIB::dnAIfIndex.38 = INTEGER: 1

OLD-CISCO-DECNET-MIB::dnAIfIndex.39 = INTEGER: 1

OLD-CISCO-DECNET-MIB::dnAIfIndex.41 = INTEGER: 22

OLD-CISCO-DECNET-MIB::dnAIfIndex.42 = INTEGER: 23

OLD-CISCO-DECNET-MIB::dnAIfIndex.52 = INTEGER: 1

OLD-CISCO-DECNET-MIB::dnAIfIndex.59 = INTEGER: 25

OLD-CISCO-DECNET-MIB::dnAIfIndex.60 = INTEGER: 25

OLD-CISCO-DECNET-MIB::dnAIfIndex.61 = INTEGER: 26

OLD-CISCO-DECNET-MIB::dnAIfIndex.62 = INTEGER: 1

OLD-CISCO-DECNET-MIB::dnANextHop.1 = Hex-STRING: 03 7C

OLD-CISCO-DECNET-MIB::dnANextHop.2 = Hex-STRING: 03 7C

OLD-CISCO-DECNET-MIB::dnANextHop.5 = Hex-STRING: 03 7C

OLD-CISCO-DECNET-MIB::dnANextHop.9 = Hex-STRING: FF 27

OLD-CISCO-DECNET-MIB::dnANextHop.12 = Hex-STRING: FC EF

OLD-CISCO-DECNET-MIB::dnANextHop.24 = Hex-STRING: 03 7C

OLD-CISCO-DECNET-MIB::dnANextHop.27 = Hex-STRING: 03 7C

OLD-CISCO-DECNET-MIB::dnANextHop.28 = Hex-STRING: 03 7C

OLD-CISCO-DECNET-MIB::dnANextHop.29 = Hex-STRING: 03 7C

OLD-CISCO-DECNET-MIB::dnANextHop.30 = Hex-STRING: 03 7C

OLD-CISCO-DECNET-MIB::dnANextHop.31 = Hex-STRING: 00 00

OLD-CISCO-DECNET-MIB::dnANextHop.33 = Hex-STRING: 03 7C

OLD-CISCO-DECNET-MIB::dnANextHop.34 = Hex-STRING: FF 8B

OLD-CISCO-DECNET-MIB::dnANextHop.35 = Hex-STRING: FF 8F

OLD-CISCO-DECNET-MIB::dnANextHop.38 = Hex-STRING: 03 7C

OLD-CISCO-DECNET-MIB::dnANextHop.39 = Hex-STRING: 03 7C

OLD-CISCO-DECNET-MIB::dnANextHop.41 = Hex-STRING: 01 A4

OLD-CISCO-DECNET-MIB::dnANextHop.42 = Hex-STRING: FE AB

OLD-CISCO-DECNET-MIB::dnANextHop.52 = Hex-STRING: 03 7C

OLD-CISCO-DECNET-MIB::dnANextHop.59 = Hex-STRING: FC EF

OLD-CISCO-DECNET-MIB::dnANextHop.60 = Hex-STRING: FC EF

OLD-CISCO-DECNET-MIB::dnANextHop.61 = Hex-STRING: FF F7

OLD-CISCO-DECNET-MIB::dnANextHop.62 = Hex-STRING: 03 7C

OLD-CISCO-DECNET-MIB::dnAAge.1 = INTEGER: 0

OLD-CISCO-DECNET-MIB::dnAAge.2 = INTEGER: 0

OLD-CISCO-DECNET-MIB::dnAAge.5 = INTEGER: 0

OLD-CISCO-DECNET-MIB::dnAAge.9 = INTEGER: 33

OLD-CISCO-DECNET-MIB::dnAAge.12 = INTEGER: 40

OLD-CISCO-DECNET-MIB::dnAAge.24 = INTEGER: 0

OLD-CISCO-DECNET-MIB::dnAAge.27 = INTEGER: 0

OLD-CISCO-DECNET-MIB::dnAAge.28 = INTEGER: 0

OLD-CISCO-DECNET-MIB::dnAAge.29 = INTEGER: 0

OLD-CISCO-DECNET-MIB::dnAAge.30 = INTEGER: 0

OLD-CISCO-DECNET-MIB::dnAAge.31 = INTEGER: 0

OLD-CISCO-DECNET-MIB::dnAAge.33 = INTEGER: 0

OLD-CISCO-DECNET-MIB::dnAAge.34 = INTEGER: 43

OLD-CISCO-DECNET-MIB::dnAAge.35 = INTEGER: 25

OLD-CISCO-DECNET-MIB::dnAAge.38 = INTEGER: 0

OLD-CISCO-DECNET-MIB::dnAAge.39 = INTEGER: 0

OLD-CISCO-DECNET-MIB::dnAAge.41 = INTEGER: 125

OLD-CISCO-DECNET-MIB::dnAAge.42 = INTEGER: 39

OLD-CISCO-DECNET-MIB::dnAAge.52 = INTEGER: 0

OLD-CISCO-DECNET-MIB::dnAAge.59 = INTEGER: 26

OLD-CISCO-DECNET-MIB::dnAAge.60 = INTEGER: 0

OLD-CISCO-DECNET-MIB::dnAAge.61 = INTEGER: 43

OLD-CISCO-DECNET-MIB::dnAAge.62 = INTEGER: 0

OLD-CISCO-DECNET-MIB::dnAPrio.1 = INTEGER: 0

OLD-CISCO-DECNET-MIB::dnAPrio.2 = INTEGER: 0

OLD-CISCO-DECNET-MIB::dnAPrio.5 = INTEGER: 0

OLD-CISCO-DECNET-MIB::dnAPrio.9 = INTEGER: 64

OLD-CISCO-DECNET-MIB::dnAPrio.12 = INTEGER: 64

OLD-CISCO-DECNET-MIB::dnAPrio.24 = INTEGER: 0

OLD-CISCO-DECNET-MIB::dnAPrio.27 = INTEGER: 0

OLD-CISCO-DECNET-MIB::dnAPrio.28 = INTEGER: 0

OLD-CISCO-DECNET-MIB::dnAPrio.29 = INTEGER: 0

OLD-CISCO-DECNET-MIB::dnAPrio.30 = INTEGER: 0

OLD-CISCO-DECNET-MIB::dnAPrio.31 = INTEGER: 0

OLD-CISCO-DECNET-MIB::dnAPrio.33 = INTEGER: 0

OLD-CISCO-DECNET-MIB::dnAPrio.34 = INTEGER: 64

OLD-CISCO-DECNET-MIB::dnAPrio.35 = INTEGER: 64

OLD-CISCO-DECNET-MIB::dnAPrio.38 = INTEGER: 0

OLD-CISCO-DECNET-MIB::dnAPrio.39 = INTEGER: 0

OLD-CISCO-DECNET-MIB::dnAPrio.41 = INTEGER: 64

OLD-CISCO-DECNET-MIB::dnAPrio.42 = INTEGER: 64

OLD-CISCO-DECNET-MIB::dnAPrio.52 = INTEGER: 0

OLD-CISCO-DECNET-MIB::dnAPrio.59 = INTEGER: 64

OLD-CISCO-DECNET-MIB::dnAPrio.60 = INTEGER: 0

OLD-CISCO-DECNET-MIB::dnAPrio.61 = INTEGER: 64

OLD-CISCO-DECNET-MIB::dnAPrio.62 = INTEGER: 0