The CV211 Laptop USB Console Adapter provides a direct Laptop-to-Computer connection for fast and easy remote desktop access with no software to install.
Solved
GNS3 Spantree Syslog Messages
Posted on 2013-01-04
Hello Experts,
I'm been trying to generate of the following syslog error messages on GNS3 lab multiswitch 3725 but no matter what I do none of messages appear. Can someone tell me what I'm doing wrong?
%SPANTREE-2-BLOCK_BPDUGUAR
%SPANTREE-2-BLOCK_PVID_LOC
%SPANTREE-2-BLOCK_PVID_PEE
%SPANTREE-2-CHNL_MISCFG:
%SPANTREE-2-LOOPGUARD_BLOC
%SPANTREE-2-LOOPGUARD_CONF
%SPANTREE-2-LOOPGUARD_UNBL
%SPANTREE-2-PVSTSIM_FAIL:
%SPANTREE-2-PVSTSIM_OK:
%SPANTREE-2-RECV_1Q_NON_1Q
%SPANTREE-2-RECV_BAD_TLV:
%SPANTREE-2-RECV_PVID_ERR:
%SPANTREE-2-ROOTGUARD_BLOC
%SPANTREE-2-ROOTGUARD_CONF
%SPANTREE-2-ROOTGUARD_UNBL
%SPANTREE-2-UNBLOCK_CONSIS
%SPANTREE-3-BAD_PORTNUM_SI
%SPANTREE-3-PORT_SELF_LOOP
%SPANTREE-3-PRESTD_NEIGH:
%SPANTREE-4-PORT_NOT_FORWA
%SPANTREE-5-EXTENDED_SYSID
%SPANTREE-5-ROOTCHANGE:
%SPANTREE-5-TOPOTRAP:
%SPANTREE-6-PORT_STATE:
%SPANTREE-7-BLOCK_PORT_TYP
%SPANTREE-7-PORTDEL_SUCCES
%SPANTREE_FAST-7-PORT_FWD_
Cheers
Carlton
I'm been trying to generate of the following syslog error messages on GNS3 lab multiswitch 3725 but no matter what I do none of messages appear. Can someone tell me what I'm doing wrong?
%SPANTREE-2-BLOCK_BPDUGUAR
%SPANTREE-2-BLOCK_PVID_LOC
%SPANTREE-2-BLOCK_PVID_PEE
%SPANTREE-2-CHNL_MISCFG:
%SPANTREE-2-LOOPGUARD_BLOC
%SPANTREE-2-LOOPGUARD_CONF
%SPANTREE-2-LOOPGUARD_UNBL
%SPANTREE-2-PVSTSIM_FAIL:
%SPANTREE-2-PVSTSIM_OK:
%SPANTREE-2-RECV_1Q_NON_1Q
%SPANTREE-2-RECV_BAD_TLV:
%SPANTREE-2-RECV_PVID_ERR:
%SPANTREE-2-ROOTGUARD_BLOC
%SPANTREE-2-ROOTGUARD_CONF
%SPANTREE-2-ROOTGUARD_UNBL
%SPANTREE-2-UNBLOCK_CONSIS
%SPANTREE-3-BAD_PORTNUM_SI
%SPANTREE-3-PORT_SELF_LOOP
%SPANTREE-3-PRESTD_NEIGH:
%SPANTREE-4-PORT_NOT_FORWA
%SPANTREE-5-EXTENDED_SYSID
%SPANTREE-5-ROOTCHANGE:
%SPANTREE-5-TOPOTRAP:
%SPANTREE-6-PORT_STATE:
%SPANTREE-7-BLOCK_PORT_TYP
%SPANTREE-7-PORTDEL_SUCCES
%SPANTREE_FAST-7-PORT_FWD_
Cheers
Carlton
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
4-
4
8 Comments
Are these messages showing up in the console log and not syslog? or are they not on the console either?
How do you have the switch/network configured? If it's not configured correctly, you won't get error messages of the sort you've listed above... There are things you can do to create the circumstances that will generate those errors, but we have to know what you've got setup in order to give you some direction on it.
hi gt2847
Please find attached screenshot and configs that will provide further insight.
Appreciate your help.
screenshot.png
ALS1.txt
ALS2.txt
DLS1.txt
DLS12.txt
Please find attached screenshot and configs that will provide further insight.
Appreciate your help.
screenshot.png
ALS1.txt
ALS2.txt
DLS1.txt
DLS12.txt
It's not clear which ports on the various switches correspond to the interlink lines you have drawn on the network diagram, so I'm not sure which ports relate to which connections...
Your configs do not show VLANs set up. Normally you'll have for each VLAN:
VLAN nnn
name somename
This sets up the VLAN in the switches table and enables it. So for all the VLANs you want to pass around your lab network, go ahead and create them on each switch.
In order to use syslog, you're going to have to put an IP address on an interface so it can talk with your NMS system. Easiest thing to do is to create a vlan interface (once you're named the VLANs as above). Put the NMS server on the VLAN with that interface so that they can communicate with each other. I'd recommend doing your logging from the ALS1 switch as you are likely to sever connectivity with your other devices during your testing. If connections to ALS1 from the logging switch become blocked, you will lose syslog messages. You are unlikely to kill NMS to ALS1 connectivity so that should be good. Once you have IP connectivity to the NMS from the switch, you'll need to put logging statements in so it will send the console messages via syslog to your NMS system.
In order to see the BPDU failure messages, you're going to have to configure ports with "spanning-tree bpduguard enable" on a link between switches. That port would then see a BPDU packet and block.
For rootguard, the link shows failure modes you should be able to configure in your model which would generate those messages.
To see the self-loop message, you'll probably have to plug a switch into itself so that it will see its own BPDU packet and complain.
That should get things started... Let me know if you need more info on configuring the switches...
Your configs do not show VLANs set up. Normally you'll have for each VLAN:
VLAN nnn
name somename
This sets up the VLAN in the switches table and enables it. So for all the VLANs you want to pass around your lab network, go ahead and create them on each switch.
In order to use syslog, you're going to have to put an IP address on an interface so it can talk with your NMS system. Easiest thing to do is to create a vlan interface (once you're named the VLANs as above). Put the NMS server on the VLAN with that interface so that they can communicate with each other. I'd recommend doing your logging from the ALS1 switch as you are likely to sever connectivity with your other devices during your testing. If connections to ALS1 from the logging switch become blocked, you will lose syslog messages. You are unlikely to kill NMS to ALS1 connectivity so that should be good. Once you have IP connectivity to the NMS from the switch, you'll need to put logging statements in so it will send the console messages via syslog to your NMS system.
In order to see the BPDU failure messages, you're going to have to configure ports with "spanning-tree bpduguard enable" on a link between switches. That port would then see a BPDU packet and block.
For rootguard, the link shows failure modes you should be able to configure in your model which would generate those messages.
To see the self-loop message, you'll probably have to plug a switch into itself so that it will see its own BPDU packet and complain.
That should get things started... Let me know if you need more info on configuring the switches...
Featured Post
Watch and learn to see how ATEN provided an easy and effective way for three jointly-owned pubs to control the 60 televisions located across their three venues utilizing the ATEN Control System, Modular Matrix Switch and HDBaseT extenders.
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
In this tutorial I will show you with short command examples how to obtain a packet footprint of all traffic flowing thru your Juniper device running ScreenOS. I do not know the exact firmware requirement, but I think the fprofile command is availab…
I have seen some questions on problems with SSH/telnet access to Cisco routers that may occur despite the fact that from a PC connected to your LAN, Internet connectivity is in place and users can access Internet sites without any issues. There are…
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…
Suggested Courses
Course of the Month8 days, 2 hours left to enroll
715 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.