Fibre Channel (SAN)

Reply
New Contributor
Posts: 2
Registered: ‎03-07-2014

Network. Advisor Problem - why am I getting Destination Table Full for SNMP and Syslog? How to I resolve?

IBM Network Advisor  E-mail Report - Management Server Event

 

IBM Network Advisor Version: 12.0.2

IBM Network Advisor Build: 41

IBM Network Advisor Server Address: xx.xxx.xxx.83

Date: Fri Mar 07 04:56:18 EST 2014

Event: Registering Server xx.xxx.xxx.83 as SNMP trap recipient to the switch xx.xxx.xxx.125 failed. Reason: The SNMP destination table is full on the switch

Severity: Error

 

IP Address: xx.xxx.xxx.83

Source: 7800bswitch

IBM Network Advisor  E-mail Report - Management Server Event

 

IBM Network Advisor Version: 12.0.2

IBM Network Advisor Build: 41

IBM Network Advisor Server Address: xx.xxx.xxx.83

Date: Fri Mar 07 04:56:18 EST 2014

Event: Registering Server xx.xxx.xxx.83 as Syslog recipient to the switch xx.xxx.xxx.124 failed. Reason: The Syslog destination table is full on the switch

Severity: Error

 

IP Address: xx.xxx.xxx.83

Source: 7800aswitch

IBM Network Advisor  E-mail Report - Management Server Event

 

Senior Member
Posts: 1
Registered: ‎01-21-2016

Re: Network. Advisor Problem - why am I getting Destination Table Full for SNMP and Syslog? How to I resolve?

Did you find an answer to this?

Brocade Moderator
Posts: 231
Registered: ‎03-29-2011

Re: Network. Advisor Problem - why am I getting Destination Table Full for SNMP and Syslog? How to I resolve?

Hi,

 

please check the contents of the syslog ip tables on the switch, e.g.  run the following command for the syslog registration on your switch  (if you run FOS < 7.4)

 

switch:admin> syslogdipshow
syslog.1 10.88.88.88

 

if you run FOS > 7.3,  then

 

switch:admin> syslogadmin --show -ip
syslog.1 172.26.26.173
syslog.2 fec0:60:69bc:92:218:8bff:fe40:15c4

 

the switch have 6 slots, if all are occupied by other syslog server, then you need to remove an ip address (syslogdipremove or syslogadmin --remove ip). The switch also have 6 slots for snmp registration trap, and you have to verify if all six slots occupied or not, and then remove a slot.  To look at the snmp trap entries for SNMPv1

 

To display the SNMPv1 configuration:


switch:admin> snmpConfig --show snmpv1
SNMPv1 community and trap recipient configuration:
Community 1: Secret C0de (rw)
Trap recipient: 10.32.147.113
Trap recipient Severity Level: 0
Community 2: OrigEquipMfr (rw)
Trap recipient: 1080::8:800:200C:1234
Trap recipient Severity Level: 0
Community 3: private (rw)
No trap recipient configured yet
Community 4: public (ro)
No trap recipient configured yet
Community 5: common (ro)
No trap recipient configured yet
Community 6: FibreChannel (ro)
No trap recipient configured yet

 

And SNMP v3 the command

 

switch:admin> snmpconfig --show snmpv3

 

And then will have to remove a trap entry/configuration to have space for BNA

 

 




If this provided you with a solution to this issue, please mark it with the button at the bottom "Accept as solution".

Any and all information provided by me is not reviewed, approved or endorsed by Brocade and is provided solely as a convenience for Brocade customers. All systems and all networks are different and unique. If you have a service affecting network problem, please open a TAC service request for service through Brocade, or through your OEM equipment provider. If this provided you with a solution to this issue, please mark it with the button at the bottom "Accept as solution"

Join the Community

Get quick and easy access to valuable resource designed to help you manage your Brocade Network.