Can't Reach Interface After Changing VRF

[Anonymous]

Hi,

There is probably a very simple answer to this question, but can't think what it is?

Very high level I have the following configuration:

code:

interface vlan 1999
description "Server Switch Management"
exit

config t
rbridge 11
interface ve 1999
ip address 172.24.110.11/24
ip route 0.0.0.0/0 172.24.110.254

vcs virtual ip address 172.24.110.10/24 inband interface ve 1999

configure
interface port-channel 10
switchport
switchport mode trunk
switchport trunk allowed vlan add 1999
switchport trunk tag native-vlan
no shutdown

int te 11/0/1
channel-group 10 mode active type standard
lacp default-up
int te 12/0/1
channel-group 10 mode active type standard
lacp default-up

This worked find and I could reach both the virtual IP address (172.24.110.10) and the Vlan 1999 interface (172.24.110.10).

The logical chassis has no other L3 addresses as is primarily just being used at L2.

The switch was on a version 6 code, and had been trying to upgrade it to version 7 but just kept erroring that it couldn't reach the SCP / FTP server even though I could ping it.

It seems in version 6 your unable to select the VRF to use when doing the firmware download, so it is defaulting I believe to mgmt-vrf.

So what I did is add the following command to ve 1999

code:

vrf forwarding mgmt-vrf

Since I did that I lost contact to switch. I did anticipate that could happen although I'm not sure why it did?

The other end of the portchannel has the IP address 172.24.110.254, and I would have expected to still been able to reach the switch from the local subnet?

Although the VRF has changed I would expect the VLAN to automatically just reside to the same VRF i.e. just moved from default to management.

Hence where I am stuck, perhaps I'm missing another command?

Many thanks in advance.

[Michael_Morey]

Thanks Martin,

Glad to hear that resolved your issue.

Michael Morey
Principal Technical Support Engineer

[Anonymous]

Hi Michael,

Your thoughts are correct. The reboot, and / or action of upgrading the switches seems to have corrected the problem and subsequently been able to create an interface ve 1999 on all the remaining Rbridges,

Thanks to you both for your perseverance.

[Michael_Morey]

Martin,

Your understanding is correct. VLANs are created globally and should be active on all RBs in a VCS fabric. My point is that the NSM backend error is likely caused by the RB not being in sync with this particular VLAN. In order to force this sync, you can remove and re-add the VLAN or reload the offending device so that it performs a config replay.

[Anonymous]

Hi Michael,

The output of the command you requested is below.

My understanding (rightly or wrongly) is that I'm running the VDX in logical chassis mode, so from a layer 2 perspective creating the VLAN 1999 should exist on every switch.

When I going to 'Rbridge 12' it effectively puts me into the layer 3 router configuration, to which I want to create an IP address on each Rbridge for that VLAN, and where I'm hitting the error.

If on Rbridge 12 I pick a VLAN, say 151, that doesn't have an L3 address configured anywhere this works without a problem. Seems to be just related to ve 1999 that I have an IP address configured on Rbridge 11.

I'm just in the process of upgrading the switches via USB, as without being able to configure the IP's on the other Rbridge's I couldn't do it over the network.

Going from 6.02 to 7.0.2b, and then to 7.2.

The action of upgrading will reboot the switches, so will try again after that and report back.

code:

Col-xx-VSP-Sw11# show vlan brief
Total Number of VLANs configured   : 23
Total Number of VLANs provisioned  : 23
Total Number of VLANs unprovisioned : 0
VLAN            Name           State                     Ports          Classification
(F)-FCoE                                                   (u)-Untagged
(R)-RSPAN                                                  (c)-Converged
(T)-TRANSPARENT                                            (t)-Tagged
================ =============== ========================== =============== ====================
1               default        ACTIVE                    Po 10(t)
                                                           Po 11(t)
                                                           Po 64(t)
22              VLAN0022       INACTIVE(member port down) Po 11(t)
30              VLAN0030       INACTIVE(member port down) Po 11(t)
64              VLAN0064       INACTIVE(member port down) Po 11(t)
70              VLAN0070       INACTIVE(member port down) Po 11(t)
71              VLAN0071       INACTIVE(member port down) Po 11(t)
102             VLAN0102       INACTIVE(member port down) Po 11(t)
146             VLAN0146       INACTIVE(member port down) Po 11(t)
147             VLAN0147       INACTIVE(member port down) Po 11(t)
148             VLAN0148       INACTIVE(member port down) Po 11(t)
149             VLAN0149       INACTIVE(member port down) Po 11(t)
150             VLAN0150       INACTIVE(member port down) Po 11(t)
151             VLAN0151       INACTIVE(member port down) Po 11(t)
199             VLAN0199       INACTIVE(member port down) Po 11(t)
240             VLAN0240       INACTIVE(member port down) Po 11(t)
252             VLAN0252       INACTIVE(member port down) Po 11(t)
1002(F)         VLAN1002       INACTIVE(no member port)
1164            VLAN1164       ACTIVE                    Po 10(t)
                                                           Po 64(t)
1264            VLAN1264       ACTIVE                    Po 10(t)
                                                           Po 64(t)
1999            VLAN1999       ACTIVE                    Po 10(t)
2002            VLAN2002       INACTIVE(member port down) Po 11(t)
2003            VLAN2003       INACTIVE(member port down) Po 11(t)
3333            VLAN3333       INACTIVE(member port down) Po 11(t)

Many thanks,

Martin