Switching

Hi,

I'm trying to setup out of band management while using vme.0 but can't seem to get it to work. I have virtual chassis with six EX4300. I have a ethernet cable plugged in the mgmt port behind the master switch to cisco mgmt switch I setup. If assign an ip to the me0.0 interface, I'm able to ssh into it from my cisco switch. 

The problem is I can't get it to work on the vme.0 interface. I want to be able to access these from my switch on a different network.  Any help or insight on what I'm doing wrong would be great. 

this the template I used to apply an ip to the interface 

{edit interfaces]
lab@s1# set vme.0 family inet address 1.1.1.1/24

HI,

This should work.

Could you please paste the outputs of

show interface terse | match vme

show arp no-resolve 

show interface vme.0 extensive

Also if you are trying to access this from another network add a static route pointng to g/w as shown below

set routing-options static route 0/0 next-hop x.x.x.x

Thanks.

Partha

How is your OOB network physically cabled?

Remember that the vme port use the out-of-band physical ME port on the rear of your member switches.  Traffic that arrives on the switches transit ports cannot reach the me port on the switch itself.  Your me ports will need to be connected to a vlan that is reachable by your mgmt stations.

Hi Partha,

Here’s the output to what you asked. The virtual chassis has redistributing BGP routes into OSPF. How can I setup a different route just for my mgmt switch while keeping my default routes for the users. Virtual router, routing instances?

 Hi Spuluka,

Yes I have a cat6 cable from the master SW mgmt port to a 3750 cisco switch. Are you saying to create a vlan and having the vme.0 be a member of it?

Is this how you create the vlan with an IP?

set vlans mgmt

set vlans mgmt vlan-id 133

set interfaces clan unit133 family inet address 1.1.1.1/26

{master:0}

root@SW> show interfaces terse | match vme 

vme                     up    down

vme.0                   up    down inet     10.0.0.126

{master:0}

root@SW> show arp no-resolve 

MAC Address       Address         Interface     Flags

84:b5:9c:c0:8b:c8 10.40.X.X     ge-0/2/0.0           none

00:15:2b:84:d2:c2 10.40.X.X     ge-1/0/0.0           none

00:22:4d:ab:3d:49 10.40.X.X    ge-3/0/42.0          none

54:be:f7:66:91:aa 10.40.X.X    ge-0/0/45.0          none

00:e0:db:41:ea:bc 10.40.X.X    ge-2/0/23.0          none

00:e0:db:41:eb:00 10.40.X.X   ge-2/0/47.0          none

68:5b:35:b0:6c:bf 10.40.X.X   ge-2/0/36.0          none

1c:99:4c:be:dc:29 10.40.X.X    ge-4/0/46.0          none

c0:f8:da:63:90:21 10.40.X.X    ge-3/0/47.0          none

18:64:72:c1:a7:d4 10.40.X.X    ge-3/0/47.0          none

18:64:72:c1:a7:c8 10.40.X.X    ge-3/0/44.0          none

18:64:72:c1:a7:cc 10.40.X.X    ge-3/0/45.0          none

18:64:72:c1:a6:ec 10.40.X.X    ge-4/0/46.0          none

18:64:72:c1:9e:d2 10.40.X.X   ge-4/0/45.0          none

18:64:72:c1:a7:da 10.40.X.X   ge-4/0/44.0          none

18:64:72:c1:a7:84 10.40.X.X   ge-3/0/46.0          none

18:64:72:c1:a7:9c 10.40.X.X   ge-4/0/47.0          none

02:00:00:00:00:0b 128.0.0.5       bme0.0               permanent

02:00:00:00:00:0b 128.0.0.6       bme0.0               permanent

02:00:00:00:00:0b 128.0.0.17      bme0.0               permanent

02:00:00:00:00:0c 128.0.0.18      bme0.0               permanent

02:00:00:00:00:0d 128.0.0.19      bme0.0               permanent

02:00:00:00:00:0e 128.0.0.20      bme0.0               permanent

02:00:00:00:00:0f 128.0.0.21      bme0.0               permanent

Total entries: 24

{master:0}

root@uscentswp01> show interfaces vme.0 extensive 

  Logical interface vme.0 (Index 6) (SNMP ifIndex 36) (Generation 13)

    Flags: Hardware-Down Device-Down SNMP-Traps 0x0 Encapsulation: ENET2

    Bandwidth: 1000mbps

    Routing Instance: __juniper_private1__ Bridging Domain: mgmt

    Traffic statistics:

     Input  bytes  :                    0

     Output bytes  :                    0

     Input  packets:                    0

     Output packets:                    0

    Local statistics:

     Input  bytes  :                    0

     Output bytes  :                    0

     Input  packets:                    0

     Output packets:                    0

    Protocol inet, MTU: 9498, Generation: 173, Route table: 0

      Flags: Sendbcast-pkt-to-re

      Addresses, Flags: Dest-route-down Is-Preferred Is-Primary

        Destination: 10.40.X.X/26, Local: 10.0.0.126,

        Broadcast: 10.40.X.X, Generation: 5

Hi,

I can see your problem u need to access the SW from different subnet without setting the default route on the switch as there is already existing default route configured.

If the other end is Cisco router for MGT subnet I will suggest u to use source NAT interface for the outgoing traffic from Cisco side hit the EX VC MGT interface, that will force the traffic to come back to Cisco and your MGT subnet without setting any routing on the EX VC.

Regards,

Mohamed Elhariry

The other option is the create a routing-instance for all the other ports and change the default route in the root routing table to be the one necessary for the ME ports.

The ME ports cannot be moved and will always be in the root routing table.

You have to rename me0 to vme.

#rename interfaces me0 to vme
#set interfaces vme unit 0 family inet address 1.1.1.1/24

This is the routing instance I tried on our srx550 and mx5. I still wasn't able to ssh from my cisco switch into these routers after my configuration on the routers. The ip on my mgmt cisco switch is 10.1.1.4 and can't ping it from my routers. Any input on how to exactly configure these type of setup?

Well in this new scenario, it looks like you are configuring a tagged trunk port facing the cisco switch.  Is the Cisco port also setup as a tagged trunk port?

Also make sure the SRX is in packet mode or you have added permission in host inbound services to allow ping on the interface in the zone assigned.