This illustrates how update works to add a 2nd NE association when an association already
existed.
•
• Remove an NE association to make room for a 2nd NE association
Note: All VMSs, GRNs, & SPs in the following example are assumed to be provisioned prior to this
example.
Table 29: Update Subscription Data Example 2
DescriptionMessage
A PDBI connection has been
established to the Active PDBA.
connect (iid 1, version 1.0)→
rsp (iid 1, rc 0, data (connectId 3, side active))←
A write transaction has been
opened.
begin_txn (iid 2, type write)→
rsp (iid 2, rc 0)←
Creating a new standalone DN
9195551600 on VMS 9195553000.
ent_sub(iid 3, dn 9195551600, vms 9195553000)→
rsp (iid 3, rc 0)←
One new standalone DN
9195551611 created on SP
9195551100 .
ent_sub(iid 4, dn 9195551611, sp 9195551100)→
rsp (iid 4, rc 0)←
This command moves the
specified standalone DN to SP
9195556666.
upd_sub(iid 5, dn 9195551611, sp 9195556666)→
rsp (iid 5, rc 0)←
This command adds the second
NE association to DN 9195551600.
upd_sub(iid 6, dn 9195551600, sp 9195556666)→
rsp (iid 6, rc 0)←
DN 9195551600 is now on VMS
9195553000 (V-Flex) and SP
9195551100 (G-Flex).
This command attempts to add a
new NE association, but is
upd_sub(iid 7, dn 9195551600, grn 9196660000)→
rsp (iid 7, rc 1044)←
rejected because it is not clear
which NE (there are 2 associated
with this DN) to be replaced.
This command specifies that the
GRN should replace VMS
upd_sub(iid 8, dn 9195551600, vms none, grn 9196660000)→
145
910-6022-001 Revision A, March 2011
PDBI Sample SessionsProvisioning Database Interface Manual
To Next Page
Loading...
