cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
601
Views
0
Helpful
2
Replies

NAM virtual appliance deploy

Hello,

I have two Nexus 1010 with VSM configured and working ok. I have deployed NAM in this Nexus 1010 ok, but i can't access to the management ip, (don't ping to default gateway). I have deployed the uplinks in Nexus 1010 as type 3 and the intereface data of NAM in vlan of management. This is correct?.

Otherwise I do not see clear as NAM deploy high availability, according to the documentation is not supported for NAM,so NAM must deploy different in each Nexus 1010.

Regards.              

2 Replies 2

mwronkow
Cisco Employee
Cisco Employee

Hello Ernesto,

The NAM management IP is tied to the 'data' vlan that was configured under the virtual-service-blade.

virtual-service-blade NAM5

  virtual-service-blade-type name NAM-1.1

  interface data vlan 119     <----------NAM mgmt would be in this vlan.

  ramsize 2048

  disksize 53

Hello,

I have the NAM data vlan assigned to the management network with a ip of management, but i can't access

virtual-service-blade NAM1

  Description: 

  Slot id:        2

  Host Name:      nam1

  Management IP:  10.12.222.90

  VSB Type Name :  NAM-1.1

  Interface:             data    vlan:    903

  Interface:         internal    vlan:     NA

  vCPU:           2

  Ramsize:        2048

  Disksize:       53

  Heartbeat:      178681

  HA Admin role: Primary 

    HA Oper role: ACTIVE

    Status:       VSB POWERED ON

    Location:     PRIMARY

    SW version:   5.1(1)

  HA Admin role: Secondary 

    HA Oper role: NONE

    Status:       VSB NOT PRESENT

    Location:     SECONDARY

    SW version:   5.1(1)

  VSB Info: 

    Domain ID : 301

virtual-service-blade VSM-1

  Description: 

  Slot id:        1

  Host Name:      Nx1000V-VSM-1

  Management IP:  10.12.222.92

  VSB Type Name :  VSM-1.1

  Interface:          control    vlan:     52

  Interface:       management    vlan:    903

  Interface:           packet    vlan:     52

  Interface:         internal    vlan:     NA

  vCPU:           1

  Ramsize:        2048

  Disksize:       3

  Heartbeat:      20544140

  HA Admin role: Primary 

    HA Oper role: STANDBY

    Status:       VSB POWERED ON

    Location:     PRIMARY

    SW version:   4.2(1)SV1(5.1a)

  HA Admin role: Secondary 

    HA Oper role: ACTIVE

    Status:       VSB POWERED ON

    Location:     SECONDARY

    SW version:   4.2(1)SV1(5.1a)

  VSB Info: 

    Domain ID : 2

virtual-service-blade NAM1
  Description: 
  Slot id:        2
  Host Name:      nam1
  Management IP:  10.12.222.90
  VSB Type Name :  NAM-1.1
  Interface:             data    vlan:    903
  Interface:         internal    vlan:     NA
  vCPU:           2
  Ramsize:        2048
  Disksize:       53
  Heartbeat:      178681
  HA Admin role: Primary 
    HA Oper role: ACTIVE
    Status:       VSB POWERED ON
    Location:     PRIMARY
    SW version:   5.1(1)
  HA Admin role: Secondary 
    HA Oper role: NONE
    Status:       VSB NOT PRESENT
    Location:     SECONDARY
    SW version:   5.1(1)
  VSB Info: 
    Domain ID : 301

This vlan 903 work fine for VSM deployed in the same Nexus 1010

virtual-service-blade VSM-1
  Description: 
  Slot id:        1
  Host Name:      Nx1000V-VSM-1
  Management IP:  10.12.222.92
  VSB Type Name :  VSM-1.1
  Interface:          control    vlan:     52
  Interface:       management    vlan:    903
  Interface:           packet    vlan:     52
  Interface:         internal    vlan:     NA
  vCPU:           1
  Ramsize:        2048
  Disksize:       3
  Heartbeat:      20544140
  HA Admin role: Primary 
    HA Oper role: STANDBY
    Status:       VSB POWERED ON
    Location:     PRIMARY
    SW version:   4.2(1)SV1(5.1a)
  HA Admin role: Secondary 
    HA Oper role: ACTIVE
    Status:       VSB POWERED ON
    Location:     SECONDARY
    SW version:   4.2(1)SV1(5.1a)
  VSB Info: 
    Domain ID : 2

Regards.

Review Cisco Networking for a $25 gift card