This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Extreme Networks
- Community List
- Switching & Routing
- ExtremeSwitching (EXOS/Switch Engine)
- RE: Add vlan to existing switch and ospf routing
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Add vlan to existing switch and ospf routing
Add vlan to existing switch and ospf routing
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
03-13-2015 12:00 AM
Not able to ping new vlan default gateway
Name VID Protocol Addr Flags Proto Ports Virtual Active router /Total
---------------------------------------------------------------------------------------
corp_CTAP_agents 3710 10.131.82.1 /24 -f----------------------- ANY 0 /1 VR-Default
CTAP-Agent 500 192.168.112.1 /24 -f----------------------- ANY 80/132 VR-Default
Default 1 --------------------------------------------- ANY 0 /0 VR-Default
EVN 501 10.20.50.1 /24 -f----------------------- ANY 1 /3 VR-Default
IPC 502 172.16.50.1 /24 -f----------------------- ANY 1 /4 VR-Default
IVN 503 192.168.50.1 /24 -f----------------------- ANY 1 /7 VR-Default
Mgmt 4095 --------------------------------------------- ANY 0 /1 VR-Mgmt
XO_VPLS_MESH 1000 10.128.254.4 /24 -f-------o--------------- ANY 1 /1 VR-Default
VLAN Interface with name corp_CTAP_agents created by user
Admin State: Enabled Tagging: 802.1Q Tag 3710
Description: None
Virtual router: VR-Default
IPv4 Forwarding: Enabled
Primary IP : 10.131.82.1/24
IPv6 Forwarding: Disabled
IPv6: None
STPD: None
Protocol: Match all unfiltered protocols
Loopback: Disabled
NetLogin: Disabled
QosProfile: None configured
Egress Rate Limit Designated Port: None configured
Flood Rate Limit QosProfile: None configured
Ports: 1. (Number of active ports=0)
Untag: 3:44
Name VID Protocol Addr Flags Proto Ports Virtual Active router /Total
---------------------------------------------------------------------------------------
corp_CTAP_agents 3710 10.131.82.1 /24 -f----------------------- ANY 0 /1 VR-Default
CTAP-Agent 500 192.168.112.1 /24 -f----------------------- ANY 80/132 VR-Default
Default 1 --------------------------------------------- ANY 0 /0 VR-Default
EVN 501 10.20.50.1 /24 -f----------------------- ANY 1 /3 VR-Default
IPC 502 172.16.50.1 /24 -f----------------------- ANY 1 /4 VR-Default
IVN 503 192.168.50.1 /24 -f----------------------- ANY 1 /7 VR-Default
Mgmt 4095 --------------------------------------------- ANY 0 /1 VR-Mgmt
XO_VPLS_MESH 1000 10.128.254.4 /24 -f-------o--------------- ANY 1 /1 VR-Default
VLAN Interface with name corp_CTAP_agents created by user
Admin State: Enabled Tagging: 802.1Q Tag 3710
Description: None
Virtual router: VR-Default
IPv4 Forwarding: Enabled
Primary IP : 10.131.82.1/24
IPv6 Forwarding: Disabled
IPv6: None
STPD: None
Protocol: Match all unfiltered protocols
Loopback: Disabled
NetLogin: Disabled
QosProfile: None configured
Egress Rate Limit Designated Port: None configured
Flood Rate Limit QosProfile: None configured
Ports: 1. (Number of active ports=0)
Untag: 3:44
20 REPLIES 20
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
03-13-2015 01:51 PM
All looks good with the configuration, if you look at your ospf config you have the following:
enable ospf export direct cost 1 type ase-type-1
enable ospf export static cost 1 type ase-type-1
This takes any direct or static configured routes and propogates them into OSPF. Your problem is that with the interface down (even though it is configured) it is not considered "up" and therefore no route. You need to have an active device or loopback turned on to test.
A quick one would be to enable loopback on the corp_CTAP_agents....
"enable loopback vlan corp_CTAP_agents" try to ping it... then disable loopback once you tested...
"disable loopback vlan corp_CTAP_agents"
enable ospf export direct cost 1 type ase-type-1
enable ospf export static cost 1 type ase-type-1
This takes any direct or static configured routes and propogates them into OSPF. Your problem is that with the interface down (even though it is configured) it is not considered "up" and therefore no route. You need to have an active device or loopback turned on to test.
A quick one would be to enable loopback on the corp_CTAP_agents....
"enable loopback vlan corp_CTAP_agents" try to ping it... then disable loopback once you tested...
"disable loopback vlan corp_CTAP_agents"
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
03-13-2015 01:44 PM
The way it's currently setup only the interface for XO_vlan is ospf enabled.
currently, the main vlan is ctap_agents = 192.168.112.1 and its a direct connect, so it's being injected into ospf. which is what i want, so 112.1 is being routed across my network to the Datacenter. so when I configured the new vlan corp_ctap_agents I want the same behavior so that is what i'm trying to figure out, why ctap_agents is being routed via ospf and not corp_ctap_agents.
Slot-1 CTAP-Cosmo-Stack.1 # show configuration ospf#
# Module ospf configuration.
#
configure ospf routerid 192.168.112.1
enable ospf
enable ospf export direct cost 1 type ase-type-1
enable ospf export static cost 1 type ase-type-1
configure ospf vlan corp_CTAP_agents priority 0
configure ospf vlan CTAP-Agent priority 0
configure ospf vlan EVN priority 0
configure ospf vlan IPC priority 0
configure ospf vlan IVN priority 0
configure ospf add vlan XO_VPLS_MESH area 0.0.0.0
configure ospf vlan XO_VPLS_MESH priority 0
* Slot-1 CTAP-Cosmo-Stack.2 #
OSPF : Enabled MPLS LSP as Next-Hop: NoRouterId : 192.168.112.1 RouterId Selection : Configured
ASBR : Yes ABR : No
ExtLSA : 24 ExtLSAChecksum : 0x9c664
OriginateNewLSA : 19632 ReceivedNewLSA : 146500
SpfHoldTime : 3 Lsa Batch Interval : 30s
CapabilityOpaqueLSA : Disabled
10M Cost : 10 100M Cost : 5
1000M Cost (1G) : 4 10000M Cost (10G) : 2
40000M Cost (40G) : 2
Router Alert : Disabled Import Policy File :
ASExternal LSALimit : Disabled Timeout (Count) : Disabled (22)
Originate Default : Disabled
SNMP Traps : Disabled
Redistribute:
Protocol Status cost Type Tag Policy
direct Enabled 1 1 0 None
static Enabled 1 1 0 None
rip Disabled 0 0 0 None
e-bgp Disabled 0 0 0 None
i-bgp Disabled 0 0 0 None
isis-level-1 Disabled 0 0 0 None
isis-level-2 Disabled 0 0 0 None
isis-level-1-external Disabled 0 0 0 None
isis-level-2-external Disabled 0 0 0 None
currently, the main vlan is ctap_agents = 192.168.112.1 and its a direct connect, so it's being injected into ospf. which is what i want, so 112.1 is being routed across my network to the Datacenter. so when I configured the new vlan corp_ctap_agents I want the same behavior so that is what i'm trying to figure out, why ctap_agents is being routed via ospf and not corp_ctap_agents.
Slot-1 CTAP-Cosmo-Stack.1 # show configuration ospf#
# Module ospf configuration.
#
configure ospf routerid 192.168.112.1
enable ospf
enable ospf export direct cost 1 type ase-type-1
enable ospf export static cost 1 type ase-type-1
configure ospf vlan corp_CTAP_agents priority 0
configure ospf vlan CTAP-Agent priority 0
configure ospf vlan EVN priority 0
configure ospf vlan IPC priority 0
configure ospf vlan IVN priority 0
configure ospf add vlan XO_VPLS_MESH area 0.0.0.0
configure ospf vlan XO_VPLS_MESH priority 0
* Slot-1 CTAP-Cosmo-Stack.2 #
OSPF : Enabled MPLS LSP as Next-Hop: NoRouterId : 192.168.112.1 RouterId Selection : Configured
ASBR : Yes ABR : No
ExtLSA : 24 ExtLSAChecksum : 0x9c664
OriginateNewLSA : 19632 ReceivedNewLSA : 146500
SpfHoldTime : 3 Lsa Batch Interval : 30s
CapabilityOpaqueLSA : Disabled
10M Cost : 10 100M Cost : 5
1000M Cost (1G) : 4 10000M Cost (10G) : 2
40000M Cost (40G) : 2
Router Alert : Disabled Import Policy File :
ASExternal LSALimit : Disabled Timeout (Count) : Disabled (22)
Originate Default : Disabled
SNMP Traps : Disabled
Redistribute:
Protocol Status cost Type Tag Policy
direct Enabled 1 1 0 None
static Enabled 1 1 0 None
rip Disabled 0 0 0 None
e-bgp Disabled 0 0 0 None
i-bgp Disabled 0 0 0 None
isis-level-1 Disabled 0 0 0 None
isis-level-2 Disabled 0 0 0 None
isis-level-1-external Disabled 0 0 0 None
isis-level-2-external Disabled 0 0 0 None
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
03-13-2015 11:57 AM
The interface doesnt have OSPF on... issue the command "show config ospf" - you will see you ospf config.. there should be a line like " configure ospf add vlan corp_CTAP_agents 3710 area
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
03-13-2015 11:49 AM
I need to wait until the center opens, I will check with them at 10am this morning. I was able to change the port speed to 100 full duplex, it would not let me do 1G.
something is still off, not sure why the vlan is not being injected into ospf, I did a show config full detail, and nothing is different.
something is still off, not sure why the vlan is not being injected into ospf, I did a show config full detail, and nothing is different.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
03-13-2015 11:45 AM
There is... Once you are in the master you can issue the command "telnet slot <#>" - once you change to the other slot you can only run very limited commands, you can do everything you need from the master (doesn't always have to be slot 1). If you do a "show log" are you seeing anything regarding port 3:34? You can search by running "show log | include 3:34" - Also look for any messages regarding stacking... Your biggest issue is the port is not active..
