D-Link DFL-260E CLI Guide for DFL-260E - Page 21

Description, Usage

Page 21 highlights

2.1.4. cc Chapter 2. Command Reference Note Requires Administrator privilege. 2.1.4. cc Change the current context. Description Change the current configuration context. A context is a group of objects that are dependent on and grouped by a parent object. Many objects lie in the "root" context and do not have a specific parent. Other objects, e.g. User objects lie in a sub-context (or child context) of the root - in this case in a LocalUserDatabase. In order to add or modify users you have to be in the correct context, e.g. a LocalUserDatabase called "exampledb". Only objects in the current context can be accessed. Example 2.2. Change context Change to a sub/child context: gw-world:/> cc LocalUserDatabase exampledb gw-world:/exampledb> Go back to the parent context: gw-world:/ospf1/area1> cc .. gw-world:/ospf1> cc .. gw-world:/> Go back to the root context: gw-world:/ospf1/area1> cc gw-world:/> or gw-world:/ospf1/area1> cc / gw-world:/> Usage cc [] Change the current context. cc -print Print the current context. cc Change to root context (same as "cc /"). Options -print Print the current context. Category that groups object types. The property that identifies the configuration object. 21

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198

Note
Requires Administrator privilege.
2.1.4. cc
Change the current context.
Description
Change the current configuration context.
A context is a group of objects that are dependent on and grouped by a parent object. Many objects
lie in the "root" context and do not have a specific parent. Other objects, e.g. User objects lie in a
sub-context (or child context) of the root - in this case in a LocalUserDatabase. In order to add or
modify users you have to be in the correct context, e.g. a LocalUserDatabase called "exampledb".
Only objects in the current context can be accessed.
Example 2.2. Change context
Change to a sub/child context:
gw-world:/> cc LocalUserDatabase exampledb
gw-world:/exampledb>
Go back to the parent context:
gw-world:/ospf1/area1> cc ..
gw-world:/ospf1> cc ..
gw-world:/>
Go back to the root context:
gw-world:/ospf1/area1> cc
gw-world:/>
or
gw-world:/ospf1/area1> cc /
gw-world:/>
Usage
cc [<Category>] <Type> <Identifier>
Change the current context.
cc -print
Print the current context.
cc
Change to root context (same as "cc /").
Options
-print
Print the current context.
<Category>
Category that groups object types.
<Identifier>
The property that identifies the configuration object.
2.1.4. cc
Chapter 2. Command Reference
21