From: Andris Zarins (a.zarins@lattelecom.lv)
Date: Tue Oct 02 2007 - 08:56:02 ART
'access vlan' and 'native vlan' can be different on both ends, as long
as you understand the consequences ;)
A
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Andy Cole
Sent: Monday, October 01, 2007 8:55 PM
To: Felix Nkansah; Cisco certification
Subject: RE: Catalyst/Fiber Backbone Connectivity Problem
Assuming these are trunk links,
The 'access vlan' and native vlan should be the same on both sides,
We work with Dot1q trunking,
Switchport access vlan 99 --- (any number you want it to be) but should
be the same on both sides, the default is vlan 1
Switchport trunk native 99
If they are not the same, it could cause some issues.
Andy
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Felix Nkansah
Sent: Monday, October 01, 2007 11:52 AM
To: Cisco certification
Subject: Catalyst/Fiber Backbone Connectivity Problem
A client of mine has a fiber backbone between two buildings on their
campus.
The fiber terminates on a Catalyst 6509 (at the data centre) and a
Catalyst 3750 at the other end. Users at the far-end connect to servers
located at the data center over this fiber.
This connection has been working fine for the past 2 years, until a
recent problem came up.
For two weeks now, the usual occurrence is for the fiber link to stop
passing traffic while working until the 3750 is rebooted or the fiber
connectors removed from the SFP port and replugged, or the interface is
administratively shut down n un-shut.
Meanwhile, the interface and line protocol remain UP on both switches
during this abnormal behaviour. There are also no log messages
occurring.
Everything look fine on both switches. They just wouldnt pass traffic.
The problem occurs about twice each day.
It's difficult diagnosing the problem now. I need help pls.
Regards,
Felix
This archive was generated by hypermail 2.1.4 : Fri Nov 16 2007 - 13:11:11 ART