Infinera DTN-X

Read the overview and setup first. This page is only what a DTN-X does differently, and all three items will catch out anyone assuming Ciena’s behaviour.

connect:
  protocol: tl1
  tl1Vendor: infinera
  tl1Gateway: "on"

Templates: infinera/, SSH and telnet.

Neighbour discovery

RTRV-TIDMAP returns keyword records with an empty AID:

"::TID=CSVLTNFCO1Y,NODEID=MA4623110007,ROUTERID=11.253.152.33"

TIDs are opaque alphanumeric names rather than anything readable, so do not expect them to describe the site.

ROUTERID is shaped like an IP address but is a routing identifier, not a management address. rConfig does not store it as the node’s IP: discovered nodes show their gateway’s address as a placeholder instead. Putting a number in the device view that nothing answers on would be worse than showing the gateway’s.

The response is paged

This is the behaviour that most affects collection. A DTN-X returns one logical answer as several blocks: every block but the last is coded RTRV rather than COMPLD, with the prompt written between them.

> RTRV-TIDMAP:::2;

   INF-SJC-1000 26-09-12 19:53:38
M  2 RTRV
   "::TID=STLTND1Y,NODEID=MA0353062311,ROUTERID=11.253.152.44"
   ... nine more in this block ...
;

>
   INF-SJC-1000 26-09-12 19:53:38
M  2 COMPLD
   "::TID=TUSTNN2Y,NODEID=MA8953593801,ROUTERID=11.253.152.64"
;

rConfig 8.4.0 and later read to the end of the response rather than to the first prompt, so there is nothing to configure. It matters because of what goes wrong otherwise: stopping at the first prompt does not merely truncate the list, it leaves the remaining blocks in the socket where they are read back as the reply to the next command. Every command after that is answered out of step.

A routed reply carries the system name, not the TID

A DTN-X relaying a command for another node answers under its own system name:

> RTRV-EQPT:STLTND1Y::3;

   INF-SJC-1000 26-09-12 19:54:26
M  3 COMPLD

The header says INF-SJC-1000 even though the command addressed STLTND1Y. rConfig knows this and does not apply the header-versus-TID check on this platform; applying Ciena’s rule here would fail every routed Infinera collection.

The trade-off is worth stating plainly: on this platform a gateway that answered locally instead of routing is indistinguishable from one that routed correctly. Nothing in the response separates the two, so the alternative is not a stricter check, it is a check that rejects correct replies.

`tl1NeighbourCmd`

Leave it unset and RTRV-TIDMAP is used. Set it and rConfig sends exactly what you wrote, with one exception: a value beginning with RTRV-NBR is replaced with RTRV-TIDMAP and a warning is logged. That was the shipped default before 8.4.0 and no node answers it, so honouring it means discovering nothing.

Verbs

RTRV-EQPT::ALL:100;        # chassis and slot inventory
RTRV-ALM-ALL::ALL:101;     # active alarms
RTRV-COND-ALL::ALL:102;    # standing conditions
RTRV-SW-VER:::103;         # software version
RTRV-SYS:::104;            # system info

Prompt: >.

Related: Ciena 6500 · Cisco ONS 15454 · Troubleshooting