Thread Rating:
  • 1 Vote(s) - 1 Average
  • 1
  • 2
  • 3
  • 4
  • 5
snmp disabled
#1
I know I probably won't get an answer on this forum, but hay why not give a try Smile

So basically snmp got disabled. Now I'm blind. New cmts is there. I can snmp only to my modem when cpe ip is 192.168.100.1 or if it's the same as hfc ip. I can't snmp to the outside network.
Disable IP filters is checked, but still it seems cm filters are still active. D3 network.
Telneting "Turn filters off" shows Error - Unknown command: 'filters off'


Maybe some good tester soul can PM for some tip or advice.
Reply
#2
SNMP is never ever disabled...

Knowledge=Power
Reply
#3
(30-09-2012, 01:21 AM)ABMJR Wrote: SNMP is never ever disabled...

I know, I meant snmp nmaccess is disabled. Who figured out the answer, pm I also know a few thing or more......
Reply
#4
OK M8..

Understood..

SNMP is so key to the CMTS and the network Elements once the system is running..
Knowledge=Power
Reply
#5
snmp is working in my area .
Reply
#6
I think the command is this...

- cd /s
- cm_filters off
- cd /n
- write


Try that and see if it works for turning off the filters for you.
You can try using this command to find out some information... I have never used it, so use at your own risk and I don't even know if it will work for you.

CM/IpHal>
man
CM/Forwarder>
CM/Forwarder> man halif_show
CM/Forwarder> man halif_show

COMMAND: halif_show

USAGE: halif_show [-s] [-d]

DESCRIPTION:
Shows all of the HalIf objects that have been registered. If -s is
specified, then it also prints a table of the interfaces, showing who can
transmit to whom. Otherwise, it just prints the descriptions. If -d is
specified, then it prints the detailed HalIf object contents, including
counters, Snoops, etc.

EXAMPLES:
halif_show --
Reply
#7
(30-09-2012, 06:13 AM)SlowGrind6 Wrote: I think the command is this...

- cd /s
- cm_filters off
- cd /n
- write


Try that and see if it works for turning off the filters for you.
You can try using this command to find out some information... I have never used it, so use at your own risk and I don't even know if it will work for you.

CM/IpHal>
man
CM/Forwarder>
CM/Forwarder> man halif_show
CM/Forwarder> man halif_show

COMMAND: halif_show

USAGE: halif_show [-s] [-d]

DESCRIPTION:
Shows all of the HalIf objects that have been registered. If -s is
specified, then it also prints a table of the interfaces, showing who can
transmit to whom. Otherwise, it just prints the descriptions. If -d is
specified, then it prints the detailed HalIf object contents, including
counters, Snoops, etc.

EXAMPLES:
halif_show --

And I get this telnet log. I think it is trying to open the config on the wrong IP:

TelnetTK--
{{
Haxorware integrated telnet daemon

Username: r
oot
Password: *****
Welcome.

CM>
CM>
c
d

CM>
CM> cd
/s

CM> cd /s

Active Command Table: SNMP Commands (snmp)

CM -> snmp

CM/SNMP>
c
m

CM/SNMP>
CM/SNMP> cm_cfgfile f
il
te
rs
of
f
CM/SNMP> cm_cfgfile filters off

WARNING - Unrecognized/unused parameter(s) - 'off'; ignoring...

WARNING: This will be applied to all 2 registered instances!
Do you really want to do this? (yes|no) [no]
y


Instance: BcmSnmpAgent for IF 1, name = 'SB5102 CM Agent w/ BRCM Factory Support' (0x807d2254)

Downloading config file filters from 10.10.10.254
Opening file 'filters' on 10.10.10.254 for reading...

0x79053f38 [ConsoleThread] Tftp Client::GetReply: (Tftp Client) Timed out on socket select!
0x79053f38 [ConsoleThread] Tftp Client::Send: (Tftp Client) Attempt #(1) Backoff (2) Exp Block #(1) Last Block #(0) Recv'd Block #(0)

0x79054ee2 [ConsoleThread] Tftp Client::GetReply: (Tftp Client) Timed out on socket select!
0x79054ee2 [ConsoleThread] Tftp Client::Send: (Tftp Client) Attempt #(2) Backoff (4) Exp Block #(1) Last Block #(0) Recv'd Block #(0)

0x79056e2c [ConsoleThread] Tftp Client::GetReply: (Tftp Client) Timed out on socket select!
0x79056e2c [ConsoleThread] Tftp Client::Send: (Tftp Client) Attempt #(3) Backoff (8) Exp Block #(1) Last Block #(0) Recv'd Block #(0)

0x7905acb6 [ConsoleThread] Tftp Client::GetReply: (Tftp Client) Timed out on socket select!
0x7905acb6 [ConsoleThread] Tftp Client::Send: (Tftp Client) Attempt #(4) Backoff (16) Exp Block #(1) Last Block #(0) Recv'd Block #(0)

0x7905b0a8 [ConsoleThread] Tftp Client::GetReply: (Tftp Client) Timed out on socket select!
0x7905b0a8 [ConsoleThread] Tftp Client::Send: (Tftp Client) Attempt #(5) Backoff (1) Exp Block #(1) Last Block #(0) Recv'd Block #(0)

0x7905b882 [ConsoleThread] Tftp Client::GetReply: (Tftp Client) Timed out on socket select!
0x7905b882 [ConsoleThread] Tftp Client::Send: (Tftp Client) Attempt #(6) Backoff (2) Exp Block #(1) Last Block #(0) Recv'd Block #(0)

0x7905c82c [ConsoleThread] Tftp Client::GetReply: (Tftp Client) Timed out on socket select!
0x7905c82c [ConsoleThread] Tftp Client::Send: (Tftp Client) Attempt #(7) Backoff (4) Exp Block #(1) Last Block #(0) Recv'd Block #(0)

0x7905e776 [ConsoleThread] Tftp Client::GetReply: (Tftp Client) Timed out on socket select!
0x7905e776 [ConsoleThread] Tftp Client::Send: (Tftp Client) Attempt #(8) Backoff (8) Exp Block #(1) Last Block #(0) Recv'd Block #(0)

0x79062600 [ConsoleThread] Tftp Client::GetReply: (Tftp Client) Timed out on socket select!
0x79062600 [ConsoleThread] Tftp Client::Send: (Tftp Client) Attempt #(9) Backoff (16) Exp Block #(1) Last Block #(0) Recv'd Block #(0)

0x790629f2 [ConsoleThread] Tftp Client::GetReply: (Tftp Client) Timed out on socket select!
0x790629f2 [ConsoleThread] Tftp Client::Send: (Tftp Client) Attempt #(10) Backoff (1) Exp Block #(1) Last Block #(0) Recv'd Block #(0)

0x790631cc [ConsoleThread] Tftp Client::GetReply: (Tftp Client) Timed out on socket select!
0x790631cc [ConsoleThread] Tftp Client::Send: (Tftp Client) Attempt #(11) Backoff (2) Exp Block #(1) Last Block #(0) Recv'd Block #(0)

0x79064176 [ConsoleThread] Tftp Client::GetReply: (Tftp Client) Timed out on socket select!
0x79064176 [ConsoleThread] Tftp Client::Send: (Tftp Client) Attempt #(12) Backoff (4) Exp Block #(1) Last Block #(0) Recv'd Block #(0)

0x790660c0 [ConsoleThread] Tftp Client::GetReply: (Tftp Client) Timed out on socket select!
0x790660c0 [ConsoleThread] Tftp Client::Send: (Tftp Client) Attempt #(13) Backoff (8) Exp Block #(1) Last Block #(0) Recv'd Block #(0)

0x79069f4a [ConsoleThread] Tftp Client::GetReply: (Tftp Client) Timed out on socket select!
0x79069f4a [ConsoleThread] Tftp Client::Send: (Tftp Client) Attempt #(14) Backoff (16) Exp Block #(1) Last Block #(0) Recv'd Block #(0)

0x7906a33c [ConsoleThread] Tftp Client::GetReply: (Tftp Client) Timed out on socket select!
0x7906a33c [ConsoleThread] Tftp Client::Send: (Tftp Client) Attempt #(15) Backoff (1) Exp Block #(1) Last Block #(0) Recv'd Block #(0)

0x7906ab16 [ConsoleThread] Tftp Client::GetReply: (Tftp Client) Timed out on socket select!
0x7906ab16 [ConsoleThread] Tftp Client::Send: (Tftp Client) Attempt #(16) Backoff (2) Exp Block #(1) Last Block #(0) Recv'd Block #(0)

0x7906bac0 [ConsoleThread] Tftp Client::GetReply: (Tftp Client) Timed out on socket select!
0x7906bac0 [ConsoleThread] Tftp Client::Send: (Tftp Client) ERROR - Request Retries > kTftpMaxRequestRetryCount (16) !
Failed to open file!
0x7906bac0 [ConsoleThread] Tftp Client::Close: (Tftp Client) ERROR - Device not opened!

Instance: BcmSnmpAgent for IF 2, name = 'SB5102 CPE Agent w/ BRCM Factory Support' (0x805e2ce8)

WARNING - unknown command id (456)! Ignoring...

CM/SNMP>
Reply
#8
That is trying to download the config file and it has timed out. What you want is to disable the filters on start up.

Here are the commands under the snmp directory...

Command Table: SNMP Commands (snmp)

Description:

SNMP commands.

Available Commands:

agent_core_show cm_cfgfile cm_filter_test debug flush
get group_members install_group key_v3 log
n2m notify_setup parent_chain set severities
show test thread_info throttle trap
view_v1v2
Reply
#9
"Disable IP Filters on startup" is the cm_filters off and that command is active. However filters are still active. I believe that during registration there is no traffic through telnet port 23. There is only snmp through 161, right?
So we have a new oid that overrides "cm_filters off". Solution would be to watch the registration process on 161 and compare it with your cmts on whom you can snmp. That oid will eventually show up.
Same theory with telnet. Find me the registration process on the isp with the cmts from who you can telnet into other modems and compare with the cmts that has telnet enabled. Secret oid will eventually pop-out. Of course if there are still active cmts in the world from whom you can telnet.
On the beginning of uncapping era it was possible to telnet just fine into other modems. Now we can't although cmts can. So there are some filters deployed.

That is just the theory, but to tell you the truth I don't have the time any more to do that all, it is so time consuming.
Reply
#10
have u tried Disable IP Filters on startup? it worked for me, but im running pretty slow . . . . if anyone can help please pm or post a new thread thanks plz.
[Image: 2212473189.png]
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)