New with VLAN VTP need help

danhngo9495 · ‎10-24-2018

I'm working on a little assignment, do not want any real answer but I post part of it because I'm confusing about some stuff that I was ask to do. I've been eading and struggling for weeks but could not get it. So looking for some further explanation.

this is running on packet tracer

………….

1) All switches in this simulation will be 24 port 2960s.

2) Start with 3 access layer switches and 2 collapsed (core + distribution) core switches in your workspace.

3) Change the names of all devices once deployed. Change the host name where possible and the display name as well. Naming standard is as follows:

possible types: PC, SW, RTR

possible topology locations: DESKTOP, ACCESS, CORE, EDGE, MGMT

possible numbers (each location): 1-20

Example: SW_ACCESS_1

4) Switching standards are as follows:

Only Core Switch 1 will be accessible via SSH from the management network with the following parameters:

domain: 4011rocks.com

username: network

password: rocks

enable secret: networkrocks

Testing hint: ssh -l 4011rocks.com <ip>

You must be able to log in remotely from the management station.

Cisco proprietary standards are to be utilized throughout the switching environment unless otherwise specified.

Each switch will have 1 single cross connect to every other switch in the access layer.

Cross connects at the access layer are gigabit ethernet only.

Uplink ports can only utilize fast ethernet ports in the range of 16-24. Management network ports are reserved for port 15. The remainder of the ports are reserved for end user devices that start at port 1 and proceed from there to port 14 as needed.

Uplinks must be a minimum of 200 Mbps.

All access switches will have an uplink path to every core switch.

Access layer end user ports need appropriate STP protections to ensure no BPDUs can flow into those ports and impact topology changes.

Access layer end user ports can skip the listening, learning, and forwarding states of the STP negotiation.

Uplinks and cross connects can use the STP feature that allows for indirect link failures to be detected more quickly. ?? ( is that Backbonefast , if it is I could not find it it CLI using Sw#(config) spanning-tree b? - could not see the command)

VLAN 1 is always reserved for management traffic. VLAN 2 is reserved for end user devices. VTP domain is INET4011.

The VLAN database will be controlled by the core switch. All other devices will listen to that switch for VLAN changes.

Management network switching is exempt from VLAN and STP standards as well as uplink and cross connect standards.

Management network will have 1 un-routed IP-based VLAN.

(Totally lost at this point, I cannot understand the requirement)

All infrastructure devices (non-endpoint) will have a management switch connection except the access layer. This includes routers and switches.

Datacenter edge switch will have 2 vlans. Vlan 1 is for mangement, vlan 2 is for the production network.

All switch interfaces should be named according to what is plugged in at the remote end of the link as follows:

Uplinks: Uplink to <Device_Name>

PCs: <PC_Name>

Cross Connects: Cross Connect to <Device_Name>

Port Channel Member: PORT-CHANNEL <Port Channel Number>

Management Interface: MGMT Switch Link

Routers: <Router_Name>

One core switch will be the STP root for the management vlan and the other will be the STP root for the production vlan.

underlined part are my confusing

danhngo9495 · ‎10-24-2018

Here is the rest of the requirement, I may have futher question when working along with it, pretty new to networking so don't know where or who to ask question.

Port Channel Member: PORT-CHANNEL <Port Channel Number>

Management Interface: MGMT Switch Link

Routers: <Router_Name>

One core switch will be the STP root for the management vlan and the other will be the STP root for the production vlan.

5) Connect 3 PCs to each access switch.

6) Assign IP addresses as follows:

The core production network will be 192.168.10.0 with a subnet mask that will allow for 126 hosts.

The first 10 IP addresses in the production range are reserved. Start addressing of hosts with the next available IP.

The default gateway is 192.168.10.1 which is also the Internet router.

The management network is 10.10.10.0 and allows for 254 hosts.

The management PC is 10.10.10.254

Infrastructure management interfaces come from the management network range.

Loopbacks are unrouted on the network 172.31.1.0/24 with the last octet matching the router number in the router name.

WAN PC is 172.16.1.2/24. Gateway is 172.16.1.1. DNS is 8.8.8.2.

Internet Web Server is 8.8.8.2/24. Gateway is 8.8.8.1.

Datacenter Server is 172.17.1.5/24. Gateway is 172.17.1.1.

HSRP gets a VIP of x.x.x.1 on the 172.17.1.0/24 network with the real being x.x.x.2 and x.x.x.3.

HSRP gets a VIP of x.x.x.4 on the 192.168.10.0/25 network with the real being x.x.x.2 and x.x.x.3.

The WAN router gets 192.168.10.5/25.

7) Layer 3 devices (Cisco 2911 routers) are connected as follows:

Connect RTR_EDGE_1 to SW_CORE_2. This is the Internet router and Internet Web Server is connected to it.

Connect RTR_EDGE_2 to SW_CORE_1 and RTR_EDGE_3 to SW_CORE_2. This is a redundant pair of datacenter routers serving the Datacenter server network. Datacenter Server is first connected to a switch that connects to both datacenter routers.

Connect RTR_EDGE_4 to SW_CORE_2. This is the WAN router and WAN PC is connected to it.

A management PC is connected to the Management Switch.

8) Routing is configured as follows:

Use a vendor neutral IGP running a single area.

Inject a default route from the most optimal location.

Do not put the Internet network into the routing protocol.

The management network is unrouted ALWAYS.

All routers and connected networks are running in the routing protocol EXCEPT the datacenter network. HSRP is running on both sides of that router pair.

For routing the datacenter network use static routing injected into the routing protocol from one location only.

Port Channel Member: PORT-CHANNEL <Port Channel Number>

Management Interface: MGMT Switch Link

Routers: <Router_Name>

One core switch will be the STP root for the management vlan and the other will be the STP root for the production vlan.

5) Connect 3 PCs to each access switch.

6) Assign IP addresses as follows:

The core production network will be 192.168.10.0 with a subnet mask that will allow for 126 hosts.

The first 10 IP addresses in the production range are reserved. Start addressing of hosts with the next available IP.

The default gateway is 192.168.10.1 which is also the Internet router.

The management network is 10.10.10.0 and allows for 254 hosts.

The management PC is 10.10.10.254

Infrastructure management interfaces come from the management network range.

Loopbacks are unrouted on the network 172.31.1.0/24 with the last octet matching the router number in the router name.

WAN PC is 172.16.1.2/24. Gateway is 172.16.1.1. DNS is 8.8.8.2.

Internet Web Server is 8.8.8.2/24. Gateway is 8.8.8.1.

Datacenter Server is 172.17.1.5/24. Gateway is 172.17.1.1.

HSRP gets a VIP of x.x.x.1 on the 172.17.1.0/24 network with the real being x.x.x.2 and x.x.x.3.

HSRP gets a VIP of x.x.x.4 on the 192.168.10.0/25 network with the real being x.x.x.2 and x.x.x.3.

The WAN router gets 192.168.10.5/25.

7) Layer 3 devices (Cisco 2911 routers) are connected as follows:

Connect RTR_EDGE_1 to SW_CORE_2. This is the Internet router and Internet Web Server is connected to it.

Connect RTR_EDGE_2 to SW_CORE_1 and RTR_EDGE_3 to SW_CORE_2. This is a redundant pair of datacenter routers serving the Datacenter server network. Datacenter Server is first connected to a switch that connects to both datacenter routers.

Connect RTR_EDGE_4 to SW_CORE_2. This is the WAN router and WAN PC is connected to it.

A management PC is connected to the Management Switch.

8) Routing is configured as follows:

Use a vendor neutral IGP running a single area.

Inject a default route from the most optimal location.

Do not put the Internet network into the routing protocol.

The management network is unrouted ALWAYS.

All routers and connected networks are running in the routing protocol EXCEPT the datacenter network. HSRP is running on both sides of that router pair.

For routing the datacenter network use static routing injected into the routing protocol from one location only.

Dennis Mink · ‎10-24-2018

so what is your question? and where are you getting stuck with all this?

Please remember to rate useful posts, by clicking on the stars below.

danhngo9495 · ‎10-25-2018

Management network will have 1 un-routed IP-based VLAN.

what is the un routerd IP-Base Vlan?

my current Vlan1 is management vlan

danhngo9495 · ‎10-25-2018

I also underline in the post:

The VLAN database will be controlled by the core switch. All other devices will listen to that switch for VLAN changes.

Management network switching is exempt from VLAN and STP standards as well as uplink and cross connect standards.

Management network will have 1 un-routed IP-based VLAN.

(Totally lost at this point, I cannot understand the requirement)

what do above requirement mean? just don't understand the requirement at all, "All other devices will listen to that switch for VLAN changes."

"1 un-routed IP-based VLAN."

Georg Pauwen · ‎10-25-2018

Hello,

the unrouted IP-based Vlan simply means you assign an IP address (the easiest would be to Vlan 1) from the same address space to each switch, which allows the switches to be accessed and managed.

The core switch needs to be the VTP server, and all other switches need to be VTP clients. That way, any change on the VTP server switch will be propagated to all other switches.

So on the core switch, configure:

Core#conf t

Core(config)#vtp mode server

and on the clients switches:

Client#conf t

Client(config)#vtp mode client

danhngo9495 · ‎10-26-2018

Thank you, I thought about that but did not try it, thanks for the vtp :), I'm still working on it hopefully learn some more new things :D For sure I will come up with some more question

Thanks for all the helps

danhngo9495 · ‎10-26-2018

"Uplinks and cross connects can use the STP feature that allows for indirect link failures to be detected more quickly."
very up on top, I missed that question, for that STP feature is that backbonefast ? I could not configure it, the command does not appear in the CLI

Georg Pauwen · ‎10-26-2018

Hello,

backbonefast needs to be configured globally, not on the interface(s):

Switch#conf t

Switch(config)#spanning-tree backbonefast