|
|
 FAQ
 Search
 Memberlist
 Usergroups
 Register
 Profile
 Private messages
 Log in
|
|
| Author |
Message |
tman
Guest
|
 Posted: Wed Feb 13, 2008 1:05 am Post subject: Switch with CATOS Question |
 |
|
I have Catalyst 2980G-A 80-port switch. It has been sending the
following messages to the console:
2008 Feb 12 16:02:39 %PAGP-5-PORTTOSTP:Port 3/12 joined bridge port
3/12
2008 Feb 12 16:03:51 %PAGP-5-PORTFROMSTP:Port 2/14 left bridge port
2/14
2008 Feb 12 16:04:07 %PAGP-5-PORTTOSTP:Port 2/14 joined bridge port
2/14
2008 Feb 12 16:05:40 %PAGP-5-PORTFROMSTP:Port 2/23 left bridge port
2/23
2008 Feb 12 16:05:57 %PAGP-5-PORTTOSTP:Port 2/23 joined bridge port
2/23
It does it over and over for all the ports.
Does anyone know what this means? And what to do to stop it? We do
not use vlans on it. We are just using it for end station ports.
Thanks |
|
| Back to top |
|
 |
|
|
Trendkill
Guest
|
| Posted: Wed Feb 13, 2008 1:12 am Post subject: Re: Switch with CATOS Question |
|
|
On Feb 12, 8:05 pm, tman <naves....@gmail.com> wrote:
| Quote: | I have Catalyst 2980G-A 80-port switch. It has been sending the
following messages to the console:
2008 Feb 12 16:02:39 %PAGP-5-PORTTOSTP:Port 3/12 joined bridge port
3/12
2008 Feb 12 16:03:51 %PAGP-5-PORTFROMSTP:Port 2/14 left bridge port
2/14
2008 Feb 12 16:04:07 %PAGP-5-PORTTOSTP:Port 2/14 joined bridge port
2/14
2008 Feb 12 16:05:40 %PAGP-5-PORTFROMSTP:Port 2/23 left bridge port
2/23
2008 Feb 12 16:05:57 %PAGP-5-PORTTOSTP:Port 2/23 joined bridge port
2/23
It does it over and over for all the ports.
Does anyone know what this means? And what to do to stop it? We do
not use vlans on it. We are just using it for end station ports.
Thanks
|
You have stp logging on which shows when ports go down (or up) because
technically a port will stop forwarding when it goes down. Therefore,
it will send a log anytime a port goes up or down. This can be very
helpful for server switches where you want to see what is dropping,
but for a user switch, it may fill your logs with useless info.
Either way, you can resolve this by changing the parameters for
logging on spanning-tree/stp. |
|
| Back to top |
|
|
|
|
