Anyone would have a GOOD documentation, or could write one about the best way to do an Audit / Broadcast without screwing up all the networked nodes ? Thank you
Audit / Broadcast
-
frank
- Alcatel Unleashed Certified Guru
- Posts: 3386
- Joined: 06 Jul 2004 00:18
- Location: New York
- Contact:
Audit / Broadcast
Anyone would have a GOOD documentation, or could write one about the best way to do an Audit / Broadcast without screwing up all the networked nodes ? Thank you
Code Free Or Die
ok.
1) These are my thoughts only (from the top of my head) & not an Alcatel guidleine
2) Different networks can be complex, this is based on a fairly straight forward ABC network (of any kind)
3) Try to never kill an audit process, it is very complex, & can be difficult to recover from ( I think I have a procedure some where if neede)
4) Know the network you are auditing, it can make all the difference when bebugging
5) be careful of things like abbreviated numbering (speed dials) accross networks
So, I think the first rule is 'the biggest node wins'. By this, I think that your largest node (sometimes done on geographic location eg capital city/province etc) should usually be the reference.
For your example, we will say that node 1 is our 'reference' node & Node 4 is our new one. Assuming that you know the setup of all the sites e.g numbering plans were taken into account entities etc & all the current sites were synced properly. I would probably go something along the lines of this.
In node 1, run the audit (build reference in local node) to node 4. In general, when I use 'audit' I set the configuration options for the objects & the nodes before starting. Run the audit with selected nodes (in this case node 4) using the general checks (this is pretty good for networks with conformity accross nodes, but can cause issues if not) x2. The second grab gets parts the first One never knew about, mainly to do with attendants & CDT's.
Gernerally I would run an immediate simulation before each one, even though it can take some extra time, it can save you a lot of grief & leave you with a happy customer
If all goes well, you should have gleefullly imported the numbering etc for node 4 into node 1. Once you are satisfied with this, we need to download it to the rest of the network (node 2, 3 & 4 in this case)
Use the 'audit' tool reference downloading over the network option & choose how you want to handle the options, again, depoends on your customer config. Basically just download all the things built in your reference node (1) to the rest of your nodes (2,3,4). Since the refernce node (1) knows already everyhting about the rest of the network, it can insert the info to the tables for each node.
1) These are my thoughts only (from the top of my head) & not an Alcatel guidleine
2) Different networks can be complex, this is based on a fairly straight forward ABC network (of any kind)
3) Try to never kill an audit process, it is very complex, & can be difficult to recover from ( I think I have a procedure some where if neede)
4) Know the network you are auditing, it can make all the difference when bebugging
5) be careful of things like abbreviated numbering (speed dials) accross networks
So, I think the first rule is 'the biggest node wins'. By this, I think that your largest node (sometimes done on geographic location eg capital city/province etc) should usually be the reference.
For your example, we will say that node 1 is our 'reference' node & Node 4 is our new one. Assuming that you know the setup of all the sites e.g numbering plans were taken into account entities etc & all the current sites were synced properly. I would probably go something along the lines of this.
In node 1, run the audit (build reference in local node) to node 4. In general, when I use 'audit' I set the configuration options for the objects & the nodes before starting. Run the audit with selected nodes (in this case node 4) using the general checks (this is pretty good for networks with conformity accross nodes, but can cause issues if not) x2. The second grab gets parts the first One never knew about, mainly to do with attendants & CDT's.
Gernerally I would run an immediate simulation before each one, even though it can take some extra time, it can save you a lot of grief & leave you with a happy customer
If all goes well, you should have gleefullly imported the numbering etc for node 4 into node 1. Once you are satisfied with this, we need to download it to the rest of the network (node 2, 3 & 4 in this case)
Use the 'audit' tool reference downloading over the network option & choose how you want to handle the options, again, depoends on your customer config. Basically just download all the things built in your reference node (1) to the rest of your nodes (2,3,4). Since the refernce node (1) knows already everyhting about the rest of the network, it can insert the info to the tables for each node.
