Bringing Up/Activating VLAN on 2900

Hi All,
the vlan, highdruid, is down, how is it brought up..? Cheers.
coolboarderguy...
Cool#sh vlan
VLAN Name Status Ports
1 default active Fa0/5, Fa0/7
2 highdruid act/lshut Fa0/1, Fa0/2, Fa0/3, Fa0/4
3 slick active Fa0/8, Fa0/9, Fa0/10, Fa0/11,
Fa0/12

Hi All,
well, 0/1 - 4 look no different to 0/7 - 12, yet, vlan 3 is active, and vlan 2 isn't...missed something..?
Cool#sh
00:56:35: %SYS-5-CONFIG_I: Configured from console by consolevlan
VLAN Name Status Ports
1 default active Fa0/5, Fa0/7
2 highdruid act/lshut Fa0/1, Fa0/2, Fa0/3, Fa0/4
3 slick active Fa0/8, Fa0/9, Fa0/10, Fa0/11,
Fa0/12
1002 fddi-default active
1003 token-ring-default active
1004 fddinet-default active
1005 trnet-default active
VLAN Type SAID MTU Parent RingNo BridgeNo Stp BrdgMode Trans1 Trans2
1 enet 100001 1500 - - - - - 0 0
2 enet 100002 1500 - - - - - 0 0
3 enet 100003 1500 - - - - - 0 0
1002 fddi 101002 1500 - - - - - 0 0
1003 tr 101003 1500 - - - - - 0 0
1004 fdnet 101004 1500 - - - ieee - 0 0
1005 trnet 101005 1500 - - - ibm - 0 0
Cool#sh ip int brief
Interface IP-Address OK? Method Status ProlVLAN1 192.168.168.2 YES NVRAM up up
VLAN2 unassigned YES unset administratively down dow
FastEthernet0/1 unassigned YES unset down dow
FastEthernet0/2 unassigned YES unset down dow
FastEthernet0/3 unassigned YES unset down dow
FastEthernet0/4 unassigned YES unset down dow
FastEthernet0/5 unassigned YES unset down dow
FastEthernet0/6 unassigned YES unset up up
FastEthernet0/7 unassigned YES unset down dow
FastEthernet0/8 unassigned YES unset down dow
FastEthernet0/9 unassigned YES unset down dow
FastEthernet0/10 unassigned YES unset down dow
FastEthernet0/11 unassigned YES unset down dow
FastEthernet0/12 unassigned YES unset down dow
Cool#

Similar Messages

Activity Guide tab not visible in BPM Workspace

I've deployed a simple BPM Process which consists of one Initiator and one User task. I've added both the activities to a milestone what I defined under the Activity Guide.
I've used JDeveloper 11.1.1.4.0 to develope the Process.
But after deploying the same in Server, I can't see the "Activity Guide" tab in the BPM Workspace.
Thogh I can see the activity guide available for editing in composer portal.
Please help me if you know how can I get the "Activity Guide" tab in the BPM Workspace?
Thanks in advance.
Sambit

Hi Paulo,
Thanks a lot for your reply.
I kind of assumed that it's a feature of BPM 11.1.1.5 FP4 after going through a few articles on the web.
But I got confused when after visiting below provided url :
http://www.oracle.com/technetwork/middleware/bpm/learnmore/488809
Please see the statement "*In earlier releases, to use Activity Guide you had to perform some manual steps to create the Activity Guide Player inside Oracle BPM Suite – BPM Workspace.*" under "Enhancements to Activity Guide within BPM Workspace" section in the document presnt in the above mentioned url.
I couldn't find any manual steps which can bring the Activity Guide Player in the workspace anyways and your reply confirms that.
Thanks,
Sambit

Define an applicant activity in SPRO

Hi All,
Can anyone please advise if we can delete the existing (standard) applicant activities in SPRO and modify the existing one ?
e.g. After we do initial data entry action in PB40, the planned activity: WW-RECEIPT automatically gets created. It has been defined in SPRO - Personnel Management -Recruitment -Applicant Selection -Applicant activities - Applicant activity types - Change automatic creation of applicant activities.
Feature PACTV is maintained.
Please advise.

Hi,
indeed the automatic creation of Activities is defined in PACTV.
You can delete the node "1 In process" and no activity will be generated.
Alternatively, you can bring the Activity in the foreground (INDIC A instead of INDIC S) so the user can choose whether to save it or not.

L2 Integration of Multiple VLANs

I have reviewed the ACI L2 and L3 Connectivity White Paper. Using the instructions, I have successfully integrated an a VLAN from from the outside into ACI. I used the Extend BD approach. In looking at the instructions, it appears that creating an External Bridge Domain is required for each L2 VLAN from the outside. Is there a way to use the same physical port (VLAN trunk port from downstream switch) to bring in multiple VLANs in to ACI.
I would like to use only one port for all VLANs to be imported.
Is this possible ? If so, what would be the configuration steps ?
thanks,

The question that should be asked is what are you trying to accomplish?
1. Either you have external endpoints that need to be members of the same EPG as fabric hosted endpoints
or
2. You have external endpoints that you need to apply policy between everything else inside the fabric.
If this is the first case what you should be extending the EPG, not the bridge domain. By extending the Bridge Domain you're essentially mapping all the external traffic for that BD into one VLAN which will be represented by an External EPG you'd create on the APIC. This is useful in the case where you have all external users coming into the fabric you want to treat together using contracts between external users and internal EPGs.
Ex.
External Users <C> Web_EPG <C> App_EPG <C> DB_EPG
C = Contract
If it's the second case above, and you have end points both inside the fabric and external that need to belong to the same EPG and have the same policies applied endpoints internal or external to ACI, you'll want to extend the EPG as detailed in the first method of the L2/L3 Connectivity guide.
Regards,
Robert

Vlan Accessing

Hi All,
I can ping successfully to another PC in the same vlan(192.168.168.10, 192.168.168.12, 192.168.168.13), but, can't ping either the management vlan(192.168.168.2) or the router(192.168.168.1). What needs setting to allow vlan3 PCs to do this.? This is not an intended deign or anything, except just playing around etc. Also, vlan2 seems down(act/lshut). Cheers.
coolboarderguy...
vlan2
Cool#sh vlan
VLAN Name Status Ports
1 default active Fa0/5, Fa0/6, Fa0/7
2 highdruid act/lshut Fa0/1, Fa0/2, Fa0/3, Fa0/4
3 slick active Fa0/8, Fa0/9, Fa0/10, Fa0/11,
Fa0/12
1002 fddi-default active
1003 token-ring-default active
1004 fddinet-default active
1005 trnet-default active
VLAN Type SAID MTU Parent RingNo BridgeNo Stp BrdgMode Trans1 Trans2
1 enet 100001 1500 - - - - - 0 0
2 enet 100002 1500 - - - - - 0 0
3 enet 100003 1500 - - - - - 0 0
1002 fddi 101002 1500 - - - - - 0 0
1003 tr 101003 1500 - - - - - 0 0
1004 fdnet 101004 1500 - - - ieee - 0 0
1005 trnet 101005 1500 - - - ibm - 0 0

Hi coolboarderguy,
Here you go with the solution...You only need to have trunks if you want more than one vlan to pass through between the sitches, or betwen switch and router or between switch and server which can be configured for trunking.
Now your router is on vlan 1 which is a bad design because you have workstation in vlan 3 and router in vlan 1 which at layer 2 are in different logical domain but considering layer 3 you have same subnet for 2 different vlan.
If it is in the same subnet in which your workstations are then it should be in vlan 3.
But incase you want your router to be in differnt vlan and different subnet then you need to have a trunk between the switch and the router and create sub interfaces on router and give encapsulation on subinterfaces. This will enable inter vlan routing to have communication between different vlans.
HTH
Ankur

How do you keep a VLAN interface up?

Is there a method that enables you to keep a vlan "UP", even when none of the physical interfaces assigned to that vlan are connected?

If you are using vtp, you can "force" the VLAN active using those commands; depending on the switch you are using, this is done a number of different ways.
newer IOS switch running native mode -
conf t
vlan 1
state active
exit
wr mem
older IOS switch
From an enable prompt -
vlan database
[enters vlan database mode)
[Note: Newer IOS warns that this is deprecated and will not show help -- the help is as follows -
switchname#vlan database
% Warning: It is recommended to configure VLAN from config mode,
as VLAN database mode is being deprecated. Please consult user
documentation for configuring VTP/VLAN in config mode.
switchname(vlan)#?
VLAN database editing buffer manipulation commands:
abort Exit mode without applying the changes
apply Apply current changes and bump revision number
exit Apply changes, bump revision number, and exit mode
no Negate a command or set its defaults
reset Abandon current changes and reread current database
show Show database information
vlan Add, delete, or modify values associated with a single VLAN
vtp Perform VTP administrative functions.
switchname(vlan)#vlan ?
<1-1005> ISL VLAN index
switchname(vlan)#vlan 1 ?
are Maximum number of All Route Explorer hops for this VLAN
backupcrf Backup CRF mode of the VLAN
bridge Bridging characteristics of the VLAN
media Media type of the VLAN
mtu VLAN Maximum Transmission Unit
name Ascii name of the VLAN
parent ID number of the Parent VLAN of FDDI or Token Ring type VLANs
ring Ring number of FDDI or Token Ring type VLANs
said IEEE 802.10 SAID
state Operational state of the VLAN
ste Maximum number of Spanning Tree Explorer hops for this VLAN
stp Spanning tree characteristics of the VLAN
tb-vlan1 ID number of the first translational VLAN for this VLAN (or zero
if none)
tb-vlan2 ID number of the second translational VLAN for this VLAN (or zero
if none)
switchname(vlan)#vlan 1 state ?
active VLAN Active State
suspend VLAN Suspended State
switchname(vlan)#vlan 1 state active (enter)
This will make the VLAN active.
Note that it "works" even when there is no help.
There's a way to do it for CAT OS, but I only have VTP clients on my few remaining Cat OS switches.
Good luck -
Nick
(PS - if this helps, please 'rate' the answer ! :-) )

Bringing all datasources to target systems

Hi,
What would you recommend about bringing and activating all datasources available on the system to another target system? We have only 2-system landscape. I think that when the replication happens, it will take awhile.
Should I just bring and activate only those that are required and bring them over to the target system only when necessary?
Thanks

Bring them when required.
In R/3, you need not have to transport the ones you dont need.
Once you get them to the target system of R/3, you can replicate only that in BW.
Ravi Thothadri

Creating VLAN on Cisco 3800 Series

Hello
I am new to networking. We have a Cisco 3800 series router with 64 ports. We have connected servers and PC's directly to the back of the router. Almost all of the ports are used with the exception of few. We would like to create a VLAN for the remaining few ports. I am able to telnet to the router or connect directly using hyper terminal.
I have been told that we cannot create VLAN's directly on the router. For that purpose we need to first get a switch and connect the switch to the router, then create VLAN’s using the switch. Can someone please provide some tips? Any suggestions would be nice…Thanks

Appreciate you getting back. Here is the "show vlan-switch" output
----------------------->
#show vlan-switch
VLAN Name                             Status    Ports
1    default                          active
1002 fddi-default                     active
1003 token-ring-default               active
1004 fddinet-default                  active
1005 trnet-default                    active
VLAN Type SAID       MTU   Parent RingNo BridgeNo Stp BrdgMode Trans1 Trans2
1    enet 100001     1500 -      -      -        -    -        1002   1003
1002 fddi 101002     1500 -      -      -        -    -        1      1003
1003 tr    101003     1500 1005   0      -        -    srb      1      1002
1004 fdnet 101004     1500 -      -      1        ibm -        0      0
1005 trnet 101005     1500 -      -      1        ibm -        0      0
---------------------->
As before I do not see any VLAN's set up. How come all the ports are not showing up on default VLAN 1. Maybe I can create a new VLAN and assign 2 or 3 ports to it. Please advise...Thanks

6509 Uplink to ASA with Vlan Pair

I have the following topology:
6509---->ASA----->Internet.
My 6509 have a IDSM.
intrusion-detection module 3 management-port access-vlan 2
intrusion-detection module 3 data-port 1 trunk allowed-vlan 352,603,1352,1603
I want to put the IDSM between 6509 and ASA.
6509 have a vlan 603 where Inside ASA is connected and I already created vlan 1603 to briding with 603, this way
I put the Inside cable of the ASA to vlan 1603, before was connected on vlan 603 but when I changed vlan switchport
of the ASA (603 to vlan 1603) my vlan 603 goes down and i can't access the internet.
Vlan 603 Goes Down because there are no users connected them but I thinked that How IDSM briding 603 with 1603
this vlan 603 will be UP again, but doesn't works.
How can I configure the IDM to UP this Vlan?

I assume the switch itself has a vlan 603 interface, and it is this vlan 603 interface that is going down.
By default the IDSM-2's data-ports are configured for "autostate exclude" which means that is the IDSM-2 port and the switches vlan interface are the only things on the vlan, then the switch will bring down it's interface. The switch excludes the IDSM-2 interface when looking for other ports on the vlan.
There is a command:
intrusion-detection module 3 data-port 1 autostate include
With this command the IDSM-2 port will now be included in the list of ports to watch, and the switch should now bring up its vlan 603 interface.
You can see the list of available commands for the IDSM-2 here:
http://www.cisco.com/en/US/docs/security/ips/7.0/configuration/guide/cli/cli_idsm2.html#wp1032690

2950 vlan limitation

Is there any way around the limit of 64 vlans on a 2950? We have a customer with a vtp enabled network with a mix of older Cisco switches and we have exceeded the 64 vlan limit supported by some of these switches. The only solution seems to be to manually add the new vlans to the switches. Can vtp advertisements be blocked for specified vlans?

By reading the below my interpretation is that the EI will support 250 vlans but will only support 64 individual instances of spanning tree pvst+ . Maybe I'm wrong but that is what it looks like .
Catalyst 2950 switches that run the standard software image (SI) support 64 VLANs; Catalyst 2950 and Catalyst 2955 switches that run the enhanced software image (EI) support 250 VLANs. Refer to the release notes for the list of switches that support each image. VLANs are identified with a number from 1 to 4094 when the EI is installed and 1 to 1005 when the SI is installed. VLAN IDs 1002 through 1005 are reserved for Token Ring and FDDI VLANs. VTP only learns normal-range VLANs, with VLAN IDs 1 to 1005; VLAN IDs greater than 1005 are extended-range VLANs and are not stored in the VLAN database. The switch must be in VTP transparent mode when you create VLAN IDs from 1006 to 4094.
The switch supports per-VLAN spanning-tree plus (PVST+) and rapid PVST+ with a maximum of 64 spanning-tree instances. One spanning-tree instance is allowed per VLAN. See the "Normal-Range VLAN Configuration Guidelines" section for more information about the number of spanning-tree instances and the number of VLANs. The switch supports IEEE 802.1Q trunking for sending VLAN traffic over Ethernet ports.
The switch supports 64 spanning-tree instances. If a switch has more active VLANs than supported spanning-tree instances, spanning tree can be enabled on 64 VLANs and is disabled on the remaining VLANs. If you have already used all available spanning-tree instances on a switch, adding another VLAN anywhere in the VTP domain creates a VLAN on that switch that is not running spanning-tree. If you have the default allowed list on the trunk ports of that switch (which is to allow all VLANs), the new VLAN is carried on all trunk ports. Depending on the topology of the network, this could create a loop in the new VLAN that would not be broken, particularly if there are several adjacent switches that all have run out of spanning-tree instances. You can prevent this possibility by setting allowed lists on the trunk ports of switches that have used up their allocation of spanning-tree instances.
If the number of VLANs on the switch exceeds the number of supported spanning tree instances, we recommend that you configure the IEEE 802.1S Multiple STP (MSTP) on your switch to map multiple VLANs to a single STP instance. For more information about MSTP, see Chapter 15, "Configuring MSTP."

1 IP subent for 2 VLANs? Possible?

Hi Sir,
I have a few questions on Vlan and IP subnet.
Q1. Can I have one subnet used on 2 Vlans? From my understanding, it is recommended to have one IP subnet used for one VLAN.
Q2. If I can use 1 IP subnet which has a prefix of /23 for 2 VLANs, then under what circumstances that we have to use this approach?
Q3.How can I use 1 IP subnet for 2 VLANs? Any sample of configuration guide?
Thank you.
Regards,
Delon

Delon,
basically what you are going to do to make this work is take a L3 switch and build the two vlans you want (will refer to them as X and Y) in the SUP
Example:
console (enable) set vlan x name x state active
vlan x created
console (enable) set vlan y name y state active
vlan y created
Now you are going to get into the layer 3 portion of the L3 device, whatever that may be, and assuming you are using 1 class C subnet for your IP space, your command structure would look something like this
(# = whatever IP structure you want to use)
router#(config) int vlan x
router#(config-int) ip add #.#.#.1 255.255.255.128
router#(config-int) no shut
router#(config-int) int vlan y
router#(config-int) ip add #.#.#.129 255.255.255.128
router#(config-int) no shut
again, this is a very basic configuration! Depending on the piece of equipment you are trying to configure this on... you should do some research on intervlan routing. 9 times out of 10 depending on the equipment, you will find step by step procedures more taylored to your needs

Extended Vlans matters on N5K

Hello there,
Looking for some help on extended vlans design. Customer is using 90% of extented VLANs as follows based on exclusive services:
1200-1499
1700-1999
1500-1799
Total of 897 VLANs.
First question is: Do you know if extentend VLANs count as active VLANs in the 512 limit or we should not worry as this limit is only for normal VLANs? The datasheet is not clear enough and does not say if this limit is for both.
Second question is: Supposing question 1 is ok, when allowing these vlans in the trunk, should we also create these VLANs or they are already active (according to conf guide), there is, should we need to issue "vlan 1200" in conf mode for instance?
Thank you!

This was a limitation with older VTP implementation(extended VLANs were not supported when VTP was first designed). With VTP version 3, extended VLANs are supported
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat6000/sw_8_5/confg_gd/vlans.htm#wp1090061

Virtualisation - trunking Vlans

Hi,
I am working on a requirement on virtualisation involving Business crtical applications in multiple data centers. The challenges being currently faced are:
1. The 3 Tier architecture with web servers, app servers and db servers to be virtualised with common ESX hosts along with multiple other intranet applications. Issues around security between environments, management of ESX, logging etc.
2. multiple swtiched environments to be virtualized with clash of Vlan id's, Vlan in excess on 512 to be trunked.
3. The ultimate goal is to go for the complete virtualised environment with full DR capability and flexibility akin Cloud computing.
4. Can we think of Q in Q support on Nexus 1000v?
Any help in untangling this situation will be highly appreciated.
regds/John

John,
With 512 VLANs just keep in mind you are at the upper limit of Nexus 1000V number of active VLANs supported (512).
While the Nexus 1000V does not support Q-in-Q, the best place to implement such a feature would be at the physical switch layer anyway.
Or perhaps another approach would be to implement your own VPLS cloud to interconnect the various switched environments together. The VLAN #'s dont need to be the same at each location, you could for example have VLAN 10 at Site A bridged to VLAN 20 at Site B. The advantage of VPLS over plain Q-in-Q would be preserving STP isolation and autonomy between sites.
Also, talk to your Cisco SE about OTV for Nexus 7000 :)
Cheers,
Brad
p.s. please rate if helpful

Vlan 1 Pruning eligibility C3750-V2

I am looking for clarification of vlan pruning; I have seen documentation that leads me to understand that vlans 1,1002-1005 are not eligible for vlan pruning as it carries management traffic such as CDP, so even if a switch has no active vlan 1 ports and the trunk native vlan has been changed vlan 1 will still not be pruned from the trunk.
This is an offshoot from a problem I raised in the following discussion in which vlan 1 is being pruned from trunks connected to a C3750-V2 but not when connected to a C3750:
https://supportforums.cisco.com/discussion/12272906/spanning-tree-root-bridge-dispute-c3750-v2
IOS version: 15-0-2.SE5

That is correct. However on the old 3750 stacks there are no active vlan 1 ports and the native vlan has been changed and vlan remains in a forwarding state. I thought the default vlan always stayed in a forwarding state, part of the reason vlan 1 cannot be deleted, to handle management traffic such as cdp (cdp is working across the trunk). I guess that makes it impractical to ever change the native vlan and a problem if you have security people who still believe vlan hopping is more than a theoretical threat. (As an after thought turning off VTP pruning also fixes the problem)
Thanks for responding

Trunking between separate buildings with same vlan numbering scheme

Hello
I have (2) warehouses physically next to each other.
Each warehouse has it's own WAN link
My Vlan design is the same across all my sites where each site has (Vlan 10 - 15) using a site specific subnet ip scheme.
I am now going to run a fiber link between my (2) warehouses and can create a trunk between the sites.
I am pretty sure of the answer but I think I am going to have to re-vlan one of the warehouses so I can add each sites vlans to the trunk.
That seems like a mid-major overhaul to one of the sites
Does anyone have any experience with this type of design and provide some guidance on steps to follow?

Many thanks, Jon. You are correct, I had not mentioned my intent to move servers around, originally.
What is not working, is that I cannot ping Houston from Atlanta and viceversa. For example, If I am logged into the ATL switch, I try to ping the HOU switch, but get no reply. In this example, Let's say that ATL switch is 10.11.1.2.. If I try to ping 10.11.2.2 (HOU) nothing. 10.11.1.x traffic should be tagged as vlan 10 in ATL, and 10.11.2.x should be NOW tagged as vlan 112 in HOU.
ATL
garfield#sh vlan brief
VLAN Name                             Status    Ports
1    default                          active    Gi1/0/49, Gi1/0/50, Gi1/0/51
                                                Gi1/0/52, Gi2/0/49, Gi2/0/50
                                                Gi2/0/52
5    VLAN0005                         active
10   VLAN0010                         active    Gi1/0/20, Gi1/0/29, Gi1/0/30
                                                Gi1/0/31, Gi1/0/32, Gi1/0/33
                                                Gi1/0/34, Gi1/0/35, Gi1/0/36
                                                Gi1/0/37, Gi1/0/38, Gi1/0/39
                                                Gi1/0/40, Gi1/0/41, Gi1/0/42
                                                Gi1/0/43, Gi1/0/44, Gi1/0/45
                                                Gi1/0/46, Gi1/0/47, Gi1/0/48
                                                Gi2/0/20, Gi2/0/29, Gi2/0/30
                                                Gi2/0/31, Gi2/0/32, Gi2/0/33
                                                Gi2/0/34, Gi2/0/35, Gi2/0/36
                                                Gi2/0/37, Gi2/0/38, Gi2/0/39
                                                Gi2/0/40, Gi2/0/41, Gi2/0/42
                                                Gi2/0/43, Gi2/0/44, Gi2/0/45
                                                Gi2/0/46, Gi2/0/47, Gi2/0/48
41   VLAN0041                         active
70   VLAN0070                         active
72   VLAN0072                         active    Gi1/0/1, Gi1/0/2, Gi2/0/1
                                                Gi2/0/2
110 VLAN0110                         active
112 VLAN0112                         active    Gi2/0/27
172 VLAN0172                         active    Gi1/0/5, Gi1/0/6, Gi1/0/7
                                                Gi1/0/8, Gi2/0/5, Gi2/0/6
                                                Gi2/0/7, Gi2/0/8
192 VLAN0192                         active    Gi1/0/3, Gi1/0/4, Gi1/0/9
                                                Gi1/0/10, Gi1/0/11, Gi1/0/12
                                                Gi1/0/13, Gi1/0/14, Gi1/0/15
                                                Gi1/0/16, Gi1/0/17, Gi1/0/18
                                                Gi1/0/19, Gi1/0/21, Gi1/0/22
                                                Gi1/0/23, Gi1/0/24, Gi1/0/25
                                                Gi1/0/26, Gi1/0/27, Gi2/0/3
                                                Gi2/0/4, Gi2/0/9, Gi2/0/10
                                                Gi2/0/11, Gi2/0/12, Gi2/0/13
                                                Gi2/0/14, Gi2/0/15, Gi2/0/16
                                                Gi2/0/17, Gi2/0/18, Gi2/0/19
                                                Gi2/0/21, Gi2/0/22, Gi2/0/23
                                                Gi2/0/24, Gi2/0/25, Gi2/0/26
                                                Gi2/0/28
222 VLAN0222                         active
310 VLAN0310                         active
722 VLAN0722                         active
VLAN Name                             Status    Ports
999 VLAN0999                         active
1002 fddi-default                     act/unsup
1003 token-ring-default               act/unsup
1004 fddinet-default                  act/unsup
1005 trnet-default                    act/unsup
garfield#
garfield#sh vtp status
VTP Version                     : running VTP1 (VTP2 capable)
Configuration Revision          : 16
Maximum VLANs supported locally : 1005
Number of existing VLANs        : 18
VTP Operating Mode              : Server
VTP Domain Name                 : SU4
VTP Pruning Mode                : Disabled
VTP V2 Mode                     : Disabled
VTP Traps Generation            : Disabled
MD5 digest                      : 0xD3 0x52 0x2B 0xBC 0x96 0x08 0xB9 0x31
Configuration last modified by 0.0.0.0 at 9-2-95 06:58:04
Local updater ID is 10.11.1.2 on interface Vl10 (lowest numbered VLAN interface
found)
garfield#
garfield#sh vtp ?
counters VTP statistics
password VTP password
status    VTP domain status
garfield#sh vtp counters
VTP statistics:
Summary advertisements received    : 709
Subset advertisements received     : 3
Request advertisements received    : 0
Summary advertisements transmitted : 2076
Subset advertisements transmitted : 16
Request advertisements transmitted : 0
Number of config revision errors   : 0
Number of config digest errors     : 0
Number of V1 summary errors        : 0
VTP pruning statistics:
Trunk            Join Transmitted Join Received    Summary advts received from
                                                   non-pruning-capable device
Gi1/0/28            1                1                0
Gi2/0/51            0                0                0
HOU
calvin#sh vlan brief
VLAN Name                             Status    Ports
1    default                          active    Gi1/0/49, Gi1/0/50, Gi1/0/51
                                                Gi1/0/52, Gi2/0/49, Gi2/0/50
                                                Gi2/0/52
5    VLAN0005                         active    Gi1/0/33, Gi1/0/34, Gi1/0/35
                                                Gi1/0/36, Gi1/0/37, Gi1/0/38
                                                Gi1/0/42, Gi1/0/43, Gi1/0/44
                                                Gi1/0/45, Gi1/0/46, Gi1/0/47
                                                Gi1/0/48, Gi2/0/33, Gi2/0/34
                                                Gi2/0/35, Gi2/0/36, Gi2/0/37
                                                Gi2/0/38, Gi2/0/42, Gi2/0/43
                                                Gi2/0/44, Gi2/0/45, Gi2/0/46
                                                Gi2/0/47, Gi2/0/48, Po11, Po12
                                                Po13
10   VLAN0010                         active
41   VLAN0041                         active    Gi1/0/11, Gi1/0/12, Gi1/0/13
                                                Gi1/0/14, Gi1/0/15, Gi1/0/16
                                                Gi1/0/20, Gi2/0/11, Gi2/0/12
                                                Gi2/0/13, Gi2/0/14, Gi2/0/15
                                                Gi2/0/16, Gi2/0/20
70   VLAN0070                         active    Gi1/0/1, Gi1/0/2, Gi1/0/3
                                                Gi1/0/4, Gi2/0/1, Gi2/0/2
                                                Gi2/0/3, Gi2/0/4
72   VLAN0072                         active
110 VLAN0110                         active
112 VLAN0112                         active    Gi1/0/21, Gi1/0/22, Gi1/0/23
                                                Gi1/0/24, Gi1/0/25, Gi1/0/26
                                                Gi1/0/27, Gi1/0/28, Gi1/0/29
                                                Gi1/0/30, Gi1/0/31, Gi1/0/32
                                                Gi2/0/21, Gi2/0/22, Gi2/0/23
                                                Gi2/0/24, Gi2/0/25, Gi2/0/26
                                                Gi2/0/27, Gi2/0/28, Gi2/0/29
                                                Gi2/0/30, Gi2/0/31, Gi2/0/32
172 VLAN0172                         active
192 VLAN0192                         active
222 VLAN0222                         active
310 VLAN0310                         active
722 VLAN0722                         active    Gi1/0/5, Gi1/0/6, Gi1/0/7
                                                Gi1/0/8, Gi1/0/9, Gi1/0/10
                                                Gi2/0/5, Gi2/0/6, Gi2/0/7
                                                Gi2/0/8, Gi2/0/9, Gi2/0/10
999 VLAN0999                         active
1002 fddi-default                     act/unsup
1003 token-ring-default               act/unsup
1004 fddinet-default                  act/unsup
1005 trnet-default                    act/unsup
calvin#
calvin#sh vtp status
VTP Version capable             : 1 to 3
VTP version running             : 1
VTP Domain Name                 :
VTP Pruning Mode                : Disabled
VTP Traps Generation            : Enabled
Device ID                       : 0015.c6fb.2000
Configuration last modified by 192.168.130.2 at 0-0-00 00:00:00
Feature VLAN:
VTP Operating Mode                : Transparent
Maximum VLANs supported locally   : 1005
Number of existing VLANs          : 18
Configuration Revision            : 0
MD5 digest                        : 0x80 0x93 0xE1 0x4B 0xCE 0xB2 0xB5 0xD5
                                    0xC6 0x9B 0x12 0xD7 0x03 0xBE 0xFF 0xBD
calvin#
calvin#sh vtp int gi 2/0/51
Interface               VTP Status
GigabitEthernet2/0/51    enabled
calvin#sh vtp counters
VTP statistics:
Summary advertisements received    : 0
Subset advertisements received     : 0
Request advertisements received    : 0
Summary advertisements transmitted : 0
Subset advertisements transmitted : 0
Request advertisements transmitted : 0
Number of config revision errors   : 0
Number of config digest errors     : 0
Number of V1 summary errors        : 0
VTP pruning statistics:
Trunk            Join Transmitted Join Received    Summary advts received from
                                                   non-pruning-capable device
Gi2/0/51            0                0                0
Po1                 0                0                0
Po2                 0                0                0
Po3                 0                0                0
calvin#
Thanks.

Bringing Up/Activating VLAN on 2900

Similar Messages

Maybe you are looking for