if there are so many Discrete trails in the NMS, so we can not change the trail name if it is a discrete trail, so need to make these discrete trails as the normal SDH
trails, without effecting the traffic.
some timed it is observed that, there are so many discrete trails (around 3000), so it is very difficult and also a long procedure to make these trails as the normal
trails one by one.
so at that time we must have a procedure in which we can reduce these discrete trails in bulk. and we also need to consider that the time consume in this process
must be less.
For better understanding please follow the diagram attached here.
In this diagram, we can clearly see that there are so many real NE connected with their neighbor Preconfigured NE.
1. we can see that, there is a fiber connectivity between real NE and pre configured NE, we only need to check that is there any VC4 server trail between a
combination of real NE and Preconfigured NE or not.
if there is any SDH trail requirement by the customer between any combination of real NE and Preconfigured NE (or it can be real-real/preconfigured-preconfigured also), but the thing is there must be a VC4 server trail if requirement is for SDH trail at VC12/VC3 level.but here we are concentrating only on the real-pre configured NE combination.
if the server trail is exsisting there, then we need to make the SDH cross connections in preconfigured NE also. (Suppose preconfigured NE connected with real NE
and the slot-port-VC4 for pre configured NE is 1-1-1, then we need to make cross connections (on all VC12) on this port with any dropping card on VC12 (Suppose on PQ1) level if the other side is having same VC12
after doing this, we should do this in all the combinations of the preconfigured NE and the real NE, because there might be a case where the services are need to be
made between A to B to C to D.
Here B and C are the real NE and A and D are the pre configured NE. so we need to follow the prcedure in all combinations of the real NE and Preconfigured NE.i.e.
from A to B, and C to D.
so here need to make the cross connections in SDH service configuration of A and D preconfigured NE.
after doing this we need to search the trail, then we will found that there are few trails are inactive, and the name of the trails will be starting from A and D, because
there must be some cross connection which will not be used in the complete trail search, because it may be possible that there are only 40 trails/cross connections
made in B and C by the customer, and because we have used all 63 cross connections in A and D for the trail completion purpose, so 40 trails will be reduced from
the discrete trail, but at the same time there must be increase in the discrete trails by 23 no.s, but these new 23 discrete trails will be shown as the "inactive trails".
so we can select those and can delete directly from the discrete trails.
if we will do this in all combination then we will find that there is a reduce in the discrete trails in a large amount in the NMS, and also after making these discrete
trails as the normal trails we can change their names also.so from that prospective also it is good.
there are so many reasons, because of which there is a increase in the discrete trails in the NMS. and one of them is discribed here.
1. if we are making the SDH cross connections in the NE level, and if we are going for the SDH trail search then these cross connections, which are made in the NE
level, will go in to the discrete level, because if we have made the cross connections only in the real NE, and if this real NE is conected with the pre configured NE,
then while trail serching NMS will find the cross connection in real NE only, not in the pre configured NE, which is connected with this real NE.
and some times the customer is force to do so, because some times the customer faces the time slot conflict problem (this problem is observed due to some NMS
version are not good) while making the SDH trail. so he will make the cross connections in the NE level between optical and elecrical (PQ1)/Ethernet card for giving
the drop lines to their end customers.
And if we are not making the SDH cross connections in the pre configured NE which is directly connected with this real NE in the topology, then at the time of SDH t
rail search; there will be a trail which will be incomplete, and this incomplete trail will go in to the discrete level.
1. try to use good NMS version to avoid the possibility of time slot conflict proble.
2. if NMS version is ok, and there is not any problem in trail making, then please use the proper procedre to make trails, instead of making the cross connections at
NE level.(select end to end NE, if there is any preconfigured NE then also need to select that NE while selecting the source or sink node while making the trail).
3. follow the same procedure if there are so many discrete trails in any SDH network, because same thing has been done successfully one network.