- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- 8212, ip routing and access point
Switches, Hubs, and Modems
1754021
Members
7197
Online
108811
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-07-2011 11:50 AM
04-07-2011 11:50 AM
8212, ip routing and access point
Dear sirs,
in the attached file you can see our network map.
Now we want to install, on each floor, some access point and create two new vlan (internet and intranet) that must remain separate between them.
As you will see below, in the master switch configuration, ip routing was enabled to allow the sharing of existing vlan.
Now these new Vlan must have different policies.
Can I ask you advice on how to update the configuration.
Thanks in advance.
***
Running configuration:
; J9091A Configuration Editor; Created on release #K.15.02.0005
hostname "CSMASTERIP128004"
module 1 type J8706A
module 2 type J8702A
module 3 type J8702A
ip default-gateway 192.168.128.1
ip routing
vlan 1
name "DEFAULT_VLAN"
untagged C1-C24
tagged A1,A3,A5,A7,A9,A11,A13,A15,A17,A19
no untagged A2,A4,A6,A8,A10,A12,A14,A16,A18,A20-A24,B1-B24
no ip address
exit
vlan 10
name "floor0"
untagged A2,A4,A6-A24,B2-B9,B16-B21,B23-B24
ip helper-address 192.168.140.10
ip address 192.168.128.4 255.255.252.0
tagged A1,A3,A5,B1
exit
vlan 11
name "floor1"
ip helper-address 192.168.140.10
ip address 192.168.132.4 255.255.252.0
tagged A7,A9,A11,A19,B1
exit
vlan 12
name "floor2"
ip helper-address 192.168.140.10
ip address 192.168.136.4 255.255.252.0
tagged A13,A15,A17,B1
exit
vlan 99
name "voip"
untagged B10-B15
ip helper-address 192.168.140.10
ip address 172.16.100.252 255.255.252.0
tagged A1,A3,A5,A7,A9,A11,A13,A15,A17,A19,B1
exit
vlan 98
name "serverfarm"
untagged B22
ip helper-address 192.168.140.10
ip address 192.168.140.4 255.255.255.0
tagged A1,A3,A5,A7,A9,A11,A13,A15,A17,A19,B1
exit
power-over-ethernet pre-std-detect
ip route 10.4.1.0 255.255.255.0 192.168.128.30
ip route 10.4.2.0 255.255.255.0 192.168.128.30
ip route 10.4.3.0 255.255.255.0 192.168.128.30
ip route 10.4.4.0 255.255.255.0 192.168.128.30
ip route 10.4.5.0 255.255.255.0 192.168.128.30
ip route 10.4.6.0 255.255.255.0 192.168.128.30
ip route 10.4.7.0 255.255.255.0 192.168.128.30
ip route 10.4.8.0 255.255.255.0 192.168.128.30
ip route 10.4.9.0 255.255.255.0 192.168.128.30
ip route 10.4.10.0 255.255.255.0 192.168.128.30
ip route 10.4.11.0 255.255.255.0 192.168.132.30
ip route 10.4.12.0 255.255.255.0 192.168.128.30
ip route 10.4.13.0 255.255.255.0 192.168.128.30
ip route 10.4.14.0 255.255.255.0 192.168.128.30
ip route 10.4.15.0 255.255.255.0 192.168.128.30
ip route 10.4.16.0 255.255.255.0 192.168.128.30
ip route 10.4.17.0 255.255.255.0 192.168.128.30
ip route 10.4.18.0 255.255.255.0 192.168.128.30
ip route 10.4.19.0 255.255.255.0 192.168.128.30
ip route 10.4.20.0 255.255.255.0 192.168.128.30
ip route 192.168.0.0 255.255.128.0 192.168.128.1
router vrrp
snmp-server community "ausl2" unrestricted
snmp-server host 192.168.140.10 community "public"
spanning-tree
spanning-tree config-name "MSTP"
spanning-tree config-revision 1
spanning-tree instance 1 vlan 10-12
spanning-tree instance 1 priority 0
spanning-tree instance 2 vlan 98 99
spanning-tree instance 2 priority 1
spanning-tree priority 0
vlan 10
vrrp vrid 10
owner
virtual-ip-address 192.168.128.4 255.255.252.0
priority 255
enable
exit
exit
vlan 11
vrrp vrid 11
owner
virtual-ip-address 192.168.132.4 255.255.252.0
priority 255
enable
exit
exit
vlan 12
vrrp vrid 12
owner
virtual-ip-address 192.168.136.4 255.255.252.0
priority 255
enable
exit
exit
vlan 98
vrrp vrid 98
backup
virtual-ip-address 192.168.140.5 255.255.255.0
enable
exit
exit
vlan 99
vrrp vrid 99
backup
virtual-ip-address 172.16.100.253 255.255.252.0
enable
exit
exit
no autorun
no dhcp config-file-update
no dhcp image-file-update
password manager
in the attached file you can see our network map.
Now we want to install, on each floor, some access point and create two new vlan (internet and intranet) that must remain separate between them.
As you will see below, in the master switch configuration, ip routing was enabled to allow the sharing of existing vlan.
Now these new Vlan must have different policies.
Can I ask you advice on how to update the configuration.
Thanks in advance.
***
Running configuration:
; J9091A Configuration Editor; Created on release #K.15.02.0005
hostname "CSMASTERIP128004"
module 1 type J8706A
module 2 type J8702A
module 3 type J8702A
ip default-gateway 192.168.128.1
ip routing
vlan 1
name "DEFAULT_VLAN"
untagged C1-C24
tagged A1,A3,A5,A7,A9,A11,A13,A15,A17,A19
no untagged A2,A4,A6,A8,A10,A12,A14,A16,A18,A20-A24,B1-B24
no ip address
exit
vlan 10
name "floor0"
untagged A2,A4,A6-A24,B2-B9,B16-B21,B23-B24
ip helper-address 192.168.140.10
ip address 192.168.128.4 255.255.252.0
tagged A1,A3,A5,B1
exit
vlan 11
name "floor1"
ip helper-address 192.168.140.10
ip address 192.168.132.4 255.255.252.0
tagged A7,A9,A11,A19,B1
exit
vlan 12
name "floor2"
ip helper-address 192.168.140.10
ip address 192.168.136.4 255.255.252.0
tagged A13,A15,A17,B1
exit
vlan 99
name "voip"
untagged B10-B15
ip helper-address 192.168.140.10
ip address 172.16.100.252 255.255.252.0
tagged A1,A3,A5,A7,A9,A11,A13,A15,A17,A19,B1
exit
vlan 98
name "serverfarm"
untagged B22
ip helper-address 192.168.140.10
ip address 192.168.140.4 255.255.255.0
tagged A1,A3,A5,A7,A9,A11,A13,A15,A17,A19,B1
exit
power-over-ethernet pre-std-detect
ip route 10.4.1.0 255.255.255.0 192.168.128.30
ip route 10.4.2.0 255.255.255.0 192.168.128.30
ip route 10.4.3.0 255.255.255.0 192.168.128.30
ip route 10.4.4.0 255.255.255.0 192.168.128.30
ip route 10.4.5.0 255.255.255.0 192.168.128.30
ip route 10.4.6.0 255.255.255.0 192.168.128.30
ip route 10.4.7.0 255.255.255.0 192.168.128.30
ip route 10.4.8.0 255.255.255.0 192.168.128.30
ip route 10.4.9.0 255.255.255.0 192.168.128.30
ip route 10.4.10.0 255.255.255.0 192.168.128.30
ip route 10.4.11.0 255.255.255.0 192.168.132.30
ip route 10.4.12.0 255.255.255.0 192.168.128.30
ip route 10.4.13.0 255.255.255.0 192.168.128.30
ip route 10.4.14.0 255.255.255.0 192.168.128.30
ip route 10.4.15.0 255.255.255.0 192.168.128.30
ip route 10.4.16.0 255.255.255.0 192.168.128.30
ip route 10.4.17.0 255.255.255.0 192.168.128.30
ip route 10.4.18.0 255.255.255.0 192.168.128.30
ip route 10.4.19.0 255.255.255.0 192.168.128.30
ip route 10.4.20.0 255.255.255.0 192.168.128.30
ip route 192.168.0.0 255.255.128.0 192.168.128.1
router vrrp
snmp-server community "ausl2" unrestricted
snmp-server host 192.168.140.10 community "public"
spanning-tree
spanning-tree config-name "MSTP"
spanning-tree config-revision 1
spanning-tree instance 1 vlan 10-12
spanning-tree instance 1 priority 0
spanning-tree instance 2 vlan 98 99
spanning-tree instance 2 priority 1
spanning-tree priority 0
vlan 10
vrrp vrid 10
owner
virtual-ip-address 192.168.128.4 255.255.252.0
priority 255
enable
exit
exit
vlan 11
vrrp vrid 11
owner
virtual-ip-address 192.168.132.4 255.255.252.0
priority 255
enable
exit
exit
vlan 12
vrrp vrid 12
owner
virtual-ip-address 192.168.136.4 255.255.252.0
priority 255
enable
exit
exit
vlan 98
vrrp vrid 98
backup
virtual-ip-address 192.168.140.5 255.255.255.0
enable
exit
exit
vlan 99
vrrp vrid 99
backup
virtual-ip-address 172.16.100.253 255.255.252.0
enable
exit
exit
no autorun
no dhcp config-file-update
no dhcp image-file-update
password manager
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP