- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- LAN Routing
- >
- Re: VLAN ISSUES
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
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
Discussion Boards
Community
Resources
Forums
Blogs
- 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
03-05-2016 12:13 AM
03-05-2016 12:13 AM
VLAN ISSUES
Hi All,
I'm having some issues with inteervlan communication, any assistance will be welcome;
hostname "SWT-CORE"
module 1 type j9726a
ip default-gateway 172.168.1.210
ip route 0.0.0.0 0.0.0.0 172.168.1.210
ip route 192.168.100.0 255.255.255.0 vlan 30
ip routing
interface 23
flow-control
name "RouterConnection"
exit
snmp-server community "public" unrestricted
oobm
ip address dhcp-bootp
exit
vlan 1
name "DEFAULT_VLAN"
no untagged 1-19,23
ip address 192.168.200.1 255.255.255.0
exit
vlan 10
name "Data"
untagged 1-9,23
ip address 172.168.1.254 255.255.255.0
exit
vlan 30
name "Voice"
untagged 10-19
ip address 192.168.100.254 255.255.255.0
ip helper-address 172.168.1.1
exit
vlan 90
name "Common Services"
ip address 172.16.1.254 255.255.255.0
exit
spanning-tree
spanning-tree mode rapid-pvst
no tftp server
no autorun
no dhcp config-file-update
no dhcp image-file-update
password manager
sh ip route
IP Route Entries
Destination Gateway VLAN Type Sub-Type Metric Dist.
------------------ --------------- ---- --------- ---------- ---------- -----
0.0.0.0/0 172.168.1.210 10 static 1 1
127.0.0.0/8 reject static 0 0
127.0.0.1/32 lo0 connected 1 0
172.168.1.0/24 10 connected 1 0
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-05-2016 09:45 AM
03-05-2016 09:45 AM
Re: VLAN ISSUES
What's the issue?
For direct attached networks, you won't need routes like this one:
ip route 192.168.100.0 255.255.255.0 vlan 30
Is the "sh ip route output" complete? It misses some local attached networks. Are associated VLAN interfaces up?