topic RE: Add vlan to existing switch and ospf routing in ExtremeSwitching (EXOS/Switch Engine)

Add vlan to existing switch and ospf routing

Sidney_Yoder — Fri, 13 Mar 2015 07:00:00 GMT

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

RE: Add vlan to existing switch and ospf routing

Bill_Stritzinge — Fri, 13 Mar 2015 07:06:00 GMT

Sidney,

Not sure I have everything correct, but if you created the vlan corp_CTAP and need to ping the default route on the OSPF interface XO_VPLS_MESH, if you are using full dynamic routing you need to have OSPF enabled on the corp_CTAP vlan.. Can you show me the output of "show iproute" and give me a little more background on what it routing where?

Bill

RE: Add vlan to existing switch and ospf routing

Bill_Stritzinge — Fri, 13 Mar 2015 07:10:00 GMT

Sidney,

Sorry for the second response but it looks like you don't have any interfaces active in the corp_CTAP vlan. See the following:

corp_CTAP_agents 3710 10.131.82.1 /24 -f----------------------- ANY 0 /1 VR-Default

see the 0/1 above... if there aren't any active interfaces in the vlan you wont be able to ping... to test enable loopback on the vlan.... "enable loopback vlan corp_CTAP_agents" - you will then be able to ping.. give that a shot..

Bill

RE: Add vlan to existing switch and ospf routing

simon_bingham — Fri, 13 Mar 2015 13:55:00 GMT

. (Number of active ports=0)

ports not up

RE: Add vlan to existing switch and ospf routing

Sidney_Yoder — Fri, 13 Mar 2015 17:40:00 GMT

The iproute also when I did a show config ospf it shows that corp_CTAP ? do I still need to run the cmd enable ospf ctap?

* Slot-1 CTAP-Cosmo-Stack.1 # show iproute
Ori Destination Gateway Mtr Flags VLAN Duration
#o1 Default Route 10.128.254.1 65 UG-D---um--f- XO_VPLS_MESH 15d:0h:5m:32s
#o1 Default Route 10.128.254.2 65 UG-D---um---- XO_VPLS_MESH 15d:0h:5m:32s
#d 10.20.50.0/24 10.20.50.1 1 U------um--f- EVN 98d:15h:46m:24s
#o1 10.50.53.0/24 10.128.254.1 65 UG-D---um--f- XO_VPLS_MESH 15d:0h:5m:32s
#o1 10.50.53.0/24 10.128.254.2 65 UG-D---um---- XO_VPLS_MESH 15d:0h:5m:32s
#oa 10.128.0.0/28 10.128.254.1 45 UG-D---um--f- XO_VPLS_MESH 15d:0h:5m:32s
#oa 10.128.0.0/28 10.128.254.2 45 UG-D---um---- XO_VPLS_MESH 15d:0h:5m:32s
#oa 10.128.0.16/28 10.128.254.5 45 UG-D---um--f- XO_VPLS_MESH 15d:0h:5m:32s
#oa 10.128.0.16/28 10.128.254.6 45 UG-D---um---- XO_VPLS_MESH 15d:0h:5m:32s
#d 10.128.254.0/24 10.128.254.4 1 U------um--f- XO_VPLS_MESH 98d:15h:46m:23s
#oa 10.130.2.0/23 10.128.254.1 55 UG-D---um--f- XO_VPLS_MESH 15d:0h:5m:32s
#oa 10.130.2.0/23 10.128.254.2 55 UG-D---um---- XO_VPLS_MESH 15d:0h:5m:32s
#oa 10.130.4.0/23 10.128.254.1 55 UG-D---um--f- XO_VPLS_MESH 15d:0h:5m:32s
#oa 10.130.4.0/23 10.128.254.2 55 UG-D---um---- XO_VPLS_MESH 15d:0h:5m:32s
#oa 10.130.6.0/23 10.128.254.1 55 UG-D---um--f- XO_VPLS_MESH 15d:0h:5m:32s
#oa 10.130.6.0/23 10.128.254.2 55 UG-D---um---- XO_VPLS_MESH 15d:0h:5m:32s
#oa 10.130.8.0/21 10.128.254.1 55 UG-D---um--f- XO_VPLS_MESH 15d:0h:5m:32s
#oa 10.130.8.0/21 10.128.254.2 55 UG-D---um---- XO_VPLS_MESH 15d:0h:5m:32s
#o1 10.130.16.0/23 10.128.254.1 65 UG-D---um--f- XO_VPLS_MESH 15d:0h:5m:32s
#o1 10.130.16.0/23 10.128.254.2 65 UG-D---um---- XO_VPLS_MESH 15d:0h:5m:32s
#oa 10.130.18.0/24 10.128.254.1 55 UG-D---um--f- XO_VPLS_MESH 15d:0h:5m:32s
#oa 10.130.18.0/24 10.128.254.2 55 UG-D---um---- XO_VPLS_MESH 15d:0h:5m:32s
#oa 10.130.20.0/23 10.128.254.1 55 UG-D---um--f- XO_VPLS_MESH 15d:0h:5m:32s
#oa 10.130.20.0/23 10.128.254.2 55 UG-D---um---- XO_VPLS_MESH 15d:0h:5m:32s
#oa 10.130.22.0/23 10.128.254.1 55 UG-D---um--f- XO_VPLS_MESH 15d:0h:5m:35s
#oa 10.130.22.0/23 10.128.254.2 55 UG-D---um---- XO_VPLS_MESH 15d:0h:5m:35s
#oa 10.130.24.0/26 10.128.254.1 55 UG-D---um--f- XO_VPLS_MESH 15d:0h:5m:35s
#oa 10.130.24.0/26 10.128.254.2 55 UG-D---um---- XO_VPLS_MESH 15d:0h:5m:35s
#oa 10.130.32.0/23 10.128.254.1 46 UG-D---um--f- XO_VPLS_MESH 15d:0h:5m:35s
#oa 10.130.32.0/23 10.128.254.2 46 UG-D---um---- XO_VPLS_MESH 15d:0h:5m:35s
#oa 10.130.64.0/23 10.128.254.1 46 UG-D---um--f- XO_VPLS_MESH 15d:0h:5m:35s
#oa 10.130.64.0/23 10.128.254.2 46 UG-D---um---- XO_VPLS_MESH 15d:0h:5m:35s
#oa 10.130.124.0/23 10.128.254.1 46 UG-D---um--f- XO_VPLS_MESH 14d:11h:8m:31s
#oa 10.130.124.0/23 10.128.254.2 46 UG-D---um---- XO_VPLS_MESH 14d:11h:8m:31s
#oa 10.130.128.0/23 10.128.254.1 46 UG-D---um--f- XO_VPLS_MESH 15d:0h:5m:35s
#oa 10.130.128.0/23 10.128.254.2 46 UG-D---um---- XO_VPLS_MESH 15d:0h:5m:35s
#oa 10.130.130.0/23 10.128.254.1 46 UG-D---um--f- XO_VPLS_MESH 15d:0h:5m:35s
#oa 10.130.130.0/23 10.128.254.2 46 UG-D---um---- XO_VPLS_MESH 15d:0h:5m:35s
#oa 10.130.132.0/23 10.128.254.1 46 UG-D---um--f- XO_VPLS_MESH 15d:0h:5m:35s
#oa 10.130.132.0/23 10.128.254.2 46 UG-D---um---- XO_VPLS_MESH 15d:0h:5m:35s
#oa 10.130.134.0/23 10.128.254.1 46 UG-D---um--f- XO_VPLS_MESH 15d:0h:5m:36s
#oa 10.130.134.0/23 10.128.254.2 46 UG-D---um---- XO_VPLS_MESH 15d:0h:5m:36s
#oa 10.130.136.0/23 10.128.254.1 46 UG-D---um--f- XO_VPLS_MESH 15d:0h:5m:36s
#oa 10.130.136.0/23 10.128.254.2 46 UG-D---um---- XO_VPLS_MESH 15d:0h:5m:36s
#oa 10.130.240.0/23 10.128.254.1 45 UG-D---um--f- XO_VPLS_MESH 15d:0h:5m:36s
#oa 10.130.240.0/23 10.128.254.2 45 UG-D---um---- XO_VPLS_MESH 15d:0h:5m:36s
#oa 10.131.4.0/23 10.128.254.1 46 UG-D---um--f- XO_VPLS_MESH 15d:0h:5m:36s
#oa 10.131.4.0/23 10.128.254.2 46 UG-D---um---- XO_VPLS_MESH 15d:0h:5m:36s
#o2 10.131.8.0/24 10.128.254.1 10 UG-D---um--f- XO_VPLS_MESH 15d:0h:5m:36s
#o2 10.131.8.0/24 10.128.254.2 10 UG-D---um---- XO_VPLS_MESH 15d:0h:5m:36s
#o2 10.131.9.0/24 10.128.254.1 10 UG-D---um--f- XO_VPLS_MESH 15d:0h:5m:36s
#o2 10.131.9.0/24 10.128.254.2 10 UG-D---um---- XO_VPLS_MESH 15d:0h:5m:36s
#o2 10.131.10.0/24 10.128.254.1 10 UG-D---um--f- XO_VPLS_MESH 15d:0h:5m:36s
#o2 10.131.10.0/24 10.128.254.2 10 UG-D---um---- XO_VPLS_MESH 15d:0h:5m:36s
#o2 10.131.11.0/24 10.128.254.1 10 UG-D---um--f- XO_VPLS_MESH 15d:0h:5m:36s
#o2 10.131.11.0/24 10.128.254.2 10 UG-D---um---- XO_VPLS_MESH 15d:0h:5m:36s
#oa 10.131.20.0/24 10.128.254.1 55 UG-D---um--f- XO_VPLS_MESH 15d:0h:5m:36s
#oa 10.131.20.0/24 10.128.254.2 55 UG-D---um---- XO_VPLS_MESH 15d:0h:5m:36s
#o2 10.131.64.0/24 10.128.254.1 10 UG-D---um--f- XO_VPLS_MESH 15d:0h:5m:36s
#o2 10.131.64.0/24 10.128.254.2 10 UG-D---um---- XO_VPLS_MESH 15d:0h:5m:36s
#o2 10.131.68.0/24 10.128.254.1 10 UG-D---um--f- XO_VPLS_MESH 6d:20h:58m:44s
#o2 10.131.68.0/24 10.128.254.2 10 UG-D---um---- XO_VPLS_MESH 6d:20h:58m:44s
#o2 10.131.69.0/24 10.128.254.1 10 UG-D---um--f- XO_VPLS_MESH 0d:2h:3m:37s
#o2 10.131.69.0/24 10.128.254.2 10 UG-D---um---- XO_VPLS_MESH 0d:2h:3m:37s
#o2 10.131.72.0/24 10.128.254.1 10 UG-D---um--f- XO_VPLS_MESH 13d:4h:53m:33s
#o2 10.131.72.0/24 10.128.254.2 10 UG-D---um---- XO_VPLS_MESH 13d:4h:53m:33s
#oa 10.131.80.0/23 10.128.254.1 55 UG-D---um--f- XO_VPLS_MESH 1d:19h:8m:44s
#oa 10.131.80.0/23 10.128.254.2 55 UG-D---um---- XO_VPLS_MESH 1d:19h:8m:44s
d 10.131.82.0/24 10.131.82.1 1 -------um---- corp_CTAP_agents 1d:12h:39m:31s
#oa 10.131.82.0/24 10.128.254.1 46 UG-D---um--f- XO_VPLS_MESH 1d:12h:51m:12s
#oa 10.131.82.0/24 10.128.254.2 46 UG-D---um---- XO_VPLS_MESH 1d:12h:51m:12s
#oa 10.131.83.0/27 10.128.254.1 46 UG-D---um--f- XO_VPLS_MESH 1d:12h:52m:14s
#oa 10.131.83.0/27 10.128.254.2 46 UG-D---um---- XO_VPLS_MESH 1d:12h:52m:14s
#oa 10.132.2.0/23 10.128.254.5 55 UG-D---um--f- XO_VPLS_MESH 15d:0h:5m:36s
#oa 10.132.2.0/23 10.128.254.6 55 UG-D---um---- XO_VPLS_MESH 15d:0h:5m:36s
#oa 10.132.4.0/23 10.128.254.5 55 UG-D---um--f- XO_VPLS_MESH 15d:0h:5m:36s
#oa 10.132.4.0/23 10.128.254.6 55 UG-D---um---- XO_VPLS_MESH 15d:0h:5m:36s
#oa 10.132.8.0/21 10.128.254.5 55 UG-D---um--f- XO_VPLS_MESH 15d:0h:5m:36s
#oa 10.132.8.0/21 10.128.254.6 55 UG-D---um---- XO_VPLS_MESH 15d:0h:5m:36s
#oa 10.132.20.0/25 10.128.254.5 55 UG-D---um--f- XO_VPLS_MESH 15d:0h:5m:36s
#oa 10.132.20.0/25 10.128.254.6 55 UG-D---um---- XO_VPLS_MESH 15d:0h:5m:37s
#oa 10.132.240.0/23 10.128.254.5 45 UG-D---um--f- XO_VPLS_MESH 15d:0h:5m:37s
#oa 10.132.240.0/23 10.128.254.6 45 UG-D---um---- XO_VPLS_MESH 15d:0h:5m:37s
#oa 10.133.4.0/23 10.128.254.5 46 UG-D---um--f- XO_VPLS_MESH 15d:0h:5m:37s
#oa 10.133.4.0/23 10.128.254.6 46 UG-D---um---- XO_VPLS_MESH 15d:0h:5m:37s
#oa 10.133.8.0/24 10.128.254.5 55 UG-D---um--f- XO_VPLS_MESH 15d:0h:5m:37s
#oa 10.133.8.0/24 10.128.254.6 55 UG-D---um---- XO_VPLS_MESH 15d:0h:5m:37s
#oa 10.134.132.0/22 10.128.254.1 145 UG-D---um--f- XO_VPLS_MESH 15d:0h:5m:37s
#oa 10.134.132.0/22 10.128.254.2 145 UG-D---um---- XO_VPLS_MESH 15d:0h:5m:37s
#o1 72.5.65.0/24 10.128.254.1 5045 UG-D---um--f- XO_VPLS_MESH 15d:0h:5m:37s
#o1 72.5.65.0/24 10.128.254.2 5045 UG-D---um---- XO_VPLS_MESH 15d:0h:5m:37s
#o1 74.201.114.0/24 10.128.254.1 5045 UG-D---um--f- XO_VPLS_MESH 15d:0h:5m:37s
#o1 74.201.114.0/24 10.128.254.2 5045 UG-D---um---- XO_VPLS_MESH 15d:0h:5m:37s
#d 172.16.50.0/24 172.16.50.1 1 U------um--f- IPC 98d:15h:46m:29s
#oa 172.16.60.0/24 10.128.254.1 46 UG-D---um--f- XO_VPLS_MESH 15d:0h:5m:37s
#oa 172.16.60.0/24 10.128.254.2 46 UG-D---um---- XO_VPLS_MESH 15d:0h:5m:37s
#oa 172.16.70.0/24 10.128.254.5 55 UG-D---um--f- XO_VPLS_MESH 15d:0h:5m:37s
#oa 172.16.70.0/24 10.128.254.6 55 UG-D---um---- XO_VPLS_MESH 15d:0h:5m:37s
#d 192.168.50.0/24 192.168.50.1 1 U------um--f- IVN 98d:15h:46m:29s
#oa 192.168.60.0/24 10.128.254.1 55 UG-D---um--f- XO_VPLS_MESH 15d:0h:5m:37s
#oa 192.168.60.0/24 10.128.254.2 55 UG-D---um---- XO_VPLS_MESH 15d:0h:5m:37s
#oa 192.168.70.0/24 10.128.254.5 55 UG-D---um--f- XO_VPLS_MESH 15d:0h:5m:37s
#oa 192.168.70.0/24 10.128.254.6 55 UG-D---um---- XO_VPLS_MESH 15d:0h:5m:37s
#d 192.168.112.0/24 192.168.112.1 1 U------um--f- CTAP-Agent 98d:15h:46m:28s
#o2 192.168.242.0/24 10.128.254.1 10 UG-D---um--f- XO_VPLS_MESH 8d:5h:27m:6s
#o2 192.168.242.0/24 10.128.254.2 10 UG-D---um---- XO_VPLS_MESH 8d:5h:27m:6s
#oa 192.168.248.0/24 10.128.254.1 55 UG-D---um--f- XO_VPLS_MESH 15d:0h:5m:37s
#oa 192.168.248.0/24 10.128.254.2 55 UG-D---um---- XO_VPLS_MESH 15d:0h:5m:37s
#o1 198.105.200.0/23 10.128.254.1 5045 UG-D---um--f- XO_VPLS_MESH 15d:0h:5m:37s
#o1 198.105.200.0/23 10.128.254.2 5045 UG-D---um---- XO_VPLS_MESH 15d:0h:5m:37s

RE: Add vlan to existing switch and ospf routing

Sidney_Yoder — Fri, 13 Mar 2015 17:46:00 GMT

I also have a pc connected to the port 3:44, which I thought was still turned on, it's in CA, I'm in Tx.

RE: Add vlan to existing switch and ospf routing

Bill_Stritzinge — Fri, 13 Mar 2015 18:14:00 GMT

Sidney,

It looks like your default route it set on the XO_VPLS_MESH interface,

#01 Default Route 10.128.254.1 65 UG-D---um--f- XO_VPLS_MESH 15d:0h:5m:32s
#o1 Default Route 10.128.254.2 65 UG-D---um---- XO_VPLS_MESH 15d:0h:5m:32s

But if you look at the other interface:

corp_CTAP_agents 3710 10.131.82.1 /24 -f----------------------- ANY 0 /1 VR-Default

You are missing the small "o" that would designate ospf is enabled on the interface, regardless with the default set you should still have connectivity if all else is there.

Given all of the above and that your default routes are defined, if the interface it up (which it shows above that it is not) you should still be able to ping it. You can check the port 3:34 by issuing the command "show port 3:44 info detail" to see if it is enabled and if it is up or down.

Bill

RE: Add vlan to existing switch and ospf routing

Sidney_Yoder — Fri, 13 Mar 2015 18:18:00 GMT

I checked the port and it does show down, even though i've enable it, I also tried to turn on the loopback and I still could not ping it.

if you are on the core lic, not the top level license is there a limit to how many vlan's you can have that would route? from what I can tell i've created it the same as CTAP_agents.

RE: Add vlan to existing switch and ospf routing

Bill_Stritzinge — Fri, 13 Mar 2015 18:24:00 GMT

If you have a device connected, I would would force the port out of auto-negotiate (default) - "configure port <#> auto off speed 1000 duplex full" - And see if that gets the device up.. Sometimes auto-negotiate doesn't always work with some other vendors.

As to OSPF, in advanced-edge mode - you can see the license level "show license" - you can can get 4 active ospf interfaces, core license take that to 400 (hardware dependent). Look like you only have one enabled thus far so I assume you have advanced-edge and would have three more available.

RE: Add vlan to existing switch and ospf routing

Sidney_Yoder — Fri, 13 Mar 2015 18:35:00 GMT

this is a stacked unit, 3 total, what's the cmd to switch to the 1st. switch?

RE: Add vlan to existing switch and ospf routing

Bill_Stritzinge — Fri, 13 Mar 2015 18:39:00 GMT

Telnet to the specific slot # - You cannot run many commands from backup or standby nodes, when you telnet into the switch just issue the command "show license" and you will see the level. To see what slot is in what role, run the command "show stacking" - it will list the "master" and backup or standby nodes by slot #. Check the "show stacking" to make sure all are up and have roles.

RE: Add vlan to existing switch and ospf routing

Sidney_Yoder — Fri, 13 Mar 2015 18:42:00 GMT

Advanced Edge, when i log in it takes me to the 2nd switch, not the primary, when i do a show stacking it shows all three. i thought there was a way to telnet or switch to the various stacking units.

RE: Add vlan to existing switch and ospf routing

Bill_Stritzinge — Fri, 13 Mar 2015 18:45:00 GMT

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..

RE: Add vlan to existing switch and ospf routing

Sidney_Yoder — Fri, 13 Mar 2015 18:49:00 GMT

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.

RE: Add vlan to existing switch and ospf routing

Bill_Stritzinge — Fri, 13 Mar 2015 18:57:00 GMT

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 " if not and you want to add the vlan -

"configure ospf add vlan corp_CTAP_agents 3710 area "

Until you see the small "o" in the flags (like in the XO vlan) - ospf will not be active on the interface.

Also do a "show ospf" to make sure it is globally enabled as well...

RE: Add vlan to existing switch and ospf routing

Sidney_Yoder — Fri, 13 Mar 2015 20:44:00 GMT

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

RE: Add vlan to existing switch and ospf routing

Bill_Stritzinge — Fri, 13 Mar 2015 20:51:00 GMT

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"

RE: Add vlan to existing switch and ospf routing

Sidney_Yoder — Fri, 13 Mar 2015 20:58:00 GMT

I had our center mgr, move the cable from sw3 to sw2 and you can see it's active, still can not ping it.

i'm running this code:
: ExtremeXOS version 12.6.5.2 v1265b2-patch1-3 by release-manager on Thu Feb 20 19:12:11 EST 2014
BootROM : 1.0.3.5
Diagnostics : 3.4

i wish we could upgrade but we can not.

RE: Add vlan to existing switch and ospf routing

Bill_Stritzinge — Fri, 13 Mar 2015 21:14:00 GMT

I assume that the PC can ping the switch now?? 10.131.82.1 ? From the switch can you ping the PC? Then run the command "show iproute origin direct" - you should see something like this...

#d 10.131.82.0/24 etc....

Make sure fowarding is still enabled... "enable ipforwarding vlan corp_CTAP_agents"

You can also do a "show iparp vlan corp_CTAP_agents" and see the IP's of the interface as well as the PC...

RE: Add vlan to existing switch and ospf routing

Sidney_Yoder — Fri, 13 Mar 2015 22:14:00 GMT

another odd item is when i do a show iparp, i'm not seeing the vlan, I have a laptop plugged in now.