This is how 6500/7600 works. Each logical interface has an internal vlan associated -- br, Ovidiu #18857 RS
On Fri, Sep 17, 2010 at 6:32 PM, Devon True <de...@noved.org> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > All: > > I noticed that when I created a VRF on a 6500 running 12.2(33)SXH6, it > created another interface: > > #sho vrf ipv4 interfaces > Interface VRF Protocol > Address > Vlan916 VRFNAME up > x.x.x.162 > VRF_1_vlan1020 VRFNAME up > x.x.x.162 > > We are using "vrf definitions" > > vrf definition VRFNAME > rd x.x.x.x:914 > ! > address-family ipv4 > route-target export asn:914 > route-target import asn:914 > route-target import asn:902 > exit-address-family > > I cannot do a "show int VRF_1_vlan1020" on this mysterious interface. Any one > have an idea why it was created? > > Thanks for any insight. > > - -- > Devon > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.12 (MingW32) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iEYEARECAAYFAkyTig0ACgkQWP2WrBTHBS+DFgCghxvDuH/++WoZRLp3zqJwDH68 > q8UAoPB0/HWL8GFJLh7Tm1QyRlgv3yPq > =v7AO > -----END PGP SIGNATURE----- > _______________________________________________ > cisco-nsp mailing list cisco-...@puck.nether.net > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/