You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/CONTAINERLAB.md
+2-38Lines changed: 2 additions & 38 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,7 +53,7 @@
53
53
54
54
## Improve visualization via custom labels in a ContainerLab YAML file
55
55
56
-
The visualization we got on the previous step lacks hierarchy. Let's fix that by assigning nodes in the ContainerLab topology YAML file to different levels, using custom labels that Graphite understands.
56
+
The visualization we got on the previous step lacks hierarchy. Let's fix that by assigning nodes in the ContainerLab topology YAML file to different levels, using custom labels that Graphite understands. Read [LABELS.md](LABELS.md) for a full list of labels supported by Graphite.
57
57
58
58
1. Open the topology YAML file in the text editor and append the following lines to each `node1-*` definition.
59
59
@@ -101,7 +101,7 @@ The visualization we got on the previous step lacks hierarchy. Let's fix that by
101
101
102
102
## Changing visualization icons
103
103
104
-
All the nodes in our visualization so far represented by the same "router" icon. Let's assume that nodes at tier-1 in our Clos topology can act as L2 switches, and we want to reflect that in the visualization. To achieve that, we can use custom label again, with a name `graph-icon`.
104
+
All the nodes in our visualization so far represented by the same "router" icon. Let's assume that nodes at tier-1 in our Clos topology can act as L2 switches, and we want to reflect that in the visualization. To achieve that, we can use custom label again, with a name `graph-icon`. See possible `graph-icon` values [here](LABELS.md#node-icons).
105
105
106
106
107
107
1. Open the topology YAML file in the text editor and append the following line to each `node1-*` definition.
@@ -124,16 +124,6 @@ All the nodes in our visualization so far represented by the same "router" icon.
124
124
graph-icon: switch
125
125
```
126
126
127
-
Possible graph-icon types are (from [Cisco DevNet NeXT UI API doc](https://developer.cisco.com/site/neXt/document/api-reference-manual/files/src_js_graphic_svg_Icons.js/#l11)):
128
-
129
-
| graph-icon | graph-icon | graph-icon |
130
-
|---|---|---|
131
-
|switch|router|wlc|
132
-
|server|phone|nexus5000|
133
-
|ipphone|host|camera|
134
-
|accesspoint|cloud|unlinked|
135
-
|firewall|hostgroup|wirelesshost|
136
-
137
127
4. Redeploy the topology
138
128
139
129
```Shell
@@ -143,29 +133,3 @@ All the nodes in our visualization so far represented by the same "router" icon.
143
133
3. Now refresh the web page in the browser, and click "Horizontal Layout". Now the bottom row of nodes uses "switch" icons.
144
134
145
135

146
-
147
-
## Using `port` visualization mode
148
-
149
-
Some nodes that can be used within ContainerLab topology may not act as regular network devices. Examples of such nodes could be
150
-
151
-
* Linux hosts with disabled IP forwarding,
152
-
* Traffic Generators.
153
-
154
-
If such node has multiple interfaces connected to the emulated topology, its visualization might not represent their role well. To address this, there is a special `port` visuzalization mode available in Graphite. With such mode enabled for a node, each its interface would be displayed as a separate icon with a name "interface-name@node-name". Below is an example of using `port` mode for `ixia-c-one` traffic generator, together with a "cloud" icon:
Possible graph-icon values, based on [Cisco DevNet NeXT UI API doc](https://developer.cisco.com/site/neXt/document/api-reference-manual/files/src_js_graphic_svg_Icons.js/#l11):
38
+
39
+
|`label: graph-icon`|
40
+
| ------------ |
41
+
|`switch`|
42
+
|`router`|
43
+
|`wlc`|
44
+
|`server`|
45
+
|`phone`|
46
+
|`nexus5000`|
47
+
|`ipphone`|
48
+
|`host`|
49
+
|`camera`|
50
+
|`access`|
51
+
|`cloud`|
52
+
|`unlinked`|
53
+
|`firewall`|
54
+
|`hostgroup`|
55
+
|`wirelesshost`|
56
+
57
+
## `port` visualization mode
58
+
59
+
Some nodes that can be used within the topology may not act as regular network devices. Examples of such nodes could be
60
+
61
+
* Linux hosts with disabled IP forwarding,
62
+
* Traffic Generators.
63
+
64
+
If such node has multiple interfaces connected to the emulated topology, its visualization might not represent their role well. To address this, there is a special `port` visuzalization mode available in Graphite. With such mode enabled for a node, each its interface would be displayed as a separate icon with a name "interface-name@node-name". Below is an example of using `port` mode for `ixia-c-one` traffic generator, together with a "cloud" icon:
0 commit comments