Re: [Emerald] On-Insert Trigger in CALLS solves NAS-Port troubles
Dale E. Reed Jr. ( (no email) )
Sat, 27 Mar 1999 15:00:14 -0800
Gerald Zebedin wrote:
>
> We have modified the trigger in the calls table to solve our problem with
> the port calculation of some NASes like CISCO AS58xx. You only need to add a
> NAS with ONE port. If a call comes in, the trigger now checks if the port
> exist. If not it looks for the NAS ID via NAS IP-address and creates the new
> port. So if you have "funny" port numbers, or don't want to create LOTS of
> ports manually you can try out this trigger. It works fine for us with CISCO
> AS52xx 52xx and 58xx and 3COM RAS1500 or Bay Remote-Annex 2000.
I've always thought about doing this, but its a major performance
issue with aheavily used servers. You could probably run it for a
while then remove the creation once they are all created.
I wrote a cursor a while back that looks at the calls table and creates
the ports that don't exist. You can run this periodically to also
auto-create ports.
------------------------------------------------------------------
/* Update Ports */
DECLARE @nasid varchar(16), @nasport int, @msg varchar(255), @serverid
int
DECLARE ub_cursor CURSOR FOR
Select NASIdentifier, NASPort