Also sprach mmm3@cornell.edu
I have 35 T1 circuits coming into my dialup pool. These circuits are in a hunt group which Verizon (f/k/a Bell Atlantic) controls. I had some trouble with one of my chassis where the HiPerARC's NIC failed. When I went to busy out the DS0s on this chassis (whose T1s are in the middle of this hunt group), instead of the calls being routed onto the next available T1, I get a fast busy as if the chassis is "seizing" all the circuits. I had to power the chassis down in order for calls to continue on to the next T1 in the hunt group. Bell At... err... Verizon says there's nothing wrong with their hunt software. Anyone have a clue handy? Can I really not remotely busy a chassis out and leave it powered up for maintenance, or is this a peculiarity with the bad NIC on the HiPerARC?
The NIC on the HiPerARC *shouldn't* affect it...though I have seen weirder things happen. Are these channelized T1's or ISDN PRI? If its PRI...my first guess would be running a translation that doesn't support service messages, but from what you said, I'm guessing chan-T1...not sure how chan-t1 deals with that type of situation though. :/ -- Jeff McAdams Email: jeffm@iglou.com Head Network Administrator Voice: (502) 966-3848 IgLou Internet Services (800) 436-4456 - To unsubscribe to usr-tc, send an email to "majordomo@xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.