6850 and SNMP
-
prcdayton
6850 and SNMP
Hello,
I'm trying to get SNMP to work on our switches. We have 15 tower sites (Layer 2 - no routing), each site has 6850 switches (some stacked) with PTP wireless backhauls connecting each site in a ring topology. We currently use an EMS system to monitor the wireless transport, but I'm unable to get these devices added in. So I tried using OmniVista to manage and monitor all the switches on the network. The only 6850 switch I can see is the one local to where the EMS/OmniVista (same server) is. When I try using the same SNMP config settings on that switch to the next upstream switch I can't discover it. OmniVista is unable to ping the equipment, even when I can't ping it from the server, telnet, ssh to it....? I'm sure this is a very simple fix, but I'm at a loss. Any help or advised would greatly be appreciated. Thank you.
I'm trying to get SNMP to work on our switches. We have 15 tower sites (Layer 2 - no routing), each site has 6850 switches (some stacked) with PTP wireless backhauls connecting each site in a ring topology. We currently use an EMS system to monitor the wireless transport, but I'm unable to get these devices added in. So I tried using OmniVista to manage and monitor all the switches on the network. The only 6850 switch I can see is the one local to where the EMS/OmniVista (same server) is. When I try using the same SNMP config settings on that switch to the next upstream switch I can't discover it. OmniVista is unable to ping the equipment, even when I can't ping it from the server, telnet, ssh to it....? I'm sure this is a very simple fix, but I'm at a loss. Any help or advised would greatly be appreciated. Thank you.
-
one6f
Re: 6850 and SNMP
Hi,
If so, you can not snmp these devices at all. First you need to get an access to the switch before OV can see it.
I understand you have installed OmniVista on the server and you can not ping(telnet,ssh) your OS6850s (except for directly attached) from your OV server?prcdayton wrote:OmniVista is unable to ping the equipment, even when I can't ping it from the server, telnet, ssh to it....?
If so, you can not snmp these devices at all. First you need to get an access to the switch before OV can see it.
-
prcdayton
Re: 6850 and SNMP
I apologize, but I meant to say that I CAN ping, telnet, ssh into all the switches on the network. The OmniVista software says that it's unable to ping the equipment.
-
one6f
Re: 6850 and SNMP
You can try to remove this device from Topology (as it always red) and to add it manually in Topology window through ip address(ip interface must exist on the switch, Loopback0 is better).
You need to set exactly snmp settings for the switch. Do you use snmp v1/2 or v3?
In Topology there are options to ping and to poll device. Are you able to ping(icmp)?
If not, are you able to ping this ip interface from OmniVista server cli? Windows, Linux, Solaris, what you have?
You need to set exactly snmp settings for the switch. Do you use snmp v1/2 or v3?
In Topology there are options to ping and to poll device. Are you able to ping(icmp)?
If not, are you able to ping this ip interface from OmniVista server cli? Windows, Linux, Solaris, what you have?
Re: 6850 and SNMP
Look show ip managed-interfatsii.
If you do not set the mood of its SNMP.
and create a user with permissions to SNMP.
SNMP v3 Conf
aaa authentication console "local"
aaa authentication ftp "local"
aaa authentication http "local"
aaa authentication snmp "local"
aaa authentication ssh "local"
snmp security no security
snmp authentication trap enable
snmp community map mode off
snmp station 10.7.1.38 162 "User2" v3 enable
user User2 password ??????? md5+des read-write all
snmp trap filter 10.7.1.38 48 49 50 51 52 53
snmp trap filter 10.7.1.38 54 55 56 57 58 59
snmp trap filter 10.7.1.38 60 61 62 63 64 65
snmp trap filter 10.7.1.38 66 67 68 69 70 71
snmp trap filter 10.7.1.38 72 73 74 75 76 77
snmp trap filter 10.7.1.38 78 79 80 81 82 83
snmp trap filter 10.7.1.38 84 85 86 87 88 89
snmp trap filter 10.7.1.38 90 91 92 93 94 95
snmp trap filter 10.7.1.38 96 97 98 99 100 101
snmp trap filter 10.7.1.38 102 103 104 105 106 107
snmp trap filter 10.7.1.38 108 109 110 111 112 113
snmp trap filter 10.7.1.38 114 115 116 117 118 119
snmp trap filter 10.7.1.38 124 120 121 122 123
snmp trap filter 10.7.1.38 125 126 127 128 129 130
snmp trap filter 10.7.1.38 131 132 133 134 135 136
snmp trap filter 10.7.1.38 137 138 139 140 141 142
snmp trap filter 10.7.1.38 143 144 145 146 147 148
snmp trap filter 10.7.1.38 149 150 151 152 153 154
snmp trap filter 10.7.1.38 155 156 157 158 159 160
snmp trap filter 10.7.1.38 161
ip managed-interface "Name-interface" application snmp
If you do not set the mood of its SNMP.
and create a user with permissions to SNMP.
SNMP v3 Conf
aaa authentication console "local"
aaa authentication ftp "local"
aaa authentication http "local"
aaa authentication snmp "local"
aaa authentication ssh "local"
snmp security no security
snmp authentication trap enable
snmp community map mode off
snmp station 10.7.1.38 162 "User2" v3 enable
user User2 password ??????? md5+des read-write all
snmp trap filter 10.7.1.38 48 49 50 51 52 53
snmp trap filter 10.7.1.38 54 55 56 57 58 59
snmp trap filter 10.7.1.38 60 61 62 63 64 65
snmp trap filter 10.7.1.38 66 67 68 69 70 71
snmp trap filter 10.7.1.38 72 73 74 75 76 77
snmp trap filter 10.7.1.38 78 79 80 81 82 83
snmp trap filter 10.7.1.38 84 85 86 87 88 89
snmp trap filter 10.7.1.38 90 91 92 93 94 95
snmp trap filter 10.7.1.38 96 97 98 99 100 101
snmp trap filter 10.7.1.38 102 103 104 105 106 107
snmp trap filter 10.7.1.38 108 109 110 111 112 113
snmp trap filter 10.7.1.38 114 115 116 117 118 119
snmp trap filter 10.7.1.38 124 120 121 122 123
snmp trap filter 10.7.1.38 125 126 127 128 129 130
snmp trap filter 10.7.1.38 131 132 133 134 135 136
snmp trap filter 10.7.1.38 137 138 139 140 141 142
snmp trap filter 10.7.1.38 143 144 145 146 147 148
snmp trap filter 10.7.1.38 149 150 151 152 153 154
snmp trap filter 10.7.1.38 155 156 157 158 159 160
snmp trap filter 10.7.1.38 161
ip managed-interface "Name-interface" application snmp
-
prcdayton
Re: 6850 and SNMP
I figured the problem out...the user account had no snmp level access. All good now. Tx
Re: 6850 and SNMP
Will the discovery still work if icmp is disabled? For example the Omnivista Server sits behind a firewall when it attempts to discover switches.one6f wrote:You can try to remove this device from Topology (as it always red) and to add it manually in Topology window through ip address(ip interface must exist on the switch, Loopback0 is better).
You need to set exactly snmp settings for the switch. Do you use snmp v1/2 or v3?
In Topology there are options to ping and to poll device. Are you able to ping(icmp)?
If not, are you able to ping this ip interface from OmniVista server cli? Windows, Linux, Solaris, what you have?
-
one6f
Re: 6850 and SNMP
That should works. OV uses snmp for the further communication.
But you can try it self with a simple code like this:
To remove:
But you can try it self with a simple code like this:
Code: Select all
qos enable
policy condition exceedIcmpCondition icmptype 11
policy condition echoIcmpCondition icmptype 8
policy condition replyIcmpCondition icmptype 0
policy action icmpAction disposition deny
policy rule echoIcmpRule precedence 102 condition echoIcmpCondition action icmpAction
policy rule replyIcmpRule precedence 101 condition replyIcmpCondition action icmpAction
policy rule exceedIcmpRule precedence 100 condition exceedIcmpCondition action icmpAction
qos applyCode: Select all
no policy rule exceedIcmpRule
no policy rule replyIcmpRule
no policy rule echoIcmpRule
no policy action icmpAction
no policy condition exceedIcmpCondition
no policy condition replyIcmpCondition
no policy condition echoIcmpCondition
qos applyRe: 6850 and SNMP
Hi one6f,
Tried disable snmp with qos enable (using your code) on the switch and discovery on OmniVista still works. Icon still green. Thanks...
Tried disable snmp with qos enable (using your code) on the switch and discovery on OmniVista still works. Icon still green. Thanks...
