Avaya Using Bay Command Console Software Instrukcja Użytkownika Pobierz pdf (Strona 86)

Using the Bay Command Console

3-16 115976-A Rev. A

3. Verify RIP.

rip/1.2.3.4> info state

enabled

rip/1.2.3.4>

Deleting a Conﬁgured Object

Because of the tree hierarchy, objects on higher branches of the tree depend on the

state (and existence) of objects closer to the root of the tree. Deleting an object

also deletes any (child) objects contained by that (parent) object. This is

analogous to deleting a main directory in a UNIX ﬁle system, where deleting a

main directory also deletes all of its subdirectories.

When you delete an object in the device conﬁguration, the BCC automatically

“cleans up” (deletes) any dependent objects.

Using the previous example, proceed as follows to delete RIP from IP 1.2.3.4:

1. Specify the conﬁguration context for the object you want to delete:

bcc> ethernet slot 2 connector 1

ethernet/2/1> ip 1.2.3.4

ip/1.2.3.4> rip

rip/1.2.3.4>

bcc> ethernet/2/1;ip/1.2.3.4;rip

2. Delete RIP.

rip/1.2.3.4> delete

ip/1.2.3.4>

3. Verify RIP.

ip/1.2.3.4> info sub-protocols

{arp/1.2.3.4/1}

ip/1.2.3.4>

Note that the instance of rip/1.2.3.4 does not appear as a conﬁgured object in the

info list for ip/1.2.3.4.

Every object conﬁgurable through the BCC has a

sub-protocols attribute, the

value of which is a list of objects conﬁgured on (or within) the current context

(

ip/1.2.3.4, in this case). If you delete an object from that context, the

sub-protocols attribute acquires a new value, {arp/1.2.3.4/1} in this example.

1 2 ... 81 82 83 84 85 86 87 88 89 90 91 ... 111 112

Brak uwag

Avaya Using Bay Command Console Software Instrukcja Użytkownika Strona 86