This portmast and one other stopped responding to telnet. That was the
first clue something was wrong. I could connect using pmvision and a "sh
netcon" revealed nothing unusual:
pm3-2> sh netcon
Hnd Recv-Q Send-Q Local Address Foreign Address (state)
98 0 0 209.239.239.7.1046 209.239.239.15.53 UDP
88 0 0 209.239.239.7.2223 0.0.0.0.0 LISTEN
582 0 0 209.239.239.7.1023 205.228.248.17.514 UDP
9 0 0 209.239.239.7.1027 0.0.0.0.0 UDP
8 0 0 209.239.239.7.67 port116.dial.vc.68 UDP
6 0 0 209.239.239.7.1643 209.239.239.22.6273 ESTABLISHED
5 0 0 209.239.239.7.161 209.239.239.17.4418 UDP
4 0 0 209.239.239.7.1649 209.239.239.5.1649 UDP
3 0 0 209.239.239.7.1026 209.239.239.17.1646 UDP
'sh mem' also didn't reveal anything-- somewhere around 800k available.
Then the calls started. Everyone was hung on authenticating username. I did
a 'sh ses' through pmvision and it showed a whole mess of empty ports, and
a lot of ports with people in the "connecting" stage. Out of 46 ports that
are usually 100% full, there were only 10 real logins, the rest were either
empty or in the "connecting" state. Both portmasters had the exact same
symptoms. And both had been up for nearly the exact amount of time (36 days
7 hours xx minutes).
OSPF
MCPPP
PRI (NI-2 off of 5ess)
A reboot cleared both of them up and everything is fine now. My other 2
portmasters (with identical configs) were not effected (now up for 36 days
8+ hours).
Weird.
Jon
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.
Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>