RE: [USR-TC] Need help with Hiper DSP code upgrade
I upgraded my ARC and NMC ok just the dsp failed -----Original Message----- From: alex [mailto:alex@wanex.ge] Sent: Tuesday, December 02, 2003 10:54 AM To: Discussion relating to the 3Com/US Robotics Total Control modem systems. Subject: Re: [USR-TC] Need help with Hiper DSP code upgrade And more: If nothing helps check that your nmc can connect to your computer (tftp port is not blocked, etc). Stephen Rivera - WRCA.Net wrote:
There are instances where you have to work up in increments. try to use a version between 2.1.85 and what you are trying to put in now.
At 09:03 AM 12/2/2003 -0500, you wrote:
Content-Class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C3B8DD.066D13D0"
Group
I m trying to get V.92 code on my modem rack. I m getting an error when upgrading the DSP code. Here is my hardware
DSP code 2.1.85
Hiper ARC code 5.3.2
Hiper NMC code 8.6.3
I get an error upgrading the dsp code to 3.5.2 Its some TFTP error.
Any help would be great.
_______________________________________________ USR-TC mailing list USR-TC@mailman.xmission.com http://mailman.xmission.com/cgi-bin/mailman/listinfo/usr-tc
----------------------------------------------------------------------- -
_______________________________________________ USR-TC mailing list USR-TC@mailman.xmission.com http://mailman.xmission.com/cgi-bin/mailman/listinfo/usr-tc
_______________________________________________ USR-TC mailing list USR-TC@mailman.xmission.com http://mailman.xmission.com/cgi-bin/mailman/listinfo/usr-tc
Hey Folks, I know this question was presented at one time or another but I have yet to see any responses so I thought I'd try again and see if anyone can shed some light so to speak. I'm seeing packets come into syslog from various nas's (hiper arcs) with the following info: Dec 3 13:57:01 as2 --syslog capture: 14000602 slot:3/mod:7 --syslog capture:stop Dec 3 13:57:03 as2 --syslog capture: 0700020c slot:13/mod:3 --syslog capture:stop Dec 3 13:57:12 as2 --syslog capture: 14000602 slot:3/mod:7 --syslog capture:stop Dec 3 13:57:16 as1 --syslog capture: 58010a01 slot:2/mod:11 --syslog capture:stop The one thing I notice is that the majority of them are regarding particular interfaces per nas. Meaning I get these types of logs over and over again.....but usually regarding the same interface (i.e. slot:3/mod:7) in the example above. I don't believe it's necessarily pertaining to that inferface but to the user connected on that interface. I'll also see things like: Dec 3 13:59:24 as2 last message repeated 4 times which leads me to believe I'm getting a LOT of these logs. Can anyone shed some light on these logs? Also....is anyone doing any type of filtering for nachi/blaster and if so are you doing it on your next hop router or on the nas directly? Regards, Todd
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday 03 December 2003 12:55 pm, Todd Bertolozzi wrote:
Hey Folks,
I know this question was presented at one time or another but I have yet to see any responses so I thought I'd try again and see if anyone can shed some light so to speak.
I'm seeing packets come into syslog from various nas's (hiper arcs) with the following info:
Dec 3 13:57:01 as2 --syslog capture: 14000602 slot:3/mod:7 --syslog capture:stop Dec 3 13:57:03 as2 --syslog capture: 0700020c slot:13/mod:3 --syslog capture:stop Dec 3 13:57:12 as2 --syslog capture: 14000602 slot:3/mod:7 --syslog capture:stop Dec 3 13:57:16 as1 --syslog capture: 58010a01 slot:2/mod:11 --syslog capture:stop
The one thing I notice is that the majority of them are regarding particular interfaces per nas. Meaning I get these types of logs over and over again.....but usually regarding the same interface (i.e. slot:3/mod:7) in the example above. I don't believe it's necessarily pertaining to that inferface but to the user connected on that interface. What makes you think that it is related to a user or users and not an interface? I assume your users don't have assigned phone numbers and that your TC isn't fronted by a switch (or telco) that is routing DID's to a specific channel on a span. If those are correct you have modems on those cards going bad. Make sure the settings for those are the smae as the rest. If they are, take those modems out of service or replace the card.
Lewis Bergman Texas Communications 4309 Maple St. Abilene, TX 79602-8044 915-695-6962 ext 115 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE/z0AL7++zav7/K8QRAoPBAJ9c3iLEnO17yKUQlv9PTZV+pcVA2ACgjFjn aACu0rT7lg2UrFHJSqVR8+c= =q/cF -----END PGP SIGNATURE-----
What makes me think it's the user and not necessarily the modem is that it seems to follow particular users. For example....I was seeing these log messages for a particular interface at a particular site all day long. The same user was connected on that interface all day as well. As soon as I kicked him offline the logs for that interface stopped and I haven't seen any really come in again for that particular interface. I could be wrong but that's why I was leaning towards that. What makes you think the modems are bad? Are you familiar with these particular syslog messages Lewis? It doesn't seem obvious to me that these are problematic modems....how sure are you about these logs? Is there another facility such as GWC Modem Driver that could possibly verify this? Thanks for you input/help. Regards, Todd -----Original Message----- From: usr-tc-bounces@mailman.xmission.com [mailto:usr-tc-bounces@mailman.xmission.com] On Behalf Of Lewis Bergman Sent: Thursday, December 04, 2003 9:09 AM To: Discussion relating to the 3Com/US Robotics Total Control modem systems. Subject: Re: [USR-TC] syslog messages -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday 03 December 2003 12:55 pm, Todd Bertolozzi wrote:
Hey Folks,
I know this question was presented at one time or another but I have yet to see any responses so I thought I'd try again and see if anyone can shed some light so to speak.
I'm seeing packets come into syslog from various nas's (hiper arcs) with the following info:
Dec 3 13:57:01 as2 --syslog capture: 14000602 slot:3/mod:7 --syslog capture:stop Dec 3 13:57:03 as2 --syslog capture: 0700020c slot:13/mod:3 --syslog capture:stop Dec 3 13:57:12 as2 --syslog capture: 14000602 slot:3/mod:7 --syslog capture:stop Dec 3 13:57:16 as1 --syslog capture: 58010a01 slot:2/mod:11 --syslog capture:stop
The one thing I notice is that the majority of them are regarding particular interfaces per nas. Meaning I get these types of logs over and over again.....but usually regarding the same interface (i.e. slot:3/mod:7) in the example above. I don't believe it's necessarily pertaining to that inferface but to the user connected on that interface. What makes you think that it is related to a user or users and not an interface? I assume your users don't have assigned phone numbers and that your TC isn't fronted by a switch (or telco) that is routing DID's to a specific channel on a span. If those are correct you have modems on those cards going bad. Make sure the settings for those are the smae as the rest. If they are, take those modems out of service or replace the card.
Lewis Bergman Texas Communications 4309 Maple St. Abilene, TX 79602-8044 915-695-6962 ext 115 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE/z0AL7++zav7/K8QRAoPBAJ9c3iLEnO17yKUQlv9PTZV+pcVA2ACgjFjn aACu0rT7lg2UrFHJSqVR8+c= =q/cF -----END PGP SIGNATURE----- _______________________________________________ USR-TC mailing list USR-TC@mailman.xmission.com http://mailman.xmission.com/cgi-bin/mailman/listinfo/usr-tc
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday 04 December 2003 09:52 am, Todd Bertolozzi wrote:
What makes me think it's the user and not necessarily the modem is that it seems to follow particular users. For example....I was seeing these log messages for a particular interface at a particular site all day long. The same user was connected on that interface all day as well. As soon as I kicked him offline the logs for that interface stopped and I haven't seen any really come in again for that particular interface. I could be wrong but that's why I was leaning towards that.
What makes you think the modems are bad? Are you familiar with these particular syslog messages Lewis? It doesn't seem obvious to me that these are problematic modems....how sure are you about these logs? I didn't even realize it was you Todd. Had I read the from I would have considered that you traced it to a user. I haven't seen that particular error but I have seen modems hang and keep a user online and pass no data. Then when you kick the user the modem hangs for a while, then drops and accepts calls again. After I see that I disable the channel for that span so it can't accept calls.
Short answer, I have no idea about your situation and should have shut up to begin with. Sorry =( - -- Lewis Bergman Texas Communications 4309 Maple St. Abilene, TX 79602-8044 915-695-6962 ext 115 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE/z2it7++zav7/K8QRAmRlAJ93sRrKK1aO5sSI9M/e27AN8WdtrQCfQmAF 34gPfdP2LUI849DTCbNlkbY= =a5jr -----END PGP SIGNATURE-----
-----Original Message----- From: usr-tc-bounces@mailman.xmission.com [mailto:usr-tc-bounces@mailman.xmission.com] On Behalf Of Lewis Bergman Sent: Thursday, December 04, 2003 12:03 PM To: Discussion relating to the 3Com/US Robotics Total Control modem systems. Subject: Re: [USR-TC] syslog messages -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday 04 December 2003 09:52 am, Todd Bertolozzi wrote:
What makes me think it's the user and not necessarily the modem is that it seems to follow particular users. For example....I was seeing these log messages for a particular interface at a particular site all day long. The same user was connected on that interface all day as well. As soon as I kicked him offline the logs for that interface stopped and I haven't seen any really come in again for that particular interface. I could be wrong but that's why I was leaning towards that.
What makes you think the modems are bad? Are you familiar with these particular syslog messages Lewis? It doesn't seem obvious to me that these are problematic modems....how sure are you about these logs? I didn't even realize it was you Todd. Had I read the from I would have considered that you traced it to a user. I haven't seen that particular error but I have seen modems hang and keep a user online and pass no data. Then when you kick the user the modem hangs for a while, then drops and accepts calls again. After I see that I disable the channel for that span so it can't accept calls.
Short answer, I have no idea about your situation and should have shut up to begin with. Sorry =( Absolutely not...I appreciate ANY response on this list. It gets people thinking and many times get issues resolved. We are having problems with ds0's coming back into service without a reboot of the dsp's but those occur only after an arc reboot. Hard to tell too whether or not certain logs should be of concern or are just part of normal operation. Todd - -- Lewis Bergman Texas Communications 4309 Maple St. Abilene, TX 79602-8044 915-695-6962 ext 115 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE/z2it7++zav7/K8QRAmRlAJ93sRrKK1aO5sSI9M/e27AN8WdtrQCfQmAF 34gPfdP2LUI849DTCbNlkbY= =a5jr -----END PGP SIGNATURE----- _______________________________________________ USR-TC mailing list USR-TC@mailman.xmission.com http://mailman.xmission.com/cgi-bin/mailman/listinfo/usr-tc
participants (4)
-
Hall, Eric M. -
Lewis Bergman -
Todd Bertolozzi -
Todd Bertolozzi