[nsp] 6509 Help - Please! :)
Paul Stewart
pauls at nexicom.net
Thu Mar 18 21:46:47 EST 2004
nrtc-6509> (enable) sh trunk
* - indicates vtp domain mismatch
# - indicates dot1q-all-tagged enabled on the port
$ - indicates non-default dot1q-ethertype value
Port Mode Encapsulation Status Native vlan
-------- ----------- ------------- ------------ -----------
15/1 nonegotiate isl trunking 2
Port Vlans allowed on trunk
--------
---------------------------------------------------------------------
15/1
Port Vlans allowed and active in management domain
--------
---------------------------------------------------------------------
15/1
Port Vlans in spanning tree forwarding state and not pruned
--------
---------------------------------------------------------------------
-----Original Message-----
From: Tim Stevenson [mailto:tstevens at cisco.com]
Sent: Thursday, March 18, 2004 9:45 PM
To: Paul Stewart; cisco-nsp at puck.nether.net; cisco-nsp at puck.nether.net
Subject: RE: [nsp] 6509 Help - Please! :)
Vlan 2 should be added to 15/1 automatically. Try a sh trunk.
Tim
At 06:41 PM 3/18/2004, Paul Stewart quipped:
>Hi Tim.. Thanks again..;)
>
>nrtc-6509> (enable) sh vlan
>VLAN Name Status IfIndex Mod/Ports, Vlans
>---- -------------------------------- --------- -------
>------------------------
>1 default active 6 4/1-48
>2 Management_VLAN active 116 1/1-2
> 3/1-48
>
>nrtc-6509> (enable) sh port 15/1
>* = Configured MAC Address
>
>Port Name Status Vlan Duplex Speed Type
>----- -------------------- ---------- ---------- ------ -----------
>------------
>15/1 connected trunk full 1000 Route
>Switch
>
>Port Trap IfIndex
>----- -------- -------
>15/1 disabled 107
>
>Port Status ErrDisable Reason Port ErrDisableTimeout Action on
>Timeout
>---- ---------- ------------------- ----------------------
>-----------------
>15/1 connected - Enable No Change
>
>Port Align-Err FCS-Err Xmit-Err Rcv-Err UnderSize
>----- ---------- ---------- ---------- ---------- ---------
>15/1 0 0 0 0 0
>
>Port Single-Col Multi-Coll Late-Coll Excess-Col Carri-Sen Runts
Giants
>----- ---------- ---------- ---------- ---------- --------- ---------
>---------
>15/1 0 0 0 0 0 0
>-
>
>On the msfc it is configured as (whole config post at bottom of my
>original
>message):
>
>interface Vlan2
> ip address xxx.xxx.100.1 255.255.255.0
>
>nrtc-6509#show interfaces vlan 2
>Vlan2 is down, line protocol is down
>
>I don't see reference to vlan 2 being on 15/1 which I realize now is
>probably an issue..:)
>
>So I do this:
>
>nrtc-6509> (enable) set vlan 2 15/1
>VLAN Mod/Ports
>---- -----------------------
>2 1/1-2
> 3/1-48
>
>No luck as you can see.. What am I doing wrong?
>
>Thanks,
>Paul
>
>-----Original Message-----
>From: Tim Stevenson [mailto:tstevens at cisco.com]
>Sent: Thursday, March 18, 2004 9:37 PM
>To: Paul Stewart; cisco-nsp at puck.nether.net; cisco-nsp at puck.nether.net
>Subject: RE: [nsp] 6509 Help - Please! :)
>
>
>I already checked the config, it looks ok to me, assuming you moved sc0
>to vlan 2.
>
>Make sure vlan 2 exists, is active in sh vlan, that sc0 is in vlan 2 &
>sc0 is active, and that you have a vlan2 int on the msfc and that it is
>no shut.
>
>That should do it - if not, not sure what the issue might be. Is vlan 2
>showing active & forwarding on 15/1?
>
>What is the config of the msfc, didn't see it in the original post.
>
>Tim
>
>At 06:25 PM 3/18/2004, Paul Stewart quipped:
>>And that is not happening... Did you see anything wrong with the
>>config? I realize it's asking yourself and others for quite a bit of
>>"reading" but we're kinda stuck at this point and don't know where to
>>turn for assistance other than this list...:)
>>
>>Thanks again,
>>
>>Paul
>>
>>
>>-----Original Message-----
>>From: cisco-nsp-bounces at puck.nether.net
>>[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Tim Stevenson
>>Sent: Thursday, March 18, 2004 9:17 PM
>>To: cisco-nsp at puck.nether.net; cisco-nsp at puck.nether.net
>>Subject: Re: [nsp] 6509 Help - Please! :)
>>
>>
>>If sc0 is active in a given VLAN, autostate should bring the vlan
>>interface up, even w/no other ports are connected in that vlan.
>>
>>Tim
>>
>>At 05:43 PM 3/18/2004, cisco-nsp-request at puck.nether.net quipped:
>>>Date: Thu, 18 Mar 2004 20:37:41 -0500
>>>From: "Paul Stewart" <pauls at nexicom.net>
>>>Subject: RE: [nsp] 6509 Help - Please! :)
>>>To: "'John Wong'" <JohnWong at crimsonlogic.com>,
>>> <cisco-nsp at puck.nether.net>
>>>Message-ID: <001001c40d52$c5280470$640aa8c0 at pstewart>
>>>Content-Type: text/plain; charset="us-ascii"
>>>
>>>Actually not yet... Didn't realize that.. Thought that the interface
>>>would be up/down instead...
>>>
>>>We're going to bring this up live in the middle of the night (last
>>>try for this week) and see what happens... Be presuming something in
>>>my config is wrong but if nobody sees anything wrong then maybe it's
>>>that simple.... I'll have to laugh if that's it... Been suffering
>>>brainfreeze now from look at this too long..;)
>>>
>>>Paul
>>
>>
>>Tim Stevenson, tstevens at cisco.com
>>Routing & Switching CCIE #5561
>>Technical Marketing Engineer, Catalyst 6500
>>Cisco Systems, http://www.cisco.com
>>IP Phone: 408-526-6759
>>********************************************************
>>The contents of this message may be *Cisco Confidential*
>>and are intended for the specified recipients only.
>>
>>_______________________________________________
>>cisco-nsp mailing list cisco-nsp at puck.nether.net
>>https://puck.nether.net/mailman/listinfo/cisco-nsp
>>archive at http://puck.nether.net/pipermail/cisco-nsp/
>
>
>Tim Stevenson, tstevens at cisco.com
>Routing & Switching CCIE #5561
>Technical Marketing Engineer, Catalyst 6500
>Cisco Systems, http://www.cisco.com
>IP Phone: 408-526-6759
>********************************************************
>The contents of this message may be *Cisco Confidential*
>and are intended for the specified recipients only.
Tim Stevenson, tstevens at cisco.com
Routing & Switching CCIE #5561
Technical Marketing Engineer, Catalyst 6500
Cisco Systems, http://www.cisco.com
IP Phone: 408-526-6759
********************************************************
The contents of this message may be *Cisco Confidential*
and are intended for the specified recipients only.
More information about the cisco-nsp
mailing list