!st time user

The trunk analyzer only looks at the traffic load when it runs, it is not an historical tool. So if the second trunk group has had no traffic during the period the analyzer is looking at it, there will be no recommendation.

A list measurements trunk group yesterday will give 24 hours of historical data and there you will be able to see if there is indeed any traffic in the second trunk group.

Switchtek

The Trunk Analyzer (under Faults & Performance in the ASA tool) is in fact a historical tool. I use this tool everyday, to get my trunk usage from the previous day.

However...When I run the list meas command from GEDI, I get the same results in regards to that period.

Thoughts?

!st time user

The trunk analyzer does not tell you if all the members of the first trunk group were ever all busy at the same time, that is not its' purpose. List measurements will tell you that, summary will tell you the busiest hour in the past 24 and hourly (by trunk group) will tell you everything that happened in the last 24 hours. The analyzer will tell if you need more (or less) trunks depending on the average traffic load the trunk group is carrying during the measured period. On Monday you always have too many trunks

If you want to force traffic to the smaller trunk group, go to the signal group and find the two T1s with Interface ID 2 and 3, put those in the other trunk group. This should give you some traffic statistics there.

If I were interested in my trunk usage yesterday, I would use the list measurements hourly report for each trunk group. That way I would not only know how busy the trunks were but at which time of day they were busiest.

I agree with you on all points, and thanks for your help.

So to answer my original question...Would the switch look at them as 1 trunk group when they have the same signaling group?

Thanks again!

Switchtek

That of course, was my post above

!st time user

Would the switch treat them as one trunk group because they are in one signaling group? The answer is yes and no, clear huh?

They are one trunk group as far as the vendor is concerned and to the extent that they are in the same signaling group the switch considers them one group (notice I say one group not one trunk group), but trunk groups can overlap signaling groups and vice versa.

You can have a trunk group with five T1s in it and five different signaling groups and the switch will treat that as one trunk group. For testing and measuring you are dealing with one trunk group that could have T1s from several vendors, it is still one trunk group to the switch.

Likewise you can have five trunk groups that each contain members of the same signaling group (remember that you can have more members in a signaling group than you can possibly fit in one trunk group) and the switch will treat that as five trunk groups. For testing and measuring you are dealing with five trunk groups even though they might be NFAS and being controlled by the same D channel from the vendor.

The relationship between trunk groups and signaling groups is not a straight one to one thing. If it were, you could not mix them.

Switchtek

Very good. Thanks for your expertise!